Transcription

Oracle Supplier NetworkXML Solutions GuideDate:Version:November 2014Version 1.0

PrefaceIntroductionThis guide provides information on the XML messages supported by the Oracle SupplierNetwork (Oracle SN).AudienceThis guide is intended for the individuals responsible for the development, setup,maintenance, and operations associated with executing electronic transaction integrationfor a company or organization.PrerequisitesBefore reading this document, you should be familiar with the capabilities of the OracleSupplier Network.Important: The information contained in this document is subject to change without notice. If you find any problems in thedocumentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error-free.2

ContentsPreface . 2XML Transaction Overview . 4Purchase Order . 5OAG PROCESS PO 007. 5cXML OrderRequest . 10Mapping Overview . 12Change Purchase Order . 20OAG CHANGE PO 006 . 20cXML OrderRequest Update . 20Mapping Overview . 21Advance Ship Notice (ASN) . 27OAG SHOW SHIPMENT 005 . 27cXML ShipNoticeRequest . 29Mapping Overview . 30Invoice . 33OAG PROCESS INVOICE 002 . 33cXML InvoiceDetailRequest . 35Mapping Overview . 37Appendix A: OAG PROCESS PO Sample Payload . 39Appendix B: cXML OrderRequest Sample Payload. 45Appendix C: OAG CHANGE PO Sample Payload . 49Appendix D: cXML OrderRequest Sample Payload (for Change PO) . 50Appendix E: OAG SHOW SHIPMENT Sample Payload . 54Appendix F: cXML ShipNotice Request Sample Payload . 57Appendix G: OAG PROCESS INVOICE Sample Payload . 59Appendix H: cXML InvoiceDetailRequest Sample Payload . 62Appendix I: HTTP Message Envelope Requirements for OAG Documents . 65Appendix J: cXML Message Header Requirements . 663

XML Transaction OverviewThe Oracle Supplier Network (Oracle SN) enables the exchange of electronic XML messages between OracleApplication customers and their trading partners. Using Oracle SN’s hub-based model, each trading partner canconfigure its preferred transaction standards, identifiers, and delivery methods. The Oracle SN uses these accountpreferences to identify the sending party and to deliver messages to the receiving trading partner. Please refer to theOracle SN Trading Partner Administration Guide to learn more about setting account configurations on the OracleSN.When sending messages to the Oracle SN, the sending trading partner can use 3 delivery mechanisms, HTTP/Sposting, Oracle Transport Adapter and the Oracle SN Web Mailbox. For delivery of the messages, the receivingtrading partner can choose from the following methods, HTTP/S posting, Oracle Transport Adapter, Oracle SN WebMailbox and Email through SMTP.The Oracle SN supports the Open Applications Group (OAG) and Commerce XML (cXML) standards. Messages sentto the Oracle SN must comply with the appropriate standard. Oracle SN can transform XML messages as requiredby the receiving trading partner. The Oracle SN supports the following transaction flows:Inbound To Oracle SNOAG PROCESS POOAG PROCESS POOAG CHANGE POOAG CHANGE POOAG SHOW SHIPMENTcXML ShipNoticeRequestOAG PROCESS INVOICEcXML InvoiceDetailRequestActivity by Oracle mationOutbound From Oracle SNOAG PROCESS POcXML OrderRequestOAG CHANGE POcXML OrderRequestOAG SHOW SHIPMENTOAG SHOW SHIPMENTOAG PROCESS INVOICEOAG PROCESS INVOICEWhen sending messages to the Oracle SN, the sender uses an envelope or cXML header to describe the sending party,receiving party and other information to identify the contents. Please read the message envelope and cXML headerappendix sections to understand more about the requirements. For Oracle Applications customers sending messagesto the Oracle SN, the Oracle Transport Adapter creates the envelope automatically. Please read the guide onConnecting R12 to the Oracle SN for more information.Note: Attachments are not supported on the Oracle SN at this time.4

