Transfer posting printout with trasns type WA

Hi
Issue: printout for Transaferposting with trans type WA with MB1B for 301 mvmnt with error message "The system could not create any outputs".
what i did was, i set the printer configuarion for inventory management output for transposting in SPRO. with customization table B517,B518,B519,B520 with diffrent options a srequested by business, for the able table i maintained a new access seequnce.i was able to take the printout sucesffully in DEV system.
Business was accepeted to  move the changes to Quality system. when i transports into QUALITy, the transport was displayed woth error message as "Table TMC1, entry B517,B518,B519,B520 table missed,". due to this transport, in qualkity system dump occured when doing MIGO transcation.
when we check the dump, it states that table B517,B518 tablel etccc.
due to this i deleted the tables in an access seequence, i moved the transport to qulity system. now NO dumps are displaying when doing MIGO transcations.
In this situtaion, how will i move changes to quality system??
my action points:
1. i cretaed a new tables B521,B522,B523,B524 with copy of B517,B518,B519,B520 and  move dto quality system.
2. i cretaed a new access seequnce for tables B521,B522,B523,B524 (Note:Old access seequcne was deleted and B517,B518,B519,B520 tables were deleted) .
3. when i check the scenario for MB1B with 301 movement in DEV system, out put is not triggring . why??
message displayed as  "The system could not create any outputs"..
Question to you:
how should we correct my mistake??
Regards,
Pabbati Obulesu

Hi,
   Please ensure that the condition record for the output types has been maintained in the Dev as well as QAS system in MN21 transaction. Maintain the same and test again.
Regards,
AKPT

