MB1C - Other Goods receipt

Hi
Here is the following message :
Storage bin 749 998 AUFNAHME does not exist (check your entry)
Message no. L9009

Hi,
This probably relates to your movement type setting in SPRO-Warehouse mgmt--Activities-Transfers-Define movement types
check for the Storage bin mnatined for ur WH No. & mvt type combination
Reg
Dheeraj

Similar Messages

Document type assigned for other goods receipts(MB1C)is WA why?

Hi,
Document type assigned for other goods receipts(MB1C)is WA why?
Thanks

Document type for Goods Receipt is WE but I found in standard(Default) system it is assigned WA?
Can anyone help me on this?
Thanks

Bapi for transaction 'MB1C' -'Enter other goods receipt...'

Hi,
Please suggest the BAPI for the transaction 'MB1C'.
thanks

BAPI TO Upload Inventory Data
GMCODE Table T158G - 01 - MB01 - Goods Receipts for Purchase Order
                     02 - MB31 - Goods Receipts for Prod Order
                     03 - MB1A - Goods Issue
                     04 - MB1B - Transfer Posting
                     05 - MB1C - Enter Other Goods Receipt
                     06 - MB11
Domain: KZBEW - Movement Indicator
     Goods movement w/o reference
B - Goods movement for purchase order
F - Goods movement for production order
L - Goods movement for delivery note
K - Goods movement for kanban requirement (WM - internal only)
O - Subsequent adjustment of "material-provided" consumption
W - Subsequent adjustment of proportion/product unit material
           call function 'BAPI_GOODSMVT_CREATE'
           exporting
               goodsmvt_header             =
               goodsmvt_code               =
             *   TESTRUN                     = ' '
          IMPORTING
              goodsmvt_headret            =
         *   MATERIALDOCUMENT            =
MATDOCUMENTYEAR             =
           tables
             goodsmvt_item               =
GOODSMVT_SERIALNUMBER       =
            return                      = errmsg.
          clear errflag.
          loop at errmsg.
                      if errmsg-type eq 'E'.
              write:/'Error in function', errmsg-message.
              errflag = 'X'.
            else.
              write:/ errmsg-message.
            endif.
            move errmsg-message to i_msg1.
            append i_msg1.
            move errmsg-message to i_msg2.
            append i_msg2.
          endloop.
          if errflag is initial.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            WAIT          =
          IMPORTING
            RETURN        =
     endif.

Enter Other Goods Receipt - MB1C Error

Dear Friends:
When working on Enter Other Goods Receipt -I entered Material,Qty,UnE and pressed enter, I got the error
'Account determination for entry SANO GBB ____ ZOB 3000 not possible' and
'No stock posting possible for this material'.
How to overcome the problem? Please advise.
Regards
MSReddy

Sridhar,
Just check in OBYC tranc. whether for tranc key GBB, you have maintained the combination of valuation grouping code you are using, general modifier ( ZOB) and valuation class ( 3000) and the G/L accounts.
If not, please maintain the same.
Enjoy,
Vidyadhar.

BDC program for Other Goods receipts

Hi all,
I need BDC program for Other goods receipts,
I have data in excel like material, batch id, qty, actual width, length, plant etc. i want to upload this in one short based on the movement type.
Thanks in advance.
Shankar

Hi MP Shankar,
This is a sample BDC program .Use the format to develop your own BDC program.First record your trasnaction and use that recorded program here.Pass your filename here.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS: p_ifile TYPE dxfile-filename.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME TITLE text-002.
PARAMETERS: p_sess RADIOBUTTON GROUP g3 "create session
 DEFAULT 'X' USER-COMMAND bdc,
 p_ctu RADIOBUTTON GROUP g3. "call transaction
SELECTION-SCREEN END OF BLOCK b3.
DATA : BEGIN OF itab OCCURS 0,
 str TYPE string,
 END OF itab,
 l_file TYPE string,
 t_bdcdata TYPE STANDARD TABLE OF bdcdata,
 wa_bdcdata LIKE LINE OF t_bdcdata.
