Using the Positional Flat File Document Protocol

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 Using Document Protocols 8-31 Document Version Parameters No parameters need to be set when you create the document version for a RosettaNet document. Document Type Parameters When you create a RosettaNet document type, you can set various parameters. Figure 8–18 shows document type parameters for a RosettaNet document. Figure 8–18 Document Type Parameters for a RosettaNet Document The image shows the RosettaNet Document Type screen. The first area of the screen shows the following fields: Document Type Name and Description. The first area also shows the Reset Parameter button. The second area of the screen shows the Service Header tab and displays the following fields: From Role, To Role, From Service, To Service, Business Transaction Name, Business Action, Time to perform for Collaboration, Collaboration Name, and Collaboration Code. At the top right of the screen are the Save and New Definition buttons. Table 8–18 describes document type parameters for a RosettaNet document. 3A4 Specific PIP type, which supports: ■ Submittal of a purchase order by a buyer ■ Submittal of an acceptance purchase order by a seller ■ Ability of a buyer to cancel or change a purchase order based on the acknowledgment response Table 8–17 Cont. PIP 3A4 Breakdown Element Description 8-32 Oracle Fusion Middleware Users Guide for Oracle B2B Document Definition Parameters When you create a RosettaNet document definition, you can set various parameters. Figure 8–19 shows the document definition parameters for a RosettaNet document. Figure 8–19 Document Definition Parameters for a RosettaNet Document The image shows the RosettaNet 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 Table 8–18 Document Type Parameters for a RosettaNet Document Parameter Description Service Header Tab - From Role The trading partner that sends the message in Partner Role Description of the PIP. To Role The trading partner that receives the message the role the trading partner receiving the message plays in the PIP. From Service The service that sends the message. To Service The service to which the message is sent. Business Transaction Name The name of the business transaction is required. Business Action The name of the business action is required. The value must be consistent with the Global Business Action Code. Time to Perform for Collaboration The time to perform the business action is required. Collaboration Name The RosettaNet collaboration name signifies the business transaction between trading partners the roles as buyer and seller depending on a common transaction. Required. Collaboration Code The textual form of the abbreviated collaboration name. Required.