How to Make a Mass Change of an IDoc Status

  • by Gaurav Aggarwal, Lead Consultant, SAP S/4HANA Finance, Infosys Limited
  • November 10, 2014
Learn how to install and use a custom program to change IDoc statuses en masse in SAP ERP Central Component (ECC) with flexible selection options that a standard SAP system does not have. By using this custom program, you can keep the IDoc queue clean and focus on IDocs that really need to be corrected.
Learning Objectives

By reading this article, you will learn how to:

  • Install and use a custom program to change the IDoc status en masse
Key Concept

An IDoc is an object in an SAP system designed to carry the data related to some transaction or master data from one application to another or from one system to another system. During the processing, an IDoc has various statuses until it reaches its final status (e.g., status 03 Data passed to port OK for an outbound IDoc). Therefore, organizations are interested in controlling the IDocs that are not yet in their final status and monitoring them to take corrective actions on those IDocs. If no more action is needed on the IDoc, the status can be changed to final so that there is no more monitoring done on that IDoc.

Organizations often may need to change the status of an IDoc manually. The statuses are different in different SAP transaction flows. For example, in normal outgoing payments, the statuses are 01 (IDOC Generated), 30 (IDoc ready for dispatch), and 03 (Data passed to port OK). An IDoc is not considered as processed (i.e., green status) until it has a status of 03.

The following scenarios call for a change in status:
 
•    During intercompany transaction flows, a billing document is not replicated as an invoice based on transaction code MIRO (enter incoming invoice) in another company code due to some omitted setting, such as a posting period not being open. Meanwhile, a user corrects the issue and books the invoice manually before the IDoc is retriggered. In such a case, setting the old IDoc status to processed is desired.
•    If exchange rate inbound IDocs are not updated in your system correctly and you want to reimport the IDocs. In this case, the old IDocs status can be changed.

•    In in-house cash management, the in-house cash center (IHC) sends the bank statement IDoc (FINSTA). However, if a duplicate bank statement is triggered before the original IDocs are processed, then the original IDocs fail because of a duplicate statement check. In such a case, the original IDoc needs to be set as processed. If the duplicate bank statement is triggered after the original IDoc is processed successfully, then the duplicate statement IDoc fails and the status of that would be required to be changed.

 

Gaurav Aggarwal

Gaurav Aggarwal is SAP S/4HANA lead consultant at Infosys Limited. He has more than 14 years of experience, including 11 years in SAP Finance. He has expertise in both SAP FI and Controlling (CO) with integration to other modules in manufacturing and process industries. He is a chartered accountant and SAP Certified Financial Consultant. He holds a bachelor’s degree in commerce and is a techno-functional expert with thorough knowledge of the necessary ABAP for functional experts. He is a veteran in G/L, AR, AP, banking, FA, Travel Management, and closing cockpit and has handled greenfield implementation, upgrades and conversions, rollouts, and support projects. 

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.