information

[Former Member]

Hi All,

In IR there is Integration Scenario & Integration Process.

what is the advantage of using Integration Scenario & process as the whole process is implimented in ID ..

so why we use in it

[Former Member]

Hey,

Having a clear Understanding Of The Basic Concept of <b>SLD</b>, <b>IR</b> and <b>ID</b> is

Important.

<b>SLD:</b> SLD is the central information provider in a system landscape. Contains two types of information.

<b>Component Information:</b> Contains the information of all available products, components including their versions.

<b>Landscape Description:</b> Contains information of all installed systems on a system landscape

Further info on [<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/31/f0ff69551e4f259fdad799a229363e/frameset.htm">SLD</a>

<b>Integration Repository:</b> Gathers all the objects that are relevant for shipment.

<b>Intergration Directory:</b> Objects have to be configured at the customer site for that system landscape.

For info on IR and ID please follow the link [<a href="http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm">Integration Builder</a>

My assumption behind the Concept of IR and ID by sap could have been to facilitate model of offshore - onsite model and better managability and abstraction of objects.

Cheers,

*Raj*

<b>*REWARD POINT IF USEFULL*</b>

[former_member184619]

Hi Anushree,

Check my reply in this thread.

Sachin

[Former Member]

Hi Refere this forun for a similar query

https://forums.sdn.sap.com/click.jspa?searchID=3723897&messageID=3698799

Mudit

[Former Member]

hi,

Integration Builder: Design - Integration Repository : IR

Integration Builder: Configuration - Integration Directory : ID

Here we will create all objects in IR independently of a System landscape those will be stored in Repository and using those object will be configured in ID. while execution first ID object will be executed from ther it will refer the ID object in runtime.

It means At configuration time you set up a collaborative process for a specific system landscape. The configuration data is structured, organized, and saved in the Integration Directory in the form of configuration objects.

for example

Receiver Determination - Interface Determination --

Interface mapping will be executed in ABAP cache while execution it reffers the Message mapping , the MM will be executed in JAVA Cache.

[Former Member]

hi

As shabrish said it is correct the thing why this integration process and scenario exits in both the IR and ID means actually this integration process or scenario is used in BPM and more thing we can create the scenarios in Integration repository and can be imported into the Integration Directory when we require.

Reward points is useful,

Regards,

Srinivas.D

[Shabarish_Nair]

<i>what is the advantage of using Integration Scenario & process as the whole process is implimented in ID ..</i>

>>>

First, The integration scenario provides you with a central point of access for all objects that you require for semantic and technical integration, for example interfaces, mappings, and software components.

Then in ID all you need is to import the same, so that the manual task of creating your ID objects are automated.