Kontakt

Ansicht
Dokumentation

RJ-J2SIM - IS-M/SD: LIS Simulate Update of Correction Orders

RJ-J2SIM - IS-M/SD: LIS Simulate Update of Correction Orders

General Material Data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program simulates update for one correction order (complaint or return) and creates an update log.

The program does not check whether the key figures for the selected correction order have already been taken into account in the statistics databases, and this is also not technically possible since it cannot be seen from the order. However, this is unimportant in a simulation; processing takes place as if the selected order had been created in the system.

The function can be used for the following purposes:

  • To check your customizing settings for updating an existing correction order
  • To check why a correction order did not trigger an update

Note

Existing update logs will be overwritten.

Output

The program outputs the new update log. The log contains a list of all updates (with information structure / update group) triggered by the correction order.

To analyze a particular update, position the cursor on the appropriate line and choose 'Details'. This function displays all data relevant to the business transaction.

According to your definition of the update rules, the program displays an overview of the key figures that were to be updated from the document. The following information is displayed for each key figure:

  • Content (updated value of key figure):
    'No update' means that no update took place, for example because a requirement was not met. In this case, the details screen provides you with a further analysis option: Position the cursor on the line you want to analyze and choose 'Key figure' or 'Features'. The details screen contains information on the source data of the document for update.
  • O/N stands for Old/New and indicates whether the update procedure is creating or changing data.
  • If a document is created in the application, new update transactions are created.

  • If a document is changed, the update triggered by creation must be corrected. In a first step, the update triggered is posted negatively. This posting is marked as 'Old' in the overview. In a second step, the new constellation is updated in the transaction as with creation and marked as 'New' in the overview.

  • The next column displays the hierarchy level of the document that triggered the update (e.g. item, schedule line).






Addresses (Business Address Services)   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 2708 Date: 20240531 Time: 062314     sap01-206 ( 49 ms )