Hi gurus bapi_goodsmvt_create

hi all
i am new to bapi.
i have used bapi_goodsmvt_create to upload open POs to sap and for each PO there is GR no and GR may have multiple POs.
when i am running prog, i need to process all the PO even if there is error with one GR i.e. out of 100 records 80 are process and 20 are not processed because one GR has 20 POs, but these POs are open and needs to be processed, how to process these 20 POs.
awaiting reply
rocky

Hi ,
u need to change the PO qty = confirmed qty , then only u can go ahead.
regards
Prabhu

Similar Messages

BAPI_GOODSMVT_CREATE - posting extra lines (amount being multiplied by 100)

Hello Gurus,
I am using BAPI_GOODSMVT_CREATE for posting.
When I check FBL3N, i see 2 lines:
The first one is correct while the second is a copy of the first one, with the exeception that the amount in Local Currency has been multiplied by 100. And this second line is not required.
I am passing only one line to the BAPI and I get 2 lines as output.
Has anyone encountered this problem before?
Thanks for your precious help.
Regards,
Parvez

Hello,
Here are some more information:
goodsmvt_code-gm_code    = '02'.
goodsmvt_item-move_type      = '101'.
The posting done in NISL is in fact done twice in SAP ECC6 :
a)      at normal standard price of the materials
b)      at standard price * 100 (current issue).
In 46C version, the posting was done only once at the standard price of the material. (correct)
In SAP ECC6, 2 postings are done:
            - Posting a) correct.
            - Posting b) multiplied by 100 should not exist. This error should be corrected.
seem to be related to the upgrade?
Any hint on this?
Thanks

BAPI_GOODSMVT_CREATE - error for movement type 343 (movement code - 04)

Hi Gurus,
I am using BAPI_GOODSMVT_CREATE for doing transfer posting MB1B.
I need to do transfer posting using movement type - 343 "Blocked to Unrestricted stock"
Movement type - 343
GOODSMVT_CODE - 04 (transfer posintg)
I am getting error message -
E /CWM/MM              001 Transfer the parallel entry quantity/entry unit of measure
Help me with some pointers.
Thanks,
Madan

Rajesh,
Here is my code for line items:
MATERIAL                       100001374
PLANT                          1AAE
STGE_LOC                       B100
BATCH                          0111331309
MOVE_TYPE                      343
ENTRY_QNT                                10.000
ENTRY_UOM                      EA
Let me know should I need to fill any other fields.
Thanks,
Madan

BAPI_GOODSMVT_CREATE Problem with movement 161

Hi Gurus,
I have a problem with BAPI_GOODSMVT_CREATE and movement type 161. We used to put 161 as the movement type when referencing a PO with "Returns Item" marked. Movement was properly posted. But now I am facing the following issue, when trying to post 161 I have the message "No goods receipt possible for purchase order 4200000084 ...", If I use movement type 101 system will assume 161 and everything is OK, but I don't understand why I could use 161 before and now I can´t, this is happening with all my POs with "Returns Item" marked.
I understand that I can just use 101, the problem is that this will require a change in a non-SAP system... that is why we prefer still using 161.
Any help will be highly appreciatted.
Thanks!

Hi,
Check this link;
Re: BAPI_GOODSMVT_CREATE for movement type 161
Regards

BAPI_GOODSMVT_CREATE for movement type 161, issues in PO creation

Hello Gurus,
I am using movement type 161 with BAPI_GOODSMVT_CREATE in order creating a vendor PO based on the goods receipt posted with the BAPI.
It works fine, nevertheless due to business requirements, I need to apply the following changes:
- in SAP standard the order type is NB by default but in our case I would like to force another order type using the same range that NB. I guess this could be done by activating exit ZXM06U17 (MM06E003). Does someone could confirm it?
- in our process, the purchasing group is not maintained at vendor level (LFM1-EKGRP) but as this field is mandatory in the PO creation and as this data can not be maintained in BAPI_GOODSMVT_CREATE, does someone know if it would be possible to force this value during the PO creation (EKKO-EKGRP) based on a maintenance table? If yes in which user-exit? Exit ZM06U43 could be used?
- furthermore, our specific PO type should have a specific account assignement EKPO-KNTTP instead of the default value U, does someone know if it would be possible to force this value during the PO creation (EKKO-EKGRP) based on a maintenance table? If yes in which user-exit? Exit ZM06U43 could be used?
Kind regards
Chris

Hi Priya,
Just want to share with your guys how to fit this error in BAPI_GOODSMVT_CREATE.
For movement type 161 of PO return you have to pass movement type 101 instead of 161
goodsmvt_item-bwart = 101. After that standard function will determine 101 to 161 automatically and
post that material doc.
NOTE:
In my case
It just heppen only the FIRST time that you do movement with PO Return wich is needed to pass
101 in stead of 161 but after that you can pass 161 the system will continue process correctly.
Hope it help.
Sayan.

