WLF_IDOC: IDoc Processing

Transaction code WLF_IDOC, IDoc monitor is an optimized enhancement of the standard SAP IDoc reporting (transactions WE02, WE05, and BD87).

A distinction can be made between the following functional areas:

• Selection
  • Optimized and additional selection options
  • Process-based selections – a predefined action is executed for the hits of a selection.
• Output
  • A large number of new functions is available on the output screen. These are mostly of interest for administrators and developers.
• New IDoc processing function:
  • The new IDoc editor is a configurable tool, used to not only make it easier to process IDocs, but also to adapt the interface of the individual objects so that a user department employee can process the IDocs. The new IDoc editor works on an ALV basis, which means that a separate window is generated for each segment type, for display and processing.

Selection

Standard Selection

• Maximum number of hits
• Simplified input, using a time function (all IDocs as of…)
• Selection options using all fields of the IDoc control record, via standard selection and additional selection

Extended Selection Options

The extended selection reduces the hit list from the basic selection, to the IDocs that correspond to the specified criteria.

• Selection options using status records:
  • You can select IDocs according to specific error messages. You can search using either the last/most current status records, or all status records.
• Free restriction using segment content:
  • You can filter the content of up to two segment fields, based on preliminary hit lists (using the standard selection as a basis). Free restrictions (selection options) are supported.
    • The LOG function is also available on the output screen. You can call up a log that documents the hits.
• Optional:
  • The content of the segment fields that can correspond to the search criteria can be changed. This function should be used with caution. It can change a very large number of IDocs. The new values are not checked.
    • Prerequisite: You must enter a unique message type or basic type if you want to use the F4 help for a segment type.

Process-Based Selection

The result of a selection leads to a predefined action.

• Monitoring:
  • You have the option to trigger an error if the selection shows a specific result.
    • Example: An unknown number of IDocs is processed in the batch. If more than one percent of these IDocs has errors, the process chain should be interrupted.
    • You can specify parameters for an age-based spacing of the IDocs. The selected IDocs are grouped according to this spacing (columns ICON_RASTER and AGE_DAYS). You can display the spacing with a specific layout variant, for analysis purposes.
• Background processing:
  • You can use this program to set up job-based parallel IDoc processing. In this case, jobs that process the IDocs in parallel are generated, according to your specifications.
• Optionally, the final status of both the jobs and the processed IDocs can be checked, and possible errors can be logged.
  • Example: You want to process an unknown number of IDocs, using ten jobs. The program selects the relevant IDocs, and distributes them equally to ten jobs.
  • Alternatively, you can create n jobs, with 100 IDocs each. You can monitor these generated jobs, and so ensure that the job chain continues only when all IDocs are processed.

Output

The output is in ALV format by default, that is, line-based without a tree structure. Advantage: The output can take place in the background, is freely configurable, and contains the regular dialog function of the ALV grid.

There is also a large number of functions on the output screen.

• Display IDoc:
  • You can display the content of an IDoc by clicking the IDoc number, or selecting a line and choosing the Display IDoc function. The IDoc is displayed in the new ALV-based view.
• Edit IDoc:
  • Select a line in the hit list and execute the Edit IDoc function.
• Direct display of status records as an application log (popup):
  • If you choose the icon for status records on the output screen, the current status records are displayed.
  • You can use BAdI method SELECT_EXTERNAL_DATA of definition WLF_PROCESS_EDIDS_EXTERNAL (spot WLF_IDOC_PROCESSING) to also display status records that are stored in external tables (not EDIDS).
  • You can use BAdI method CALL_TCODE of definition WLF_PROCESS_TCODE_CALL (spot WLF_IDOC_PROCESSING) to assign application-specific transactions to error messages, to simplify error processing.
  • Example: When a specific error message appears, the transaction Change Material (MM02) should be offered.
• Display of current status record:
  • By clicking the traffic light icon in the Status column, you navigate directly to the display of the latest status record.
• Direct display of linked objects (if available):
  • If you choose the icon for object links (for example, application documents) on the output screen, the current links are displayed. The icon varies, depending on the number of linked objects.
• Navigation to message type, partner profiles, IDoc type, and so on:
  • Some columns allow direct navigation to their respective context. These columns are underlined – the cursor symbol changes when it hovers over one of these columns (hotspot).
• Send IDocs:
  • You can send IDocs to another logical system. The IDoc is copied to the target system. There are no content checks. The control record can be adapted so that the information corresponds to the partner profiles in the target system.
  • Example: An IDoc with errors should be copied to the test system for analysis. Prerequisite: An RFC connection must be available, and you must have the authorization to use it.
• Compare IDocs:
  • You can compare two IDocs. You can do this in one system, or different systems. The result is output as an application log.
  • Example: After a program correction, you want to check whether an IDoc’s content is correct.
  • Local comparison: Select two IDocs in the hit list, and execute the Compare IDocs function.
  • Remote comparison: Select one IDoc, and execute the Compare IDocs function. You are now asked to select a target system or comparison system, and log on to it.
  • In the target system, choose your comparison list, and select an IDoc. Once you execute the Save function, the comparison is carried out. The contents of all segment fields are compared. Prerequisite: The IDocs have the same IDoc type.
• Call up log:
  • If you search IDocs for field content, you can call up the results log where the hits are documented. It is possible to navigate directly to the respective segment. If a new field value was allocated, the IDocs for which a change was made are flagged.
  • Note: The changes are documented (the unchanged original IDoc is saved (status 70)).
• Change status:
  • If you have the corresponding authorization, you can change the status of selected IDocs (validation only for context input/output). This function is mainly useful in test situations, when IDocs should be processed multiple times.
  • Note: The changes are documented as status records.
• Process selected IDocs:
  • Selected IDocs can be processed in the following ways:
  • a) Direct processing (foreground): The selected IDocs are processed in the foreground.
  • b) Dialog processing (BD87): The selected IDocs are submitted to transaction BD87, and displayed in dialog mode.
  • c) Background processing: The selected IDocs are processed in the background.
  • Note: Only IDocs with a status that allows processing are taken into account here.
• Change control record:
  • In a nonlive system, you can adjust the fields of the control record.
• Change view:
  • The selected IDocs can be displayed in two ways in a hierarchical tree structure. If you select IDocs in the hit list, only these IDocs are submitted; otherwise, all IDocs are submitted.
  • By status
  • By message type
• Call transaction via RFC:
  • Use this function to execute the current transaction in a remote system. You may have to log on to this system.
• Copy IDoc and delete a segment:
  • You can delete an individual segment of an IDoc, using the segment number. The original IDoc is not changed by this or linked with the copy.

New segment editor

The new IDoc editor is a configurable tool, used to not only make it easier to process IDocs, but also to adapt the interface of the individual objects so that a user department employee can process the IDocs. The new IDoc editor works on an ALV basis, which means that a separate window is generated for each segment type, for display and processing.