Config needed for MIGO

Dear Friends,
We have a requirement from the client.
Initially, the user will create a PO and in that PO they will have an additional line item called Add on Cost. There will be a Zcondition type for that.
Now the clients requirement is they want this Add on Cost to go to a different account while doing MIGO.
For Example If 100 is the material cost and 25 is the Add on Cost, while doing MIGO the accounting entry should be
Inventory A/C  Dr  125
       To GR/IR A/C            100
       To Addon Cost A/C    25
Can you please suggest what configuration needs to be done for this.

Dear,
This will require huge rework like creating new transaciton key, map this key to valuation string, assign this string to the movement type and then assign G/L account to this transaction, which I would not recommend. I recommend you to create condition type for this and create new key in OBCN and then map this account key to condition type which will create accounting document you want.
Regards,
Chintan Joshi.

Similar Messages

  • Config need for T. Code PA30, PA71

    Dear Experts,
    I have a following Client requirement as like,
    1. There are two SAP User (AS User 1 and User 2)  for SAP Payroll. requirement is whenever "User 1 " will create a record for IT0008, 0014 , 00015 and 0057 through PA30 or PA71 that record should always create in Lock mode.
    2. When "User 2" will check the same created record by "User 1". And same he(User 2) will Unlock after the check.
    So my quiry is is it possible through std config or I have to do anything Enhancement to achive the same. Please guide me.
    Regards
    Swapnil

    Hi,
    You can achieve this at authorisation level. Ask your basis guy to help on this...
    Pls maintain authorisation object below for user 1 (which will be by default lock mode when he will create the record 8 , 14 , 57 etc)
    P_ORGIN,P_PCLX,P_PERNR
    maintained above auth objects as auth level E
    Regards,
    Mahesh

  • Needed config settings for automatic storage location

    hi,
    sap gurus,
    configuration settings needed for automatic storage location at sales order level.
    it is coming by using OVL3 at delivery document level.
    but we need it sales order level.
    regards,
    balaji.t

    Hi Balaji,
    In standard Storage location cannot be defaulted in Sales order. OVL3 is for determining the storage location in Delivery.
    However to map your requirement of having Storage location determination in the Sales order do the following:
    In the Plant Setting IMG> Enterprise Structure> Definition> Logistics - General> Define, copy, delete, check plant. Here select your plant and go to Address for this plant. Here in Search term 2 Maintain some alphabet say "A". Now ask your ABAPer to write a user exit for determining the Storage location if the Sales order has the same Plant used in it with search term as "A" then use table V_TVKOL (storage location determination table) and fetch the correct storage location based on Shipping Point + Plant + Storage conditions.
    Hope the same works for you!!
    Regards,
    Ajinkya

  • User-exit for MIGO, need change GKONT for CO

    Good evening,
    Dear friends, sorry for my english.
    I have made user-exit for MIGO in GGB1 and put on it in SPRO.
    I have HKONT=V3100* and corresponding HKONT=1551*( OBYC, group WRX).
    Then i run MIGO and make Purchase Order.
    In my user exit, if HKONT of first position eq V3100, i must change corresponding HKONT from 1551 to V1551*.
    When i make Order, i am run view documents: FI and other HKONTs changed successfully! ( first possition has V3100, second - V1551).
    User-exit must work only with sy-tcode = MIGO or MIRO.
    But CO documens NOT changed: HKONT(type of cost) eq V3100, but corr GKONT = 1551*...
    I also try to use OPEN FI, but have the same picture... (in CO docs V3100* and 1551, but all another docs and FI too - V3100 and V1551*).
    I see, that GKONT has only COEP. And this table a cannot see in user-exit.
    I think, that FI doc must do CO doc,
    but why in
    View documents->RW-infodocs->documents CO = it is not change?
    Please, answer me? if you can. regards.

    Please, view Print-Screen of my problem:
    <a href="http://rodendron.blogspot.com/2007/07/user-exit-for-migo.html">http://rodendron.blogspot.com/2007/07/user-exit-for-migo.html</a>
    Anybody can help?

  • Need config steps for Multi-Mode Transportation in SD

    Hi Gurus,
    I am implementing Transportation Module in SD , I covered domestic part means Single mode .
    But Now i have complete Multi-Mode Transporatation for Export , contains Rail, Ships, i.e Multimode Transporation ,
    Please give me Config. steps for it
    Thanks
    Devdatta Joshi

    Check if the link below is helpful:
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LETRA/SDTRA.pdf
    Regards,
    Rajesh Banka
    Reward points if helpful.

  • Specifying coherence-cache-config.xml for multiple clusters

    Hi,
    I am running two cache clusters (Cluster A and B that hold different cache types). we have a web application that needs to communicate with both the clusters. we have two coherence-cache-config-g.xml files, one for each cluster.
    where do we specify the two coherence-cache-config.xml for each of these clusters in our coherence.jar that we deploy on the web app server.
    pls provide some inputs...
    thanks in advance,
    - G.

    Hi G,
    You can define a path to the cache configuration descriptor in your operation configuration override file (tangosol-coherence=override.xml) or specify it in the system property "tangosol.coherence.cacheconfig".
    Please see this Wiki page for details:
    http://wiki.tangosol.com/display/COH32UG/configurable-cache-factory-config
    Regards,
    Gene

  • BDC for MIGO for GR OutBound Delivery( A01 & R05 ) from Movement Type 107 to 109

    Hi,
    I am stuck with a very typical situation need all your expertise and advices for a solution.
    We are basically trying to create change the movement type from 107 to 109 through MIGO.
    I have made a BDC recording for MIGO ( because we would like to track each delivery specifically under shipment , I know that there is a BAPI which is there to do this but it works fine if we do the shipment with Purchase Order as input which dont want in that manner )
    Process:
    1. Creating Production Order
    2. Creating Purchase Order
    3. Creating STO
    4. Deliveries
    5. PGI for Deliveries
    6. Shipment for group of outbound Deliveries
    I have created a z program where i am passing shipment number in the selection screen.
    Then it would take all the deliveries for that shipment and pass each delivery to MIGO and process it and change the status from 107 to 109.
    Interesting part here is, the code works absolutely perfect only from my ID. But when I test from other ID it is not executing, so to check where is the problem I have added mess_tab to the CALL TRANSACTION to capture what message is been populated for my ID comparing with others
    Message Captured on Others ID's:
    MSGID: 00
    MSGNR: 344
    MSGV1: SAPLMIGO
    MSGV2: 1300
    Message Captured on MY ID:
    MSGID: MIGO
    MSGNR: 012
    MSGV1: 5000005802
    MSGV2: (empty)
    This is the problem this program is executing only on MY ID, rest all ID's it is not processing.
    We have cross verified with security and basis regarding any authorization issues but nothing came up.
    Please help me what could be the issue ( WHY it is processing successfully for my and WHY NOT for other ID's)
    Below is the main code :
    CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'                     " Converting Date format to DD/MM/YYYY
         EXPORTING
           DATE_INTERNAL            = sy-datum
         IMPORTING
           DATE_EXTERNAL            = lv_date_external
         EXCEPTIONS
           DATE_INTERNAL_IS_INVALID = 1
           OTHERS                   = 2.
           IF SY-SUBRC <> 0.                                     "#EC NEEDED
    * Implement suitable error handling here
           ENDIF.
    *   Validating input shipment number with database table VTTP
           SELECT VTTP~TKNUM
                  VTTP~TPNUM
                  VTTP~VBELN
             FROM VTTP INNER JOIN VTTK
             ON VTTP~TKNUM = VTTK~TKNUM
             INTO TABLE IT_VTTP
             WHERE VTTK~TKNUM = P_TKNUM
               AND VTTK~STDIS = 'X'.
           IF sy-subrc = 0.
    *   Validating all deliveries having same Delivery type or not
             SELECT * FROM likp INTO TABLE it_likp FOR ALL ENTRIES IN it_vttp WHERE vbeln = it_vttp-vbeln
                                                                                AND vbtyp = 'J'.
             IF sy-subrc = 0.
               CLEAR lv_lines.
               LOOP AT it_likp INTO wa_likp.
                 REFRESH:it_vbfa,BDCDATA.
    *   Validating if Delivery Type = 109 (GR already done), or Delivery Type = 107 (must process for GR )
                 SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
    *                                                AND vbtyp_v = 'J'
                                                         AND bwart = '109'.
                 IF sy-subrc = 0.
                   lv_flag1 = 'X'.
                 ELSE.
                   SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
    *                                                  AND vbtyp_v = 'J'
                                                           AND bwart = '107'.
                   IF sy-subrc NE 0.
                     MESSAGE 'No Deliveries with Movement Type "107" ' TYPE 'I'.
                   ELSE.
                     lv_flag2 = 'X'.
                     lv_lines = lv_lines + 1.
    **  BDC for MIGO
                     perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                     perform bdc_field       using 'BDC_OKCODE'
                                                   '=OK_GO'.
                     perform bdc_field       using 'GODYNPRO-ACTION'
                                                   'A01'.
                     perform bdc_field       using 'GODYNPRO-REFDOC'
                                                   'R05'.
                     perform bdc_field       using 'GODEFAULT_TV-BWART'
                                                   '109'.
                     perform bdc_field       using 'BDC_CURSOR'
                                                   'GODYNPRO-OUTBOUND_DELIVERY'.
                     perform bdc_field       using 'GODYNPRO-OUTBOUND_DELIVERY'
                                                   wa_likp-vbeln. "'80019574'.
                     perform bdc_field       using 'GOHEAD-BLDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-BUDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-WEVER'
                                                   '1'.
                     perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                     perform bdc_field       using 'BDC_OKCODE'
                                                   '=OK_POST1'.
                     perform bdc_field       using 'GODEFAULT_TV-BWART'
                                                   '109'.
                     perform bdc_field       using 'GOHEAD-BLDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-LFSNR'
                                                   wa_likp-vbeln. "'0080019574'.
                     perform bdc_field       using 'GOHEAD-BUDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-WEVER'
                                                   '1'.
                     perform bdc_field       using 'GODYNPRO-DETAIL_ZEILE'
                                                   '   1'.
                     perform bdc_field       using 'GOITEM-ERFME'
                                                   'EA'.
                     perform bdc_field       using 'GOITEM-ERFMG'
                                                   '1'.
                     perform bdc_field       using 'GOITEM-LSMNG'
                                                   '1'.
                     perform bdc_field       using 'GOITEM-LSMEH'
                                                   'EA'.
                     perform bdc_field       using 'GOITEM-MIGO_ELIKZ'
                                                   '1'.
                     perform bdc_field       using 'GOITEM-BWART'
                                                   '109'.
                     perform bdc_field       using 'GOITEM-LGOBE'
                                                   'RX Cross-docking'.
                     perform bdc_field       using 'BDC_CURSOR'
                                                   'GODYNPRO-DETAIL_TAKE'.
                     perform bdc_field       using 'GODYNPRO-DETAIL_TAKE'
                                                   'X'.
                     PERFORM bdc_dynpro      USING 'SAPLMIGO' '1300'.
                     PERFORM bdc_field       USING 'BDC_CURSOR'
                                                   'G_TIP_DONT_SHOW_AGAIN'.
                     PERFORM bdc_field       USING 'BDC_OKCODE'
                                                   '=OK_TIP_GO'.
                     PERFORM bdc_field       USING 'G_TIP_DONT_SHOW_AGAIN'
                                                   'X'.
    *& Avoid unncessary screens to populate while processing background.
                     LV_OPTIONS-DISMODE = 'N'.
                     LV_OPTIONS-UPDMODE = 'S'.
                     LV_OPTIONS-NOBINPT = 'X'.
                     CALL TRANSACTION 'MIGO' USING BDCDATA  OPTIONS FROM LV_OPTIONS MESSAGES INTO IT_MESSTAB1 .
                     WAIT UP TO 1 SECONDS.
                     DELETE IT_MESSTAB1 WHERE MSGTYP NE 'E'.
                     IF IT_MESSTAB1[] IS NOT INITIAL.
                       APPEND LINES OF IT_MESSTAB1 TO IT_MESSTAB.
                     ENDIF.
                   ENDIF.
                 ENDIF.
               ENDLOOP.
             ENDIF.
           ELSE.
             MESSAGE 'Shipment Number does not exists Or not Planned' TYPE 'E'.
           ENDIF.
         ELSE.
           MESSAGE 'Please insert Shipment Number' TYPE 'E'.
         ENDIF.
         IF lv_flag1 = 'X' AND lv_flag2 = 'X'.
           MESSAGE 'This shipment is processed with an inconsistent goods receipt' TYPE 'I'.
         ELSEIF lv_flag1 = 'X'.
           MESSAGE 'Shipment already been processed for these deliveries' TYPE 'I'.
         ELSEIF lv_flag2 = 'X'.
           lv_lines1 = lv_lines.
           CONDENSE lv_lines1 NO-GAPS .
           CONCATENATE lv_lines1 'Goods Receipt are posted for the shipment '
                  INTO lv_message SEPARATED BY space.
           MESSAGE  lv_message TYPE 'I'.
         ENDIF.
    * Display Messages from Message TAB.
         DELETE ADJACENT DUPLICATES FROM IT_MESSTAB.
         DATA:lv_msg TYPE string.
         LOOP AT IT_MESSTAB INTO WA_MESSTAB.
           CALL FUNCTION 'FORMAT_MESSAGE'
             EXPORTING
               ID        = WA_MESSTAB-MSGID
               NO        = WA_MESSTAB-MSGNR
               V1        = WA_MESSTAB-MSGV1
               V2        = WA_MESSTAB-MSGV2
               V3        = WA_MESSTAB-MSGV3
               V4        = WA_MESSTAB-MSGV4
             IMPORTING
               MSG       = lv_msg
             EXCEPTIONS
               NOT_FOUND = 1
               OTHERS    = 2.
           IF sy-subrc <> 0.
    * Implement suitable error handling here
           ENDIF.
           WRITE:/ lv_msg.
         ENDLOOP.
    *        Start new screen                                              *
       FORM BDC_DYNPRO USING PROGRAM DYNPRO.                 "#EC PF_NO_TYPE
         CLEAR BDCDATA.
         BDCDATA-PROGRAM  = PROGRAM.
         BDCDATA-DYNPRO   = DYNPRO.
         BDCDATA-DYNBEGIN = 'X'.
         APPEND BDCDATA.
       ENDFORM.
    *        Insert field                                                  *
       FORM BDC_FIELD USING FNAM FVAL.                       "#EC PF_NO_TYPE
         CLEAR BDCDATA.
         BDCDATA-FNAM = FNAM.
         BDCDATA-FVAL = FVAL.
         APPEND BDCDATA.
       ENDFORM.
    Thanks,
    Srini

    Hi Rob,
    Thanks for quick reply.
    I have checked the NOTE : 304122
    But there in the NOTE it says ( " BAPI, BAPI_GOODSMVT_CANCEL, BAPI_GOODSMVT_CREATE, CNTL_ERROR" )
    These BAPI's work perfectly for (purchase order as input type), but here out type is ( A01 & R05 ) we are giving DELIVERY NUMBER as input to MIGO.
    So for this scenario we cannot use those BAPI's mentioned in the NOTE.
    Also as stated earlier in the message interesting part is
    "The code works absolutely perfect only from my ID. But when I test from other ID it is not executing. Code is working exactly as expected ONLY to my ID. When i try to execute the same code from another's ID it is not working"
    So what do you think might be the issue?

  • BADI/User exit for MIGO fi postings

    Hello Experts,
    I have one requirement regarding at the time of MIGO accounting entry is generating based on the OBYC settings,now the client want along with this entry, want to create one more FI document through background,In the background we will give the debit g/l and credit g/l.That means at the time of MIGO two FI documents has to generate one is with OBYC setting gl's and second FI entry is from programe hard coded gl's.
    For this requirement has any BADI/USER Exit.I appriciate your valuable inputs.
    Regards,
    Nivas.

    Hi,
      May I know why you need two accounting documents?
      You may refer the similar thread: BADI / Exit required for MIGO for posting FI document
      And about the number ranges - I would suggest a custom number range object and a different number range for these additional documents.
      Also refer the doc: Methods to find Customer/User Exit's & BADi's for a Transaction Code!
    Regards,
    AKPT

  • User Exit for MIGO (goods receipt and goods issue)

    Hi all ,
    When i create a cross company goods receipt or goods issue through MIGO,I need to add another line item to the accounting documents posted with the sales tax calculated.For this i need to use a user exit which adds another line item.
    Can someone suggest me the user exit which i need to use ?
    any input would be of great help.
    Thanks,
    nsp.

    Hi
    Available exits for MIGO are
    Transaction Code - MIGO                     Goods Movement
    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.
    No of Exits:          8
    You would hav to search through these.
    Hope this helps to solve ur problem....
    <b>do reward if useful....</b>
    regards
    dinesh

  • BDC for MIGO & J1IEX

    Hi,
    For Goods reciept for Kanban material there is transaction called PKBC. Inside this transaction we wrote two BDC's i.e One for MIGO (with only Part1) & J1iex(Capturing & posting the excise invoice). After running this we found that accounting document contains all the entries including Part2. But During MIRO we are not getting excise amount which is payable to the vendor.
    Please help me to resolve this. Incase if you need any clarification please ket me know.
    Thanks in advance
    Regards,
    Krishna A S V

    why r u using two BDC
    why dont u use only one and update Part I and Part II at a time
    regards,
    snb

  • Maintain Config Id for the Start page of e-rec application

    Hi,
    I've a requirement wherein I need to hide one of the links in the startup pages for the internal candidates. I have made the necessary configuration settings . Also , defined "WDCONFIGURATIONID" parameter for the "hrrcf_a_startpage_int_cand". But its not picking up the config id for the application. Please guide me if I'm missing something.
    Thanks
    Nidhi

    Nidhi,
    try with sap-wd-configId
    .If it doesnot work there is something wrong with the configuration you created.
    check this doc
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b52e13c3-0901-0010-8fa6-d11a51821b7c
    Thanks
    Bala Duvvuri

  • Tax config steps for women in ecc 5.0 version

    Hi to all Guru's,
    I want to configure tax for women in ECC5.0 VERSION.
    The tax tables are V_T7INT1 AND V_T7INT3.
    in V_T7INT1 i have maintained tax code for men and in V_T7INT3
    I have maintained tax slabs for the men for corresponding the tax code.
    But i am not gettng how i have to configure tax slabs for women in ecc5.0 version.
    in ecc5.0 version we dont have drop down slab type for men and women like in ECC6.0 VERSION
    Please let me know the config steps needed for tax calculation for women.
    Thanks
    Priya

    Hi sameer,
    I searched all the notes but i am not gettng that note for ECC5.0.
    Please suggest me some note numbers so that i can go through it?
    Thanks
    Priya

  • Step wise config data for schedule line agreements

    DEar All,
    I need urgently one the foolowing doc:
    step wise config data for schedule line agreements.
    thanks
    regards,
    s KUMAR

    Hi,
    1) Scheduling Agreement is a long term agreement and PO is normally a one-off. When you have long term relation with supplier you will go with SA.
    2) SA need not have delivery schedules at the time of ordering. It's like a contract with vendor for all basic prices, quantities & terms. You will release schedules as & when required. This method is very popular with manufacturing ind (e.g. automotive) where they negotiate prices but delivery schedules are given periodically based on their actual production/sales demands.
    3) In a PO, you must give schedules in PO itself.
    4) If you know contract & release order (or call-off) concept, then SA is like contract and SA schedule is like release order. PO is release order.
    or
    While using schedule agreement, you will create delivery schedule, when ever you require materials.
    Firm and trade off zone in delivery schedule details will be forwarded to your vendor. you can create daily , weekly , monthly schedule lines
    Example : if you have created a schedule agreement for product " A " for quantity 1000, and you require material of 100 nos in the first month, you can create schedule line for this 100 only and this will be transmitted to vendor( if you are using LPA you have to release schedule line). when ever you require further qty based on your requirement you will create another delivery schedule line, then it will be transmited to vendor.
    In case of PO if you are ordering 1000 qty , you need to specify the delivery date in Purchase order it self, and all the dates are immediately transmited to vendor along with Purchase order.
    For configuration steps please follow
    http://help.sap.com/saphelp_47x200/helpdata/en/93/7439fb546011d1a7020000e829fd11/frameset.htm
    Hope this will help.
    Thanks,
    Raja

  • Field Exit For Migo Badi

    Hi to all experts,
    I need to assign F4 help to a headertext field for MIGO tcode . I have searched all the exits but couldnt find field exit for it. What are the different options fulfilling this requirement.Please help me out

    Hi,
        The following are the enhancement/Business Add ins,  Please use the appropriate exit for your requirement
      Enhancement/ Business Add-in            Description
    Enhancement
    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
    Business Add-in
    MB_DOCUMENT_UPDATE                      BADI when updating material document: MSEG and MKPF
    MB_DOC_BADI_INTERNAL                    BAdIs During Creation of a Material Document (SAP Internal)
    MB_ME_CSGMT_BADI_SAP                    BAdI: Consignment Processing - Stock Transfer
    MB_MIGO_BADI                            BAdI in MIGO for External Detail Subscreens
    MB_MIGO_ITEM_BADI                       BAdI in MIGO for Changing Item Data
    MB_PHYSINV_INTERNAL                     Connection: Core Inventory and Retail AddOn
    MB_QUAN_CHECK_BADI                      BAdI: Item Data at Time of Quantity Check
    MB_RESERVATION_BADI                     MB21/MB22: Check and Complete Dialog Data
    MB_RESERVATION_SCR                      Screen BAdI for Retrofit DFPS
    MB_RESERVATION_UPCHD                    BAdI for Creation and Changing of Manual Reservations
    MB_RES_BAPI_CHANGE                      BAdI: Execution of Changes to Reservation Fields
    MB_RES_BAPI_CREATE1                     BAdI: Adoption of Customer's Own Fields as Reserv. Fields
    MB_RES_BAPI_DETAIL1                     BAdI: Display of Customer's Own Fields in Reservations
    MB_STOR_LOC_BADI_GTS                    BADI to Check and Change Storage Location (GTS Fct. Only)
    MB_DOCUMENT_BADI_SAP                    BADI for Creation and Changing of a Material Document
    ARC_MM_EBAN_CHECK                       BAdI: Enhancement of Archivability Check (MM_EBAN)
    ARC_MM_EBAN_PRECHECK                    BAdI: Enhancement of Archivability Check (MM_EBAN)
    ARC_MM_EBAN_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EBAN)
    ARC_MM_EINA_CHECK                       BAdI: Enhancement of Archivability Check (MM_EINA)
    ARC_MM_EINA_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EINA)
    ARC_MM_INVBEL_CHECK                     BAdI: Enhancement of Archivability Check (MM_INVBEL)
    ARC_MM_INVBEL_WRITE                     BAdI: Enhancement of Scope of Archiving (MM_INVBEL)
    ARC_MM_MATBEL_CHECK                     Prüfung ADD-ON-spezifischer Kriterien für MM_MATBEL
    ARC_MM_MATBEL_WRITE                     Check Add-On-Specific Data for MM_MATBEL
    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 During Creation of a Material Document

  • Which exit for MIGO Subcontracting

    Dear Abaper,
    We were using MB1B t-code for doing subcontracting with reference to PO. We had used a BADI for that.
    Now, we have upgraded our system to EHP6.
    In EHP6 MB1B is obsolete. And as per SAP we have to use MIGO.
    In MIGO we cannot do subcontracting with reference to PO.
    In the transaction MIGO this PO reference functionality is not implemented for movement type 541.
    There are so many exits available in MIGO,
    please tell me which exit to use to do the subcontracting with Movement type 541 for MIGO Transaction.
    Thanks and Regards,
    Arati. 

    Arati, follow this note, it is exactly what you need:
    1915825 - Transfer Posting reference to a Purchase Order in MIGO
    Resolution
    The business function 'LOG_MM_OM_1' must be activated in your system.
    Also, the BADI MB_MIGO_SC_PO_TRANSFER must be activated into the system and then the option 'A08 Transfer Posting' and 'R01 Purchase Order' appears.
    To activate the business function go to tcode SFW5 and mark the function LOG_MM_OM_1 and click on Activate Changes.
    After that you can go to MIGO and check:
    Regards,
    Felipe

