Exit for Modifying screen attributes during ME22N

Hi Experts,
I need to make some fields output only at item level in transaction ME22N i.e. during PO change. Is there any exit or BADI available for that.
Regards

> Hi Experts,
>
> I need to make some fields output only at item level
> in transaction ME22N i.e. during PO change. Is there
> any exit or BADI available for that.
>
> Regards
This is mainly config.
Check in SPRO - IMG
Materials Management > Purchasing > Purchase Order > Define Screen Layout at Document Level
Also these BAdis are available:
ME_PROCESS_PO_CUST - For Custom logic in Enjoy transactions
ME_GUI_PO_CUST - For Additional Custom screens in ME2xn
Read the documentation, it will help.
Also, read the config section about enhancements in Purchasing using old enhancement technology. See below.
OSS is also a good place for documentation. OSS 496083.
Good luck!
Leonardo De Araujo
Develop Enhancements for Purchasing
     In this step, you develop enhancements for Purchasing.
     The following SAP enhancements are available for the Purchasing area:
     o   AMPL0001
         User subscreen for additional AMPL data (Manufacturer part number)
     o   LMELA002
         Adoption of batch number from shipping notification at time of
         posting of a goods receipt
     o   LMELA010
         Incoming shipping notification: adoption of item data from IDoc
     o   LMEQR001
         User exit for source determination
     o   M06B0001
         Role determination for release of requisitions
     o   M06B0001
         Changes to communication structure for release of requisitions
     o   M06B0003
         Number range and document number
     o   M06B0004
         Number range and document number
     o   M06B0005
         Changes to communication structure for overall release of purchase
         requisitions
     o   M06E0004
         Changes to communication structure for release of purchasing
         document
     o   M06E0005
         Role determination for release of purchasing documents
     o   ME590001
         Grouping of requisitions for PO split in transaction ME59
     o   MEETA001
         Determination of schedule line type (backlog, immediate requirement,
         forecast)
     o   MEFLD004
         Determination of earliest delivery date for checking at time of
         goods receipt (PO only)
     o   MELAB001
         Generation of forecast delivery schedule: realization via creation
         profile
     o   MEQUERY1
         Enhancement for document overview ME21N / ME51N
     o   MEVME001
         Calculation of default GR quantity and over/underdelivery tolerances
     o   MM06E001
         User exits for inbound EDI messages and outbound purchasing
         documents
     o   MM06E003
         Number range and document number
     o   MM06E004
         Control of import data screens in purchase orders
     o   MM06E005
         Customer fields in purchasing documents
     o   MEREQ001
         Customer's own data in purhcase requisitions
     o   MM06E007
         Change document for requisitions when converting into POs
     o   MM06E008
         Monitoring of contract target value in case of release orders
     o   MM06E009
         Relevant texts for "Texts exist" indicator
     o   MM06E010
         Field selection for vendor address
     o   MM06E011
         Activation of requisition block
     o   MM06L001
         Exits for determination of ratings in vendor evaluation
     o   MMAL0001
         ALE source list distribution: outbound processing
     o   MMAL0002
         ALE source list distribution: inbound processing
     o   MMAL0003
         ALE purchasing info record distribution: outbound processing
     o   MMAL0004
         ALE purchasing info record distribution: inbound processing
     o   MMDA0001
         Default values for delivery addresses
     o   MMFAB001
         User exit for generation of releases
     o   MRFLB001
         Control items during release creation
     o   LWBON001
         Enhancement of LIS update through extension of the communication
         structure MCKONA (business volumes and rebate income)
     o   LWBON003
         Change settlement data for end-of-period rebate settlement before
         creation of settlement documents
     o   LWSUS001
         Customer-specific source determination in Retail
     Activities
     1. Either create a new project or use an existing one and then enter
         the enhancement.
     2. Activate the project
         Your enhancement will only become effective after activation.
     Further notes
     In contrast to modifications, enhancements are basically
     release-insensitive since they are not implemented in the SAP original
     but in a name range that is reserved for the customer.
     The general procedure for creating enhancements can be found in the
     enhancement transaction at Help -> Application help.
     If you want to display the documentation for an enhancement, choose Goto
     -> Documentation in the enhancement transaction.
Return ->
     Application

Similar Messages

How to find the user exit for a screen..

Hi,
plz help me how to find the user exit for a screen..?
Regards
Anbu