Purchase OrderPurchase Order transactions are sent by a buying organization from their Oracle Purchasing Applications. TheOracle Supplier Network will receive a PROCESS PO 007 OAG XML payload from the buyer and will route it to thesupplier, or transform it into a cXML OrderRequest. The OAG order is transformed into a cXML OrderRequestwhen the supplier has specified, on the Oracle SN, their preferred Purchase Order format as cXML. This sectiondescribes both the OAG PROCESS PO 007 and the cXML OrderRequest that suppliers can choose to receive fromthe Oracle SN. The Oracle SN makes certain mapping decisions in generating the cXML order based on OAG dataelements, which are described in the following sections.OAG PROCESS PO 007Field DescriptionsThe following table describes the data types (fields) in the DTD that are used by the Oracle Purchasing Applicationto generate the PROCESS PO 007 message. For complete information on the OAG BOD, refer to the Business ObjectDefinition included within the Open Applications Group Integration Specification Release 7.2.1 athttp://www.openapplications.org.OAGIS PROCESS PO 007Required? CNTROLAREA BSR VERB value ”PROCESS” NOUN value ”PO” REVISION value “007” SENDER RequiredRequiredRequiredRequiredRequired LOGICALID COMPONENT TASK REFERENCEDID CONFIRMATION RequiredRequiredRequiredRequiredRequired LANGUAGE CODEPAGE AUTHID DATETIME (CREATION) DATAAREA PROCESS PO POORDERHDR RequiredRequiredRequiredRequiredRequired DATETIME (DOCUMENT) OPERAMT VALUE NUMOFDEC SIGN OptionalOptionalOptionalOptionalOptional CURRENCY OptionalRequiredDescriptionThe fields included in this area provide informationabout the XML document:Shows the Business Service Request name per OAGI:Value is “PROCESS”.Value is “PO”.Value is “007”Provides information on the system that sends thedocument:Sender system identifier.Sender application name. Value is “PURCHASING”.Event or Action. Value is POISSUE.Unique reference ID for this document.Confirmation when document is received. Value is 0,meaning none is required.Language in which the text fields are transmitted.Character set used in this XML document.System ID of sender. Value is APPS.Creation date and time of the XML document.The fields included in this area provide informationabout the data included in the XML document.This data type provides header-level purchase order(PO) information. One PO header data type is requiredper document.Timestamp for PO creation.Total amount of the PO.Monetary amount of the PO.Number of decimals (applied to Value field).Indicator ( or -) of whether the amount is positive ornegative.Three-character International Standards Organization5

OAGIS PROCESS PO 007Required? UOMVALUE Optional UOMNUMDEC UOM POID POTYPE OptionalOptionalRequiredRequired ACKREQUEST CONTRACTS OptionalOptional DESCRIPTION NOTES1-NOTES9 PORELEASE USERAREA OptionalOptionalOptionalOptional DATETIME (ACTSTART) DATETIME (ACTEND) FOB DESCRIPTN TERMID FTTERM DESCRIPTN TERMID EXCHRATE DATETIME (EXCHRATEDATE) DATETIME (APPREQ) CONFIRM DFFPOHEADER onal ATTRIBUTE1 ATTRIBUTE2 PCARDHDR MEMBERNAME PCARDNUM DATETIME PCARD BRAND PARTNER – tionalOptionalOptional NAME ONETIME PARTNID PARTNRTYPE CURRENCY PARTNRIDX TAXID USERAREA DFFVENDOR ATTRIBUTE1 ATTRIBUTE2 ISO) currency code.Numeric value indicator of the value of the factor whenamount is expressed in terms of multiples of the unit ofmeasure (UOM).Number of decimals in the UOMVALUE field.Unit of measure (units of the quantitative amount).Unique ID for the purchase order.Indicator of various types of POs. STANDARD orBLANKET is used here.Acknowledgement required (Y/N).Supplier’s contract document number, to be used only ifthis is a release from the blanket order.Description for the PO header.Notes to the supplier.Indicates new release for blanket.The following fields are provided by Oracle in thisUSERAREA:Start active date for the Blanket.End active date for the Blanket.FOB shipping terms.FOB description.FOB terms.Freight payment terms:Freight description.Freight terms.Currency exchange rate.Date for the exchange rate.Acceptance due by date. Qualifier 'APPREQ'.PO confirmed. Y/NPO header-level descriptive flexfield (DFF) attributes(16).PO header-level flexfield.PO header-level flexfield.This segment contains P-card detail.Member name on the P-card.P-card number.Expiration date of the P-card.Brand of the P-card.This data type provides information about the tradingpartner. Two occurrences of the partner data type arerequired — Supplier and SoldTo.Name of the supplier.Indicator if used only one time.Supplier ID.Type of partner. Value is Supplier.Preferred operating currency.Unique identifier of supplier.Tax identifier of the supplier.Oracle provided fields.PO supplier-level descriptive flexfield attributes (16).PO supplier-level flexfields.PO supplier-level flexfields.6

