SAP ERP and SAP A1 - Error Handling (Magic xpi 4.13)
The Magic xpi Server checks for errors during the execution of a step. If there is an error in the SAP ERP or SAP A1 connector step, the Error Handler is invoked and handles the error.
The error codes for the SAP A1 connector are listed below:
|
|
1102
|
Connect process error: <Err Description>
|
1103
|
SAP A1 connector error return: <Err Description>
|
The error codes for the SAP ERP connector are listed below:
|
|
8888
|
.Net Exception
|
9999
|
Java Exception
|
1102
|
Connect process error
|
1103
|
SAP ERP connector error return
|
1601
|
Step invocation error
|
1602
|
ACM: No available AC found
|
1603
|
AC: Step incorrectly configured
|
1604
|
Input/output error
|
1605
|
Communication: Data Transfer error
|
1606
|
.NET launcher: failed to call .NET connector
|
1607
|
.NET launcher: More than one IStep.NET.assembly found
|
1608
|
.NET launcher: No IStep.NET.assembly found
|
1609
|
Communication: Message processing error
|
1610
|
RemoteStepInvoker: Invocation timeout error
|
1611
|
.NET launcher:Jave.NET interop failure
|
1612
|
AC: Unknown connector name
|
1613
|
AC: Unsupported runtime technology
|
1614
|
AC: Metadata file for the connector not found
|
1615
|
AC: Wrong data in metadata.xml file
|
You can also use Magic xpi's General Component Errors with the SAP ERP or SAP A1 connector. The codes are returned to the Magic xpi Server in the Invocation program’s Error Code parameter.
Error Handling in Magic xpi