Field exit for VA02 / for GOTO- HEADER- SHIPPING

Hello ,
Please help me out with field exit for GOTO->HEADER->SHIPPING in VA02 transaction .
I have to check if the shipping condition enetered against values in TVARV variable .
If unequal i need to display a warining messge .
But the requirement is it needs to be checked against field exit .
Thanks ,
Rahul

Dear Sheo
I know OMJN can set the material Slip mandatory. but my question is how to seperate by company code.
for example:
company code D001 mandatory
company code D002 Input
regards,
Yang

Similar Messages

Field exits dont work for ENJOY trx

HI All,
May I know why field exits do not work for ENJOY transction codes.
Is this same case with User exits and screen exits??
Please make me clear on this.
Satish

I guess field exits have been removed in the recent versions and enjoy transactions are the latest one, SAP has not incorporated the same.
However, user exits will work with all transactions in the latest versions as well.
regards,
Ravi
Note : Please mark all the helpful answers

User Exit in VA02 for Warranty Status field change

Hi Gurus,
Can any one pls suggest the user exit that gets trigerred when there is a Warranty Status Field change in the Repair Order of Order type ZRAS and when the change occurs it has to update the work center of the Corresponding Service Order.
Pls help me with this issue.
Regards,
VIJAYB.

Transaction Code - VA02                     Change Sales Order
Enhancement/ Business Add-in            Description
Enhancement
V60F0001                                SD Billing plan (customer enhancement) diff. to billing plan
V46H0001                                SD Customer functions for resource-related billing
V45W0001                                SD Service Management: Forward Contract Data to Item
V45S0004                                Effectivity type in sales order
V45S0003                                MRP-relevance for incomplete configuration
V45S0001                                Update sales document from configuration
V45P0001                                SD customer function for cross-company code sales
V45L0001                                SD component supplier processing (customer enhancements)
V45E0002                                Data transfer in procurement elements (PRreq., assembly)
V45E0001                                Update the purchase order from the sales order
V45A0004                                Copy packing proposal
V45A0003                                Collector for customer function modulpool MV45A
V45A0002                                Predefine sold-to party in sales document
V45A0001                                Determine alternative materials for product selection
SDTRM001                                Reschedule schedule lines without a new ATP check
Business Add-in
BADI_SD_SCH_GETWAGFZ                    Scheduling Agreement: Read WAGFZ from S073
BADI_SD_V46H0001                        SD Customer functions for resource-related billing
No.of Exits:         15
No.of BADis:          2

Field Exit or User Exit for Maintenance Order field.

Dear All,
we need an field exit or an user exit for order(AUFNR)field in PM module.
The Client wants that the value of this field should be validated and for certaion condition an error message should be given while saving an invoice for this order.
Kindly provide the user exit ..
Its urgent.
Thansk in advance ..
regards
Ajay.

Implement Field Exit within program
For this example I am using dta element 'EBELN' from table EKKO.
Step 1: Execute program 'RSMODPRF', entering the data element of the field
Step 2:Create function module when prompted, and add you code to the source section using the parameter 'INPUT' as the field value you are checking
Step 3:      Save and activate Function and execute transaction 'CMOD'.
Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
Step 3:      Save and activate Function and execute transaction 'CMOD'.
Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
Step 5:      Enter data element
Step 6:      Save and activate
Step 7: Execute program 'RSMODPRF' again but this time leave data element field blank. Step 8: Select the checkbox for the data element you have just created and choose option: Field exit->Activate This will now be active for all instances of this data element, but you can assign specific program and screen combinations by pressing the 'Assign prog./screen' button. You can also change the code you entered in the field exit function module by pressing the 'Edit FM' button.
regards
vinod

Field Exit for Batch Input creation from LSMW

Hi all,
I am having problems getting a field exit to work for validation of user id in the "Create Batch Input Session" step of LSMW.
Program: /SAPDMC/SAP_LSMW_BI_RECORDING
Screen: 1000
Data Element: SYUNAME
Any help would be appreciated.
Regards,
Jason
Message was edited by: Jason Lante

Field exits are not supported after 4.6 yes, but they still work. I found the reason why my field exit wasn't working; it related to the fact that the field I am applying it to is not directly related to a dictionary object. Meaning I cannot apply a field exit.
So my question now is what other ways are there to enhance LSMW?
Regards,
Jason

Is there any BADI or any other alternate in ECC for the Field exits

Hi guys,
Is there any BADI or any other alternate in ECC for the Field exits:
FIELD_EXIT_BP_VERS_Z
FIELD_EXIT_BP_VERSION

