USER EXIT BY TCODE MIGO

Hi to all
I need do it, a enhancement by the transaction MIGO, just when the document is saved.
Somebody knows, an enhacement in particular ??
Thank by their aid.
regards
Dario

Hi,
Assuming this is your requirement..
Store the MKPF & MSEG details in a Z table...when the material document is created..
Solution
1)
Create a function module Z_ADD_ZTABLE..Which should be remote enabled..
Give the parameter..
You can select on MKPF and MSEG with the material document number that has been just posted...The values are available in XMKPF-MBLNR..
Example.
SELECT SINGLE * FROM MKPF WHERE MBLNR = XMKPF-MBLNR.
****The return code will be zero..Means the record is available in the database.
2)
IN the BADI MB_DOCUMENT_BADI or in the USER EXIT...
CALL the function module in BACKGROUND TASK..
Example
CALL FUNCTION 'Z_ADD_ZTABLE' IN BACKGROUND TASK
         Exporting
Hope this is clear..
Thanks,
Naren

Similar Messages

  • User exit for  tcode migo

    hi all,
    plz solve my problem.
    how to find a badi  for tcode migo  ?
    wher to write code?
    can any bodysuggest me?
    thanks
    sachhidananda

    Hi Sachhidananda,
    MIGO belongs to MB Package
    These are the BAdI's for MB package.
    MB_CHECK_LINE_BADI..............BAdI: Check Line Before Copying to the Blocking Tables
    MB_CIN_LMBMBU04...................posting of gr
    MB_CIN_MM07MFB7...................BAdI for India Version exit in include MM07MFB7
    MB_CIN_MM07MFB7_QTY...........Proposal of quantity from Excise invoice in GR
    MB_DOCUMENT_BADI................ BAdIs when Creating a Material Document
    MB_DOCUMENT_UPDATE ..........BADI when updating material document: MSEG and MKPF
    MB_MIGO_BADI .........................BAdI in MIGO for External Detail Subscreens
    MB_MIGO_ITEM_BADI ................BAdI in MIGO for Changing Item Data
    MB_RESERVATION_BADI............MB21/MB22: Check and Complete Dialog Data
    After finding the appropriate BAdI u need to Implement the BAdI in SE19 Tcode.
    In SE19 , give the Implementation name and click on create  pushbutton then u get a popup Definition Name. Give the Definition Name and click on Enter (Continue).
    Here u can see all the Methods in Interface Tab.
    U need to select the Appropriate METHOD and in that METHOD u need to write the Code.
    For Example
    Best regards,
    raam

  • User Exit for TCode CJ20N to populate Project system user fields

    Hi team,
    need one support from your side..
    I am looking for User Exit for TCode CJ20N to populate Project system user fields on SAVE.
    I have found
    Enhancement        CNEX0001
    Short text         PS: User field
    which is exactly suiting my req...as it has USER Fields (USR08/USR09 )in export paramters..
    BUT it is not triggering on SAVE,,
    Any hint or is any other user exit/badi which have USER Fields in export paramters.
    Warm Regards
    Krishan

    Hi Krishnan,
    If you want a custom tab that contains User defined fields at Project level then you have to use CNEX0006 user exit. Before this you must declare your fields using the CI include CI_PROJ in the PROJ table.
    If you want a custom tab that contains User defined fields at WBS level then you have to use CNEX0007 user exit. Before this you must declare your fields using the CI include CI_PRPS in the PROJ table.
    In the PBO function module exit of these exits you must use the following statements as the first statement.
    MOVE-CORRESPONDING sap_proj_imp TO proj.
    MOVE-CORRESPONDING sap_prps_imp TO prps.
    In the PAI function module exit of these exits you must use the following statement as the last statement.
    MOVE-CORRESPONDING proj TO cnci_proj_exp.
    MOVE-CORRESPONDING prps TO cnci_prps_exp.
    The remaining programming as in the case any Screen Exit.
    Regards,
    Abijith

  • User exits for Tcode FCH5

    May any one of you plz suggest me any userexits for tcode fch5.
    i want to restrict the field  of account id for validation.
    how can i do this.
    waiting for your reply.

    Hi Pawan,
    U can use this program to find user exit for Tcode FCH5
    Find User exit for Tcode
    REPORT z_find_userexit NO STANDARD PAGE HEADING.
    *&  Enter the transaction code that you want to search through in order
    *&  to find which Standard SAP User Exits exists.
    *& Tables
    TABLES : tstc,     "SAP Transaction Codes
             tadir,    "Directory of Repository Objects
             modsapt,  "SAP Enhancements - Short Texts
             modact,   "Modifications
             trdir,    "System table TRDIR
             tfdir,    "Function Module
             enlfdir,  "Additional Attributes for Function Modules
             tstct.    "Transaction Code Texts
    *& Variables
    DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
    DATA : field1(30).
    DATA : v_devclass LIKE tadir-devclass.
    *& Selection Screen Parameters
    SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
    SELECTION-SCREEN SKIP.
    PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
    SELECTION-SCREEN SKIP.
    SELECTION-SCREEN END OF BLOCK a01.
    *& Start of main program
    START-OF-SELECTION.
    Validate Transaction Code
      SELECT SINGLE * FROM tstc
        WHERE tcode EQ p_tcode.
    Find Repository Objects for transaction code
      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 = enlfdir-area.
            MOVE : tadir-devclass TO v_devclass.
          ENDIF.
        ENDIF.
    Find SAP Modifactions
        SELECT * FROM tadir
          INTO TABLE jtab
          WHERE pgmid    = 'R3TR'
            AND object   = 'SMOD'
            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:/(95) sy-uline.
          FORMAT COLOR COL_HEADING INTENSIFIED ON.
          WRITE:/1 sy-vline,
          2 'Exit Name',
          21 sy-vline ,
          22 'Description',
          95 sy-vline.
          WRITE:/(95) sy-uline.
          LOOP AT jtab.
            SELECT SINGLE * FROM modsapt
            WHERE sprsl = sy-langu AND
            name = jtab-obj_name.
            FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
            WRITE:/1 sy-vline,
            2 jtab-obj_name HOTSPOT ON,
            21 sy-vline ,
            22 modsapt-modtext,
            95 sy-vline.
          ENDLOOP.
          WRITE:/(95) sy-uline.
          DESCRIBE TABLE jtab.
          SKIP.
          FORMAT COLOR COL_TOTAL INTENSIFIED ON.
          WRITE:/ 'No of Exits:' , sy-tfill.
        ELSE.
          FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
          WRITE:/(95) 'No User Exit exists'.
        ENDIF.
      ELSE.
        FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
        WRITE:/(95) 'Transaction Code Does Not Exist'.
      ENDIF.
    Take the user to SMOD for the Exit that was selected.
    AT LINE-SELECTION.
      GET CURSOR FIELD field1.
      CHECK field1(4) EQ 'JTAB'.
      SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
      CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
    Rgds,
    Prakash

  • User exit/Badi in MIGO after save

    hi all
    I am trying to find a user-exit/BAdi in tcode MIGO.
    This one should be called after saving the MIGO document.
    Using this i want to put control over auto TO creation for some specific plants and storage locations.
    Important thing is I am using version 4.6C.

    Hi,
    Please try the last one. This may suit.
    For "Automatic TO creation (background processing)", the following user exits are available:
    MWMTOAU1 Selection of requirements for automatic creation of orders.
    MWMTOAU2 Reference number assignment.
    MWMTOAU3 Selection of posting change notices for automatic creation of transfer orders.
    Thanks and Regards
    Guru

  • User exit MB_CF001 in MIGO

    Folks,
    I am using the user exit MB_CF001 to get the data from  XMSEG table and send it to an external system. I was asked to call an RFC function module in this user exit to send the XMSEG data to an external system but the user exit documentation clearly says not to use RFC function call in this user exit.
    I also heard that I can do this by using the idocs that get posted after MIGO is done. Could anyone give me step by step procedure how to do this as I am new to IDOCS.
    Points will be rewarded for best answers.
    Thanks,
    Alok

    Dear Alok,
    Below is a documentation about IDOCs. Hope it will be useful to you.
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    Important links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    >SAP ALE & IDOC
    Steps to configuration(Basis)
    >>1. Create Logical System (LS) for each applicable ALE-enabled client
    >>2. Link client to Logical System on the respective servers
    >>3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    >>4. Create RFC Destinations(SM59)
    >>5. Ports in Idoc processing(WE21)
    >>6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    >Steps to customize a new IDoc
    >>1. Define IDoc Segment (WE31)
    >>2. Convert Segments into an IDoc type (WE30)
    >>3. Create a Message Type (WE81)
    >>4. Create valid Combination of Message & IDoc type(WE82)
    >>5. Define Processing Code(WE41 for OUT / WE42 for IN)
    >>6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Best Regards,
    Rajesh.
    Please reward points if found helpful.

  • User exit/BADI for MIGO Batch numbers

    Hi All,
    I want to find a user exit which will give the oldest batch number (MCHA-LWDET) of semi-finished product during the goods receipts of the finished prodocut in MIGO.
    Could you please give me any hints to find out the user exit for this.
    Regards,
    Sekhar D

    Hi,
    Check these User exits... for MIGO
    Exit Name           Description
    MBCF0002            Customer function exit: Segment text in material doc. item
    MBCF0005            Material document item for goods receipt/issue slip
    MBCF0006            Customer function for WBS element
    MBCF0007            Customer function exit: Updating a reservation
    MBCF0009            Filling the storage location field
    MBCF0010            Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MBCF0011            Read from RESB and RKPF for print list in  MB26
    MB_CF001            Customer Function Exit in the Case of Updating a Mat. Doc.
    Check thse BADI's.. for MIGO
    Badi Name          
    ARC_MM_EBAN_CHECK   
    ARC_MM_EBAN_WRITE   
    ARC_MM_EINA_WRITE   
    ARC_MM_INVBEL_WRITE 
    ARC_MM_MATBEL_CHECK 
    ARC_MM_MATBEL_WRITE 
    MB_CHECK_LINE_BADI  
    MB_CIN_MM07MFB7     
    MB_CIN_MM07MFB7_QTY 
    MB_DOCUMENT_BADI    
    MB_DOCUMENT_BADI_SAP
    MB_DOCUMENT_BADI_SAP
    MB_DOC_BADI_INTERNAL
    MB_DOC_BADI_INTERNAL
    MB_ME_CSGMT_BADI_SAP RTFASH:
    MB_MIGO_BADI        
    MB_MIGO_ITEM_BADI   
    MB_PHYSINV_INTERNAL  MB_PHYSINV_INTERNAL BAdI Implementation
    MB_RESERVATION_SCR   DFPS: Field in the Reservation
    MB_RESERVATION_UPCHD DFPS: Reservation
    Regards,
    Raghu
    Edited by: Raghavendra  Rao G on Aug 27, 2009 5:50 PM

  • User exit for tcode ME21N and ME22N

    Hi everyone
    Can anybody tell me the user exits found in the tcodes ME21N nad ME22N, when saving a PO?
    Regards
    Anjali

    AMPL0001            User subscreen for additional data on AMPL
    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            Individual customer 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.
    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
    MEQUERY1            Enhancement to Document Overview ME21N/ME51N
    MM06E011            Activate PReq Block
    LMEKO001            Extend communications structure KOMK for pricing
    LMEKO002            Extend communications structure KOMP for pricing
    If useful reward.
    Vasanth

  • BADi/User Exit in J1IEX/MIGO

    Hi.,
    While capturing excise invoice in MIGO, iI wanna to make excise material type NONCENVATABLE as default for those items which has JMIP (Inventorized duty) in Purchase Order.If the material is maintained as Raw/asset/consumable/tools & if JMIP condition is maintained for that material in PO,then while capturing excise invoice in MIGO,it should take the excise material type as NONCENVATABLE.
    Are there any Badi/User Exits for this?
    Please guide on this issue
    Thanks & Regards,\

    Check with function module "J_1IEX_DETERMINE_CHAPTER_ID" & "J_1IEX_FILL_EXCISE_ITEMS"..

  • User exit for Tcode F-22.

    Hi guys.
    is there any user exit fot T-code F-22 to avoid duplicate invoice?

    available use exits are
    F050S001            FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
    F050S002            FIDCC1: Change IDoc/do not send                      
    F050S003            FIDCC2: Change IDoc/do not send                      
    F050S004            FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not se
    F050S005            FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI documen
    F050S006            FI Outgoing IDoc: Reset Clearing in FI Document      
    F050S007            FIDCCH Outbound: Influence on IDoc for Document Change
    F180A001            Balance Sheet Adjustment                             
    FARC0002            Additional Checks for Archiving MM Vendor Master Data
    RFAVIS01            Customer Exit for Changing Payment Advice Segment Text
    RFEPOS00            Line item display: Checking of selection conditions  
    RFKORIEX            Automatic correspondence                             
    SAPLF051            Workflow for FI (pre-capture, release for payment)   
    and you can find user exits for any transaction with the help of this code
    tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
             tables : 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 obligatory.
    select single * from tstc where tcode eq p_tcode.
    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 = 'SMOD'
                           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:/(95) sy-uline.
               format color col_heading intensified on.
               write:/1 sy-vline,
                      2 'Exit Name',
                     21 sy-vline ,
                     22 'Description',
                     95 sy-vline.
               write:/(95) sy-uline.
               loop at jtab.
                  select single * from modsapt
                         where sprsl = sy-langu and
                                name = jtab-obj_name.
                       format color col_normal intensified off.
                       write:/1 sy-vline,
                              2 jtab-obj_name hotspot on,
                             21 sy-vline ,
                             22 modsapt-modtext,
                             95 sy-vline.
               endloop.
               write:/(95) sy-uline.
               describe table jtab.
               skip.
               format color col_total intensified on.
               write:/ 'No of Exits:' , sy-tfill.
            else.
               format color col_negative intensified on.
               write:/(95) 'No User Exit exists'.
            endif.
          else.
              format color col_negative intensified on.
              write:/(95) 'Transaction Code Does Not Exist'.
          endif.
    at line-selection.
       get cursor field field1.
       check field1(4) eq 'JTAB'.
       set parameter id 'MON' field sy-lisel+1(10).
       call transaction 'SMOD' and skip first   screen.
    Message was edited by: Vijay Kumar Reddy

  • User Exits for Tcode FB50

    Hi,
    Is there a User exits that upon clicking of save button in Tcode FB50?
    thank you!!!
    james

    Hi,
    Below are the User exits(enhancement name) for transaction FB50
    Exit Name           Description
    F050S001            FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
    F050S002            FIDCC1: Change IDoc/do not send
    F050S003            FIDCC2: Change IDoc/do not send
    F050S004            FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
    F050S005            FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
    F050S006            FI Outgoing IDoc: Reset Clearing in FI Document
    F050S007            FIDCCH Outbound: Influence on IDoc for Document Change
    F180A001            Balance Sheet Adjustment
    FARC0002            Additional Checks for Archiving MM Vendor Master Data
    FEDI0001            Function Exits for EDI in FI
    RFAVIS01            Customer Exit for Changing Payment Advice Segment Text
    RFEPOS00            Line item display: Checking of selection conditions
    RFKORIEX            Automatic correspondence
    SAPLF051            Workflow for FI (pre-capture, release for payment)
    Best Regards,
    Brijesh

  • User exit/ Badi for Migo

    HI all,
    My requirement Is to POst another transaction at migo.
    lets say after transaction 909, i  have to create another material doc using
    BAPI_GOODSMVT_CREATE..
    Is there a User exit or Badi which is safe to use?...
    i am currently using
    EXIT_SAPMM07M_001 but there are times that locks entries are not
    yet removed from the first movement type(909).
    or any other approach with my requirement..?

    Hi,
    Steps to achieve..
    1) Create a FM in se37 with the "Remote enabled module" radio button enabled in the attributes tab..
    Do all your functionality in this Function module..
    2)
    In the exit EXIT_SAPLMBMB_001..
    Call the FM that you created above in BACKGROUND TASK..
    CALL FUNCTION 'Z_POST_NEW_DOCUMENT'
                      IN BACKGROUND TASK
    This will work...
    Thanks,
    Naren

  • User exits for tcode FBV0

    Hi,
    My requirement is that the user who has parked the document should not be able to post the parked document through tcode FBV0.
    Is there any user exit where in I can validate the current system user and the user who has parked the document?
    I have tried the user-exit SAPLF040,but this does not suffice my requirement.
    Also is it possible to define our own exits in tcode OB28?
    Regards,
    Rajeev

    Info on user exits can be found here http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    Transaction Code - FBV0                     Post Parked Document
    |Exit Name          |Description                                                              |
    |F050S001           |FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment                   |
    |F050S002           |FIDCC1: Change IDoc/do not send                                          |
    |F050S003           |FIDCC2: Change IDoc/do not send                                          |
    |F050S004           |FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send                 |
    |F050S005           |FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document                  |
    |F050S006           |FI Outgoing IDoc: Reset Clearing in FI Document                          |
    |F050S007           |FIDCCH Outbound: Influence on IDoc for Document Change                   |
    |F180A001           |Balance Sheet Adjustment                                                 |
    |FARC0002           |Additional Checks for Archiving MM Vendor Master Data                    |
    |RFAVIS01           |Customer Exit for Changing Payment Advice Segment Text                   |
    |RFEPOS00           |Line item display: Checking of selection conditions                      |
    |RFKORIEX           |Automatic correspondence                                                 |
    |SAPLF051           |Workflow for FI (pre-capture, release for payment)                       |
    No of Exits:         13
    These are the user exits possible for FBV0
    <b>we can find user exit for any transaction, copy and run the following code in SE38</b>
    report z_find_userexit no standard page heading.
    *&  Enter the transaction code that you want to search through in order
    *&  to find which Standard SAP User Exits exists.
    *& Tables
    tables : tstc,     "SAP Transaction Codes
             tadir,    "Directory of Repository Objects
             modsapt,  "SAP Enhancements - Short Texts
             modact,   "Modifications
             trdir,    "System table TRDIR
             tfdir,    "Function Module
             enlfdir,  "Additional Attributes for Function Modules
             tstct.    "Transaction Code Texts
    *& Variables
    data : jtab like tadir occurs 0 with header line.
    data : field1(30).
    data : v_devclass like tadir-devclass.
    *& Selection Screen Parameters
    selection-screen begin of block a01 with frame title text-001.
    selection-screen skip.
    parameters : p_tcode like tstc-tcode obligatory.
    selection-screen skip.
    selection-screen end of block a01.
    *& Start of main program
    start-of-selection.
    * Validate Transaction Code
      select single * from tstc
        where tcode eq p_tcode.
    * Find Repository Objects for transaction code
      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 = enlfdir-area.
            move : tadir-devclass to v_devclass.
          endif.
        endif.
    * Find SAP Modifactions
        select * from tadir
          into table jtab
          where pgmid    = 'R3TR'
            and object   = 'SMOD'
            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:/(95) sy-uline.
          format color col_heading intensified on.
          write:/1 sy-vline,
          2 'Exit Name',
          21 sy-vline ,
          22 'Description',
          95 sy-vline.
          write:/(95) sy-uline.
          loop at jtab.
            select single * from modsapt
            where sprsl = sy-langu and
            name = jtab-obj_name.
            format color col_normal intensified off.
            write:/1 sy-vline,
            2 jtab-obj_name,
            21 sy-vline ,
            22 modsapt-modtext,
            95 sy-vline.
          endloop.
          write:/(95) sy-uline.
          describe table jtab.
          skip.
          format color col_total intensified on.
          write:/ 'No of Exits:' , sy-tfill.
        else.
          format color col_negative intensified on.
          write:/(95) 'No User Exit exists'.
        endif.
      else.
        format color col_negative intensified on.
        write:/(95) 'Transaction Code Does Not Exist'.
      endif.
    * Take the user to SMOD for the Exit that was selected.
    at line-selection.
      get cursor field field1.
      check field1(4) eq 'JTAB'.
      set parameter id 'MON' field sy-lisel+1(10).
      call transaction 'SMOD' and skip first screen.

  • Reg. User Exit for TCode FCH5

    Hi All,
               Is there any user exit for Manual Check Entry Program (Tcode FCH5) that will not allow user
    to make any modifications in existing check's.
    Thks
    Shailesh

    Hi,
    just mark your question as 'Answered' and give some comments.
    Thanks.

  • User exits for tcodes CJR2, CJR8, CJ40, and CJ42

    Hi,
    I have a requirement to capture confirmed (saved/posted) cost and revenue plans for a particular WBS in any of the above tcodes executed by the user.  Is there any user exit/badi/or bapi for such?
    Appreciate any feedback on this.
    Regards,
    jacky

    Hi,
    Check whether you can use SAPLBPFC (CJ40, CJ42).
    Regards
    Sreekanth

Maybe you are looking for