OAGIS PROCESS PO 007Required? CUSTOMERNUM ADDRESS - Supplier ADDR LINE1- ADDRLINE9 CITY COUNTRY DESCRIPTN FAX1 POSTALCODE REGION STATEPROVN TELEPHONE1-TELEPHONE9 USERAREA tionalOptionalOptionalOptionalRequiredOptional DFFVENDORSITE ATTRIBUTE1 ATTRIBUTE2-16 CONTACT – SupplierOptionalOptionalOptional NAME EMAIL FAX1 - FAX9 TELEPHONE1-TELEPHONE9 PARTNER – SoldTo NAME1 ONETIME quired PARTNRID PARTNRTYPE CURRENCY PARTNRIDX ADDRESS – SoldToRequiredRequiredRequiredOptionalOptional ADDRLINE1 - ADDRLINE3 CITY COUNTRY POSTALCODE STATEPROVN TELEPHONE1-TELEPHONE9 CONTACT – onalOptional NAME1 EMAIL TELEPHONE1-TELEPHONE9 PARTNER – BillToRequiredRequiredOptionalOptional NAME1 ONETIME OptionalRequired PARTNRID Required PARTNRTYPE RequiredDescriptionBuyer’s ID in supplier’s system.Supplier site info.Lines of site address.City within the address.Country within the address.Supplier site name.Fax numbers of the supplier site.Postal code within the address.Region within the address.State within the address.Telephone numbers for this address.PO supplier site-level descriptive flexfield attributes(16).PO supplier site-level flexfields.PO supplier site-level flexfields.PO supplier site-level flexfields.This data type provides contact information for thissupplier.Contact name for the supplier.Email address for the supplier contact.Fax number for the supplier.Telephone number for the supplier.Buyer information.Name of the buyer company.Indicator of whether this partner is established for thistransaction only.Unique identifier for the partner in Oracle Applications.Identifier for the type of partner. Value is SoldTo.Preferred operating currency of the partner.Unique identifier of the partner.The following rows list fields for the address data typerelated to the partnerLines of the address.City within the address.Country within the addressPostal code within the address.State within the address.Telephone numbers for this address.The following rows list fields for the contact data typerelated to the partner SoldTo.Full name of the buyer.E-mail address for the contact.Telephone number of the contact.Bill-to location in Oracle Applications. All theorganization information is obtained from the SoldToorganization itself.Name of the buyer company.Indicator of whether this partner is established for thistransaction only.Unique identifier for the Bill To Location ID in OracleApplications.Identifier for the type of partner. Value is BillTo.7

OAGIS PROCESS PO 007Required? CURRENCY PARTNRIDX ADDRESS - BillToRequiredOptionalOptional ADDRLINE1 - ADDRLINE3 CITY COUNTRY POSTALCODE STATEPROVN TELEPHONE1-ELEPHONE9 PARTNER - Carrier NAME1 ONETIME tionalOptionalRequired PARTNRID Required PARTNRTYPE POTERM RequiredRequired DESCRIPTN TERMID POORDERLIN RequiredRequiredRequired QUANTITY VALUE NUMOFDEC RequiredRequiredRequired SIGN Required UOM OPERAMT (UNIT) RequiredRequired VALUE NUMOFDEC SIGN OptionalOptionalOptional CURRENCY UOMVALUE OptionalOptional UOMNUMDEC UOM OptionalOptional POLINENUM HAZRDMATL ITEMRV NOTES1-NOTES9 DESCRIPTN ITEM OptionalRequiredOptionalOptionalOptionalOptional ITEMX RequiredDescriptionPreferred operating currency of the partner.Unique identifier of the partner.The following rows list fields for the address data typerelated to the partner BillTo.Lines of the address.City within the address.Country within the address.Postal code within the addressState within the addressTelephone numbers for this address.Carrier information is passed in this segment.Name of the carrier.Indicator of whether this partner is established for thistransaction only.Not used by Oracle Applications, but required byOAGI. It is assigned a fixed value of 0.Identifier for the type of partner. Value is Carrier.The POTERM data type represents payment due datesand discounts:Description of payment terms.Identifier for payment terms.This data type provides details of a PO line. At leastone PO line data type is required. This data type willoccur one or more times and contains the followingfields:Quantity of the item ordered, using the following fields:Numeric value of the quantity.One-character numeric value that indicates the numberof decimals in the value field.Indicator ( or -) of whether the quantity is positive ornegative.Unit of measure that indicates the units of the quantity.Unit price of the item. Following are the fields includedin this segment:Monetary unit amount of the PO line.Indicator of the number of decimals in the value field.Indicator ( or -) of whether the amount is positive ornegative.Three-character ISO currency code.Numeric indicator of the value of the factor whenamount is expressed in terms of multiples of the UOM.Number of decimals in the UOMVALUE field.Unit of measure indicator (units of the quantitativeamount).Line number of the PO.Hazardous material class description.Item revision number.Note to supplier.Description of the item.Identifier of the product. All segments are concatenatedto display the item.Supplier's item number.8

