Application Development and Automation 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: 
Read only

User exit for VA02

Former Member
0 Likes
2,960

Hi,

I have a Z table which maintains all blocks(billing,dunning,delivery) for the sales order.I need to insert the data from VA02 into my Ztable if at all anyone creates or changes the block in the transaction VA02 or VA01.Can anyone suggest me which user exit i can use.

Thanks in advance.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,457

Hi,

for future purpose create one program, copy the below code and execute, it will ask the Tcode there enter the Tcode for which you want to find the user exits and then execute, it will displays all the user exits related to that Tcode.

TABLES : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.

TABLES : tstct.

DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.

DATA : field1(30).

DATA : v_devclass LIKE tadir-devclass.

PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.

SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.

IF sy-subrc EQ 0.

SELECT SINGLE * FROM tadir WHERE pgmid = 'R3TR'

AND object = 'PROG'

AND obj_name = tstc-pgmna.

MOVE : tadir-devclass TO v_devclass.

IF sy-subrc NE 0.

SELECT SINGLE * FROM trdir WHERE name = tstc-pgmna.

IF trdir-subc EQ 'F'.

SELECT SINGLE * FROM tfdir WHERE pname = tstc-pgmna.

SELECT SINGLE * FROM enlfdir WHERE funcname = tfdir-funcname.

SELECT SINGLE * FROM tadir WHERE pgmid = 'R3TR'

AND object = 'FUGR'

AND obj_name EQ enlfdir-area.

MOVE : tadir-devclass TO v_devclass.

ENDIF.

ENDIF.

SELECT * FROM tadir INTO TABLE jtab

WHERE pgmid = 'R3TR'

AND object = 'SMOD'

AND devclass = v_devclass.

SELECT SINGLE * FROM tstct WHERE sprsl EQ sy-langu AND

tcode EQ p_tcode.

FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.

WRITE : 'Transaction Code - ',

20(20) p_tcode,

45(50) tstct-ttext.

SKIP.

IF NOT jtab[] IS INITIAL.

WRITE sy-uline.

FORMAT COLOR COL_HEADING INTENSIFIED ON.

WRITE:/1 sy-vline,

2 'Exit Name',

21 sy-vline ,

22 'Description',

95 sy-vline.

WRITE : sy-uline.

LOOP AT jtab.

SELECT SINGLE * FROM modsapt

WHERE sprsl = sy-langu AND

name = jtab-obj_name.

FORMAT COLOR COL_NORMAL INTENSIFIED OFF.

WRITE:/1 sy-vline,

2 jtab-obj_name HOTSPOT ON,

21 sy-vline ,

22 modsapt-modtext,

95 sy-vline.

ENDLOOP.

WRITE : sy-uline.

DESCRIBE TABLE jtab.

SKIP.

FORMAT COLOR COL_TOTAL INTENSIFIED ON.

WRITE:/ 'No of Exits:' , sy-tfill.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE : 'No User Exit exists'.

ENDIF.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE : 'Transaction Code Does Not Exist'.

ENDIF.

AT LINE-SELECTION.

GET CURSOR FIELD field1.

CHECK field1(4) EQ 'JTAB'.

SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).

CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.

Reward if useful.

Thanks,

Sreeram.

7 REPLIES 7
Read only

former_member386202
Active Contributor
0 Likes
1,457

Hi,

Exits for VA02

SDAPO001 Activating Sourcing Subitem Quantity Propagation

SDTRM001 Reschedule schedule lines without a new ATP check

V45A0001 Determine alternative materials for product selection

V45A0002 Predefine sold-to party in sales document

V45A0003 Collector for customer function modulpool MV45A

V45A0004 Copy packing proposal

V45E0001 Update the purchase order from the sales order

V45E0002 Data transfer in procurement elements (PRreq., assembly)

V45L0001 SD component supplier processing (customer enhancements)

V45P0001 SD customer function for cross-company code sales

V45S0001 Update sales document from configuration

V45S0003 MRP-relevance for incomplete configuration

V45S0004 Effectivity type in sales order

V45W0001 SD Service Management: Forward Contract Data to Item

