Ansicht
Dokumentation

RJ-J4SIM - IS-PSD: Simulate Billing Doc.Update for LIS

Vendor Master (General Section)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Description

This program simulates LIS update for one billing document and creates an update log.

The program does not check whether the key figures for the selected billing documents have already been included in the statistics databases, and such a check would not be possible since this cannot be seen from the billing documents. Processing takes place as if the selected billing document had been created in the system.

Examples of when to use this function:

• To check your customizing settings for updating an existing billing document

• To check why a billing document did not trigger an update

Note

The program overwrites existing update logs.

Output

The program displays the new update log. The log contains a list of all updates (with information structure/update group) that were started by the billing document.

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

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

• Contents (updated value of key figure):
  'No update' means that the update did not take place, for example because a requirement was not met. In this case, you can use the details screen for further analysis: 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 being updated.

• O/N stands for old/new and indicates whether the update procedure has added or changed data.

• If a document is added in the application, this only results in new update transactions.

• However, if a document is changed, the update resulting from the addition must be corrected. The first step in doing this is to make negative posting for the update that took place when the data was created. This posting is marked as 'Old' in the overview. In a second step, the new constellation is updated in the transaction as if it had been created and marked as 'New' in the overview.

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

rdisp/max_wprun_time - Maximum work process run time   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 2738 Date: 20240531 Time: 062157     sap01-206 ( 31 ms )