Hi,
check this program this will give you the list of user-exit and BADI for the perticular Tcode.
REPORT zuserexit_badi.
TABLES : tstc,
tadir,
modsapt,
modact,
trdir,
tfdir,
enlfdir,
sxs_attrt ,
tstct.
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
PARAMETERS : p_tcode LIKE tstc-tcode,
p_pgmna LIKE tstc-pgmna .
DATA wa_tadir TYPE tadir.
START-OF-SELECTION.
IF NOT p_tcode IS INITIAL.
    SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.
ELSEIF NOT p_pgmna IS INITIAL.
    tstc-pgmna = p_pgmna.
ENDIF.
IF sy-subrc EQ 0.
    SELECT SINGLE * FROM tadir
    WHERE pgmid = 'R3TR'
    AND object = 'PROG'
    AND obj_name = tstc-pgmna.
    MOVE : tadir-devclass TO v_devclass.
    IF sy-subrc NE 0.
      SELECT SINGLE * FROM trdir
      WHERE name = tstc-pgmna.
      IF trdir-subc EQ 'F'.
        SELECT SINGLE * FROM tfdir
        WHERE pname = tstc-pgmna.
        SELECT SINGLE * FROM enlfdir
        WHERE funcname = tfdir-funcname.
        SELECT SINGLE * FROM tadir
        WHERE pgmid = 'R3TR'
        AND object = 'FUGR'
        AND obj_name EQ enlfdir-area.
        MOVE : tadir-devclass TO v_devclass.
      ENDIF.
    ENDIF.
    SELECT * FROM tadir INTO TABLE jtab
    WHERE pgmid = 'R3TR'
    AND object IN ('SMOD', 'SXSD')
    AND devclass = v_devclass.
    SELECT SINGLE * FROM tstct
    WHERE sprsl EQ sy-langu
    AND tcode EQ p_tcode.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    SKIP.
    IF NOT jtab[] IS INITIAL.
      WRITE:/(105) sy-uline.
      FORMAT COLOR COL_HEADING INTENSIFIED ON.
Sorting the internal Table
      SORT jtab BY object.
      DATA : wf_txt(60) TYPE c,
      wf_smod TYPE i ,
      wf_badi TYPE i ,
      wf_object2(30) TYPE c.
      CLEAR : wf_smod, wf_badi , wf_object2.
Get the total SMOD.
      LOOP AT jtab INTO wa_tadir.
        AT FIRST.
          FORMAT COLOR COL_HEADING INTENSIFIED ON.
          WRITE:/1 sy-vline,
          2 'Enhancement/ Business Add-in',
          41 sy-vline ,
          42 'Description',
          105 sy-vline.
          WRITE:/(105) sy-uline.
        ENDAT.
        CLEAR wf_txt.
        AT NEW object.
          IF wa_tadir-object = 'SMOD'.
            wf_object2 = 'Enhancement' .
          ELSEIF wa_tadir-object = 'SXSD'.
            wf_object2 = ' Business Add-in'.
          ENDIF.
          FORMAT COLOR COL_GROUP INTENSIFIED ON.
          WRITE:/1 sy-vline,
          2 wf_object2,
          105 sy-vline.
        ENDAT.
        CASE wa_tadir-object.
          WHEN 'SMOD'.
            wf_smod = wf_smod + 1.
            SELECT SINGLE modtext INTO wf_txt
            FROM modsapt
            WHERE sprsl = sy-langu
            AND name = wa_tadir-obj_name.
            FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
          WHEN 'SXSD'.
For BADis
            wf_badi = wf_badi + 1 .
            SELECT SINGLE text INTO wf_txt
            FROM sxs_attrt
            WHERE sprsl = sy-langu
            AND exit_name = wa_tadir-obj_name.
            FORMAT COLOR COL_NORMAL INTENSIFIED ON.
        ENDCASE.
        WRITE:/1 sy-vline,
        2 wa_tadir-obj_name HOTSPOT ON,
        41 sy-vline ,
        42 wf_txt,
        105 sy-vline.
        AT END OF object.
          WRITE : /(105) sy-uline.
        ENDAT.
      ENDLOOP.
      WRITE:/(105) sy-uline.
      SKIP.
      FORMAT COLOR COL_TOTAL INTENSIFIED ON.
      WRITE:/ 'No.of Exits:' , wf_smod.
      WRITE:/ 'No.of BADis:' , wf_badi.
    ELSE.
      FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
      WRITE:/(105) 'No userexits or BADis exist'.
    ENDIF.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(105) 'Transaction does not exist'.
