Skip to Content

Context

The main purpose of this document is for leveraging the new feature i.e., IDOC_AAE (Java stack IDOC adapter) introduced in SAP PI 7.3 where as ABAP stack IDOC adapter was used till PI 7.11 version.This document will be useful who want to go with single stack from PI 7.3/PI 7.31 (AEX) and connect with SAP ECC using IDOC adapter, even dual stack (ABAP+Java) can use this IDOC_AAE adapter to connect to SAP apart from ABAP stack IDOC adapter.

Audience

SAP PI consultants, who are new to PI 7.3/7.31/AEX, want to leverage the IDOC_AAE adapter (Java stack)

Issues

1)Unable to post idoc into ECC from PI(ABAP Stack).

Error:Authorisation issue in sm58.

Solution:S_IDOCCTRL  and B_ALE_RECV roles added by securities team

2) Error in sm58 on posting idoc from ECC(Using Java AAE)

Error: Bean IDOC_INBOUND_ASYNCHRONOUS not found on host

Solution: Please make sure that the user has sufficient authorizations. You need the S_IDOCDEFT (EDI_TCD = “WE30”; ACTVT = “03”) authorization.

3) Problem in port setting (Not mandatory)

The default Sender port field is not mandatory but sometimes if you face issue then go for the below mentioned solution

Solution:Go to NWA

  1. Path:Configurations ->infrastructure->application resources
  2. Javaidoc resource adapter ->properties tab

Set the default Sender port field of your PI system

4) Authorisation issues

Error : No RFC authorization for function module IDOCTYPE_READ_COMPLETE.

Solution: You need to give to Service User, the right roles and authorization object to execute RFC function

Contents of the blog

Introduction.

a)Configurations in NWA.

b)Configurations at the Sender System (SAP ECC).

c)Design the Scenario in the Enterprise Service Repository.

d)Configure the Scenario in Integration Directory.

e)Testing the scenario.

Introduction

The purpose of this document is to show all the steps needed to configure an IDoc_AAE to file scenario

This document will help SAP PI consultants to understand the ALE (Application Link Enabling) and NWA settings needed to complete this scenario.

Systems involved in developing the scenario

·         Sender system : SAP ECC (SAPDEV_100) Client No -100

·         PI system : SAP NETWEAVER PI 7.3 (PIDEV_100) ) Client No-100

·         Receiver : Local File Directory (NFS)

Brief Overview of Configurations

a) Configurations in NWA

1)      Settings in Application Resources

2)      Create JCO RFC Provider destination

b) Configurations at the Sender System (SAP ECC)

1)      Create RFC Destination

2)      Create Port

3)      Create Logical System

4)      Create Partner Profile

c) Design the Scenario in the Enterprise Service Repository  

1)      Import the Required IDoc from Sender SAP ECC System

2)      Create Data Type for File structure

3)      Create Message Type for DataType

4)      Create Service Interface

5)      Create Message Mapping doing simple one to one mapping

6)      Create Operation Mapping

d) Configure the Scenario in Integration Directory

1)      Assign Business System for sender ECC

2)      Create Configuration Scenario

3)      Create Receiver Business component

4)      Create Sender Communication Channel

5)      Create Receiver Communication Channel

6)      Create Integrated Configuration

e) Testing the scenario

1)      Trigger the IDoc from ECC

2)      Check the triggered idoc message in PI Adapter engine in RWB

3)      Check whether the Message is received in your file system.

Detailed description of the steps

a) Configurations in NWA

Open NWA page

1) In NWA navigate  to the below path:

     Configuration –> Infrastructure —-> Application Resources

/wp-content/uploads/2012/09/1th_135398.png

Enter “inboundRA”  in the Resource Name and click on filter icon

Select Resource Adapter, inboundRA

/wp-content/uploads/2012/09/2ndimage_135399.png

Click on “Properties”

Enter a value for “MaxReaderThreadCount”  between 5 to 10

Enter “true” for Local

/wp-content/uploads/2012/09/3rd_135400.png