Hi,
If you are aware that these are the field exit funciton modules that get created when you create a field exit for the corresponding data element.
Hence there will not be any replacement for this FM, But you need to find where the data element is triggering(the tcode) and check in debugging if there is any BADI/Enhancement Point.
Hence check for which data element the FM belong to using the program RSMODPRF and check if they are globally activated, then they trigger on all the screen/transactions..(Tedious to replace with BADi/Enhancemnet points everywherre)
If the field exit is activated for screens, check to which transaction the screens belong to and then check for enhancement point or badi that trigers on the screen..
Hope this helps
Regards
Shiva

Now a simple question of Field exit.

well, im really very glad because my last post was a success and i can solve de problem!!!!thank you all...
this time i need in the VF01 on one field ('Reference'/Xblnr), when the user press save, to show some popup allowing entry data, so the user may choose some keys from a Ztable that i have to create, and then continue saving.
May i use a field exit for this?what steps shall i follow to activate a field exit and put my code?
Note: there isn't an User exit that appear in the moment i need, the one i asked in my last post doesn't work for this and any of the others finded in ZFindexit. when i'm debugging <b>'perform userexit_pricing_prepare_tkomk' </b>
appeared, is this an User exit? inside this perform i have changed manually while debugging the field i need and the proccess ended OK. how can i activate this exit?
well, i'm sure that someone know the asnwer....
i'll be very glad with the ones who can help me!!!!
and i'll give points in rewards for those who help me as a gratefulness of my part...
i'm waiting your help, thank in advance....

Hi andrew,
you will have a standard program RSMODPRF for field exits.
Execute that program and create a a field exit(function module) for 'XBLNR' giving the data element of XBLNR and number of the field exit as inputs.
There you can write the related code...
Hope this helps you.
Regards,
Vinod.

Regarding field exit

hi guru
my requirement is that i want to change a predefined field lenth 9 character. to 12 character. how can i do it.
please help me.

hI
ABAP DICTIONARY
Field Exits:
     Field exits take you from a screen field with a data element reference to a function module. Field exits can be either global or local.
Field exit function modules adhere to the following naming convention:
prefix:     FIELD_EXIT_
name:     <data element name>_
suffix (optional):     0 to 9, A to Z
Global field exits are not limited to a particular screen. If a global field exit's data element is used on multiple screens, you will branch to a function module from all of these screens once the exit has been activated. Here you can, for example, edit the contents, force a new entry to be made by outputting an error message, or prohibit certain users from proceeding further.
Local field exits are valid for one screen only. If you assign a screen from a specific program to the data element, then you will only branch to a function module from this screen once the exit has been activated. To be able to allow different functionality on different screens referring to the same data element, you can assign exit numbers to data elements. Each exit number refers to a different function module.
prefix:     FIELD_EXIT_
name:     <data element name>_
suffix (optional):     0 to 9, A to Z
   Field Exits It is triggered at field level.
      It is attached at data element
     Specific to one screen only or to all the screen where field appears.
     Field exit is not allowed in SAP version 4.7 and above .
Example with screen shots for consultants working in
SAP V 4.6 below version.

Ship-to-party field in display mode in TC va02 for some users.

Hi Sap Gurus,
My client requirement is this ,he wants the ship-to-party field in TC Va02 to be in display mode for some lower level user and at the same time she wants the ship-to-party field for higher level users to be editable.
Can anybody tell me how to do this .Va02 TC will be given to lower level users where they will be able to edit other fields except ship-to-party.
Thanks N Regards,
Siddhartha

Hello Siddhartha ji,
I think you can proceed in this way:-
Create TCode zva02 by copying from VA02 .
Then Create Screen Variant and assign that screen variant to transaction variant .
Then Create Variant Group for that Tcode and then assign this variant group to those particular users.
Even you can proceed with out creating the ZVA02 Tcode.
All Will be done in SHD0 TCode.
@ others :- i am basicaly into ABAP...so I may be wrong...pls Help him out ..
Regards,
jeevan kumar Medimi.

User exit for Pop-Up text Header Note II for transactions VA02 and VA03

Hi ,
Need new user exit to call text pop-up functionality (used in standard at sales order creation) when modifying or displaying a sales order (VA02 / VA03)
Text ID: ZX02
Text Object: VBBK
Text procedure: X1
Access sequence: 6002
Text is always shown at creation if exists for the SOLD-TO in the sold-to language, and is defined in customizing as to be displayed : V_TTXER_N-TXPFL = 'Y' or 'Z'
This is checked in RV_TEXT_COPY
NOTE: Present while creating the sales order , popup is coming to add the text.Same pop up required for VA02/VA03 transaction.
Reason: all orders are entered via EDI . In these cases the info from the text is not displayed.
Pl. let me know the user exit for above requirement.
Moderator message: please do your own research before asking.
Edited by: Thomas Zloch on Jan 13, 2011 1:50 PM

