Sap idoc deletion program

You decide which one you want to allow. Depending on the setting, however, not all functionalities may be available to you. These cookies are vital for the functionality of the website.

Cookies that are set in connection with the system of the website. These cookies are used to generate statistics and enable us to optimise the website for visitors. Used to send data to Google Analytics about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels.

These cookies are used to ensure that any adverts visible are relevant to your interests. Services Integration Hub. Supplier Portal. Web EDI. EDI Optimisation. Getting Started with EDI. ERP Integration. Supplier Relationship Management. VAN Connectivity. White Papers. B2B Integration Life Cartoons. Vision, Mission and Values. Employee Voices. Philipp Liegl. Parallel Processing of iDocs batches can be activated by filling in the Parallel Processing parameters.

This is not the same as what we discussed previously about overlapping batch jobs. This program is useful to re-process Inbound iDocs which are in an error status.

Usually, when an inbound iDoc is not posted successfully, it will go into an error status of 51 Application document not posted. Notice the program does not have a selection parameter for iDoc Status. The program considers all iDocs in error status This is another important program that processes iDocs in yellow status.

If the iDoc is processed successfully from the program it will be converted from status 30 to status 03 Data passed to port OK. When you transfer multiple iDocs to the Port at the same time as a batch, this parameter defines the maximum number of iDocs added before the Commit Work. If the number is too large it might result in short dumps and time-outs of the process. As the name suggests, use this program to delete iDocs from the system.

Depending on the retention period of iDocs of your organization you can schedule this as a background job. Use this program to change the status of an iDoc manually. In a production environment, this program is mostly used to set the iDocs that should not be processed again to status 68 no further processing. You can ignore the warning but you then run the risk of possibly archiving some IDocs twice. Define the start date of the archiving session and the spool parameters print output.

The traffic lights should now be green, indicating that these parameters have been maintained. Please note that you can set the archiving mode for the print output to Store Only and therefore avoid printing every individual archiving log. Enter the object type IDOC as the attachment parameter and use the F4 Help to select a suitable document type for the object type. Also enter a free text as additional information for the archiving report.

Choose to create a report variant. As selection parameters, enter the message type and a time period within which the IDocs received their last, current status. You can specify whether you want to perform this variant as a Test run or Production run , in the Process Flow segment on the selection parameter screen.