XI_IDOC_DEFAULT_PIDEV,PIDEV refers to the PI system ID.

/wp-content/uploads/2012/09/4rth_135401.png

The ProgramID visible here, XI_IDOC_DEFAULT_ PIDEV, must be used when creating the RFC destination of type T on the ECC system

2) Create JCO RFC Provider destination

In NWA navigate  to the below path:

Configuration –>Infrastructure –>JCO RFC Provider

Create JCO RFC Provider destination with name XI_IDOC_DEFAULT_ PIDEV  in NWA where PIDEV refers to the PI System ID.

/wp-content/uploads/2012/09/5th_135402.png

/wp-content/uploads/2012/09/6th_135403.png

Enter Gateway host and gateway service of your PI system.

b)Configurations at the Sender System (SAP ECC)

This section describes all the configurations needed in the Sender SAP System (ECC) for sending an IDoc to PI

1. Create RFC Destination

On your SAP ECC system in order to send the IDOCs you need to create an RFC destination of type T (TCP/IP)

Go to Transaction SM59 create a new RFC destination of Type T

1.         1.    Select the radio button Registered Server Program

2.      In the program ID enter the program ID from inboundRA of NWA(explained in the later part of the document)

3.      Enter  the gateway host and gateway service of your PI  server

/wp-content/uploads/2012/09/7th_135404.png

In PIDEVCLNT100_AAE  and  XI_IDOC_DEFAULT_PIDEV , PIDEV refers to the PI system ID.

Scroll down and fill the following details

/wp-content/uploads/2012/09/8th_135405.png

Enter Gateway host and gateway service of your PI system.

After you configure that you should be able to check the configuration using the test connection button on the RFC destination.

/wp-content/uploads/2012/09/9th_135406.png

2. Create Port

Goto Transaction WE21

1.      Click on the Transactional RFC from Ports (left tree panel)

2.      Click on Create Button

3.      Give Port Name(SAP<SID>)here or select generate port name and click on continue. In my example I have given as SAPPIDEV _AAE(PIDEV is PI System Id and _AAE for better understanding)

4.      Give the description of the port and select RFC destination of type T created above. Now click on save.

/wp-content/uploads/2012/09/10th_135407.png

3. Create Logical System

Goto Transaction BD54

1.      Click on create Button

2.      Give name for your Logical System PIDEVCLNT100( <SID>CLNT<ClintNo.>)where PIDEV  is PI System ID and  100 is client  Number .

3.      Now click on save

/wp-content/uploads/2012/09/11th_135408.png

4. Create Partner Profile

Create Partner Profile with outbound parameter (WE20) to be send to the PI receiver system

1.      Go to Transaction WE20

2.      Select Partner Type LS

3.      Click on Create Button

4.      Give Logical System Name which we have just created in step 3 as Partner No, Partner Type should be LS , Agent (some valid data) ,Language (EN). Now click on Save

5.      Now create an Outbound Parameter.

    • Select the required Message Type.
    • Select the Receiver Port (which we have created in step 2 SAPPIDEV _AAE in this example).
    • Select Transfer IDoc Immediately option in Output mode for Immediate Testing. Select Basic Type Save.
    • Enter all credentials in the post processing permitted agent tab.

    /wp-content/uploads/2012/09/12th_135409.png

We can see Message Type is added in the outbound parameter.

13TH.png

c) Design the Scenario in the Enterprise Service Repository  

1) Import the Required IDoc from Sender SAP ECC System

2) Create Data Type for File structure

/wp-content/uploads/2012/09/14th_135411.png

3) Create Message Type for DataType

/wp-content/uploads/2012/09/15th_135412.png

4) Create Inbound Service Interface for File

/wp-content/uploads/2012/09/16th_135413.png

5) Create Message Mapping doing simple one to one mapping

/wp-content/uploads/2012/09/17th_135415.png

6) Create Operation Mapping

/wp-content/uploads/2012/09/18th_135419.png

d)Configure the Scenario in Integration Directory

Prerequisites

