Creation of Goods receipt - MB_CREATE_GOODS_MOVEMENT/BAPI_GOODSMVT_CREATE

Hi Friends,
I need to create a goods receipt for an inbound delivery.
Iam planning to use either MB_CREATE_GOODS_MOVEMENT or BAPI_GOODSMVT_CREATE.
But every time iam getting the error saying that the 101 movement type cant be used.
In my case i need to use both the movement types 101 and 543.
Basically i need to populate both the main item and component material information.
If any one has done this, Can you please give me the sample code.
Regards
Sasi

Hi,
Iam usig the gm_code as 05.
I am paasing the movement indicator ,in that particular field.
    lw_goodsmvt_item-material = lw_imseg-matnr.
    lw_goodsmvt_item-plant = lw_imseg-werks.
    lw_goodsmvt_item-batch = lw_imseg-charg.
  IF lw_imseg-sgtxt = 'F'.
    lw_goodsmvt_item-move_type = '101'.
    lw_goodsmvt_item-mvt_ind = 'B'.
    lw_goodsmvt_item-NO_MORE_GR = 1.
    lw_goodsmvt_item-stge_loc = lw_imseg-lgort.
    ELSEIF lw_imseg-sgtxt = 'C'.
    lw_goodsmvt_item-move_type = '543'.
    endif.
    lw_goodsmvt_item-entry_qnt = lw_imseg-erfmg.
    lw_goodsmvt_item-entry_uom = lw_imseg-erfme.
    lw_goodsmvt_item-expirydate = lw_imseg-mhdat.
    lw_goodsmvt_item-DELIV_NUMB =
    lw_goodsmvt_item-DELIV_ITEM =
am i doing something wrong here.
iam gettign the following error message
Goods movement not possible with mvmt type 101
Goods movement not possible with mvmt type 543

