|Oracle® Fusion Middleware User's Guide for Oracle B2B
11g Release 1 (220.127.116.11)
Part Number E10229-13
|PDF · Mobi · ePub|
This appendix discusses the TA1 acknowledgment feature of Oracle B2B.
HIPAA messages are used for information exchange. HIPAA messages are required to send the Interchange Acknowledgment (TA1).
The appendix contains the following sections:
There are many kind of acknowledgments for a HIPAA document that are exchanged between initiator and responder.
When an initiator sends a message, following are the different types of the acknowledgments in the order of precedence:
TA1 – Interchange level acknowledgment
997/999– Functional acknowledgment (999 for 5010 versions and above)
The message flow is completed when TA1 or 997/ 999 is sent for inbound business message as shown in Figure K-1.
Figure K-1 TA1 acknowledgment
TA1 documents are available as a preseeded ZIP file in Oracle B2B.
Figure K-2 displays a sample TA1 document definition.
Figure K-2 A Sample TA1 Document Definition
Figure K-3 displays a sample TA1 agreement.
Figure K-3 A Sample TA1 Agreement
You can configure Oracle B2B to use TA1 both for the inbound and the outbound message directions.
For inbound messages, EDI position ISA14 Payload value of
1 determines whether Oracle B2B should send a TA1 acknowledgment. If the value is
1, then the the Interchange is checked and TA1 is sent to the trading partner.
For outbound messages, you can configure whether Oracle B2B should expect a TA1 acknowledgment from the trading partner in the Oracle B2B console.
To configure TA1
Log on to the Oracle B2B console.
Click Administration and then click Document.
Click EDI_X12 under Document Protocols in the Document navigation panel.
Create a document protocol version and name it
Click the Interchange tab in the Document Protocol Version section to the right.
Select either of the following from the TA1 list as shown in Figure K-4:
Always: A TA1 acknowledgment is always expected
OnError: A TA1 acknowledgment is expected when there is an error in the message
Figure K-4 Configuring TA1