1 Reply Latest reply: Apr 10, 2007 1:16 AM by Biju Thantry

BAdI for SD Pricing This question is Assumed Answered.

Ben Axelrad Apr 9, 2007 10:34 PM Hi,

 

I am investigating various user-exits and special functionality for SD pricing.  I don't have any special customer requirements yet, but would like to expand my bag of tricks.

 

I came across these two BAdIs.

 

SD_COND_ACCESS_A     Access in Pricing (replacement) 

SD_COND_SAVE_A       Save condition application A, E 

 

Does anyone have experience with them?  In what types of situations would they be used?

 

Thanks,

Ben

1130 Views

Average User Rating(0 ratings)

Re: BAdI for SD Pricing

Biju Thantry Apr 10, 2007 1:16 AM (in response to Ben Axelrad)

Hi Ben,

 

Iam not sure what these BADIs are used for but defenitely you could go thru the following user exits...for price

determinations...

Iam sure one of them can easily satisfy any of the buisness requirements...and you could include a small routine to

satisfy your buisness needs...

 

reward points if it helps

 

regards

Biju

 

 

 

USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ) 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.

 

USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ) 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.

 

USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA) 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.

USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB) 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.

 

USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB) 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.

 

USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB) 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.

 

USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA) You can install additional checks to

the standard checks of condition lines (e.g. maximum/minimum value).

 

USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA) 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.

 

USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA) You can use this user exit

to change the pricing type that has been predefined in the copying control table in billing.

 

USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB) This field is used in the

formulas and therefore initialized before the loop for the pricing procedure starts.

 

USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB) Within a loop for the price

components during pricing, specific values can be transferred into the communication structures in pricing to be

further processed.

 

USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB) 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).

 

USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB) 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.

 

USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB) 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.

 

USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB) 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.

 

USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA) You can change the KONV fields for

copied price components