Similar Messages

  • Creation of Goods receipt in ECC from legacy system

    Hi
    I hae to design a synchronous scenario for legacy system to sap ECC for creation of Goods receipt in ECC , pl help which method RFC/BApi , or proxy shall be the best method , keeping in mind the performance .
    rgds
    mojib

    Hi,
    When ever we are dealing with the SAP Systems we have the choice of 3 options to go with
    1) IDOC--When ever we have the standard IDOC and the process is Async
    2) RFC/BAPI-----When ever we have the standard BAPI and the process is Sync
    3) Proxy----When ever we are dealing with large amount of data and the process may be Sync or Async
    /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
    REgards
    Seshagiri

  • Automatic serial number&equipment creation in goods receipt

    Dear gurus,
    We use to automatic serial number&equipment creation in goods receipt. While serial number master datas and equipment master datas were creating in goods receipt, how can we fill some fields for serial number and equipment master datas? (Instead of to use IQ02 and IE02 after every goods receipts for some default enteries) Any user exit or BADI?
    Thank you.

    Use user exits EXIT_SAPLIE01_005 and EXIT_SAPLIE01_007 in customer exit IQSM0005.
    Regards,
    Lakshman

  • Early Inspection Lot Creation on Goods Receipt

    I work for a company that melts steel into batches referred to as Heats.  Each of these Heats are processed through various steps to create tubing.  In the tubing operations multiple Heats are applied to production orders but the integrity of each Heat is always maintained.  If we do a Goods Issue for 6 Heats into a production order, we expect to do a Goods Receipt of 6 Heats from that production order and inherit all of the Heat related characteristics for each Heat processed.  At certain points we do laboratory tests for chemisties and properties of each Heat.  These tests are run while the order is being processed through other operations but need to be recorded against the batch.  We are thinking that we need to do Goods Receipt Inspection with Early Inspection Lot Creation.  It looks like this method will create a single Inspection Lot upon release of the Production order.  Is there a way to create multiple Inspection Lots that will correspond to Heat batches prior to the actual Goods Receipt?

    6 partial GR (Heats) are done against 1 production order? Then, you will have one inspection lot and one usage decision for the entire lot (03 / 04: Goods Receipt Inspection with Early Inspection Lot Creation.).
    Think this: Each heat can be one sample/ inspection point each, in case of early goods receipt. So, if you have 6 samples: 3 pass and 3 fails, then do the Usage decision on 3/6th of the quantity at the end of the test: this needs to done manual stock psting while doing the UD.
    So, you do the inspection at the sample levels, but not at multiple inspection lot level.
    There is a way to create mutiple inspection lots on partial GR for the same process order.
    The logic lies like this, if your previous inspection lot is reset on usage decision, then you will get a new inspection lot when doing a partial GR.
    If the UD is not reset case:
    (a) Usage decision open: It will increase the QI stock in the same inspection lot. This means no new inspection lot creation.
    (b) Usage decision done: It will post to unrestricted, thinking that the rest of the sample is OK!! So, again no new inspection lot creation.
    This I tried on 04 inspection type. I am not sure on 03. Hope this helps!!

  • Import of bulk serial numbers with Goods Receipt

    Hello
    I need to create an Add-On that automates the creation of Goods Receipt PO documents with linked serial numbers. Using the DI API I manage to create the Goods Receipt and link about 1000 serial numbers to one document without any problems. When the item qty (and linked serial number qty) goes beyond 10,000 it crashes (probably runs out of memory).
    I know an alternative would be possibly using the DI Server. Has anyone ever done this with such big volumes? Not sure if the DI Server would be able to handle say 100,000 serial numbers, at a time.
    Any advice is appreciated.
    Thanks,
    Jéan

    Thanks Gordon.
    This is not good news. I am just concerned as the SDK help on DI Server specifically states:
    "Business partners can use the DI Server for the following main scenarios:
    ==>> Heavy duty operations, such as batch"
    I assume this is the same type of "heavy duty operation" as a data take-on would be? Or does it mean that B1's serial number management is limited to small quantities at a time.
    Jéan

  • Good receipt document can't be found

    hi everyone..
    My name angga. currently i simulate make good receipt using BAPI_GOODSMVT_CREATE.
    i am input this field :
    GOODSMVT_HEADRET
    - posting_date -> 20.08.2008      
    - doc_date -> 20.08.2008
    - gm_code -> 01
    GOODSMVT_ITEM
    - material               - entry_qnt                         
    - plant                   - po_number -> 47000001963
    - stge_loc              - po_item -> 10
    - move_type           - no_more_gr -> "X"
                                - mvt_ind -> B
    after i executed, i sucessfully got the GR document/accounting document. But after i check my PO using T-code ME23N , there isn't any good receipt for PO 47000001963.
    Futhermore, i cek in table MKPF and also i can't find the GR document.
    can anyone give me some explenation about this ??
    i hope all of u can help me. thank you
    Regards,
    Anggara Mahardika
    Edited by: Anggara Mahardika on Aug 20, 2008 11:33 AM

    hi dear,
    do like this..
    CALL FUNCTION 'BAPI_GOODSMVT_CREATE'   DESTINATION 'NONE'
               EXPORTING
                    goodsmvt_header       = wa_goodsmvthdr
                    goodsmvt_code         = wa_goodsmvt_code
                    testrun               = w_testrun
               IMPORTING
                    goodsmvt_headret      = wa_goodsmvthdr_ret
                    materialdocument      = w_materialdocument
            MATDOCUMENTYEAR       =
               TABLES
                    goodsmvt_item         = it_goodsmvt_item
            GOODSMVT_SERIALNUMBER =
                    return                = it_return
      IF NOT w_materialdocument IS INITIAL."
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' DESTINATION 'NONE'
          EXPORTING
            wait   = 'X'
          IMPORTING
            return = wa_return.
        IF sy-subrc = 0.
         WRITE: / 'Goods Recieve document saved'  , w_materialdocument.
      MESSAGE  w_materialdocument TYPE 'I'.
        ENDIF.
    Regards,
    Sudarsan

  • Blocking A/P Invoice  without Good Receipt PO

    Dear Sir/Madam,
    Are there any ways to block AP Invoice without creation of Good Receipt PO? The Purchase user whom I want to control need to create PO and AP Invoice. Good Receipt PO is done by warehouse.
    My version is 8.81 PL 06.
    Thankyou.

    hi,
    yes it is possible by using the Store Procedure SP_TranactionNotification.
    pls. use the ff. code
    if @object_type = '18' and @transaction_type ='A'
    begin
         if exists (select T0.itemcode from PCH1 T0 where T0.basetype = '-1' and T0.docentry = @list_of_cols_val_tab_del)
    begin
              set @error = 1
              Set @error_message = 'A/P Invoice Cannot be raised without GRPO Reference'
         end
    end
    open your SQL Management Studio Select your database -->> Programmability -->> StoredProcedure -->> SP_TranactionNotification right click and modify. then you can find
    --     ADD     YOUR     CODE     HERE
    below this one you put the code i provide above and check it.
    regards,
    Fidel

  • Creating goods receipt with refernce to PO number using BAPI_GOODSMVT_CREAT

    Hi Gurus,
    I have a requirment where in, I need to create a goods receipt with reference to a PO number which has been created by BAPI_PO_CREATE1, using another BAPI BAPI_GOODSMVT_CREATE.  How can I do this? what are all the values that I need to fill in GOODSMVT Create BAPI.
    Please help its very urgent... Need to submit by EOD.
    Thanks,
    Suma

    hi
    hope this code will help you,.
    Reward if help.
    REPORT ZRICH_0001 .
    Structures for BAPI
    DATA: GM_HEADER  TYPE BAPI2017_GM_HEAD_01.
    DATA: GM_CODE    TYPE BAPI2017_GM_CODE.
    DATA: GM_HEADRET TYPE BAPI2017_GM_HEAD_RET.
    DATA: GM_ITEM    TYPE TABLE OF
                     BAPI2017_GM_ITEM_CREATE WITH HEADER LINE.
    DATA: GM_RETURN  TYPE BAPIRET2 OCCURS 0 WITH HEADER LINE.
    DATA: GM_RETMTD  TYPE BAPI2017_GM_HEAD_RET-MAT_DOC.
    CLEAR: GM_RETURN, GM_RETMTD. REFRESH GM_RETURN.
    Setup BAPI header data.
    GM_HEADER-PSTNG_DATE = SY-DATUM.
    GM_HEADER-DOC_DATE   = SY-DATUM.
    GM_CODE-GM_CODE      = '04'.                                " MB1A
    Write 971 movement to table
    CLEAR GM_ITEM.
    MOVE '412'                 TO GM_ITEM-MOVE_TYPE     .
    MOVE 'Q'                 TO GM_ITEM-SPEC_STOCK.
    MOVE '3800533484'  TO GM_ITEM-MATERIAL.
    MOVE '1'     TO GM_ITEM-ENTRY_QNT.
    *MOVE 'PC'    TO GM_ITEM-ENTRY_UOM.
    MOVE '1060'  TO GM_ITEM-PLANT.
    MOVE '0007'  TO GM_ITEM-STGE_LOC.
    *MOVE '0901'   TO GM_ITEM-MOVE_REAS.
    MOVE 'P203601001' TO GM_ITEM-WBS_ELEM.
    MOVE 'P203601001' TO GM_ITEM-VAL_WBS_ELEM.
    APPEND GM_ITEM.
    Call goods movement BAPI
    CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
         EXPORTING
              GOODSMVT_HEADER  = GM_HEADER
              GOODSMVT_CODE    = GM_CODE
         IMPORTING
              GOODSMVT_HEADRET = GM_HEADRET
              MATERIALDOCUMENT = GM_RETMTD
         TABLES
              GOODSMVT_ITEM    = GM_ITEM
              RETURN           = GM_RETURN.
    IF NOT GM_RETMTD IS INITIAL.
      COMMIT WORK AND WAIT.
      CALL FUNCTION 'DEQUEUE_ALL'.
    ELSE.
      COMMIT WORK AND WAIT.
      CALL FUNCTION 'DEQUEUE_ALL'.
    ENDIF.
    WRITE:/ GM_RETMTD.
    LOOP AT GM_RETURN.
      WRITE:/ GM_RETURN.
    ENDLOOP.
    check the BAPI_GOODSMVT_CREATE.
    Functionality
    You can use this method to create a material document for a goods movement.
    You can only create one material document each time you call up the method.
    You can use a simulation function before posting the goods movement to check how the data is updated in the database. The standard system is configured so that the goods movement is posted immediately without simulating beforehand.
    Ensure that you transfer the data in the same way as it is run in the database, for example,
    Material number 18-figure with leading zeros
    Batches with uppercase letters
    Note that for all transactions/events listed below, the posting date is entered in the header data of the material document. In the BAPI2017_GM_HEAD_01 interface, fill the PSTNG_DATE (import structure GOODSMVT_HEADER) field.
    Notes
    Authorization check check
    In the MM Inventory Management component, the method does not execute any authorization checks.
    Note that during a posting of a goods movement, depending on the business transaction of the system, authorization objects of other applications can also be checked.
    Transfer
    The following information about the material document that is to be created is transferred to the method:
    a structure with header data
    a structure with the code for the movement
    a table with the item data
    a table with the serial numbers
    The posting is carried out in the SAP R/3 via the MB_CREATE_GOODS_MOVEMENT function module.
    Confirmations
    Messages are returned in the Return parameter. The parameter documentation shows the return codes and their meanings.
    Further Information
    The method can only carry out your function if no error messages were generated in the Return table. This is the case if the header data and all the items were processed successfully.
    Transaction control is not implemented. The calling program therefore has to execute the Commit Work itself after this method has been successfully called (in other words, if no errors were reported in the Return parameter).
    Which fields have to be filled during the various transactions/ events?
    The following sample scenarios demonstrate which fields have to be filled for which business transactions/events (code).
    There are the following types of transactions/events:
    1. GM_Code 01: Goods receipt for purchase order
    2. GM_Code 02: Goods receipt for production order
    3. GM_Code 03: Goods issue
    4. GM_Code 04: Transfer posting
    5. GM_Code 05: Other goods receipts
    6. GM_Code 06: Reversal of goods movements
    7. GM_Code 07: Subsequent adjustment to a subcontract order
    Entering the movement indicator
    Depending on the transaction, you must enter the following in the movement indicator:
    GM_Code 01 (Goods receipt for purchase order): B
    GM_Code 02 (Goods receipt for production order): F
    For all other transactions, you leave the field blank.
    For 1: GM_Code 01: Goods receipt for purchase order
    Purchase order known
    The following fields have to be filled:
    Purchase order
    Purchase order item
    Movement type
    Movement indicator
    Quantity in unit of entry
    ISO code unit of measurement for unit of entry or
    quantity proposal
    The following fields may have to be filled in some cases (incomplete listing):
    Shelf life expiration date (if it has been configured like this in the system)
    Reason for movement (if it has been configured like this in the system)
    Batch (if the material is handled in batches and batch numbers are not assigned automatically)
    Storage location (if a storage location has not been specified in the purchase order item)
    The following fields can be filled (incomplete listing):
    Stock type
    Item text
    Unloading point
    Delivery completed indicator
    You cannot fill the following fields (incomplete listing):
    Account assignment fields (account assignment is adopted from the purchase order)
    Reservation
    Receiving/issuing material
    Receiving/issuing plant
    Receiving/issuing storage location
    In the case of a purchase order item with the "subcontracting" item category, only the GR item in the interface is to be transferred. The system automatically determines GI items.
    Purchase order unknown: Shipping notification known
    The following fields have to be filled:
    Delivery
    Delivery item
    Movement type
    Other fields, such as those under "Purchase order known". The system determines the relevant purchase order item via the delivery/delivery item.
    Purchase order unknown: Purchase order should be created automatically
    The following fields have to be filled:
    Material number
    Plant
    Storage location
    Vendor
    Movement type
    Movement indicator
    Quantity in unit of entry
    ISO code unit of measurement for unit of entry
    The following fields may have to be filled in some cases (incomplete listing):
    Shelf life expiration date (if it has been configured like this in the system)
    Reason for movement (if it has been configured like this in the system)
    Batch (if the material is handled in batches and batches are not assigned automatically)
    The following fields can be filled (incomplete listing):
    Stock type
    Item text
    Unloading point
    You cannot fill the following fields (incomplete listing):
    Account assignment fields (automatic creation of purchase order items with account assignment is not supported)
    Reservation
    Receiving/issuing material
    Receiving/issuing plant
    Receiving/issuing storage location
    Purchase order unknown: A purchase order should not be created
    The following fields have to be filled:
    Material number
    Plant
    Storage location
    Vendor
    Movement type
    Movement indicator
    Quantity in unit of entry
    ISO code unit of measurement for unit of entry
    The following fields may have to be filled in some cases (incomplete listing):
    Shelf life expiration date (if it has been configured like this)
    Reason for movement (if it has been configured like this)
    Batch (if the material is handled in batches and automatic assignment of batch numbers is not set)
    The following fields can be filled (incomplete listing):
    Special stock indicator
    Item text
    Unloading point
    Goods recipient
    The following fields cannot be filled (incomplete listing):
    Account assignment fields (automatic creation of purchase order items with account assignment is not supported)
    Reservation
    Receiving/issuing material
    Receiving/issuing plant
    Receiving/issuing storage location
    Receiving/issuing batch
    The input combinations listed above for the GM_CODE 01 can be combined within an input table so that they can be posted in a material document. Items can also be posted for different purchase orders, provided that all the purchase orders refer to the same vendor.
    Transfer of subcontracting components
    During the posting of the ordered material of a subcontract order with movement type 101, for the transfer of the subcontracting components, the filled unique identification of the document line (LINE_ID) is also required.
    More information on LINE_ID and PARENT_ID
    The following fields have to be filled for the components:
    Unique identification of the document line
    Identification of the immediately superior line
    Material number
    Plant
    Storage location
    Quantity in unit of entry
    The following fields can be filled for the components:
    All other fields in the method that are included in this list.
    The following fields cannot be filled for the components:
    All fields that are not included in the list above. The movement indicator must be initial.
    Additional fields in goods-receipt-based invoice verification
    When you post a goods receipt to purchase order with movement type 102, an issue with reference to a previously posted goods issue, the following fields must also be transferred:
    REF_DOC_IT (LFPOS): Item of a reference document
    REF_DOC (LFBNR): Document number of a reference document
    REF_DOC_YR (LFBJA): Fiscal year of a reference document
    Only when you transfer these fields is it guaranteed that the reference to the original goods movement stay the same.
    For 2 GM_Code 02: Goods receipt for production order
    The following fields have to be filled:
    Order
    Movement type
    Movement indicator
    Quantity in unit of entry
    ISO code unit of measurement for unit of entry or
    quantity proposal
    The following fields may have to be filled in some cases (incomplete listing):
    Shelf life expiration date (if the system has been configured like this)
    Reason for movement (if the system has been configured like this)
    Batch (if the material is handled in batches and automatic batch number assignment is not set)
    Storage location (if storage location has not been specified in the order)
    The following fields can be filled (incomplete listing):
    Order item (co-product)
    Stock type
    Item text
    Unloading point
    "Delivery completed" indicator
    The following fields cannot be filled (incomplete listing):
    Account assignment fields (the account assignments are adopted from the purchase order)
    Reservation
    Receiving/issuing material
    Receiving/issuing plant
    Receiving/issuing storage location
    Receiving/issuing batch
    For 3 GM_Code 03: Goods issue
    Goods issue without reference to a reservation
    The following fields have to be filled:
    Material number
    Plant
    Storage location
    Movement type
    Movement indicator
    Quantity in unit of entry
    ISO code unit of measurement for unit of entry
    The following fields may have to be filled in some cases (incomplete listing):
    Special stock (e.g. sales order, project, vendor etc.)
    Shelf life expiration date (if the system is configured like this)
    Reason for movement (if the system has been configured like this)
    Batch (if the material is handled in batches and automatic batch number assignment is not set)
    Account assignment fields
    The following fields can be filled (incomplete listing):
    Special stock indicator
    Item text
    Unloading point
    Goods recipient
    The following fields cannot be filled (incomplete listing):
    Reservation
    Receiving/issuing material
    Receiving/issuing plant
    Receiving/issuing storage location
    Receiving/issuing batch
    Goods issue with reference to a reservation
    The following fields have to be filled:
    Reservation number
    Reservation item
    Record type of the reservation
    Movement indicator
    Quantity in unit of entry
    ISO code unit of measurement for unit of entry
    The following fields may have to be filled in some cases (incomplete listing):
    Shelf life expiration date (if this has been configured in the system)
    Reason for movement (if this has been configured in the system)
    Batch (if the material is handled in batches and automatic batch number assignment is not set)
    Storage location (if not planned in the reservation)
    The following fields can be filled (incomplete listing):
    Special stock indicator
    Item text
    Unloading point
    Goods recipient
    The following fields cannot be filled (incomplete listing):
    Movement type
    Material
    Plant
    Account assignment fields
    For 4 GM_Code 04: Transfer posting
    Transfer posting without reference to a reservation
    The following fields have to be filled:
    Material number
    Plant
    Storage location
    Movement type
    Movement indicator
    Quantity in unit of entry
    ISO code unit of measurement for unit of entry
    The following fields may have to be filled in some cases (incomplete listing):
    Receiving material
    Receiving plant
    Receiving storage location
    Receiving batch (if material is handled in batches and you want to change batches)
    Receiving/issuing special stock (e.g. sales order, project, vendor etc.)
    Shelf life expiration date (if this has been configured in the system)
    Reason for movement (if this has been configured in the system)
    Batch (if the material is handled in batches and automatic batch number assignment is not set)
    The following fields can be filled (incomplete listing):
    Special stock indicator
    Item text
    Account assignment fields (for automatic posting lines: Expense/income from stock transfer)
    The following fields cannot be filled (incomplete listing):
    Reservation
    Transfer posting with reference to a reservation
    See goods issue with reference to a reservation
    For 5 GM_Code 05: Other goods receipts
    Other goods receipt without reference to a reservation
    See goods issue without reference to a reservation
    Other goods receipt with reference to a reservation
    See goods issue with reference to a reservation
    For 6 GM_Code 06: Reversal of goods movements
    You can use the Cancel method to reverse goods movements. But you may also want to cancel a goods movement without referring to a material document (see the Cancel method).
    If you want to work without referring to the document, you have to fill the field BAPI_GM_ITEM_CREATE-XSTOB in the interface (import table GOODSMVT_ITEM). In this case, the system converts the movement type assigned in the interface to the reversal movement type. Alternatively, you can set the reversal movement type in the interface. In this case, the BAPI_GM_ITEM_CREATE_XSTOB field must be transferred blank.
    If you want to cancel a goods movement with reference to a reservation (without using the Cancel method) you can only transfer the field BAPI_GM_ITEM_CREATE_XSTOB if it is filled. Movement types are not transferred when you post with reference to a reservation, as the movement type is contained in the reservation item.
    For 7. GM_Code 07: Subsequent adjustment to a subcontract order
    Ordered material of subcontract order
    The following fields have to be filled:
    Unique identification of document line (can be assigned to anything)
    Posting date in document header
    Document number of purchasing document
    Item number of purchasing document
    Material number check
    Plant check
    Movement type (select movement type 121)
    Movement indicator (must be O)
    Further entries are not allowed. The entry quantity for the ordered material of a subcontract order must be zero.
    Components
    The following fields have to be filled:
    Unique identification of document line (can be assigned to anything)
    Identification of the immediately superior line
    Plant
    Material number check
    Quantity in unit of entry; can also be negative
    The following fields can be filled:
    Storage location
    All other fields in the method that are included in this list.
    The following fields may not be filled:
    All fields that are not in the list above. The movement indicator must be blank.
    More information on LINE_ID and PARENT_ID
    Additional fields in goods-receipt-based invoice verification
    When you post a subsequent adjustment, the following fields must also be transferred:
    REF_DOC_IT (LFPOS): Item of a reference document
    REF_DOC (LFBNR): Document number of a reference document
    REF_DOC_YR (LFBJA): Fiscal year of a reference document
    Only when you transfer these fields is it guaranteed that the reference to the original goods movement stays the same.

  • Error in creation of purchase materials/Goods receipt against PO(FI-MM)

    Hi All,
    While processing FI - MM integration iam facing below errors,request to guide me with same
    1) While creation of purchase materials
    Valuation class 7920 not allowed for material type Raw material Message no. M3180
    Diagnosis
    The combination of values you have entered is not defined in the system.
    Procedure
    Check your entries, and choose a valid value or combination of values with F4.
    I have crossed checked in t code OMSK valuation class 7920 exists.
    2) Goods receipt against PO:
    Number range for trans./event type WE in year 2014 does not exist Message no. M7562
    Diagnosis
    The number range for document number assignment has not been maintained in the year 2014 for the transaction/event type WE.
    Procedure
    Contact your system administrator.
    in second case i have maintained number ranges in OBA7,OMBT,still iam facing with the same issue
    Regards
    Santosh

    Hi Dev,
    Thanks for your reply...yea i have done the ground work before posting this query
    but bitt confused with the post i have come across..
    Problem was occurring due to the wrong updating of raw material instead of finished goods in  MM01 (CREATION OF PURCHASE MM)
    however i have over come my 2nd issue,hopefull will over come my 1st issue also
    Thanks a lot
    Santosh 

  • Automatic creation of transfer orders from goods receipt of purchase order.

    Hi experts
    The project i am currently working on requires the following;
    When goods receipting a purchase order i have a requirement for the system to create automatic transfer orders to put the stock away into storage bins.  I am aware that the stock goes straight into the 902 area once goods receipted.  Is it possible to have the transfer orders created automatically out of 902 once the goods receipt has been posted.
    In support of this, i have made an entry in transaction OMKX for the following;
    Reference Movement Type - 101
    Movement Indicator - B (goods movement for purchase order)
    Movement Type - 101
    TR Create Transfer requirement - X
    Immed. TO Creation - A
    Addl Data - X
    Once i receipt the PO it just sits in 902 and does not create any automatic transfer orders.
    Could someone please help me
    Thanks
    Simon

    Please try to process the material document of the GR manually by LT06 in foreground to find out the root cause of the error.
    You may also want to setup the mail control (V_T321-MAILK) for immediate TO creation in OMKX. The system will send you a express message (depending on your setup) if TO creation is failed.

  • Goods receipt Capacity check in PO creation- EHP2

    Hi
    I have activated business function LOG_MM_CI_1 in our ECC 6.0 system . I have also activated Goods receipt capacity check and subsequent settings in customization . I am able to view the GR capacity check icon in Purchase order creation (ME21N). When I click this icon by selecting the line item , system does not perform any function . I have read in SAP documentation that Vendor can be assigned to door . I am not able to find this assignment in the system . Not sure whether this function is only applicable to retail system and not to SAP R/3 . If some one worked on this functionality , kindly request you to throw some light on this functionality .
    with regards,
    Joseph Anand B

    Same thing is happening to me right now .. did you found out what the error was,, or what was missing ?
    Please reply soon as I have a demo on the same in two days..
    Regards
    Digant.

  • Goods Receipt Report With 101 movement type using bapi_goodsmvt_create

    Dear Abapers,
            i am getting some problem, i got requirement like Goods Receipt Report with 101 movement type using
    bapi_goodsmvt_create and data should upload through excel sheet.
    still facing problems, i have searched sdn forum n sdn code also, but relevant answer i could not find.
    What are all the inputs i need to take and please give some valuable inputs to me.
    please do help ..... thanks for advance..
    Thanks & regards,
    Vinay.
    Moderator message : Spec dumping is not allowed, show the work you have already done. Thead locked.
    Edited by: Vinod Kumar on Sep 27, 2011 10:58 AM

    Dear Abapers,
            i am getting some problem, i got requirement like Goods Receipt Report with 101 movement type using
    bapi_goodsmvt_create and data should upload through excel sheet.
    still facing problems, i have searched sdn forum n sdn code also, but relevant answer i could not find.
    What are all the inputs i need to take and please give some valuable inputs to me.
    please do help ..... thanks for advance..
    Thanks & regards,
    Vinay.
    Moderator message : Spec dumping is not allowed, show the work you have already done. Thead locked.
    Edited by: Vinod Kumar on Sep 27, 2011 10:58 AM

  • Posting a goods Receipts by using 'BAPI_GOODSMVT_CREATE'

    Hi experts,
    For a Handling Unit number, im Posting a goods Receipts by using 'BAPI_GOODSMVT_CREATE'
    Im passing the below values to the BAPI, to create a Material document and transfer order.
    GOODSMVT_HEADER- PSTNG_DATE (System Date)
    GOODSMVT_HEADER - DOC_DATE (System date)
    GOODSMVT_HEADER- PR_UNAME (SY-NAME)
    GOODSMVT_CODE- GM_CODE ( 01)
    GOODSMVT_ITEM-MOVE_TYPE (Movement type): movement type '101'
    GOODSMVT_ITEM- DELIV_NUMB_TO_SEARCH (Delivery)
    GOODSMVT_ITEM-DELIV_ITEM_TO_SEARCH (Delivery item)
    GOODSMVT_ITEM-PLANT (Plant) VEPO- WERKS
    GOODSMVT_ITEM-STGE_LOC (Storage location) VEPO- LGORT
    GOODSMVT_ITEM-ENTRY_QNT (Quantity)
    GOODSMVT_ITEM-ENTRY_UOM (Unit of measure)
    GOODSMVT_ITEM-PO_NUMBER (Purchase order)
    GOODSMVT_ITEM-PO_ITEM (Purch. order item)
    GOODSMVT_ITEM-UNLOAD_PT ( HU number)
    GOODSMVT_ITEM-MVT_IND (Movement indicator) = 'B'
    I dont know what values has to be passed to the following fields in BAPI
    *GOODSMVT_ITEM-SU_PL_STCK_1*
    *GOODSMVT_ITEM-SU_PL_STCK_2*
    *GOODSMVT_ITEM-ST_UN_QTYY_1*
    *GOODSMVT_ITEM-ST_UN_QTYY_2*
    *GOODSMVT_ITEM-UNITTYPE_1*
    *GOODSMVT_ITEM-UNITTYPE_2*
    All those values has to be updated in the Material document.
    Please help me on this.
    Thanks & regards,
    Leo
    Edited by: Thomas Zloch on Nov 17, 2011 10:11 AM

    I konw that I'm digging an old thread but let's have a look. I have the same problrm (filling the DMBTR field from the BAPI). I have not tried yet but checking the code of the BAdI I found that the EXTENSIONIN_TO_MATDOC method of the MB_BAPI_GOODSMVT_CREATE BAdI is called before creating the material posting and it has the IMSEG table as changing parameter. I will give it a try soon. Hope that it will work.
    Has anyone experience with it by any chance?
    Adam

  • Automatic creation of po during goods receipt

    Dear all,
    po has not been created, but while receiving the material i want automatic generation of po. i have some knowledge about it but it is not working. Can some one send detailed information. with navigation details. Tips that are posted on the sdn is not working.
    Regards

    Hi
    Pl Make sure you have done following settings for the Automatic Creation of PO during GR:
    1) In SPRO ---> Enterprise Structure ---> Assignment -
    >  Material Management ---> Assign Std. Purchase Org. to your Plant...
    2) In Material Master -
    > Purchasing View -
    > Pl. Check. Automatic PO check Box   and  Maintain Purchasing Group....
    3)Create your Vendor for oyur Company Code and  Std. Pur. Org. combination and in that Vendor Master -> Purchasing Data View--- > Pl. Check Auto. PO Check Box...
    4)For your Vendor -Material Master - Plant -Std. Pur. Org combination Maintain valid Info record...
    5)In OLMB --->  Goods Receipt -
    > Automatic Creation of PO ---> for the M.Type:101  pl. check  Auto PO check Box
    6) In OLMB ---> Movement types ---> Copy,Delete, Check M.Types ---> Choose the M.Type:101   and go into Details -
    > Then goto  allowed Fields for M.Types for M.Type:101 --->  there for the M.Type:101   make the field   LIFNR as a Mandatoty field...
    If you have done the above settings properly...then  in  MIGO ---> Choose Transaction GR  and referance as Others
      and do the GR....Make sure you are doing GR with M.Type:101....and yougive the Vendor's name during   GR....
    Now If you save the GR ...automatically PO will be created...
    this you can see it by displaying the MIGO Document..
    Reward if useful
    Regards
    S.baskaran

  • Call BAPI_GOODSMVT_CREATE to create a goods receipt for purchase order

    Hi,
    I'm calling the bapi BAPI_GOODSMVT_CREATE to create a goods receipt for purchase order, but the following code doesn't work. It doesn't give me any kind of error message but it does nothing as well...
    Can anyone help me please?
    Thank You
    Hugo
    Code
    DATA: wa_goodsmvt_header  LIKE bapi2017_gm_head_01,
                            wa_goodsmvt_code    LIKE bapi2017_gm_code,
                            wa_bapi2017_gm_head TYPE bapi2017_gm_head_ret-mat_doc.
                      DATA: it_goodsmvt_item LIKE bapi2017_gm_item_create OCCURS  0 WITH HEADER LINE,
                            it_return        LIKE bapiret2 OCCURS  0 WITH HEADER LINE.
                      wa_goodsmvt_header-pstng_date = SY-DATUM.
                      wa_goodsmvt_header-doc_date   = SY-DATUM.
                      wa_goodsmvt_header-ref_doc_no = '4500000020'.
                      wa_goodsmvt_code-gm_code = '01'.          "Goods receipt for purchase Order
                      it_goodsmvt_item-stge_loc  = 'BPF2'.
                      it_goodsmvt_item-move_type = '101' .
                      it_goodsmvt_item-entry_qnt = 17.
                      it_goodsmvt_item-entry_uom = 'KG'.
                      it_goodsmvt_item-mvt_ind   = 'B'.
                      it_goodsmvt_item-po_number = '4500000020'.
                      it_goodsmvt_item-po_item   = '00010'.
                      it_goodsmvt_item-material  = '50'.
                      APPEND it_goodsmvt_item.
                      CALL FUNCTION  'BAPI_GOODSMVT_CREATE'
                        EXPORTING
                          goodsmvt_header  = wa_goodsmvt_header
                          goodsmvt_code    = wa_goodsmvt_code
                        IMPORTING
                          materialdocument = wa_bapi2017_gm_head
                        TABLES
                          goodsmvt_item    = it_goodsmvt_item
                          return            = it_return.
                        data: begin of errmsg occurs 10.
                                include structure bapiret2.
                        data: end of errmsg.
                        data: wmenge like iseg-menge,
                              errflag.
                        clear errflag.
                        loop at errmsg.
                          if errmsg-type eq 'E'.
                            write:/'Error in function', errmsg-message.
                            errflag = 'X'.
                          else.
                            write:/ errmsg-message.
                          endif.
                        endloop.
                        if errflag is initial.
                          commit work and wait.
                          if sy-subrc ne 0.
                            write:/ 'Error in updating'.
                            exit.
                          else.
                            write:/ 'Ok'.
                          endif.
                        endif.
                        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
                        EXPORTING
                        wait = ' '.

    Hi,
    Thank you for the asnwer! I'm a rookie at ABAP so please forgive my stupid questions
    I've changed the code to:
    DATA: wa_goodsmvt_header  LIKE bapi2017_gm_head_01,
                            wa_goodsmvt_code    LIKE bapi2017_gm_code,
                            wa_bapi2017_gm_head TYPE bapi2017_gm_head_ret-mat_doc.
                      DATA: it_goodsmvt_item LIKE bapi2017_gm_item_create OCCURS  0 WITH HEADER LINE,
                            it_return        LIKE bapiret2 OCCURS  0 WITH HEADER LINE.
                      wa_goodsmvt_header-pstng_date = SY-DATUM.
                      wa_goodsmvt_header-doc_date   = SY-DATUM.
                      wa_goodsmvt_header-ref_doc_no = '4500000020'.
                      wa_goodsmvt_code-gm_code = '01'.          "Goods receipt for purchase Order
                      it_goodsmvt_item-plant     = 'BP01'.
                      it_goodsmvt_item-stge_loc  = 'BPF2'.
                      it_goodsmvt_item-move_type = '101' .
                      it_goodsmvt_item-entry_qnt = 10.
                      it_goodsmvt_item-entry_uom = 'KG'.
                      it_goodsmvt_item-mvt_ind   = 'B'.
                      it_goodsmvt_item-po_number = '4500000020'.
                      it_goodsmvt_item-po_item   = '10'.
                      it_goodsmvt_item-material  = '50'.
                      APPEND it_goodsmvt_item.
                      CALL FUNCTION  'BAPI_GOODSMVT_CREATE'
                        EXPORTING
                          goodsmvt_header  = wa_goodsmvt_header
                          goodsmvt_code    = wa_goodsmvt_code
                        IMPORTING
                          materialdocument = wa_bapi2017_gm_head
                        TABLES
                          goodsmvt_item    = it_goodsmvt_item
                          return            = it_return.
                          write:/ it_return-message.
    And the return message is : Material document data and PO data do not match (Material)
    Any idea of what might be the problem?
    Thanks

Maybe you are looking for