OAGIS 10.1 XML Delivery Errors
After you run the Generate and Transfer XML Transactions process to deliver transactions in OAGIS 10.1 XML format, review the status of your XML transaction deliveries. If necessary, take corrective actions on any transactions that weren't successfully delivered.
XML Transaction Delivery Errors
Use the Manage Transactions page to review transactions delivered in XML format. Use Collaboration Messaging to review and correct any transactions with the XML delivery status Processing Error or Delivery Failed.
-
Use the Manage Undelivered Collaboration Messages page to review the error details of transactions with the XML delivery status Processing Error.
-
Use the Manage Failed Collaboration Messages page to review the error details of transactions with the XML delivery status Delivery Failed.
Inbound CBOD Collaboration Message
The inbound CBOD collaboration message returns an acknowledgment code of Success, Error, or Other. This acknowledgment code appears in the XML Delivery Status column of the Manage Transactions page.
The CBOD acknowledgment codes appear in the XML Delivery Status column in this way:
-
Document Received corresponds to Success.
-
Document Not Received corresponds to Error.
-
Unknown Acknowledgment Code corresponds to Other.
If a customer trading partner wants to send a status code other than one of these three, you can map customer codes to one of the three statuses using the Manage Confirmation Codes page of the Manage B2B Trading Partners task in the Collaboration Messaging work area.
Review Errors in XML Transaction Delivery
To review errors in XML delivery:
-
Navigate to the Manage Transactions page.
-
Search for transactions with the Delivery Method field set to XML.
-
Scroll across to expose the Ready for XML Delivery and XML Delivery Status columns.
-
If the XML Delivery Status column for an XML transaction displays Processing Error or Delivery Failed, use Collaboration Messaging to investigate the cause of the failure.
-
Navigate to the Collaboration Messaging work area.
-
If the status is Processing Error, navigate to the Manage Undelivered Collaboration Messages page.
You can either reprocess these transactions from the Manage Undelivered Collaboration Messages page or set them to Delivery Failed by canceling the transactions.
-
If the status is Delivery Failed, navigate to the Manage Failed Collaboration Messages page.
You can reprocess these transactions with another run of the Generate and Transfer XML Transactions process, setting the Transactions Included parameter to Failed Transactions.
Correct Errors in XML Transaction Delivery
Review and correct outbound processing, document retrieval, and inbound processing errors using the Manage Failed Collaboration Messages and Manage Undelivered Collaboration Messages tasks.
To review and correct errors in XML delivery:
-
Navigate to the Collaboration Messaging work area.
-
Open either the Manage Failed Collaboration Messages page or the Manage Undelivered Collaboration Messages page.
-
Search for the XML transaction you want.
-
In the Messages section, review the Error Type and Error Subtype columns:
-
Error Type displays the category of delivery error: Outbound Processing Error, Document Retrieval, or Inbound Processing Error.
-
Error Subtype displays the specific delivery error.
-
This table displays for each Error Type and Error Subtype the corrective action to use:
Error Type |
Error Subtype |
Corrective Action |
---|---|---|
Outbound Processing Error |
Collaboration Messaging Framework is disabled |
|
Outbound Processing Error |
Application Partner Document status is Disabled |
|
Outbound Processing Error |
External Partner Document not found |
|
Outbound Processing Error |
External Partner Message not found |
|
Outbound Processing Error |
Application Partner Document status is Hold |
|
Outbound Processing Error |
External Service Invocation Failure |
|
Outbound Processing Error |
Unexpected error |
|
Outbound Processing Error |
External Partner Document status not Active |
|
Outbound Processing Error |
External Partner Message status not Active |
|
Outbound Processing Error |
Application Service Invocation Failure |
|
Document Retrieval |
Application Partner Document not found |
|
Document Retrieval |
Application Query returned no records |
Rerun the Generate and Transfer XML Transactions process with the Transactions Included parameter set to Failed Transactions. |
Inbound Processing Error |
Setup validation failure |
|
Inbound Processing Error |
Unidentified Message Type |
|