Split 1 IDoc into 2

Hi All,
The scenario is SAP MDM --> PI -->SAP ECC,
MDM sends XML Message with 3 segments and a field (Material Number).
The 1st and 3rd segment have a field class type, based on which the splitting is to be done.
The 1st segment has a default class type value as 001, and when splitted the 1st and 2nd segment will go to IDoc1 along with field Material Number.
The class type of 3rd segment needs to be checked, if the value is 002 it will form IDoc2 and the common field Material Number will also be part of IDoc2. Both the resulting IDocs will be sent to ECC. Please help me with this.
Thanks,
NehaSingh

Hi Neha,
Can you kindly explain which multimapping work in your case as for my info for receiver IDOC adapter multimapping does not work for 7.0 is this functionality has been provided in some recent upgrade ? or you are using 2 message mapping and 2 interface mapping and putting a condition on Interface determination to call required mapping .Kindly explain how you achieved your requirement .
Regards,
Saurabh

Similar Messages

  • Split the IDOC into multiple IDOC if the IDOC has more than 500 records

    Hi All,
    I developed an outbound IDOC in which we are facing an issue.
    There is some limitation on the maximum idoc size it can handle.
    If number of records is more than 500, split the idoc into multiple iDoc's, e.g. if it would have 1300 records , the result would be 2 iDoc's with 500 records, and the last one would have 300 records
    How can i acheive this.
    Regards
    Jai

    Hi,
    1) first you need to know which message type/Idoc type you are triggering.
    2) Get the Corresponding processcode from Partner profiles(WE20/ WE41).
    3) Then the look for prper user-exit in the related processing FM.
    4) write logic to split the IDoc accordingly.
    if no proper user exit available then copy the standard processing FM and need to all ALE related configurations.
    Catch hold any ABAP expert in your team to do all these.
    Suresh

  • Split Single IDOC into Multiple IDOC's Based on Segment Type

    Hi Experts,
    I have a scenario IDOC to FILE ,  Split Single IDOC into Multiple IDOC's based on Segment Type
    Outbound:
    ZIdocName
    Control Record
    Data Record
    Segment 1
    Segment 2
    Segment 3
    Status Record
    I should get output like below
    Inbound:
    ZIdocName
    Control Record
    Data Record
    Segment 1
    Status Record
    ZIdocName
    Control Record
    Data Record
    Segment 2
    Status Record
    ZIdocName
    Control Record
    Data Record
    Segment 3
    Status Record
    Please suggest me step by step process to achieve this task.
    Thanks.

    Thanks a lot Harish for reply.
    I have small doubt. According to your reply , If we have N number of segments in single IDOC with same fields in all segments then for splitting Single IDOC into Multiple IDOC's based on Segment Type we need to duplicate N number of target IDOC tree structure.
    Is that possible to Split single IDOC into Multiple IDOC's based on Segment Type using only one Target IDOC structure without duplicating the Target IDOC structure tree.

  • How can I split an Orders05 iDoc into multiple iDocs?

    Hello,
    Can one of you experts please tell me how I can split an ORDERS05 iDoc into multiple iDocs based upon Delivery addresses? 
    For example, if the iDoc contains 3 different Delivery Addresses then I need to split it into 3 iDocs.
    It has been suggested to me that I can Create a custom function module. In this custom fm split the idoc into 3 based on the delivery address and create it using the FM MASTER_IDOC_DISTRIBUTE.
    Problem is I don't know how to do this.  Any help is greatly appreciated.  Thanks.
    Dan

    Hi Dan Avis
    Write a Custom  Z program .
    1 get order05 idoc number....
    2 get the segment details...(Based on you condition...)
    3 In a loop  send the data to the FM MASTER_IDOC_DISTRIBUTE  (Based on you condition...)
    4 IDOC will generated,,,every loop and
    5 Change the status of original idoc .
    or
    Create Function module and use the FM as process code to create 3 idocs...and processs...new generated idoc and block original idocs...
    Call me if you have questions  @ 302 290 5677
    Thanks
    Ramesh

  • How to Split Single Outbound Idoc into Multiples

    Hi guys
    Hope you all are doing good.
    Can you please let me know , How to Split Single Outbound IDOC into multiples.
    I am looking for some sought of configuration in IDOC/from SHIPMENT Configuration level.  Because this needs to be implemented for Shipment IDOCS.  Please let me know if this can be done through configurations apart from implementing  User exit or copying the outbound shipment function module.
    Awaiting for your valuable replies.
    Best Regards
    Shiva

    Hello,
    1. Routes
    2. Packaging used
    3. Shipment Type
    Regards
    Waza

  • Split one IDoc into two IDocs ?

    hello all,
    I wanna split one IDoc into two IDocs in XI?
    how can implement it?
    plx give some suggestions.
    thx in advance
    best regards
    Yaning
    Message was edited by:
            Yaning Liu

    Yaning,
    Please find the below blog for changing the ocurrences of IDOC
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Best regards,
    raj.

  • Splitting single idoc into multiple xml's

    Hello,
    My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process.
    and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process

    Hi Abhishek,
    [quote]My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process
    For this, you have to go for multimapping.
    The links for it are already provided in the above posts.
    and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process
    Can you please explain this requirement further?
    -Supriya.

  • Problems with sending IDocs into R/3 using BPM

    Hi Vishnu,
    as I have read the forum, you have experience with sending IDocs into R/3 from XI using the BPM.
    Did you have problem, that this sending takes very long time?
    My BPM splits the xml, sends IDoc into R/3 immediately, but the processing of the 2nd IDoc takes 6-10 minutes!
    Do you have any idea, what could be wrong?
    Thanx 4 answer, Peter

    Vishnu, I was discussing this problem in another thread, but no helpful answer was sent, and I have read, that you have experience, so - just for explanation
    Well,
    yes, this situation is really strange.. New facts are:
    when I send into XI XML, which is splitted in the BPM only into 1 IDoc, it is processed immediately. When I send there XML for 2 IDocs, the first is processed immediately, the 2nd starts immediately, but end of process is after 6-10 minutes, it depends... Then I tried to send there XML for 10 IDocs - and now attention please! 5 of them have been processed almost immediately, 5 of them after 8 minutes...  The last test was with 16 items - 6 processed immediately, 10 after 10 minutes...  And all these 10 minutes was my 4 processor XI box unavailable, with over 60% load... But finally the IDocs arrive!!
    Any explanation???
    This is really unbelievable situation!
    Port name is SAPDEV, rfc destination DEVCLNT100
    Actually, when I was creating the scenarion using the wizard and trying to add my communication channel(IDoc type) to receiver agreement, I got error - communication channel is not configured correctly, use another one. But somewhere I read, that I should create the receiver agreement manually. So I did.
    To my BPM:
    -receive MSG
    -switch (but I'm testing only one branch now) - and the MSG message is always passed here, it's ok
    -then I have transformation to MultiMSG (message with multiple DATA for multiple IDOCS)
    -then comes the split mapping Multi2SingleMSG
    -then ForEach Block with sending the Single MSG
    this is the end of the BPM, and outside the BPM comes the mapping Single2IdocMSG and sending the IDoc into R/3
    before I had the Single2Idoc mapping in the BPM, but thought, that this could be the bottleneck, so moved the mapping after the BPM... It didn't help...
    So, what do you say?
    Peter

  • Breaking up of, One IDoc to many IDocs & combing Many IDocs into one IDoc?

    Does anybody have any sample code of:
    Splitting an IDoc into multiple IDocs and
    Combining many similar IDocs into one IDoc
    Any pointers will be appreciated.
    Regards
    Mahesh

    This is the code for splitting of an inbound idoc into multiple idoc
    REPORT ztemp no standard page heading .
    ******************Data Declaration for selection screen***************
    TABLES: edidc,edidd.
    CALL SELECTION-SCREEN 9000.
    SELECTION-SCREEN: BEGIN OF SCREEN 9000,
                      BEGIN OF BLOCK b1 WITH FRAME.
    SELECT-OPTIONS: idocno FOR edidc-docnum.
    SELECTION-SCREEN:END OF BLOCK b1 ,
                      END OF SCREEN 9000.
    *******************Data Declaration ************************************
    DATA : it_contrl LIKE TABLE OF edidc WITH HEADER LINE,
           it_hdata     LIKE TABLE OF edidd WITH HEADER LINE,
           it_fdata  LIKE TABLE OF edidd WITH HEADER LINE,
            it_gdata  LIKE TABLE OF edidd WITH HEADER LINE,
           it_data LIKE TABLE OF edidd WITH HEADER LINE,
           it_status LIKE TABLE OF bdidocstat WITH HEADER LINE,
           it_bdwfretvar LIKE TABLE OF bdwfretvar WITH HEADER LINE,
           it_bdi_ser LIKE TABLE OF bdi_ser WITH HEADER LINE,
           it_ldata LIKE TABLE OF edidd WITH HEADER LINE,
           it_tede2  LIKE  tede2,
           vbeln LIKE vbak-vbeln,
           idocnum LIKE  edidc-docnum,
           result LIKE bdwfap_par-result,
           it_stat LIKE edids.
    DATA : count TYPE i ,
           counter TYPE i ,
           temp TYPE i VALUE 1 ,
           line TYPE i ,
           tab LIKE sy-tabix.
    *********************passing values to control record*****************
    it_contrl-direct = '2'.
    it_contrl-rcvprn = 'ID3IDES802'.
    it_contrl-rcvprt = 'LS'.
    it_contrl-doctyp = 'ORDERS05'.
    it_contrl-idoctp = 'ORDERS05'.
    it_contrl-sndpor = 'ZSOFI'.
    it_contrl-sndprt = 'LI'.
    it_contrl-sndprn = '1000'.
    it_contrl-mestyp = 'ORDERS'.
    APPEND it_contrl.
    ************************Select query for data*************************
    SELECT   * FROM edid4 INTO CORRESPONDING FIELDS OF TABLE it_fdata
    WHERE   docnum IN idocno.
    SELECT   * FROM edid4 INTO CORRESPONDING FIELDS OF TABLE it_data
    WHERE   docnum IN idocno AND segnam NOT LIKE 'E1EDP%'  .
    SELECT   * FROM edid4 INTO CORRESPONDING FIELDS OF TABLE it_hdata
    WHERE   docnum IN idocno AND segnam  LIKE 'E1EDP%'.
    **************select query to count the no of E1EDP01 segment*********
    SELECT COUNT( * ) FROM edid4 INTO count  WHERE docnum IN idocno AND
    segnam = 'E1EDP01'.
    *************to determine the no of idocs to be generated************
    count = count / 5.
    PERFORM datasplit.
    **********************************for remaining idocs*****************
    counter = count MOD 5.
    IF counter NE 0.
      PERFORM dataremain. .
    ENDIF.
    *&      Form  datasplit
          text
    -->  p1        text
    <--  p2        text
    FORM datasplit  .
      LOOP AT it_data.
        MOVE-CORRESPONDING it_data TO it_gdata.
        APPEND it_gdata.
      ENDLOOP.
      DO count TIMES.
        PERFORM split.
        perform idoccreate.
        enddo.
    ENDFORM.                   " datasplit
    *&      Form  SPLIT
          text
    -->  p1        text
    <--  p2        text
    FORM split .
      LOOP AT it_hdata.
        IF temp <= 5.
          ON CHANGE OF it_hdata-segnam.
            IF it_hdata-segnam = 'E1EDP01'.
              MOVE-CORRESPONDING it_hdata TO it_gdata.
              APPEND it_gdata.
            ELSE.
              MOVE-CORRESPONDING it_hdata TO it_gdata.
              APPEND it_gdata.
              temp = temp + 1.
            ENDIF.
          ENDON.
        ENDIF.
      ENDLOOP.
    ENDFORM.                    " SPLIT
    *&      Form  dataremain
          text
    -->  p1        text
    <--  p2        text
    FORM dataremain .
      CLEAR it_gdata[].
      LOOP AT it_data.
        MOVE-CORRESPONDING it_data TO it_gdata.
        APPEND it_gdata.
      ENDLOOP.
      LOOP AT it_hdata .
        IF sy-tabix  > 10.
          MOVE-CORRESPONDING it_hdata TO it_gdata.
          APPEND it_gdata.
        ENDIF.
      ENDLOOP.
      perform idoccreate.
    ENDFORM.                    " dataremain
    *&      Form  idoccreate
          text
    -->  p1        text
    <--  p2        text
    form idoccreate .
    ***********************for creating the inbound idocs****************
    CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'
       EXPORTING
         pi_status_message             = it_stat
         pi_do_handle_error            = 'X'
       PI_NO_DEQUEUE                 = ' '
         pi_return_data_flag           = 'X'
      PI_RFC_MULTI_CP               = '    '
       IMPORTING
         pe_idoc_number                = idocnum
         pe_state_of_processing        = sy-subrc
         pe_inbound_process_data       = it_tede2     "for process code
        TABLES
          t_data_records                = it_gdata
      T_LINKED_OBJECTS              =
        CHANGING
          pc_control_record             = it_contrl
    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.
      COMMIT WORK.
    *it_contrl-status = '64'.
    modify it_contrl index 1.
    ****************for posting the idoc**************************
      CALL FUNCTION 'IDOC_INPUT_ORDERS'
        EXPORTING
          input_method                = 'A'
          mass_processing             = '1'
       IMPORTING
         workflow_result             = result
      APPLICATION_VARIABLE        =
      IN_UPDATE_TASK              =
      CALL_TRANSACTION_DONE       =
       DOCUMENT_NUMBER             = vbeln
        TABLES
          idoc_contrl                 = it_contrl[]
          idoc_data                   = it_gdata[]
          idoc_status                 = it_status[]
          return_variables            = it_bdwfretvar[]
          serialization_info          = it_bdi_ser[]
      EDI_TEXT                    =
      EDI_TEXT_LINES              =
       CLEAR : it_contrl-docnum.
      COMMIT WORK.
    endform.                    " idoccreate

  • Split Idoc

    hi,
      Please let me  know ,How  to  Split larger  Idoc  into  Multiple  Idocs?
    Thanks,
    Asha

    You need to use "packet size" in outbound parameter in WE20.
    Check this
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/0b/2a6661507d11d18ee90000e8366fc2/frameset.htm
    or if you want to split the single IDoc into multiple then probably you need to look into the triggering program
    a®

  • How to adjust splitted lines into one line in Text file?

    Hi Guys,
    I have a text file with 3 fields(comma separated): GLCode (Number), Desc1 (Char), Desc2(Char) and need to load it into BW.
    My Text file looks like:
    1011.00,"Mejor PC Infrastructure","This line is ok."
    1012.00,"Telephone Equipment $","This line ends in next line.   
    1)Need to change the equipment immediately.
    2)Take immediate action"
    1013.00,"V1 Computer Server Infrastructure # Equip","For purchases
    of components that make up the company's network, such as servers, hubs, routers etc."
    1014.00,"Flash Drive","Need to provide all IT Developer"
    This is how file looks like. Now I need the followings:
    1. Need to remove the space and need to adjust the splitted line into one. Say here
    line/record 2 is splitted into 3 lines and need to adjust in 1 line.
    2. In Line 5 (Record 3) data splitted into 2 lines and need to make 1 line.
    3. Need to remove bad characters.
    Could someone help me please how to proceed ?
    Regards,

    Not quite correct by my testing.  Try:
    $i=0
    Get-Content .\test.txt | ForEach {
    If ($i%2){
    ("$Keep $($_)").Trim()
    }Else{
    $keep=$_
    }$i++
    Good catch!
    Boe Prox
    Blog |
    Twitter
    PoshWSUS |
    PoshPAIG | PoshChat |
    PoshEventUI
    PowerShell Deep Dives Book

  • How To UPLOAD a DATA (.DAT) fiel from PC to internal table and then split it into the data different columns

    Hi all,
    I am new to ABAP Development. I need to upload a .DAT file (the file doesn#t have any proper structure-- Please find the .DAT file in the attachment). After uploading the DATA (.DAT) fiel I need to split in into different columns. Refering the attached .DAT fiel the fields in bracets like:
    [Arbeitstag],  [Pecunia], [Mita], [Kunde], [Auftrag] and  [Position] are different fields that need to be arranged in columns in an internal table. this .DAT fiel which I want to upload and then SPLIT it into various fields will will treated as MASTER DATA table for further programming. The program that I had written is as below. Also please refer the attached .DAT table.
    Please if any one could help me. i searched a lot in different forums but couldn't find me  a solution. Also note that the attached fiel is in text (.txt) format here but in real situation the same fiel is in DATA (.DAT) format.
    *& Report  ZDEMO_ZEITERFASSUNG9
    REPORT  ZDEMO_ZEITERFASSUNG9.
    Types: Begin of ttab,
            Rec(1000) type c,
           End of ttab.
    DATA: itab  type table of ttab.
    DATA: wa_tab type ttab.
    DATA: file_str type string.
    Parameters: p_file type localfile.
    At selection-screen on value-request for p_file.
                                           CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
                                            EXPORTING
    *                                          PROGRAM_NAME        = SYST-REPID
    *                                          DYNPRO_NUMBER       = SYST-DYNNR
    *                                          FIELD_NAME          = ' '
                                               STATIC              = 'X'
    *                                          MASK                = ' '
                                             CHANGING
                                               file_name           = p_file.
    *                                        EXCEPTIONS
    *                                          MASK_TOO_LONG       = 1
    *                                          OTHERS              = 2
    Start-of-Selection.
      file_str = P_file.
      CALL FUNCTION 'GUI_UPLOAD'
        EXPORTING
          filename                      = '\\10.10.1.92\Volume_1\_projekte\Zeiterfassung-SAP\BUP_ZEIT.DAT'   " This the file  source address
          FILETYPE                      = 'DAT'
          HAS_FIELD_SEPARATOR           = ';'
    *     HEADER_LENGTH                 = 0
    *     READ_BY_LINE                  = 'X'
    *     DAT_MODE                      = ' '
    *     CODEPAGE                      = ' '
    *     IGNORE_CERR                   = ABAP_TRUE
    *     REPLACEMENT                   = '#'
    *     CHECK_BOM                     = ' '
    *     VIRUS_SCAN_PROFILE            =
    *     NO_AUTH_CHECK                 = ' '
    *   IMPORTING
    *     FILELENGTH                    =
    *     HEADER                        =
        tables
          data_tab                      = itab
       EXCEPTIONS
         FILE_OPEN_ERROR               = 1
         FILE_READ_ERROR               = 2
         NO_BATCH                      = 3
         GUI_REFUSE_FILETRANSFER       = 4
         INVALID_TYPE                  = 5
         NO_AUTHORITY                  = 6
         UNKNOWN_ERROR                 = 7
         BAD_DATA_FORMAT               = 8
         HEADER_NOT_ALLOWED            = 9
         SEPARATOR_NOT_ALLOWED         = 10
         HEADER_TOO_LONG               = 11
         UNKNOWN_DP_ERROR              = 12
         ACCESS_DENIED                 = 13
         DP_OUT_OF_MEMORY              = 14
         DISK_FULL                     = 15
         DP_TIMEOUT                    = 16
         OTHERS                        = 17
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      LOOP at itab into wa_tab.
            WRITE: / wa_tab.
      ENDLOOP.
    I will be grateful to all you experts for ur inputs
    regards
    Chandan Singh

    For every Auftrag, there are multiple Position entries.
    Rest of the blocks don't seems to have any relation.
    So you can check this code to see how internal table lt_str is built whose first 3 fields have data contained in Auftrag, and next 3 fields have Position data. The structure is flat, assuming that every Position record is related to preceding Auftrag.
    Try out this snippet.
    DATA lt_data TYPE TABLE OF string.
    DATA lv_data TYPE string.
    CALL METHOD cl_gui_frontend_services=>gui_upload
      EXPORTING
        filename = 'C:\temp\test.txt'
      CHANGING
        data_tab = lt_data
      EXCEPTIONS
        OTHERS   = 19.
    CHECK sy-subrc EQ 0.
    TYPES:
    BEGIN OF ty_str,
      a1 TYPE string,
      a2 TYPE string,
      a3 TYPE string,
      p1 TYPE string,
      p2 TYPE string,
      p3 TYPE string,
    END OF ty_str.
    DATA: lt_str TYPE TABLE OF ty_str,
          ls_str TYPE ty_str,
          lv_block TYPE string,
          lv_flag TYPE boolean.
    LOOP AT lt_data INTO lv_data.
      CASE lv_data.
        WHEN '[Version]' OR '[StdSatz]' OR '[Arbeitstag]' OR '[Pecunia]'
             OR '[Mita]' OR '[Kunde]' OR '[Auftrag]' OR '[Position]'.
          lv_block = lv_data.
          lv_flag = abap_false.
        WHEN OTHERS.
          lv_flag = abap_true.
      ENDCASE.
      CHECK lv_flag EQ abap_true.
      CASE lv_block.
        WHEN '[Auftrag]'.
          SPLIT lv_data AT ';' INTO ls_str-a1 ls_str-a2 ls_str-a3.
        WHEN '[Position]'.
          SPLIT lv_data AT ';' INTO ls_str-p1 ls_str-p2 ls_str-p3.
          APPEND ls_str TO lt_str.
      ENDCASE.
    ENDLOOP.

  • Unable to import IDoc into IR

    Hi - For no reason i can't import the IDoc into XI.
    The problem seems to be that in backend system is a problem. The basis-type and the segments are all released - to me because i released and de-released them. The Idoc was developed in client 010 and i want to import ist from 011 - of course there was some kind of transport!
    In WE20 of backend system i am not able to pick this IDoc for Incoming parameter, no idea why.
    In XI i am able to import MetaData via IDX2 but i am still not able to import the IDoc!!
    can somebody help?! br Jens

    Hi,
    1 Scenario
    This guide deals with all the configurations required to create an IDoc adapter in Exchange Infrastructure
    3.0 to send an IDoc from XI to the SAP backend system.
    Unlike other types of adapters, the IDoc adapter has dependencies on the XI 3.0 ABAP configurations and
    the backend SAP system configurations. Those configurations information will have to be either created
    first or retrieved in order to complete the IDoc adapter configuration.
    2 Introduction
    Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
    systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
    simple, are many times missed or mis-configured, causing the delivery of messages to fail.
    Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
    ABAP.
    Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
    SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
    backend SAP system.
    3 The Step By Step Solution
    The basic steps for the IDoc configuration are outline below:
    1. Configure SM59 on XI to communicate to SAP backend system.
    2. Configure port on XI for IDoc communication.
    3. Create or verify the Logical System Name on the SAP backend system.
    4. Create or verify business system in XI’s System Landscape Directory.
    5. Verify the Logical System Name of the business system.
    6. Verify or add the Logical System Name for the sender business system.
    7. Create/configure the Communication Channel for the IDoc receiver adapter
    3.1 Configure SM59 on XI to communicate to SAP backend system.
    1. Using transaction SM59, create an RFC destination with Connection Type = “3”.
    In this example, the RFC destination name is “NDVCLNT510”.
    2. Enter the logon information:
    3. Test the connection by clicking on “Testing connection” and “Remote logon”.
    Both must be successful.
    3.2 Configure port on XI for IDoc communication.
    4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is “SAPNDV”.
    •     &#61472;The Port name must be in the form of “SAPxxx”, where xxx is the system ID of the backend SAP
    system.
    •     The Client must be the client number of the backend SAP system.
    •     Select the RFC Destination which was created in the previous step.
    3.3 Create or verify the Logical System Name on the SAP backend system.
    5. Enter transaction SALE on the SAP backend system.
    6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
    3.4 Create or verify business system in XI’s System Landscape Directory.
    The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
    7. In the System Landscape Directory,  select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical  System Name.
    3.5 Verify the Logical System Name of the business system.
    8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
    Navigate the menu:
    Service • Adapter Specific Identifiers.
    If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
    9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
    Landscape Directory.
    •     &#61472;Double-click on the business system in the Integration Directory.
    •     &#61472;Switch to Edit mode.
    •     &#61472;Select menu: Service • Adapter-Specific Identifiers 
    10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
    11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
    3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
    15. In the Integration Directory, create an IDoc receiver communication channel.
    •     &#61472;The RFC Destination is from step 3.1.
    •     &#61472;The Port is from step 3.2.
    NOTE:
    There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
    4 Appendix
    Transaction: IDX2
    There are a couple of situation where IDX2 can be useful on the XI system.
    1. When we want to test connection between the XI and SAP backend system.
    2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
    meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
    Go to transaction IDX2 and click on “Create”.
    Enter the IDoc Type and the Source Port as defined in step #2. Click “Continue”.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
    Regards
    Hemant
    Award point if find helpful

  • Unable to import IDoc into NWBPM from NWDS

    Dear PO Experts,
    We are migrating an existing interface
    (IDoc<-->PI<-->SOAP using BPM (Multiple sync calls)).
    We are un able to import IDoc into NW BPM project as a service Interface. (For BPM we exported IDoc into local system as an external definition and did few modifications to the xsd as per below blog and exported back to PO server as an external definition.Create Service Interface for the same .
    http://scn.sap.com/community/process-orchestration/blog/2014/09/24/idoc-to-nw-bpm-scenario#comment-542653 )
    We are getting below exception while importing IDoc Service Interface into BPM project.I have attached IDoc WSDL file for your reference.Could you please share your expertise on this issue.
    >>>An internal error occurred during: "Importing MOIN models for XSDs and WSDLs...".
    java.lang.OutOfMemoryError: Java heap space
    at java.util.ArrayList.<init>(ArrayList.java:112)
    at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
    (XSDParticleImpl.java:1271)
    at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
    (XSDParticleImpl.java:1050)
    at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
    (XSDParticleImpl.java:1149)
    at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
    (XSDParticleImpl.java:1039)
    at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
    (XSDParticleImpl.java:1272)
    at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
    (XSDParticleImpl.java:1060)
    at org.eclipse.xsd.impl.XSDParticleImpl.getDFA
    (XSDParticleImpl.java:2041)
    at org.eclipse.xsd.impl.XSDModelGroupImpl.validateRoot
    (XSDModelGroupImpl.java:599)
    at org.eclipse.xsd.impl.XSDComplexTypeDefinitionImpl.validate
    (XSDComplexTypeDefinitionImpl.java:1408)
    at org.eclipse.xsd.impl.XSDConcreteComponentImpl.validate
    (XSDConcreteComponentImpl.java:565)
    at org.eclipse.xsd.impl.XSDSchemaImpl.validate(XSDSchemaImpl.java:1653)
    at com.sap.tc.esmp.tools.core.util.EMFUtils.validate(EMFUtils.java:613)
    at
    com.sap.tc.esmp.tools.xsd.xml.EmfSchemaImporter.calculateAffectedPartitions(EmfSchemaImporter.java:903)
    at
    com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.calculateAffectedPartitions(Wsdl1Importer.java:365)
    at
    com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.resolveImportLink(Wsdl1Importer.java:545)
    at
    com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.createChainLink(Wsdl1Importer.java:522)
    at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.init
    (Wsdl1Importer.java:461)
    at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.<init>
    (Wsdl1Importer.java:337)
    at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer.prepareWsdlImport
    (Wsdl1Importer.java:1381)
    at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer.prepareWsdlImport
    (Wsdl1Importer.java:1368)
    at com.sap.tc.esmp.tools.facade.Import.prepareWsdlImport
    (Import.java:106)
    at
    com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor.doImportFiles(RepositoryMetadataProcessor.java:298)
    at
    com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor.access$300(RepositoryMetadataProcessor.java:52)
    at com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor$4.run
    (RepositoryMetadataProcessor.java:248)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Regards
    Venkat

    Hi Venkat,
    Find the below link.
    http://scn.sap.com/community/process-orchestration/blog/2014/11/29/using-idocs-in-nwbpm

  • TCODE TO DOWNLOAD IDOC INTO A FLAT FILE

    Hi All,
       Please let me know if there is any tcode to download IDOC into a flat file..
    Regards,
    Kaveri

    try with we60 where you should have links to download the idoc type.
    Please check this:
    1. How to Download a Hierarchy to a Flat File
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0403a990-0201-0010-38b3-e1fc442848cb
    2. How To Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0 Version 1.10
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
    run the report RSEOUT00 with the idoc number, flat xml file will be generated at the location user/sap/XI/SYS/global/idoc_file
    Please rewrds if found help ful

  • How to get structure of IDOC into xi in the scenario is IDOC - XI - File

    hi XI Guys,
          When i want to Integrate SAP sys(IDOC) with File how to get structure of IDOC into XI, As we will define Data types in File -> XI -> File. Please send Step by Step process as i am new to Netweaver(XI)
    ThankYou,
    B.Pushparaju.

    When i want to Integrate SAP sys(IDOC) with File how to get structure of IDOC into XI
    >>>>
    import the IDoc under the imported object in your SCV. Note that import should be allowed for the SCV.
    As we will define Data types in File -> XI -> File.
    >>>>
    Ref. these blogs to help you out ..
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2

Maybe you are looking for