cancel
Showing results for 
Search instead for 
Did you mean: 

MESSAGE MAPPING AND INTERFACE MAPPING

Former Member
0 Kudos

Hi all,

what s the differnce between msg mapping and interface mapping?

Regards,

rao

Accepted Solutions (1)

Accepted Solutions (1)

GabrielSagaya
Active Contributor
0 Kudos

Message mapping

*********************

1) Transformation from one message structure to another message structure

2) Message Mapping is nothing but a set of rules for producing target XML from the source XML according to business requirement.These rules are nothing but relations between the source XML tags and target XML tags

3) 4 types(graphical, java, xslt, abap) mapping

4) You can check whether a complete message mapping functions at runtime once you have described it, by using the Test tab page.

Interface mapping

*********************

1) Interface mapping registers a pair of interfaces for a scenario and specifies the message mapping to be used

2) you can execute multiple mapping programs consecutively

3) To check whether an interface mapping that you have defined functions at runtime, test the interface mapping on the Test tab page.

Limitations

************

1) value mapping table cannot be accessed here

2) runtime constants of the mapping runtime are not set,but set to dummy values.

Answers (4)

Answers (4)

vijay_b4
Active Contributor
0 Kudos

Hi Rao,

Message Mapping

Here you can map the source and target messages.

Interface Mappings

Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time (see: Defining Interface Determinations). The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response messages, fault messages, or all three.

Reward points if this helps

Regards

Vani

former_member556603
Active Contributor
0 Kudos

Hello Rao,

Interface Mapping

● You can reference interfaces from any software component version.

● You can reference mapping programs (message mappings, XSLT or Java mappings) from the same namespace and the same software component version as the interface mapping.

Message Mapping

You can reference any message types or the request/response/fault part of an imported interface.

It is also possible to reference non-independent objects. See: Message Mappings and References Between Mapping Programs.

Interface Mappings

Use

Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time (see: Defining Interface Determinations). The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response messages, fault messages, or all three.

Interface Mappings

When defining mapping programs for request, response, or fault messages, the definition is first separated from the interfaces that reference the corresponding message types. Furthermore, you can reuse a message type for multiple interfaces. This means that the simple definition of a mapping program is not sufficient to establish a connection (that is based on the assignment of outbound and inbound interfaces).

This role is undertaken by the interface mapping:

● An interface mapping specifies the corresponding mapping programs for request, response, or fault messages for a selected interface pair. You use an interface mapping to register mappings for an interface pair.

● You can also specify multiple mapping programs to be executed one after the other in the case of requests and responses for an interface mapping.

You can also define multiple interface mappings for the same interface pair, to provide multiple variants in the Integration Repository. At configuration time, the customer can select the appropriate mapping in an interface determination and save it in the Integration Directory.

http://help.sap.com/saphelp_nw04/helpdata/en/12/05731a10264057badc32d3d3957015/content.htm

Message Mapping:

Purpose

Mapping maps a source structure to a target structure. There are various reasons why this may be necessary:

A business partner expects other technical field names or another structure for transferring data.

http://help.sap.com/search/highlightContent.jsp

Thanks,

Satya

Edited by: SATYA KUMAR AKKARABOYANA on May 15, 2008 5:21 PM

Former Member
0 Kudos

Hi,

message mapping:

In message mapping, different message structures are mapped to each other. The mapping is supported by a graphical mapping editor. The editor enables you to design a structure mapping between any two XML structures.

The mapping editor generates Java source code from the graphical mapping description that is then compiled and packed in a JAR file that the PCK executes at runtime.

The mapping editor can load the following schemas into the structure overview:

XML schema definitions (XSD) or XML files from a local file

Schemas from another PCK

In the case of XSD files, the mapping editor generates an XML representation for both the source structure and the target structure. If the XSD file contains more than one global element, use a dialog box to select one global element as the root element.......Once you have created a message mapping, the system navigates to the mapping editor Design tab page.

Interface mapping:

Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time.

You can also create multiple interface mappings for the same interface pair

reward points if its helpful

Thanks,

Madhu

Former Member
0 Kudos

Hi rao.

In a message mapping you declare how the source message will be mapped to the the target message.

What source field will be mapped to the target field and any conditions for it to happen.

In the interface mapping you define what interfaces that will be communicating with each other. You will also see what message mapping the interfaces are using to exchange data. You need to do the message mapping before you do the interface mapping to get it correct.

BR

Andreas