STO - Movement Types

Hi
GRN with reference to purchase order or Inbound delivery, movement type taken is 101.
I've configured the STO process (Site to Site & Storage Location to Storage Location).
Site to Site process
STO and outbound delivery is created. Post Goods Issue completed with movement type (641). Same movement type 101 is captured during Goods receipt with respect to outbound delivery. Same in the case of Location to location STO.
Since movement type 101 is used for both process, in reporting level i'm not able to differentiate GR done from vendors and GR done through STO's.
Whether any customized movement types can be used for STO process.
Regards
SAM

Hi..
Following are the DC and stores which we have.
DC : 6000 (Warehouse)
Store : 6001 (Showroom)
GR from vendors with reference to PO or inbound delivery completed with movement type 101 in DC 6000
Present stock position is 1000.
Now a STO from site to site 6000 to 6001
STO created for 10 pcs - Outbound delivery - PGI completed (641) - GR done at 6001 with reference to outbound delivery (101).
Again STO from 6001 to 6000.
STO created for 10 pcs - Outbound delivery - PGI completed (641) - GR done at 6000 with reference to outbound delivery (101).
Now the entries with movement type 101 in DC 6000 is for 1000 pcs and 10 pcs.
While extracting the data to BI, for stock movement reports. GRN qty will consider 1010 pcs.
We have around 7800 SKU's, entire report is getting wrong. Thats why i'm enquiring about customized movement types. Please suggest.
Regards
SAM

