EDI and AS2 Status Reporting
EDI status reporting enables operations personnel to track the status of EDI and AS2 transmissions. If enabled, status reports provide comprehensive status of a document exchange transaction, including an interchange and any acknowledgments correlated to the interchange. These reports provide data on receipt, validation, batching, and acknowledgment processing of EDI and AS2 messages.
You can use these reports to get the status of pending and unacknowledged interchanges, complete interchanges, error scenarios, or business scenarios. With these reports, you can do the following:
Confirm the receipt of interchanges
List outgoing interchanges awaiting acknowledgment
List all rejected interchanges received
List outgoing interchanges that are reported as rejected or partially accepted.
Data included in the status reports is obtained from interchange control segments, such as ISA, TA1, GS, UNB, and UNG (with the exception of the Functional ACK status).
Status Reporting UI
EDI and AS2 status reports are available from the BizTalk Server Administration Console. From the Group Hub page of the BizTalk Group node, you have links to EDI interchange and correlated acknowledgment status, batch status, and AS2 message and correlated MDN status. Each of these reports provides a range of status parameters that you can include or exclude from a query expression, enabling you to build the status report that they need.
In addition to seeing the status of an EDI interchange, you can also view the transaction sets in an interchange. You do so by enabling the storage of message payloads in the EDI tables of the tracking (BizTalkDTADb) database. You can view the transaction sets by using the view details command in the status reporting UI.
You can also store inbound or outbound AS2 messages or MDNs in the non-repudiation database. You can view the transaction sets or AS2 messages by right-clicking the message in the status report and selecting the appropriate command.
Status Report Components
The BizTalk Server components involved in status reporting are the following:
The EDI Disassembler in the EDI receive pipeline that creates and updates status entries in the data store for an incoming interchange
The EDI Assembler in the EDI send pipeline that creates and updates status entries in the data store for an outgoing interchange
The data stores that store the status report entries. These are the BAM Primary Import database for tracking data and the EDI Message Content table of the BizTalk tracking database (BizTalkDTADb) for EDI transaction sets and/or AS2 message contents
Status reporting UI on the Group Hub page of the BizTalk Server Administration console, which is used to display status reporting data
Agreement property and fallback agreement property options in BizTalk Server Administration console, which is used to enable and configure status reporting
DTA and SQL Analysis Server that leverage the BAM infrastructure.
In This Section
© 2010 Microsoft Corporation. All rights reserved.