Re: [ubl] FW: ubl party document

my immediate comment  to Dirk is that he could just use a PartyTypeCode and not the ContractingPartyType (that contains a PartyTypeCode).

On 26/03/2014, at 10:36 PM, Duvekot, Kees wrote:

> All,
>  
> Here an example of our “RID-Supplier” document that we have defined as part of our UBL implementation. We use this document to inform other systems about newly created suppliers in our ERP system.
>  
> I have included a example of the resulting XML in this email.
> In the ZIP you will find the XSD that we use for this document, plus an sample on how a generic UBL PartyData document might look like create by my collegue.
>  
> If you have any questions then we can discuss this in the UBL Atlantic Call.
>  
> Kees Duvekot
>  
>  
> Van: Lub, Dirk 
> Verzonden: woensdag 26 maart 2014 13:39
> Aan: Duvekot, Kees
> Onderwerp: ubl party document
>  
> Kees,
>  
> We discussed a more standard alternative for our (Rfs)  implementation of a party document:  
>  
> In the attached zip file  you find
>  
> -          Rid_Supplier as the Rfs implementation of a ‘partydocument’ , including the defining spreadsheet.
>  
> -          The result of my effort of creating an UBL party document ( named UBL-PartyData )
>  
> In this document I used:
> cbc:LifeCycleStatusCode             - as replacement of: ecbc:SupplierLifeCycleStatusCode              
> cac:OriginatorParty                        - as replacement of: ecbc:MasterOwnerCode ( the owner of this data )
> cac:Party                                            - should contain the party data
> cac:ContractingPartyType           - to indicate a role  (instead of using ‘SupplierParty’, ‘CustomerParty’, etc)
>  
> notes – I’m not very happy with cac:ContractingParty  - it would be nice if the role could be defined in the Party Type itself
>  
> Regards
> Dirk Lub
>  
>  
>                
>  
>  
>  
>  
>  
> <party.zip><RFS-Supplier.xml>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

-----------------
Regards 
Tim McGrath

Fremantle, Western Australia
http://www.documentengineeringservices.com