How do you know "ECOM Order"?
What constitutes a "HOLD"?
I'd do something like:
In USEREXIT_SAVE_DOCUMENT_PREPARE (SAVE has been pressed at this point and SAVE_DOCUMENT is to fire off other processes, etc).
IF sy-tcode eq 'VA01' or sy-tcode eq 'VA02'.
if vbak-something (identify your ECOM order)
loop at vbap transporting no fields (Think it's back to VBAP at this point)
where... (look for your hold indicator in every row)
endloop.
if sy-subrc eq 0. "found the hold
message innn(class) display like 'E'.
endif.
endif.
endif.
Be VERY careful with ANYTHING that you put into SAVE_DOCUMENT exit form.

Screen exit for me32k for header and for items

hi experts,
i need a screen exit from me32k to add subscreen in :
1. items
2. header
thanks in advanced,
dana.

Hi,
Just some information on screen exits:
Screen Exit:
How to implement screen exit for a SAP standard transaction
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
User Exits:
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
To find a Exit.
Goto Transaction -- Find The Package
SMOD >f4>Use the Package here to Find the Exits In the Package.
Else if you Want to search by Application Area wise ,
There is one more tab to find the Exits in the Respective Application Area.
Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
Now Run ur Transaction to Check if it Triggers.
Thats it..
Suppose you need to find out all the user exits related to a tcode.
1. Execute the Tcode.
2. Open the SAP program.
3. Get the Development Class.
4. Execute Tcode SE84.
5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
6. Enter the Development class and execute.
Check out this thread..
The specified item was not found.
1. Type the transaction : system->status-> <PROG. NAME>
2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
3. Open CMOD utilities->SAP enhancements
EDIT->All selections
4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
5. The displayed list contains the enhancements names for the transaction You were looking for.
6. Create a project in CMOD and the code in default include->activate.
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.planetsap.com/userexit_main_page.htm
User-Exits
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/ab038.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.sap-basis-abap.com/sapab013.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
These links will help you to learn more on user exits.
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.allsaplinks.com/user_exit.html
www.sap-img.com/abap/what-is-user-exits.htm
Also please check these threads for more details about user exits.
Re: Screen exit
user exit and customer exit
user exit
1. Document on UserExits in FI/CO
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
2. Finding User Exits...
http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
3. List of all User Exits...
http://www.planetsap.com/userexit_main_page.htm
Reward if found helpfull,
Cheers,
Chaitanya.

Screen exit for VA02

HI SAP Gurus,
I have a scenario where client wants a popup screen everytime user tries to save the field IHREZ (Your reference) field in transaction va02..The screen will contain various database fields including the following
Unit# , Service Order #,
Material#,
Material description ,
Qty ,
Cost ,
Markup factor ( From Z factor table),
Sales Price,
All the field are display fields except for markup factor which is a field from a ztable.The number of line items can be 200.Sales price will be calculated as
qtycostmarkup factor
There are two additional fields Labour and Hours which are to be entered by the user and then some calculation will be done to get the total price invested in repairing.This total price should be updated in a custom condition pricing for repair.
i have been suggested
To trigger the pop-up screen, use user exit MV45AFZZ, Form
USEREXIT_MOVE_FIELD_TO_VBKD.
But I have doubts like as what to use screen painter or there is some standard function module to call a popup.PLease suggest all the possible solution which i can look into.
Thanks in advance.
points will be rewarded to all the relevant answers
thanks
twinkle

Hi,
Pls do not enter the fields as header data it has restriction of only two fields.
These all r the possible user exits on VA02, Just go thru it ..
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
Maybe you can use subroutine USEREXIT_MOVE_FIELD_TO_VBSN in MV45AFZB.
Pls reward helpful points.
Regards,
Ameet

Transaction variant for VA02 is not working for few fields

Hi All,
I have created a transaction variant for VA02. Made the necessary code changes for populating the variant name in MV45AFZZ. It is working fine for all the screens and all the fields except for second screen of VA02.
First screen - Enter sales order number.
Second screen - Overview screen.
In second screen, I have disabled all the screen fields. When I run the variant, all fields are disabled except sold-to party, ship-to party and create sold to party ICON. All these fields belongs to screen 4701.
In the transaction variant I can see that these fields screen attributes set to output only. I don't see anything different for these fields compared to other fields.
First I thought it is because of mandatory fields. But some other mandatory fields are disabled after my changes. Why is this happening only for these 3 fields (Only for screen 4701 I can say).
Surprisingly, if I do any action like enter/select other tab, these fields are getting disabled.
Your inputs on this are highly appriciated.
Thanks,
Vinod.
Edited by: Vinod Kumar Vemuru on Dec 31, 2009 10:01 AM

Thanks, happy to see the reply.
But I have given the correct names as suggested by you.
I have also created a Transaction ZVA02 as i dont want this variant to be applied on standard VA02.
It is working on first screen but not on subsequent screens. Am i missing something, some link or activation?
Transaction Code VA02                  Change Sales Order
Transaction Variant ZTRN_VA02                       testing
ZTRN_VA02_0102                                        SAPMV45A     102
ZTRN_VA02_4001                                        SAPMV45A     4001
ZTRN_VA02_4021                                        SAPMV45A     4021
ZTRN_VA02_4050                                        SAPMV45A     4050
ZTRN_VA02_4401                                        SAPMV45A     4401
ZTRN_VA02_4701                                        SAPMV45A     4701
ZTRN_VA02_4900                                        SAPMV45A     4900
when I run this the first screen is applied correctly but what happens next.

Field Exit for ME21N & ME22N transactions

HI Friends,
I need to make the SAP Standard screen field "Overdeliv. Tol." & "Unlimited" to inactive under the Item level data --> Delivery tab in ME21N & ME22N transaction.
Can i do ths? If so give me the steps and Screen exit for the same...

For User Exit's
goto to tcode->status->program name->double click on that,
then goto to-> attribute take the package name and
Goto SMOD tcode ->Utilities->give the package name and F8
then a list of exits will display for that tcode as well as that package.
double click on the exit u can see the Fm exit,screen exit,feild exit,include exit. there
u can check the table MODSAP
For BADI's,
1)goto to tcode SE24 give the CL_EXITHANDLER and display and then double click on the GET_INSTANCE
keep Break point at this location 'call method cl_exithandler=>get_class_name_by_interface'
then the tcode it will trigger there and we can debugg there we can find badi'for that tcode and then remove the break point.
2)Goto to tcode->status->program name->double click on that program will display's
then press crtl+F then cl_exithandler
Thank u,
santhosh

