Creating a 1Sync Document

Using Document Protocols 8-39 The image shows the Correlation tab for a 1Sync document. Parameters include Correlation From XPath Name, Correlation From XPath Expression, Correlation To XPath Name, and Correlation To XPath Expression. The parameters are explained in the surrounding text. See the following for more information: ■ Section 8.1, Using the Custom Document Protocol ■ Section 1.7, Oracle B2B Samples and Cookbooks. A 1Sync example is provided with the B2B samples.

8.9 Changing Document Details

Document details—document protocol versions and document type parameters—can be changed for a remote trading partner from the Partners Documents tab. Host administrators can change any remote trading partners document details here host administrators must change their own data on the Administration Document tab, and remote administrators can change document details for their own data, if the remote administrator has been granted access to those document types. See Section 1.4.2, Restricting Access to Document Types, for more information. Figure 8–24 shows the Version tab in the Document Details section, where parameters for the document protocol version can be changed. Figure 8–24 Changing Document Details 8-40 Oracle Fusion Middleware Users Guide for Oracle B2B The image shows the Documents tab from the Partners link. Two documents are displayed: 850def and 997def, both EDI X2 documents. GChips is the sender and receiver of the 850def and the receiver of the 997def. The Interchange tab of the Document Protocol Version tab is displayed to show where you can change document details. Delimiters, and parameters such as Interchange Control Version Number, Interchange Date , and Interchange Time are typically changed for different remote trading partners. Figure 8–25 shows the Document Type tab, where parameters for the document type can be changed. Figure 8–25 Changing Document Details The image shows the Documents tab from the Partners link. Two documents are displayed: 850def and 997def, both EDI X2 documents. GChips is the sender and receiver of the 850def and the receiver of the 997def. The Interchange tab of the Document Protocol Version tab is displayed to show where you can change document details. Use the Override Version Param and Override DocType Param parameters to indicate that override values are provided. Document type parameter values set for a remote trading partner take precedence over the default document type parameter values set for the document definition when the document was created on the Administration Document tab. Using Document Protocols 8-41 To override document details: 1. Click the Partners tab. 2. Click the Documents tab. 3. Select a remote trading partner. 4. Select a document definition. 5. Select the override types that apply: ■ Override Version Param ■ Override DocType Param 6. Provide values to override values on the Version tabs or the Document Type tabs, or both.

7. Click Save.

8.9.1 Changing Document Definitions After Deploying an Agreement

Changes to a document definition after an agreement is deployed are not reflected in the trading partners profile. Use the Document Details area on the Partners Documents tab to change document protocol version and document type parameters. Then redeploy the agreement.

8.9.2 Changing Document Definitions After Importing Metadata

If you import B2B metadata and then change the document from the Administration Document tab, then you must also make the same changes to the supported document definition for the host and remote trading partners from the Partners Documents tab. Use the Version, Document Type, and Definitions tabs under Document Details to make the changes.

8.10 Using Document Routing IDs

A document routing ID is useful in two circumstances: when enqueuing to an AQ queue and when using B2B documents in a SOA composite application. If you set a document routing ID for messages enqueued to an AQ queue inbound only, then the AQ consumer name is set to the document routing ID. Within a SOA composite application, if you use a document routing ID in your B2B binding component instead of the document definition, then all messages with the same document routing ID are routed to the same SOA composite. This is useful if you have many different document definitions, but you want them to be handled the same way. The WSDL uses the document routing ID instead of the document definitions. In a SOA composite application, the B2B Configuration Wizard provides an option to use the document routing ID instead of selecting a document definition, as shown in Figure 8–26 . 8-42 Oracle Fusion Middleware Users Guide for Oracle B2B Figure 8–26 Document Routing ID Option in Oracle JDeveloper The image shows the Document Definition dialog box of the B2B Configuration Wizard. The first area of the dialog box shows a field to select the document definition of the service. To the right of the field are the Search, Refresh, and B2B Configuration buttons. The second area of the dialog box shows the Use Routing ID check box and an expanded hierarchy of the Document Definitions. The final area of the dialog box shows the Help, Back, Next, Finish, and Cancel buttons. When using AQ, if you set the routing ID value instead of using the default b2buser, then do not set it to a numeric value. Use a combination of alphabetic and numeric values.