OAGIS PROCESS PO 007Required? USERAREA Optional REQUESTOR CATEGORYID CONTRACTPONUM CONTRACTPOLINENUM VENDORQUOTENUM LISTPRICE MARKETPRICE PRICENOTTOEXCEED NEGPRICE tionalOptionalOptional TAXABLE Optional TXNREASONCODE Optional TYPE1099 LINEORDERTYPE HAZRDUNNUM HAZARDUNDESC DFFLINE ATTRIBUTE 1 ATTRIBUTE2-16 DFFITEM ATTRIBUTE 1 ATTRIBUTE2-16 KFFITEM ATTRIBUTE1-20 POLINESCHD onal DATETIME (NEEDDELV) QUANTITY VALUE NUMOFDEC OptionalRequiredRequiredRequired SIGN Required UOM PSCLINENUM USERAREA RequiredRequiredOptional DATETIME (PROMSHIP) DATETIME (APPROVAL) PRICEOVRRD TAXABLE TAXCODE PARTNER - onal NAME ONETIME OptionalOptionalDescriptionThe following fields are provided by OracleApplications within this USERAREA:Requestor of this line.Item category unique identifier.Contract PO number for this line.Contract PO line number for this order.Supplier’s quote number for this line.List price of the item.Market price of the item.Unit price not to exceed this amount.Negotiable price indicator, using Y (for Yes) or N (forNo). Only applicable to blankets. Known as PriceOverride in Oracle Purchasing.Indicator of whether this item is taxable, using Y (forYes) or N (for No).Transaction reason code, used to group requisition linesfor autocreating POs.Type 1099, Y/N.Line order type, such as Goods or Services.UN hazard number.UN hazard description.Descriptive flexfields at the line level.Descriptive flexfields at the line level.Descriptive flexfields at the item level.Descriptive flexfields at the item level.Key flexfields at the item level.Data type for requested ship date information for thisPO line, using the following fields:Need-by delivery date.Quantity of the item ordered, using the following fields:Numeric value of the quantity.One-character numeric indicator of the number ofdecimals in the value field.Indicator ( or -) of whether the quantity is positive ornegative.Unit of measure indicator of the units of the quantity.Line number on the delivery schedule of the PO.The following fields are provided by Oracle in theUSERAREA:Promise date.Last acceptance date.For future use.Taxable indicator, Y/N.Tax code if taxable is Y.The following fields related to the ShipTo partner datatype are provided by Oracle Applications within thisUSERAREA:Name of the ShipTo partner.Indicator of whether this partner is established for this9

