Material Document in IDOC.

Hi,
Can i find the Material Document number in IDOC display mode? I can find the Qty, Posting Date... Etc., but i could not find the material document in  IDOC in any of the Segment of message type: MBGMCR01.
Regards,
Kumar

Thanx

Similar Messages

  • How can we find the Idoc number which posts the material document in SAP

    Hi All,
    How can we find the Idoc number which posts the material document in SAP. We could not able to find the IDOC number from the material document which was posted by Idoc.
    Thanks
    Chandru

    Hi,
    In MIGO you can go to service of object(Just above show overview) and check 5th option workflow you will find the idoc number.
    regards
    suresh

  • IDOC message type WMMBXY not including Serial numbers in GR material documents when created with reference to an Inbound delivery

    Hello,
    We currently have an inbound ALE process (message type WMMBXY and basic type WMMBID02) to post GR's against inbound delivery. If the inbound delivery item is maintained with serial numbers, we want those serial numbers to be pulled into the goods movement material document (and stored in SER03).
    Currently segment E1MBXYJ is maintained with the inbound delivery number in field VLIEF_AVIS and Inbound delivery item number in field
    VBELP_AVIS. In segment E1MBXYI, no purchase order is assigned and the fields EBELN and EBELP are blank. The movement indicator (KZBEW) has the value 'B'.
    Even after making the above settings, the serial number(s) maintained on the Inbound delivery item do not get saved to the material document.I did look at OSS note 833603 (Solution for 2 - GR for Inbound delivery) and we have followed the same settings. This works when there is no serial number in the Inbound delivery. However if we have serial numbers, the IDOC posts successfully, however the material documents in MB03 do not have any serial numbers copied over from the Inbound delivery where the serial numbers are definitely assigned.
    Any help you can provide is greatly appreciated!
    Thanks,
    Ashvin
    P.S
    If we manually create the GR via MIGO, the serial numbers are automatically applied to the GR material document. This is what we want to accomplish via the above IDoc process.

    Hi
    Try with enhancement MWMIDO08. See note 833603 - EDI: Goods receipt for stock transport order for further information.
    I hope this helps you
    Regards
    Eduardo

  • Finding the idoc number for material document

    Hi,
    I have a material document which was created by an idoc. How do I know the idoc number that has created this material doc?
    We have lots of idocs coming from external systems which do GI, GR, transfer postings etc. With the material document , not able to trace which idoc created it.
    Regards

    Hi Ramees,
    "Refer the Tables MKPF / MSEG inorder to get the IDOC no's for Material Docs. "
    But how can it be found for Transfer posting documents where no PO history exist !!
    Alex.

  • Inbound Idoc for material document cancellation

    Hello,
    Could you update me whether there is any Inbound Idoc type available for material document cancellation (like t.code MBST).  I found message type MGBMCR, but it's only allowing me to create the material document like GRs but not cancellations.
    /Mallik

    To my knowledge, there is no such IDoc. Cancellation is an exceptional situation and should be treated as such. If one needs an IDoc interface for cancellations, I'd have to say there is something very wrong with the business process.

  • Need an IDOC EDI STEPS for material document(MB03)

    HI ALL,
    i need an IDOC for material document. For example, user in SAP make material document (t-code MIGO or MB11), then automatical is downloading outbound IDOC, which contain information about material document.HOW TO PROCESS IT THROUGH EDI .GIVE THE STEPS.

    like below you can do your settings
    The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
    1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
    2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
    3. After that, assign the IDoc Type to Message Type in WE82.
    4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
    5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
    6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
    7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
    8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
    i. In Message Control Configuration, we'll maintain
    a. Condition Tables
    b. Access Sequences
    c. Output Types
    ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
    iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
    Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
    For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
    However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.

  • Status 51 material document data and po data do not match(vendor)

    i am using we19 to try an inbound idoc mbgmcr(receipt for po)
    i put in gm_code 01
    movement indicator B(goods receipt for po)
    vendor 3815
    PO 4500015241
    PO Order Item 00030
    Movement type 101
    qty in unit of entry  1
    iso code unit of measurement pc
    on the po screen i see the po item and qty to be delivered is 75
    when i run the inbound idoc i get
    status 51 material document data and po data do not match(vendor) but as i say on the po inquiry screen i see the po vendor item with 75 to be delivered
    what am i missing????????????????

    thank you
    i put in the leading zeros and got rid of that problem
    now i am getting status 51
    posting only possible in 2004/07 and 2004/06
    but in the posting date i use 07/02/2004  i have tried several dates in the period but get the same error
    any ideas?
    thanks you

  • User-Exit - MIGO How to get the Number of Material Document

    Hi everyone!!
    I'm looking for an user-exit after saving in MIGO transaction. I need the Number of Material Document (MKPF-MBLNR) to generate an IDOC.
    Does anybody knows an user-exit to get this number?
    Regards,
    Rubens Kumori
    Edited by: Rubens  Kumori on Oct 20, 2008 3:26 PM

    In BADI definition [MB_DOCUMENT_BADI|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=mb_document_badi&adv=false&sortby=cm_rnd_rankvalue], you may use interfaces [MB_DOCUMENT_BEFORE_UPDATE|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=mb_document_badiMB_DOCUMENT_BEFORE_UPDATE&adv=false&sortby=cm_rnd_rankvalue] (before update task) and [MB_DOCUMENT_UPDATE|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=mb_document_badiMB_DOCUMENT_UPDATE&adv=false&sortby=cm_rnd_rankvalue] (in update task)
    Regards

  • Insering Material document number which is created while posting MBGMCR02

    Hello Friends ,
    i have a requiremnt to insert the material document(mblnr) which is created while by  posting  the MBGMCR02 inbound idoc for
    post goods issue .the requirement is to insert the MBLNR at weo5/we02 at status records.
    message type MBGMCR .
    For example the system will show the status message as 53 if idoc is created successfully and below that the 'message : BAPI EXECUTED SUCCESSFULLY its showing , instead of this message i wanted to show the new MBLNR number there .'
    please help me by giving good suggestions.
    thanks Advance
    Anant

    Is there any standard Function Module to find out FI Document number using Material Document number?
    let me know is there any Function module available to identify these Material Document number or FI Document number?
    Is there any standard Function Module to find out all the details ( such as Invoice date, vendor, amout, tax amount , payment due date, payment terms , approver)  using invoice document number.

  • IS-Retail POSDM- double posting of  material documents and billing document

    Hello All,
    I had initially posted this question in "Industries Solution General" forum. Reposting it in the appropriate forum-
    We have a nightly job for program "RWPOS_PARA_ENQUEUE" which processes all WPUBON idocs (sales info) that comes in from POSDM. Sometimes we have noticed that for one idoc 2 material documents and 2 billing documents are being created with the same information.
    Note that this happens sporadically and we have no idea why or when it can happen. Also, we have duplicate checks in POSDM and this happens only when the idoc flows into ECC from POSDM i.e. one sales idoc posts 2 sets of documents for no apparent reason. Is there any way to prevent this? Why is this happening? Your inputs will be really appreciated.
    Thanks,
    Smitha

    hi,
    Just go to FB03 click enter and then
    Company code
    Fiscal Year
    Ledger
    Document type against customer invoice DR and then if u hav an idea abt the customer invoice doc then give doc number ....other excute and search for the customer no....
    And then double click on the document
    then goto ENVIRONMENT -
    > Document over view -
    > relation ship brower click
    then you can see all the relating document to that account  i.e account doc,profitcenter doc ,material ,oytbond delivery doc ,billing doc etc...
    if useful assign points.....
    regards,
    santosh kumar

  • BD20, Duplicate material document (BD20)

    hi guys,
    We have a IDOC number status 64 generated with barcode and quantity details(POS data) in the segments through custom programs.. when we run BD20 to post the IDOC into application then the IDOC status changes to 53 and material document and Billing document is generated ( we can check in WPER)..
    but sometimes for a single IDOC we can see multiple Material documents and billing documents where the data (articles) in both the material documents are SAME..
    Can some one through light on this issue plz..
    reg,
    nazeer

    Hi Nazeer,
    Is this problem come when due to some reason IDOC stuck and then reprocess .
    or one shot posting .. and who much number of segment in one IDOC
    you can use RWPOS_PARA_ENQUEUE in palce of BD20
    Regards,
    Amit Shivhare

  • Duplicate material document created BD20 (POS)

    hi guys,
    We have a IDOC number status 64 generated with barcode and quantity details (POS data) in the segments through custom programs.. when we run BD20 to post the IDOC into application then the IDOC status changes to 53 and material document and Billing document is generated ( we can check in WPER)..
    but sometimes for a single IDOC we can see multiple Material documents and billing documents where the data (articles) in both the material documents are SAME..
    Can some one through light on this issue plz...
    regards,
    nazeer

    Hi Nazeer,
    Its very much possible that multiple IDOCs get generated for the same material it depends how frequently your BD20 program is scheduled, What parameters are passed to BD20. Another possibility is that same IDOC may get generated with change pointer program RBDMIDOC.
    Do you sense any Negetive impact of having the Duplicate IDOCs. I guess you just need to Ignore it.
    Regards
    Shital

  • User exit for material document.

    Hi,
    does any one know and user exit or BADi which gets triggered when ever a material document is posted  ( Saved) in to the system and is irrespective of transaction used.  we want to send the updated stock information and their status to a third party system when ever there is a material document posted via an IDoc.

    Try BAdI [MB_DOCUMENT_BADI|http://www.sdn.sap.com/irj/scn/advancedsearch?query=mb_document_badi], method [IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_UPDATE|http://www.sdn.sap.com/irj/scn/advancedsearch?query=mb_document_badi+mb_document_update]
    Regards,
    Raymond

  • Transaction document for Idoc type

    Hi Experts,
    I am seeking little information about below Idoc type from POS to SAP IS Retail,
    I would like to know that, what are the transaction documents generated in SAP IS Retail after executing of below inbound idoc type.
    For example WPUUMS – It will create billing document for aggregate sales and material document for Goods movement.
    Similarly, please help me for below Idoc type.
    ·         WPUBON
    ·         WPUTAB
    ·         WPUBWB
    ·         WPUFIB
    ·         WPUKSR

    Hi Vanrajsinh,
    I'd recommend you to go through the help.sap.com POS Inbound Interface for general information;
    POS Interface - Inbound @ help.sap.com
    and then crawl through related customizing in SPRO: Sales & Distribution > POS Interface > Inbound where you'll find the document types corresponding to individual IDoc types and IMG documentation per activity is also quite 'explicit'.
    Not to leave you only with links, more information below but document types generated depend on the above config;
    WPUBON - POS interface: Upload sales docs (receipts) non-aggregated;
    Usually creates billing document and article document to post sales and goods issue per receipt, billing type and movement types can be defined in SPRO POS as above > Control Sales per receipt
    WPUFIB - POS Interface: Upload Financial Accounting Interface SRS/POS
    creates only FI posting (accounting documents) for pre-defined POS financial transactions; SPRO POS as above > Transaction Types for Financial Transactions and Trans.Type  Cotrol of Fin.Trans.
    WPUKSR - POS Upload Cashier Data
    Cashier statistics, I've only used it for statistics (RIS, no transaction documents created)
    WPUTAB - POS interface: Upload day-end closing POS / Payment List
    Creates billing document to post payment per payment type if not already posted via receipts, SPRO POS as above > Payment List Control
    WPUUMS - POS interface: Upload sales data (compressed)
    as WPUBON but aggregated sales, SPRO POS as above > Aggregated Sales Control
    WPUWBW - POS interface: Upload goods movements
    Creates article documents to post goods movements
    Note that you usually do not use all IDoc types at the same time as this would lead e.g. to posting a single receipt via multiple flows.
    Hope this helps!
    Regards,
    Tomas

  • MATERIAL ON ALE IDOCS

    HI CAN ANYONE GIVE ME THE MATERIAL ON ALE IDOCS......NOT JUST THE BASIC MATERIAL........I WAANT THE IN DEPTH MATERIAL...........THANKS.

    HI,
    There are basically two types of IDOCs.
    Basic IDOCs
    Extended IDOCs
    Idoc Components
    Basic Idoc
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extension Idoc
    Extending the functionality by adding more segments to existing Basic IDOCs.
    Creation of IDoc
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Create IDOC Type
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    u can also check all these links related to idocs
    http://www.allsaplinks.com/idoc_sample.html
    http://www.allsaplinks.com/
    http://www.sap-img.com/
    http://www.sappoint.com/abap.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
    Regards,
    Laxmi.

Maybe you are looking for