The input to a 997 map is the log file created by the inbound map that requested the Functional Acknowledgement. To create a correct 997, you must use either an ODBC log or an expanded text log in the inbound map requesting the 997. If you used a short text log, the 997 will be created, but it will be incorrect.
A TA1 interchange acknowledgement is used to indicate whether a functional acknowledgement is expected back from the receiver of a transaction set. If it is, the TA1 writes certain information to the log during mapping that enables it to process the functional acknowledgement. The TA1 does not guarantee anything about the correctness or completeness of the contents of the ISA envelope – it merely acknowledges that it was received. A TA1 is normally used in test environments to verify the routing of documents.
Table 1-3 lists the functional acknowledgement map names, which are located at C:\Program Files\Sybase\HIPAA52\Maps\FAMaps\4.0 and C:\Program Files\Sybase\HIPAA52\Maps\FAMaps\4.2.
Map |
Description |
|---|---|
997INBND |
ODBC-compliant log/inbound reconciliation |
997ODBCA |
ODBC-compliant log/ALL trading partner |
997ODBCT |
ODBC-compliant log/specific trading partner |
997XLGA |
Expanded text log/ALL TradePartner |
997XLGTP |
Expanded text log/specific trading partner |
LOGUPDATE |
ODBC or expanded text log/log persistence |
TA1_UPDATE |
ODBC log/inbound reconciliation any-to-any |
TA1ODBCA |
TA1 log/ALL trading partner |
TA1ODBCT |
TA1 log/specific trading partner |
TA1XLG. |
Expanded text log/in memory |
