COR1/2/3 process header screen exit

Hi,
The task is to add an additional tab strip with additional data in process order header - COR1, COR2, COR3
Is there a way to do that without modifying standard screen? Some screen exits? I wasnt able to find any
regards,
Jurijs

hi Jurijs Tolokoncevs ,
Please check the following exits
Transaction Code - COR1                     Create Process Order
Exit Name
Description
CCOWB001
Customer exit for modifying menu entries
COIB0001
Customer Exit for As-Built Assignment Tool
COZF0001
Change purchase req. for externally processed operation
COZF0002
Change purchase req. for externally procured component
PPCO0001
Application development: PP orders
PPCO0002
Check exit for setting delete mark / deletion indicator
PPCO0003
Check exit for order changes from sales order
PPCO0004
Sort and processing exit: Mass processing orders
PPCO0005
Storage location/backflushing when order is created
PPCO0006
Enhancement to specify defaults for fields in order header
PPCO0007
Exit when saving production order
PPCO0008
Enhancement in the adding and changing of components
PPCO0009
Enhancement in goods movements for prod. process order
PPCO0010
Enhancement in make-to-order production - Unit of measure
PPCO0012
Production Order: Display/Change Order Header Data
PPCO0013
Change priorities of selection crit. for batch determination
PPCO0015
Additional check for document links from BOMs
PPCO0016
Additional check for document links from master data
PPCO0017
Additional check for online processing of document links
PPCO0018
Check for changes to production order header
PPCO0019
Checks for changes to order operations
PPCO0021
Release Control for Automatic Batch Determination
PPCO0022
Determination of Production Memo
PPCO0023
Checks Changes to Order Components
STATTEXT
Modification exit for formatting status text lines
Transaction Code - COR2                     Change Process Order
Exit Name
Description
CCOWB001
Customer exit for modifying menu entries
COIB0001
Customer Exit for As-Built Assignment Tool
COZF0001
Change purchase req. for externally processed operation
COZF0002
Change purchase req. for externally procured component
PPCO0001
Application development: PP orders
PPCO0002
Check exit for setting delete mark / deletion indicator
PPCO0003
Check exit for order changes from sales order
PPCO0004
Sort and processing exit: Mass processing orders
PPCO0005
Storage location/backflushing when order is created
PPCO0006
Enhancement to specify defaults for fields in order header
PPCO0007
Exit when saving production order
PPCO0008
Enhancement in the adding and changing of components
PPCO0009
Enhancement in goods movements for prod. process order
PPCO0010
Enhancement in make-to-order production - Unit of measure
PPCO0012
Production Order: Display/Change Order Header Data
PPCO0013
Change priorities of selection crit. for batch determination
PPCO0015
Additional check for document links from BOMs
PPCO0016
Additional check for document links from master data
PPCO0017
Additional check for online processing of document links
PPCO0018
Check for changes to production order header
PPCO0019
Checks for changes to order operations
PPCO0021
Release Control for Automatic Batch Determination
PPCO0022
Determination of Production Memo
PPCO0023
Checks Changes to Order Components
STATTEXT
Modification exit for formatting status text lines
Transaction Code - COR3                     Display Process Order
Exit Name
Description
CCOWB001
Customer exit for modifying menu entries
COIB0001
Customer Exit for As-Built Assignment Tool
COZF0001
Change purchase req. for externally processed operation
COZF0002
Change purchase req. for externally procured component
PPCO0001
Application development: PP orders
PPCO0002
Check exit for setting delete mark / deletion indicator
PPCO0003
Check exit for order changes from sales order
PPCO0004
Sort and processing exit: Mass processing orders
PPCO0005
Storage location/backflushing when order is created
PPCO0006
Enhancement to specify defaults for fields in order header
PPCO0007
Exit when saving production order
PPCO0008
Enhancement in the adding and changing of components
PPCO0009
Enhancement in goods movements for prod. process order
PPCO0010
Enhancement in make-to-order production - Unit of measure
PPCO0012
Production Order: Display/Change Order Header Data
PPCO0013
Change priorities of selection crit. for batch determination
PPCO0015
Additional check for document links from BOMs
PPCO0016
Additional check for document links from master data
PPCO0017
Additional check for online processing of document links
PPCO0018
Check for changes to production order header
PPCO0019
Checks for changes to order operations
PPCO0021
Release Control for Automatic Batch Determination
PPCO0022
Determination of Production Memo
PPCO0023
Checks Changes to Order Components
STATTEXT
Modification exit for formatting status text lines

