EMDK0001 - IS-U: contract - subscreen integration and field check

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Enhancement

You can maintain your own fields or tables for the contract. You do this in a subscreen in the contract transactions ES20, ES21, and ES22.

For this subscreen, you must create and activate a screen and some function modules. You use these function modules to enter and check your data.

The customer-specific program enhancement communicates with the contract transactions via the normalized enhancement function modules EXIT_SAPLES20_001 to EXIT_SAPLES20_010.

Note that the enhancement function modules for the contract are also processed during move-in.

From this group of function modules you can activate the following function modules, which are not dependent on the other components of the enhancement; in other words, you do not require a CI include. The subscreens must exist, but can be blank.

• EXIT_SAPLES20_001

You can use this function module to carry out your own field checks.

• EXIT_SAPLES20_002

You can use this function module to supply fields with default values.

Note

You store your own coding for each function module in the following include files:

Function module	Include file
EXIT_SAPLES20_001	ZXES20U01
EXIT_SAPLES20_002	ZXES20U02
EXIT_SAPLES20_003	ZXES20U03
EXIT_SAPLES20_004	ZXES20U04
EXIT_SAPLES20_005	ZXES20U05
EXIT_SAPLES20_006	ZXES20U06
EXIT_SAPLES20_007	ZXES20U08
EXIT_SAPLES20_008	ZXES20U09
EXIT_SAPLES20_009	ZXES20U010
EXIT_SAPLES20_010	ZXES20U011

Recommendation

Before you implement this enhancement, SAP recommends that you familiarize yourself with the development model for the Utilities Industry (IS-U) component. You require this information to understand the program structure and the function modules, and it will also assist you in implementing your own coding.

When adding your own data to the contract, you have the following options:

• For data that you enter directly in the table EVER (SI/CI include), you must implement and activate the following components:

• Function modules the following function module documentation:

- EXIT_SAPLES20_003 (PBO)

- EXIT_SAPLES20_004 (PAI_BEFORE)

- EXIT_SAPLES20_005 (PAI_AFTER)

- EXIT_SAPLES20_007 (INPUT)

- EXIT_SAPLES20_009 (ACTION)

• Screen SAPLXES20, screen number 0200

• (for the new fields in ES20 contract maintenance)

• Screen SAPLXES20, screen number 0300

• (for the new fields in contract maintenance, move-in)

• CI include CI_EVER (customer table with your own data)

• For data in your own tables, which are not dependent on the contract, you must implement and activate the following components:

• Function modules the following function module documentation:

- EXIT_SAPLES20_003 (PBO)

- EXIT_SAPLES20_004 (PAI_BEFORE)

- EXIT_SAPLES20_005 (PAI_AFTER)

- EXIT_SAPLES20_006 (OPEN)

- EXIT_SAPLES20_007 (INPUT)

- EXIT_SAPLES20_008 (PREPARE_CLOSE)

- EXIT_SAPLES20_009 (ACTION)

- EXIT_SAPLES20_010 (CLOSE)

• Screen SAPLXES20, screen number 0200

• Screen SAPLXES20, screen number 0300

ROGBILLS - Synchronize billing plans   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 5828 Date: 20211129 Time: 005848     sap01-206 ( 58 ms )