Difference between Tcode MB1A, MB1B, MBIC Can any body let me know what is the difference between

all the three... 1. Mb1a - Enter Goods issue.. 2. Mb1b - Transfer Posting.. 3. Mb1c - Enter other goods receipts... If I am not wrong these all 3 are used for Non-consumables items... In what conditions I should be used..... === MB1A transaction code is used for goods issue. This is used for posting materials from stock to consumption say to a costcenter (mvt 201) or to a subcontractor(543). Transaction MB1B is used to perform transfer postings and stock transfers. Stock transfers refer to physical movement where as in transfer posting physical movements of goods is not involved. eg: transfer posting from material to material (309). transfer posting from stock to stock (321,343,349). stock transfer from plant to plant (301). stock transfer from sloc to sloc (311). In the above postings if the valuation change is involved then an accounting document is generated. Transaction mb1c is used for other goods receipts. That is say for a goods receipt w/o reference to PO. Srinivasulu Tallapalli === First I would like to say that all three transactions used in goods movement. MB1A - Goods issue leads to a reduction in Stock. MB1B - Transfer posting is used when there is a change in Stock ID or stock category of a material. There is no need for the actual (physical) movement of goods. MB1C - Other is used in instances where there is no reference document. Alternatively the transaction MIGO, can be used for all three transaction but when an entry is to be made for the respective movements, specify the transaction and reference in the respective fields on the initial MIGO screen. Patrick Kgosana === I have used Migo seperately which is for all the transactions but ...if the stock is not consumables I hope we use MB1B that I am sure.. I have used it.. My question is when to use MB1A and MB1C which is again tranfer of Stock.. Mb1b also reduces the stock when you consignment/ Subcontracting to your subcontractor so I need more clarification Rajeev === I was wrong in my earlier mail about the transaction codes. Use MB1B for transfer posting. Here your material is not consumed, but only stock transformation. Use MB1A for goods issue, which updates your material consumption. Your material is no more in the stock and it will be consumed for external requirement. Priya. === I think that: 1. MB1A: GOODS Withdrawal = 1. Sales Order creation - no impact. 2. Goods Receipt - reduce the planned independent requirement during MRP run For e.g. if PIR is 100, quantity remained as 100 in PIR, however during MRP run, 100 will not be included in the MRP planned as stock is available. 3. Delivery - minus the quantity for the oldest planned independent in demand management. For e.g. if PIR is 100 and delivery 90, PIR becomes 10 (withdrawal 90). - MB1B: Transfer posting = If you are involved with inventory, then you need the GR/IR account (Inventory Account) when the IR is posted. If you are not involved about inventory, then the system does not need the GR/IR account when the IR is posted, the system needs a G/L instead of the GR/IR account. - MB1C: Other Goods receipts = You can add a new material to the material master and set a beginning balance on it by using transaction MB1C. Sub Contracting: (1) You have a material that can be procured externally, and you have maintained BOM with components. Any waste generated and received during subcontracting process can be maintained as component with negative quantity.

(2) You create a subcontracting PO (PO with Item Category L). You can also maintain Purchase Info Record for Subcontract category for material and subcontractor. (3) You make a transfer posting to issue components for SC PO. Material is sent to subcontractor. As material remains under your ownership, system does not make any value entry. But quantity is shown as "Material Provided to Vendor" (4) You receive finished material against SC-PO. You also specify components consumed in manufacturing of finished goods. Additionally, if you have negative components in BOM, now you'll also receive subcontracting by-products. There are three events, so three accounting entries are generated: DR FG Stock/ SC By-Product Stock; CR Change in Stock (FG/ SC By-Product ) (for finished goods received) DR Subcontracting Charges; CR GR/IR Clg (for moneys payable to Subcontractor) DR Consumption (Components); CR Change in Stock (FG/ SC By-Product ) (material provided to Vendor is now charged to expense) (5) You do the IV for SC Invoice, and the process is complete. I think that you have got some concepts clarification. Yves SAP MM Reference Books: SAP Material Management Interview Questions, Certification and Configuration Books Goto: SAP MM Purchasing Back to: SAP MM (Materials Management) Configuration Hints and Tips Return to :SAP ABAP/4 Programming, Basis Administration, Configuration Hints and Tips

