{"id":2349,"date":"2020-09-24T12:31:57","date_gmt":"2020-09-24T12:31:57","guid":{"rendered":"https:\/\/support.itscope.hostpress.me\/?post_type=kb&p=2349"},"modified":"2025-04-29T14:26:40","modified_gmt":"2025-04-29T12:26:40","slug":"structure-of-the-order-document-with-licensees","status":"publish","type":"kb","link":"https:\/\/guide.itscope.com\/en\/kb\/structure-of-the-order-document-with-licensees\/","title":{"rendered":"Structure of the ORDER document for an order involving licensees"},"content":{"rendered":"\n

Structure of an order with a licensee<\/h2>\n\n\n\n

<\/p>\n\n\n\n

The same structure applies as described in the article ‘Structure of the ORDER document for a standard purchase order<\/a>‘.<\/p>\n\n\n\n

For orders with licensee details we have provided the following additional structure for the OpenTrans ORDER:<\/p>\n\n\n\n

All orders containing licensee line items have one thing in common: customer data is required. In this case, the customer<\/strong> PARTY_ROLE is used to define the party.<\/p>\n\n\n\n

All required customer data, such as company name, contact person, addresses and contact email address, are defined in the customer<\/strong> party, e.g.:<\/p>\n\n\n\n

<PARTY>\n   <ns2:PARTY_ID type=\"buyer_specific\">K100023<\/ns2:PARTY_ID>\n   <PARTY_ROLE>customer<\/PARTY_ROLE>\n   <ADDRESS>\n      <ns2:NAME>Examplecompany<\/ns2:NAME>\n      <CONTACT_DETAILS>\n         <ns2:CONTACT_NAME>Doe<\/ns2:CONTACT_NAME>\n         <ns2:FIRST_NAME>John<\/ns2:FIRST_NAME>\n         <ns2:PHONE>030123456<\/ns2:PHONE>\n         <ns2:EMAILS>\n            <ns2:EMAIL>john.doe@examplecompany.com<\/ns2:EMAIL>\n         <\/ns2:EMAILS><\/strong>\n      <\/CONTACT_DETAILS>\n      <ns2:STREET>12 Main Street<\/ns2:STREET>\n      <ns2:ZIP>1234<\/ns2:ZIP>\n      <ns2:CITY>Anytown<\/ns2:CITY>\n      <ns2:COUNTRY>USA<\/ns2:COUNTRY>\n      <ns2:COUNTRY_CODED>US<\/ns2:COUNTRY_CODED>\n      <ns2:PHONE type=\"office\">+1 030\/123456<\/ns2:PHONE>\n      <ns2:FAX type=\"office\">+1 030\/1234567<\/ns2:FAX>\n      <ns2:URL>www.examplecompany.com<\/ns2:URL>\n   <\/ADDRESS>\n<\/PARTY><\/pre>\n\n\n\n
There may be multiple customer parties, as an order may contain multiple licensees, and each line item where a licensee is entered will have a reference to the customer party.<\/p>\n\n\n\n
For normal hardware orders, a CUSTOMER_ORDER_REFERENCE entry for each line item is not necessary. For items with a licensee, this is mandatory in order to define a reference to the customer party, e.g.:<\/p>\n\n\n\n
<ORDER_ITEM>\n   \u2026\n   <CUSTOMER_ORDER_REFERENCE>\n      <!--Reference to the end customer party, for their contact details and email details -->\n      <CUSTOMER_IDREF type=\"buyer_specific\">K100023<\/CUSTOMER_IDREF>\n   <\/CUSTOMER_ORDER_REFERENCE>\n<\/ORDER_ITEM><\/pre>\n\n\n\n
Orders with ESD line items<\/h2>\n\n\n\n
In addition to the licensee data mentioned above, an ESD line item within an order must be identified using <PRODUCT_TYPE>esd<\/PRODUCT_TYPE>. This field can be determined by the product family (contractTypeId)<\/a> in the API\/export data formats<\/a>. The ESD email address is read directly from the customer party in the Contact_Details from the <ns2:EMAIL> XML field.<\/p>\n\n\n\n
   \n<ORDER_ITEM>\n   \u2026\n       <PRODUCT_ID>\n            <ns2:SUPPLIER_PID type=\"supplier_specific\">Supplier product ID<\/ns2:SUPPLIER_PID>\n            ...\n            <ns2:PRODUCT_TYPE>esd<\/ns2:PRODUCT_TYPE>\n       <\/PRODUCT_ID>\n \u2026\n<\/ORDER_ITEM> <\/pre>\n\n\n\n
Orders with service line items<\/h2>\n\n\n\n
Service products include eCare Packs, support, exchange and services such as: HP eCare Pack, Fujitsu Support Services, warranty, maintenance, Lenovo Carepacks. In addition to the licensee data mentioned above, a service line item within an order must be identified by <PRODUCT_TYPE>service<\/PRODUCT_TYPE>. The ProductType can be determined by the product family (contractTypeId)<\/a> in the API\/export data formats<\/a>. The customer email of the service recipient is read directly from the customer party in the Contact_Details from the XML field <ns2:EMAIL>. In addition, the full customer address and contact details are also transmitted from the customer party to the supplier. If required, the supplier can then pass on all the necessary data to the respective service provider.<\/p>\n\n\n\n
   \n<ORDER_ITEM>\n   \u2026\n       <PRODUCT_ID>\n            <ns2:SUPPLIER_PID type=\"supplier_specific\">Supplier article number<\/ns2:SUPPLIER_PID>\n            ...\n            <ns2:PRODUCT_TYPE>service<\/ns2:PRODUCT_TYPE>\n       <\/PRODUCT_ID>\n \u2026\n<\/ORDER_ITEM> <\/pre>\n\n\n\n
<\/p>\n\n\n\n
Download examples<\/h2>\n\n\n\n
ESD orders<\/h3>\n\n\n\n
The files are provided with HTML comments to better understand the structure of an ORDER document<\/a>. These files are also valid as reference files for sending test ESD orders to the Partner Test Distributor (DistributorId 10000735), via the ITscope API method business\/deals\/send<\/a><\/strong>.<\/p>\n\n\n\n
Example_ESD_ORDER_Testdistributor_Bestellung_1Party_ESD_only.xml<\/p>\n\n\n\n