ENDIF.
AT LINE-SELECTION.
DATA : wf_object TYPE tadir-object.
CLEAR wf_object.
GET CURSOR FIELD field1.
CHECK field1(8) EQ 'WA_TADIR'.
READ TABLE jtab WITH KEY obj_name = sy-lisel+1(20).
MOVE jtab-object TO wf_object.
CASE wf_object.
    WHEN 'SMOD'.
      SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
      CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
    WHEN 'SXSD'.
      SET PARAMETER ID 'EXN' FIELD sy-lisel+1(20).
      CALL TRANSACTION 'SE18' AND SKIP FIRST SCREEN.
ENDCASE.
Reagards,
Bharat.

User exit for MB1A screen

I want to block the withdraw qty in MB1A screen.I used MBCFC003 AND MBCF0005 BUT I couldn't get the exact result.Is it user exit for MB1A screen -PPC00009.So can anyone tell me the exact user exit.
Regards,
Maran.d

Dear Maran,
What's your exact requirement?What do you want to block in MB1A T Code?
You want to restrict for 261 movement for an order or reservation in MB1A?
These are the exits that can be used for MB1A,
MB_CF001                                Customer Function Exit in the Case of Updating a Mat. Doc.
MBCF0011                                Read from RESB and RKPF for print list in MB26
MBCF0010                                Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0009                                Filling the storage location field
MBCF0007                                Customer function exit: Updating a reservation
MBCF0006                                Customer function for WBS element
MBCF0005                                Material document item for goods receipt/issue slip
MBCF0002                                Customer function exit: Segment text in material doc. item
Regards
S Mangalraj

How to find screen exit for a screen?

Hi,
If you know the transaction, how to find if there is a screen exit exists or not?
Here even I know the screen number also. I have opened it in screen painter. How can I see if there is a screen exit for the screen?
Thank you.

Hii
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
Screen exit
Regards
Naresh

Screen /user exit for additional screen on sales order header

Hello sir's,
can anybody help me for this query---
Screen /user exit for additional screen on sales order header.
exit name.
Thanks in advance,
Vikram

Hi,
SAP has provided screen modification. This you can do on "Additional data B" screen at both header and line iteam level.
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 ( this is the screen exit at header ) or SAPMV45A 8459 ( this is the screen exit at item ) as user exits. There few more exits you will have to code to get this screen works. The are,
MV45AOZZ - PBO module of screen
MV45AIZZ - PAI module of screen
MV45ATZZ - Global data definition for user-exit.
Check this link for more info regarding user-exit in sales docs.
http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/frameset.htm
We have alredy implemented this solution at line item level. Let me know if you have any question.
Regards,
RS

User exit for Exchange rate in PO (ME22n) of Delivery/invoice Tab

Hi SDN,
We are using 4.6c. I wanna make the FIELD "Exchange rate" in Purchase Order (Tx: ME22n) of Delivery/invoice Tab into display mode. So can any one tell the USER EXIT i have to use to make SCREEN-INPUT = 0 for this screen field, MEPO1226-WKURS.
Thanks in Advance.
Regards
Basha

Transaction Code - ME22N                    Change Purchase Order
Exit Name           Description
LMEDR001            Enhancements to print program
LMELA002            Adopt batch no. from shipping notification when posting a GR
LMELA010            Inbound shipping notification: Transfer item data from IDOC
LMEQR001            User exit for source determination
LMEXF001            Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001            Customer-Specific Source Determination in Retail
M06B0001            Role determination for purchase requisition release
M06B0002            Changes to comm. structure for purchase requisition release
M06B0003            Number range and document number
M06B0004            Number range and document number
M06B0005            Changes to comm. structure for overall release of requisn.
M06E0004            Changes to communication structure for release purch. doc.
M06E0005            Role determination for release of purchasing documents
ME590001            Grouping of requsitions for PO split in ME59
MEETA001            Define schedule line type (backlog, immed. req., preview)
MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1            Enhancement to Document Overview ME21N/ME51N
MEVME001            WE default quantity calc. and over/ underdelivery tolerance
MM06E001            User exits for EDI inbound and outbound purchasing documents
MM06E003            Number range and document number
MM06E004            Control import data screens in purchase order
MM06E005            Customer fields in purchasing document
MM06E007            Change document for requisitions upon conversion into PO
MM06E008            Monitoring of contr. target value in case of release orders
MM06E009            Relevant texts for "Texts exist" indicator
MM06E010            Field selection for vendor address
MMAL0001            ALE source list distribution: Outbound processing
MMAL0002            ALE source list distribution: Inbound processing
MMAL0003            ALE purcasing info record distribution: Outbound processing
MMAL0004            ALE purchasing info record distribution: Inbound processing
MMDA0001            Default delivery addresses
MMFAB001            User exit for generation of release order
MRFLB001            Control Items for Contract Release Order
AMPL0001            User subscreen for additional data on AMPL
No of Exits:         35
USER EXIT
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.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Rewards if useful.........
Minal

