Master_idoc_distribute

Hi Experts,
Can we pass multiple Partner Number of Recipient in the Master idoc control record ie in RCVPRN field in one shot. and pass it into the FM  Master_idoc_distribute.
Plz suggest
Regards
Santosh

Hi,
No it is not possible. There is always only one control record per idoc.
If you look at the parameter of FM master_idoc_distribute, you will see that "MASTER_IDOC_CONTROL" is import parameter and it is not define as table parameter.
Let me know if you have any question.
Regards,
RS

Similar Messages

  • Is the MASTER_IDOC_DISTRIBUTE FM called even without a Custo Distri. Model.

    Hi all
    In have a question dealing with ALE.
    I am trying to send a BOM Change and create IDoc to a XI system.
    My question is :
    Is the MASTER_IDOC_DISTRIBUTE FM called even without a Customer Distribution Model?
    Or to test my scenario do I HAVE to create a CDM, using BD64.
    Please advise.
    specific answers will be appriciated.

    Hi,
    It is required to create a model view..otherwise who is distributing the message to whom can't be rocognised..Hence it is required..
    check the sample code ..
    *& Report ZZ_Program_To_Create_Idoc
    report zz_program_to_create_idoc .
    tables: ekko,ekpo.
    selection-screen skip 3.
    selection-screen begin of block b1 with frame title titl.
    selection-screen skip.
    select-options s_ebeln for ekko-ebeln.
    selection-screen skip.
    selection-screen end of block b1.
    data: header_segment_name like edidd-segnam value 'Z1EKKO',
    item_segment_name like edidd-segnam value 'Z1EKPO',
    idoc_name like edidc-idoctp value 'Z19838IDOC1'.
    data: header_segment_data like z1ekko,
    item_segment_data like z1ekpo.
    data: control_record like edidc.
    data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
    data: i_communication like edidc occurs 0 with header line,
    i_data like edidd occurs 0 with header line.
    data: begin of i_ekko occurs 0,
    ebeln like ekko-ebeln,
    aedat like ekko-aedat,
    bukrs like ekko-bukrs,
    bsart like ekko-bsart,
    lifnr like ekko-lifnr,
    end of i_ekko.
    data: begin of i_ekpo occurs 0,
    ebelp like ekpo-ebelp,
    matnr like ekpo-matnr,
    menge like ekpo-menge,
    meins like ekpo-meins,
    netpr like ekpo-netpr,
    end of i_ekpo.
    start-of-selection.
    select ebeln aedat bukrs bsart lifnr from ekko
    into table i_ekko where ebeln in s_ebeln.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln in s_ebeln.
    control_record-mestyp = messagetyp.
    control_record-rcvprt = 'LS'.
    control_record-idoctp = idoc_name.
    control_record-rcvprn = '0MART800'.
    loop at i_ekko.
    header_segment_data-ebeln = i_ekko-ebeln.
    header_segment_data-aedat = i_ekko-aedat.
    header_segment_data-bukrs = i_ekko-bukrs.
    header_segment_data-bsart = i_ekko-bsart.
    header_segment_data-lifnr = i_ekko-lifnr.
    i_data-segnam = header_segment_name.
    i_data-sdata = header_segment_data.
    append i_data.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln = i_ekko-ebeln.
    loop at i_ekpo.
    item_segment_data-ebelp = i_ekpo-ebelp.
    item_segment_data-matnr = i_ekpo-matnr.
    item_segment_data-menge = i_ekpo-menge.
    item_segment_data-meins = i_ekpo-meins.
    item_segment_data-netpr = i_ekpo-netpr.
    i_data-segnam = item_segment_name.
    i_data-sdata = item_segment_data.
    append i_data.
    endloop.
    clear i_ekpo.
    refresh i_ekpo.
    endloop.
    call function 'MASTER_IDOC_DISTRIBUTE'
    exporting
    master_idoc_control = control_record
    OBJ_TYPE = ''
    CHNUM = ''
    tables
    communication_idoc_control = i_communication
    master_idoc_data = i_data
    exceptions
    error_in_idoc_control = 1
    error_writing_idoc_status = 2
    error_in_idoc_data = 3
    sending_logical_system_unknown = 4
    others = 5
    if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
    with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    else.
    loop at i_communication.
    write: 'IDOC GENERATED', i_communication-docnum.
    endloop.
    commit work.
    endif.
    initialization.
    titl = 'ENTER THE PURCHASE ORDER NUMBER'.
    reward  if helpful
    Regards,
    Nagaraj

  • IDOC in yellow state after MASTER_IDOC_DISTRIBUTE

    Hello,
    I am sending idocs using MASTER_IDOC_Distribute to the target. In the partner profile, I have checked process idocs immediately.
    After the function call, there is commit work command.
    I like to process idocs immediately.
    Most of the time the idocs are in yellow state, and require BD87 to process idocs. I checked several tips in SDN and unable to resolve it.
    Thank you for the help
    Regards
    William

    Hi William,
    The below links might be helpful for your problem:
    [Call of master_idoc_distribute|http://help.sap.com/saphelp_nw04/helpdata/en/78/21783151ce11d189570000e829fbbd/frameset.htm]
    [Re: Use of MASTER_IDOC_DISTRIBUTE|Re: Use of MASTER_IDOC_DISTRIBUTE]
    Regards
    Bhanu
    Intelligroup.
    Edited by: Bhanu Tiruveedula on May 13, 2008 8:10 PM

  • Typical problem with MASTER_IDOC_DISTRIBUTE

    I have written the custom program to fetch the data and to form an outbound IDoc using MASTER_IDOC_DISTRIBUTE.
    The problem is when i execute the pgm 1st time the IDoc got generated. As it was in Yellow state i tried to execute the program RSEOUT00. Even then it was in yellow state.
    Now again i ran the custom program and create danother IDoc. Even now this IDoc is also in Yellow state. But now when i ran RSEOUT00 program with these two IDoc numbers, now the 1st one got into green while the 2nd remained in Yellow.
    Now my Questions are
    1. First of all why it was in yellow color when i ran the program first time even though when i set "Trigger immediately " at partner profiles.
    2. Why the first one is going into green state when the second idoc got generated ?

    HI Friends,
    i have solved the issue by myself.
    I have just used the FM EDI_DOCUMENT_DEQUEUE_LATER before commit wok statement.
    Can any one explain me the reason why it worked out ?

  • Function Module MASTER_IDOC_DISTRIBUTE to be called in background task?

    Hi,
    We are generating outbound Idocs in a report. In this report we are using Function Module Master_Idoc_Distribute. Now we have faced some performance issues and the basis consultant is asking us to:
    Call the function module using CALL FUNCTION Master_Idoc_Distribute IN BACKGROUND TASK.
    1) How will calling the FM Master_IDOC_Distribute in background task help improve the performance?
    2) By calling the function module in background task, will it have any impact on the sequencing of the idocs? If yes what is the way out, as the idoc sequence is very important.
    Thanks in advance,
    Mick

    1) How will calling the FM Master_IDOC_Distribute in background task help improve the performance?
    ->Calling the FM in background task will help in performance as it will be called in the background process mode like a tRFC.So it will not occupy any dialog process which are limited.
    2) By calling the function module in background task, will it have any impact on the sequencing of the idocs? If yes what is the way out, as the idoc sequence is very important.
    ->It will not have any impact on IDoc sequence.

  • To get IDOC number when running MASTER_IDOC_DISTRIBUTE in update task.

    Hi ,
    I am running 'MASTER_IDOC_DISTRIBUTE' Func Module for creating FIDCC2 message type IDOC in UPDATE TASK. I am not getting IDOC number of the created IDOC in this case.
    Can anyone pls update me how do I get it?
    Thanks,
    Prabhu
    Note: Useful answers will be rewarded.........

    I found the resolution....
    Thanks all.

  • What is the concept behind MASTER_IDOC_DISTRIBUTE

    What is the concept behind MASTER_IDOC_DISTRIBUTE ?

    Hi Manjunath,
    Please check the Documentation of the Function Module in SE37
    This function module is the interface from the application to the ALE layer on the outbound side. The application can pass an IDoc, the so-called master IDoc, as an internal table using the parameters MASTER_IDOC_CONTROL and MASTER_IDOC_DATA.
    This IDoc is then converted into one or communcation IDocs and stored in the ALE layer. IDocs for which no errors occurred are passed to dispatch control.
    In the table parameter  COMMUNICATION_IDOC_CONTROL the header records for the communication IDocs created are retturned. You can tell whether processing was successful from the field STATUS.
    A COMMIT WORK must be dispatched in the calling program, otherwise the IDocs may not be dispatched.
    Best regards,
    raam

  • Problem with FM 'MASTER_IDOC_DISTRIBUTE'

    Hello,
    I am wirtting a FM that will create IDoc of type OILORD (Sales Order).
    I am using 'MASTER_IDOC_DISCTRIBUTE' fm to do so.
    Now my problem is the IDoc gets created but is in status '30'.
    In my partner profile i have ticked on trigger imm.
    also when i create a sales order through VA01 it is creating the IDoc and the status of that idoc is '03'. mind you its the same idoc. of type OILORD and even they have used same FM i.e. MASTER_IDOC_DITRIBUTE'
    also after calling FM MASTER_IDOC_DITRIBUTE' in my FM i am checking for sy-subrc and when sy-subrc is 0 i call commit work.
    I need to create the IDoc ( with status '03') through my FM only..
    I am aware that by executing program RSEOUT00 or via Tcode we14 or BD87  I can process the IDoc with status 30 and change the status to 03 .. i did try using submit stmt and submit the idoc number that is returned by the 'communication_idoc_control'  to program RSEOUT00 but it didnt help...
    in fact when i call the RSEOUT00 program externally and execute it with the idoc number it does change the status of the IDOC from 30 to 03 but if i do the same via my FM it doesnt do any thing ..
    so can any one help me with this..
    thank you.

    Hi
    Just go through the following code for creating idoc:
    REPORT  ZALE_USR.
    CONSTANTS:   C_DOCTYP TYPE EDIDC-IDOCTP VALUE 'ZUSRDET01',
                 C_SEGNAM TYPE EDIDD-SEGNAM VALUE 'Z1USRDET01',
                 C_MESTYP TYPE EDIDC-MESTYP VALUE 'ZUSRDET'.
      DATA:      IT_ZUSR02 TYPE USR02 OCCURS 10,
                 IT_EDIDC TYPE EDIDC OCCURS 0,
                 IT_EDIDD TYPE EDIDD OCCURS 0,
                 WA_ZUSR02 TYPE USR02,
                 WA_EDIDC TYPE EDIDC,
                 WA_EDIDD TYPE EDIDD,
                 WA_Z1USRDET01 TYPE Z1USRDET01,
                 V_OCCMAX TYPE IDOCSYN-OCCMAX,
                 V_NBSEG TYPE I.
                CLEAR WA_ZUSR02.
                CLEAR WA_EDIDC.
                Save the message type and the basic IDoc type in the control segment.
                MOVE C_MESTYP TO WA_EDIDC-MESTYP.
                MOVE C_DOCTYP TO WA_EDIDC-IDOCTP.
                Retrieve the maximum number of segments in the basic IDoc type.
                SELECT MIN( OCCMAX )  FROM IDOCSYN  INTO V_OCCMAX  WHERE IDOCTYP EQ C_DOCTYP AND SEGTYP EQ C_SEGNAM.
                Save the whole USR02 table content in the IT_ZUSR02 internal table.
                SELECT * FROM USR02 INTO CORRESPONDING FIELDS OF TABLE IT_ZUSR02.
                Create a data segment for each line of IT_ZUSR02.
                LOOP AT IT_ZUSR02 INTO WA_ZUSR02 .
                  MOVE-CORRESPONDING WA_ZUSR02  TO WA_Z1USRDET01.
                  CLEAR WA_EDIDD.
                  MOVE C_SEGNAM TO WA_EDIDD-SEGNAM.
                  MOVE WA_Z1USRDET01 TO WA_EDIDD-SDATA.
                  APPEND WA_EDIDD TO IT_EDIDD.
                  CLEAR WA_ZUSR02.
                 CLEAR WA_Z1USRDET01.
                ENDLOOP.
               Count the number of data segments.
                  DESCRIBE TABLE IT_EDIDD LINES V_NBSEG.
               If the number of data segments exceeds the maximum allowed number,then display an error message.
                  IF V_NBSEG GT V_OCCMAX.
                  WRITE:/ 'ERROR'.
                  ENDIF.
                  CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
                    EXPORTING
                      master_idoc_control                  = WA_EDIDC
                    OBJ_TYPE                             = ''
                    CHNUM                                = ''
                    tables
                      communication_idoc_control           = IT_EDIDC
                      master_idoc_data                     = IT_EDIDD
                   EXCEPTIONS
                     ERROR_IN_IDOC_CONTROL                = 1
                     ERROR_WRITING_IDOC_STATUS            = 2
                     ERROR_IN_IDOC_DATA                   = 3
                     SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4
                     OTHERS                               = 5
                  IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
                  ENDIF.
    execute the program, then run bd87. i think it will solve your problem
    <b>Reward points for helpful ans</b>
    Regards
    Aarti

  • Question on using FM  'MASTER_IDOC_DISTRIBUTE'

    Hi guys,
    I am always recieving an excemption = 2 (error_writing_idoc_status) when using 'MASTER_IDOC_DISTRIBUTE', what would be the problem with my code? thanks in advance!
    Regards,
    Mike

    HI,
    Ur report should be this format.
    *& Report  z_idoc_demo                                                 *
    *&  1. Create a Segment in WE31                                        *
    *&  2. Create an Idoc type in WE30.                                    *
    *&  3. Create a Message Class in WE81.                                 *
    *&  4. Assign Message Type to Idoc Type in WE82.                       *
    *&  5. Create a Port in WE21.                                          *
    *&  6. Create a Partner profile in WE20.                               *
    REPORT  z_idoc_demo.
    TYPES : BEGIN OF tw_mara,
            matnr TYPE matnr,
            mtart TYPE mtart,
            meins TYPE meins,
            ntgew TYPE ntgew,
            END OF tw_mara,
            tt_mara TYPE STANDARD TABLE OF tw_mara.
    DATA: gf_so_matnr TYPE matnr.
    SELECT-OPTIONS: so_matnr FOR gf_so_matnr.
    DATA: lt_edidc TYPE edidc OCCURS 0 WITH HEADER LINE,
          lw_edidc TYPE edidc,
          lt_edidd LIKE edidd OCCURS 0 WITH HEADER LINE,
          lw_zmat TYPE zsivseg.
    DATA: lw_mara TYPE tw_mara,
          lt_mara TYPE tt_mara.
    START-OF-SELECTION.
      SELECT matnr mtart meins ntgew FROM mara INTO TABLE lt_mara
                                     WHERE matnr IN so_matnr.
      IF NOT lt_mara[] IS INITIAL.
        lw_edidc-direct = 1.
        lw_edidc-rcvprn = 'SAPLER'.
        lw_edidc-rcvprt = 'LS'.
        lw_edidc-rcvpor = 'SIVPORT'.
        lw_edidc-mestyp = 'ZSIVMATERIAL'.
        lw_edidc-idoctp = 'ZSIVIDOC'.
        LOOP AT lt_mara INTO lw_mara.
          MOVE : lw_mara-matnr TO lw_zmat-matnr,
                 lw_mara-mtart TO lw_zmat-mtart,
                 lw_mara-meins TO lw_zmat-meins,
                 lw_mara-ntgew TO lw_zmat-ntgew.
          MOVE : 'ZSIVSEG' TO lt_edidd-segnam,
                 lw_zmat TO lt_edidd-sdata.
          APPEND lt_edidd.
          CLEAR : lt_edidd, lw_zmat.
        ENDLOOP.
      ENDIF.
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
        EXPORTING
          master_idoc_control            = lw_edidc
        TABLES
          communication_idoc_control     = lt_edidc
          master_idoc_data               = lt_edidd
        EXCEPTIONS
          error_in_idoc_control          = 1
          error_writing_idoc_status      = 2
          error_in_idoc_data             = 3
          sending_logical_system_unknown = 4
          OTHERS                         = 5.
      IF sy-subrc EQ 0.
        READ TABLE lt_edidc INDEX 1.
        IF sy-subrc EQ 0.
          WRITE:/10 lt_edidc-docnum.
        ENDIF.
      ENDIF.
    Regards,
    S.Nehru.

  • Problem with MASTER_IDOC_DISTRIBUTE

    Hi all.
    I'm using the FM 'MASTER_IDOC_DISTRIBUTE' to create IDOCs. I'm having the following problem: when I execute this function, it creates the IDOC and transfer it by XML, and the STATUS (you can look in transaction WE20) is set to 03 (IDOC generated and sent). I need this status set to 03, in other words I need the IDOC generated but not send, I will enter in transaction WE14 and do it manually.
    Thanks and regards.

    The problem was that my program was creating IDOCs and sending it. In other words, it was not exactly a "problem", the only one thing that I needed was generate IDOC and don't send it. I solved this problem by entering in transaction WE20 and configuring it.
    Thanks and Regards.

  • Outbound Idocs-FM MASTER_IDOC_DISTRIBUTE

    Hi,
    We have a standalone report, which sends outbound idoc. As per our basis consultant it seems that the idocs after being generated are stuck in the qRFC queue for a long time, which is causing issues.
    He has suggested that we call the function module MASTER_IDOC_DISTRIBUTE in BACKGROUND TASK instead of calling it just like that.
    1) Should it be background task or update task?
    2) What is the significance of calling it in background task or update task?
    3) What is the qRFC queue?
    Thanks in advance,
    Mick

    follow the link
    www.erpgenie.com/sapgenie/docs/ale_whitepaper.doc
    www.sapbrainsonline.com/ARTICLES/TECHNICAL/ALE/ALE_INTRODUCTION.html - 80k
    www.erpgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    QRFC QUEUE
    All types of applications are instructed to communicate with other applications. This communication may take place within an SAP system, with another SAP system, or with an application from a remote external system. An interface that can be used for dealing with this task is the Remote Function Call (RFC).  RFCs can be used to start applications in remote systems, and to execute particular functions.
    Whereas the first version of the RFC, the synchronous RFC, (sRFC) required both systems involved to be active in order to produce a synchronous communication, the subsequent generations of RFC had a greater range of features at their disposal (such as serialization, guarantee for one-time-only execution, and that the receiver system does not have to be available). These features were further enhanced through the queued RFC with inbound/outbound queue.  
    Communication between applications within an SAP system and also with a remote system can basically be achieved using the Remote Function Call (RFC). Here, the following scenarios are possible:
    ·         Communication between two independent SAP systems
    ·         Communication between a calling SAP system and an external receiving system
    ·         Communication between a calling external system and an SAP receiving system
    The following communication model shows what these communication scenarios may look like in reality. The actual sending process is still done by the tRFC (transactional Remote Function Call). Inbound and outbound queues are added to the tRFC, leaving us with a qRFC (queued Remote Function Call). The sender system is also called the client system, while the target system corresponds to the server system.
    In practice, the following three scenarios for data transfer exist:
    Scenario 1: tRFC
    This scenario is appropriate is the data being sent is independent of each other. A calling application (or client) in system 1 uses a tRFC connection to a called application (or server) in system 2. In this scenario, data is transferred by tRFC, meaning that each function module sent to the target system is guaranteed to be executed one time only. You cannot define the sequence in which the function modules are executed, nor the time of execution. If an error occurs during the transfer, a batch job is scheduled, which sends the function module again after 15 minutes.
    Scenario 2: qRFC with outbound queue
    In this scenario, the sender system uses an outbound queue, to serialize the data that is being sent. This means that function modules which depend on each other (such as update and then change) are put into the outbound queue of the sender system, and are guaranteed to be sent to the target system one after each other and one time only. The called system (server) has no knowledge of the outbound queue in the sender system (client), meaning that in this scenario, every SAP system can also communicate with a non-SAP system. (Note: the programming code of the server system must not be changed. However, it must be tRFC-capable.)
    Scenario 3: qRFC with inbound queue (and outbound queue)
    In this scenario, as well as an outbound queue in the sender system (client), there is also an inbound queue in the target system (server). If a qRFC with inbound queue exists, this always means that an outbound queue exists in the sender system. This guarantees the sequence and efficiently controls the resources in the client system and server system.  The inbound queue only processes as many function modules as the system resources in the target system (server) at that time allow. This prevents a server being blocked by a client. A scenario with inbound queue in the server system is not possible, since the outbound queue is needed in the client system, in order to guarantee the sequence and to prevent individual applications from blocking all work processes in the client system.
    Properties of the Three Communication Types 
    To help you decide which communication type you should use in your system landscape for your requirements, the advantages of the three communication types are listed below:
           1.      tRFC: for independent function modules only
           2.      qRFC with outbound queue: guarantees that independent function modules are sent one after each other and one time only (serialization). Suitable for communication with non-SAP servers.
           3.      qRFC with inbound queue: in addition to the outbound queue in the client system, an inbound queue makes sure that only as many function modules are processed in the target system (server) as the current resources allow. Client and server system must be SAP systems. One work process is used for each inbound queue.
    for detailed information
    http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/eae2a889e711d2956500a0c94260a5/frameset.htm
    Edited by: sharad narayan on Apr 11, 2008 11:46 AM

  • MASTER_IDOC_DISTRIBUTE inbound idocs?

    I am trying to post an inbound IDOC that was created inside an ABAP program.
    I have tried MASTER_IDOC_DISTRIBUTE and set the direction on the control record to '2' (inbound), however when i look at the idoc posted in WE02, its in the outbound section, not the inbound.  Of course it's failing there because the partner is not set up (nor should it be) to process this idoc as outbound.

    Hi, I think if you direcly call this FM (IDOC_INPUT_ORDERS), it can goes, even without the IDOC number. The IDOC number is for the EDI/ALE layer to differentiate the IDOCs, but it looks no usage in the Inbound FM inside, as these FM is only for inbound IDOC data into server.
    Maybe there will be some consistency issue occur, but the inbound can be done, haven't tried it.
    By the way, it looks you want to create a IDOC which has the same sender and receiver, it has some other way, you can reference in the following link:
    http://www.sapgenie.com/ale/whitepaper.htm
    In The 7.3 Topic it has been explained to configure this scenerio.
    hope it will be helpful
    Thanks a lot

  • MASTER_IDOC_DISTRIBUTE and BD64

    Hello all,
    My goal is to call the function MASTER_IDOC_DISTRIBUTE in a specific outbound idoc function module, WITHOUT giving the receiver system/port/msgcode informations
    I would like it to determine automatically using the customizing from BD64, as it works for several function modules in our system.
    BUT : the concerned message type is ACC_ACT_ALLOC. I cannot customize it directly in BD64, as it is a BAPI interface. Therefore I need to use "Add BAPI" in the distribution model (method AcctngActivityAlloc-Post).
    And the consequence is that MASTER_IDOC_DISTRIBUTE cannot find the related information (receiver...)
    Do you confirm that in the case of a async BAPI interface like msg type ACC_ACT_ALLOC, we cannot customize the distribution model information, and so we are force to hard code these information in the specific function module (structure IDOC_CONTROL, fields RCVPRN, RCVPRT, MESCOD...) ? or did i miss something ?
    thanks in advance for your help

    Hello,
             Once the Master IDoc is created, a Syntax Check is done for the Segment Definitions and if the Syntax Check is OK, then the Communication IDoc(s) are generated. So, until this Process is complete, we'll not be able to get the Complete Log.
    Thanks and Regards,
    Venkat Phani Prasad Konduri

  • Use of MASTER_IDOC_DISTRIBUTE

    Hi all!!
    I have created my own IDoc and send it to the target system using the MASTER_IDOC_DISTRIBUTE function. Everything seems to work correctly, I can see in my system the OK status, but I can not see anything in the receiver system.
    If I use the test tool, I can see that my IDoc has reached the receiver system.
    I do not now what am I doing incorrectly... has someone any idea?? Why does not reach the receiver system using the function and reach when using the test tool? If anything would not be correctly configured, nor of them should work, no? Perhaps I am calling the function with incorrect values? I do not know. The outbound log is identical in both of them.
    Thank you very much!
    Araitz.

    Hi Arairz,
    A COMMIT WORK must be dispatched in the calling program, otherwise the     
    IDocs may not be dispatched.                                               
    Perform an explicit commit work after the function module call.                                                                   
    Regards,
    Aditya

  • Function MASTER_IDOC_DISTRIBUTE

    Hi Experts,
    I have generated an IDOC with the function MASTER_IDOC_DISTRIBUTE without errors. But when I check the SAP transaction WE02, there is no new IDOC. Could anybody tell me, where I will find my new IDOC?
    Thanks.
    Best Regards
    Lukas

    Hello Lukas,
    Set a break point after FM MASTER_IDOC_DISTRIBUTE
    Please check the table IT_COMM_CTRL, it will contain the Idoc number
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
         IN UPDATE TASK
         EXPORTING
           MASTER_IDOC_CONTROL            = ST_EDIDC
         TABLES
           COMMUNICATION_IDOC_CONTROL     = IT_COMM_CTRL
           MASTER_IDOC_DATA               = IT_EDIDD
    Thanks.

Maybe you are looking for