Similar Messages

VL01N / VL02N Delivery Header Screen Exit BAdI

Hi,
I am using LE_SHP_TAB_CUST_HEAD BAdI to add a custom tab in VL01N / VL02N header. I added a field with reference to VBPA-KNREF on my custom subscreen.
I need to update XVBPA and YVBPA tables (Partners data) in my subscreen based on the VBPA-KNREF custom field input and send back to the delivery processing. This BAdI allows to change only LIKP data when passing data from subscreen back to the delivery transaction/program.
Any experience with this BAdI or any ideas?
Thanks.

You need to use the methods
TRANSFER_DATA_TO_SUBSCREEN to pass the data from the standard fields to Subscreen fields
TRANSFER_DATA_FROM_SUBSCREEN to pass the data from the subscreen fields to standard fields
1) Create a Function Group e.g. ZVL02N_CUST
2) Create your screen in this function Group
3) Pass this program & screen information in the ACTIVATE_TAB_PAGE method
ef_caption = 'ADD. TAB'.
ef_program = 'ZVL02N_CUST'.
ef_dynpro = '9100'.
4) Create a function module ZVL02N_SET_DATA_SUBSCREEN in the same Function Group. Put all the required fields as the importing parameters in this function module. Create the same fields in the TOP include of the function group. Save the data from the importing parameter to the TOP Include fields. You can use these fields in your screen PBO to set your subscreen fields.
5) Same way create a FM ZVL02N_GET_DATA_SUBSCREEN in the same Function Group. Put all the required fields as the exporting parameters in this Function Module. Set the this exporting parameters values from the TOP include fields.
Regards,
Naimesh Patel

Screen exit for VL02N

Hi,
I want to add 2 fields on each line item of the delivery note prior to processing and Shipping which should be positioned in u201CLoading and Shipmentu201D tab of Delivery Note line item. This data to be stored in LIPS table.
Can any one suggest Screen exit/ BADI to implement the above changes.
Thanks

Reffer below thread:
Re: VL01N / VL02N Delivery Header Screen Exit BAdI
hope it will solve the problem.
Reddy
Note: mark the usefull answers

Screen Exit in Tcode COR1 - Create Process Order

Hi All,
Can anyone let me know if there is a screen exit or a BADI where in i can use it to extend the COR1 general data tab to include a field.
Even if i can add a additional tab in COR1 tcode through a BADI, will be good.
Please help.
Thanks,
Jaffer Ali.S

Hi,
STEP1:- Add Z-Fiels in Structure CAUFVD & Table: AUFK using (Goto --> Append Structure)
Step1. T-code: CMOD
STEP2: Enter project name: Zxxxxx --> Create
STEP3: Enter Short text -- > Click Enhancement Assignment
STEP4: Enter Enhancement: PPCO0001 & PPCO0020
STEP5: Click on Components
STEP6.1: double click on Screen-Exit: SAPLCOKO (Screen no: 5900)
A) Add Z-fileds in SCreen layout with keyp of structure :CAUFVD
Screen FLOW LOGIC:-
Process before output.
PROCESS BEFORE OUTPUT.
Set the screen status
Screen modifications incase of Display
MODULE screen_display.
Process after input.
PROCESS AFTER INPUT.
Screen fields and its processing.
CHAIN.
    FIELD: caufvd-z_cust1,
            caufvd-z_cust2,
            caufvd-z_cust3,
            caufvd-z_cust4,
            caufvd-z_cust5,
            caufvd-z_qty1,
            caufvd-z_qty2,
            caufvd-z_qty3,
            caufvd-z_qty4,
            caufvd-z_qty5.
    MODULE header_update.
ENDCHAIN.
FIELD: z_total.
MODULE disp_data.
Update the header.
Not required as of now.
module screen_display output.
Disable input in case of display.
if sy-tcode = 'COR3'.
    loop at screen.
         screen-input       = 0.
        modify screen.
    endloop.