1)Assign Business System for sender ECC

2)Create Configuration Scenario

3)Create Receiver Business component

/wp-content/uploads/2012/09/19th_135420.png

4)Create Sender Communication Channel using IDOC_AAE adapter

/wp-content/uploads/2012/09/20th_135421.png

Select Default(recommmended) in RFC Server Parameters

The Ack Destination can be left blank or the value given as above

5)Create Receiver Communication Channel

/wp-content/uploads/2012/09/21th_135422.png

6)Create Integrated Configuration

/wp-content/uploads/2012/09/22nd_135423.png

Select appropriate sender and receiver components, channels in different tabs of integrated configuration.

e)Testing the scenario

1)Trigger the Idoc from ECC system.

  • Enter the tcode we19 to trigger the idoc
  • Search with message type  of idoc(ORDRSP) that you want to trigger, and then select the idoc type (ORDERS05)
  •   We will get Idoc with all its segments
  • Click on the control segment that is EDIDC in this idoc and fill all the sender and receiver details like Port,Partner No and partner type.
  • Then select any other data segment and populate values in the idoc
  • We will get a message as IDoc sent to SAP system or external program
  • After entering values click on the tab standard outbound processing on the top to trigger the idoc.

2) Check the triggered idoc message in PI Adapter engine

     Navigate to Runtime work bench

     Go to Message Monitoring Link, Select Adapter Engine from the combo box Messages from component and click on display button

    You can see the message here with success status

3) Check whether the Message is received in your file system.

     Since we have selected NFS in our channel, we check it in al11 tcode in PI system.

     Go to the target directory that you specified in your channel. You can find your file being placed there.

To report this post you need to login first.

29 Comments