Field Exit for VA11 screen ?

Hello Abapers,
I need ur help to find out the field exit available for VA11 screen.
How to find the field exit wht is the procedure?
Thks

Hi Venkateswar,
First you check this link once.,
http://www.****************/Tutorials/ExitsBADIs/MK01/FieldExit.htm
Field exits are frozen on the 4.6C maintenance level and are not further developed. This means that the existing functionality is kept with all restrictions (see also the last item below). Existing exits can be further used and are called at runtime as usual.
Existing exits can be maintained using program RSMODPRF (run the program using transaction SE38). Activation of the field exits and assignment of the dynpros can also be carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank).
If required, new field exits can be created using program
RSMODPRF (see the program documentation).
Please find below the step by step procedure for field exit :-
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
An easy way to determine the data element associated to a particular screen field is to:
Go the appropriate screen.
Position the cursor in the appropriate field.
Press F1 for field-level help.
Click on the Technical info pushbutton (or press F9) on the help dialog box.
On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
Step 2: Go To Field Exit Transaction
The transaction to create field exits is CMOD.
You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
After choosing this menu path, a dialog box will prompt you for the appropriate data element .
Enter the data element name and click the Continue pushbutton.
Now, you will be able to create the function module associated to the data elements field exit.
Step 4: Create Function Module
You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the Continue pushbutton.
In the Function module field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
You can add an identifier (an underscore followed by a single character ).
The first function module for a data elements field exit must be created without an identifier.
To create the function module, click on the Create pushbutton, choose menu path Function module -> Create, or press F5.
After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing Enter, you will be able to go ahead and create the function module.
Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
From the function modules attributes screen, click on the Source code pushbutton or choose the Goto -> Function module menu path to the code of the function module.
Here you will add your desired functionality for the field exit.
Remember that field exits function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
After coding the function module, you must remember to activate it.
Use the Function module -> Activate menu path to activate the function module.
At this point, you can return to the field exit transaction.
You should be able to 'green arrow' back to this transaction.
When you return to the field exit transaction, you will see an entry for the newly created field exit.
At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
This step is only needed if you want to make a field exit local.
To make a field exit local, select the field exit and click on the Assign prog./screen pushbutton.
In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the Fld. Exit field.
If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
The field exit must be active for it to be triggered by the system.
Activate the field exit by choosing the Field exit -> Activate menu path.
After assigning the field exit to a change request, its status will change to Active and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Please reward points if helpful.
Cheers,
Swamy Kunche

Field exit for VA02 / for GOTO- HEADER- SHIPPING

Similar Messages

Maybe you are looking for