Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

USER EXIT for transaction VA01 while update in second screen

Former Member
0 Kudos

HI all,

Can any one tell what is the user exit used while udating in second screen ie by changing the price for condition type and then updating. So while updating i want to know which is user exit available.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Write the code in MV45AFZZ Include and below are form routines

----


  • FORM USEREXIT_PRICING_PREPARE_TKOMK *

----


  • This userexit can be used to move additional fields into the *

  • communication table which is used for pricing: *

  • *

  • TKOMK for header fields *

  • *

  • This form is called from form PREISFINDUNG_VORBEREITEN. *

  • *

----


FORM USEREXIT_PRICING_PREPARE_TKOMK.

  • TKOMK-zzfield = xxxx-zzfield2.

*{ INSERT DEVK904950 1

  • TKOMK-PRCTR = '0000002201'.

*} INSERT

ENDFORM.

*eject

----


  • FORM USEREXIT_PRICING_PREPARE_TKOMP *

----


  • This userexit can be used to move additional fields into the *

  • communication table which is used for pricing: *

  • *

  • TKOMP for item fields *

  • *

  • This form is called from form PREISFINDUNG_VORBEREITEN. *

  • *

----


FORM USEREXIT_PRICING_PREPARE_TKOMP.

  • TKOMP-zzfield = xxxx-zzfield2.

ENDFORM.

*eject

3 REPLIES 3

Former Member
0 Kudos

Write the code in MV45AFZZ Include and below are form routines

----


  • FORM USEREXIT_PRICING_PREPARE_TKOMK *

----


  • This userexit can be used to move additional fields into the *

  • communication table which is used for pricing: *

  • *

  • TKOMK for header fields *

  • *

  • This form is called from form PREISFINDUNG_VORBEREITEN. *

  • *

----


FORM USEREXIT_PRICING_PREPARE_TKOMK.

  • TKOMK-zzfield = xxxx-zzfield2.

*{ INSERT DEVK904950 1

  • TKOMK-PRCTR = '0000002201'.

*} INSERT

ENDFORM.

*eject

----


  • FORM USEREXIT_PRICING_PREPARE_TKOMP *

----


  • This userexit can be used to move additional fields into the *

  • communication table which is used for pricing: *

  • *

  • TKOMP for item fields *

  • *

  • This form is called from form PREISFINDUNG_VORBEREITEN. *

  • *

----


FORM USEREXIT_PRICING_PREPARE_TKOMP.

  • TKOMP-zzfield = xxxx-zzfield2.

ENDFORM.

*eject

Former Member
0 Kudos

Hi

Use the Include program MV45AFZZ of the sales order main Program SAPMV45A

in that use the Pricing related PERFORM ..FORM.

FORM USEREXIT_PRICING_PREPARE_TKOMK.

FORM USEREXIT_PRICING_PREPARE_TKOMP.

take the access key and write the code in these forms and check by keeping a break-point, whether it is triggering or not.

Reward points for useful Answers

Regards

Anji

Former Member
0 Kudos

Hi,

User exits in the program MV45AFZZ

The user exits which you can use for modifications in sales document processing are listed below.

• USEREXIT_DELETE_DOCUMENT

This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.

For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.

The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.

• USEREXIT_FIELD_MODIFICATION

This user exit can be used to modify the attributes of the screen fields.

To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.

The usage of the field groups (modification group 1-4) is as follows:

• Modification group 1: Automatic modification with transaction MFAW

• Modification group 2: It contains 'LOO' for step loop fields

• Modification group 3: For modifications which depend on check tables or on other fixed information

• Modification group 4: is not used

The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.

This FORM routine is called up by the module FELDAUSWAHL.

See the Screen Painter manual for further information on structuring the interface.

• USEREXIT_MOVE_FIELD_TO_VBAK

Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".

The user exit is called up at the end of the FORM routine VBAK_FUELLEN.

• USEREXIT_MOVE_FIELD_TO_VBAP

Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".

The user exit is called up at the end of the FORM routine VBAP_FUELLEN.

• USEREXIT_MOVE_FIELD_TO_VBEP

Use this user exit to assign values to new fields at the level of the sales document schedule lines.

The user exit is called up at the end of the FORM routine VBEP_FUELLEN.

• USEREXIT_MOVE_FIELD_TO_VBKD

Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document" .

The user exit is called up at the end of the FORM routine VBKD_FUELLEN.

• USEREXIT_NUMBER_RANGE

Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.

The user exit is called up in the FORM routine BELEG_SICHERN.

• USEREXIT_PRICING_PREPARE_TKOMK

Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.

• USEREXIT_PRICING_PREPARE_TKOMP

Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.

• USEREXIT_READ_DOCUMENT

You use this user exit if further additional tables are to be read when importing TA01 or TA02.

The user exit is called up at the end of the FORM routine BELEG_LESEN.

• USEREXIT_SAVE_DOCUMENT

Use this user exit to fill user-specific statistics update tables.

The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.

Note

If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.

• USEREXIT_SAVE_DOCUMENT_PREPARE

Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.

The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.

User exits in the program MV45AFZA

• USEREXIT_MOVE_FIELD_TO_KOMKD

Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination" .

• USEREXIT_MOVE_FIELD_TO_KOMPD

Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination ".

• USEREXIT_MOVE_FIELD_TO_KOMKG

Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".

• USEREXIT_MOVE_FIELD_TO_KOMPG

Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".

• USEREXIT_REFRESH_DOCUMENT

With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.

For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.

The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.

The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.

Regards