Screen exit for JIT call PJ02/PJ03

Hi,
I am new to SAP PP module
In one of my project requirement i have to add 2 new fields to standard exiting screen (PJ02 / PJ03) well I want add at Header level if I can't I would like to add at "single item level" screen.
Could somebody please tell me what is the name of the screen exit ?
I looked into package LAPA in transaction SE80 couldn't find much.
Note : We are using SAP 4.6C system
Thanks
Sarath

Write the following code in ZXWTYU01.
TABLES: WTY_PNWTYH_CUST,
MOVE IV_MODE TO GV_MODE.
MOVE-CORRESPONDING IS_PNWTYH TO : WTY_PNWTYH_CUST,
GS_PNWTYH_DYNPRO,
Write the following code in ZXWTYU02.
EV_ACTIV = 'X'.
MOVE GS_PNWTYH_DYNPRO TO ES_PNWTYH_DYN.
MOVE-CORRESPONDING WTY_PNWTYH_CUST TO : ES_PNWTYH_CUST,
: ES_PNWTYH_DYN.

Similar Messages

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 Exits for VA21

I have to add a field(date) in the screen in the transaction VA21 .
Is there any Screen exit for transaction VA21 ? if not how do i go about doing the same

Hello Amit,
The requirement is can be met as follows....
U can add the required field in the Additional data tab for header.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, This screens contain the Include screens SAPMV45A 8309 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
This should resolve ur problem.

Screen Exit for ME51N

HI ,
EVERYBODY
I AM DOING SCREEN EXIT FOR TCODE ME51N, ENHANCEMENT (MEREQ001) EXIT SAPLMEGUI , I HAVE ADDED TWO FIELDS
VALIDITY START DATE AND VALIDITY END DATE.
I HAVE CONFUSION ABOUT HOW TO EXPORT DATA ENTERED IN SUBSCREEN.
PLS HELP ME ..........
THANKS & REGARDS
SANJEEV

hi,
EXIT_SAPLMEREQ_001 -
Export Data to Customer Subscreen for Requisition (PBO)
*sample code write in the corresponding include
DATA: ls_mereq_item TYPE mereq_item.
clear eban values if no PReq item
IF im_req_item IS INITIAL.
CLEAR: *eban,
         eban.
ELSE.
read item data from system
ls_mereq_item = im_req_item->get_data( ).
fill customer field with old values
eban-zflag = ls_mereq_item-zflag.
   *eban-zflag = ls_mereq_item-zflag.
ENDIF.
Read and store activity type to chnge the field status
of the subscreen
IF NOT im_req_item IS INITIAL.
gf_aktyp = im_req_item->GET_ACTIVITY( ).
endif.
EXIT_SAPLMEREQ_003 Import Data from Customer Subscreen for Requisition
data:     ls_mereq_item type mereq_item.
*get values if PReq item exists
if not im_req_item is initial.
*read item data from system
ls_mereq_item = im_req_item->get_data( ).
*if customer field changed
if eban-zflag ne *eban-zflag.
*fill field with new value
    ls_mereq_item-zflag = eban-zflag.
*set new item data to system
    call method im_req_item->set_data( ls_mereq_item ).
*tell the system that there has something changed on the customer tab
    EX_CHANGED = 'X'.
endif.
endif.
cheers,
sasi

Screen Exit for MI01 and LI01N

Hi,
I need a screen exit for MI01 and LI01N. Please reply ASAP

