Create event Outbound Idoc

Hi Community,
I configured all to send by Nast an outbound idoc DELVRY03 message type DESADV.
Now I wish to know idoc number e its status in order to update custom table about process.
Is there some event (like Created) that I could catch after the idoc is created? Have you any suggestion to solve my trouble?
thanks in advance,
Frank

hi ,
Check in trx <b>WE05</b> for idoc list.
there u can get idocno,status,...
Cheers
ALfred
Reward points for helpful answers.

Similar Messages

  • Error while creating an outbound idoc using idoc type delvry02

    hi,
         i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
    ERROR:
                " SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
    MESSAGE NO: AM053
    Help would be appreciated.
    regards
    leo

    The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
    It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
    Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

  • If output type is missing in PO, can system create a Outbound IDOC for that

    Hi
    Scenario: sales order should get generated in anoter system once PO is saved in first system. But this is not happening for a new vendor. I checked & found that output type is missing in PO. Asked user to provide  another PO for which SO was created. I checked that PO, here also output type is missing.
    I am surprised that if output type is missing in PO, can system create a Outbound IDOC for that PO? If yes then I am not aware of this process.
    Please help me in analyzing this problem.
    Regards
    Sapmm12

    Hi Sridhar,
    Thanks for your replay.
    I checked for other vendor also. condition records does not exist in NACE  for any of them. But user is claiming that sales aorder is getting created for those PO. Though I have asked them to provide the sales order number & possibly outbound IDOC number for at least one vendor.
    I tried to search IDOC number with reference to PO number but system is taking too much time & ending with run ime error. Because I do not have details of partner, receiver not even message type. Neither I have any process document which can explain how this process works?
    any other approach which may work here?
    Regards
    sapmm12

  • Step by step procedure to create an Outbound IDOC's

    Hi,
    Can anyone let me know the steps to create an outbound idoc.
    Regards
    Shiva

    Hi!
    IDOCs:
    - IDOC is an Intermediate Document'. It is simply a data container used to exchange information
    between any two processes that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
    -When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.
    This number is unique with in the client.
    - IDOCs are independent of the sending and receiving systems.
    - IDOCs are independent of the direction of data exchange.
    - In the IDOCs, data is stored in text format.
    - IDOC will wait until the Remote System is Active.
    *IDOC Definition Components
    - Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and
    any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has
    an attribute that defines whether the segment is option or mandatory.
    Minimum/Maximum range for each segment: It defines the maximum and minimum
    number of timesa data record corresponding to a segment cn exist in an IDOC.
    - Segments : A segment defines the format and structure of a data record.
    Segments are reusable componets. A segment consists of various fields that represent data
    in data record.
    IDOC Run time components:
    - A unique IDOC number 16 digits is allocated.
    - One control record is attached to the IDOC.
    - Segments translate into data records.
    - Status records are attached.
    - Sytax rules are checked.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC,
    this information basically includes the IDOC number, sender and receiver information,
    and information such as the message type it represents and the IDOC type.
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40.
    - The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number,
    hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as
    the IDOC achieves different milestones or encounters an error. At every milestone a statu code,
    date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for
    inbound processes.
    Message Type: Identifies what type of information transformed between logical systems or partners.
    Message type is not a local object type , it is transportable.
    Port : A Port defines the medium in which data is exchanged between the two systems in
    the ALE process, IDocs are transferred via memory.
    1. TRFC ports are used for ALE communicaion.
    2. File Ports used by EDI
    3. CPI-C ports used to communicate with R/2 systems.
    4. Internet ports used to connect with Internet Applications.
    5. ABAP-PI ports used to process data via the ABAP programming interface.
    6. XML ports used to process files in XML format.
    Partner Profiles:
    A partner profile has three views, which maintain different parameters for the partner.
    1. The General Parameters View : Values are stored in table EDPP1.
    2. The Outbound Parameters view : Values are stored in table EDP13, except for the
    Message control parameter , which are stored in table EDP12.
    3. The Inbound Parameters View: Values are stored in table EDP21.
    Transaction Codes :
    WE31- Segment Creation
    WE30 - IDOC structure
    WE81 - Message type creation
    WE82 - Link between Message type and IDOC type.
    WE21 - Creation of POrt
    WE20 - Partner Profile creation
    WE19 - Test tool for IDOC Processing.
    SALE - ALE (Application Linking and Enabling) settings
    Go through the link for basics related to IDOCs:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
    Check these links.
    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://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    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
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Check these out..
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    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://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    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://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    Reward Points if it is Useful.
    Regards
    Tamá

  • Create 2 outbound Idocs for 1 message type

    Hi Experts,
    We are sending an outbound Idoc of message type DESADV.  We would like to trigger 2 Idocs per Shipping Notification.
    Could you please help?
    Thanks,
    Vitish.

    Hello Vitish
    Each output partner can have it's own output. Also for the same message type. Maybe the 2 DESADV IDOC's are sent to different partners or destinations. But even when not you still can define 2 different output partners for the message type. Then 2 outputs will be triggered for the same message type.
    Regards Jack 

  • Empty files created when outbound IDOC is wrttien to EDI

    SAP is generating null ORDRSP and DESADV IDOC files. We've checked the individual IDOCs and they appear to be OK however the userdata/PO1/TLEDI/out directory clearly show the null value's. Has anyone encountered this kind of issue?

    Hi all !
    When is configuration XI , I have a error :
    EDI: Partner profile inbound not available
    Message no. E0337
    Diagnosis
    An inbound partner profile could not be found with the following key:
    /IS/LS//CREMAS////
    This involves the key fields of table EDP21:
    -SNDPRN  partner number of sender
    -SNDPRT  partner type of sender
    -SNDPFC  partner function of sender
    -MESTYP  logical message type
    -MESCOD  logical message code
    -MESFCT  logical message function
    -TEST    test flag
    Procedure
    Please check the inbound partner profiles.
    Execute function
    I can't configuration it. Help me, plz !
    Thanks !

  • Recommended Status Codes usage for Inbound & Outbound IDocs

    Hi,
        Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
    I assume we use 51 for Posting Program (not 56) and
    26 for a Z-Selection Program (Not 37 or any other Code).
       Please let me know what is recommended and which status codes most of the people use while Custom Development.
    Thanks and Regards,
    Venkat.

    Hi,
    Outbound IDOC Status Codes
    The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
    Outbound IDOCs
    Code Error Event Severity SAP Meaning
    02 Yes Error Error passing data to port
    03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
    04 Yes Error Control information of EDI subsystem
    05 Yes Error Translation
    06 No Harmless Translation
    07 Yes Error Syntax check
    08 No Harmless Syntax check
    09 Yes Error Interchange handling
    10 No Harmless Interchange handling
    11 Yes Error Dispatch
    12, 13, 14 No Harmless OK
    15 Yes Warning Interchange acknowledgement negative
    16 No Harmless Functional acknowledgement
    17 Yes Warning Functional acknowledgement negative
    18 No Harmless Triggering EDI subsystem
    20 Yes Error Triggering EDI subsystem
    22 No Harmless Dispatch OK, acknowledgement still due
    23 Yes Error Retransmission
    24 No Harmless Control information of EDI subsystem
    25 Yes Warning Processing despite syntax error
    26 Yes Error Syntax check
    27 Yes Error ALE error
    29 Yes Error Error in ALE services
    30 No Harmless Ready for dispatch (ALE)
    31 No Harmless IDOC is marked for deletion
    33 No Harmless Original of an IDOC which was edited
    34 Yes Error Error in control record of IDOC
    36 Yes Error Timeout error; electronic signature not performed
    37 Yes Error IDOC added incorrectly
    38 No Harmless IDOC archived
    39 No Harmless Receive confirmed
    40 Yes Error Application document not created in target system
    41 No Harmless Application document created in target document
    Inbound IDOC Status Codes
    The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
    Inbound IDOCs
    Code Error Event Severity SAP Meaning
    51, 52 Yes Error Posting error
    53 No Harmless Posting successful
    54 Yes Error Error during formal application check
    55 No Harmless Formal application check
    56 Yes Error IDOC with error added
    60 Yes Error Syntax error
    61 Yes Warning Processing despite syntax error
    62 No Harmless IDOC passed to application
    63 Yes Error Error passing IDOC to application
    64 No Harmless IDOC ready to be passed to application
    65 Yes Error ALE error
    68 No Harmless IDOC is marked for deletion
    70 No Harmless Original of an IDOC which was edited
    73 No Harmless IDOC archived
    Regards,
    Raj.

  • Creation of Inbound Idoc for the Outbound Idoc in same client

    Hi,
    My requirement:
    Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
    It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
    I found there is a field for function module in WE21,can this be used to get the requirement done.
    Please suggest.
    Regards,
    Amar

    Example of a program that create and post an inbound idoc....maybe that will help you:
    report  zzinbound_idoc.
    data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
    data: g_edidd like edi_dd40 occurs 0 with header line.
    data: g_e1bpache09 like e1bpache09.
    parameter: mode type c default 'A'.
    refresh: g_idoc_control_record, g_edidd.
    clear:   g_idoc_control_record, g_edidd.
    *-Build Control Record -*
    g_idoc_control_record-mestyp  = 'ACC_DOCUMENT'.   "Message type
    g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
    g_idoc_control_record-direct  = '2'.              "Direction
    * Receiver
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
        g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-rcvprt = 'LS'.             "Partner type
    g_idoc_control_record-rcvpfc = ''.               "Partner function
    * Sender
    g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-sndprt = 'LS'.             "Partner type
    g_idoc_control_record-sndpfc = ''.               "Partner function
    g_idoc_control_record-refmes = 'Customer clearing'.
    append g_idoc_control_record.
    *-Build Idoc Segments -*
    *---E1KOMG
    clear g_edidd.
    clear g_e1bpache09.
    g_edidd-segnam               = 'E1BPACHE09'.
    g_edidd-segnum               = 1.
    move g_e1bpache09 to g_edidd-sdata.
    append g_edidd.
    *-Create idoc -*
    *-Syncronous
    if mode = 'S'.
      call function 'IDOC_INBOUND_SINGLE'
        exporting
          pi_idoc_control_rec_40              = g_idoc_control_record
    *     PI_DO_COMMIT                        = 'X'
    *   IMPORTING
    *     PE_IDOC_NUMBER                      =
    *     PE_ERROR_PRIOR_TO_APPLICATION       =
        tables
          pt_idoc_data_records_40             = g_edidd
        exceptions
          idoc_not_saved                      = 1
          others                              = 2.
      if sy-subrc <> 0.
        message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      endif.
    *-Asynchronus
    else.
      call function 'IDOC_INBOUND_ASYNCHRONOUS'
        in background task as separate unit
        tables
          idoc_control_rec_40 = g_idoc_control_record
          idoc_data_rec_40    = g_edidd.
      commit work.
    endif.
    write: / 'Well done!'.

  • Duplicate Outbound IDocs getting Triggered at the same time.

    Hi Folks,
    I have created custom outbound idoc and done all the configurations required like WE20, WE30, WE31, WE81, WE82, WE 41, WE57 etc.
    Also I have written my code to populate segments and then call MASTER_IDOC_DISTRIBUTE in the custom function module which is assigned to the process code and also done the configurations like we57 etc. for the same.
    Now when I trigger my output type from VL74 transaction, I noticed two entries in we02 resulting in two IDocs generated for 1 HU.
    The difference in two IDocs is the first IDoc getting generated in error with status 29. While the second one as success with status 03.
    The data records containing segments have same values for both the IDocs number.
    Whether the configuration is a issue here or problem in code of custom fm?
    Please help.

    Hi Anil,
    Appreciate your quick response.
    In my custom FM I have populated an internal table it_master_idoc_data with two records of two segments, containing segment name in SEGNAM filed and segment data in SDATA field. 
    Please let me know whether the data in this internal table of structure EDIDD sufficient for passing to MASTER_IDOC_DISTRIBUTE FM? Or do I need to populate any other field of EDIDD.
    Also I am exporting a structure master_idoc_control containing values in this 5 fields.
    MESTYP = Z message type, Z IDOCTP, partner and details in  RCVPOR, RCVPRN, RCVPRT fields.
    I am not populating the internal table communication_idoc_control while calling FM MASTER_IDOC_DISTRIBUTE from my custom function module.
    After executing MASTER_IDOC_DISTRIBUTE FM, when the control comes back to my custom FM there is one record in communication_idoc_control  internal table with IDoc number in DOCNUM field with status 29(error). Now when we check in WE02 there are two IDocs generated after this transaction's execution.
    The first one in error which FM MASTER_IDOC_DISTRIBUTE returns and second one in success with status 03.
    Please help....
    Thanks,
    Pravesh

  • Post inbound as well as outbound IDOCs through a report

    Hi all,
            I have a specific requirement where i need to post an IDOC through a report which ressemble to WE05. This requirement implies for Inbound as well as Outbound for all message types. Can anyone let me know how can this be achieved. Please let me know if this can be acheived through any FM or method.
    Regards
    Simin.R

    Hi,
    To create a new inbound idoc use the following function module:
    IDOC_INBOUND_SYNCHRONOUS
    To Create a outbound idoc use the function module
    MASTERIDOC_CREATE_* - search and decide based on your requirement.
    Regards,
    Baburaj

  • Good Movement Outbound Idoc

    Hi ,
    We have to transmit Goods movement idoc to our partner.Since i couldn't find any standard outgoing idoc for material document posting.
    Therefore we are considering below two approaches to get it done
    Solution 1
    We will use the user exit / customer exit like MB_CF001 available at material document posting to call FMs which will populate edidc & edidd of idoc type WMMBID02 (WMMBXY message type). We will updated NAST with our hard coded output types like ZABC.As soon as the the output type gets processed the message will be transmitted to partner.(For this output type we are planning to configure despatch time as IMMEDIALTELY therefore i believe message will get transmitted as soon as material document is posted.)
    But we can see few challenges in this
    1) Which program and routines we have to attach with output types ?
    2) In NAST along with output type we also have to update , material document number. How to get it before posting a document ?
    Solution 2
    We will use the user exit / customer exit like MB_CF001 available at material document posting.Using this exit we create a XML file with field and place into a disred directory. XI people will do the rest work for us.
    Need you advice on the feasible solution of two and which is more cost / effort effective 
    regards
    Shrey

    Hello,
    I've looked into WMMBID02 IDOC with Message type WMMBXY, and looked further into idoc documentation.  It is used for inbound GR transactions.  Below is what I intent to do.  We issue a PO to vendor via edi, vendor ships goods to us, and using MIGO, goods receipt transaction is performed.  What I intent to do is to create an outbound idoc when MIGO is performed, so that I can let the vendor know that we received the goods.
    Thanks,
    S

  • How to generate an outbound IDOC for customer Invoice

    Hi
    I want to configure that if I create a invoice using TCODE FB70 it should automatically create a outbound IDOC ACC_BILLING( for customer).How I can achieve this. Can any one give me complete step by step help.
    thanks in advance.
    karunb

    You should be able to use it using 'change pointers'.
    For this you will first need to activate change pointer for this message type (check SALE > modelling..>Master data distribution). Next, you will need to setup your ALE config for this IDOC/message type.
    In ALE, you will be able to either run a standard SAP report adhoc, or schedule it such that all changes recorded using change pointer (changes including new customerr records) are collected as IDOCs and sent.
    This is a standard SAP scenario, you only need to do the config/setup to get there. You may wish to read more on change pointers to understand this.
    cheers,

  • Outbound idoc when good receipt is performed

    Hi Gurus,
    I've been trying to create an outbound idoc as good receipt is performed in 46c.  I've looked into MBGMCR and STPPOD message types and they don't work.  I did some configuration so that I could manually create an outbound file going into MB02 tcode.  Your expert instructions to creating an outbound idoc when good receipt is done is greatly appreciated.
    Thanks,
    S.

    Hello,
    I've looked into WMMBID02 IDOC with Message type WMMBXY, and looked further into idoc documentation.  It is used for inbound GR transactions.  Below is what I intent to do.  We issue a PO to vendor via edi, vendor ships goods to us, and using MIGO, goods receipt transaction is performed.  What I intent to do is to create an outbound idoc when MIGO is performed, so that I can let the vendor know that we received the goods.
    Thanks,
    S

  • Outbound Idoc from FI Customer Invoice

    Hello,
    Does anyone know if it is possible to create an outbound Idoc originating from an FI Invoice for a customer?  Specifically, we are trying to do this for an interest invoice.  I would think that we might be able to create a correspondence type that would do this, however I am unable to find any documentation on this functionality.
    Thanks,
    Mark

    Hello,
    For the texts you can try a subsutition, specifically the exit program or use a BTE via the FIBF transaction.
    Mark as helpful.
    Regards
    Waza

  • Outbound idoc has data from previous idoc as well

    Hi Experts
    I am doing the goods receipt against a scheduling agreement using idocs. If this goods receipt is succesful, I am triggering an outbound idoc informing the WMS of the goods receipt. For example, if idoc number 1 comes in for GR , code has been mentioned in the inbound function module for trigger of an outbound idoc A. Please note that the difference that this isnt the case of an output type.
    Now the problem that arises is , the idoc data for outbound idocs is being accumulated and sent. For example, if 1 is the GR idoc, A is the outbound idoc, then 2 is the 2nd GR idoc, then AB is the data coming  2nd outbound idoc (instead of just B), then 3 is the 3rd GR idoc, then ABC is the data coming  for 3rd outbound idoc(instead of just C)
    I am a little confused about the same as to which area this pertains to and would really appreciate quick help on the same.
    Regards
    Shubhankar

    Hi,
    How are you testing this functionality ? Is it using WE19 test transaction or ??
    If that is the case then please come out of transaction everytime you process the idoc.
    Also, clarify your scenario in more detail.
    Processing of your single inbound idoc creates more than one outbound idocs or
    for every inbound idoc which is processed you are creating one outbound idoc in user exit.
    Also check if the idocdata internal table is refreshed once an outbound idoc is created.
    If possible please send your code.
    KR Jaideep,

Maybe you are looking for