Similar Messages

  • Auto print of Goods Issue/Transfer Posting Documents by Movement type

    Hi,
    We have created two different output types to print the layout's of Goods Issue/Transfer Posting Documents.
    The requirement is to default the message in the document by movement type (key combination)
    Meaning if it is 201 it should populate GI output type
    If it is 313 it should populate TP output type.
    we do not have any standard key combination  (NACR) by movement type wise.
    Any alternative way of meeting this requirement?
    Thanks
    Regards
    Ram

    Hello Kevin,
    I donu2019t think it is necessary to use a user exit to keep the Material B (that is transferred from Material A) in the same bin.
    This can be controlled in the customizing: indicator Post to same bin, that can be set in the WM Movement type (V_T333-KZUAP) and in the Storage type (V_T3010-KZUAP).
    Now I donu2019t know your business process but I am surprised that Material B requires more space than Material A since it is u2018bornu2019 by means of a transfer posting and not a production or packing step that makes it bigger in terms of capacity required.
    A workaround for this could be to transfer (LT10) Material A first to a separate Storage type (with the Post to same bin-flag set) that has no Capacity check and after the 309 posting transfer it back into the warehouse with LT10.
    Success and thanks beforehand for any credits!
    Kind regards,
    Bart

  • Storage location is not updated after posting GR with Mvt type 107(Valuated GR blocked stock)

    Hi experts,
    Before posting GR through Movement type 107 (valuated GR blocked stock) we can see the storage location field in MIGO screen and able to enter value into this field. But after posting GR when we retrieve the material document we are finding that the field (storage location) is blank, i.e. it's not updated at all. When we check the stock in MMBE we find that no quantity is updated for valuated GR blocked stock.
    We want the storage location to be updated while posting GR with 107 Mvt type.
    Any idea Please?
    Points assured.
    Thanks
    Amitava

    SAP describes it in help.sap.com: Since the material is not to be added to the inventory yet, do not enter a storage location.
    If you require a storage location, then I assume that your design does not match with the design of SAP, you are using a function to solve a gap which is not foreseen by SAP for this case.
    Especially the 107 is usually representing stock which is still in transfer but you are already the legal owner and have to show the value of those goods in your books.

  • Transfer Posting MB1B with MvT 311

    Dear experts,
    I have 1 issue. For example, to do transfer posting from Sloc '1201' to Sloc '10F1' and '10F1' is in WM. With movement '311' , a transfer requirement is automatically created, followed by a transfer order creation screen.
    I have automate all these process using 'BAPI_GOODSMVT_CREATE', 'L_TO_CREATE_TR' & 'L_TO_CONFIRM'. And it works fine.
    My question is, physically the user is actually do the stock placement first to the storage bin then only they create a transfer posting. At the point of stock placement, the end user do not know the storage location to move stock. If I automate this process to create TO first then only do transfer posting, is it a correct way? I want to use FM 'L_TO_CREATE_SINGLE' & 'L_TO_CONFIRM'. Please advise.
    Thank you.

    Hello Hasniza,
    Yes you could use this function modules:
    L_TO_CREATE_SINGLE                                                       
    Create a transfer order with one item                                                                               
    L_TO_CREATE_MOVE_SU                                                      
    Create a transfer order to move a storage unit                                                                               
    L_TO_CREATE_TR                                                           
    Create a transfer order for a transfer requirement                                                                               
    L_TO_CONFIRM                                                             
    Confirm a transfer order                                                
    Please check the following link:
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/c6/f83a294afa11d182b90000e829fbfe/frameset.htm
    You could do that by using the user exit EXIT_SAPLL03T_002 not directly via function module.
    Please also pay attention to the documentation of enhancement MWMTO002: 
    "... Therefore, you must never start a transfer order creation via a function module."                                                       
    But you call FM L_TO_CREATE_SINGLE inside of this exit.   
    I hope it helps you.
    Regards,
    Fábio Almeida
    MM Consultant

  • Transfer Posting problem with "sales order stock type" status

    Hello, i have this problem, i spend 2 days looking in the forum, but
    nothing, the question is:
    The SD users sell an item, and the item get the status of "sales order
    stock type" in the MMBE, but at the same time, the MM user made a
    trasfer posting in two steps, he take out material with transaction
    MIGO, mvt 351, to another plant, but the materail was already
    compromised with SD; now he cant sell the items, because he dont
    realize that the material was in sales order stock type, and he already
    transfer it to another plant. how can i block this? if a material in
    MMBE is with "sales order stock type" status, he CANT transfer it with
    351 mvt type, what config i have to make?  thanks a lot!!!!
    now the quantity of the unrestict use
    stock is lower than the sales order, we dont want to have this issue,
    thanks again
    Edited by: Alex Arti on Aug 6, 2008 7:14 PM
    Edited by: Alex Arti on Aug 6, 2008 7:16 PM

    Hi!
    Have you recently upgraded to EHP4? In this case, please, check the note 1441195. This note should solve the issue that you are reporting.
    I hope this helps,
    Esther.

  • MM Transfer material UNBW with movement types

    Dear friends !
    I would like to know if is it possible to transfer material UNBW thru MM ?
    Could I use movement type 303 - 305  or 641 and 101 ?
    best regards
    Ale

    HI,
    You can use any movement type UNBW. For UNBW account assignment is mandatory so when you post UNBW material reciept it will directly post to comsumption account not to stock account.
    Regards,
    Chetan.

  • Posting IDOCs with partner type SP ?

    We have to post IDOCs to SAP where the partner type is SP . How do we configure XI to achieve this ?
    We are disabling the control record and so not looking at the option of hardcoding the EDI_DC record.
    I understand we need to specify Alternate identifiers in IDOC channel and also choose header mapping in receiver agreement, however am not very clear on the steps.
    Can neone help me with the steps.
    Thanks
    Saravana

    I need values something like below to be in the control record of the IDOC and could not find a way of doing it
      <SNDPOR>PORT1</SNDPOR>
      <SNDPRT>SP</SNDPRT>
      <SNDPRN>ServiceProvider1</SNDPRN>
      <RCVPOR>SAPS32</RCVPOR>
      <RCVPRT>SP</RCVPRT>
      <RCVPRN>ServiceProvider2</RCVPRN>
    By default , the SNDPRT & RCVPRT carry the constant "LS"(i still do not get y this is enforced by the IDOC adapter). Our sender system is a FTP server & receiever is SAP system. We have the Business Systems defined as service without party.
    I tried hardcoding the values in EDI_DC40 in message mapping, but the IDOC adapter removes(!!) it and creates its own header(inspite of the chk box being unchecked or checked!!?? in the communication channel configuration)
    Christoph , i could not make out much out of the thread u ve pointed to.
    Thanks
    Saravana

  • IDOC status 64 not converting to 53, while trying to post GR with IDOC type MBGMCR02

    Hi All,
    We are having a issue while posting GR for an inbound delivery using IDOC type MBGMCR02. We are using FM BAPI_IDOC_INPUT1 for the same (taken from the process code BAPI). The IDOC is getting generated, but with status 64. And here it is throwing a dump Messge type "X".
    How can we get this IDOC processed to next stage / get status 53. The IDOC is failing to get status 53, while updating the delivery document flow information.
    We took the ref' of note # 833603, to post the GR.
    Any help is highly appreciated.
    Regards,
    Simadri

    Thanks Sudeesh for replying my question.
    I just found one note 1993787 which resolved my isssue and was released recently on 2nd may
    Thanks,
    Simadri

  • 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

  • Transfer posting against purchase order in MIGO transaction

    Dear all,
    How can we make the settings in MIGO transaction code for Transfer posting with reference to Purchase order.
    Other wise, i want to do the transfer posting of my goods to my sub contractor with refernce to PO number in MIGO Tcode
    Any config settings are required.
    Thanks & Regards,
    R.Saravanan

    As per SAP online help you have three options to post components to your SC vendor's special stock:
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/4d/2b906243ad11d189410000e829fbbd/frameset.htm
    You can provide components for existing purchase orders in the following ways:
    from the SC Stock Monitoring for Vendor list as a goods issue via Inventory Management
    from the SC Stock Monitoring for Vendor list as a delivery via Shipping
    from the Inventory Management menu
    If you read the instruction for the third option (first two is about ME2O), you will see it is speaking about MB1B and not about MIGO.
    1. From the Inventory Management menu, choose Goods movement ® Transfer posting.
    2. Enter the issuing plant and storage location. Choose Movement type ® Transfer posting ® Stck w. subcontract. ® From unrestricted. Enter the vendor and then choose Transfer posting ® Create with reference ® To purchase order.
    A dialog box appears in which you can enter up to 4 purchase orders.
    In MIGO you can choose only "A08" with "R02", "R08", "R09". "R01" is not allowed for "A08" in standard system.
    (Maybe it is possible but I do not know how...)
    Edited by: Csaba Szommer on Aug 5, 2010 11:54 AM
    Edited by: Csaba Szommer on Aug 5, 2010 11:54 AM

  • Import from database an internal table with generic Type : Web Dynpro ABAP

    Hi everyone,
    i have a requirement in which i'm asked to transfer data flow between two frameworks, from WD Component to another. The problem is that i have to transfer internal tables with generic types. i used the import/ export from database approache but in that way i get an error message saying "Object references and data references not yet supported".
    Here is my code to extract a generic internal table from memory.
        DATA l_table_f4 TYPE TABLE OF REF TO data.
      FIELD-SYMBOLS: <l_table_f4> TYPE STANDARD TABLE.
      DATA lo_componentcontroller TYPE REF TO ig_componentcontroller .
      DATA: ls_indx TYPE indx.
      lo_componentcontroller =   wd_this->get_componentcontroller_ctr( ).
      lo_componentcontroller->fire_vh_search_action_evt( ).
      ASSIGN l_table_f4 TO <l_table_f4>.
    *-- Import table for Help F4
      IMPORT l_table_f4 TO <l_table_f4> FROM DATABASE indx(v1) TO ls_indx ID 'table_help_f4_ID'.
    The error message is desplayed when last instruction is executed " IMPORT l_table_f4...".
    I saw another post facing the same problem but never solved "Generic Type for import Database".
    Please can anyone help ?
    Thanks & Kind regards.

    hi KIan,
    go:
    general type
    TYPE : BEGIN OF ty_itab,
               field1 TYPE ztab-field1,
               field2 TYPE ztab-field2,
    *your own fields here:
               field TYPE i,
               field(30) TYPE c,
               END OF ty_itab.
    work area
    DATA : gw_itab TYPE ty_itab.
    internal table
    DATA : gt_itab TYPE TABLE OF ty_itab.
    hope this helps
    ec

  • Transfer posting stocks from quality inspection to unrestricted, problem

    Hello Guys,
    kindly help me i am having problems doing transfer posting (mb1b) using movement type 321. because in my stock overview (mmbe) thera are stocks in Quality Inspection, i want that to be trasfered in Unrestricted Stock. that's why i execute transfer posting but there is an error occured doing it so. the error is "change the inspection stock of material 1078 in QM only". how could i make this stocks transfer to unrestricted?
    please advise me the correct way to settled this.
    thanks and regards,

    Hello Guys,
    I am very thankful for all of you contributing to this thread of mine hope in some other time you can work it out with me again I already done all this resolutions you have mention and I also know that is all the right wya to solve this issue but i dont see my problem exists on the configuration in material tpye allocation because in our business sample the FERTin standard SAP but with us it is customized name, have different code it was not define in TLtype in material allocation for quality inspection (Q), now i know what to do to call our admin to authorized my config there.
    Thank you so much i will closed this thread now please help me in some of other query next time. hehehehe..
    Regards,

  • Transfer posting MIGO  vs MB1B

    Hi,
    while doing transfer posting 311 with MB1B system automatically propose issued  batch on receiving storage location. With MIGO both batch are entered manually. Is there any setup (or user parameter) with which when we enter issuing batch in MIGO automatically receiving batch will be set as same?
    Best regards,
    vuk

    This thread solved the problem  (answer from Theodor)  [automatic batch number in migo_tr with movement type 301|automatic batch number in migo_tr with movement type 301]
    For MIGO field UMCHA set to optional.
    Inventory Management and Physical Inventory->Settings for Enjoy Transactions->Settings for Goods Movements (MIGO) -> Field Selection per Mvt Type
    Best Regards,
    Nenad

  • Transfer Posting 412 E triggers transaction key AUM

    Hi everybody,
    I'm trying to do a transfer posting ( 412 E) , every data ("dest" and "from" as material, plant, batch and storage location ) are the same. But the system is triggering the transaction key AUM, and I dont know why. I 've checked the material price (MAP) and it didn't change.
    Pls your help!!!

    The transfer posting made with the movement type 412 E is a reversal movement type (for the movement type 412, T156-XSTBW = X; so the movement type 412 is a reversal movement). The valuation logic for transfer postings made with reversal movements is explained in the note 180503.
    The material, valuation type and sales order item has an entry in   table EBEW . Table EBEW stores the valuated sales order   stock, similar to   MBEW, but this type of stock has its own pricing. All goods movements   with movement type 411/412 special stock E (valuated) will be done   the price determination of table EBEW.
    As explained in the attached note 180503 when you make transfer  posting with movement type 412 and special stock indicator E into the  sales order stock from the valuated stock the  goods movement is now  valuated with the price of the receiving valuation segment of the   of the sales order stock and not with the price of the issuing valuation segment.
    The difference between the valuation in issuing segment to stock account and the valuation in receiving segment to stock account will be posted to AUM account.

  • Difference between Stock transfer and transfer posting

    I am little confused about the difference between stock transfer and transfer posting. Please clarify
    <<Locked - reason: failed to search before posting question>>
    Edited by: Csaba Szommer on Feb 9, 2011 9:10 AM

    Hello,
    Transfer posting may involve or not involve the physical goods transfer.  In the system you might do transfer posting from quality to unrestricted, or from one store location to another.
    In transfer posting you remove and or replace materials from storage in one storage location and place them in another storage location.
    That transction code you use for transfer posting MB1B with following movement types may be used
    301, 303,305,311,411,309.
    301 is Stock Transfer Between Plants in One Step
    303 & 305 : Stock Transfer Between Plants in Two Steps
    In stock transfer, it always involves physical movement of goods, like transfer between plants under same company code or different company codes.
    Following types are possible with STO's
    Stock Transport Order Without Delivery
    Stock Transport Order with Delivery via Shipping
    Stock Transport Order with Delivery and Billing Document/Invoice
    http://help.sap.com/saphelp_470/helpdata/en/4d/2b90dc43ad11d189410000e829fbbd/content.htm
    Please go through attach SAP document
    BR,
    Tushar

Maybe you are looking for