V46H0001 SD Customer functions for resource-related billing

V60F0001 SD Billing plan (customer enhancement) diff. to billing plan

Regards,

Prashant

Read only

Former Member
0 Likes
1,457

Hi,

USe MV45AFZZ user exit, in write the code in save subroutine.

regards,

Santosh Thorat

Read only

Former Member
0 Likes
1,457

Enhancement Description

USEREXIT_CHANGE_SALES_ORDER In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).

USEREXIT_CHECK_VBAK This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.

USEREXIT_CHECK_VBAP This user exit can be used to carry out additional checks (e.g. for completion) at item level.

USEREXIT_CHECK_VBEP This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line.

USEREXIT_CHECK_VBKD The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.

USEREXIT_CHECK_VBSN You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.

USEREXIT_CHECK_XVBAP_FOR_DELET In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).

USEREXIT_CHECK_XVBEP_FOR_DELET In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).

USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).

USEREXIT_COBL_RECEIVE_VBAK Option to assign values from the document header to the new fields.

USEREXIT_COBL_RECEIVE_VBAP Option to supply values from the item to the new fields.

USEREXIT_COBL_SEND_HEADER A changed field can be copied from the structure to the header (see source text MV45AFZB)

USEREXIT_COBL_SEND_ITEM A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).

USEREXIT_CUST_MATERIAL_READ You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)

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.

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

USEREXIT_FILL_VBAP_FROM_HVBAP You can use this user exit to fill additional fields in the sub-item with data from the main item.

USEREXIT_MOVE_FIELD_TO_COBL Option to include new fields in structure COBL.

USEREXIT_MOVE_FIELD_TO_KOMKH You can use this user exit to include new fields for batch determination (document header).

USEREXIT_MOVE_FIELD_TO_KOMPH You can use this user exit to include new fields for batch determination (document item).

USEREXIT_MOVE_FIELD_TO_ME_REQ "With this user exit you can include additional fields for the following fields:

• EBAN (purchase requisition)

• EBKN (purchase requisition-account assignment)

• USEREXIT_GET_FIELD_FROM_SDCOM"

USEREXIT_MOVE_FIELD_TO_TVCOM_H You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.

USEREXIT_MOVE_FIELD_TO_TVCOM_I You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.

USEREXIT_MOVE_FIELD_TO_VBAK Use this user exit to assign values to new fields at sales document header level.

USEREXIT_MOVE_FIELD_TO_VBAKKOM Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)

USEREXIT_MOVE_FIELD_TO_VBAP Use this user exit to assign values to new fields at sales document item level

USEREXIT_MOVE_FIELD_TO_VBAPKOM Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)

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

USEREXIT_MOVE_FIELD_TO_VBEPKOM Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)

USEREXIT_MOVE_FIELD_TO_VBKD Use this user exit to assign values to new fields for business data of the sales document

USEREXIT_MOVE_FIELD_TO_VBSN You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).

USEREXIT_MOVE_WORKAREA_TO_SDWA You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.

USEREXIT_NEW_PRICING_VBAP Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.

USEREXIT_NEW_PRICING_VBKD Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.

USEREXIT_NUMBER_RANGE user exit to define the number ranges for internal document number assignment depending on the required fields

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.

USEREXIT_SAVE_DOCUMENT_PREPARE Use this user exit to make certain changes or checks immediately before saving a document.

USEREXIT_SET_STATUS_VBUK In this user exit you can you can store a specification for the reserve fields in VBUK (header status).

USEREXIT_SET_STATUS_VBUP In this user exit you can you can store a specification for the reserve fields for VBUP (item status).

USEREXIT_SOURCE_DETERMINATION You can use this user exit to determine which plant will be used for the delivery

USEREXIT_STATUS_VBUK_INVOICE You can use this user exit to influence billing status at header level.

SDAPO001 Activating Sourcing Subitem Quantity Propagation

SDTRM001 Reschedule schedule lines without a new ATP check

V45A0001 Determine alternative materials for product selection

V45A0002 Predefine sold-to party in sales document

V45A0003 Collector for customer function modulpool MV45A

V45A0003 Collector for customer function modulpool MV45A

