Ansicht
Dokumentation
M06B0002 - Changes to comm. structure for purchase requisition release
BAL_S_LOG - Application Log: Log header data CPI1466 during BackupThis documentation is copyright by SAP AG.
This user exit allows you to change the communication structure for determining the release strategy for purchase requisitions.
Examples:
-
Filling of user fields in CEBAN
-
The following user fields are available:
-
USRC1
USRC2
USRN1
USRN2
-
The communication structure CEBANZZ is also available. This allows you to apply your own fields.
- The cost center master record can be read via the cost center in the communication structure and the cost center manager inserted in the user field USRC1.
-
If the class for determining the requisition strategy contains a characteristic with reference to CEBAN-USRC1, the strategy is determined as a function of the cost center manager.
- Changing standard fields in CEBAN
-
If the value of the purchase requisition applied in the standard SAP System for strategy determination
is not to be used, the value can be calculated on a customer-specific basis. The field CEBAN-GSWRT can be overwritten with this value.
- If this class for determining the requisition strategy now contains a characteristic with reference to CEBAN-GSWRT, the strategy will be determined as a function of the changed value.
BAL_S_LOG - Application Log: Log header data CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Length: 1455 Date: 20240425 Time: 121946 sap01-206 ( 28 ms )