endif.
endmodule.                 " screen_display OUTPUT
module header_update input.
check not sy-tcode = 'COR3'.
perform data_check using caufvd.
endmodule.                 " HEADER_UPDATE INPUT
*Validate screen input fiels
form data_check using p_caufvd structure caufvd.
data: l_v_count type i.
get parameter id 'MAT' field p_caufvd-matnr.
if p_caufvd-z_cust1 is initial and p_caufvd-z_qty1 is initial and
     p_caufvd-z_cust2 is initial and p_caufvd-z_qty2 is initial and
     p_caufvd-z_cust3 is initial and p_caufvd-z_qty3 is initial and
     p_caufvd-z_cust4 is initial and p_caufvd-z_qty4 is initial and
     p_caufvd-z_cust5 is initial and p_caufvd-z_qty5 is initial.
else.
    if not p_caufvd-z_cust1 is initial
      and not p_caufvd-z_qty1 is initial.
      select single count(*) into l_v_count from zcc_t01
        where z_custmat = p_caufvd-z_cust1 and
              matnr = p_caufvd-matnr.
      if l_v_count < 1.
        message e000(zpp) with 'Entered customer does not exist'.
      endif.
      clear l_v_count.
    else.
      message e000(zpp) with 'Fill both customer material and Qty'.
    endif.
    if not p_caufvd-z_cust2 is initial
      and not p_caufvd-z_qty2 is initial.
     select single count(*) into l_v_count from zcc_t01
        where z_custmat = p_caufvd-z_cust2 and
              matnr = p_caufvd-matnr.
      if l_v_count < 1.
        message e000(zpp) with 'Entered customer does not exist'.
      endif.
      clear l_v_count.
    elseif
     not ( p_caufvd-z_cust2 is initial and p_caufvd-z_qty2 is initial ).
      message e000(zpp) with 'Fill both customer material and Qty'.
    endif.
    if not p_caufvd-z_cust3 is initial
      and not p_caufvd-z_qty3 is initial.
     select single count(*) into l_v_count from zcc_t01
        where z_custmat = p_caufvd-z_cust3 and
              matnr = p_caufvd-matnr.
      if l_v_count < 1.
        message e000(zpp) with 'Entered customer does not exist'.
      endif.
      clear l_v_count.
    elseif
     not ( p_caufvd-z_cust3 is initial and p_caufvd-z_qty3 is initial ).
      message e000(zpp) with 'Fill both customer material and Qty'.
    endif.
    if not p_caufvd-z_cust4 is initial
      and not p_caufvd-z_qty4 is initial.
     select single count(*) into l_v_count from zcc_t01
        where z_custmat = p_caufvd-z_cust4 and
              matnr = p_caufvd-matnr.
      if l_v_count < 1.
        message e000(zpp) with 'Entered customer does not exist'.
      endif.
      clear l_v_count.
    elseif
     not ( p_caufvd-z_cust4 is initial and p_caufvd-z_qty4 is initial ).
      message e000(zpp) with 'Fill both customer material and Qty'.
    endif.
    if not p_caufvd-z_cust5 is initial
      and not p_caufvd-z_qty5 is initial.
     select single count(*) into l_v_count from zcc_t01
        where z_custmat = p_caufvd-z_cust5 and
              matnr = p_caufvd-matnr.
      if l_v_count < 1.
        message e000(zpp) with 'Entered customer does not exist'.
      endif.
      clear l_v_count.
    elseif
     not ( p_caufvd-z_cust5 is initial and p_caufvd-z_qty5 is initial ).
      message e000(zpp) with 'Fill both customer material and Qty'.
    endif.
endif.
endform.                    " Data_check
STEP7:-Double click on Function Exit:EXIT_SAPLCOKO_005
            Doouble click on include program: ZXCO1U21 and careae and add below code in include program
Data declarations
TYPES: BEGIN OF l_ty_zqty,
        z_custmat TYPE zcc_t01-z_custmat,
        z_qty     TYPE zcc_t01-z_qty,
       END OF l_ty_zqty.
