Quantity withdrawn field in BAPI_GOODSMVT_CREATE

When i use BAPI_GOODSMVT_CREATE to post with movement type 261 for transaction MB1A in a custom program with sel screen process order,material,batch no and qty, quantity withdrawn field is not updating.(This field is in process order COR3 Transaction).
if i do full quantity its working fine,whenever i do partial qty, it should be updated in quantity withdrawn field.
Any one has input please let me know
Thanks
Suresh

code is '03'.
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
           EXPORTING
             goodsmvt_header         = ls_goodsmvt_header
             goodsmvt_code           = '03'
*           TESTRUN                 = ' '
*           GOODSMVT_REF_EWM        =
           IMPORTING
             goodsmvt_headret        = ls_goodsmvt_headret
             materialdocument        = lv_mblnr
             matdocumentyear         = lv_mjahr
           TABLES
             goodsmvt_item           = lt_goodsmvt_item
*           GOODSMVT_SERIALNUMBER   =
             return                  = lt_return
*           GOODSMVT_SERV_PART_DATA =
*           EXTENSIONIN             =

Similar Messages

  • Quantity Withdrawn field in production order

    Hi all,
    I have a doubt
    there is a component A in production order
    Required quantity is 10
    Initially i issue 15 qty's then the same qty gets updated in "Quantity withdrawn" field (component overview screesn)
    Then i reverse 3 qty's of component A,which is very much visible in documented goods movement
    Whereas the same is not getting update in the ""Quantity withdrawn" field ,Still 15 qty is appearing against "Quantity withdrawn" field
    This may be normal behaviour of the system,I'm not sure
    Can you please confirm on this
    If not then please give me possible reasons why it is not getting updated ?
    Thanks,
    SVP

    Hi all,
    I also wonder about this (actually it's an issue for this customer ... ). As same as production order, Network order (it's activity more correctly) also show withdrawn quantity in CN25 transaction.
    In my case, I've done good issue quantity 2 EA, then I reverse it. and same again. finally I do good issue 2 EA.
    GI         -2 EA : CN25
    cancel GI 2 EA : CN29
    GI         -2 EA : CN25
    cancel GI 2 EA : CN29
    GI         -2 EA : CN25
    (Yeah, normally it will not happen often but it can.)
    I expect withdrawn Quantity 2 EA but it shows 10 EA. So have wonder with actual data table MSEG. It has SMBLN value (referred document number to cancel) as I think. It's very normal.
    Why withdrawn field doesn't count that cancel quantity?
    Is there any configuration that I missed ? or Is it normal result?
    But System should do show 'Cancelled GI Quantity' (so that end-user can notify actual GI quantity) to make it understand.
    Regards,
    Yeum
    Edited by: Hee Chul Yeum on Jan 22, 2009 10:50 AM

  • CO02 - Quantity withdrawn

    Hi Friends,
    If I do goods issue through MIGO, In production order quantity withdrawn column (Component overview) is empty and in document goods movement also it is not shown the with drawn quantity. If I use back flush, then system shows with drawn quantity. Why this is happening?
    My requirement is, system should show quantity withdrawn in production order, for all t. codes MIGO, MB1A.
    Thanks,
    Pook

    Hi,
    In MIGO, proceed by selecting Goods ıssue then Order and enter production order no. Reservations of the order will be listed in the items. Mark OK for the items and save.
    Alternatively in MB1A choose "To order" and enter production order no, then post movements.
    This way posting will be done against order reservations and quantity withdrawn field gets updated.
    Regards.

  • Behaviour of 'quantity withdrawn' at PP Order in subcontracting scenario

    In a PP order with external operation (Control key PP02) and assigned materials. When the purchase order is created for this external operation, based on purchase requisition the 'quantity withdrawn' at CO02 is updated after save the purchase order.
    I doubt, if this is the natural behaviour for the quantity withdrawn field, or this field should be updated just at the 543 consumption movement from vendor, or at least in the movement 541.
    Thanks & Regards,
    Felipe Garzón Quintero

    Felipe,
    It is standard behavior of the system because when you see MD04 for same component you can see 2 MRP element showing for same requirement.
    BR
    KK

  • How to populate cusotom fields using BAPI_GOODSMVT_CREATE  for MIGO

    Hi,
    I was to update custom field using BAPI_GOODSMVT_CREATE for MIGO and store it is MSEG table.
    Please tell me how to proceed.
    Moderator message: last warning, if you continue to post the same thread again, I will submit your user ID for deletion. See my comments in your previous posts.
    Edited by: Thomas Zloch on Jul 14, 2011 4:38 PM

    Hi ANID,
    Thanks for the reply.
    I have checked in the documention of the bapi and no communication structure regarding to the bapi is there so i am not able to figure out where to add the custom field so that it can be added in the MKPF table.
    Regads
    Dipak

  • CN 752: Requirement quantity & & smaller than quantity withdrawn & &

    Dear Gurus,
    I have found a strange behavior in SAP PM order processing.
    Even after withdrawing the spare parts, system is allowing to change the required quantity.
    If someone is increasing the quantity thats fine.
    But if someone is decreasing the quantity, system should not allow it.
    System is giving below information message:
    CN 752
    Requirement quantity & & smaller than quantity withdrawn & &
    I want to give error in such scenario.
    I have tried setting an error message for above message, but its not working.
    Any help in this regard will be highly appreciated.
    Please help.
    Thanks & Regards,
    Mihir Popat

    Hello,
    Thank you very much for your inputs.
    I have checked that, but it is still not working for me.
    I have debugged the standard code and found that it is hard coded over there as information message for message CN 752, and system is not checking any table while issuing the message.
    However for message CN 750, system checks the table and decides accordingly, whether to give warning or error.
    Hence, it is clear that it will be information message only.
    I will be mapping my requirement with user exit CNEX0026, where i will check the withdrawn quantity and required quantity and decide on whether to give error or not.
    Thanks to all for your help.
    Closing the thread.
    Regards,
    Mihir Popat

  • Addiing 'lsmng' field in bapi_goodsmvt_create

    Hi Buddies,
    i want to update lsmng field through bapi_goodsmvt_create, but colud not find that field in bapi, please tell me how add this field in bapi. my sap versin is 4.7
    Response is awiated.

    see my post reply
    http://scn.sap.com/message/13649968

  • Quantity& currency fields

    hi every one, can any one tell me how to handle/insert quantity& currency fields in  BDC?

    Hi
    Welcome to SDN forum
    You have to pass the Qty and Currency fields as CHAR type fields only
    see the sample PO BDC in which these fields are populated using BDC
    REPORT zmm_bdcp_purchaseorderkb02
    NO STANDARD PAGE HEADING LINE-SIZE 255.
    Declaring internal tables *
    *-----Declaring line structure
    DATA : BEGIN OF it_dummy OCCURS 0,
    dummy(255) TYPE c,
    END OF it_dummy.
    *-----Internal table for line items
    DATA : BEGIN OF it_idata OCCURS 0,
    ematn(18), "Material Number.
    menge(13), "Qyantity.
    netpr(11), "Net Price.
    werks(4), "Plant.
    ebelp(5), "Item Number.
    END OF it_idata.
    *-----Deep structure for header data and line items
    DATA : BEGIN OF it_me21 OCCURS 0,
    lifnr(10), "Vendor A/c No.
    bsart(4), "A/c Type.
    bedat(8), "Date of creation of PO.
    ekorg(4), "Purchasing Organisation.
    ekgrp(3), "Purchasing Group.
    x_data LIKE TABLE OF it_idata,
    END OF it_me21.
    DATA : x_idata LIKE LINE OF it_idata.
    DATA : v_delimit VALUE ','.
    DATA : v_indx(3) TYPE n.
    DATA : v_fnam(30) TYPE c.
    DATA : v_count TYPE n.
    DATA : v_ne TYPE i.
    DATA : v_ns TYPE i.
    *include bdcrecx1.
    INCLUDE zmm_incl_purchaseorderkb01.
    Search help for file *
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
    CALL FUNCTION 'F4_FILENAME'
    EXPORTING
    program_name = syst-cprog
    dynpro_number = syst-dynnr
    IMPORTING
    file_name = p_file.
    START-OF-SELECTION.
    To upload the data into line structure *
    CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
    filename = p_file
    filetype = 'DAT'
    TABLES
    data_tab = it_dummy.
    Processing the data from line structure to internal tables *
    REFRESH:it_me21.
    CLEAR :it_me21.
    LOOP AT it_dummy.
    IF it_dummy-dummy+0(01) = 'H'.
    v_indx = v_indx + 1.
    CLEAR it_idata.
    REFRESH it_idata.
    CLEAR it_me21-x_data.
    REFRESH it_me21-x_data.
    SHIFT it_dummy.
    SPLIT it_dummy AT v_delimit INTO it_me21-lifnr
    it_me21-bsart
    it_me21-bedat
    it_me21-ekorg
    it_me21-ekgrp.
    APPEND it_me21.
    ELSEIF it_dummy-dummy+0(01) = 'L'.
    SHIFT it_dummy.
    SPLIT it_dummy AT v_delimit INTO it_idata-ematn
    it_idata-menge
    it_idata-netpr
    it_idata-werks
    it_idata-ebelp.
    APPEND it_idata TO it_me21-x_data.
    MODIFY it_me21 INDEX v_indx.
    ENDIF.
    ENDLOOP.
    To open the group *
    PERFORM open_group.
    To populate the bdcdata table for header data *
    LOOP AT it_me21.
    v_count = v_count + 1.
    REFRESH it_bdcdata.
    PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0100',
    ' ' 'BDC_CURSOR' 'EKKO-LIFNR',
    ' ' 'BDC_OKCODE' '/00',
    ' ' 'EKKO-LIFNR' it_me21-lifnr,
    ' ' 'RM06E-BSART' it_me21-bsart,
    ' ' 'RM06E-BEDAT' it_me21-bedat,
    ' ' 'EKKO-EKORG' it_me21-ekorg,
    ' ' 'EKKO-EKGRP' it_me21-ekgrp,
    ' ' 'RM06E-LPEIN' 'T'.
    PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
    ' ' 'BDC_CURSOR' 'RM06E-EBELP',
    ' ' 'BDC_OKCODE' '/00'.
    MOVE 1 TO v_indx.
    *-----To populate the bdcdata table for line item data
    LOOP AT it_me21-x_data INTO x_idata.
    CONCATENATE 'EKPO-EMATN(' v_indx ')' INTO v_fnam.
    PERFORM subr_bdc_table USING ' ' v_fnam x_idata-ematn.
    CONCATENATE 'EKPO-MENGE(' v_indx ')' INTO v_fnam.
    PERFORM subr_bdc_table USING ' ' v_fnam x_idata-menge.
    CONCATENATE 'EKPO-NETPR(' v_indx ')' INTO v_fnam.
    PERFORM subr_bdc_table USING ' ' v_fnam x_idata-netpr.
    CONCATENATE 'EKPO-WERKS(' v_indx ')' INTO v_fnam.
    PERFORM subr_bdc_table USING ' ' v_fnam x_idata-werks.
    v_indx = v_indx + 1.
    PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
    ' ' 'BDC_CURSOR' 'RM06E-EBELP',
    ' ' 'BDC_OKCODE' '/00'.
    ENDLOOP.
    PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
    ' ' 'BDC_CURSOR' 'RM06E-EBELP',
    ' ' 'BDC_OKCODE' '=BU'.
    PERFORM bdc_transaction USING 'ME21'.
    ENDLOOP.
    PERFORM close_group.
    End of selection event *
    END-OF-SELECTION.
    IF session NE 'X'.
    *-----To display the successful records
    WRITE :/10 text-001. "Sucess records
    WRITE :/10 SY-ULINE(20).
    SKIP.
    IF it_sucess IS INITIAL.
    WRITE :/ text-002.
    ELSE.
    WRITE :/ text-008, "Total number of Succesful records
    35 v_ns.
    SKIP.
    WRITE:/ text-003, "Vendor Number
    17 text-004, "Record number
    30 text-005. "Message
    ENDIF.
    LOOP AT it_sucess.
    WRITE:/4 it_sucess-lifnr,
    17 it_sucess-tabix CENTERED,
    30 it_sucess-sucess_rec.
    ENDLOOP.
    SKIP.
    *-----To display the erroneous records
    WRITE:/10 text-006. "Error Records
    WRITE:/10 SY-ULINE(17).
    SKIP.
    IF it_error IS INITIAL.
    WRITE:/ text-007. "No error records
    ELSE.
    WRITE:/ text-009, "Total number of erroneous records
    35 v_ne.
    SKIP.
    WRITE:/ text-003, "Vendor Number
    17 text-004, "Record number
    30 text-005. "Message
    ENDIF.
    LOOP AT it_error.
    WRITE:/4 it_error-lifnr,
    17 it_error-tabix CENTERED,
    30 it_error-error_rec.
    ENDLOOP.
    REFRESH it_sucess.
    REFRESH it_error.
    ENDIF.
    CODE IN INCLUDE.
    Include ZMM_INCL_PURCHASEORDERKB01
    DATA: it_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
    DATA: it_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
    DATA: E_GROUP_OPENED.
    *-----Internal table to store sucess records
    DATA:BEGIN OF it_sucess OCCURS 0,
    msgtyp(1) TYPE c,
    lifnr LIKE ekko-lifnr,
    tabix LIKE sy-tabix,
    sucess_rec(125),
    END OF it_sucess.
    DATA: g_mess(125) type c.
    *-----Internal table to store error records
    DATA:BEGIN OF it_error OCCURS 0,
    msgtyp(1) TYPE c,
    lifnr LIKE ekko-lifnr,
    tabix LIKE sy-tabix,
    error_rec(125),
    END OF it_error.
    Selection screen
    SELECTION-SCREEN BEGIN OF LINE.
    PARAMETERS session RADIOBUTTON GROUP ctu. "create session
    SELECTION-SCREEN COMMENT 3(20) text-s07 FOR FIELD session.
    SELECTION-SCREEN POSITION 45.
    PARAMETERS ctu RADIOBUTTON GROUP ctu. "call transaction
    SELECTION-SCREEN COMMENT 48(20) text-s08 FOR FIELD ctu.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 3(20) text-s01 FOR FIELD group.
    SELECTION-SCREEN POSITION 25.
    PARAMETERS group(12). "group name of session
    SELECTION-SCREEN COMMENT 48(20) text-s05 FOR FIELD ctumode.
    SELECTION-SCREEN POSITION 70.
    PARAMETERS ctumode LIKE ctu_params-dismode DEFAULT 'N'.
    "A: show all dynpros
    "E: show dynpro on error only
    "N: do not display dynpro
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 48(20) text-s06 FOR FIELD cupdate.
    SELECTION-SCREEN POSITION 70.
    PARAMETERS cupdate LIKE ctu_params-updmode DEFAULT 'L'.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 3(20) text-s03 FOR FIELD keep.
    SELECTION-SCREEN POSITION 25.
    PARAMETERS: keep AS CHECKBOX. "' ' = delete session if finished
    "'X' = keep session if finished
    SELECTION-SCREEN COMMENT 48(20) text-s09 FOR FIELD e_group.
    SELECTION-SCREEN POSITION 70.
    PARAMETERS e_group(12). "group name of error-session
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 51(17) text-s03 FOR FIELD e_keep.
    SELECTION-SCREEN POSITION 70.
    PARAMETERS: e_keep AS CHECKBOX. "' ' = delete session if finished
    "'X' = keep session if finished
    SELECTION-SCREEN END OF LINE.
    PARAMETERS:p_file LIKE rlgrap-filename.
    at selection screen *
    AT SELECTION-SCREEN.
    group and user must be filled for create session
    IF SESSION = 'X' AND
    GROUP = SPACE. "OR USER = SPACE.
    MESSAGE E613(MS).
    ENDIF.
    create batchinput session *
    FORM OPEN_GROUP.
    IF SESSION = 'X'.
    SKIP.
    WRITE: /(20) 'Create group'(I01), GROUP.
    SKIP.
    *----open batchinput group
    CALL FUNCTION 'BDC_OPEN_GROUP'
    EXPORTING
    CLIENT = SY-MANDT
    GROUP = GROUP
    USER = sy-uname.
    WRITE:/(30) 'BDC_OPEN_GROUP'(I02),
    (12) 'returncode:'(I05),
    SY-SUBRC.
    ENDIF.
    ENDFORM. "OPEN_GROUP
    end batchinput session *
    FORM CLOSE_GROUP.
    IF SESSION = 'X'.
    *------close batchinput group
    CALL FUNCTION 'BDC_CLOSE_GROUP'.
    WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
    (12) 'returncode:'(I05),
    SY-SUBRC.
    ELSE.
    IF E_GROUP_OPENED = 'X'.
    CALL FUNCTION 'BDC_CLOSE_GROUP'.
    WRITE: /.
    WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
    ENDIF.
    ENDIF.
    ENDFORM. "CLOSE_GROUP
    Start new transaction according to parameters *
    FORM BDC_TRANSACTION USING TCODE TYPE ANY.
    DATA: L_SUBRC LIKE SY-SUBRC.
    *------batch input session
    IF SESSION = 'X'.
    CALL FUNCTION 'BDC_INSERT'
    EXPORTING
    TCODE = TCODE
    TABLES
    DYNPROTAB = it_BDCDATA.
    WRITE: / 'BDC_INSERT'(I03),
    TCODE,
    'returncode:'(I05),
    SY-SUBRC,
    'RECORD:',
    SY-INDEX.
    ELSE.
    REFRESH it_MESSTAB.
    CALL TRANSACTION TCODE USING it_BDCDATA
    MODE CTUMODE
    UPDATE CUPDATE
    MESSAGES INTO it_MESSTAB.
    L_SUBRC = SY-SUBRC.
    WRITE: / 'CALL_TRANSACTION',
    TCODE,
    'returncode:'(I05),
    L_SUBRC,
    'RECORD:',
    SY-INDEX.
    ENDIF.
    Message handling for Call Transaction *
    perform subr_mess_hand using g_mess.
    *-----Erzeugen fehlermappe
    IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
    IF E_GROUP_OPENED = ' '.
    CALL FUNCTION 'BDC_OPEN_GROUP'
    EXPORTING
    CLIENT = SY-MANDT
    GROUP = E_GROUP
    USER = sy-uname
    KEEP = E_KEEP.
    E_GROUP_OPENED = 'X'.
    ENDIF.
    CALL FUNCTION 'BDC_INSERT'
    EXPORTING
    TCODE = TCODE
    TABLES
    DYNPROTAB = it_BDCDATA.
    ENDIF.
    REFRESH it_BDCDATA.
    ENDFORM. "BDC_TRANSACTION
    Form subr_bdc_table *
    text
    -->P_0220 text *
    -->P_0221 text *
    -->P_0222 text *
    FORM subr_bdc_table USING VALUE(P_0220) TYPE ANY
    VALUE(P_0221) TYPE ANY
    VALUE(P_0222) TYPE ANY.
    CLEAR it_bdcdata.
    IF P_0220 = ' '.
    CLEAR it_bdcdata.
    it_bdcdata-fnam = P_0221.
    it_bdcdata-fval = P_0222.
    APPEND it_bdcdata.
    ELSE.
    it_bdcdata-dynbegin = P_0220.
    it_bdcdata-program = P_0221.
    it_bdcdata-dynpro = P_0222.
    APPEND it_bdcdata.
    ENDIF.
    ENDFORM. " subr_bdc_table
    Form subr_mess_hand *
    text *
    -->P_G_MESS text *
    FORM subr_mess_hand USING P_G_MESS TYPE ANY.
    LOOP AT IT_MESSTAB.
    CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
    ID = it_messtab-msgid
    LANG = it_messtab-msgspra
    NO = it_messtab-msgnr
    v1 = it_messtab-msgv1
    v2 = it_messtab-msgv2
    IMPORTING
    MSG = P_G_MESS
    EXCEPTIONS
    OTHERS = 0.
    CASE it_messtab-msgtyp.
    when 'E'.
    it_error-error_rec = P_G_MESS.
    it_error-lifnr = it_me21-lifnr.
    it_error-tabix = v_count.
    APPEND IT_ERROR.
    when 'S'.
    it_sucess-sucess_rec = P_G_MESS.
    it_sucess-lifnr = it_me21-lifnr.
    it_sucess-tabix = v_count.
    APPEND IT_SUCESS.
    endcase.
    ENDLOOP.
    Describe table it_sucess lines v_ns.
    Describe table it_error lines v_ne.
    ENDFORM. " subr_mess_hand
    Regards
    ANJI

  • Some fields in BAPI_GOODSMVT_CREATE

    Hi Abapers,
    I am usiing BAPI_GOODSMVT_CREATE for the MIGO transaction for creating material document.
    With movement type '101' and MVT_IND = 'B'.
    In this am not able to find out some fields like ' 1. Activate Print (XNAPR) , 2.Quantity in delivery note (LSMNG) , 3. unit of measure (LSMEH).
    Please let me know how to get these field.
    Thanks & Regards,
    Simha S

    hi shakya
    check this thread.
    Re: About BAPI_GOODSMVT_CREATE
    Set parameter is used to set the values of screenfields like checkboxes,
    when u set it as X means u r ticking a checkbox
    Anyways i dont think this has anything to do with ur requirement. I guess so!!
    кu03B1ятu03B9к
    Edited by: kartik tarla on Jan 22, 2009 9:31 AM
    Edited by: kartik tarla on Jan 22, 2009 9:34 AM

  • Quantity Required Does not Match Quantity Withdrawn (LBS)

    Hi,
    I am sometimes noticing a problem where the quantity in our production orders is not getting withdrawn in full.  We are only noticing this when we are consuming in LB.  We have production orders where we calculate the number of LB of material that is required.  When we confirm the production order the material backflushes from inventory - however sometimes leaves .001LB open.  These parts are set to backflush in the material master, and also has a component scrap factor set in the material master.
    For example:  The requirement quantity in the production order (RESB-BDMNG) is 3.608.  After the order is confirmed, and the material backflushes the withdrawn quantity on the production order (RESB-ENMNG) is updated with 3.607.  The finial issue indicator (RESB-KZEAR) on the production order is also checked, which means there are no more planned movements for the order.  It is not a big deal for one or two production orders; but over time we will have hundreds, which will throw off our inventory.
    Any idea why this is happening or if there is a setting somewhere we are missing?
    Thank you for the help.

    In transaction code CUNI click Unit of Measurement for Mass and in there for LB (or LBS whatever unit you're facing problem) change the Decimal places and Decimal pl. rounding to 3. Though system will allow you to enter a number higher than 3, the domain used for all quantity fields in SAP (MENG13, TCode SE11) stores only 3 places of decimals, so it's the system limitation.

  • Change quantity (MENGE) field in G/L posting

    Hi gurus.  I need to be able to change the quantity (BSEG/MENGE) field in a G/L document that has already been posted.  I found the area in config to add the field to be able to change.  So I made the change in config.  Then I pulled up a document that already existed, but the field is still grayed out.  I also created a new entry, then went back in to change mode, and the field is grayed out.  Any ideas?
    Thank you
    Janet

    Not sure about my answer, but I know that you are not allowed to modify any value related fields after a FI document is posted (example, value). So, my guess is by changing the quantity amount will be effected and hence FB02 will not allow you to modify quantity.

  • Project Systems - Quantity withdrawn with reference to network

    Here material is assigned to network. The requirement is 10 nos. But when the quantity is withdrawn from warehouse (mvt 281), it is 15 nos. Now we have withdrawn 5 nos more than requirement.
    Can I cofigure my system so that quntity should not be withdrawn more than the requirement ?

    Hi,
    I have checked this in system. SAP allows to issue more quantity against reservation. To restrict this you will have to go for some development. Look for any userexit available.
    Reward points if helpful.
    Regards
    Message was edited by:
            Shrikant Rakate

  • Field in BAPI_GOODSMVT_CREATE

    Hi ,
    I am using BAPI_GOODSMVT_CREATE for creating GRN , In transcation MIGO , at line item level there is a field which does not exist in GOODSMVT_ITEM table.Please suggest me how to populate the field which does not exist in BAPI_GOODSMVT_CREATE.
    Regards
    Edited by: Subhash Karidhal on Mar 5, 2008 6:06 AM

    Hi,
    I guess you are trying to tell that you need to populate fields which are added in the item table through Append structure.If that is the case then all you need is to populate the "extensionin" field in the tables tab of the FM "BAPI_GOODSMVT_CREATE",here you need to specify the name of the include structure and its values.Hope this helps.
    Regards,
    Kiran
    Edited by: Kiran NN on Mar 5, 2008 6:35 AM

  • Requirement quantity and quantity withdrawn are not matching

    From a production order the requirement quantity of one component is 4 and for another component, it is 2. But the withdrawn quantity for the first component is 5 and for the 2nd component it is 0. This has caused a COGI error.
    Also the total quantity and the delivered quantity is shown as 6.
    How can this be corrected and prevented from happening in the future.

    Hi Jeby,
                Thanks very much for your reply.
    Batch management is not used for both the components.
    For both the components the storage location is mentioned in the components overview of the production order. When I checked in the material master the same storage location is existing in the materiala master also

  • How to enhance extra fields in BAPI_GOODSMVT_CREATE.

    Dear Sap Gurus,
    I am facing a problem . I am using standard bapi for MIGO transaction i.e. BAPI_GOODSMVT_CREATE . it is working fine. in our company, along with BADI, MIGO was modified with two extra tab viz. Waybill and ExchangeRate. Here we are maintaining some of  own developed fields . Plz guide me how can i modify this Bapi so that i can update these developed fields . The appropriate answers will be highly appreciated <removed by moderator>.
    Is there any alternative solution?
    NOTE : Currently Using ECC 5.0 SAP
    Thanks & Regards,
    Vijay
    Edited by: Thomas Zloch on Oct 19, 2010 5:43 PM

    Hello,
    1. Use structure BAPIPAREX for passing custom fields. (There are several blogs/posts on how to make use of this).
    2. In the BAPI i noticed there is a BAdI to populate these fields into your business tables.
    Call BAdI MB_BAPI_GOODSMVT_CREATE to fill own fields
        TRY.
            get badi lo_mb_bapi_GOODSMVT_CREATE.
          CATCH cx_badi_not_implemented.                    "#EC NO_HANDLER
        ENDTRY.
        TRY.
            call badi lo_mb_bapi_goodsmvt_create->extensionin_to_matdoc
              EXPORTING
                EXTENSION_IN = EXTENSIONIN[]
              CHANGING
                CS_IMKPF     = S_IMKPF
                CT_IMSEG     = T_IMSEG[]
                CT_RETURN    = return.
          CATCH cx_badi_initial_reference.                  "#EC NO_HANDLER
        ENDTRY.

Maybe you are looking for