What is IDoc?
IDoc or Intermediate Document represents an SAP (System Applications and Products in Data Processing) document format for business transaction data transfers. SAP IDoc’s purpose is similar to XML – data exchange and automation in computer systems. IDoc acts as the data container and offers many automation, monitoring, and error handling tools in the SAP system.
Idoc Script has many implicit worldwide capacities. Capacities perform activities, including string correlation and control schedules, date organizing, and ResultSet control. A few capacities likewise return results, for example, the consequences of figurings or examinations.
Data is passed to capacities by encasing the data in enclosures after the name of the capacity. Snippets of data that are passed to a capacity are called boundaries. A few capacities don’t take boundaries; a few capacities take one boundary; some take a few. There are likewise works for which the quantity of boundaries relies upon how the capacity is being utilized.
Alongside worked in capacities, Idoc Script utilizes a scope of factors. Factors utilized inside Idoc contents incorporate powerful factors, contingent unique factors, and page show factors. A large number of these factors can be utilized both inside contents and indicated exclusively in the WebCenter Content config. cfg and intrados.cfg documents, or utilized in an internet browser URL.
How to find IDoc error and how to reprocess?
- 1) If you want to reprocess the IDOC with the correct storage location, use the transaction code WE19 and enter the existing IDOC number, and press enters: Goto WE19, select IDoc and execute.
- 2) The details will be shown in the IDoc.You will face a test tool for the IDOC processing screen; enter the correct value of the storage location in the corresponding field and click the standard inbound icon.
- 3) Change the data in the segment as per your requirement.
- 4) Click on the standard inbound process.
Blunders in the Inbound ALE/EDI Interface
Blunders other than punctuation mistakes can happen from where a physical IDoc is made in the framework direct at which the IDoc is conveyed to the application−posting program. These mistakes are basically because of arrangement issues in the accomplice profile or data passed in the control record that doesn’t locate a coordinating accomplice profile. These mistakes are logged with a status code of 56 (IDoc with Errors Added).
A mistake in the Inbound Process: EDIITS00008068
For a non−syntax mistake during inbound IDoc handling before calling the posting program, the framework starts this errand. The individual distinguished in the General perspective on the accomplice profile is informed. If an accomplice profile can’t be perused by any means, the IDoc overseer is advised.
Mistakes in the Application Posting Program
After an IDoc is passed to the posting program, mistakes detailed by the posting program are viewed as application blunders. These are signed in the IDoc with a status code of 51 (Application Document Not Posted).
Such blunders are generally identified with information in the IDoc and are among the most well-known mistakes seen on an inbound cycle.
A standard assignment exists for every approaching message. The naming show is _Errors. These errands are started because of a blunder function (InputErrorOccurred) set off by the application IDoc object’s framework. The individual recognized in the Inbound perspective on the accomplice profile for that message is told.
For instance, the undertaking of approaching requests is Orders_Error (TS00008046). This undertaking is begun when the InputErrorOccurred function is raised on object IDOCORDERS. By utilizing exchange SWE2, we can see the linkage between a function and the assignment in the function linkage table.
Mistakes in the Subsystem
These mistakes are significant just for outbound IDocs. When an IDoc leaves the SAP framework and is moved to the subsystem, blunders experienced in the subsystem or cycles from there on are accounted for to SAP. These blunders start a work process that sends a warning to the EDI director. This errand permits the head to quickly reprocess the IDoc whenever wanted when executing the work thing.
A mistake in the Subsystem, Post−Processing Allowed: EDIRTS70008125
When the subsystem sends a status record revealing a preparing mistake, the framework begins this undertaking, and the IDoc head is advised.
Blunder in the subsystem: EDISTS30000078
Status Error 26 :
1. “Get details from previous status records with status 26.”
2. “EDI: Syntax error in IDoc (segment cannot be identified)”
This blunder is also important for outbound IDocs and is set off by circumstances like those that trigger EDIR. EDIS was the standard cycle code up to form 4.6A when EDIR supplanted it. It can even now be set off as a fallback when the design doesn’t bring about EDIR being called. Whenever set off, the framework begins this undertaking, and the IDoc manager is told.
Blunder code 26 methods the IDoc has an improper language structure. The tree structure of an IDoc is characterized in WE30 and tells the IDoc motor if a section is compulsory and how arranged the portions are composed. On the off chance that you attempt to construct an IDoc that doesn’t submit to this format, the motor tosses a grammar blunder with status code 26. You can deactivate the sentence structure check in the accomplice profile definition (WE20).