DATA: l_s_zqty TYPE l_ty_zqty,
      l_t_zqty LIKE STANDARD TABLE OF l_s_zqty,
      l_v_frac TYPE zcc_t01-z_qty,
      l_v_four TYPE f VALUE '0.4'.
SET PARAMETER ID 'MAT' FIELD i_caufvd-matnr.
Get the fields from ZCC_T01 and display it.
IF ( sy-tcode EQ 'COR1' OR sy-tcode EQ 'COR2' )
          AND g_v_flag IS INITIAL.
IF i_caufvd-z_cust1 IS INITIAL AND
     i_caufvd-z_cust2 IS INITIAL AND
     i_caufvd-z_cust3 IS INITIAL AND
     i_caufvd-z_cust4 IS INITIAL AND
     i_caufvd-z_cust5 IS INITIAL.
    SELECT z_custmat z_qty INTO TABLE l_t_zqty FROM zcc_t01
    WHERE matnr = i_caufvd-matnr
      AND z_qty NE space
      AND z_qty NE '0'.
    CHECK sy-subrc = 0.
    LOOP AT l_t_zqty INTO l_s_zqty.
      CASE sy-tabix.
        WHEN 1.
          caufvd-z_cust1 = l_s_zqty-z_custmat.
          caufvd-z_qty1 = i_caufvd-gamng * l_s_zqty-z_qty / 100.
          COMPUTE l_v_frac = FRAC( caufvd-z_qty1 ).
          IF l_v_frac > l_v_four.
            COMPUTE caufvd-z_qty1 = CEIL( caufvd-z_qty1 ).
          ELSE.
            COMPUTE caufvd-z_qty1 = FLOOR( caufvd-z_qty1 ).
          ENDIF.
          CLEAR l_v_frac.
        WHEN 2.
          caufvd-z_cust2 = l_s_zqty-z_custmat.
          caufvd-z_qty2 = i_caufvd-gamng * l_s_zqty-z_qty / 100.
          COMPUTE l_v_frac = FRAC( caufvd-z_qty2 ).
          IF l_v_frac > l_v_four.
            COMPUTE caufvd-z_qty2 = CEIL( caufvd-z_qty2 ).
          ELSE.
            COMPUTE caufvd-z_qty2 = FLOOR( caufvd-z_qty2 ).
          ENDIF.
          CLEAR l_v_frac.
        WHEN 3.
          caufvd-z_cust3 = l_s_zqty-z_custmat.
          caufvd-z_qty3 = i_caufvd-gamng * l_s_zqty-z_qty / 100.
          COMPUTE l_v_frac = FRAC( caufvd-z_qty3 ).
          IF l_v_frac > l_v_four.
            COMPUTE caufvd-z_qty3 = CEIL( caufvd-z_qty3 ).
          ELSE.
            COMPUTE caufvd-z_qty3 = FLOOR( caufvd-z_qty3 ).
          ENDIF.
          CLEAR l_v_frac.
        WHEN 4.
          caufvd-z_cust4 = l_s_zqty-z_custmat.
          caufvd-z_qty4 = i_caufvd-gamng * l_s_zqty-z_qty / 100.
          COMPUTE l_v_frac = FRAC( caufvd-z_qty4 ).
          IF l_v_frac > l_v_four.
            COMPUTE caufvd-z_qty4 = CEIL( caufvd-z_qty4 ).
          ELSE.
            COMPUTE caufvd-z_qty4 = FLOOR( caufvd-z_qty4 ).
          ENDIF.
          CLEAR l_v_frac.
        WHEN 5.
          caufvd-z_cust5 = l_s_zqty-z_custmat.
          caufvd-z_qty5 = i_caufvd-gamng * l_s_zqty-z_qty / 100.
          COMPUTE l_v_frac = FRAC( caufvd-z_qty5 ).
          IF l_v_frac > l_v_four.
            COMPUTE caufvd-z_qty5 = CEIL( caufvd-z_qty5 ).
          ELSE.
            COMPUTE caufvd-z_qty5 = FLOOR( caufvd-z_qty5 ).
          ENDIF.
          CLEAR l_v_frac.
        WHEN OTHERS.
      ENDCASE.
    ENDLOOP.
    g_v_flag = 'X'.