AT SELECTION SCREEN ON VALUE REQUEST
Value request for the filename.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_ifile.
PERFORM help_input_file.
START-OF-SELECTION.
CLEAR l_file.
l_file = p_ifile.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 filename = l_file
 filetype = 'ASC'
 TABLES
 data_tab = itab
 EXCEPTIONS
 file_open_error = 1
 file_read_error = 2
 no_batch = 3
 gui_refuse_filetransfer = 4
 invalid_type = 5
 no_authority = 6
 unknown_error = 7
 bad_data_format = 8
 header_not_allowed = 9
 separator_not_allowed = 10
 header_too_long = 11
 unknown_dp_error = 12
 access_denied = 13
 dp_out_of_memory = 14
 disk_full = 15
 dp_timeout = 16
 OTHERS = 17.
*Start new session
IF p_sess = 'X'.
 PERFORM bdc_open.
ENDIF.
LOOP AT itab.
 PERFORM creat_batch_input.
 PERFORM bdc_insert.
 IF p_ctu = 'X'.
 CALL TRANSACTION 'SE38' USING t_bdcdata MODE 'A'.
 ENDIF.
ENDLOOP.
IF p_sess = 'X'.
 PERFORM bdc_close .
ENDIF.
*& Form bdc_open
 text
--> p1 text
<-- p2 text
FORM bdc_open .
CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 client = sy-mandt
 group = 'ZMUK'
 user = sy-uname
 EXCEPTIONS
 client_invalid = 1
 destination_invalid = 2
 group_invalid = 3
 group_is_locked = 4
 holddate_invalid = 5
 internal_error = 6
 queue_error = 7
 running = 8
 system_lock_error = 9
 user_invalid = 10
 OTHERS = 11.
ENDFORM. " bdc_open
*& Form creat_batch_input
 text
--> p1 text
<-- p2 text
FORM creat_batch_input .
use your own recorded program here.
PERFORM bdc_dynpro USING 'SAPLWBABAP' '0100'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=STRT'.
PERFORM bdc_field USING 'RS38M-PROGRAMM'
 itab-str.
PERFORM bdc_field USING 'RS38M-FUNC_EDIT'
 'X'.
PERFORM bdc_dynpro USING 'SAPLSLVC_FULLSCREEN' '0500'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=&F03'.
PERFORM bdc_dynpro USING 'SAPLWBABAP' '0100'.
PERFORM bdc_field USING 'BDC_OKCODE'
 '=BACK'.
PERFORM bdc_field USING 'RS38M-PROGRAMM'
 itab-str.
PERFORM bdc_field USING 'RS38M-FUNC_EDIT'
 'X'.
ENDFORM. " creat_batch_input
*& Form bdc_insert
 text
--> p1 text
<-- p2 text
FORM bdc_insert .
CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 tcode = 'SE38'
 TABLES
 dynprotab = t_bdcdata
 EXCEPTIONS
 internal_error = 1
 not_open = 2
 queue_error = 3
 tcode_invalid = 4
 printing_invalid = 5
 posting_invalid = 6
 OTHERS = 7.
ENDFORM. " bdc_insert
*& Form bdc_dynpro
 text
 -->P_0168 text
 -->P_0169 text
FORM bdc_dynpro USING p_program TYPE any
 p_dynpro TYPE any.
CLEAR wa_bdcdata.
wa_bdcdata-program = p_program.
wa_bdcdata-dynpro = p_dynpro.
wa_bdcdata-dynbegin = 'X'.
APPEND wa_bdcdata TO t_bdcdata.
ENDFORM. " bdc_dynpro
*& Form bdc_field
 text
 -->P_0179 text
 -->P_0180 text
FORM bdc_field USING p_fnam TYPE any
 p_fval TYPE any.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = p_fnam.
wa_bdcdata-fval = p_fval.
CONDENSE wa_bdcdata-fval.
APPEND wa_bdcdata TO t_bdcdata.
ENDFORM. " bdc_field
*& Form bdc_close
 text
--> p1 text
<-- p2 text
FORM bdc_close .
CALL FUNCTION 'BDC_CLOSE_GROUP'
 EXCEPTIONS
 not_open = 1
 queue_error = 2
 OTHERS = 3.
ENDFORM. " bdc_close
*& Form help_input_file
 text
--> p1 text
<-- p2 text
FORM help_input_file .
DATA: lt_file_table TYPE filetable,
 la_file_table LIKE LINE OF lt_file_table,
 l_rc TYPE i,
 l_pcdsn TYPE cffile-filename.
REFRESH lt_file_table.
CLEAR la_file_table.
CALL METHOD cl_gui_frontend_services=>file_open_dialog
 CHANGING
 file_table = lt_file_table
 rc = l_rc.
