Introduction to Agreements Oracle Fusion Middleware Online Documentation Library

6-4 Oracle Fusion Middleware Users Guide for Oracle B2B ■ For the outbound agreement, select the document definition in which the host trading partner is the sender Acme -- Globalchips in Figure 6–4 ■ For the inbound agreement, select the document definition in which the host trading partner is the receiver Acme -- GlobalChips in Figure 6–4 Step 3: Provide the agreement ID and name Provide any agreement identifier and agreement name. These fields can have the same value if you need only one for tracking purposes. Step 4: Select validation, translation, and functional acknowledgment options Table 6–1 describes the validation, translation, and functional acknowledgments available when you create an agreement. Table 6–1 Agreement Options Option Description Validate Select to enable validation of the document against the configured ECS file. Translate Select to enable the translation of XML to native format and vice versa for EDI and HL7, for example. If Translate is not selected no translation, then B2B cannot correlate the business message with the functional acknowledgment, irrespective of the value of the B2B Handle FA property. See Section B.1, Properties To Set in Fusion Middleware Control, for information about the property. Functional Ack Select to enable the functional acknowledgment for success or error criterion. FA Handled by B2B If set to true, then B2B autogenerates the functional acknowledgment FA message for inbound EDI and HL7 messages. Inbound FA messages are consumed when this option is true. When this option is set to false, B2B does not autogenerate the FA document. The back-end application middleware must generate the FA and provide it to B2B as an outbound message. When option is set to false, inbound FA documents are passed back to the back-end application. If the document does not require an FA as indicated by the agreement-level setting, then this option is ignored. The default value for this property is true. See Section B.1, Properties To Set in Fusion Middleware Control, for more information. When Functional Ack Handled by B2B is set to false, then Notify Inbound Functional Acks must be set to false also for the inbound FA to be sent to the back-end application. If Notify Inbound Functional Acks is set to true while Functional Ack Handled by B2B is set to false, then the incoming 997 FA doc generates only a notification and the 997 document itself is not sent back to the back-end application. Document Retry Interval Enter the length of time in minutes between document retries. See Section 5.5.5, Configuring Delivery Retry Options for more information about configuring retry attempts. Document Retry Count Enter the number of times to retry the message. See Section 5.5.5, Configuring Delivery Retry Options for more information about configuring retry attempts.