ENDIF.
IF g_v_flag IS INITIAL AND sy-tcode = 'COR2'.
    MOVE-CORRESPONDING i_caufvd TO caufvd.
ENDIF.
ELSE.
MOVE-CORRESPONDING i_caufvd TO caufvd.
ENDIF.
STEP8:- Double click EXIT_SAPLCOKO_006
            Doouble click on include program: ZXCO1U17 and careae and add below code in include program
Data Declaration.
tables : caufvd.
Export the fields.
move-corresponding caufvd to e_coci_aufk.
hope this help...
Regards
Sudheer Madisetty

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 FB60 on header level

hi , i am working on FB60 . i want to add an extra tab i.e extra screen on the header level . are there any screen exits for fb60 to add extra screen?

hi praveen,
search this forum on how to implement a badi if you haven't done one before. also, go to transation SE18 and read the documentation on badi_fdcb_subbas01 which clearly says that its used for FB60... see the example how they have used it by going to menubar Implementation->Overview then choose FI_FDCB_SUBBAS01_EX (Example for Screen Enhancement 1 on FDCB Basic Data Screen)...you should look at the method PUT_DATA_TO_SCREEN_OBJECT and tab Subscreens where the screen exits are available to use.
In FB60, if you go to menubar System->Status and check the Program (Subscreen) and Screen Number, you'll see it'll match the program name and screen no. provided in the Subscreen tab of the BADI.
Hope this helps.
Cheers,
Sougata.

Screen exit of Po header

Hello Friends ,
I have added new tabstrip in PO header with two new fields which are appended to Ekko table by append structure.
1) When creating the PO, the changes to these new fields are not getting updated into Ekko table
2) After doing the changes to these new fields in Me22n, if i am trying to save the Po it's giving the information message 'No data changed' and the changes to these new fields are not getting updated in Ekko table.
Could you please advice me regarding this problem.
Thank's in advance,
Arvind.

Hello Friends,
The screen exit is shown below ,here in 101 screen i have added two new fields
SAPMM06E                       0101 CUSTSCR1 SAPLXM06                       0101
To update the new fields in the new tab strip , i have written the code in the user exit of PO header (EXIT_SAPMM06E_006) as shown below.
Note:The two new fileds are check boxes ,depending on some conditions we need to mark the check boxes.
TABLES:CI_EKKODB.
if not I_LFM1-ZZINTLIF is initial.
CI_EKKODB-ZZINTLIF = I_LFM1-ZZINTLIF.
endif.
IF ( I_EKKO-BSART = I_LFM1-ZZEDIBSART1 ) OR
     ( I_EKKO-BSART = I_LFM1-ZZEDIBSART2 ) OR
     ( I_EKKO-BSART = I_LFM1-ZZEDIBSART3 ) OR
     ( I_EKKO-BSART = I_LFM1-ZZEDIBSART4 ) OR
     ( I_EKKO-BSART = I_LFM1-ZZEDIBSART5 ) .
    CI_EKKODB-ZZEDI = 'X'.
ENDIF.
But these two new fields i.e. ZZINTLIF and ZZEDI are not getting updated in the table Ekko and the changes are not reflected on screen also.
Please help me regarding this issue.
Thank you,
Arvind.

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 in Header Level in ME51N

Hi,
Are there any screen exits in header level in ME51N screen? I need to call a BSP upon the click of a button and when the user selects a line item from there, it has to fall as a line item in the PR screen.
Need your help on this.
Thanks and Regards,
Manideep Settipalli

Hello,
Please refer to this very useful document about finding user-exits, BADI's eg.
Methods to find Customer/User Exit's & BADi's for a Transaction Code!
Regards
Ali Murat

Screen exit for ME51N in header

Hi friends,
Is there any screen exit for ME51N(Purchase requisition) in header level.I found MEREQ001 enhancement, but this is for item level.please help.
regards,
Thoufique.

Hi Thoufique,
try the following screen 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
Also, for more help on your problem, refer to the following link:
Re: re: screen exits
Hope this will help you...

Process on Value-Request in Screen Exit

