Use the RosettaNet Document Standard

You can create customized document definitions using the RosettaNet document standard or protocol in B2B for Oracle Integration.

Note:

You must first create a RosettaNet schema before you can create a document definition that uses the RosettaNet standard. See Create a New B2B Schema.

Create a new B2B document definition using the RosettaNet document standard

1. Create a document.

   Note:

   The RosettaNet document standard is supported in both B2B trading partner mode and B2B standalone mode.
   1. To create a document in a project in B2B trading partner mode.
      1. In the navigation pane, click Projects.
      2. Click the project in which to create the document.
      3. Click B2B .
      4. In the Documents section, click Add.
   2. To create a document in B2B standalone mode.
      1. In the navigation pane, click B2B, then Documents.
      2. On the Documents page, click Create.
2. In the Create document pane, enter the following details.

   Element	Description
   Name	Enter a document name.
   Identifier	This field is automatically populated with the document name. You can manually change this value.
   Description	Enter an optional description of the customization details for this document.
   Use a shared document	Select to use a shared document. Selecting this option enables a Shared document list to be displayed for you to select the shared document to use. Shared documents only available in a different project are displayed. Documents created in a standalone environment (that is, outside a project) are not available for selection. After creation, an Override label appears below the document name in the Documents section to indicate that it is shared. To understand how shared documents work, see What's Supported in Projects for B2B. Note: This option is only available within projects in B2B trading partner mode. It is not supported in B2B standalone mode.
   Available to other projects	Select to make this document available for use in other projects. After creation, a Shared label appears below the document name in the Documents section to indicate that it is available for use in other projects. Note: Before you make the document available to other projects, ensure that the document uses a shared schema. For details on how to create a shared schema, see Create a New B2B Schema. Note: This option is only available within projects in B2B trading partner mode. It is not supported in B2B standalone mode.
   Document standard	Select RosettaNet from the drop-down list.
   Document version	Select an existing document version.
   Document type	Select an existing document type.
   Document schema	Select an existing schema. If a schema does not exist, you cannot create a document definition. See Create a New B2B Schema.

3. Click Create.

   The document details page for your new B2B document using the RosettaNet standard is displayed.

   
   
   

4. If you want to use a different document schema, select an existing schema from the Document schema drop-down list or click Edit to upload a new schema file.

   You can also define document properties for the schema.

5. In the Document property section, define document properties for the schema.
   1. Expand Business identifiers, and add at least one identifier (primary). You can also add a second and third identifier to associate with this document. The business identifier names and expressions enable filtering by the identifiers on the Instances page when this document is sent or received.
   2. In the Expression field, click to select a business identifier expression path.
   3. Expand Service header to view parameters used for validating inbound messages and creating RosettaNet outbound messages.

      For this example, the service header parameters provided are for a document configured to use PIP3A4 (Purchase Order Request). The Time to perform for collaboration (minutes) field shows the time window in which the buyer is expecting the purchase order acceptance message from the seller. If the acceptance message does not arrive within this time window, it times out.

      
      
      

   4. Expand Correlation and Parameters to show additional parameters. You must manually populate these fields. In particular, note the three fields for XPath expressions.

      
      
      

      The Correlation from XPath expression field shows the following expression:

      /*[local-name()='Pip3A4PurchaseOrderRequest']/*[local-name()='thisDocumentIdentifier']/*[local-name()='ProprietaryDocumentIdentifier']/text()

      The value for ProprietaryDocumentIdentifier in the request purchase order from the buyer integration must match with the value in the response purchase order of the seller integration. Whichever fields you configure for correlations to occur, you must supply the value correctly in the request/response payloads to get the relevant messages successfully correlated.

      For example:

      • If the seller's ProprietaryDocumentIdentifier parameter in the request purchase order consists of this value:

        <thisDocumentIdentifier>
           <ProprietaryDocumentIdentifier>420002933046</ProprietaryDocumentIdentifier>
        </thisDocumentIdentifier>

      • Then the seller's the ProprietaryDocumentIdentifier parameter in the response purchase order must consist of the same value:

        <thisDocumentIdentifier>
           <ProprietaryDocumentIdentifier>420002933046</ProprietaryDocumentIdentifier>
        </thisDocumentIdentifier>

      If your buyer and seller integrations are both REST Adapter-triggered, you can make these edits in the Body section of the Configure and run page. This page appears when you select Run from the Actions menu for your integrations. This configuration ensures that message delivery occurs in the correct sequence at runtime.

6. Click Save.