Configuring Common Fallback Properties for X12 and EDIFACT Encoded Messages
Fallback properties apply to both X12 (including HIPAA) - and EDIFACT-encoded interchanges. As with all fallback agreement properties, these properties apply only when BizTalk Server has not determined the agreement to which an incoming our outgoing message resolves to.
Prerequisites
You must be logged on as a member of the BizTalk Server Administrators or BizTalk Server B2B Operators group.
To set common global properties
In the BizTalk Server Administration Console, right-click the Parties node, and then click X12 Fallback Settings or EDIFACT Fallback Settings.
In the Fallback Settings General Pages tab, on the General page, do the following:
Click Enable Fallback Settings to enable BizTalk Server to use the fallback agreement settings if no agreement is resolved for incoming or outgoing messages.
Important
If this option is not checked, BizTalk Server will not use the properties set in the fallback agreement.
Click Activate EDI Reporting to activate reporting for all EDI messages. This ensures messages are displayed in the status reporting screens displayed by clicking the links at the bottom of the Group Hub pane of the BizTalk Server Administration Console.
If you clicked Activate EDI Reporting, click Store transaction set/payload for reporting to store transaction sets in the EDI tables of the tracking (BizTalkDTADb) database.
Click Log EDI errors and warnings generated by EDI engine to Windows event log to log error/warnings messages generated by the EDI engine (EDI pipelines, batching orchestration, routing orchestration, etc.), with contextual information, to the Windows Event Viewer. If cleared, these error/warning messages will not be logged to the Event Viewer.
Note
System/processing errors are logged in the Event Viewer whether or not this checkbox is selected.
Click Apply to accept the changes before continuing with the configuration, or click OK to validate and accept the changes and then close the dialog box.