Hi Nishu,
For MI01 below are the exits:-
MBCF0002 Customer function exit: Segment text in material doc. item
MBCF0005 Material document item for goods receipt/issue slip
MBCF0006 Customer function for WBS element
MBCF0007 Customer function exit: Updating a reservation
MBCF0009 Filling the storage location field
MB_CF001 Customer function exit for update of material document
MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0011 Read From RESB and RKPF For Print List in MB26
MBCFC003 Maintenance of batch master data for goods movements
MBCFC004 Maintenance of batch specifications for goods movements
For LI01N :-
MWM2S001 Exit to Determine 2-Step Picking Characteristic
MWMBAP01 Enhancement for BAPI WarehouseTransOrder.GetDetail
MWMBAP02 Enhancement for BAPI WarehouseStock.GetDetail
MWMD0001 Transfer order print via RLVSDR40
MWMD0002 Transfer order print as multiple process with RLKOMM40
MWMIDI07 Enhancement for Output WMPIHU (Create Pick-HU) Inbound
MWMIDO11 Enhancement for message WMTORD: TO with several items
MWMIDO12 Enhancement for Output WMPIHU (Pick-HUs) Outbound
MWMIDO13 Extension for WMMBXY (subsequent tasks after goods movement)
MWMPP001 Enhancement WM/PP Interface (automatic TR generation)
MWMRF001 RF: Influence Display of material description
MWMRF100 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0100)
MWMRF101 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0101)
MWMRF102 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0102)
MWMRF104 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0104)
MWMRF105 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0105)
MWMRF106 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0106)
MWMRF107 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0107)
MWMRF108 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0108)
MWMRF151 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0151)
MWMRF152 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0152)
MWMRF153 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0153)
MWMRF170 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0170)
MWMRF202 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF203 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0203)
MWMRF204 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0204)
MWMRF205 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0205)
MWMRF212 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0212)
MWMRF213 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0213)
MWMRF221 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0221)
MWMRF302 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0302)
MWMRF303 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0303)
MWMRF304 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0304)
MWMRF305 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0305)
MWMRF312 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0312)
MWMRF313 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0313)
MWMRF321 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0321)
MWMRF400 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0400)
MWMRF402 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0402)
MWMRF403 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0403)
MWMRF404 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0404)
MWMRF405 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0405)
MWMRF406 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0406)
MWMRF410 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0410)
MWMRF411 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0411
MWMRF412 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0412)
MWMRF502 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0502)
MWMRF503 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0503)
MWMRF504 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0504)
MWMRF505 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0505)
MWMRF600 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0600)
MWMRF601 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0601)
MWMRF630 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0630)
MWMRF631 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0631)
MWMRF632 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0632)
MWMRF633 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0633)
MWMRF634 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0634)
MWMRF650 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0650)
MWMRF651 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0651)
MWMRF700 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF701 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0701)
MWMRF702 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0700)
MWMRF703 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0703)
MWMRF704 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0704)
MWMRF705 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0705)
MWMRF760 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0760)
MWMRF761 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0761)
MWMRF762 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0762)
MWMRF763 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0763)
MWMRF764 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0764)
MWMRF765 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0765)
MWMRF766 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0766)
MWMRF767 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0767)
MWMRF768 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0768)
MWMRF769 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0769)
MWMRF777 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0777)
MWMRF800 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0800)
MWMRF801 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0801)
MWMRF802 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0802)
MWMRF803 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0803)
MWMRF804 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0804)
MWMRF805 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0805)
MWMRF806 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0806)
MWMRF807 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0807)
MWMRF888 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0888)
MWMRF889 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0202)
MWMRF998 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0998)
MWMRF999 ENHANCEMENT FOR USER SCREENS (LOGICAL SCREEN 0999)
MWMRFCOD Enhancement for function codedisabling
MWMRFDLV select delivery by user criteria
MWMRFPRT Enhancement for printing
MWMRFSSG user exit for sorting TOs in RF system-guided transaction
MWMRFUP Customer defined general purpose pushbutton called from scr.
MWMRP001 Cust. Exit for Fixed Bin Replenish.: Delivery Item Selection
MWMRP002 Cust. Exit for Fixed Bin Replenishment: TR Quantity Distr.
MWMRP003 Customer Exit for Replenishment using RLLNACH1
MWMRP004 User Exit for Replenishment using RLLNACH4
MWMTO001 Enhancements for end of transfer order generation
MWMTO010 Exit: Calculation of Total Planned TO Processing Time
MWMTO011 Correction of Planned Processing Time for TO Item
MWMTO012 Correction of Sorting and Split Transfer Order
MWMTO013 Stock Removal for Sev. Storage Types as in Stringent FIFO
MWMTOAU3 Separate selection of posting changes for autom.TO creation
MWMTR001 Exits at the end of transfer rqmnt creation (IM,PP interf.)
Choose the approriate one which suits your requirement.
Hope it helps you.
Regards
Abhii...