OAGIS PROCESS PO 007 PARTNRID PARTNRTYPE CURRENCY PARTNRIDX ADDRESS - ShipTo ADDRLINE1 - ADDRLINE3 CITY COUNTRY POSTALCODE STATEPROVN TELEPHONE1-TELEPHONE9 DISTPROJECT REQUESTOR DISTNUM PROJECTNUM PROJECTTYPE TASKNUM QUANTITY CONVRATE DATETIME(EXRATEDATE) DESTTYPE DIFFDISTRIBUTION ATTRIBUITE1 ATTRIBUTE2-16 lDescriptiontransaction only. This is always.Unique identifier for the partner in Oracle Applications.Identifier for the type of partner. Value is ShipTo.Preferred operating currency of the partner.Unique identifier of the partner.The ADDRESS element contains the following fields:Lines of address for the partner ShipTo.City within the address.Country within the address.Postal code within the address.State or providence within the address.Telephone numbers for this address.Used only if Projects installed.Requester.Distribution number.Project number.Project type.Project task number.Quantity ordered for this distribution line.Currency conversion rate.Currency conversion date.Destination type code, such as Inventory or Expense.Distribution descriptive flexfields (16).Distribution descriptive flexfields (16).cXML OrderRequestField DescriptionsThe following section provides information on the some of the common data types (fields) in the cXMLOrderRequest document created by the Oracle SN. For complete information on the cXML Order Request, refer tothe cXML specifications at http://www.cxml.org. OrderRequestHeader RequiredIncludes the following attributes: The orderID attribute represents the purchase order number. TheorderDate attribute is the date the purchase order was created. The orderType attribute is set to,“regular” or “release” (if order is against a master agreement). The type attribute is set to “new”, or“update” (if order is a change order). Total OptionalRepresents the total amount of the purchase order, not including tax and shipping. ShipTo RequiredRepresents the address of the ShipTo entity. ShipTo address information is always populated inboth the header and lines of the OrderRequest. The header ShipTo address information isderived from line 1 ShipTo address. BillTo RequiredRepresents the address of the Bill To entity. Shipping Optional10

Describes the carrier used to ship the line items. Cost of shipping information is not passed fromthe OAG order. Payment OptionalRepresents the payment method. Pcard OptionalThe number attribute represents the procurement card number and the expiration represents theexpiration date of the card used to pay for the items being requested. Contact OptionalRepresents contact information for the buyer – includes name, address, email, and phoneinformation. Contact role information is not passed from the OAG order. Extrinsic name “ACKREQD” OptionalAn extrinsic element used to indicate whether an acceptance from the supplier is required or not.Value is Y/N. Extrinsic name ”ACKBYDATE” OptionalAn extrinsic element used to indicate the date the acceptance from the supplier must be returned. Extrinsic name ”SUPPNOTE” OptionalAn extrinsic element used to capture PO header notes to a supplier.The following header level extrinsic fields can be used to exchange additional header information: Extrinsic name "ATTRIBUTE1"/ Optional Extrinsic name "ATTRIBUTE2"/ Optional Extrinsic name "ATTRIBUTE3"/ Optional Extrinsic name "ATTRIBUTE4"/ Optional Extrinsic name "ATTRIBUTE5"/ Optional Extrinsic name "ATTRIBUTE6"/ Optional Comments OptionalUsed to capture the description of the PO, if provided by the buyer. ItemOut RequiredIncludes the following attributes: The quantity attribute represents the number of items being requested.The aggrementItemNumber attribute represents the blanket purchase item number if the purchase orderis a release. The requestedDeliveryDate attribute is used to capture the need by delivery date. ItemID SupplierPartID OptionalThe supplier’s part number for the item. ItemDetail Required Unit Price RequiredUsed to capture the price per unit of the item. Description RequiredThe description of the item. UnitofMeasure RequiredThe unit of measure used for the item. Extrinsic name ”LINENUM” OptionalAn extrinsic element used to capture the purchase order line number. Extrinsic name ”SHIPMENTNUM” OptionalAn extrinsic element used to capture the purchase order shipment line number. Extrinsic name ”BUYERPARTNUM” OptionalAn extrinsic element used to capture the buyer’s internal part number.The following line level extrinsic attribute fields can be used to exchange additional line information: Extrinsic name "ATTRIBUTE1"/ Optional Extrinsic name "ATTRIBUTE2"/ Optional Extrinsic name "ATTRIBUTE3"/ Optional Extrinsic name "ATTRIBUTE4"/ Optional Extrinsic name "ATTRIBUTE5"/ Optional Extrinsic name "ATTRIBUTE6"/ Optional SupplierList Required11