You must be Logged on to comment or reply to a post.

  1. Alejandro Ferrara

    Good guide. I followed all steps and Idocs are getting stucked in ABAP. SM58 says Error: Bean IDOC_INBOUND_ASYNCHRONOUS not found on host as you said in Issues (2).

     

    Could you tell me wich user must I check the authorizations? You don’t specify it in the solution.

     

    Thank you in advance.

    (0) 
  2. Carlos Ocampos

    Good work!

    But just one comment:

    You don’t need to do the second step in NWA.

    2) Create JCO RFC Provider destination

     

    JCO RFC Provider destination is not neccesary for this config.


    Kind regards.

    (0) 
  3. Bhargava krishna Talasila

    Hi Swathi,

     

    i have one query..

     

    As you mentioned in b) step 1) RFC destination

     

    Enter  the gateway host and gateway service of your PI  server.

     

    I think this should be ECC host and gateway service.

     

    im getting error ” Program id not registered “.

     

    please Confirm me..

     

    Regards

    Bhargava krishna

    (0) 
      1. Bhargava krishna Talasila

        Did you register the program id in SAP Gateway and in NWA?

         

        Also you need to provide ECC gateway host and service details in NWA –> Application resources–> inbound RA –> resource adapter –>properties..

         

        Check that.. once.. hope it will work..

         

        Regards

        Bhargava krishna

        (0) 
      2. Senthilnathan Natarajan

        Hi Krishna,

        After providing the ECC gateway host/service in NWA->properties, I am able to get the RFC detsination working.

        Thanks for pointing me in the right direction.

         

        Senthil

        (0) 
  4. Jorge Huedo

    Hi guys,

    I’m trying to perform this configuration but I’m stuck with the RFC Destination in ECC.

     

    Let’s recap what I have done:

    • Create Destination in PI (XI_IDOC_DEFAULT_DESTINATION)
    • Config the inboundRA
      • 5 and true, and the PI Gateway (I’m not 100% sure about this).
      • Also our program id XI_IDOC_DEFAULT_P21
    • Create destination in sm59 type T using our program id and as gateway the pi gateway.

     

    And I’m having the next error:

     

    Logon    Connection Error

    Error Details    Error when opening an RFC connection

    Error Details    ERROR: access denied for tp XI_IDOC_DEFAULT_P21 from host ecchost

    Error Details    LOCATION: SAP-Gateway on host P21CE73 / 3301

    Error Details    COMPONENT: SAP-Gateway

    Error Details    COUNTER: 278

    Error Details    MODULE: D:/depot/bas/740_REL/src/krn/si/gw/gwxxreg.c

    Error Details    LINE: 667

    Error Details    RETURN CODE: 748

    Error Details    SUBRC: 0

    Error Details    RELEASE: 740

    Error Details    TIME: Wed Aug 21 16:29:23 2013

    Error Details    VERSION: 2

     

    I know that the program id is working because if I change it return that the program id is not valid, also the technical user I’m using has SAP_ALL so it shouldn’t be a problem.

     

    Any ideas?

    Thanks.

    Jorge

    (0) 
    1. Bhargava krishna Talasila

      Hi Jorge,

       

      you need to provide ECC gateway host and service details in NWA –> Application resources–> inbound RA –> resource adapter –>properties..

       

      It is connection issue, re-check your gateway host and service details.

       

      Please check it once.

       

      Regards

      Bhargava krishna

      (0) 
      1. Satish Dhanalakoti

        Hi,

         

        We too faced the same issue and we fixed it by modifying the Reginfo file of PI and ECC system.

         

        By definition, the Gateway host and service should be of PI server only in NWA and in ECC’s RFC.

         

        Please make the changes in Reginfo file to allow the program-id to be registered and accessed in ECC.

         

        Regards,

        Satish Dhanalakoti

        (0) 
        1. Jorge Huedo

          Thanks Satish,

          We found that from PO 7.4 the security in gateway is activated by default.

          We had two diferents PIs one in 7.3.1 and another in 7.4 and with the default installation was working in the 7.3.1 and not in the 7.4.

          We set the parameter gw/acl_mode = 0 in the PO box worked fine.

          Thanks

          Jorge

          (0) 
  5. Arun Kumar

    Good document .

    As already a couple of colleagues  pointed out, no need to set up JCO RFC provider .

    Program id set in InboundRA adapater properties  will be used for setting up TCP/IP destination in ECC side

    Gateway  service of PI  should work just fine ( in the adapter properties setting local gateway property ;true’) as long as the gateway service name is specified correctly with PI host name and ACL parameter is set to allow registerign services and using externally

    Regards

    Arun

    (0) 
  6. jafer shaik

    I have done all the NWA CONFIGURATIONS,I am confused while triggering the IDOC through WE19 T.code what we have to give the Sender and Receiver PORT,Partner No for trigerring. Please help me out this is a IDOC_AAE to FILE scenario Single stack SAP PI 7.3

    (0) 
  7. Aditya Sharma

    The most important thing missing is integrated configuration.Definition of inbound/outbound interfaces in business component and systems is missing too.

    It would have been better because without it still some hit and trial has to be done.

    (0) 
  8. durga gidugu

    I think I’m late to the party, looks like the MaxReaderThreadCount plays crucial role. In my case we had IDOC’s stuck in SM58 and RFC to PI server was failing with erro “PROGRAM REGISTER FAILED”

     

    The value of ThreadCount for the inboundRA was set to 5 which was earlier 0, restarted the services and it works all fine. Also gw/acl_mode parameter to be set on PI server

     

    BTW.. good blog swathi.!

    (0) 
  9. chandar t

    Hi Swathi,

     

    Thanks for the nice blog. Can you please carify on BD64, model veiw controller setting is required here or not?

     

    Thanks,

    Chandar T

    (0) 
  10. Philomena steffy

    Hi Swathi,

          I have a doubt of what needs to be filled in sender and receiver information while triggering outbound IDoc(we19).

     

    Regards,

    Philo

    (0) 
  11. Ashok Avula

    Hi swathi,

    I strucked in T RFC connection, while i’m testing RFC Connection its throwing below error.

    In NWA configurations application resource InboundRA is  not available..

    please help me and suggest.

     

    Thanks &Regards,

    Ashok

    (0) 

Leave a Reply