Can I Upload Some of the Files to Idoc

This blog volition give tips & tricks on working with idocs.

Questions that will exist answered are:

How can I actively monitor idocs?
How can I reprocess idocs in error?
How to procedure idocs in collect manner?
How can I search the business concern content of idocs?
How to execute technical consistency bank check for the idoc settings?
How can I make clean up idocs?
How can I force a change of idoc status?

Idoc search and list

Next to WE02 and WE05, yous can use transaction WLF_IDOC to listing idocs. WLF_IDOC tin can also scan the idocs for content. Read more than on WLF_IDOC in this blog.

WE06 agile idoc monitoring

Transaction WE06 can be used to setup active idoc monitoring. If idocs are running into filibuster for certain status, yous can send workflow:

You need to activate the ALARM message workflow: this is a piece of work item of the TS74508518 standard chore.

Read the total SAP help for more than details.

WE09 search idoc for business content

Transaction WE09 tin be used to search idocs for business content:

Brusque instruction on how to utilise WE09 is documented in OSS note 1823081 – WE09 – criteria for searching in data records.

A search office is also bachelor in transaction WLF_IDOC.

Set idoc status

Program RC1_IDOC_SET_STATUS can exist used to change an idoc status:

This program is meant to run on non-production systems. Take special intendance and call back twice before running this program on a productive system.

Technical consistency check

You tin can utilise transaction BDM5 to execute a technical consistency bank check for your idoc configuration:

Per item a lot of sanity checks are performed:

Processing inbound idocs that are on collect

Yous can utilise transaction BD20 to process inbound idocs with partner profile on collect (idocs status 64):

You tin can also schedule the program RBDAPP01 in batch to process the idocs in status 64 periodically.

When yous post too many idocs too fast with firsthand processing, the SAP organization might get overloaded and volition leave the idocs in condition 64. In this example all-time to switch to collect fashion and plan the program RBDAPP01 periodically for processing. See more than in OSS note 1872637 – Delays posting entering IDocs (condition 64) which have been configured to trigger immediately.

Problems fix OSS note for RBDAPP01: 2795034 – RBDAPP01 – selection of IDocs that have not yet been completely saved (dirty read).

For parallel processing read this note: 2697762 – ALE: Maximum processes for processing.

Idocs remaining on status 64

In weird cases inbound idocs with partner profile set to process immediately remain in condition 64.

Potential root causes:

Temporary system overload (no more free work processes)
Short dump in idoc processing (check in transaction ST22)
Wrong configuration in SWE2 event linkage: see OSS note 1776423 – IDocs remain in status 64 despite existence gear up to "Trigger immediately" in WE20
Wrong configuration for idocs from file: meet OSS note 2706508 – All of a sudden, inbound IDoc´s are not being processed automatically, and remain in status 64

Sending outbound idocs that are on collect

If you have configured outbound idocs to be nerveless, the idocs remain in status 30 until they are to be sent out. The sending tin be washed with transaction WE14 or by batch task of programme RSEOUT00:

Recent bug note on RSEOUT00: 2747015 – IDoc: Locks in IDoc outbound processing.

Custom idoc processing remains in status 30

If y'all take custom idocs or custom idoc processing and y'all call function module MASTER_IDOC_DISTRIBUTE for the outbound distribution, the idocs might go stuck in status 30, fifty-fifty if you set up the partner profile to immediate processing. If this is the case, read OSS note 1575852 – Outbound IDocs remain in status 30. This solution provided might seem strange, but information technology does work:

Implement the following "triple" into your program that creates the idocs:

Call Part 'DB_COMMIT'.
CALL FUNCTION 'DEQUEUE_ALL'.
COMMIT WORK.

Checking that outbound idocs accept passed RFC layer

If at that place are issues with outbound idocs, most likely information technology is because they are stuck in the RFC layer. Y'all tin can cheque this with transaction SM58.

You can use transaction BD75 to catechumen the idocs from status 03 to condition 12. Status 12 means that they have correctly passed the RFC layer. The plan backside BD75 is RBDMOIND, which can also exist planned in a batch job:

Reprocessing failed entering and outbound idocs with technical errors

If outbound idocs fail with technical errors similar 02, 25, 26, 29: kickoff correct the technical setup error. When the setup is fixed, you can utilize transaction BD83 to reprocess the failed idocs (in stead of regenerating them):

If entering idocs neglect with technical errors like 56, 61 , 63: first right the technical setup error. When the setup is fixed, you lot tin use transaction BD84 to reprocess the failed idocs (in stead of request the sender to send them again):

Planning these programs in batch chore is non a good idea. Fix the root cause, then this reprocessing is not required any more than in the futurity.

Reprocessing edited idocs

If y'all have edited idocs and desire to reprocess them again, use transaction WPIE to starting time the processing:

Reprocessing inbound idocs in condition 51

Y'all can use program RBDMANI2 to reprocess idocs in status 51 (error in functionality):

This program is usually run in background manner every bit well in productive system. In a productive system don't run information technology too frequently, since very try volition add together a new condition 51. Therefore as well limit the amount of days of history you want to reprocess automatically. Do use the option to filter on message class and number, to reprocess but selective messages for selective message type. The most common apply is to reprocess idocs that could not exist processed due to another user locking the data.

This might result into a couple of variants, or even a couple of different batch jobs running at different frequencies for reprocessing different message types.

If the reprocessing takes long fourth dimension, read OSS note 2524675 – Long processing time when processing IDocs in status 51. This basically tells you to start deleting or archiving idocs.

Idoc clean upwards

Transaction WE11 tin can exist used to delete idocs. If you desire to archive idocs, you tin use archiving object IDOC. Run across OSS note 40088 – Deletion or reorganization of IDocs, or this blog on technical clean up.

hicksonbaid1970.blogspot.com

Source: https://www.saptechnicalguru.com/idoc-tips-tricks/