The Document Hierarchy Introduction to Document Protocols

4-4 Oracle Fusion Middleware Users Guide for Oracle B2B

4.1.2 Document Protocols with Acknowledgments

For any message flow that involves an acknowledgment, Oracle B2B sends an acknowledgment only once. Resubmission does not generate another acknowledgment if the message has already been acknowledged. If further information about the message state is needed, then the trading partner must be notified by some other means for example, e-mail.

4.2 Creating Document Definitions

After using Oracle B2B Document Editor to create the transaction set files, use the Oracle B2B interface to create the document definition and import the transaction set files. To create a document definition: 1. Click the Administration tab. 2. Click the Document tab. 3. Select one of the document protocols, as shown in Figure 4–5 . Figure 4–5 Selecting a Document Protocol The image shows the following Oracle B2B tabs: Document, Deploy, and Manage Deployments. The Document tab is selected and shows the following document protocols: Custom, EDI_EDIFACT, EDI_X12, HL7, OAG, PositionalFlatFile, RosettaNet, UCCNet, and UserDefined. Note: The document version, document type, and document definition are not editable after they are created. You must delete the specific document element version, type, or definition and create a new one. Updating the document elements after creation can lead to metadata inconsistency, metadata validation issues, and run-time errors. Creating Document Definitions 4-5

4. Click New Version.

Figure 4–6 shows the New Version button. Note: To create a new Custom document with a name that you provide, click the Document Protocols folder and click Add. Then enter a protocol name, for example, MyXML_Document. Do not use an existing document protocol name. The image shows NewCustomDocumentProtocol in the Document Protocols list and provides a field for you to enter a name, MyXML_Document in this example, and optional description. 4-6 Oracle Fusion Middleware Users Guide for Oracle B2B Figure 4–6 Creating a Document Version The image shows a section of the Oracle B2B screen displaying the Document, Deploy, Manage Deployments, Types, ImportExport, and Schedule Batch tabs. The Document tab is selected. The left pane is labeled Documents and shows an expanded hierarchy of Document Protocols with ED_EDIFACT selected. The right pane is labeled Document Protocol Name and shows the Protocol Name and Description fields for the EDI_EDIFACT document. The right pane also shows the Save and New Version buttons. 5. Enter a version name, provide document version parameters as applicable, and click Save. The version is used for document identification and can be case sensitive and use a fixed syntax, depending on the protocol. Figure 4–7 shows the document protocol version page for an EDI EDIFACT D98A document. Figure 4–7 Entering Document Protocol Parameter Information The image shows a section of the Oracle B2B screen displaying the Document tab. The left pane is labeled Documents and shows an expanded hierarchy of Document Protocols with ED_EDIFACT NewVersion selected. The right pane is labeled Document Protocol Version and shows the Version Name and Description fields for