Thursday, October 18, 2007 Sample ABAP Program for MB1B Call Transaction REPORT YMBIE096 LINE-SIZE 80. *----------------------------------------------------------------------* * Program: YMBIE096 * Author: Sheila Titchener * Date: Mar 1999 * Purpose: To move stock to new plant *----------------------------------------------------------------------* TABLES: MCHB. * internal table DATA: BEGIN OF I_MCHB OCCURS 0, MATNR LIKE MCHB-MATNR, LGORT LIKE MCHB-LGORT, CHARG LIKE MCHB-CHARG, J_2CTRNR LIKE MCHB-J_2CTRNR, J_2CELNG LIKE MCHB-J_2CELNG, CLABS LIKE MCHB-CLABS, END OF I_MCHB. *-----------------------new code smt nov 98----------------------------* batch input tables DATA BEGIN OF BDCDATA OCCURS 100. INCLUDE STRUCTURE BDCDATA. DATA END OF BDCDATA. DATA BEGIN OF MESSTAB OCCURS 10.

INCLUDE STRUCTURE BDCMSGCOLL. DATA END OF MESSTAB. * SELECT-OPTIONS S_MATNR FOR MCHB-MATNR. PARAMETERS: P_DISP AS CHECKBOX. DATA W_MODE. DATA W_MESSAGE LIKE MESSAGE. *----------------------------------------------------------------------* START-OF-SELECTION. *----------------------------------------------------------------------* SELECT MATNR LGORT J_2CELNG CHARG CLABS J_2CTRNR FROM MCHB INTO CORRESPONDING FIELDS OF TABLE I_MCHB WHERE MATNR IN S_MATNR AND WERKS = 'BT'. *----------------------------------------------------------------------* END-OF-SELECTION. *----------------------------------------------------------------------* LOOP AT I_MCHB. CHECK I_MCHB-J_2CELNG NE 0. CHECK I_MCHB-J_2CELNG = I_MCHB-CLABS. PERFORM MOVE_STOCK. ENDLOOP. *&---------------------------------------------------------------------* *& Form MOVE_STOCK *&---------------------------------------------------------------------* * Call transaction MB1B to transfer stock *----------------------------------------------------------------------* FORM MOVE_STOCK. DATA: W_QTY(10). WRITE I_MCHB-J_2CELNG TO W_QTY DECIMALS 0. REFRESH: BDCDATA, MESSTAB. PERFORM DYNPRO USING: 'X' 'SAPMM07M' '0400', ' ' 'RM07M-BWARTWA' '301', ' ' 'RM07M-WERKS' 'BT', ' ' 'RM07M-LGORT' I_MCHB-LGORT, ' ' 'BDC_OKCODE' '/0', 'X' 'SAPMM07M' '0421', ' ' 'MSEGK-UMWRK' '94', ' ' 'MSEGK-UMLGO' I_MCHB-LGORT, ' ' 'BDC_OKCODE' 'NLE', *CODING BLOCK 'X' 'SAPLKACB' '0002', ' ' 'BDC_OKCODE' '/0', 'X' 'SAPMM07M' '0421', ' ' 'MSEG-MATNR(1)' I_MCHB-MATNR, ' ' 'MSEG-ERFMG(1)' W_QTY, ' ' 'MSEG-CHARG(1)' I_MCHB-CHARG,