Field Exit for VA11 screen ?

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

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

PPCO0007 User Exit for Changing Header Fields During Order (CO40)

.. Hi !!!!
I need your help or suggestions,
I need to change the standar order before to save, i found the user exit PPCO0007,
i assign the new value for the order, but when finish the fuction, EXIT_SAPLCOZV_001, the new values are
lost, and finally the system set the standard order.
Someona know how can change the order and the the batch.
Thanks
Noemí Huerta

Hi Noemi
You can use the enchancement PPCO0007 (exit when the production order is saved).
Use the function module EXIT_SAPLCOZV_001 (User Exit for Checking or Changing Header Fields During Order Save) to update the field priority starting the information in the material-customer info record.

User exit for Production order confirmation during goodsmovement

Hi Guru's
Am in need to find the user exit for Equipment master creation. Equipmentmaster will be created when the goods movement 101 happens. can someone help me out to find the user exits. thanks

Hi,
Ok thanks for that.For Co11n please find the user exits below.But i am not sure which will suit your requirment.Please let me know for any further help.
CONF0001 Enhancements in order confirmation
CONFPI01 Process order conf.: Calculate cust.specific default va
CONFPI02 Process order confirmation: Customer spec. input checks
CONFPI03 Process order conf.: Cust. spec. check after op. select
CONFPI04 Process order conf.: Customer specific input checks 2
CONFPI05 Process order conf.: Cust. spec. enhancements when savi
CONFPI06 Process order confirmation: Actual data transfer
CONFPM01 PM/SM order conf.: Determine cust. specific default val
CONFPM02 PM/SM order confirmation: Customer specific input check
CONFPM03 PM/SM order conf.: Cust. spec. check after op. selectio
CONFPM04 PM/SM order conf.: Customer specific input check 2
CONFPM05 PM/SM order conf.: Cust. specific enhancements when sav
CONFPP01 PP order conf.: Determine customer specific default val
CONFPP02 PP order conf.: Customer specific input checks 1
CONFPP03 PP order conf.: Cust. specific check after op. selectio
CONFPP04 PP order conf.: Customer specific input checks 2
CONFPP05 PP order conf.: Customer specific enhancements when sav
CONFPP06 PP Order Confirmations: Actual Data Transfer
CONFPP07 Single Screen Entry: Inclusion of User-Defined Subscree
CONFPS01 PS confirmation: Determine customer specific default va
CONFPS02 PS confirmation: Customer specific input checks 1
CONFPS03 PS confirmation: Customer specific check after op. sele
CONFPS04 PS confirmation: Customer specific input checks 2
CONFPS05 PS confirmation: Customer specific enhancements when sa
Thanks,

User exit for modify miro

Hi all,
i want user exit for miro. it's trigers when i enter purchase order no.
also i want modify item data after enter purchase order no.
please help me.
Thanks,

Hi,
These are the available user-exits in MIRO:
Exit Name           Description
LMR1M001            User exits in Logistics Invoice Verification
LMR1M002            Account grouping for GR/IR account maintenance
LMR1M003            Number assignment in Logistics Invoice Verification
LMR1M004            Logistics Invoice Verification: item text for follow-on docs
LMR1M005            Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006            Logistics Invoice Verification: Process XML Invoice
MRMH0001            Logistics Invoice Verification: ERS procedure
MRMH0002            Logistics Invoice Verification: EDI inbound
MRMH0003            Logistics Invoice Verification: Revaluation/RAP
MRMN0001            Message output and creation: Logistics Invoice Verification
regards
Aveek

User exit to modify likp-vsbed during the creation of the delivery

Hi ,
I need to find an exit to modify LIKP-VSBED while I am trying to create a delivery(VL01N) from a sales order . I did not find any exits . Also when I referred to the OSS notes , I found this note elevant 396378 . From the note I guess it is not possible to modify the above said field .
Can anyone help me out with this .
Regards ,
Varun .
Message was edited by:
        varun sonu