Screen Exit for Header ME51N

Hi experts, there is some screen-exit for HEADER of ME51N??
I've found only MEREQ001, but it has a screen exit only for item requisition...
Thanks.
Alexandere

Hi,
check the following screen exit Information for Enhancement "MEREQ001"
Calling screen     No.   Area       Called screen     No.
SAPLMEGUI       0014 SUB0     SAPLXM02        0111
also find the following user-exits
EXIT_SAPLMEREQ_001             Export Data to Customer Subscreen for Re
EXIT_SAPLMEREQ_002             Prepare Customer Subscreen for Requisiti
EXIT_SAPLMEREQ_003             Import Data from Customer Subscreen for
Regards
Sreeni

Screen exit for fb01 transaction

i would like to know the screen exit for transaction code fb01

I dont think there is any. I might be wrong. Maybe you could use Enhancement and call external program.

Screen exit for FS00 transaction

Hi All,
My requirement is i need to provide a button in FS00 transaction to approve the GL Code. Can anyone suggest me screen exit for FS00 transaction.
Thanks,
Chitra.

Hi
You can find Exits and BADI from SPRO. Just identify the area where you want to enhance and go to that area by SPRO , then you can see system enhancement that are available. This is the good way to find enhancement because you can find the documentation related to enhancement.
Like SPRO > Material Management > Purchasing > Develop enhancement for purchasing (Exits)
or see Business add ins for purchasing. Read the documentation.
Else you can search exits and badi by the package name like find the package of a transaction where you want to put enhancement. SE93 > Transaction name > Display > Package.
then go to SE80 and open the package then see function group start with X. this are exits that are available. you can find enhancement also.
Else to find BADI related to a transaction just put break point to class method cl_exithandler->get_instance in SE24.
and run the transaction , then you can find the BADI as exit name in this function call.
These are the way you can find enhancement , but the way which is describe 1st is the best way.
hope it will solve ur problem.
Thanks

Screen-exit for profit center creation - transaction KE51.

Hi All,
Background: The client has the requirement of importing profit centre master data from legacy system into SAP ECC system. Few of the legacy data could not be filled into existing sap fields, hence the requirement has been to populate the data into custom fields.
The client also has the requirement, that the same fields are required during online entry. For this we need to enhance the profit centre creation screen (transaction code KE51) with two additional custom fields.
Requirement: To enhance profit centre creation screen with custom fields. Screen-exit for KE51 transaction.
Pre-work: Program SAPLRKPM in SAP ECC system is the main program. It does not have any screen or sub screen area for custom fields addition. Debugged the program to check for screen-exits, found none.
Below user-exits are not either screen-exits or cannot be used for enhancing profit center screen.
PCA00001 EC-PCA: Document changes for data transfer
PCA00002 Profit Center Accounting: derivation of representative mat.
PCA00003 Derive Partner Profit Center for External Deliveries
PCA00004 Check valuation for invoice verification with transfer price
PCA00005 Check valuation for invoice verification with transfer price
PCASELEK EC-PCA: Selection criteria for data transfer
Solution required for: Could anyone please let me know if it is possible to enhance the profit center creation screen. If yes, please provide the names of the screen-exit/ badi exit.
(Just a thought, modifying the standard seems to be the only solution, this should be the last option and i agree, please provide your inputs.)
Thanks in advance.
Warm Regards,
Goutham.

Thank you Manohar for the response.
The requirement is to display custom fields on standard sap screen and there are no screen-exits. So, i suppose the standard screen has to be modified.
Could you please provide brief explanation on
May be you should consider maintaining custom mapping table instead of going for chaning standard.
With Regards,
Goutham.

