Date Of Mfg. in transfer posting

Hi Friends,
Pl. help in following scenario.
I have activated btch management for finish products.
When I am confirming my process order, date of manufacturing is entered for FG batch produced.
When I am transferring this material to other Finsh material in transfer posting 309 movement type, previos batch date of Mfg is automatically copied to new batch.
This I want to deactivate, i.e. user should enter this date of mfg manually for this new batch.
Please guide. Thanks in advance.
Regards,
Amit shirsath.

Waiting for your suggestions.
Regards,
Amit.

Similar Messages

  • Transfer Posting for Line Items between Reconciliation Account

    HI,
    My customer want to transfer costing the line items between a old Reconciliation Account and a New Reconciliaton Account.
    For example, i have a Account Group Vendor with a old Reconciliation Account " Vendor CEE".
    This reconciliation account has the line items concern differents Vendors.
    Edit a new Account Group calling ( CEE) to replace a Old Account Group.
    After changing in Vendor Master data the Reconciliation account, we need to transfer posting the line items in the new account reconciliation
    In Sap system is there a report can do it? Can you help me?
    Regards

    Hi,
    Thank you for the answer.
    I did that, and exactly:
    - In Trx Obbw insert the reconciliation account and Adjustement account.
    - and execute the trx FAGLF101 in test but the sap system give me the following error:
      " Account determination for transaction A00 is missing for account 0205016001 ZM P001 "
       Message no. FR005
    Can you help me?
    Regards
    Edited by: Marika De Cesare on Oct 18, 2011 1:06 PM

  • Transfer posting from one GL account to another

    Hi,
    For a GL account which is not open item managed, now have to check the "open item management".
    since it has the amount, so i can not do it.
    But i read the following help message.
    If you want to switch this function on retroactively for a certain account, you should create a new account with the correct setting and use this to make a transfer posting of existing items.
    so, after creating a new GL account with correct settings. How to Transfer the posting of the Existing items?
    Thanks in advance,
    Swetha

    Hi all,
    i posted a document in F-02 by debiting the new GL account and crediting the old account.
    now, the balance of the old account is Zero.
    but still can not save it by checking the " open item management" because it says as below.
    "Account balance = 0 but open items exist in the account
    The data contains error, you cannot save"
    so, by making zero also we can not change the that Chcek box.
    and another option you all suggested is transfer of the posting to new Gl account.
    since the old account is not open item managed, so i can not follow this option also.
    and one more, have to come across this kind of issue?
    then how did you solve it.
    Please share your finding.
    Regards,
    Swetha

  • Asset Transfer posting ABT1N

    hI,
    while working with transaction ABT1N Asset transfer posting from existing (comp code) asset to new (comp code) asset with
    Document, posting, asset value date -> this will be the same date 1.1.2011,
    system gives error message" You cannot post to asset in company code 'abcd' fiscal year 2011.
    After that
    I changed the Document, posting, asset value date -> this will be the same date 20.11.2011, system gives error message "
    Account 20900000 does not exist in company code 'abcd'.
    Please resolve the issue both the scenarios.
    Thanks,
    Sahara.

    please search.  the "account does not exist" error has been dealt with previously.

  • Transfer posting Quality to Quality within plant ..mov type 323...

    Hi All,
               I am not able to process Transfer posting Quality to Quality within plant with mov type 323 through MIGO transaction.
    Error : Change the inspection stock of material 936317 in QM only.(Change the inspection stock of material 936317 in QM only
    Message no. QA495
    Diagnosis
    You want to make a stock posting to/from the inspection stock. This is not allowed for material 936317 because the quality inspection control has been activated by QM.
    The following cases can occur:
    The inspection stock should be increased, although an inspection is not foreseen for the current goods movement
    The inspection stock should be released, although  you can only do this using the QM transactions.
    System response
    You cannot carry out the stock posting.
    Procedure
    Check both the QM inspection setup data and the movement type for material 936317 in the quality management view of the material master.
    Exception:
    If you post a return delivery to a vendor with reference to a purchase order, or cancel a goods receipt, the stock indicator from the order is proposed.
    Check and modify this proposal as required.
    The stock may have been transferred already and is therefore no longer in inspection stock.
    Kindly help me to resolve the issue.

    Hi,
    Please check the stock of  material 936317  in MMBE , One lot will be in Quality Inspection.
    Clear the lot to unrestricted lot
    try now you will be able to do  Transfer posting Quality to Quality within plant ..mov type 323
    G.Ganesh Kumar

  • BAPI_GOODSMVT_CREATE error - Duplicate Transfer Posting

    Hello,
    I'm using BAPI_GOODSMVT_CREATE for transfer posting with GM Code 04 and Movement Type 311.
    But the posted material document is incorrect. Instead of 2 lines only, the line items becomes 4.
    Could anyone please help me?
    Thanks in advance!

    Hi Gold Yap,
          I have done the Transfer posting by using BAPI_GOODSMVT_CREATE.
         Below i added my sample code. Please go through.
    Report XYZ.
    TABLES : mslb , mchb .
    DATA : BEGIN OF i_stock OCCURS 0 ,
           matnr LIKE mslb-matnr ,
           werks LIKE mslb-werks ,
           charg LIKE mslb-charg ,
           sobkz LIKE mslb-sobkz,
           lifnr LIKE mslb-lifnr ,
           lblab LIKE mslb-lblab ,
           END OF i_stock .
    DATA : BEGIN OF i_batch OCCURS 0 ,
           matnr LIKE mchb-matnr ,
           werks LIKE mchb-werks ,
           lgort LIKE mchb-lgort ,
           charg LIKE mchb-charg ,
           clabs LIKE mchb-clabs ,
           END OF i_batch .
    DATA: BEGIN OF it_mess OCCURS 10,
          charg LIKE mslb-charg ,
          lgort LIKE mchb-lgort,
          lifnr LIKE mslb-lifnr,
          err LIKE bapiret2-message,
          flag,
          END OF it_mess.
    DATA match.
    DATA :  header LIKE bapi2017_gm_head_01 . "OCCURS 0 WITH HEADER LINE .
    DATA :  code LIKE bapi2017_gm_code .  " OCCURS 0 WITH HEADER LINE .
    DATA :  item LIKE bapi2017_gm_item_create OCCURS 0 WITH HEADER LINE.
    DATA : i_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE .
    DATA : matdoc LIKE bapi2017_gm_head_ret .
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME .
    SELECT-OPTIONS : s_matnr FOR mslb-matnr .
    PARAMETERS : p_werks LIKE mslb-werks DEFAULT 'TPFB' .
    SELECTION-SCREEN END OF BLOCK b1 .
    AT SELECTION-SCREEN OUTPUT .
      LOOP AT SCREEN .
        IF screen-name = 'P_WERKS' .
          screen-input = '0' .
          MODIFY SCREEN .
          CLEAR screen .
        ENDIF.
      ENDLOOP .
    START-OF-SELECTION .
      CLEAR: i_stock[],i_stock.
      CLEAR: it_mess[],it_mess.
      CLEAR: i_batch[],i_batch.
      SELECT matnr werks charg sobkz lifnr  lblab
      FROM mslb INTO TABLE i_stock
      WHERE matnr IN s_matnr
        AND werks = p_werks.
      DELETE i_stock WHERE sobkz <> 'O'.
      DELETE i_stock WHERE lblab <= '0.000'.
      IF i_stock[] IS INITIAL .
        MESSAGE 'NO Data Available In MSLB Table' TYPE 'S' .
      ELSE.
        DELETE i_stock WHERE charg = 'COMMON' .
        IF i_stock[] IS INITIAL .
          MESSAGE 'Already Transfer Posting to Common Batch' TYPE 'S' .
        ENDIF.
      ENDIF .
      SELECT matnr werks lgort charg clabs
      FROM mchb
      INTO TABLE i_batch
      WHERE matnr IN s_matnr
        AND werks = p_werks .
      DELETE i_batch WHERE clabs <= '0.000'.
      IF i_batch[] IS INITIAL .
        MESSAGE 'NO Data Available In MCHB Table' TYPE 'S' .
      ELSE .
        DELETE i_batch WHERE charg = 'COMMON' .
        IF i_batch[] IS INITIAL .
          MESSAGE 'Already Transfer Posting to Common Batch' TYPE 'S' .
        ENDIF.
      ENDIF .
      CLEAR : header,code,matdoc  .
      header-pstng_date  = sy-datum.
      header-doc_date    = sy-datum.
      header-pr_uname    = sy-uname.
      header-header_txt  = 'Transfer Posting'.
      code-gm_code       = '04'.
      SORT i_batch BY matnr werks charg.
      LOOP AT i_batch.
        CLEAR: item[],item.
        item-material        = i_batch-matnr.
        item-plant           =  i_batch-werks.
        item-batch           = i_batch-charg.
        item-entry_qnt       =  i_batch-clabs .
        item-stge_loc        = i_batch-lgort .
        item-move_type       = '309'.
        item-move_batch = 'COMMON'.
        APPEND item .
        CLEAR item .
        match = 'X'.
        PERFORM bapi_run USING match.
      ENDLOOP.
      LOOP AT i_stock .
        CLEAR: item[],item.
        item-material        = i_stock-matnr.
        item-plant           =  i_stock-werks.
        item-batch           = i_stock-charg.
        item-vendor          =  i_stock-lifnr .
        item-entry_qnt       =  i_stock-lblab .
        item-move_type       = '309'.
        item-spec_stock      =  'O'.
        item-move_batch = 'COMMON'.
        APPEND item .
        CLEAR item .
        match = 'Y'.
        PERFORM bapi_run USING match.
      ENDLOOP.
      IF i_stock[] IS NOT INITIAL OR i_batch[] IS NOT INITIAL .
        IF it_mess[] IS INITIAL.
          MESSAGE 'Transfer Posted Successfully' TYPE 'S' .
        ELSE.
          SORT it_mess BY charg err.
          WRITE:/2 'Batch',11'Location',20'Vendor'.
          LOOP AT it_mess.
            AT NEW charg.
              SKIP.
            ENDAT.
            IF it_mess-flag = 'X'.
              WRITE: /2 it_mess-charg COLOR 6, it_mess-lgort COLOR 3
                     INTENSIFIED OFF,it_mess-lifnr COLOR 2 INTENSIFIED OFF.
            ENDIF.
            WRITE: /10 it_mess-err.
          ENDLOOP.
        ENDIF.
      ENDIF .
    *&      Form  bapi_run
          text
    -->  p1        text
    <--  p2        text
    FORM bapi_run USING match .
      CLEAR: i_return[],i_return.
      CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
        EXPORTING
          goodsmvt_header = header
          goodsmvt_code   = code
        TABLES
          goodsmvt_item   = item
          return          = i_return.
      IF i_return[] IS INITIAL.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait = 'X'.
      ELSEIF i_return[] IS NOT INITIAL.
        CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
        LOOP AT i_return WHERE type = 'E'.
          it_mess-charg = i_stock-charg.
          IF match = 'X'.
            it_mess-lgort = i_batch-lgort.
          ELSEIF match = 'Y'.
            it_mess-lifnr = i_stock-lifnr.
          ENDIF.
          it_mess-err   = i_return-message.
          IF sy-tabix = 1.
            it_mess-flag = 'X'.
          ENDIF.
          APPEND it_mess.
          CLEAR  it_mess.
        ENDLOOP.
      ENDIF.
    ENDFORM.                    " bapi_run
    Regards,
    S.C.K

  • While doing transfer posting  in  Tcode MIGO,with moment type 413e

    I am doing transfer posting with moment type 413 ,E
    changing the stock from one sale order to another sale order .
    and  the material is not related to planning .mrp type ND
    I am getting  warning messege
    "sale order (sobkz= ) is not  for this goods moment "
    Can any body help me  to remove this msg
    thanks in advance
    Srinivas

    when a cost center is created with KS01 transaction, then the user has to enter a validity period.
    So this cost center is just not valid for the given date.
    Check in KS03 and ask  the CO consultant to do the necessary actions

  • Transfer posting with Mov Type 311E in MIGO with reference to SC-PO

    Hi,
    I am working with MTO scenario.
    I want to carry out transfer posting of material with movement type 311E against subcontracting Purchase Order which is sale order specific.
    However, system does not allow me to do the same. whenever transfer posting, PO & movement type is selected in transaction MIGO, item details entry tabs are displayed blank.
    Below steps are being follow:
    Scenario is MTO ( special stock subcontracting)
    1. Subcontracting PO no. 4500000147 against Sale Order no 61 created.
    2. RM code - 61, available stock 100 TO & batch no.0000000127
    3. Transfer material to vendor for processing through MIGO ( since it is a special sales order stock, transferring happens from SL 0001- Main Stores to SL VLSC -Virtual storage location) using movement type 311 E
    5. Item Data details tabs are blank.---This is the issue / error.
    Note: I am restricted to post transfer posting through MIGO-Transfer Posting (will not use MB1B) due to some enhancement of MIGO and interfaces with legacy system.
    Please have a look on attachment for SAP screen issue.
    Regards
    Mohit Jaiswal

    Hi Mohit ,
    please check below link , you need to perform steps as given
    http://help.sap.com/saphelp_470/helpdata/en/4d/2b90b043ad11d189410000e829fbbd/content.htm
    also see the sales order subcontracting using the business addon
    http://help.sap.com/erp2005_ehp_04/helpdata/en/c7/2587b8dad94c52854ccd28015dceb0/frameset.htm

  • Transfer posting issue

    while doing transfer posting from QI stock to unrestricted stock, following error message is occuring.
    plz suggest the solution.
    Change the inspection stock of material xxxx in QM only
    Message no. QA495
    Diagnosis
    You want to make a stock posting to/from the inspection stock. This is not allowed for material xxxxx because the quality inspection control has been activated by QM.
    The following cases can occur:
    The inspection stock should be increased, although an inspection is not foreseen for the current goods movement
    The inspection stock should be released, although  you can only do this using the QM transactions.
    System Response
    You cannot carry out the stock posting.
    Procedure
    Check both the QM inspection setup data and the movement type for material xxxx in the quality management view of the material master.
    Exception:
    If you post a return delivery to a vendor with reference to a purchase order, or cancel a goods receipt, the stock indicator from the order is proposed.
    Check and modify this proposal as required.
    The stock may have been transferred already and is therefore no longer in inspection stock.

    Hi,
    Please reffer the below link:
    Change the inspection stock of material xxxx in QM only
    Thanks and Regards
    Binoj M D

  • Error in Transfer posting for movement type 303

    Hi Sir,
    I am getting following error while doing Transfer posting for movement type 303 thru BAPI_GOODSMVT_CREATE
    Error in Function:
    Order    not found or not permitted for Goods Movement.
    I am passiing all mandatory parameter for it as per BAPI Documentaion in tcode BAPI
    Transfer posting
    Transfer posting without reference to a reservation
    The following fields must be populated:
    Material number
    Plant
    Storage location
    Movement type
    Movement indicator
    Quantity in unit of entry
    ISO code unit of measurement for unit of entry
    If I am doing manually by MB1B tcode, it is successfully done.......here its not asking any ORDER No...
    Please help me .........
    Regards,
    Krishan

    I'm not sure what you're system set up is...   So I'd suggest looking at everything you enter on the screen and then checking to make sure you are passing all the information in the BAPI.
    With that said our system does require posting date, and batch.  You might check that.   Also check that you've included all the required information in the header.
    Did you use the same data when you tried to process the BAPI that you used when you tried to do MB1B manually?

  • PO no is not updateing in MSEG table for transfer posting wrt PO

    Hi All ,
    PO number not updateing  in MSEG table field EBELN for transfer posting with reference to PO . What should be the reason . This is for subcontracting process .

    Hi Raghavendra Balegar
    If u r doing through scheduling agreement then it will not sit in MSEG. only if u doing through standard PO i.e. NB then only u can view the data of PO in MSEG.
    Regards
    Ram

  • Mb1b Transfer posting problem (urgent)

    hello
    i m using movement type 309.
    in the second screen they are entering batch..so based on that batch i m getting matnr and quantity in that batch.
    In my ZBAPI ..
    SELECT matnr clabs FROM mchb
                           INTO TABLE it_mb1b
                           WHERE werks = plant      
                           AND   lgort = send_stloc 
                           AND   charg = batch.    
    In the second line item..They are entering scrap material which the data has to get from MARD table. There is no batch exists for this second line item.
    i m writing query to get the data from mard like this:-
      SELECT matnr labst FROM mard
             INTO CORRESPONDING FIELDS OF TABLE it_mard
                           WHERE matnr LIKE '%-SCRAP'
                           AND   werks = plant     
                           AND   lgort = '2200'. 
    So, how to fill this second line item in BAPI.
    For the first line item i m using it_gmitem-entry_qnt in the BAPI item list.  This is for the first item in second screen.
    Similarly how to fill the second line item in BAPI_GOODSMVT_CREATE.

    FUNCTION zbapi_mb1b_new.
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(MOVE_TYPE) LIKE  BAPI2017_GM_ITEM_CREATE-MOVE_TYPE DEFAULT
    *"       '309'
    *"     VALUE(PLANT) LIKE  BAPI2017_GM_ITEM_CREATE-PLANT DEFAULT '2000'
    *"     VALUE(SEND_STLOC) LIKE  BAPI2017_GM_ITEM_CREATE-STGE_LOC
    *"     VALUE(RECV_STLOC) LIKE  BAPI2017_GM_ITEM_CREATE-MOVE_STLOC
    *"     VALUE(MOVE_PLANT) LIKE  BAPI2017_GM_ITEM_CREATE-MOVE_PLANT
    *"       DEFAULT '2000'
    *"     VALUE(BATCH) LIKE  BAPI2017_GM_ITEM_CREATE-BATCH
    *"     VALUE(QUAN_MEASURE) LIKE  BAPI2017_GM_ITEM_CREATE-QUANTITY
    *"  EXPORTING
    *"     VALUE(MAT_DOC) LIKE  BAPI2017_GM_HEAD_RET-MAT_DOC
    *"  TABLES
    *"      RETURN STRUCTURE  BAPIRET2
      DATA : ls_quan1 TYPE p DECIMALS 3,
             ls_quan2 TYPE p DECIMALS 3,
             ls_quan3 TYPE p DECIMALS 3,
             ls_quan4 TYPE p DECIMALS 3,
             ls_quan5 TYPE p DECIMALS 3,
             ls_quan6 TYPE p DECIMALS 3.
      DATA : it_mard LIKE mard OCCURS 0 WITH HEADER LINE.
      gmhead-pstng_date = sy-datum.  "Posting date defaulted to system date
      gmhead-doc_date   = sy-datum.  "Document date defaulted to system date
      gmcode-gm_code    = '04'.       "Transfer Posting (MB1B)
      SELECT matnr clabs FROM mchb
                           INTO TABLE it_mb1b
                           WHERE werks = plant       "Plant
                           AND   lgort = send_stloc  "Storage location
                           AND   charg = batch.      "Batch Number
      SELECT matnr labst FROM mard
                           INTO CORRESPONDING FIELDS OF TABLE it_mard
                           WHERE matnr LIKE '%-SCRAP'
                           AND   werks = plant      "Plant
                           AND   lgort = '2200'.    "2094 in production
      LOOP AT it_mb1b INTO wa_mb1b.
        ls_quan2 = ( 5 / 100 ) * wa_mb1b-clabs.
        ls_quan3 = wa_mb1b-clabs + ls_quan2.
        ls_quan4 = wa_mb1b-clabs - ls_quan2.
        IF ( quan_measure EQ wa_mb1b-clabs ).
          ls_quan6 = wa_mb1b-clabs.
       ELSEIF ( quan_measure > wa_mb1b-clabs AND quan_measure <= ls_quan3 ).
          ls_quan5 = quan_measure - wa_mb1b-clabs.  "difference
          READ TABLE it_mard WITH KEY matnr0(3) = wa_mb1b-matnr0(3).
          IF sy-subrc EQ 0.
            it_mard-labst = it_mard-labst - ls_quan5.
            MODIFY it_mard TRANSPORTING labst WHERE
                             matnr0(3) = wa_mb1b-matnr0(3).
          ELSE.
          ENDIF.
          MODIFY mard FROM TABLE it_mard.
          CLEAR it_mard.
          ls_quan6 = wa_mb1b-clabs + ls_quan5.
       ELSEIF ( quan_measure < wa_mb1b-clabs AND quan_measure <= ls_quan4 ).
          ls_quan5 = wa_mb1b-clabs - quan_measure.
          it_mard-labst = it_mard-labst + ls_quan5.
          MODIFY it_mard TRANSPORTING labst WHERE
                              matnr0(3) = wa_mb1b-matnr0(3).
          MODIFY mard FROM it_mard.
          ls_quan6 = wa_mb1b-clabs.
       ENDIF.
        it_gmitem-move_type    = move_type.      "Movement type
        it_gmitem-plant        = plant.          "Plant
        it_gmitem-stge_loc     = send_stloc.     "Storage Location
        it_gmitem-move_plant   = move_plant.     "Receiving Plant
        it_gmitem-move_stloc   = recv_stloc.     "Receiving storage location
        it_gmitem-batch        = batch.          "Batch Number
        it_gmitem-material     = wa_mb1b-matnr.  "Material Number
        it_gmitem-move_mat     = wa_mb1b-matnr.  "Receiving/issuing material
        it_gmitem-entry_qnt   = ls_quan6.        "Quantity in unit of entry
        APPEND it_gmitem.
      ENDLOOP.
      CLEAR return.
      CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
        EXPORTING
          goodsmvt_header             = gmhead
          goodsmvt_code               = gmcode
      TESTRUN                     = 'X'
       IMPORTING
      GOODSMVT_HEADRET            =
         materialdocument            = mat_doc
      MATDOCUMENTYEAR             =
        TABLES
          goodsmvt_item               = it_gmitem
      GOODSMVT_SERIALNUMBER       =
          return                      = return
      IF NOT mat_doc IS INITIAL.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
       EXPORTING
         wait          = 'X'
    IMPORTING
      RETURN        =
      ELSE.
      ENDIF.
    ENDFUNCTION.

  • Mb1b transfer posting

    Hello friends,
    In mb1b second screen, they are entering second line item which is called scrap(eg: M03-SCRAP).This is updated in MARD table as the scrap materials doesn't belong to any batch.
    So, they are entering matnr and labst (quantity in second line item).
    How to identify this particular scrap material from mard table.
    I m writing query like this:-
    SELECT matnr labst FROM mard
           INTO CORRESPONDING FIELDS OF TABLE it_mard
                           WHERE matnr = 'M03-SCRAP'
                           AND   werks = plant
                           AND   lgort = '2200'.
    How to get this material number without hardcoding bcoz this ll be vary for different material numbers.

    Hello max,
    scrap field they enter like "M03-SCRAP".
    They said that if first 3 letters of scrap = first 3 letters of receiving material.
    then data has to pick from mard-labst and to be added to the first line item of material and mard should be updated.
    please luk into my coding(function module):-
      DATA : ls_quan2 TYPE p DECIMALS 3,
             ls_quan3 TYPE p DECIMALS 3.
      DATA : it_mard LIKE mard OCCURS 0 WITH HEADER LINE.
      gmhead-pstng_date = sy-datum.
      gmhead-doc_date   = sy-datum.
      gmcode-gm_code    = '04'.       "Transfer Posting (MB1B)
      SELECT matnr clabs FROM mchb
                           INTO TABLE it_mb1b
                           WHERE werks = plant
                           AND   lgort = send_stloc
                           AND   charg = batch.
      SELECT matnr labst FROM mard
                           INTO CORRESPONDING FIELDS OF TABLE it_mard
                           WHERE matnr like '%SCRAP'
                           AND   werks = plant
                           AND   lgort = '2200'.
      LOOP AT it_mb1b INTO wa_mb1b.
        it_gmitem-move_type    = move_type.
        it_gmitem-plant        = plant.
        it_gmitem-stge_loc     = send_stloc.
        it_gmitem-move_plant   = move_plant.
        it_gmitem-move_stloc   = recv_stloc.
        it_gmitem-batch        = batch.
        it_gmitem-material     = wa_mb1b-matnr.
        ls_quan2 = quan_measure - wa_mb1b-clabs.
        IF ls_quan2 LE 0.
          ls_quan3 = wa_mb1b-clabs.
        ELSE.
          ls_quan3 = wa_mb1b-clabs + ls_quan2.
          it_mard-labst = it_mard-labst - ls_quan2.
    MODIFY table it_mard TRANSPORTING labst.
        <b>MODIFY it_mard TRANSPORTING labst WHERE matnr = 'M03-SCRAP'.</b>    MODIFY mard. " FROM TABLE it_mard.
        ENDIF.
    <b>" Here how we know that matnr only update in mard.</b>
        it_gmitem-entry_qnt    = ls_quan3.
        APPEND it_gmitem.
      ENDLOOP.
      CLEAR return.
      CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
        EXPORTING
          goodsmvt_header             = gmhead
          goodsmvt_code               = gmcode
      TESTRUN                     = 'X'
       IMPORTING
      GOODSMVT_HEADRET            =
         materialdocument            = mat_doc
      MATDOCUMENTYEAR             =
        TABLES
          goodsmvt_item               = it_gmitem
      GOODSMVT_SERIALNUMBER       =
          return                      = return
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait          = 'X'
    IMPORTING
      RETURN        =

  • GL Transfer Posting

    Hi all
    Can anyone help with the following?
    I've a balance sheet account xxxx which is not open item managed and there are many postings to that account for long.
    Now, I would like to change it to open item management. I know it wouldn't let me change as the balance on the account is not zero.
    I want to switch this function on retroactively, so I'm creating a similar account yyyy with same settings and do a GL transfer posting.
    Now, question is how to do the GL transfer posting? After I do the GL transfer posting from xxxxx to yyyyy, can I delete xxxxx and recreate xxxxx it with open item mgmt switched on.. and then do the transfer posting from yyyyy to xxxxx..?  I want to do this because, the end user doesn't want to change the gl a/c no. but would like to have the open item mgmt swtiched on..
    I hope the scenario is clear
    Can anyone help?

    Hi,
    Good afternoon and greetings,
    There is a program RFSEPA02 which is used to convert the line items into open items managed...All you have to do is change the master to make it as open item managed after changing the FSG (Field Status Group) of Account Groups and then activate the open item managed.  Run this program and it will convert all the records into open item managed for the old records.
    PLEASE NOTE:
    YOU CAN USE THIS PROGRAM IN CONSULTATION WITH SAP.  PLEASE CHECK IT OUT WITH THEM AND USE THE PROGRAM TO CONVERT THE OPEN ITEM OLD DATA.  HOPE IT IS CLEAR. PLEASE REFER TO SAP FOR USING THIS PROGRAM.
    Hope this meets your requirement and request you to reward points if found useful.
    Thanking you
    With kindest regards
    Ramesh Padmanabhan

  • Concept of Transfer Posting?

    Hi,
    What is the concept of transfer posting when trabsferring the material (my scenarion is transfer of material from plant to depot)
    Usefull answer will be rewarded
    Thanks

    hi
    ur depot is also a kind of plant so u can refer plt to plt transfer
    The stock transfer process begins with a requirement to transfer material from one plant to another within the same company code. This request, a stock transfer requisition, may be created automatically by MRP in the procuring plant, or manually by a buyer.
    The process also works without MRP. Here, the buyer creates the stock transport order directly. The only master data requirement is the material master to support the stock transfer process. The material master must exist in both the procuring (receiving) plant and the providing (issuing) plant. Unlike other purchase orders, stock transfer purchase orders are not subject to approval. A buyer validates the accuracy of the stock transfer purchase requisition and converts it into a stock transfer purchase order. Without MRP, the buyer creates the stock transfer purchase order directly. A warehouse clerk at the issuing plant monitors the materials to be shipped, and creates necessary deliveries. Once a delivery is created, a pick list is generated for the materials. A warehouse clerk gathers the materials and confirms the picked quantities. Once the delivery is complete, the delivery quantities are issued, appropriate documentation is generated, and the shipment is sent, ending the process for the issuing plant. Goods are received at the receiving plant referencing the delivery number on the shipping documents. Inventory is received into a location based on fixed parameters proposed from the material master which can be changed at time of purchase order creation or goods receipt (transactional data capture).
    Process Flow
    This scenario consists of the following steps:
    Creating stock transport order
    Creating delivery for stock transport order
    Key Points
    Supports all required documents for stock transfers with delivery
    Supports all required master data aspects like batch management and serial numbers
    Monitors stock in transit
    Delivery costs can be entered in the stock transport order
    use following link
    http://help.sap.com/bp_bblibrary/600/Documentation/J52_Scen_Overview_EN_IN.ppt
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/47/60fff649f011d1894c0000e829fbbd/frameset.htm
    regards
    kunal
    Edited by: kunal ingale on Aug 21, 2008 6:41 AM

Maybe you are looking for