Hi,
In the include MV50AFZ1 check the following user exit
      FORM USEREXIT_MOVE_FIELD_TO_LIKP                              *
      This userexit can be used to move some fields into the        *
      delivery header workaerea LIKP.                               *
      This form is called, when a header is created                 *
      This form is called at the end of form LIKP_FUELLEN.          *
FORM USEREXIT_MOVE_FIELD_TO_LIKP.
Thanks,
Naren

User Exit for PO creation(me21n and me22n) - A/c assgn Category is existing

Hi all,
I would like to have your guidance to find out an appropriate EXIT to meet the following req.
Requirement is such that : This EXIT should generate a G/L account automatically (or over-write the existing G/L a/c) during any PO creation(me21n and me22n tcodes - before saving) based on the fields(mandatory) :
A/c Assignment Category,
Material,
Company code and
Vendor
entered by the user(during his/her PO creation activity)
The identified EXITS as of now are EXIT_SAPLEBND_002 (But the package is not matching our PO tcodes : me21n and me22n)
and EXIT_SAPMM06E_017(Package ME- same as tcodes me21n,me22n)
and even other Exits available for PO based on before saving activity.
Even I tried out creating a PO in debugging mode(with break points set at the above EXITs).
Please do help me out at the earliest to identify the appropriate EXIT to meet this requirement.
With Regards,
Srividya

Hi!
in SMOD give MM06E005 enhancement
FM name
EXIT_SAPMM06E_017
This will be triggered during saving.
Regards
Tamá

User exit for component data in ME21n/ME22n

Hello,
I have a requirement to issue an error message if a component quantity is not evenly divisible by the end item quantity. The component data (BOM) is entered after clicking the components button on ME21n/ME22n at the item level detail. I need to evaluate the data after a user clicks save, but I cannot find a user exit where the data is passed into, or where it is defined as global data where I can reference it in a user exit. The data is stored on the screen in structure MDPM and stored in the database in table RESB.
I appreciate any help,
David

Thanks for pointing me in the right direction.
I was able to put my code in EXIT_SAPMM06E_012 and retrieve the component data through (SAPLEINK)XMDPM[]
Below is the code I used to assign the data to be able to evaluate it.
FIELD-SYMBOLS: <z_mdpm_x> TYPE ANY.
DATA: i_mdpm_x TYPE STANDARD TABLE OF MDPM_X.
Fetching Component data
ASSIGN ('(SAPLEINK)XMDPM[]') to <z_mdpm_x>.
CHECK sy-subrc = 0.
Assigning data into an internal table
i_mdpm_x[] = <z_mdpm_x>.
CHECK i_mdpm_x[] IS NOT INITIAL.
David
Edited by: David Herrema on Oct 20, 2010 3:03 PM

Screen exit for RF screen LM61

Hi all,
I have created a screen exit SAPLXLHU 1765 for the dummy RF screen SAPLLMOB 1765.
The new screen has to be part of the XLHU function group, as the screen to be modified is for packing by delivery through the RF transaction LM61.
I have saved this new screen as a local object. and now I am unable to change it or move it into a workbench request by changing the dev class. Even if I delete the screen and create it again it directly saves it as a local object without promting for the development class.
Is there any other way to assign this to the request.
Thanks in advance
Sheetal.

Hi Sheetal,
Very interesting, I to am working on a similar enhancement for an RF screen in SAPLXLRF (not SAPLXLHU but the concept is the same). I also saved the enhancement screen as a local object to allow testing but can no longer add it to a development package or transport. Even if I delete and recreate the screen, it still ends up as local.
I do not need to transport the enhancement screen as yet but will in future. I was thinking of raising a customer message with SAP to see if they could help.
Let me know if you manage to find a solution.
Regards
Che

User exit for selection screen of Tcode VL31N, VL32N

Dear Experts,
I want to modify selection screen of tcode VL31N, VL32N. Please help me to send user exit Tcode VL31N, VL32N.
Thanks and regards,
DucTV1.

Hi Patrik,
The ALV report is generating from a query AQZZ/SAPQUERY/MEMEVL31========, in which the field catalogue of the ALV is coming from normal list dispaly structure only, structure of which is coming from %goo structure.
Either try to find out an enhancement here , so that you can add fields over there.
Thanks and Regards,
Antony Thomas

Exit for Modifying screen attributes during ME22N

Similar Messages

Maybe you are looking for