Hi,
I have few fields in the screen exit to be supported with F4 Value Help. These values are not from R3 Dictionary Tables. The Values are N, P, T, F, R, K, M, G etc. When the User Clicks the Drop Down, all the possible values should appear in a small window near the screen filed. Can any one please suggest me a suitable solution for this requirement.
Thanks for your Help in Advance.
Kannan

Hi,
You can use the FM 'F4IF_INT_TABLE_VALUE_REQUEST'
TABLES: T005T.
DATA: BEGIN OF t_t005 OCCURS 0,
        land1 TYPE t005-land1,
      END OF t_t005.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(6) v_text FOR FIELD P_LAND1.
PARAMETERS: p_land1 TYPE t005-land1.
SELECTION-SCREEN END OF LINE.
INITIALIZATION.
v_text = 'Country'.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_land1.
REFRESH: t_t005.
SELECT land1
         INTO TABLE t_t005
         FROM t005.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
       EXPORTING
           DDIC_STRUCTURE   = 'T005'
            PVALKEY          = ' '
            retfield         = 'LAND1'
            dynpprog         = sy-repid
            DYNPNR           = sy-dynnr
            dynprofield      = 'P_LAND1'
            callback_program = sy-repid
            value_org        = 'S'
       TABLES
            value_tab        = t_t005
       EXCEPTIONS
            parameter_error = 1
            no_values_found = 2
            OTHERS           = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Thanks,
Naren

Menu Exits and Screen Exits

hi everyone,
can you send me some examples on menu exits and screen exits.
thank you.
preetham

Hi Preetham,
In older versions MENU Exits approached through Transaction CMOD by creating
PROJECTS and activating the project and assigning Program to that
Transaction Codes. For MENU Exits, Transaction Codes will be starting with
"+" sign and with default text "NODE TEXT NOT FOUND" for which you can
assign your Report or Dialog Program etc., (for Eg:- +DW4 MENU Exits
Transaction available in TOOLS --> ABAP Workbench --> Utilities --> <Node
Text Not found>).
Procedure for Creating MENU Exits.
1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command
Line.
2) In Area Menu Paramenter type 'S000' (S triple Zero)
3) Then Press Change Icon in Application Tool Bar. Then It may ask for
Access Key [or] it may display "Specify Processing mode" window. If it ask
for the Access Key Check for the availability of OSS Note and apply to open
Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify
Processing mode" window with Three Push Button. In which select "Change" and
proceed further.
4) Then it will display "Information" window with the following information
"Caution : The Original Language of the structure is German (editing lang. :
English) ". Then press "Enter Key to proceed further.
5) Then you will get into "Edit Area Menu S000".
6) for eg:- Expand Tools Menu.
7) Then Press ABAP Workbench <Icon>.
8) Then you will get into ABAP Workbench Menu Tree.
9) Then Expand Utilities Menu.
10) In the last line you will find one MENU EXIT Provision to include your
own menu. "Node Text Not Found" This text can be change by double Clicking
that. There you can find the T.Code. Here for Eg:- "+DW4".
11) for eg: - Here change the Text to "Sample Menu Exit" and then note down
the T.Code "+DW4".
12) Then Save with Change Request Number and come out of Transaction SE43.
13) Then Goto Transaction SE93.
14) Then type T.Code "+DW4" and press Create.
15) Then proceed further to create transaction called "+DW4".
I hope this could help you in Creating Menu Exit...
Creating menu exits
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
For screen exits.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
the tcode is cmod...
1.From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
2.Choose Edit component.
3.Choose the screen exit and double click on it
4.Create your subscreen using the Screen Painter.
5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
6.Choose the PAI and PBO to write down the logic.
7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
8.Go to the transaction ME22 to view the customer defined screen exit.
9.Enter the purchase order number and press Enter.
10.Go to the menu header --> Details.
11.Purchase number is visible on the standard screen
check the foll link,
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
also refer
MEnu Exit
http://www.sap-img.com/abap/what-is-user-exits.htm
Creating menu exits
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
For screen exits.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
chech these links for user exists its usefull
http://www.allsaplinks.com/user_exit.html
Re: Screen exit
user exit and customer exit
http://help.sap.com/saphelp_47x200/helpdata/en/dd/561602545a11d1a7020000e829fd11/frameset.htm
http://www.sap-basis-abap.com/sapab013.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
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
MENU
refer
MEnu Exit
just refer to the link below for step by step procedure with screen shots
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
Check this link:
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module 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 points if helpful.
Thanks
Naveen khan
Message was edited by:
Pattan Naveen