Error throws in "BAPI_GOODSMVT_CREATE"

Hey gurus,
After i am executing this bapi "BAPI_GOODSMVT_CREATE", in the error table "return" i am getting the messages like"Posting only possible in periods 2007/11 and 2007/10 in company code 1003".
Could any one of you calrify this asap?

Looks like your posting periods are not open.. check your posting date
or
please contact your functional consultant..
there is a report which can open the posting periods for you..The program name should be (RMMPERI) . .but contacting your functional consultant is the best thing to do.
Message was edited by:
Srihari Hebbar

BAPI_GOODSMVT_CREATE update VBFA or not for Outbound Delivery?

Dear Gurus,
When I try to use BAPI_GOODSMVT_CREATE to do the goods receipt for the outbound delivery as the replacement for MIGO transaction, I use 01 as movement code and the bapi create material document and updating MSEG. But it doesn't update VBFA so the items is still showed in MIGO and cannot post there (because it is already moved in BAPI in program.)
Anybody have any suggestion for this situation? Thanks a lot and points will be rewarded.

Hello,
When you use BAPI_GOODSMVT_CREATE to post Goods Receipt for outbound delivery, reference documents at header and line items should be delivery number and line numbers (BAPI2017_GM_HEAD_01-REF_DOC_NO, BAPI2017_GM_ITEM_CREATE-DELIV_NUMB_TO_SEARCH & BAPI2017_GM_ITEM_CREATE-DELIV_ITEM_TO_SEARCH). Then only document flow will be updated.
Thanks,
Venu

BAPI_GOODSMVT_CREATE for Outbound delivery

Hi Gurus,
I am using BAPI_GOODSMVT_CREATE for creation of GRN against a Outbound delivery
I am able to create the same using MIGO,but not with the help of this bapi
i have passed GM_CODE as 01 and MVT_IND as L
and all relevant datas but it throws an error
E M7 226 Update control of movement type is incorrect (entry 101 X X _ L)
What shall i do??
Can any one help me?

Hi,
Leave MVT_IND as blank.
And be sure to provide delivery number and item and other shipping details.
Leave rest part as it is.
Regards,
Sunny

BAPI_GOODSMVT_CREATE with Serial Number

Dear Gurus,
Scenario
We have to transfer serialized Material from one plant to another via STO
ST order --> Delivery --> PGI (with Serial Number) --> MIGO at recieving plant.
For MIGO (101) movement we want to use BAPI_GOODSMVT_CREATE.
Now we have tried many combinations for it.
if we se GM_CODE = '01'. and Movement Indicator 'B' (for purchase orders) then it gives error "Maintain Serial number."
So if we maintaine serial number in thetable it says that you "cannot assign this serial number to the material "(AS the serial no is attached to the material at the time of PGI).
Now if we try to change the the movement Indicator to 'L' (for deliveries) we are getting the error "Update control of movement type is incorrect (entry 101 X X _ L) "
We have maintianed all necessary fields otherwise it would not give he Maintain srial no error (we think). I know this is very technical. but if anyone has prior knowledge please Help
Dany

hI,
I have on similar error and i made this .
header
   IT_HEADER-PSTNG_DATE = SY-DATUM.
   IT_HEADER-DOC_DATE   = SY-DATUM.
   IT_HEADER-PR_UNAME   = SY-UNAME.
   IT_HEADER-HEADER_TXT = W_NUMDOC .
   IT_HEADER-REF_DOC_NO = IT_INPUT-NUMFR.
Tcod MB01
   IT_CODE-GM_CODE = '01'.
Fill item
   IT_ITEM-MATERIAL   = IT_PEDNEC-MATNR.     "Material Code
   IT_ITEM-PLANT      = ZGSARMZ-WERKS.
   IT_ITEM-MOVE_TYPE = ZGSMOVMOT-TPMOV1.    "Mov. Type
If necessary used table T156t
the field KZBEW most be used in th internal table .
IT_ITEM-MVT_IND
   IT_ITEM-MVT_IND    = 'B'.
   IT_ITEM-ENTRY_QNT = ABS( IT_INPUT-QTDSEL ).
   IT_ITEM-ENTRY_UOM = 'UN'.
   IT_ITEM-PO_NUMBER = IT_INPUT-EBELN.
   IT_ITEM-PO_ITEM    = IT_INPUT-EBELP.
IT_ITEM-STGE_LOC   = .
IT_ITEM-BATCH      = .
IT_ITEM-COSTCENTER = .
IT_ITEM-CUSTOMER   = .
   APPEND IT_ITEM.
