APPENDIX: Response Codes for X12 Bridges
Important
Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.
If you're brand new to Logic Apps, then we suggest getting started here:
-
Create your first logic app, or quickly get started using a pre-built template
-
View all the available connectors you can use in your logic apps
Lists the possible response codes you might encounter when a message is processed using the X12 Receive or X12 Send pipelines in the BizTalk Services Portal.
Response Code |
Description |
|---|---|
200 |
This response code denotes that all the transaction sets in the message/interchange were processed as well as routed successfully. |
202 |
This response code denotes that even though all the transaction sets in the messages/interchange were processed successfully, there were errors while routing one or more of them to the success endpoint. However the ones which could be routed to the success endpoint were routed to the suspend endpoint successfully. |
206 |
This response code denotes that one or more transaction sets failed processing. The successfully-processed transaction sets are routed to the success endpoint and the others that failed processing are sent to the suspend endpoint. |
500 |
This response code denotes all other issues that might be encountered while processing transactions set(s) in a message/interchange. Such a response code is mostly encountered when even the message suspension fails. |
See Also
Configuring EDI, AS2, and EDIFACT on BizTalk Services Portal