Custom Field using screen exits CS01/CS02/CS03

Dear Experts,
I am using Screen exits to add some text description in CS01/CS02/CS03, my requirement is to add a field 'Product Appearance' with multiple lines for the material description. For this I have created customer field 'ZTEXT1' and appended it to STKO table. Now in screen painter(SE51) i need to add 3-4 lines of type stko-ztext1 because the product desc is of size 300-400 character.
I am not able to create 3-4 lines of type stko-ztext1. Can u plz suggest how can i add 3-4 lines of type stko-ztext1 in SE51.
I am able to create a blank field in SE51 using Edit->Grouping->Step Loop->Define, but while activating it is giving error as "Input/Outpt field STKO-ZTEXT1 and key word are not in the same screen".
Plz suggest.
Regards

Hi Kurtt,
Below are the available user exits :-
PCSD0001 Applications development R/3 BOMS
PCSD0002 BOMs: Customer fields in item
PCSD0003 BOMs: Customer fields in header
PCSD0004 BOM comparison
PCSD0005 BOMs: component check for material items
PCSD0006 Mass changes user exit
PCSD0007 Check changes in STKO
PCSD0008 WBS BOM: Customer-specific explosion for creating
PCSD0009 Order/WBS BOM, determine URL page
PCSD0010 Order/WBS BOM, determine explosion date
PCSD0011 Knowledge-based order BOM, parallel update
PCSD0012 Customer - Mat. number/mat. number during material exchange
PCSD0013 Customer-specific processing of an explosion for BOM browser
PCSD0014 Knowledge-based order BOM: Status
Check which one suits your requirement.
Regards
Abhii

Sold to party in Order header screen

Hi,
Iam having a service contract and when I assign the service contract in service order header screen in SALES DOCUMENT field, I need to have the sold to party(assigned to Contract) field automatically populate in the sold to party field in the order header screen.
Presently its not happening and how to make this?
Is there is any relavent exit available for this?
regards
KRISHNAN

I can't remember exactly how we did it - only that we did manage it via a user-exit.
Unfortunately I don't have the documentation either...
You could do it at save (IWO10009) as follows:
data: t_ihpa like ihpavb occurs 10.
* get order parnter data
call function 'PM_PARTNER_GET_XIHPA'
    tables
      h_xihpa = t_ihpa.
* do your own processing here
* remembering to set the UPDKZ field (I=insert, U=update, etc)
* set order partner data
call function 'PM_PARTNER_PUT_XIHPA'
    tables
      h_xihpa = t_ihpa.
Not entirely orthodox, but it'll work...
PeteA
[www.pjas.com]

Screen exit and bapi

how can we call a subscreen in screen exit.
how can we do error handling in bapi?differenece between bapi and bdc.
i will give the 10points to correct answers.
kiran

Hi,
Call subscreen in screen exit:
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
the tcode is cmod...
1.From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
2.Choose Edit component.
3.Choose the screen exit and double click on it
4.Create your subscreen using the Screen Painter.
5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
6.Choose the PAI and PBO to write down the logic.
7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
8.Go to the transaction ME22 to view the customer defined screen exit.
9.Enter the purchase order number and press Enter.
10.Go to the menu header --> Details.
11.Purchase number is visible on the standard screen
Please check if the thread given below would be of any help.
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/menu-exits-72696#
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
error handling in bapi:
While creating BAPIs,include Return table (of structure BAPIRET2)as table parameter. This table is populated with error messages/Sucessful messages after BAPI was executed.
Diff b/w bdc and bapi:
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system
or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
BAPI.
BAPI stands for Business API(Application Program Interface).
A BAPI is remotely enabled function module
ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access.
Also they are part of Businees Objest Repository(BOR).
Regards
Kiran Sure

COR1/2/3 process header screen exit

Similar Messages

Maybe you are looking for