Kontakt

Ansicht
Dokumentation

RJ-J1SIM - IS-M/SD: LIS - Simulate Sales Order Update

RJ-J1SIM - IS-M/SD: LIS - Simulate Sales Order Update

ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program simulates the dialog update for one sales order and creates an update log.

The system does not check whether or not the key figures for the selected sales order have already been taken into account in the statistics database. This is also not possible technically since it cannot be seen from the order. However, this is unimportant when performing a simulation: here processing takes place as if the selected order was created in the system.

Examples of when to use this function:

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

Note

Existing update logs will be overwritten.

Output

The program displays the new update log created. The log contains a list of all updates (with information structure / update group) that were triggered by the sales 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 procedure.

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, perhaps because a requirement was not met. In this case, the details screen provides you with a further option for analysis: position the cursor in the line you want to analyze and choose 'Key figure' or 'Features'. The details screen contains information on the source data from the document for update.
  • O/N stands for Old/New and indicates whether an update transaction is one 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 the creation must be corrected. To do this, the update triggered is posted negatively in a first step. This posting is marked 'Old' in the overview. In a second step, the new constellation is updated as for creation and marked as 'New' in the overview.

  • The hierarchy level of the document that triggered the update is displayed in the next column (for example, item, schedule line).






ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 2703 Date: 20240601 Time: 011902     sap01-206 ( 55 ms )