V45A0004 Copy packing proposal

V45E0001 Update the purchase order from the sales order

V45E0002 Data transfer in procurement elements (PRreq., assembly)

V45L0001 SD component supplier processing (customer enhancements)

V45L0001 SD component supplier processing (customer enhancements)

V45L0001 SD component supplier processing (customer enhancements)

V45L0001 SD component supplier processing (customer enhancements)

V45L0001 SD component supplier processing (customer enhancements)

V45L0001 SD component supplier processing (customer enhancements)

V45L0001 SD component supplier processing (customer enhancements)

V45P0001 SD customer function for cross-company code sales

V45S0001 Update sales document from configuration

V45S0003 MRP-relevance for incomplete configuration

V45S0003 MRP-relevance for incomplete configuration

V45S0004 Effectivity type in sales order

V45W0001 SD Service Management: Forward Contract Data to Item

V46H0001 SD Customer functions for resource-related billing

V46H0001 SD Customer functions for resource-related billing

V60F0001 SD Billing plan (customer enhancement) diff. to billing plan

SDVFX001 User exit header line in delivery to accounting

SDVFX002 User exit for A/R line (transfer to accounting)

SDVFX003 User exit: Cash clearing (transfer to accounting)

SDVFX004 User exit: G/L line (transfer to accounting)

SDVFX005 User exit: Reserves (transfer to accounting)

SDVFX006 User exit: Tax line (transfer to accounting)

SDVFX007 User exit: Billing plan during transfer to Accounting

SDVFX008 User exit: Processing of transfer structures SD-FI

SDVFX009 Billing doc. processing KIDONO (payment reference number)

SDVFX010 User exit item table for the customer lines

SDVFX011 Userexit for the komkcv- and kompcv-structures

V05I0001 User exits for billing index

V05I0001 User exits for billing index

V05I0001 User exits for billing index

V05I0001 User exits for billing index

V05N0001 User Exits for Printing Billing Docs. using POR Procedure

V05N0001 User Exits for Printing Billing Docs. using POR Procedure

V05N0001 User Exits for Printing Billing Docs. using POR Procedure

V60A0001 Customer functions in the billing document

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V60P0001 Data provision for additional fields for display in lists

V61A0001 Customer enhancement: Pricing

V02V0001 Sales area determination for stock transport order

V02V0002 User exit for storage location determination

V02V0003 User exit for gate + matl staging area determination (headr)

V02V0004 User Exit for Staging Area Determination (Item)

V50PSTAT Delivery: Item Status Calculation

V50Q0001 Delivery Monitor: User Exits for Filling Display Fields

V50Q0001 Delivery Monitor: User Exits for Filling Display Fields

V50R0001 Collective processing for delivery creation

V50R0002 Collective processing for delivery creation

V50R0004 Calculation of Stock for POs for Shipping Due Date List

V50S0001 User Exits for Delivery Processing

V50S0001 User Exits for Delivery Processing

V53C0001 Rough workload calculation in time per item

V53C0002 W&S: RWE enhancement - shipping material type/time slot

V53W0001 User exits for creating picking waves

V53W0001 User exits for creating picking waves

V53W0001 User exits for creating picking waves

VMDE0001 Shipping Interface: Error Handling - Inbound IDoc

VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)

VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)

VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)

SDQUX001 User exit: SD product allocation processing, extended checks

SDQUX002 SD product allocation processing, change schedule line

SDQUX003 User-Exit : SD Product allocation, extended checks (ATP)

SDQUX004 Product Allocations: Change the Product Allocation Steps

SDQUX005 Product Allocations: Adjust product allocation quantities

SDVAX001 Determine Billing Plan Type

V09A0001 Reference/duplicate decision making manual address

V09A0002 Partner type KU EXIT for NO_KNVV

Reward points if found helpful...

Cheers,

Chandra Sekhar.

Read only

Former Member
0 Likes
1,458

Hi,

for future purpose create one program, copy the below code and execute, it will ask the Tcode there enter the Tcode for which you want to find the user exits and then execute, it will displays all the user exits related to that Tcode.

TABLES : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.

TABLES : tstct.

DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.

DATA : field1(30).

DATA : v_devclass LIKE tadir-devclass.

PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.

SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.

IF sy-subrc EQ 0.

SELECT SINGLE * FROM tadir WHERE pgmid = 'R3TR'

AND object = 'PROG'

AND obj_name = tstc-pgmna.

MOVE : tadir-devclass TO v_devclass.

IF sy-subrc NE 0.

SELECT SINGLE * FROM trdir WHERE name = tstc-pgmna.

IF trdir-subc EQ 'F'.

SELECT SINGLE * FROM tfdir WHERE pname = tstc-pgmna.

SELECT SINGLE * FROM enlfdir WHERE funcname = tfdir-funcname.

SELECT SINGLE * FROM tadir WHERE pgmid = 'R3TR'

AND object = 'FUGR'

AND obj_name EQ enlfdir-area.

MOVE : tadir-devclass TO v_devclass.

ENDIF.

ENDIF.

SELECT * FROM tadir INTO TABLE jtab

WHERE pgmid = 'R3TR'

AND object = 'SMOD'

AND devclass = v_devclass.

SELECT SINGLE * FROM tstct WHERE sprsl EQ sy-langu AND

tcode EQ p_tcode.

FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.

WRITE : 'Transaction Code - ',

20(20) p_tcode,

45(50) tstct-ttext.

SKIP.

IF NOT jtab[] IS INITIAL.

WRITE sy-uline.

FORMAT COLOR COL_HEADING INTENSIFIED ON.

WRITE:/1 sy-vline,

2 'Exit Name',

21 sy-vline ,

22 'Description',

95 sy-vline.

WRITE : sy-uline.

LOOP AT jtab.

SELECT SINGLE * FROM modsapt

WHERE sprsl = sy-langu AND

name = jtab-obj_name.

FORMAT COLOR COL_NORMAL INTENSIFIED OFF.

WRITE:/1 sy-vline,

2 jtab-obj_name HOTSPOT ON,

21 sy-vline ,

22 modsapt-modtext,

95 sy-vline.

ENDLOOP.

WRITE : sy-uline.

DESCRIBE TABLE jtab.

SKIP.

FORMAT COLOR COL_TOTAL INTENSIFIED ON.

WRITE:/ 'No of Exits:' , sy-tfill.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE : 'No User Exit exists'.

ENDIF.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE : 'Transaction Code Does Not Exist'.

ENDIF.

AT LINE-SELECTION.

GET CURSOR FIELD field1.

CHECK field1(4) EQ 'JTAB'.

SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).

CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.

Reward if useful.

Thanks,

Sreeram.

Read only

Former Member
0 Likes
1,457

Hi,

go to the program SAPMV45A, in that program go to include MV45AFZZ there you can find subroutine "FORM userexit_field_modification.", in that you can write your own code to enter the entries into you ZTABLE.

Reward if useful.

Thanks,

Sreeram.

Read only

Former Member
0 Likes
1,457

Hi Sir,

Please do reward if useful.

Thankx.

SDAPO001 Activating Sourcing Subitem Quantity Propagation

SDTRM001 Reschedule schedule lines without a new ATP check

V45A0001 Determine alternative materials for product selection

V45A0002 Predefine sold-to party in sales document

V45A0003 Collector for customer function modulpool MV45A

V45A0004 Copy packing proposal

V45E0001 Update the purchase order from the sales order

V45E0002 Data transfer in procurement elements (PRreq., assembly)

V45L0001 SD component supplier processing (customer enhancements)

V45P0001 SD customer function for cross-company code sales

V45S0001 Update sales document from configuration

V45S0003 MRP-relevance for incomplete configuration

V45S0004 Effectivity type in sales order

V45W0001 SD Service Management: Forward Contract Data to Item

V46H0001 SD Customer functions for resource-related billing

V60F0001 SD Billing plan (customer enhancement) diff. to billing plan

Read only

Former Member
0 Likes
1,457

if anyone changes or creates you want to update. Means at the time of saving the order you want to trigger that logic. So, write the logic in USEREXIT_SAVE_DOCUMENT for the transaction type change and creation.