READ TABLE lt_file_table INTO la_file_table INDEX 1.
l_pcdsn = la_file_table-filename.
MOVE l_pcdsn TO p_ifile.
ENDFORM. " help_input_file

IDOC for Goods Receipt

Dear All
Pls let me know if there is any IDOC for T.Code: MB1C ( Other Goods Receipts).
Right now we r using the message type:WPUWBW but when i try to post it goes to the T.code:WPED ( SALES AUDIT EDITOR )
Regards,
Shanmugasundaram.

hi,
sure there is
the new one is called MBGMCR02
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Updating of serial nos in MIGO - Goods receipts

Can any one suggest if there is a way to upload the serial nos while doing MIGO as it is very difficult entering it manually for large no of quantities of a serialized material.
I hope you got my query, pls let me know if I need to elaborate more.
Thanks!!

Hi,
I don't know a good standard procedure to make entering SN easier. (apart from automatic SNs entry, but I assume, that you have SNs and you have to enter them to the system)
Usually in such situations I prepare a custom (Z..) TCODE in which the proces of registering the Material Document is:
1. Enter Header and item data -> accept save (not POST) and go to custom screen
2. Enter serials for each serialized item -> using BAPI assign it to material document and save
3. Show the last screen -> when the user can finally post document.
Additionally usually I add some control logic to chceck wheter eneterd SN are OK.
In SAP standard in TCODE MB01 (MB1C for other goods receipt) you can copy+paste SNs for item (SN entrace screen). But the limit is 19 SNs in one step. Next you have scroll the screen.
Hope it helps.
Regards,
w.
Edited by: Wojciech Zalech on May 14, 2010 8:22 AM

Free goods receipt without PO

1. Is it possible to make of Free Goods Receipt of material without PO generate? If yes how?
2. Also such free goods reciept if i made with Standard Price maintain in Material master so which account posting is made after GRN?

Hi,
Entering a Delivery Free of Charge Without Reference to a Purchase Order
You receive a delivery from a vendor free of charge for which no purchase order was placed, you post the receipt of the goods as a miscellaneous (other) goods receipt.
Choose Goods movement ® Goods receipt ® Other. Enter the data as required and choose movement type 511. When you process the items, the system prompts you, for every item, to maintain a text for the delivery free of charge on the detail screen. This entry is mandatory, since without a purchase order there is no other way of entering information about the delivery
If you maintain standard price
Standard Price
When a delivery free of charge is posted, the stock of the material increases by the quantity of goods received.
For a material valuated at a standard price, the total value of the material must increase in relation. Therefore, the stock account is credited with the value of the delivered quantity x standard price. The offsetting entry is made to the "Income from price differences" account
Reward if useful
Regards

BAPI o FM for posting goods receipt of an inbound delivery

Hi
I have a program that post a goods receipt for an inbound delivery using batch input of transaction VL32 (in the first screen of this trx pushing button "Post Goods Recepit"). We need to change it for a BAPI o FM that makes the same process. I've seen other threads of the same issue that makes reference to BAPI_GOODSMVT_CREATE. I've checked it using value 05 of GM_Code
(other goods receipt) but it doesn't work (I think the movement type I using is not compatible with the code 05). Can anybody tell me if this BAPI can do what i need? In that case, anybody have an example code? I've seen other FM: MB_CREATE_GOODS_MOVEMENT. Is that a better choice? Example code will be much appreciated
Thanks and regards
Dani

Check whether there is any BTE from FIBF and use it accordingly.
Also check from SWEL whether any event is getting published when the GR is being done.
If none of the above works try to find some user Exit where you can code the needful.
Thanks
Arghadip

Goods Receipt 511 with message QM Only QA495

Hi experts:
I'm trying to do an 511 movement for a material, but appears the following message "Change the inspection stock of material 000000000000425217 in QM only".
My material has inspection typ :
01 - Goods receipt inspection purchase order
05 - Inspection for other goods receipt
08 - Stock transfer
Checking the inspection type for goods movements (Quality Management ==> Quality Inspection ==> Inspection Lot Creation ==> Inspection for Goods Movement) I can check that 511 movement has inspection lot origin 05..
Somebody can help me?

Check whether 05 inspection lot is already created.Check the stock type when you are doing movement.It should be "Quality " & not "Unrestricted"'
Also make sure that in OMJJ what are allowed T codes.

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.

