Status Processing 

 

Use

The status records log the stages through which the IDoc passes along its path, for example “generated” or “ready for dispatch”.This data is important for monitoring communication and compiling statistics.

Features

Processing

The subsystem can inform you of the processing stages for an IDoc which has been received. The following status confirmation (or status report) methods are possible:

●      Status records can be forwarded to the IDoc Interface using the file port. The IDoc number is used for identification purposes. The receiving system determines at what time the status message is returned. Each status record must contain the number of the IDoc to which it refers. In this way, a link can be created to the IDoc and to the application document in the IDoc Interface.

 

The status records that the confirmation can contain depends on the configuration and technical capabilities of the subsystem.

●      Status records can also be returned as an IDoc (IDoc type SYSTAT01). In this case, all possible communication paths (= port types) are permitted.

Do not confuse the status information contained in the SYSTAT01 data records, which refer to a different (your) IDoc received by the partner, with the status records of SYSTAT01 itself. These are not discussed here.

Exception Handling

If the status confirmation indicates a communication error, exception handling is started (see also: Rule Resolution in Exception Handling ). A workflow can be triggered, during which the users responsible can respond to the communication error.

In the standard system, exception handling is implemented using process code EDIR, which refers to task TS70008125. If you are executing the work item as the recipient, you see the status record of the corresponding outbound IDoc. You can try to send the IDoc again, but the partner profiles will not be read a second time. All data required to send the IDoc is read from the control record. If, for example, you have exchanged the port in the partner profiles, the IDoc is still sent to the original port. As an alternative there is the process code EDIS with the task TS30000078, which only allows a status record to be displayed, but not the resending of the outbound IDoc.

When a release change occurs, you must carry out the IMG activity Extended exception handling for status confirmation use to switch from EDIS to EDIR.

The recipient is determined in the following order:

...

       1.      If a user is entered in the outbound partner profiles, that person is notified.

       2.      Otherwise, the person defined in the general partner profiles is notified.

Customizing Activities

You can decide which statuses are error statuses which trigger exception handling: Choose the transaction SALE ® IDoc Interface/ALE ® Set-Up System Monitoring ® Set-Up IDoc Status Display ® Edit Status Values. In the detail screen enter a Process code that refers to a workflow. The workflow implements the exception handling in the standard system. In general however, it does not have to be like this. For more information, see Exception Handling: Procedure.

In status maintenance you can also display or change the status group (qualification) assignments which play an important role in the monitoring programs.