Captures all supplier related information in the following fields: Supplier Name RequiredThe name of the supplier company. SupplierID RequiredThe identifier assigned by buyer’s Oracle Procurement application for supplier. SupplierLocation RequiredUsed to capture supplier address, phone, and fax information. Contact OptionalProvides contact information for the supplier – includes name, email, and phone information. Tax TaxDetail OptionalThe TaxDetail element uses the purpose attribute to indicate whether the line item is subject totax. The category attribute indicates the tax code being applied to the line item. Comments OptionalUsed to capture line item notes for the supplier.Mapping OverviewThe following table shows the data types (fields) mapped between the PROCESS PO 007 (OAG PO) and cXMLOrderRequest. This table is not the complete mapping but is intended to highlight some of the key transformationsdone by Oracle SN. The cXML OrderRequest header is generated by Oracle SN trading partner parameters, not bedata elements from the OAG PO. Please refer to the OAG Process PO and cXML OrderRequest sample payloads inthe Appendices for transformation examples.It is important to note the structural difference between the two order formats. The OAG PO supports a three levelorder, consisting of a header, lines, and shipments; whereas the cXML PO supports a two level order, which includes aheader and lines. When mapping from the OAG order the shipment lines become PO lines in the cXML order. Linelevel extrinsics were added to the cXML PO to provide PO line number and shipment schedule line number referencesback to the OAG order.OAG TagcXML TagPROCESS PO 007cXML cXML version '1.2.007' cXML payloadID cXML timestamp cXML/Header/From/ Credentialdomain / Credentialdomain CommentsOur current version.Comes fromCONTROL NUMBERvariable passsed by Hubserver.Comes from TIMESTAMPvariable passed by Hubserver.Comes fromSENDER ID TYPE variablepassed by Hub server.Comes from SENDER IDvariable passed by Hubserver.Comes fromRECEIVER ID TYPEvariable passed by Hubserver.12

er/ Credentialdomain "OracleSN" /IdentitycXML/Header/Sender/ Credentialdomain "OracleSN" /SharedSecretComes from RECEIVER IDvariable passed byHubserverComes fromRECEIVER USERNAMEvariable passed byHubserverComes fromRECEIVER PASSWORDvariable passed byHubservercXML/Header/Sender/UserAgent 'Oracle Supplier Network'DATAAREA/PROCESS PO/POORDERHDR/ cXML / Request / OrderRequest / OrderRequestHeader POORDERHDR/POIDPOORDERHDR/DATETIME OrderRequestHeader orderID POORDERHDR/POTYPE OrderRequestHeader orderDate OrderRequestHeader orderType If POTYPE is 'RELEASE'then orderType is set to'release'. If POTYPE is'STANDARD' thenorderType is set to 'regular'.In all other cases the valueof orderType is set to samevalue as POTYPE OrderRequestHeader type 'new' DATAAREA/PROCESS ERAMT/NUMOFDECDATAAREA/PROCESS /PARTNRIDXPOLINESCHD/USERAREA/PARTNER/NAME OrderRequestHeaderagreementID This two values are filledfor POTYPE 'RELEASE'only.OrderRequestHeader/Total/ Moneycurrency hipToGenerate the ShipTosegment from the firstschedule line in the firstorder lineShipTo/ AddressisoCountryCode ShipTo/ Address addressID ShipTo/Address/ Namexml:lang "en" 13

/TELEPHONEDATAAREA/PROCESS PO/POORDERHDR/PARTNER[PARTNRTYPE 'BillTo']/PARTNER[PARTNRTYPE 'BillTo']/ADDRESS/COUNTRYPARTNER[PARTNRTYPE 'BillTo']/PARTNRIDXPARTNER[PARTNRTYPE 'BillTo']/ADDRESS/DESCRIPTNPARTNER[PARTNRTYPE R is null then the value ofDeliverTo gets ddress/PostalAddress/StreetFor each ADDRLINE, Street tag gets ress/PostalCodeShipTo/Address/PostalAddress/ Country isoCountryCode hone/TelephoneNumber/ CountryCode isoCountryCode Value is converted into acountry umber/NumberOrderRequestHeader/BillToBillTo/ Address isoCountryCode BillTo/ Address addressID reetFor each ADDRLINE, the Street tag will repeat.14

DRLINEPARTNER[PARTNRTYPE 'BillTo']/ADDRESS/CITYPARTNER[PARTNRTYPE '

The Oracle SN supports the Open Applications Group (OAG) and Commerce XML (cXML) standards. Messages sent to the Oracle SN must comply with the appropriate standard. Oracle SN can transform XML messages as required by the receiving trading partner. The Ora