Badi for me21n,me22n,me23n

HI experts,
      CAn any one help me out infinding a badi for me21n,me22n,me23n, which triggered on every press of enter key or some other check, so that i could kept a validation for the header and item fields of the t.codes

Hi,
Go for BADI,
Follow the below steps to find out what all BADI's are called when you press any button in any transaction.
1) Goto se24 (Display class cl_exithandler)
2) Double click on the method GET_INSTANCE.
3) Put a break point at Line no.25 (CASE sy-subrc).
Now
4) Execute SAP standard transaction
5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
7) This way you will find all the BADIs called on click of any button in any transaction.
Reward points if useful....
Regards
AK

Similar Messages

  • How to add a custom button on Application Toolbar for ME21N, ME22N & ME23N

    Hi Experts,
    I am new to this forum. I hope someone will help me.
    My Requirement is as :
    I want to add a new custom button on Application Toolbar for ME21N, ME22N & ME23N.
    There are already standard buttons in this toolbar which is Document Overview On, Hold, Personal Settings etc.
    So after the 'personal settings' button i want add a new button and want to write a code which will open one custom screen.
    I am not able to find any exit for this....
    Please help...
    Thanks....

    Hey Buddies
    Try below BADI : ME_PROCESS_PO_CUST
    and check with required methods.
    1)PROCESS_ITEM
    2)CHECK
    3)POST
    Regards,
    Pranav

  • Badi for ME21N & ME22N to check storage location

    Hello Guru's,
    I need BADI for ME21N & ME22N to check storage location is maintained for plant used in PO i'm using method IF_EX_ME_PURCHDOC_POSTED~POSTED with definition name ME_PURCHDOC_POSTED but this throws message on SAVE.
    But my requirement this message should be displayed before saving.Please guide

    Hi,
    Use BADI:
    ME_PROCESS_PO_CUST
    BADI CL_ME_PO_CUST
    Business Add-in
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                      Processing of Component Default Data at Time of GR: Customer
    ME_PO_SC_SRV                              BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                    Enhancements to Price Determination: Customer
    ME_PO_PRICING                              Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                        Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                                  Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                           Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK               FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_DEFINE_CALCTYPE                  Control of Pricing Type: Additional Fields
    ME_COMMTMNT_REQ_RE_C            Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    SMOD_MRFLB001                           Control Items for Contract Release Order
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    Edited by: Neenu Jose on Nov 21, 2008 6:13 AM
    Edited by: Neenu Jose on Nov 21, 2008 6:16 AM

  • New Tab on header level for me21n/me22n/me23n

    Hi Friends
    i have created a new tab on the me21n/me22n/me23n  header level using the exit
    MM06E005 , The tab is displayed but i am not unable to udate the records into the
    EKKO  Table whereas i have added my field in the include of  EKKO  CL_EKKODB
    Kindly somebody help me with elaborated steps  .
    Thanks & Regards
    Digvijay Rai

    Hi Digvijay,
    Once the data is entered on the screen ..code is written to update the table ie...
    flow of data from custom screen for header is OK..but for display and change we need to
    import the data in a similar manner to the customer subscreen or the tab added in header level
    As you can see the following 3...code must be done in EXIT_SAPMM06E_006/007 to fetch data to customer subscreen for display/change actions..use 006/007 for PBO/PAI actions..
    EXIT_SAPMM06E_006   Export data to customer subscreen for header(PBO)....INCLUDE ZXM06U36
    EXIT_SAPMM06E_007   Export data to customer subscreen for header(PAI)....INCLUDE ZXM06U38 .
    EXIT_SAPMM06E_008   Import data from customer subscreen for header
    Pls check and revert..in addition
    go to smod->MM06E005-> "documentation" -> Display to read more on documentation about data flows and exits used for it
    Hope it helps
    Regards
    Byju

  • EXIT BADI FOR ME21N ME22N AND ME23N

    Hello Boys.
    I want  to change the field 'Tax code' (MWSKZ) in a Purchase order on transaction ME21N, ME22N AND ME23N.
    I want to change thios field in a BADI, USER EXIT or ENHANCEMENT-POINT.
    But I can't find where change this field.
    thanks for your help.
    Best regards.

    Try Badi : ME_PROCESS_PO_CUST
        CALL METHOD im_item->get_data
          RECEIVING
            re_data = v_data_item.
    Your code to change the tax code
    CALL METHOD im_item->set_data( v_data_item ).
    <REMOVED BY MODERATOR>
    Edited by: Aparna Shekhar on Jun 12, 2008 11:33 AM
    Edited by: Alvaro Tejada Galindo on Jun 12, 2008 12:52 PM

  • EXIT_SAPMM06E_006  for ME21N, ME22N, ME23N

    Hi all
    i need help to insert some fields from EKPO in
    the Tcode ME21/2N. For example EKPO-BRGEW on status tab in the to header part.
    I have appended this field into structure CI_EKKPODB also created subscreen for SAPLXM06 u2013 0111.
    need to assign this  screen to SAPMM06E-0111.  can anybody tell me how to assign screen. 
    If I can get a sample code to write in the EXIT_SAPMM06E_006 will be very much useful.  so that data from this field must be displayed on the header part of the status tab.
    Points are not issue.  Will reward points.
    Thanx and regards
    Manisha.

    Hi Manisha,
    Firstly When you are adding a customer field to the ME21n transaction at header level, you just check under which structure you are appending it.
    You are appending into EKPO table. It is for item details.
    You go for EKKO table, it is for header data. In that there is custom include, you can add your field there and activate it.
    Recently I have developed one Screen exit for ME21n transaction. I have added a custom field and populated the data into the database. If you need it I will send to your ID  for your reference.
    Code has to be written in the function modules EXIT_SAPMM06E_008 so that data flows to and fro between the main SAP program and custom sub screen program. Double clicking on the exit we can write the code in it.
    In that Exit we will having parameters. When ever we enter the data in the screen, That means screen field it should get captured and sent to the parameters in the function module. Then later it is modified.
    Reward points if useful.
    Cheers,
    Swamy Kunche

  • Exit or Badi for ME21N /  ME22N to update Shipping data

    Hi gurus,
    when i try to modify or create any purchasing order i need to force to 'X' the field
    - Order Combination Indicator - ( MEPO1331-KZAZU )
    i try to implement badi ME_PROCESS_PO_CUST - method PROCESS_ITEM ed exit - EXIT_SAPMM06E_013 - but nothing to do.
    can yuo help me??

    Nothing to do...
    I already tried to use this BADI .method ITEM.
    ls_ekpv = im_item->get_shipping_data( ).
    ls_ekpv-kzazu = 'X'.
    im_item->set_shipping_data( im_ekpv = ls_ekpv ).
    In this method i get old data via call method get_shipping_data
    and i set new nata with method set_shipping_data
    in this standard method i found a firewall ( standard note )
    Only some fields can change in the structure...but not my field ( kzazu )
    FC

  • In transactions ME21n, ME22n, ME23n I need to add new field to item detail

    Hello,
    In transactions ME21n, ME22n, ME23n I need to add a new field  to the table control TC_1211, in SAPLMEGUI screen 1211 for PO line items.  The new field is UNSPSC Code, a 30 char field, which will be enterable/changeable on the ME21n, ME22n screens and display only on ME23n. 
    BADI ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order.  Is this the correct BADI to use for the purpose of adding a new input/output field to the PO detail SAPLMEGUI screen 1211?   
    Does anyone have any examples of adding a new field to PO Item Detail screen using BADI ME_PROCESS_PO_CUST?  I have had some experience creating Badi's, and would appreciate very much some sample code if possible. 
    We are on release SAP ERP Central Component 5.0
    SAPKB64018     SAP Basis Component
    SAPKA64018     Cross-Application Component
    SAPKH50013     Logistics and Accounting
    Thank you,
    Victoria

    Hi,
    Thank you for the response.  I tried this and found  Badi ME_PROCESS_PO_CUST.  Do you have any examples of adding a new cust field to PO Item overview screen using badi ME_PROCESS_PO_CUST? I have had little experience creating badi's, and would appreciate very much some sample code if possible.
    In transactions ME21n, ME22n, ME23n I need to add a new field in PO Item overview (screen 1211 of SAPLMEGUI). The new field ZZUNSPSC, has been appended to table EKPO as a 30 char field, which will be enterable/changeable on the ME21n, ME22n screens and display only on ME23n.
    Can you tell me if method FIELDSELECTION_ITEM of badi ME_PROCESS_PO_CUST the correct one to use for the purpose of adding a new input/output field to the PO item overview on SAPLMEGUI screen 1211?
    Thank you for help - much appreciated,
    Vicki

  • Needs to be Hide Additional Planning button on ME21N/ME22n/ME23n

    Hi All-
    Is there anyway we can disable the 'Additional Planning' push button on 'ME21N/ME22N/ME23N' either using user-exit or 'BADI's?
    Please let me know..
    Thanks,
    Sony

    using transaction variants we can disable the additional planning button in the me21n/me22n/me23n
    transaction code for creating a transaction variant is SHD0.

  • New tab implementation at item level in ME21N/ME22N/ME23N.

    Hi Friends,
    I have implemented two badis 1. ME_GUI_PO_CUST and 2. ME_PROCESS_PO_CUST to get a new tab at item level in ME21N/ME22N/ME23N, I could see this new tab only in ME23N but not in ME21N/ME22N, and I found that Badi ME_PROCESS_PO_CUST is not getting triggered for any of these tcodes : ME21N/ME22N/ME23N. Can anybody help me getting this issue resolved with coding example as well.
    Thanks in Advance.

    Hi Know ,
    I know that we have to use the following BADIs
    ME_PROCESS_PO_CUST
    ME_GUI_PO_CUST
    But I does not know what are the methods to be implemented
    and what is the code we have to write in that methods .
    Thanks in advance ,
    Siva.

  • How to make the custom field enable/disable in ME21n/ME22n/ME23n trans

    Hi Experts,
    I need help.
    I have created one custom field in the transaction ME21n/ME22n/ME23n under customer data 2 tab. But my problem is the field is always in enable (means editable only)  even in Display mode. How to make the field is non editable in display mode and editable in change mode.
    I have tried by putting some logic to make that field to change alternatively according to change/display button. And it is working fine but if we click any othe button , this field is becoming editable even in display mode.
    How to make this field to behave as standard fields?
    Please reply me <removed by moderator>
    Thank you in advance.
    Best Regards,
    Divakar.
    Edited by: Thomas Zloch on Mar 2, 2012

    If you have BADI implimented for custom tabs then you can do this in method ME_PROCESS_PO_CUST~FIELDSELECTION_ITEM
    lv_changeable = im_header->is_changeable( ).
      LOOP AT ch_fieldselection ASSIGNING <fs>
        IF lv_changeable IS INITIAL.
          <fs>-fieldstatus = '*'. " Display
        ELSE.
          <fs>-fieldstatus = '+'. " Change
        ENDIF.
    endloop.

  • ABAP runtime error while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N

    Dear All Expert,
    I am facing problem while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N,
    Please find the below ABAP Runtime Error.
    Runtime Errors         LOAD_TYPE_VERSION_MISMATCH
    Date and Time          10.02.2011 11:13:07
    Short text
         Change of a Dictionary structure at runtime of a program.
    What happened?
         Runtime error
         The current ABAP program "CL_IM_WRF_MM_PROC_PO==========CP" had to be
          terminated because one
         of the statements could not be executed at runtime.
    What can you do?
         Restart the program.
         If the error persists, contact your SAP administrator.
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    Error analysis
         The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY"
          changed
         during the flow of the transaction.
         As the type was already used in the old version
         and in the new type should be used in the same transaction in the new
          version, the transaction had to be cancelled to avoid inconsistencies.
    How to correct the error
        Try to restart the program.
    System environment
        SAP-Release 700
        Application server... "iqe"
        Network address...... "172.25.0.85"
        Operating system..... "Linux"
        Release.............. "2.6.9-55.ELsmp"
        Hardware type........ "x86_64"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 0
        Shortdump setting.... "full"
        Database server... "iqe"
        Database type..... "ORACLE"
        Database name..... "IQE"
        Database user ID.. "SAPSR3"
        Terminal................. "MUMJML5727"
        Char.set.... "C"
        SAP kernel....... 700
        created (date)... "Dec 26 2010 20:17:07"
        create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
        Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 285
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 700
    Operating system..... "Linux 2.6"
    Memory consumption
    Roll.... 16192
    EM...... 25139088
    Heap.... 0
    Page.... 40960
    MM Used. 8038136
    MM Free. 4528408
    User and Transaction
    Client.............. 600
    User................ "JKMM"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4D524AD1FD7A42F9E1000000AC190055"
    Program............. "CL_IM_WRF_MM_PROC_PO==========CP"
    Screen.............. " "
    Screen line......... " "
    Information on where terminated
        The termination occurred during generation of the ABAP/4 program
         "CL_IM_WRF_MM_PROC_PO==========CP".
        The termination occurred in line 213
        of the source code of program "CL_IM_WRF_MM_PROC_PO==========CM007" (when
         calling the editor 2130).
    Source Code Extract
    Line  SourceCde
      183   DATA: l_flag TYPE wrf_pbas_boolean.
      184
      185   CALL FUNCTION 'WRF_POHF_MSG_READ_PREVIEW_FLAG'
      186     IMPORTING
      187       e_preview_flag = l_flag.
      188
      189   IF NOT l_flag IS INITIAL.
      190
      191     DATA: l_header TYPE REF TO cl_po_header_handle_mm.
      192
      193     MOVE im_header ?TO l_header.
      194
      195     CALL METHOD l_header->if_output_mm~preview( ).
      196
      197     CALL FUNCTION 'WRF_POHF_MSG_RESET_PREV_FLAG'.
      198
      199 ***$ Widening Cast for printing information.
      200 **    CALL FUNCTION 'WRF_POHF_STORE_PRINT_INFO_SET'
      201 **      EXPORTING
      202 **        im_header = l_header.
      203
      204 * Printing Preview
      205 * IF NOT gv_preview IS INITIAL.
      206 *    CALL METHOD l_header->if_output_mm~overview( ).
      207 *    CALL METHOD l_header->if_output_mm~preview( ).
      208 * clear gv_preview.
      209   ENDIF.
      210
      211 *  ENDIF.
      212
    >>>>> ENDMETHOD.
    Internal notes
        The termination was triggered in function "ab_RxDdicStruShareFailed"
        of the SAP kernel, in line 2539 of the module
         "//bas/700_REL/src/krn/runt/abtypload.c#11".
        The internal operation just processed is " ".
        Internal mode was started at 20110210111306.
        Name of the changed type......: "WRF_POHF_KOMP_STY"
        New version of the type.......: 20070508193207
        Old version of the type.......: 20070508193207
        New user......................: "Type" "WRF_POHF_KOMP_STY"
        Version of the new user.......: 20070508193207
        Old user......................: "???" "???"
        Version of the old user.......: "???"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (CTrcStack2+0x78)[0x6cbb78]
    (CTrcStack+0xb)[0x6cc17b]
    (ab_rabax+0x3be5)[0xb8d985]
    (_Z24ab_RxDdicStruShareFailedPKtm4RUDIS0_S1_S0_+0x163)[0xb16823]
    (_Z19ab_GetDdicTypeIndexPKtm4RUDI+0x1f6)[0xb0dbb6]
    (_Z11ab_LoadViewPtjPKtPK11PROGRAMHEADPj+0x27e)[0xb16ede]
    (_Z18ab_GetDdicTypeLoad4RUDI+0x6e)[0xb1705e]
    (ab_GetView+0xc1d)[0xb0ee1d]
    (_Z20CompressInitRcByDatajPK6CG_DIRjjS1_jj4RUDIPKhj+0x60d)[0xe32b2d]
    (_Z21cg_CompressStackFrameP4TRIGjj+0x169)[0xe33399]
    (_Z8cg_blkleP3ENV+0x75f)[0xe4779f]
    (_Z9sc_cblklePKt8ENV_KINDP7SC_INFO+0x394)[0xe90024]
    (sc_blkle+0xdd)[0xec6e4d]
    (rs_oper_abap1729+0x37)[0x10eb237]
    (rs_expan_abap+0xa1996)[0xfd7a2a]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_inclu+0x5fa)[0xe0d50a]
    (rs_oper_abap2160+0x3a)[0x1115d6a]
    (rs_expan_abap+0xcd41d)[0x10034b1]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_checkStart+0x41)[0xe1ac51]
    (cg_generate+0xb65)[0xe57755]
    (ab_gabap+0x14a)[0xb01a5a]
    (dy_gen_abap+0x63c)[0x74428c]
    (ab_genprog+0x13d3)[0xb03d13]
    (_Z17ab_LoadProgOrTrfoPKtjPj+0xb56)[0x8f9ab6]
    (_Z11ab_LoadProgPKtj+0x11)[0x8f9ca1]
    (_Z15LoadGlobalClassPKtjjj9ClasState+0x24c)[0x958c2c]
    (_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x214)[0x957404]
    (_Z11ab_FillCfixtj+0x65)[0x957ae5]
    (_Z26ab_CrefToCladId_ActivateOKtPh+0x7d)[0x957b6d]
    (_Z8ab_jaboov+0x623)[0x959793]
    (_Z8ab_extriv+0x607)[0x8ba9c7]
    (_Z9ab_xeventPKt+0x1c1)[0xa1c021]
    (_Z8ab_triggv+0x9c)[0xa1c77c]
    (ab_run+0x97)[0xbde5c7]
    (N_ab_run+0x9)[0x736359]
    (dynpmcal+0x669)[0x7333b9]
    (dynppai0+0x8eb)[0x734d9b]
    (dynprctl+0x3e9)[0x733db9]
    (dynpen00+0x4a5)[0x726eb5]
    (Thdynpen00+0x359)[0x541bd9]
    (TskhLoop+0xc49)[0x54d999]
    (ThStart+0x20f)[0x55b29f]
    (DpMain+0x2da)[0x4bd49a]
    (nlsui_main+0x9)[0x4910c9]
    (main+0x33)[0x491103]
    /lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x3cde51c3fb]
    Please help me to resolve the issue.
    Thanks & Regards
    SKK

    read this part again:  The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY" changed during the flow of the transaction. As the type was already used in the old version and in the new type should be used in the same transaction in the new version, the transaction had to be cancelled to avoid inconsistencies. How to correct the error Try to restart the program
    how often had you restarted ME21N before you posted this message?
    In best case this message appears only once, because the program / or dictionary was changed while you executed ME21N
    If many times, then contact your ABAPer, because then he probably did not transport all objects that were changed, or the objects have to be regenerated in your system.

  • ME21N, ME22N, ME23N call ME12 instead of ME13

    Hi
    Our users would like to be able to go from ME21N, ME22N, ME23N and directly to ME12, so that they can make changes in the info records.
    As standard the transaction codes ME21N, ME22N, ME23N calls up ME13 which is display mode of the info recrod.
    I have some concerns to make this change and that is weather the changes made in ME12 will take effect in ME21N if they are creating a PO and want to make changes to the info record.
    The other thing is that it might be difficult to control the changes made in the info records if it is possible to do this "on the fly" and not consider the consequenses of the change, other than to satisfy and here-and-now need for a certain issue.
    If we want to proceed with this, how would I do this the best way to call up ME12 in stead of ME13.
    Best regards
    Birgitte Hamborg Jakobsen

    Hi,
       I cant understand why you want to go to ME12 directly instead of ME13 from ME2*N transactions. In case the user want to change anything, he can go to menu - info record - change from ME13 directly. I dont think its worth spending time and effort to change it to ME12.
       Even though you change anything in info record from ME2*N transactions, the changes wont reflect back to your PO. The changes will be reflected in new PO only, not in already created documents.
    Regards,
    AKPT

  • Print preview in ME21N/ME22N/ME23N

    Hi!
    In transactions ME21N/ME22N/ME23N we can see PO print preview after we click Print preview button.
    Is it possible to deactivate upper toolbar in this preview??
    Or deactivate:  Go to -> 'View list'   in this toolbar?

    Thanks for your answers.
    Now, I have another question:
    How can I transport transaction variant assigning??
    On developer system I created transaction variant, variant group and assigned users to it.
    It works perfectly.
    Transaction variant and variant group I assigned to Workbench request and transported it to Test System 1 (TE1)
    Assigning user to variant group I assigned to Customizing transport and transported to Test System 1 (TE1).
    However it doesn't work correctly on TE1.
    I have to go again into SHD0 on TE1 and assign users to variant group. Then it works.
    Now I have acces to TE1 to SHD0 but I will don't have it soon.
    How can I transport transaction variant assigning??
    How can I activate my variant globally?  For all users??
    I typed * in User field. Is it correctly??
    regards,
    Michal

  • Material descri screen level field greyout in ME21N/ME22N/ME23N-Urgent

    Hi,
    I have a requirement in ME21N/ME22N/ME23N is that when i want to change a PO, the material short description field should be grey out after the material is entered in the item level.
    Can anybody suggest me how to do screen level field greyout in ME21N/ME22N/ME23N.
    Thanks in advance,
    Esaki

    Hi,
    This query can be solved by modifying some configuration part. Your MM consultant in project can do this or you can also try this following meintioned path: Goto tcode SPRO
    SPRO>Materials Management>Purchase Order-->Define Screen layout at document level.
    In this screen layout for the mentioned transactions ME21N/ME22N/ME23N ,material short description field can be greyed out by selecting display mode for that field.
    For more clarification refer documentation against this point in SPRO.
    Hope this solves your problem.
    Regards,
    Brajvir

Maybe you are looking for