PIPs Using the RosettaNet Document Protocol

Using Document Protocols 8-33 area of the screen shows the following tabs: Parameters, XPath, Correlation, and Apps. The Parameters tab is selected and shows the following fields: Document Routing ID and DTDXSD Namespace Conversion a drop-down list. At the top right of the screen is the Save button. Table 8–19 describes the document definition parameters for a RosettaNet document. Table 8–19 Document Definition Parameters for a RosettaNet Document Parameter Description Parameters Tab - Document Routing ID Sets the consumer name to the back-end application DTDXSD Namespace Conversion A converted document can optionally replace the original RosettaNet document. Select Both to replace the RosettaNet document with the converted document for both the inbound and outbound messages. Select Inbound to replace the RosettaNet document with the converted document for the inbound message. Select Outbound to replace the RosettaNet document with the converted document for the outbound message. Select None for no replacement. None passes the DTD instance as-is. Inbound converts the instance DTD to XSD. Outbound converts the instance XSD to DTD. Both convert both inbound and outbound formats. XPath Tab See Section 8.1.1, How to Configure the XPath Expression for a Custom XML Document, XPath Name1 The XML XPath name for retrieving the value from the payload XPath Expression1 The XML XPath expression for retrieving the value from the payload XPath Name2 The XML XPath name for retrieving the value from the payload XPath Expression2 The XML XPath expression for retrieving the value from the payload XPath Name3 The XML XPath name for retrieving the value from the payload XPath Expression3 The XML XPath expression for retrieving the value from the payload Correlation Tab Correlation is required for a two-action PIP, for example, a 3A4. Correlation From XPath Name The name of the correlation property for initiating the correlation. For example, Pip3A4PurchaseOrderRequest in [local-name=Pip3A4PurchaseOrderRequest][local-name=thisDocumentIdent ifier]text. Correlation From XPath Expression The XML XPath for retrieving the value from the payload to initiate the correlation. Correlation To XPath Name The name of the correlation property for the correlation. Correlation-to represents the other message that takes part in the correlation. For example, Pip3A4PurchaseOrderConfirmation in[local-name=Pip3A4PurchaseOrderConfirmation][local-name=requesting DocumentIdentifier]text. Correlation To XPath Expression The XML XPath for retrieving the value from the payload for the correlation. Apps Tab - Document The name of the internal application document. Action A sub-classification within the document. XSLTFile The name of the XSLT file. 8-34 Oracle Fusion Middleware Users Guide for Oracle B2B

8.7.2 RosettaNet Validation

RosettaNet validation compares the elements in RosettaNet XML-format business documents to the requirements specified in the RosettaNet Message Guideline specification to determine their validity. This specification defines requirements for details such as element datatypes, element lengths, element value lists, and element cardinality. PIPs that require RosettaNet dictionary validation are also validated when a dictionary is present. The minimum validation-level requirements on the sections of a RosettaNet XML-format business document are as follows. These requirements cover the preamble, delivery header, service header, and service content sections of a document. Documents not following one or more of these requirements are identified as invalid.

1. The XML-format business document requires compliance with its DTD.

2. Elements with datatypes, lengths, or both that are specified in the RosettaNet

Message Guideline specification require validation against this specification.

3. An elements list of values specified in the entity instance list in the corresponding

RosettaNet Message Guideline specification requires validation against this specification.

4. If the Message Guideline specification defines the cardinality specification of an

element differently from the corresponding DTD specification, the Message Guideline specification takes precedence.

5. If a PIP requires dictionary validation, and a dictionary is included, the service

content requires validation against the dictionary as a part of action performance.

6. Cross-tag validation is based on message guidelines.

8.8 Using the UCCNet Document Protocol

Oracle B2B implements UCCNet, which enables trading partners—typically retailers and suppliers in the retail and consumer goods industries—to exchange documents with UCCNet. Table 8–20 lists the UCCNet document types supported in Oracle B2B. Table 8–20 UCCNet Document Types Standard registerCommand confirmCommand linkCommand checkComplianceCommand documentCommand documentIdentificationCommand notificationStateCommand queryCommand registerLinkCommand publicationCommand publishCommand catalogueItemMaintenanceCommand priceCommand Using Document Protocols 8-35 For information about the organization that created and maintains the UCCNet standards, go to http:www.1sync.org Document Version Parameters No parameters need to be set when you create the document version for a UCCNet document. Document Type Parameters No parameters need to be set when you create the document type for a UCCNet document. Document Definition Parameters When you create a UCCNet document definition, you can set various parameters. Figure 8–20 shows document definition parameters for a UCCNet document. Figure 8–20 Document Definition Parameters for a UCCNet Document The image shows the UCCNet Document Definition screen. The first area of the screen shows the following fields: Document Definition Name, Description, Definition, and validateCommand registerOwnershipCommand subscriptionCommand notifyCommand response Table 8–20 Cont. UCCNet Document Types Standard 8-36 Oracle Fusion Middleware Users Guide for Oracle B2B Root XSD Name. The first area also shows the Reset Parameter button. The second area of the screen shows the following tabs: XML, Routing, XPath, Correlation, and Apps. The XML tab is selected and shows the following fields: Identification Expression XPath and Identification Value. At the top right of the screen is the Save button. Table 8–21 describes the document definition parameters for a UCCNet document.

8.8.1 Creating a 1Sync Document

The 1Sync document protocol helps in the data synchronization between seller and buyer, which enables the transfer of product and location information with the continuous synchronization of the data over time. Table 8–21 Document Definition Parameters for a UCCnet Document Parameter Description XML Tab - Identification Expression XPath Locates a node in the XML payload Identification Value Provides the value to match in the node identified by the Identification Expression. If the values match, then the document is successfully identified. If the value is left blank, then Oracle B2B checks for the existence of the node and the document is successfully identified. Routing Tab - Document Routing ID Sets the consumer name to the back-end application XPath Tab See Section 8.1.1, How to Configure the XPath Expression for a Custom XML Document, XPath Name1 The XML XPath name for retrieving the value from the payload XPath Expression1 The XML XPath expression for retrieving the value from the payload XPath Name2 The XML XPath name for retrieving the value from the payload XPath Expression2 The XML XPath expression for retrieving the value from the payload XPath Name3 The XML XPath name for retrieving the value from the payload XPath Expression3 The XML XPath expression for retrieving the value from the payload Correlation Tab - Correlation From XPath Name The name of the correlation property for initiating the correlation. Correlation From XPath Expression The XML XPath for retrieving the value from the payload to initiate the correlation. Correlation To XPath Name The name of the correlation property for the correlation. Correlation To XPath Expression The XML XPath for retrieving the value from the payload for the correlation. Apps Tab - Document The name of the internal application document. Action A sub-classification within the document. XSLTFile The name of the XSLT file. Using Document Protocols 8-37 Use the Custom document protocol or the UCCNet document protocol to create a 1Sync XML document. Figure 8–21 shows a document definition for a 1Sync document, using the Custom document protocol. Figure 8–21 1Sync Document Definition The image is described in the surrounding text. You can correlate 1Sync request and response messages as follows: ■ Use the document routing ID on the Routing tab. The routing ID 1Sync_64_catalogueRequest is shown Figure 8–22 . Note: The GS-1 organization has changed the standard name from UCCNet to 1Sync. Use either the seeded UCCNet document protocol or create a new Custom document protocol, 1Sync, as illustrated in the figure. The functionality is the same.