Showing results for 
Search instead for 
Did you mean: 

Basic Dought.. In Integration Repository

Former Member
0 Kudos

Hi All,

Any body Explain me the below topics

<b>Integration Scenario & Integration Process</b>

- Integration Scenarios,

- Action,

- Integration Processes,

<b>Interface object</b>

1. message Interfaces

2. message type

3. fault message types

4. data types

- exchangefaultdata

- exchangeLogData

5. Datatype Enhancements

6. Context Objects

7. External Definitions

<b>Mapping Objects</b>

- Interface Mapping

- Message Mapping

- Mapping Templates

- Imported Archives

<b>Adapter Objects</b>- Adapter Metadata

- Communication Channel Template

This information very use full to me

Thanks & Regards

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos


I have taken some time off for you and have given the best possible explanation for the doubts you have.

<b>Integration Scenarios:</b>

An integration scenario completely models the exchange of

messages for a collaborative process and provides an overview of the process flow.

Please go through this link for further reference:

<b>Integration Processes</b>

An integration process is an executable, cross-system process for processing messages. In an integration process you define all the process steps that are to be executed and the parameters relevant for controlling the process.

You implement integration processes when you want to define, control, and monitor complex integration processes that extend across enterprise and application boundaries. The design and processing of integration processes is also known as cross-component Business Process Management (cross-component BPM, ccBPM).

Please go through this link for further reference:


<u>Interface object</u></b>

<b>1. message Interfaces</b>

ou use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure.

Please go through this link for further reference:


2. message type</b>

A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type

Please go through this link for further reference:


3. fault message types</b>

Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.

Please go through this link for further reference:

<b>4. data types</b>

A data type is a basic unit for defining the structure of the data for a message type and, as a result, for the message to be exchanged.

Please go through this link for further reference:

exchangefaultdata and exchangeLogData

All fault message types reference the data type ExchangeFaultData for this part and, indirectly, the data type ExchangeLogData. These data types are automatically created in a namespace when you create the first fault message type there.


5. Datatype Enhancements</b>

SAP applications enable customers to enhance application source code without making modifications and thus to meet customer-specific requirements that are not provided for in the standard shipment. The applications can use Business Add-Ins (BAdIs) for this purpose. Furthermore, if customers use applications that exchange messages by using XI, they can define data type enhancements for Integration Repository data types.

Please go through this link for further reference:

<b>6. Context Objects</b>

Context objects are a simple alternative to XPath expressions for accessing the contents of a message.

Please go through this link for further reference:


7. External Definitions</b>

External definitions enable you to import WSDL, XSD, and DTD documents to the Integration Repository so that you can access the message definitions they contain as external messages.

Please go through this link for further reference:

<b><u>Mapping Objects</u>


<b>Interface Mapping</b>

Interface mappings register your mapping program for an interface pair in the Integration Repository.

Please go through this link for further reference:


Message Mapping</b>

Please go through this link for further reference:


Mapping Templates</b>

Just like you can reuse data types in different message types, you can also save parts of message mappings as Mapping Templates and reuse them elsewhere. Once you have saved a mapping template it serves as a copy template that you can then load into other message mappings and modify to fit your requirements.

Please go through this link for further reference:

<b><u>Adapter Objects</u></b>

<b>Adapter Metadata</b>

With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.

Please go through this link for further reference:

<b>Communication Channel Template</b>

You can preconfigure a communication channel with a communication channel template. You can use the communication channel template as a template to define a communication channel at configuration time.

Please go through this link for further reference:

I am sure i have clearly explained your doubts.




Answers (5)

Answers (5)

0 Kudos

1.Integration Scenario:It completely models the message exchange and process flow of collaborative process.

It gives clear picture of what are all the desing objects

(Data type,Message type, Message interface,Message mapping,Message Interface)

It is template for generating configuration Objects(Receiver determination,Interface Determination,Receiver aggrm).


An action represents a function withing an applicaton component, that is not subdivided.It is an independent desing object.

3.Integration Process:Integration Process in an executeble collaborative process.

Interface Objects

1.Message Interface

It is utershell of messages to be exchanged.It is entry point, can be compared with port.The attributes of Message interface are mode and type communication.

2.Message type:It describes actual message to be exchanged by referring data type.

3.Data type:It specifies what are the attributes and fields are user to construct a message.

4.Fault Message type: It enables developers to send information about the errors in the receiver application program to the sender.

5.External Definition:

To describe message schema WSDL,XSD,DTD are often used.If description of message structure already exists in one of the above formats you can use it in the IR by importing an external definition.

Message Mapping

Message mapping refers to a mapping of messages and is supported by a graphical editor.

interface mapping:

It registers your mapping program for an interface pair in IR.



iGATE Global Solution Ltd Hyderabad 91-98490 65377

Active Contributor
0 Kudos

Hi Reddy,

i ll try to make it as simple as possible,

<b>Interface object</b>

1. message Interfaces

This is the means in which message is transfered to and from XI. Every Message Interface is inbound, outbound, abstarct, synchm, and asynch. the message interaces are used in sender agreement / receiver agreement and used to bound to a communication channel.

2. Message Type

As interfaces are used for flow of messages, a message type message type comprises a data type that describes the structure of a message. Same message type can be used in many Interfaces

3.Data Type

Basic unit defining the structure of your data

4.External Definitions

Instead of defining a data type, you can import an XSD called as an External Definition.

5.Context Objects

These are used to define your XPATH in a simple fashion.

Interface Mapping

This is used to transform the message from one interface into the format of another interface. They make use of message mapping.

Message Mapping.

These are used to transform the message type from one format to another. For every message mapping atleast one interface mapping has to be created.

Imported Archives.

You can import an external Mapping program ( java / XSLT ) mapping under imported archive and use them for your mapping program for interface mapping

Integration Process

this is used to define you BPM.



Former Member
0 Kudos

Hi reddy,

u can goto <b></b> and get the definition for the concepts in detail else refer to this link



Active Contributor
0 Kudos

Hi Redddy,

Just Search for each of these topics in this help link and you wil find all the information that u need.



Former Member
0 Kudos

Hi Bhavesh,

Just i need Defination.. please do need ful..

Thanks and Regards


Former Member
0 Kudos

Hi Reddy,

I think the best way would be to read it hrough

SAP XI has basically Design time and Configuration time.

What you want explanations on are objects in Design time.