Using the OAG Document Protocol

8-28 Oracle Fusion Middleware Users Guide for Oracle B2B Document Version Parameters No parameters need to be set when you create the document version for a positional flat file. Document Type Parameters No parameters need to be set when you create the document type for a positional flat file. Document Definition Parameters When you create a document definition for a positional flat file, you can set various parameters. Figure 8–16 shows document definition parameters for a positional flat file. Figure 8–16 Document Definition Parameters for a Positional Flat File including SAP iDocs The image shows the PositionalFlatFile Document Definition screen. The first area of the screen shows the following fields: Document Definition Name, Description, Definition, and Root XSD Name. The first area also shows the Reset Parameter button. The second area of the screen shows the following tabs: Transaction, Identification, Routing, XPath, Correlation, and Apps. The Transaction tab is selected and shows the Transaction Set ecs File field. At the top right of the screen is the Save button. Table 8–16 describes the document definition parameters for a positional flat file. Table 8–16 Document Definition Parameters for a Positional Flat File Parameter Description Transaction Tab - Transaction Set ecs File Use the Browse button to find the ecs file. Identification Tab - Using Document Protocols 8-29

8.7 Using the RosettaNet Document Protocol

Oracle B2B implements the nonproprietary, XML-based RosettaNet standards to exchange documents over the Internet. RosettaNet standards prescribe when information should be exchanged, acknowledged, or confirmed, and how messages in an exchange should be packaged and physically exchanged between trading partners. In addition to using the RosettaNet document guideline files in Oracle B2B Document Editor, you can also download standard DTD files from the RosettaNet Web site. A RosettaNet DTD, when used with Oracle B2B in a SOA composite application, must be converted to an XSD. An AQ Adapter added to the composite application can convert the inbound DTD to an XSD and manipulate the data as needed. Likewise, the AQ Adapter can convert the outbound XSD to a DTD for Oracle B2B to send the message out. Identification Value Not applicable Identification Start Position Used in combination with the end position to retrieve a value from the payload between the start and end positions Identification End Position Used in combination with the start position to retrieve a value from the payload between the start and end positions 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, for more information. 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. Table 8–16 Cont. Document Definition Parameters for a Positional Flat File Parameter Description 8-30 Oracle Fusion Middleware Users Guide for Oracle B2B RosettaNet standards are specified by using of the RosettaNet Partner Interface Process PIP, RosettaNet Dictionaries, and RNIF. Oracle B2B supports all PIPs. The RosettaNet Technical Dictionary is not supported in Oracle B2B. For information about the RosettaNet consortium and its history, and for a complete list of PIP clusters and segments, go to http:www.rosettanet.org

8.7.1 PIPs

A PIP is an XML-based dialog that defines the business processes between trading partners. It defines the structure, sequence of steps, roles buyer and seller activities, data elements, values, and value types for each business document message exchanged between trading partners. Using PIP 3A4 as an example, you can see how a PIP defines a dialog between trading partners, as shown in Figure 8–17 . Figure 8–17 PIP 3A4 Message Exchange Between Buyer and Seller The image shows a PIP3A4 message being exchanged. First, the buyer sends the purchase order request to the seller. Then seller sends a receipt acknowledgment. Next, the seller sends a purchase order confirmation. Finally, the buyer sends a receipt acknowledgment. A PIP sequence combines a cluster, segment, and type. The PIP sequence 3A4, for example, encodes the information shown in Table 8–17 . Table 8–17 PIP 3A4 Breakdown Element Description 3 Order manage cluster, with which trading partners can: ■ Order catalog products ■ Create custom orders ■ Manage product distribution and delivery ■ Support product returns and financial transactions 3A Quote and order entry segment Purchase Order Request Receipt Acknowledgment Purchase Order Confirmation Receipt Acknowledgment Buyer Seller