Skip to Content
avatar image
Former Member

What is the use of configuring ALE Settings in ECC System in IDOC Scenario?


Can any buddy explain me why we are creating RFC destination,port,partner profile, logical system,Distribution model? and Please explain me IDOC_AAE to IDOC_AAE scenario in single stack pi 7.31.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Jun 21, 2017 at 09:31 AM

    Hi Siva,

    These are very broad questions that I don't feel can be answered extensively on a support forum like this. You are basically asking us to teach you the nuts and bolts of SAP integration and then divert into a specific PI scenario.

    I would recommend that you take a few hours to familiarize yourself with the basics of SAP ALE by reading up on the topic in SAP Help, putting it in Google (which will yield dozens or hundreds of tutorials), or investing in one of the IDoc-related books from SAP Press. Once you have understood that, you can start learning about PI.

    To give you a few pointers on the objects you asked about:

    A Partner Profile represents a communication endpoint that you are interacting with in an ALE scenarios. The profile must either reference a master data record (for Bank, Benefits Provider, Business Partner, Customer, Vendor or User Profiles) or a customizing entry (for Logical Systems, i.e. other SAP or non-SAP systems that you want to communicate with but that are not representing one of the other functions).

    Inside the partner profile, you configure for each message type that you want to exchange with the entity represented by the profile, how that message should be handled. For outbound messages, that includes specifying a destination where the message should be sent. That destination is represented by a port. A port can have many different types. In most cases, you will be using a Transactional RFC port (to send and IDoc to another SAP system via RFC). An RFC Port points to an RFC destination, which contains the physical connection parameters of the system you want to integrate with. So the port is the logical destination and the RFC destination is the physical destination.

    A distribution model is used primarily in Master Data Distribution scenarios. It serves as a filtering objects that tells the ALE process which IDocs are really relevant for a particular system. For instance you may want to limit the distribution of master data to an Asian CRM system to Customer and Material Master IDocs relevant for Asian Sales Organizations.

    There is a lot more to know - books have been written about this - but as I said earlier, I don't think you can get a comprehensive answer in the form of an SCN forum post.


    Add comment
    10|10000 characters needed characters exceeded