Ansicht
Dokumentation

JHAC0004 - IS-M/AM: Addition of Customer-Specific Data to Contract

JHAC0004 - IS-M/AM: Addition of Customer-Specific Data to Contract

BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

This enhancement means it is possible to take account of additional fields when editing a contract (import, dialog, save). These fields can be displayed for processing in screen exit SAPLXJHV 0200.

These additional fields can be added to the existing database tables for the contract using a customer append and are then read and updated automatically by the system together with the standard fields. Global variables in the contract dialog have the same structure as the database tables and are therefore also enhanced by the additional fields. You must program the following function exits to make these additional fields available to screen exit SAPLXJHV 0200:

  • EXIT_SAPMJHW1_001: Prior to dialog, global variables that are transferred as parameters must be copied into the global structures in function group XJHV. These global structures can then be displayed in screen exit SAPLXJHV 0200.
  • EXIT_SAPMJHW1_002: Following dialog, the global structures in XJHV must be copied to the global variables in the contract dialog that are transferred as parameters.

The system can also read additional customer-specific tables. The following function exits must be programmed to do so:

  • EXIT_SAPLJHAB_002: When a contract is imported, the customer-specific tables must be read and the data stored in the global variables for function group XJHV. This function can be accessed for several contracts successively. This means that the global variables in XJHV must have the capacity to store data for several contracts simultaneously.
  • EXIT_SAPLJHAB_001: When any contract is updated, the global variables in XJHV must be updated in the customer-specific tables.
  • EXIT_SAPLJHAB_003: When any contract is initialized, the global data in XJHV must also be initialized. This means it is possible to retain imported values in the global variables for XJHV and to store values that have been changed in dialog in additional global variables. During the update, it is possible to determine the changes that have actually been made by means of comparison and only save these to the database. Variables must also be initialized during the initialization process. If you fail to do so, the system would attempt to save changes to the database that have already been saved during a previous update when it next performs the update.





General Material Data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 3084 Date: 20240424 Time: 214705     sap01-206 ( 72 ms )