Routine USEREXIT_PRICING_PREPARE_TKOMK
Include RV60AFZZ (SAPLV60A )
This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document. This user exit is described in detail in the “New fields in pricing” section.
Routine USEREXIT_PRICING_PREPARE_TKOMP
IncludeRV60AFZZ (SAPLV60A)
This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing. This user exit is described in detail in the “New fields in pricing” section.
Routine USEREXIT_FIELD_MODIFICATION
IncludeMV61AFZA (SAPMV61A )
You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals. This user exit is also used in order processing.
Routine USEREXIT_FIELD_MODIFIC_KZWI
IncludeMV61AFZB (SAPMV61A )
You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
This user exit is also used in order processing.
Routine USEREXIT_FIELD_MODIFIC_KOPF
IncludeMV61AFZB (SAPMV61A)
You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
Routine USEREXIT_FIELD_MODIFIC_LEER
IncludeMV61AFZB (SAPMV61A )
You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
Routine USEREXIT_PRICING_CHECK
IncludeMV61AFZA (SAPMV61 )
You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
Routine USEREXIT_PRICING_RULE
IncludeRV61AFZA (SAPLV61A )
In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
Routine USEREXIT_CHANGE_PRICING_RULE
IncludeMV61AFZA (SAPMV61A)
You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
Routine USEREXIT_XKOMV_BEWERTEN_INIT
IncludeRV61AFZB (SAPLV61A )
This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
Routine USEREXIT_XKOMV_BEWERTEN_END
SAPLV61A
IncludeRV61AFZB
Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
Routine USEREXIT_XKOMV_ERGAENZEN
SAPLV61A
IncludeRV61AFZB
In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
Routine USEREXIT_XKOMV_ERGAENZEN_MANU
SAPLV61A
IncludeRV61AFZB
You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
Routine USEREXIT_XKOMV_FUELLEN
SAPLV61A
IncludeRV61AFZB
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
Routine USEREXIT_XKOMV_FUELLEN_O_KONP
SAPLV61A
IncludeRV61AFZB
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
Routine USEREXIT_PRICING_COPY
SAPLV61A
IncludeRV61AFZA
You can change the KONV fields for copied price components.
Note: as of Release 4.6A, the display of the condition screen (screen 6201) has been converted from a full screen to a subscreen. The full screen is included in the SAPMV61A module pool, the subscreen, however, in program SAPLV69A. Therefore, instead of MV61AFZA and MV61AFZB, the user exits in LV69AFZZ should be used. For reference, see OSS note 313569.