Regards .
pedro

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.

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.

Problem using BAPI--BAPI_GOODSMVT_CREATE

Hi Gurus,
I am trying to use the BAPI--BAPI_GOODSMVT_CREATE for performing goods reciepts but it is giving the Error "No stock posting possible for this material", When i try to use the MIGO for the same the posting is done. Can any one please suggest me what is the problem with the BAPI and how to correct it?
Thanks in advance
Anoop

Hi Jurgen,
I have done that still it is giving the same error, any other suggestions??
Regards
Anoop

User Exit triggers BAPI BAPI_GOODSMVT_CREATE

Hi Super Gurus!
I have a complex situation, till now no solution is being provided.
Does anybody know how can I trigger the BAPI BAPI_GOODSMVT_CREATE in a plant for make automatic recepction of a STO?
I wanted to trigger it once shipment is another plant
Any Guru idea?
Thanks in advance and best regards

Nothing is in CMOD since you haven't created a project yet.
Try transaction SMOD and search for V56* and then you find
a lot.
Find the one you need and then create a project in CMOD
and add the enhancement.

Bapi_goodsmvt_create for subcontracting challan

Dear Gurus,
we are using "bapi_goodsmvt_create" BAPI for creating MIGO transcation, here good receipt agianst Purchase order so GM = 01, here we required to capture sub contracting callan & year.
but in "bapi_goodsmvt_create" it's not possible.
so kindly help in the same.
Regards

Hi,
For capturing or reconciliation of subcontracting challan, you develop a z program & capture sub Con challan against GR, hence you need not have to enter sub con challan at the time of GR
Regards,
Vikas

BAPI_GOODSMVT_CREATE is not working for movement type 701 in MIGO

Hi gurus
Can anybody help to track that bapi: BAPI_GOODSMVT_CREATE is not working for movement type 701 for MIGO Transaction.

call this standard BAPI, AND EXECUTE IN SE37
""Local Interface:
*" IMPORTING
*"     VALUE(GOODSMVT_HEADER) LIKE BAPI2017_GM_HEAD_01 STRUCTURE
*"        BAPI2017_GM_HEAD_01
*"     VALUE(GOODSMVT_CODE) LIKE BAPI2017_GM_CODE STRUCTURE
*"        BAPI2017_GM_CODE
*"     VALUE(TESTRUN) LIKE BAPI2017_GM_GEN-TESTRUN DEFAULT SPACE
*"     VALUE(GOODSMVT_REF_EWM) LIKE /SPE/BAPI2017_GM_REF_EWM STRUCTURE
*"        /SPE/BAPI2017_GM_REF_EWM OPTIONAL
*" EXPORTING
*"     VALUE(GOODSMVT_HEADRET) LIKE BAPI2017_GM_HEAD_RET STRUCTURE
*"        BAPI2017_GM_HEAD_RET
*"     VALUE(MATERIALDOCUMENT) TYPE BAPI2017_GM_HEAD_RET-MAT_DOC
*"     VALUE(MATDOCUMENTYEAR) TYPE BAPI2017_GM_HEAD_RET-DOC_YEAR
*" TABLES
*"      GOODSMVT_ITEM STRUCTURE BAPI2017_GM_ITEM_CREATE
*"      GOODSMVT_SERIALNUMBER STRUCTURE BAPI2017_GM_SERIALNUMBER
*"       OPTIONAL
*"      RETURN STRUCTURE BAPIRET2
*"      GOODSMVT_SERV_PART_DATA STRUCTURE
*"        /SPE/BAPI2017_SERVICEPART_DATA OPTIONAL
*"      EXTENSIONIN STRUCTURE BAPIPAREX OPTIONAL
*"      GOODSMVT_ITEM_CWM STRUCTURE /CWM/BAPI2017_GM_ITEM_CREATE
*"       OPTIONAL
call function 'BAPI_GOODSMVT_CREATE'
    exporting
      goodsmvt_header         = goodsmvt_header
      goodsmvt_code           = goodsmvt_code
      testrun                 = testrun
      goodsmvt_ref_ewm        = goodsmvt_ref_ewm
    importing
      goodsmvt_headret        = goodsmvt_headret
      materialdocument        = materialdocument
      matdocumentyear         = matdocumentyear
    tables
      goodsmvt_item           = goodsmvt_item
      goodsmvt_serialnumber   = goodsmvt_serialnumber
      return                  = return
      goodsmvt_serv_part_data = goodsmvt_serv_part_data
      extensionin             = extensionin.
commit work.
hi, rewards point, if this is useful,
regrds
karthikeyan

Hi gurus bapi_goodsmvt_create

Similar Messages

Maybe you are looking for