This present post is in continuation with previous post of Error notification process part one . Going through the that post will give more convenience in under standing the present post.
Errors in the Inbound ALE/EDI Interface
Errors other than syntax errors can occur from the point at which a physical IDoc is created in the system to the point at which the IDoc is delivered to the application−posting program. These errors are mainly due to configuration problems in the partner profile or to information passed in the control record that does not find a matching partner profile. These errors are logged with a status code of 56 (IDoc with Errors Added).
Error in the Inbound Process: EDIITS00008068
For a non−syntax error during inbound IDoc processing before calling the posting program, the system initiates this task, and the person identified in the General view of the partner profile is notified. If a partner profile cannot be read at all, the IDoc administrator is notified.
Errors in the Application Posting Program
After an IDoc is passed to the posting program, errors reported by the posting program are considered application errors. These are logged in the IDoc with a status code of 51 (Application Document Not Posted).
Such errors are usually related to data in the IDoc and are among the most common errors seen on an inbound process.
A standard task exists for each incoming message. The naming convention is_Errors. These tasks are initiated as a result of an error event (InputErrorOccurred) triggered by the system on the application IDoc object. The person identified in the Inbound view of the partner profile for that message is notified.
For example, the task for incoming orders is Orders_Error (TS00008046). This task is started when the InputErrorOccurred event is raised on object IDOCORDERS. By using transaction SWE2, we can see the linkage between an event and the task in the event linkage table.
Syntax Errors during Outbound Processing
After an outbound IDoc has been created successfully in the system, the IDoc goes through a syntax check. This task is started for syntax errors found on an outbound IDoc. Errors are logged in the IDoc with a status code of 26 (Error during Syntax CheckOutbound). This error usually occurs during testing, and frequent syntax errors in a live system suggest a lack of testing .
Syntax ErrorOutbound: EDIXTS00008070
If an outbound IDoc fails the syntax check, the system initiates this task. The person identified in the partner profile for the IDoc message is notified.
Errors in the Outbound ALE/EDI Interface
Errors other than syntax errors can occur from the point at which a physical IDoc is created in the system to the point at which the IDoc is delivered to the EDI subsystem. These errors are mainly due to configuration problems in the partner profile, but can also occur when receivers for a message cannot be determined. These errors are logged with a status code of 29 (Error in ALE Service).
Error in the Outbound Process: EDIOTS00007989
For non−syntax errors when processing outbound IDocs the system initiates this task, and the person identified in the General view of the partner profile is notified. If a partner profile cannot be read at all, the IDoc administrator is notified.
Errors in the Outbound ALE/EDI Interface (IDoc Packet Processing)
When outbound IDocs are processed in groups, errors other than syntax errors can occur from the point at which a physical IDoc is created in the system to the point at which the IDoc is delivered to the EDI subsystem. These errors are mainly due to configuration problems in the partner profile, but can also occur when receivers for a message cannot be determined. These errors are logged with a status code of 29 (Error in ALE Service).
Error in the Outbound Process (IDoc Packet Processing): EDIPTS60001307
For non−syntax errors when processing outbound IDocs in packets the system initiates this task, and the IDoc administrator is notified.
Errors in the Subsystem
These errors are relevant only for outbound IDocs. When an IDoc leaves the SAP system and is transferred to the subsystem, errors encountered in the subsystem or processes thereafter are reported to SAP. These errors start a workflow that sends a notification to the EDI administrator. This task allows the administrator to initiate immediate reprocessing of the IDoc, if desired, when executing the work item.
Error in the Subsystem, Post−Processing Allowed: EDIRTS70008125
When the subsystem sends a status record reporting a processing error, the system starts this task, and the IDoc administrator is notified.
Error in the subsystem: EDISTS30000078
This error is also relevant only for outbound IDocs and is triggered by situations similar to those that trigger EDIR. EDIS was the standard process code up to version 4.6A, when EDIR replaced it. It can still be triggered as a fallback when configuration does not result in EDIR being called. If triggered, the system starts this task, and the IDoc administrator is notified.
Related Posts
SAP WORK ITEM AND INBOX
EDI Tasks and Roles SAP ABAP BDC PART 11
SAP ABAP BDC PART 12 BDC SAMPLE CODE FOR XD01
SAP ABAP BDC PART 13 BDC SESSON METHOD SAMPLE CODE
Errors in the Inbound ALE/EDI Interface
Errors other than syntax errors can occur from the point at which a physical IDoc is created in the system to the point at which the IDoc is delivered to the application−posting program. These errors are mainly due to configuration problems in the partner profile or to information passed in the control record that does not find a matching partner profile. These errors are logged with a status code of 56 (IDoc with Errors Added).
Error in the Inbound Process: EDIITS00008068
For a non−syntax error during inbound IDoc processing before calling the posting program, the system initiates this task, and the person identified in the General view of the partner profile is notified. If a partner profile cannot be read at all, the IDoc administrator is notified.
Errors in the Application Posting Program
After an IDoc is passed to the posting program, errors reported by the posting program are considered application errors. These are logged in the IDoc with a status code of 51 (Application Document Not Posted).
Such errors are usually related to data in the IDoc and are among the most common errors seen on an inbound process.
A standard task exists for each incoming message. The naming convention is
For example, the task for incoming orders is Orders_Error (TS00008046). This task is started when the InputErrorOccurred event is raised on object IDOCORDERS. By using transaction SWE2, we can see the linkage between an event and the task in the event linkage table.
Syntax Errors during Outbound Processing
After an outbound IDoc has been created successfully in the system, the IDoc goes through a syntax check. This task is started for syntax errors found on an outbound IDoc. Errors are logged in the IDoc with a status code of 26 (Error during Syntax CheckOutbound). This error usually occurs during testing, and frequent syntax errors in a live system suggest a lack of testing .
Syntax ErrorOutbound: EDIXTS00008070
If an outbound IDoc fails the syntax check, the system initiates this task. The person identified in the partner profile for the IDoc message is notified.
Errors in the Outbound ALE/EDI Interface
Errors other than syntax errors can occur from the point at which a physical IDoc is created in the system to the point at which the IDoc is delivered to the EDI subsystem. These errors are mainly due to configuration problems in the partner profile, but can also occur when receivers for a message cannot be determined. These errors are logged with a status code of 29 (Error in ALE Service).
Error in the Outbound Process: EDIOTS00007989
For non−syntax errors when processing outbound IDocs the system initiates this task, and the person identified in the General view of the partner profile is notified. If a partner profile cannot be read at all, the IDoc administrator is notified.
Errors in the Outbound ALE/EDI Interface (IDoc Packet Processing)
When outbound IDocs are processed in groups, errors other than syntax errors can occur from the point at which a physical IDoc is created in the system to the point at which the IDoc is delivered to the EDI subsystem. These errors are mainly due to configuration problems in the partner profile, but can also occur when receivers for a message cannot be determined. These errors are logged with a status code of 29 (Error in ALE Service).
Error in the Outbound Process (IDoc Packet Processing): EDIPTS60001307
For non−syntax errors when processing outbound IDocs in packets the system initiates this task, and the IDoc administrator is notified.
Errors in the Subsystem
These errors are relevant only for outbound IDocs. When an IDoc leaves the SAP system and is transferred to the subsystem, errors encountered in the subsystem or processes thereafter are reported to SAP. These errors start a workflow that sends a notification to the EDI administrator. This task allows the administrator to initiate immediate reprocessing of the IDoc, if desired, when executing the work item.
Error in the Subsystem, Post−Processing Allowed: EDIRTS70008125
When the subsystem sends a status record reporting a processing error, the system starts this task, and the IDoc administrator is notified.
Error in the subsystem: EDISTS30000078
This error is also relevant only for outbound IDocs and is triggered by situations similar to those that trigger EDIR. EDIS was the standard process code up to version 4.6A, when EDIR replaced it. It can still be triggered as a fallback when configuration does not result in EDIR being called. If triggered, the system starts this task, and the IDoc administrator is notified.
Related Posts
SAP WORK ITEM AND INBOX
EDI Tasks and Roles
SAP ABAP BDC PART 12 BDC SAMPLE CODE FOR XD01
SAP ABAP BDC PART 13 BDC SESSON METHOD SAMPLE CODE
No comments :
Post a Comment