Screen exit for transaction XK01

Hi,
I want to add a field for the transaction 'XK01'.
How to find out the screen exit for this transaction.
If we dont have screen exit for this transaction, is there any other way to add the field.
Ps help regardng this.

Hi,
Check the BADI CUSTOMER_ADD_DATA_CS , this is used to add a tab screen with the custom fields.
VENDOR_ADD_DATA Additional Vendor Data
Vendor Master (XK01) Screen Exit
check the foll link,
userexits be..
RFKRRANZ User exits: Accounts Payable Information System
SAPMF02K User exits: Vendor master data
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Regards
Kiran Sure

Screen exit for transaction VA41

dear all,
i want to add two fields to the transaction code VA41 contract creation.can anybody tell me screen exit for this or else how to do it?
regards,
Debesh

Hi Debesh Tripathy,
In additional data A Tab you have some customer field than you can use it, if these fields don't match with you request you can add fields in Additional data B tab with help of ABAP, since you need to modify the screen the PBO and PAI 8459 of program SAPMV45A. Bear in mind this screen is also used by VA21 and VA01 so you need to put a conditional to doesn't show this field in these others transaction.
Thanks,
Mariano.

Screen exit for transaction MD14.

Hi collegues,
Does anyone know what the screen exit for transaction MD14 is? I need to add an extra field to the detail screen of transaction MD14. The field name to be added is MDBA-LIFNR.
Thanks.

Exit found.

Screen Exit for t-code F-06

Dear All
I have an requirement like I need to add a field in the t-code f-06, in the first screen it self, they need a field to add from the table BKPF. I have searched for any screen exits for the package FBAS, but I am unable to find out.
Please guide me is there any other alternative way to solve this issue.
Thanks and Regards
Praveen Kumar

HI,
What ever you can achevie by using User Exit you can acheive with Badi's
[ABAP BADI SCREEN ENHACEMENTS |http://www.*******************/2008/09/abap-badi-screen-enhacements.html]html
[badi screen enhancements implementation |http://www.*******************/2008/10/badi-screen-enhancements-implementation.html]

Screen Exit for TX01/02/03

Hi,
I've searched for possible screen exits for tcode TX01/02/03 but cannot find any. Is there any possible way to add a custom tab?
Any inputs is appreciated.

Thanks! that link solved my problem. I have one question though, when I add the custom tab with some fields, can we add the custom fields to the database table VTBFHA/VTBFHAZU? or should we create a custom table for this custom fields?
Edited by: Marc Ng on Feb 24, 2009 4:38 AM

How to Implement Screen Exits for MK01...

Hi All,
I have to implement screen exits for Tcode MK01.
There is a BADI namely VENDOR_ADD_DATA_CS for Mk01.
Please guide me on how to implement a screen exit..
If possible send me the steps to be followed.
Regards,
Vidya.

Hi,
Check this:
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Have a look at this thread:
your working with BADI Then do as follows....
you follow the SPRO way and do everything they say.
1.you make an own z program with your subscreens
2.by VENDOR_ADD_DATA you put something like this to method CHECK_ADD_ON_ACTIVE:
Aktivierung Zusatzfelder für ZDB
if i_screen_group = 'Z1'.
e_add_on_active = 'X'.
endif.
3.by VENDOR_ADD_DATA_CS you put something like this to get_taxi_screen
CASE i_taxi_fcode.
Premier
WHEN 'Z1_SRCE1'.
e_screen = '0100'.
e_program = 'ZPM_SCREENEXIT_MK02'. " your own program
e_headerscreen_layout = ' '.
Deuxiem
WHEN 'Z1_SRCE2'.
e_screen = '0110'.
e_program = 'ZPM_SCREENEXIT_MK02'.
e_headerscreen_layout = ' '.
ENDCASE.
4. you make sure, that everything is active
Regards
Kiran
Edited by: Kiran Sure(skk) on Apr 11, 2008 3:42 PM

Screen exit for JIT call PJ02/PJ03

Similar Messages

Maybe you are looking for