Maybe you are looking for

  • Newsgroup reorganization + New AL BPM Suite Product Center on Dev2Dev

    Hi, As you've probably noticed, we've reorganized the BPM newsgroups a little - cutting down on the dozen or two that we had (aqualogic.business.service.*), leaving just five: aqualogic.bpm.general aqualogic.bpm.modeling (renamed old .project.develop

  • Problems with Sound in Quicktime Pro

    Im having problems with my Quicktime Pro. Basically whenever i open up a movie file using Quicktime (.mov, .avi, .mpg, etc) the video will play but the audio jumps and sounds like B B B B B, K K K K, D D D D. It does this even if i open a Quicktime M

  • Loading a Plugin before MediaFactoryItem is added

    Hello, When I try to load my plugin before a MediaFactoryItem is added to the MediaFactory, it won't work (the plugin doesn't load). However, when load a plugin after there is at least one item in the MediaFactory, the plugin works fine. Is this an i

  • Problem with SOAP tutorial

    Hi, I followed the SOAP tutorial. It worked fine until I tried to test the SOAP web service. Then I got: [SOAPException: faultCode=SOAP-ENV:Server; msg=service 'soapdatetimeservicepackage.SOAPDateTimeService' unknown]      java.lang.String soapdateti

  • Installing CS3 Upgrade Version on a NEW PC

    Hello, I've had a lot of problems contacting Adobe and hope you can help me. I'm getting a new PC soon and want to install my copy of CS3 Design Standard. The disk here is an upgrade disk as I had the original creative suite (also an upgrade disk). B