Errors can be encountered at various points in the inbound and outbound processes of SAP edi/ale. work flow. Errors are routed to responsible agents via workflow. The selected agents find a work item in their Inbox. The work items can be executed to examine the details of the error. After the problem is fixed, the process can be restarted from the point of failure.
The error notification process comprises the three steps given below and are explained further.
Errors are classified into categories, depending on the type. A task is started in response to an error. The error−handling process for each type of error is unique and defined in a task via the method that is executed.
A role is also defined for each task to identify the person responsible for it. The following sections describe the error categories, listing the process code and task for each.
General Errors are encountered in the process before an IDoc is created. In the inbound process, these errors are related to reading or deleting the IDoc file at the OS level, or to any internal errors in processing an incoming IDoc file. In the outbound process, these errors can be related to errors creating the output file.
No IDoc created yet: EDIMTS30000020
This process code can sometimes be invoked by file−opening and reading problems when processing status files from the EDI subsystem. The system initiates this task, and the IDoc administrator is notified.
Display NAST Record with Msg. No IDoc created yet: EDINTS70008037
If an error occurs before an IDoc is created in an outbound process using Message control, this process code is invoked. When the work item is processed, it displays the object keys of the NAST record that attempted to trigger the IDoc creation.
Using information from the NAST record, the system attempts to notify the receiver identified either in the Outbound Partner Profile view for the partner and document or in the General view. If neither can be determined, the IDoc administrator is notified.
Error in the Inbound Status File: EDILTS70008373
If an error occurs in the processing of an IDoc status file from the EDI subsystem before an IDoc is created, the system triggers this process code. Such errors result from problems in opening the file, reading the status records, or formatting problems on a record and the IDoc administrator is notified.
Syntax Errors during Inbound Processing
After an inbound IDoc has been created successfully in the system, the IDoc goes through a syntax check. When syntax errors are found in an incoming IDoc, they are logged in the IDoc with a status code of 60 (Error during Syntax CheckInbound). Syntax errors usually occur during testing; frequent syntax errors in a live system suggest a lack of testing.
Syntax ErrorInbound: EDIYTS00008074
If the inbound IDoc fails the syntax check, the system initiates this task, and the person identified in the partner profile for the IDoc message is notified.
Related Posts
SAP WORK ITEM AND INBOX
EDI Tasks and Roles
Business Objects
ALE EDI WORK FLOW architechere
The error notification process comprises the three steps given below and are explained further.
- Determining the task to be started.
- Routing the error to a responsible agent as a work item.
- Processing the work item by the responsible agent.
Errors are classified into categories, depending on the type. A task is started in response to an error. The error−handling process for each type of error is unique and defined in a task via the method that is executed.
A role is also defined for each task to identify the person responsible for it. The following sections describe the error categories, listing the process code and task for each.
General Errors are encountered in the process before an IDoc is created. In the inbound process, these errors are related to reading or deleting the IDoc file at the OS level, or to any internal errors in processing an incoming IDoc file. In the outbound process, these errors can be related to errors creating the output file.
No IDoc created yet: EDIMTS30000020
This process code can sometimes be invoked by file−opening and reading problems when processing status files from the EDI subsystem. The system initiates this task, and the IDoc administrator is notified.
Display NAST Record with Msg. No IDoc created yet: EDINTS70008037
If an error occurs before an IDoc is created in an outbound process using Message control, this process code is invoked. When the work item is processed, it displays the object keys of the NAST record that attempted to trigger the IDoc creation.
Using information from the NAST record, the system attempts to notify the receiver identified either in the Outbound Partner Profile view for the partner and document or in the General view. If neither can be determined, the IDoc administrator is notified.
Error in the Inbound Status File: EDILTS70008373
If an error occurs in the processing of an IDoc status file from the EDI subsystem before an IDoc is created, the system triggers this process code. Such errors result from problems in opening the file, reading the status records, or formatting problems on a record and the IDoc administrator is notified.
Syntax Errors during Inbound Processing
After an inbound IDoc has been created successfully in the system, the IDoc goes through a syntax check. When syntax errors are found in an incoming IDoc, they are logged in the IDoc with a status code of 60 (Error during Syntax CheckInbound). Syntax errors usually occur during testing; frequent syntax errors in a live system suggest a lack of testing.
Syntax ErrorInbound: EDIYTS00008074
If the inbound IDoc fails the syntax check, the system initiates this task, and the person identified in the partner profile for the IDoc message is notified.
Related Posts
SAP WORK ITEM AND INBOX
EDI Tasks and Roles
Business Objects
ALE EDI WORK FLOW architechere
No comments :
Post a Comment