Skip to Content
avatar image
Former Member

Idoc to Idco scenario

Hi Experts,

I need help from you all as i struck in idoc to idoc scenario.

i need to send the idoc from source system(R/3) to target system SAP(APO).

Please guide me what all the steps to be followed.

i need to send the same idoc to target.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • avatar image
    Former Member
    Nov 03, 2008 at 04:34 AM

    Hi,

    Follow this thread

    idoc to idoc

    Regards,

    Ravi.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 03, 2008 at 04:35 AM

    hi,

    [idoc-to-idoc-scenario;

    also a sample scenario wid steps as follows :

    Description:

    In this scenario we are sending an IDOC from an R/3 system to the IDOC in other R/3 system through XI.

    XI Details:

    Integration Builder: Design

    Component Name : SAPNW of sapnw

    Namespace : urn: idoc2idoc

    Integration Builder: Configuration

    Scenario Name : IDoc2IDoc

    Business System : SAP01 (Cgnsap 01 System)

    SSI (Cgnsap 13 System)

    Communication Channels:

    1) No Sender Channel is required as we are using IDOC.

    2) CC_OUT_IDOC_MATMAS05 [Send the data from Xi to CGNSAP01].

    Transaction Codes Used:

    SM59- To Create RFC Destinations

    WE21- To Create IDoc Ports

    SALE- To Create Logical System

    WE20- To Create Partner Profiles

    BD64- Display Distribution Model

    WE19- To Trigger an IDoc

    IDX1- Port Maintenance in IDoc Adapter

    IDX2- Metadata Overview for IDoc Adapter

    Processing Steps:

    Source Side Configuration: CGNSAP13 (SAP R/3)

    IDOC used: MATMAS.MATMAS05

    Using Transaction Code WE19 we can see the structure of IDOC (MATMAS05), which we are using

    Go to Transaction Code WE19 and enter the name of IDOC in Basic Type and execute

    Click on the Segment data and then a screen will come in which the data of IDOC is entered

    Creation of RFC Destination:

    1. Create RFC Destination: To create a RFC destination use transaction SM59.

    The RFC destination is created to provide IDOC a route from SAP system to XI server. Thus once the IDOC is initiated will reach to this destination for further transformations.

    2. Create a RFC Destination XI_IDOC2IDOC with Target Host: Cgnsap 32(XI System) and select the connection type as 3(Connection to R/3 System).

    The following screen will come once you will click on Create for new RFC destination.

    Give a name to your RFC destination.

    The Target Host field will be your XI server like cgnsap32.

    All the other fields are dependent on the target host.

    Save this and your RFC will be created.

    Go to Logon/Security tab and fill the details for the Cgnsap32 system as shown below

    Creation of IDOC PORT:

    3. Create Port: To create a port uses the transaction WE21. We need a port to send the IDOC to the intended RFC destination.

    Create a new Transactional RFC.

    Give the port name.

    Select the RFC destination for this port.

    Save the data.

    Creation of Logical System:

    4. Now Go to Transaction Code SALE and create Logical System.

    Sending and Receiving Systems->Logical Systems->Define Logical System

    Click on New Entries and fill the relevant details as show below

    b) As we will save it a new window will pop up, in this click on Create and then it will ask you to create a New Request. Just give description of the request and save it, else everything is self-generated.

    c) Hence the Logical System is created.

    Create another RFC Destination with Target host as cgnsap13. Also create a port and logical system as above using the RFC Destination. This is used as a sender to trigger the IDOC from cgnsap13.

    Creation of Partner Profile:

    Partner Profiles: Now we will create Partner Profiles by using transaction WE20. These partner profiles are created to identify our logical system uniquely, as we know that there can be n number of logical system in a Business System.

    In the Partner No field enter the name of the logical system created.

    Enter the Partner Type as LS (logical system).

    The type and Lang field will be same.

    In the Agent field select the business system from which you are sending the IDOC.

    In the Message Type Field include the IDOC.

    Save all the data.

    Creation of Distribution Model:

    Go to Transaction Code BD64 and create Distribution Model.

    Click on create model view, window will popup as shown below.

    Enter the short text and the technical name as required.

    Once the model view is created, click on Add message type. A window pops up as shown below. Enter the details of the model view, sender logical system name (for cgnsap13 in this case) and the receiver logical system name. (Logical system created in cgnsap13 for sending to XI server)

    XI SIDE CONFIGURATION: CGNSAP32 (XI SYSTEM)

    Creation of RFC Destination:

    1. Go to Transaction Code SM59 and select R/3 Connections and click on CREATE.

    2. Create a RFC Destination RFC_IODCTOIODC with Target Host: Cgnsap 01(R/3 System) and select the connection type as 3(Connection to R/3 System).

    Creation of IDOC PORT:

    3. Go to Transaction Code IDX1 and create an IDoc Port PORT_01 (Transactional RFC) and map it with the RFC destination (RFC_IDOCTOIDOC).

    4. Go to Transaction Code IDX2, Click on Create and enter the details of IDoc Type and Source Port.

    Target Side Configuration: CGNSAP01 (SAP R/3)

    Creation of Logical System:

    4. Now Go to Transaction Code SALE and create Logical System.

    Sending and Receiving Systems->Logical Systems->Define Logical System.

    Click on New Entries and fill the relevant details as show below

    b) As we will save it a new window will pop up, in this click on Create and then it will ask you to create a New Request. Just give description of the request and save it , else everything is self generated.

    c) Hence the Logical System is created.

    Creation of Partner Profile:

    Partner Profiles: Now we will create Partner Profiles by using transaction WE20. These partner profiles are created to identify our logical system uniquely, as we know that there can be n number of logical system in a Business System.

    In the Partner No field enter the name of the logical system created.

    Enter the Partner Type as LS (logical system).

    The type and Lang field will be same.

    Now add Inbound parameters.

    In this screen, enter the Message type and the Process Code for u2018MATMASu2019 and save it.

    Now go to XI (http://cgnsap32:50000/rep), click on Integration Repository for Design.

    Go to SLD by clicking on the u2018System Landscape Directoryu2019 in the above screen

    Click on Business Landscape and check for the Business Systems, which have the required Technical systems (cgnsap01, cgnsap13 in this case) and the required clients (800 of cgnsap01 and 800 of cgnsap13).

    We create a business system if the required business systems do not exist

    Creation of Business System:

    Click on New Business System and the following screen will appear.

    Enter the name of the Business System and click next.

    Select the type of the business system in this case its Web AS ABAP.

    Select the Technical System for the Business System.

    Select the required client.

    Select the Business system role and related integration server and click Finish to complete the creation of the business system.

    Design: Integration Repository

    1. Create a Namespace under component SATYAM_SAPXI_IDOC.

    2. Import the IDOC by using Import Wizard in the Imported Object in the Design time.

    3. Create a Message Mapping and drag IDOC Structure into Source Message and Target Message panes. Map the mandatory fields of the input and output IDoc structure. Save and activate the message mapping.

    4. Create an Interface Mapping for the IDoc.

    CONFIGURATION TIME:

    SCENARIO: Create a scenario in which all the objects will be created.

    Scenario Name: SAP_XI_IDOCTOIDOC

    Business System Name: SAP01 (for cgnsap01), SSI (for cgnsap13)

    As we are going to send IDOC from the system so no Sender Channel is required.

    SENDER AGREEMENT: No Sender Agreement is required.

    Communication Channel:

    Select IDOC Adapter and provide the details as shown below.

    RECEIVER DETERMINATION: In receiver determination, we have to specify the Service and Receiver details.

    INTERFACE DETERMINATION: Specify the service, interface and Inbound and outbound interfaces.

    RECEIVER AGREEMENT:

    Provide the sender service, receiver service and Receiver Communication Channel here.

    In the Header Mapping, select the Sender Service as the receiving R/3 Business system

    (SAP 01 in this case).

    Testing :

    To test all the configuration of IDOC which you have done follow this test procedure:

    Use transaction we19 for IDOC Processing.

    Give your IDOC and execute it.

    c) Then enter values in IDOC and save it.

    d) Check the values in the XI System using SXMB_MONI Transaction Code.

    Regards.

    Siddhesh

    Edited by: Siddhesh Naik on Nov 3, 2008 10:06 AM

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 03, 2008 at 04:57 AM

    Hi...

    Please find the below link,about how to configure IDOC adapters .

    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098

    Regards,

    Leela

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 03, 2008 at 06:55 AM

    Hello Bhaskar,

    Refer the below doc from SDN for more understanding.

    https://www.sdn.sap.com/irj/sdn/howtoguides?rid=/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660

    Regards,

    Jilan

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 03, 2008 at 07:46 AM

    Hey,

    You need to do following settings.

    Steps for ALE settings:-

    Steps for XI

    Step 1)

    Goto SM59.

    Create new RFC destination of type 3(Abap connection).

    Give a suitable name and description.

    Give the Ip address of the R3 system.

    Give the system number.

    Give the gateway host name and gateway service (3300 + system number).

    Go to the logon security tab.

    Give the lang, client, username and password.

    Test connection and remote logon.

    Step 2)

    Goto IDX1.

    Create a new port.

    Give the port name.

    Give the client number for the R3 system.

    Select the created Rfc Destination.

    Step 3)

    Goto IDX2

    Create a new Meta data.

    Give the Idoc type.

    Select the created port.

    Steps for R3.

    Step 1)

    Goto SM59.

    Create new RFC destination of type 3(Abap connection).

    Give a suitable name and description.

    Give the Ip address of the XI system.

    Give the system number.

    Give the gateway host name and gateway service (3300 + system number).

    Go to the logon security tab.

    Give the lang, client, username and password.

    Test connection and remote logon.

    Step 2)

    Goto WE21.

    Create a port under transactional RFC.(R3->XI)

    Designate the RFC destination created in prev step.

    Step 3)

    Goto SALE.

    Basic settings->Logical Systems->Define logical system.

    Create two logical systems(one for XI and the other for R3)

    Basic settings->Logical Systems->Assign logical system.

    Assign the R3 logical system to respective client.

    Step 4)

    Goto WE20.

    Partner type LS.

    Create two partner profile(one for XI the other for R3).

    Give the outbound or inbound message type based on the direction.

    Step 5)

    Goto WE19

    Give the basic type and execute.

    fill in the required fields.

    Goto IDOC->edit control records.

    Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)

    Click outbound processing.

    Step 6)

    Go to SM58

    if there are any messages then there is some error in execution.

    Goto WE02.

    Check the status of the IDOC.

    Goto WE47.

    TO decode the status code.

    Step 7)

    Not mandatory.

    Goto BD64.

    Click on Create model view.

    Add message type.

    BD87 to check the status of IDOC.

    In case if not authorized then go to the target system and check in SU53, see for the missing object

    and assign it to the user.

    regards,

    Milan

    Add comment
    10|10000 characters needed characters exceeded