Return Component flag in Good Receipt

Hello, I'm creating a report which need to know which one is a Good Receipt and a Return Component from Production Order.
I've tried to look at the table, but can't find which is the flag for Return Component and the other (Good Receipt).
Does anyone can help?
Thanks
-Flo

Hi,
Try this:
SELECT T0.DocNum as [Receipt No.] ,T1.BaseRef as [Prod Order No.] ,T1.ItemCode ,T1.Quantity
FROM OIGN T0
INNER JOIN IGN1 T1 on T0.DocEntry=T1.DocEntry
WHERE TranType is null and BaseType=202
Thanks,
Neetu

Diffrent Between Goods Receipt Transaction Code MB01 and MIGO?

Dear All
Could anyone please tell me different between goods receipt by MB01 and MIGO.
Should I choose MIGO or MB01.
Thank and Best Regards,
Thang

Hi,
It is better to use MIGO.
MIGO replaces all the conventional transactions for posting goods movements, whose transaction codes start with MB*.
You can use the transaction (MIGO) to post the following goods movements:
- Goods receipts from external procurement
- Goods receipts for orders
- 'Other' goods receipts
- Return deliveries and subsequent deliveries
- Goods issues
- Transfer postings and stock transfers
- Subsequent adjustment for subcontracting
The advantages this transaction brings
This transaction provides many advantages over the old transaction for posting goods movements, for example:
- You can maintain and display all the data on one screen. You can find all the information you need for an item without having to switch from screen to screen. You can just hide any detailed information you do not require.
- When you enter goods movements, the system does not issue any messages; before you post the goods movements, you can display all the messages at once.
- Instead of having to enter the same data every time you enter a new goods movement (for example, plant, storage location, or movement type), you enter the data you use most often only once via Settings -> Default values. The system then proposes this data every time you enter a goods movement.
- If you do not know the exact name of the material, plant, or storage location, you just enter part of the number or a description. The system then searches for and proposes the complete term for you.
How the screen is structured
The screen is split into three areas:
- Overview tree
You can show and hide this area via the Overview on/off pushbutton. The overview screen displays the last ten documents for orders, reservations, material documents or held data. You thereby always have an overview of the last activities you carried out.
- Header data
You can show and hide this area via the Open/close header data pushbutton.
- Detail data
You can show this area by clicking on the item for which you want to display detail data in the Line column of the item overview. You can hide the detail data again by choosing Close detail data.
Each time you call up the transaction, the screen is displayed as it was configured the last time you used it.

Goods receipt - others

Hi all!
We do a mere job work for our customers. We receive the materials from customers, do some work on it and return back the same. For this i have created 2 material codes for finished and raw as non-valuated material(UNBW). Process is like i have created an enquiry(1300003) , created quotation(1400026)based on enquiry, created sales order(1500079) with reference to quotation and tried to receive the raw material in 501 E or 561 E with reference to sales order.
But when i tried to do goods receipt in MB1C (561 E) with reference to a particular sales order number(1500079) system throws me an error as below.
Account assignment cannot be carried out because of different origin no.
Message no. V1134
Diagnosis
The sales document to which you want to refer is based on sales document 1300003 and item 000010. Therefore, the settlement and possibly inventory management are carried out using the number of the preceding document.
System Response
This entry is not allowed.
Procedure
Enter the document and the item number of the preceding sales document.
System is not accepting the sales order number as reference but its accepting the enquiry number when i do 561 E
How can we solve this issue..
Thanks in advance,
Raj.

solution can be found in OSS note 50619 - Individual purchase order and quotation

Posting goods receipt using transaction MB1C

Hi
When I posting goods receipt using transaction MB1C , I am getting following error
Account 310000 for Transo/event key BSX is a A control Account.
Please tell me the solution for this error.
kalai.

Dear Suriya,
If your issue is still un-resolved, Just try with:
T. Code: FS00
Key-in your G/L Account - 310000 & Company Code, in respective fields; go to
Tab: Create/bank/interest
Here, you will find a Box: Post automatically only. Enable the box (check-mark the box) for GR/IR clearing account.
Jope, this may help in some ways.
Best Regards,
Amit.
Note: In continuation to others' suggestion, I'll also suggest to consult FI-Personnel, at your end.

MB1C - Other Goods receipt

Similar Messages

Maybe you are looking for