' ' 'BDC_OKCODE' '/0', *CODING BLOCK 'X' 'SAPLKACB' '0002', ' ' 'BDC_OKCODE' '/0', *CODING BLOCK 'X' 'SAPLKACB' '0002', ' ' 'BDC_OKCODE' '/0', * 'X' 'SAPMM07M' '0410', * ' ' 'BDC_OKCODE' '/0', *CODING BLOCK * 'X' 'SAPLKACB' '0002', * ' ' 'BDC_OKCODE' '/8', *CODING BLOCK * 'X' 'SAPLKACB' '0002', * ' ' 'BDC_OKCODE' '/8', 'X' 'SAPLJ2CW' '0190', ' ' 'J_5C7-UMCHA' I_MCHB-CHARG, ' ' 'BDC_OKCODE' '/7', 'X' 'SAPMM07M' '0421', ' ' 'BDC_OKCODE' '/11', *CODING BLOCK 'X' 'SAPLKACB' '0002', ' ' 'BDC_OKCODE' '/0'. IF P_DISP = 'X'. W_MODE = 'A'. ELSE. W_MODE = 'N'. ENDIF. CALL TRANSACTION 'MB1B' USING BDCDATA MODE W_MODE UPDATE 'S' MESSAGES INTO MESSTAB. WRITE: / I_MCHB-MATNR, I_MCHB-CHARG, I_MCHB-LGORT, I_MCHB-J_2CTRNR, I_MCHB-J_2CELNG. IF SY-SUBRC NE 0. * what to do if there's an error???? LOOP AT MESSTAB. SY-MSGNO = MESSTAB-MSGNR. CALL FUNCTION 'WRITE_MESSAGE' EXPORTING MSGID = MESSTAB-MSGID MSGNO = SY-MSGNO MSGTY = MESSTAB-MSGTYP MSGV1 = MESSTAB-MSGV1 MSGV2 = MESSTAB-MSGV2 MSGV3 = MESSTAB-MSGV3 MSGV4 = MESSTAB-MSGV4 MSGV5 = MESSTAB-MSGV4 IMPORTING * error = MESSG = W_MESSAGE * msgln = EXCEPTIONS OTHERS = 1.

WRITE: / W_MESSAGE. * message id messtab-msgid type 'I' number messtab-msgnr. ENDLOOP. ENDIF. ENDFORM. " CHANGE_BILLING_TYPE *----------------------------------------------------------------------* FORM DYNPRO - new form smt nov 1998 *----------------------------------------------------------------------* > DYNBEGIN * > NAME * > VALUE *----------------------------------------------------------------------* FORM DYNPRO USING DYNBEGIN NAME VALUE. IF DYNBEGIN = 'X'. CLEAR BDCDATA. MOVE: NAME TO BDCDATA-PROGRAM, VALUE TO BDCDATA-DYNPRO, 'X' TO BDCDATA-DYNBEGIN. APPEND BDCDATA. ELSE. CLEAR BDCDATA. MOVE: NAME TO BDCDATA-FNAM, VALUE TO BDCDATA-FVAL. APPEND BDCDATA. ENDIF. ENDFORM. * Posted by Amit Khari at 10:06 PM 0 comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Sample ABAP Code Sample Sample Sample Sample Sample Sample Sample Sample Sample Sample Sample Sample ABAP ABAP ABAP ABAP ABAP ABAP ABAP ABAP ABAP ABAP ABAP ABAP Program Program Program Program Program Program Program Program Program Program Program Program to Upload table using new function GUI_UPLOAD for Submitting report with selection table for Sending SAP Mail for Search Layout sets for given String for Sapscript PerForm Module for Create IDOC for Output file to application server then send mail with Download details for Module Pool Skeleton for Module Pool containing screen loop processing for MB1B Call Transaction of Function Module to Convert Work Center into Personnel Number of FTP Function Module

Sample ABAP Program to EXPORT LIST TO MEMORY Sample ABAP Program to Execute Unix command from within SAP Sample ABAP Program to Get Output in EXCEL Sample ABAP Program to Implement EDI Sample Program to dynamically change upload/download program for any Table Sample ABAP Program to download table using new function GUI_DOWNLOAD Sample ABAP Program to Download file to Presentation Server Sample ABAP Program to display pop message to avoid abort Sample ABAP Program of ALV Grid Sample ABAP Program of Dialogue Module Pool Sample ABAP Program to DIALOGUE FLOW LOGIC Sample ABAP Program to Delete a file from the application server Sample ABAP Program to Compare to Unix or PC files and print differences Sample ABAP Program to Colour cells in ALV Sample ABAP Program to Calculate difference between date/times in hours Sample ABAP Program of BW User Exit Sample ABAP Program of ALV Grid control using OO methods Browse a file on the application server