Outbound idocs

hello all
few months ago I made background job
which use similar transaction to BD87 (rbdmon00)
but someone deleted it
and right now I need to recreate it
... I don't remember code of this transaction...
I need to reread once more all iDocs with status 02
just to sent them.
I can use to do that transaction BD87 \but only manually
to do that in background job I need to use this transaction code which I forgot...
When I've done it our previous abaper give me this transaction code... and I didn't write it down :/
please - anyone have any idea ... ?
Thx

Hi ,
You can use transaction WE02/WE05/WE09 for the same . Just give the input parameters : like status - 02 , the date when you created the Idocs,direction etc. You can retrieve the same .
Regards,
Deepthi

Similar Messages

  • Outbound IDOC process - Using standard  or Custom Program

    Hi all,
    i'm having some doubts regarding IDOC's outbound processing.
    I'm trying to understand 2 scenarios:
    1- Trigger Standard Outbound IDOC without writting any Z program ou IDOC FM.
    It's possible to trigger a outbound idoc for exemple, whenever a sales order is created. To do this is, i suposed i don't need to write any code at all, correct?
    What i need to do is create a logical system (SALE), define Transmission protocol (WE20, in here i associate the partner, and the outbound message type? After this point is the idoc automatic triggered?
    If not, what is the correct procedure?
    2 Trigger Ountbound IDOC using Z program.
    Whats is diferent from the point 1 to this situation?
    Best regards,
    Pedro

    Kali,
    1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
    2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
    3.Again ans is same as in point 1.

  • Is it possible to generate outbound idocs for FI invoices? How?

    Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

    Dear Gabriel
    Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
    As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
    So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP.  However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
    thanks
    G. Lakshmipathi

  • Function Module to Generate Outbound IDOC for Sales Documents

    Hello Experts,
    Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents.  Some of the fm's I have come across are the following:
    IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
    IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
    Points will be given for any help provided.
    Thanks in advance.

    Hi Nagaraj,
    I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order.  For everyone's reference here is the code:
    form process_data.
      DATA v_idoc       TYPE edidc-docnum.
      DATA i_edidd      TYPE TABLE OF edidd.
      DATA wa_idoc_ctrl TYPE edidc.
      LOOP AT i_nast INTO wa_nast.
        CLEAR i_msgs[].
        CALL FUNCTION 'WFMC_PROTOCOL_GET'
          EXPORTING
            cps_nast        = wa_nast
          tables
            messages        = i_msgs
         EXCEPTIONS
           NOT_FOUND       = 1
           OTHERS          = 2.
        LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
    *--- Check first if there is an IDOC
          IF wa_msgs-msgv1 IS INITIAL.
            CONTINUE.
          ENDIF.
          v_idoc = wa_msgs-msgv1.
          CLEAR i_edidd[].
          CLEAR wa_idoc_ctrl.
          CALL FUNCTION 'IDOC_READ_COMPLETELY'
            EXPORTING
              document_number                = v_idoc
            IMPORTING
              IDOC_CONTROL                   = wa_idoc_ctrl
    *         NUMBER_OF_DATA_RECORDS         =
    *         NUMBER_OF_STATUS_RECORDS       =
            TABLES
    *         INT_EDIDS                      =
              INT_EDIDD                      = i_edidd
            EXCEPTIONS
    *         DOCUMENT_NOT_EXIST             = 1
    *         DOCUMENT_NUMBER_INVALID        = 2
              OTHERS                         = 3.
          CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
            EXPORTING
              object                              = wa_nast
              control_record_in                   = wa_idoc_ctrl
    *       IMPORTING
    *         OBJECT_TYPE                         =
    *         CONTROL_RECORD_OUT                  =
            tables
              int_edidd                           = i_edidd
    *       EXCEPTIONS
    *         ERROR_MESSAGE_RECEIVED              = 1
    *         DATA_NOT_RELEVANT_FOR_SENDING       = 2
    *         OTHERS                              = 3
          IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ENDIF.
          COMMIT WORK.
        ENDLOOP.
      ENDLOOP.

  • Automated error email notification when outbound IDOC fails

    Hi,
    The requirement is that whenever the outbound IDOC of message type PAYEXT, basic type PEXR2002, fails, then email has to be trigerred to a group id.
    I had suggested to write a report program that runs as a job. If the IDOC goes to error status then mail will be sent from this report. Client prefers it to be done through workflow.
    There is a standard process code for outbound IDOC failure handling EDIO (we40). standard task 7989 has been assigned to this process code. I dont want to modify this standard task as I am not sure of impact.
    Terminating event for this task is 'ERRORPROCESSCOMPLETD'.
    I have developed the workflow that has trigerring event 'ERRORPROCESSCOMPLETD' and bound with the IDOC number. This will send mail to the group id with the IDOC details
    Now issue is that, I am not sure if standard process EDIO will be trigerred automatically, or should we configure anywhere. Since this is standard outbound IDOC, I am not able to add the process code in partner profile.
    Please give your inputs or any other alternate solution to send mail through workflow when  outbound IDOC fails.
    Thanks in advance.

    Hi,
    I guess in your outbound partner profile for PAYEXT. you need to add process code  EDIO in message control TAb. WHich will cause to trigger the workflow which will send the notification.

  • Outbound IDOC WPDTAX  not getting generated

    Hi
    I am not  able to generate outbound IDOC WPDTAX through WPMA transaction.
    We are using TAXUSJ as the tax procedure.
    Tax Condition type UTXJ and JR1 has been maintained in the system.
    On looking at the code against WPMA ,
    POS_TAX_GET is called to calculate taxes.
    It does not have a fetch against all the condtion tables for tax.
    The above condition has been maintained in table A053.While the above program fetches data against only A003.
    Can somebody help?
    Regards,
    Amit.

    Hi  Amit,
    For TAXUSJ, the conditions maintained are time dependent conditions.
    However , IDoc type WPDTAX01 does not support time dependent conditions.
    Only time independent conditions will be transferred with the help of Idoc type WPDTAX01.
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/3f/81e33bfa5d11d38d1f080009d10d9a/frameset.htm
    Regards,
    Lisa

  • Message type for Scheduling Agreement - Outbound IDoc

    Hi All,
    I have to create an Idoc for Scheduling Agreement through a Z program based on some conditions. I have bit confusion, whether i can use Idoc type for Orders(e.g ORDERS01..05) & Message type ORDERS / ORDCHG to generate Outbound Idoc.
    Already there is process code for for ORDCHG mappig IDOC_OUTPUT_ORDCHG & ORDERS mappig IDOC_OUTPUT_ORDERS.  Whether there will be any impact on this.
    Appreciate your help.
    Regards,
    Anbalagan.

    Hi Anji,
    Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
    But I have to send Outbound Idoc for a Schedule Agreement.
    Whether the same  Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
    Please Advice.
    Regards,
    Anbalagan

  • 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.

  • Consuming an outbound iDoc from a Java Web Dynpro application on EP front

    Hi,
    I am trying to consume an outbound iDoc from a SAP system into a Java Web Dynpro application. The result would be displayed on the Enterprise Portal. Could anyone help me with the process to be followed for the same.
    Regards,
    Chandrima.

    Hi,
    I am trying to consume an outbound iDoc from a SAP system into a Java Web Dynpro application. The result would be displayed on the Enterprise Portal. Could anyone help me with the process to be followed for the same.
    Regards,
    Chandrima.

  • 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

  • How to generate Outbound idoc for Material Reservation

    Hi Experts,
    I want to send outbound IDoc when a material reservation is created with tcode MB21.
    I have been working on this issue and finding the solution in SCN for a week...
    I found some messages similar to this but I could not find out the correct way how to do that.
    At this moment, I configured BD64/WE20 referring the following topic which seems to be feasible solution but could not find any outbound IDocs created, unfortunately.
    Implement ALE_RESERVATION_CREATE
    I appreciate if someone can help me how to create outbound IDoc with MB21 or advice some possibility of missing configuration or steps.
    Best Regards,
    Kenji

    Hi;
    Have been able to find the solution to create the IDoc MRESCR after entering a reservation? 
    I am in the same situation and I do not see the IDoc output in the BD87. 
    It would be nice if you share the solution.
    Thanks in advance

  • Change Business Partner in CRM to trigger OutBound IDOC in R/3 system

    Hi Team,
    I am stuck on a requirement, We have a scenario were the Business Partner is created in CRM system
    which creates a BDOC and is passed to R/3 system through an Inbound IDOC which  triggers the Outbound IDOC to PI system. So far good.
    The scenario we are getting stuck is when a Business partner is changed in CRM an IDOC triggered in R/3 system but this being a change the Change pointers are not called hence the IDOC which is supposed to be triggered for the PI system is not getting triggered.
    Can you please tell me what steps should I take to trigger this Outbound IDOC from R/3 system?
    I did some anlyasis and found a table which COM_BUPA_CALL_FU which contains a set of function module which is triggered in the sequence. Is this the solution or if you have any different do let me know.
    Thanks,
    Imran

    Hi,
    Did you add the entry for your new custom 'Z' long text inPITX Tcode in R3 side. Every long texts in CRM should be linked to R3 long text here. If there is no entry please add one and try changing the text in CRM.
    Hope this helps,
    Karuna.

  • FM to fill outbound IDOC with change document details.

    Hi ,
    I am working on an enhancement EXIT_SAPLMGMU_001 for an interface to track the changes to the material master.
    Can someone please let me know if there is a FM to populate outbound IDOC with change document details like when a material is
    created /changed. Thanks much.
    Regards,
    Sanjeev
    Edited by: sanjeev.s on Apr 14, 2010 3:32 PM

    Call the function module "MASTER_IDOC_DISTRIBUTE" to create idoc.  Use function module "CHANGEDOCUMENT_READ_HEADERS" to get the change document details.
    Regards
    Vinod

  • Purchase Order Outbound Idoc issue. Message Type ORDER

    Hi Experts,
    I am having issue with outbound IDoc generated from Purchase Order.(Message Type ORDER and Basic Type ORDERS05)
    Issue is when i create PO idoc Segment  E1EDP01 and field ACTION populates as 001 this works fine.
    Now when made any changes to the purchase order.* PO trigers one more EDI - Idoc. but the ACTION field is stil as 002.*
    Could any tell me how to fix this.
    Cheers...Gopinath.

    Hi,
    Thank you.
    I have found the issue and fixed.
    Below three setting was missing same has been done in Partner Profile now ok.
    Message type u2013 ORDCHG, Processing Code u2013 ME11 and Change flag On.
    Cheers..Gopinath
    Edited by: Gopinath A.R on Oct 8, 2009 3:14 PM

  • Procedure to Error Out Outbound IDocs

    Hello,
             I have a Requirement in which I am using ORDERS05 IDoc Type and extended it to ZORDER05 to populate Custom Fields and sending the Purchase Order Outbound IDoc to the Vendor from SAP System. Now, my requirement is that if any of the Custom Fields are not maintained in SAP and not populated in the IDoc, I need to Error Out the IDoc with Error Status 26. I am currently working on the SAP ECC 5.0. I have implemented similar Error Handling Mechanism earlier by using Enhancement Framework as I was working in ECC 6.0 environment where I've added the Code by Creating an Enhancement Implementation in the Function Module IDOC_CREATE_ON_DATABASE. But since ECC 5.0 does not have the Enhancement Framework feature,  please let me know how to achieve this.
    Thank You,
    Venkata Phani Prasad K

    Hi
    why don't you try using the standard method for validation of data?
    By implementing the customer-function EXIT_SAPLEINM_002 or BAdI MM_EDI_ORDERS_OUT  you can make checks of completeness of the idoc segments (in your case, additional custom data) and, if they were not complete, report an error message raising the exception DATA_NOT_RELEVANT_FOR_SENDING
    ie
    if <Idoc Custom Field> is initial.
    MESSAGE ID 'S1'
                   TYPE 'E'
                   NUMBER '333'
                   WITH Additional data are incomplete' 
                   RAISING data_not_relevant_for_sending.
    endif.
    Thus you have the evidence of the error in the processing log of the output message while the IDOC is not created.
    The solution works very well and is not invasive.
    Regards.
    Andrea

Maybe you are looking for