Similar Messages

  • PGI for STO movement type error Message no. L9005

    Hi Gurus,
    I have created an STO.Created delivery and confirmed TO.
    Now while doing PGI,single step only(647 movement type),
    system throws the following message,
    "" Error during search for WM movement type (641 1 L K  )
       Message no. L9005 "".
    As per my checking for both IM movement types 641 and 647, ' 641 ' has been assigned as
    Ref movement type and " 601"  has been assigned as WM movement type.
    601 is maintained in WM.Should I maintain 641 in WM?That case I have to change SAP std settings..
    If so pls provide me the details for 641 K.
    Kindly help.
    Best Regards

    Hi Kumar,
    Try the following:
    Maintain an entry for your warehouse with movement type 641 SpStIn and Movment Indicator l combination in transaction OMLR.
    And also ,
    Check in IMG Path - Enterprise Structure --> Assignment --> Logistis Execution --> Assign warehouse number to plant/storage location.
    Here check whether the warehouse number is assigned to your plant and storage location.
    Thanks!
    Preethi
    Edited by: preethi R on Dec 2, 2008 10:50 AM
    Edited by: preethi R on Dec 2, 2008 10:50 AM

  • STO Movement Type !

    hi
    Could anyone guide me on this:
    I have created a material master which is meant for free samples.
    The material master fields have the same values except the two things:
    1. We have a material group sepately for samples.
    2. A separate Valuation class created and assigned in the material master for samples.
    Now, when i do STO for the material, in the delivery ,instead of proposing 641 system is proposing 647 movement type. This 647 is a copied from 641.
    I am wondering what prompts system to propose MT 647 instead of 641.
    Item category and delivery type is correct.
    I checked up OMJJ, movement type defining area, did not find anything useful.
    can any one help me by explaining what prompts MT647 and where is the control?

    Hi...
    Please check Mvt. Type in item catagory of delivery. What is the default is set there in mvt. type field.
    Thx.

  • Which movement type use for return stock form one plant to other plant  in

    HI friends i am working on STO PROCESS
    i need to transfer return stock from one plant to other plant as a return stock i am using Mvt type 455
    but system shows  following error
    Update control of movement type is incorrect (entry 455 X X _ L)
    Message no. M7226
    Diagnosis
    The system could not find entry 455 X X _ L in any of the movement type control tables.
    Procedure
    Cancel current processing.
    Contact your system administrator.
    Action to be taken by the system administrator
    Check in Customizing for Inventory Management under Copy, Change Movement Types whether the entry is contained in the Update control view for the movement type.
    If the entry is missing, proceed as follows:
    For standard movement types, this means that the given process is not supported using the present data combination. Do not create any entries without prior arrangement with your SAP consultant. Otherwise, incorrect postings may result.
    For customer-defined movement types (beginning with 9, X, Y, or Z), this may mean that they have not been fully defined. Delete the movement type and re-create it by copying a standard movement type.
    thanks in advance

    Hello,
         I think there is a standard STO movement type you can use. But I can't remember. Why don't you try to find it and test if it fit your requirement?
         There are some information for your reference. Please check on website:
    http://www.sap-img.com/materials/difference-for-stock-transfer-and-transfer-posting.htm
    Using STO without delivery: 
      doc.type: UB
      GI:351, GR:101
      STO with delivery:
      GI:641, GR:101
      delivery type:NL
      STO with delivery and billing:
      GI:643, GR:101
      delivery type:NLCC , billing type:IV
         And if you want to use the way to return the goods replenishment, try to flag the return checkbox while you create purchase order item. Of course, corresponding configuration is required.

  • Stock Transfer by movement type 301 referring STO

    Dear Experts,
    I am unable to generate a stock transfer referring an STO in MB1B or MIGO by movement type 301. I am successfully doing whenever I refer a Reservation. Please advice.
    Regards,,
    Subhro Chakravarty

    Hi,
    i have to ask you to read the SAP Documentation for 'Stock Transfer Using a Stock Transport Order'.
    It is explained there how to post a goods movement for STO.
    http://help.sap.com/erp2005_ehp_04/helpdata/en/4d/2b90dc43ad11d189410000e829fbbd/frameset.htm
    br, G

  • Movement Type 161error in STO return (Plant to Plant) at the time of goods issue .

    Hi all...
    Am getting the following error while posting goods issue through VL02N
    Update control of movement type is incorrect (entry 161 X X _ L)
    Message no. M7226
    Diagnosis
    The system could not find entry 161 X X _ L in any of the movement type control tables.
    Process : STO Return Plant to Plant.
    Purchase Order ( STO) done.
    Goods issue done.
    Goods receipt at the receiving plant.
    Amended Purchase order, added one more line item and ticked return.
    Inbound delivery done.
    VL02n Goods issue am getting the error.
    Pls help.
    Suhas
    MM consultant

    Update control of movement type is incorrect (entry 161 X X _ L)
    Have a look into your OMJJ customizing for 161 movement type:
    It probably looks like mine:
    the error message has the info in exact the same sequence
    161 X X _ L
    this is 161, checkmark checkmark blank L  in the table above.
    L would mean reference to a delivery.
    But as you can see here, there is no L, everything is B which means reference to purchase order.
    It is not allowed to add items in a delivery without purchase order reference, it is technically possible, but it finally ends in the error you have.
    The process has to start from the purchase order.

  • Movement type 1-step in Schedule line category for STO

    Hello Experts,
    What is the difference between single step and two step movement type in Stock Transport Order? What is its significance?
    My understanding in case of stock to stock and plant to plant material movements in Inventory management:
    If we use single step, once the goods are issued at the issuing plant stocks are updated immediately both at the issuing plant (reduced) and receiving plant (increased).
    In case of two steps,
    Stock to stock – material will be in <u>stock in transfer</u> for receiving plant once the goods are issued at issuing plant
    Plant to plant – Material will be in <u>stock in transit</u> for receiving plant once the goods are issued at issuing plant.
    Is this the same concept in STO?
                          OR
    What is the significance of Movement type 1-step in Scheudle line category?

    Have a look there
    http://help.sap.com/saphelp_470/helpdata/en/4d/2b90dc43ad11d189410000e829fbbd/frameset.htm

  • Movement types used in STO one-step process

    Dear all,
    Presently the one-step STO process in my system uses mvt 645 for Good Issue and mvt 101 for goods receipt. I need to have it use a custom copy of mvt 101 for goos receipt.
    Does anyone know where this setting can be changed? Can it be changed?
    Thanks
    Cao Huy

    Hi
    Please make use the above link
    and the transcation Code: OMJJ.
    Copy, Change Movement Types
    Assuming  want to create another movement type Z01.
    Transaction OMJJ
    Select the standard movement type 101
    Click copy, then overwrite the 101 with Z01
    Click the Enter button, then click Copy all
    Select the new movement type Z01
    On the left hand column screen, click Reversal/follow-on movement
    Fill in the reversal movement type
    *For the rest of the options, you can leave it alone or change it depending on your requirement *
    Rgds
    RG

  • Movement types used in these activities and also STO

    HI SAP GURUS,
    Movement types used in these activities and also STO ( PLANT TO DEPO), (DEPO TO PLANT ) WIT AND WITHIN 1 COMPANY CODES
    AT PGI
    AT BILLING
    AT RETURNS
    all possible ways OR any short cuts
    points are to be rewarded for best relevent answer

    hi
    for PGI 601
    for Returns 651
    for Billing - None, because it is either copied from delivery or order.
    What is a depo in your language? Is it a storage location,if yes, shop floor to storage location it is 911
    for STO
    If it is within company code STO, in the STO it is 101, during delivery 641.
    it is intra company codes, then it is 101 in STO and delivery it is 645 or 647 (not sure)
    goodluck.

  • STO based delivery movement type determination

    Hi,
    I had a question.
    For deliveries created from sales order, the delivery item movement type is derived from the schedule line category definition. But for stock transfer order based delivery, there's no sales order created , then there's no schedule line category there.
    How does SAP determine the movement type in this case?
    Thanks.

    1. For replenishment delivery, the movement type is still determined from schedule line category.
    2. For every delivery item category, there is a corresponding sales item category with the same name.
    3. Tcode VOV5, you can find the corresponding schedule line categtory at the same.
    4. Tcode VOV6, you can then find the movement type in schedule line category. BTW: the filed "Movement Type 1-Step" is for one-step STO. Movement type in field  "Movement Type" is for two-step STO.
    5. In addition: for replenishment delivery, even though there is no sales order, the copy control is still defined from SO to delivery. The sales order type is the default order type in delivery type cusotmizing.

  • STO Goods Issue Movement Type 641 vs 603

    Hello,
    I created a STO for stock transfer.  During the Goods Issue against delivery, the system is picking movement type 603.  Is this right? I have always seen 641 for issuing goods against STO outbound delivery.
    How to make system choose movement type 641 for goods issue against STO outbound delivery.
    Thanks,

    As expected, why do u choose to use UL, and why not NL?
    If you continue to use UL, may be u should ask your SD consultant to change the schedule line category to movt type 641 or change the existing schedule line category movt type to 641..
    hope this helps...
    Rgds,
    Harish

  • Movement type for goods issue in intercompany STO business scenario

    Hi, everyone,
    In intercompany STO scenario, firstly we should create a purchase order with a transfer order type just like as UB,
    then we use T-code: VL10B to create the delivery note by referencing the purchase order created in first step, in succession, billing, goods reciept.
    Actually I have a question about the movement type in goods issue process. The standard is 643 deliveried by SAP.
    Can I customize the movement type in intercompany STO business scenario

    hi,
    The following are the scenarios of cross plant goods movements:
    Alternate plant procurement of purchased items
    Alternate plant production
    Plant-to-plant goods transfer of grouped project stock
    Stock transfer without reference to a stock transfer order (STO)
    1 Step – 301
    1 Step reversal – 302
    Stock transfer with reference to an STO in the receiving plant without SD
    2 Steps - 351 and 101
    2 Steps reversal – 102 and 352
    Stock transfer with reference to an STO in the receiving plant with SD delivery
    2 Steps – 641 and 101
    2 Steps reversal – 102 and 642
    1 Step – 647
    1 Step reversal – 648
    Movement Type &  Description
    301 / 302
    Goods receipt into production order in another plant. This is a one-step, cross-plant stock transfer. This movement type does not use STOs but behaves like a goods receipt of stock, except that the stock comes from another plant into the current plant. Movement 302 is the reverse of 301.
    351 / 352
    Stock transfer that is in transit between two plants. This is a two–step, cross-plant stock transfer, because after movement 351, you do not immediately see the stock in the receiving plant. After movement 351, the stock is in transit between the two plants. Only after you have performed a goods receipt (movement 101/102)of this ”in-transit” stock into the receiving plant can you see this stock in the receiving plant. Movement 352 is the reverse of 351.
    641 / 642
    Stock transfer that is in transit between two plants, with delivery documents (Sales and Distribution). This is a two-step, cross-plant transfer of stock, because after movement 641, you do not immediately see the stock in the receiving plant. After movement 641, the stock is in transit between the two plants. Only after you have performed a goods receipt (movement 101/102 ) of this ”in-transit” stock into the receiving plant can you see this stock in the receiving plant. Movement 642 is the reverse of 641.
    647 / 648
    Stock transfer to another plant, with delivery documents (Sales and Distribution), with STO. This is a one-step, cross-plant stock transfer because after movement 647, you cannot immediately see the stock in the receiving plant. The stock is never in transit with this movement type, but the stock is transferred with reference to an STO with Sales and Distribution documents. Movement 648 is the reverse of 647.
    regards,
    Siddharth

  • STO One Step Movement Type Configuration

    Currently,we have a scenario where we want to configure a copy of movment 645 (one step) to use. The reason is we have follow on processes that are conditional and the stock transport is a logical move for business reason.
    We are able to configure the copy of the original movement. However, what we are not able to do is change the subsequent "101" follow on movement. 
    We would like to change this. Can someone give some advice...
    Steve Selasky
    IT Tech Lead

    Hello
    Stock  tranport  order for 1st step  Plant to plant 1 step  has movement type 301 and there is no need to do GR.
    The quantity of the stock transferred is posted immediately from the unrestricted-use stock of the issuing plant to the unrestricted-use stock of the receiving plant
    Kindly recheck your scenario or provide more details to check how it can be done.
    Awaiting your kind reply.
    Kishor

  • Excise Invoice for ther movement type

    Dear ALL SAP Gurus,
    In 100% EOU plant when we purchase materials against CT3 there is no excise duties on purchase. But when we purchase material without CT3 there are excise duties which will get add into material cost.
    When same material I transfered to other plant , may I have to make excise invoice( J1IS and J1IV). Client does not have any cenvatable facility.
    Also when I return this material to vendor whether J1IS and J1IV has be necessory.
    Please explain this scenarios.
    Thanks in advance
    Mahesh

    Hi,
    PLz maintian the excise data for that mterial in ithe Excise master data J1ID.
    1.For no excise dute just select as No excise duty at the time of MIGO from Excise invoice tab on the top.
    2.For Excise duty select as exise duty during MIGO.
    3.For STOS maintain as assessable value in the J1ID master data for that material in the supplying plant, the excise calculated Through J1IS as per assessable value u maintained in the master data.
    4.For vendor returns, reverse the FI documents manually for MIRO, then cancel the material doc after u post the Excise invoice , then agian u cancel the Excise invoice so that excise registers can be reversed. Then u do the vendor returns through MOGO and 122 Mov type.
    Plz check and clear.
    Regards,
    Andra.

  • BDC for MIGO for GR OutBound Delivery( A01 & R05 ) from Movement Type 107 to 109

    Hi,
    I am stuck with a very typical situation need all your expertise and advices for a solution.
    We are basically trying to create change the movement type from 107 to 109 through MIGO.
    I have made a BDC recording for MIGO ( because we would like to track each delivery specifically under shipment , I know that there is a BAPI which is there to do this but it works fine if we do the shipment with Purchase Order as input which dont want in that manner )
    Process:
    1. Creating Production Order
    2. Creating Purchase Order
    3. Creating STO
    4. Deliveries
    5. PGI for Deliveries
    6. Shipment for group of outbound Deliveries
    I have created a z program where i am passing shipment number in the selection screen.
    Then it would take all the deliveries for that shipment and pass each delivery to MIGO and process it and change the status from 107 to 109.
    Interesting part here is, the code works absolutely perfect only from my ID. But when I test from other ID it is not executing, so to check where is the problem I have added mess_tab to the CALL TRANSACTION to capture what message is been populated for my ID comparing with others
    Message Captured on Others ID's:
    MSGID: 00
    MSGNR: 344
    MSGV1: SAPLMIGO
    MSGV2: 1300
    Message Captured on MY ID:
    MSGID: MIGO
    MSGNR: 012
    MSGV1: 5000005802
    MSGV2: (empty)
    This is the problem this program is executing only on MY ID, rest all ID's it is not processing.
    We have cross verified with security and basis regarding any authorization issues but nothing came up.
    Please help me what could be the issue ( WHY it is processing successfully for my and WHY NOT for other ID's)
    Below is the main code :
    CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'                     " Converting Date format to DD/MM/YYYY
         EXPORTING
           DATE_INTERNAL            = sy-datum
         IMPORTING
           DATE_EXTERNAL            = lv_date_external
         EXCEPTIONS
           DATE_INTERNAL_IS_INVALID = 1
           OTHERS                   = 2.
           IF SY-SUBRC <> 0.                                     "#EC NEEDED
    * Implement suitable error handling here
           ENDIF.
    *   Validating input shipment number with database table VTTP
           SELECT VTTP~TKNUM
                  VTTP~TPNUM
                  VTTP~VBELN
             FROM VTTP INNER JOIN VTTK
             ON VTTP~TKNUM = VTTK~TKNUM
             INTO TABLE IT_VTTP
             WHERE VTTK~TKNUM = P_TKNUM
               AND VTTK~STDIS = 'X'.
           IF sy-subrc = 0.
    *   Validating all deliveries having same Delivery type or not
             SELECT * FROM likp INTO TABLE it_likp FOR ALL ENTRIES IN it_vttp WHERE vbeln = it_vttp-vbeln
                                                                                AND vbtyp = 'J'.
             IF sy-subrc = 0.
               CLEAR lv_lines.
               LOOP AT it_likp INTO wa_likp.
                 REFRESH:it_vbfa,BDCDATA.
    *   Validating if Delivery Type = 109 (GR already done), or Delivery Type = 107 (must process for GR )
                 SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
    *                                                AND vbtyp_v = 'J'
                                                         AND bwart = '109'.
                 IF sy-subrc = 0.
                   lv_flag1 = 'X'.
                 ELSE.
                   SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
    *                                                  AND vbtyp_v = 'J'
                                                           AND bwart = '107'.
                   IF sy-subrc NE 0.
                     MESSAGE 'No Deliveries with Movement Type "107" ' TYPE 'I'.
                   ELSE.
                     lv_flag2 = 'X'.
                     lv_lines = lv_lines + 1.
    **  BDC for MIGO
                     perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                     perform bdc_field       using 'BDC_OKCODE'
                                                   '=OK_GO'.
                     perform bdc_field       using 'GODYNPRO-ACTION'
                                                   'A01'.
                     perform bdc_field       using 'GODYNPRO-REFDOC'
                                                   'R05'.
                     perform bdc_field       using 'GODEFAULT_TV-BWART'
                                                   '109'.
                     perform bdc_field       using 'BDC_CURSOR'
                                                   'GODYNPRO-OUTBOUND_DELIVERY'.
                     perform bdc_field       using 'GODYNPRO-OUTBOUND_DELIVERY'
                                                   wa_likp-vbeln. "'80019574'.
                     perform bdc_field       using 'GOHEAD-BLDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-BUDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-WEVER'
                                                   '1'.
                     perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                     perform bdc_field       using 'BDC_OKCODE'
                                                   '=OK_POST1'.
                     perform bdc_field       using 'GODEFAULT_TV-BWART'
                                                   '109'.
                     perform bdc_field       using 'GOHEAD-BLDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-LFSNR'
                                                   wa_likp-vbeln. "'0080019574'.
                     perform bdc_field       using 'GOHEAD-BUDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-WEVER'
                                                   '1'.
                     perform bdc_field       using 'GODYNPRO-DETAIL_ZEILE'
                                                   '   1'.
                     perform bdc_field       using 'GOITEM-ERFME'
                                                   'EA'.
                     perform bdc_field       using 'GOITEM-ERFMG'
                                                   '1'.
                     perform bdc_field       using 'GOITEM-LSMNG'
                                                   '1'.
                     perform bdc_field       using 'GOITEM-LSMEH'
                                                   'EA'.
                     perform bdc_field       using 'GOITEM-MIGO_ELIKZ'
                                                   '1'.
                     perform bdc_field       using 'GOITEM-BWART'
                                                   '109'.
                     perform bdc_field       using 'GOITEM-LGOBE'
                                                   'RX Cross-docking'.
                     perform bdc_field       using 'BDC_CURSOR'
                                                   'GODYNPRO-DETAIL_TAKE'.
                     perform bdc_field       using 'GODYNPRO-DETAIL_TAKE'
                                                   'X'.
                     PERFORM bdc_dynpro      USING 'SAPLMIGO' '1300'.
                     PERFORM bdc_field       USING 'BDC_CURSOR'
                                                   'G_TIP_DONT_SHOW_AGAIN'.
                     PERFORM bdc_field       USING 'BDC_OKCODE'
                                                   '=OK_TIP_GO'.
                     PERFORM bdc_field       USING 'G_TIP_DONT_SHOW_AGAIN'
                                                   'X'.
    *& Avoid unncessary screens to populate while processing background.
                     LV_OPTIONS-DISMODE = 'N'.
                     LV_OPTIONS-UPDMODE = 'S'.
                     LV_OPTIONS-NOBINPT = 'X'.
                     CALL TRANSACTION 'MIGO' USING BDCDATA  OPTIONS FROM LV_OPTIONS MESSAGES INTO IT_MESSTAB1 .
                     WAIT UP TO 1 SECONDS.
                     DELETE IT_MESSTAB1 WHERE MSGTYP NE 'E'.
                     IF IT_MESSTAB1[] IS NOT INITIAL.
                       APPEND LINES OF IT_MESSTAB1 TO IT_MESSTAB.
                     ENDIF.
                   ENDIF.
                 ENDIF.
               ENDLOOP.
             ENDIF.
           ELSE.
             MESSAGE 'Shipment Number does not exists Or not Planned' TYPE 'E'.
           ENDIF.
         ELSE.
           MESSAGE 'Please insert Shipment Number' TYPE 'E'.
         ENDIF.
         IF lv_flag1 = 'X' AND lv_flag2 = 'X'.
           MESSAGE 'This shipment is processed with an inconsistent goods receipt' TYPE 'I'.
         ELSEIF lv_flag1 = 'X'.
           MESSAGE 'Shipment already been processed for these deliveries' TYPE 'I'.
         ELSEIF lv_flag2 = 'X'.
           lv_lines1 = lv_lines.
           CONDENSE lv_lines1 NO-GAPS .
           CONCATENATE lv_lines1 'Goods Receipt are posted for the shipment '
                  INTO lv_message SEPARATED BY space.
           MESSAGE  lv_message TYPE 'I'.
         ENDIF.
    * Display Messages from Message TAB.
         DELETE ADJACENT DUPLICATES FROM IT_MESSTAB.
         DATA:lv_msg TYPE string.
         LOOP AT IT_MESSTAB INTO WA_MESSTAB.
           CALL FUNCTION 'FORMAT_MESSAGE'
             EXPORTING
               ID        = WA_MESSTAB-MSGID
               NO        = WA_MESSTAB-MSGNR
               V1        = WA_MESSTAB-MSGV1
               V2        = WA_MESSTAB-MSGV2
               V3        = WA_MESSTAB-MSGV3
               V4        = WA_MESSTAB-MSGV4
             IMPORTING
               MSG       = lv_msg
             EXCEPTIONS
               NOT_FOUND = 1
               OTHERS    = 2.
           IF sy-subrc <> 0.
    * Implement suitable error handling here
           ENDIF.
           WRITE:/ lv_msg.
         ENDLOOP.
    *        Start new screen                                              *
       FORM BDC_DYNPRO USING PROGRAM DYNPRO.                 "#EC PF_NO_TYPE
         CLEAR BDCDATA.
         BDCDATA-PROGRAM  = PROGRAM.
         BDCDATA-DYNPRO   = DYNPRO.
         BDCDATA-DYNBEGIN = 'X'.
         APPEND BDCDATA.
       ENDFORM.
    *        Insert field                                                  *
       FORM BDC_FIELD USING FNAM FVAL.                       "#EC PF_NO_TYPE
         CLEAR BDCDATA.
         BDCDATA-FNAM = FNAM.
         BDCDATA-FVAL = FVAL.
         APPEND BDCDATA.
       ENDFORM.
    Thanks,
    Srini

    Hi Rob,
    Thanks for quick reply.
    I have checked the NOTE : 304122
    But there in the NOTE it says ( " BAPI, BAPI_GOODSMVT_CANCEL, BAPI_GOODSMVT_CREATE, CNTL_ERROR" )
    These BAPI's work perfectly for (purchase order as input type), but here out type is ( A01 & R05 ) we are giving DELIVERY NUMBER as input to MIGO.
    So for this scenario we cannot use those BAPI's mentioned in the NOTE.
    Also as stated earlier in the message interesting part is
    "The code works absolutely perfect only from my ID. But when I test from other ID it is not executing. Code is working exactly as expected ONLY to my ID. When i try to execute the same code from another's ID it is not working"
    So what do you think might be the issue?

Maybe you are looking for