XI message interface type

Hi ,
I have scenario file-XI-R/3.I am not doing any mapping.
I have created 2 message interface say MOUT of type outbound with message type MT1 and MIB of type Inbound with message type MT2.
In Integration directory by mistake I have put MIB everywhere in sender and Receiever interface.But to my surprise everything worked fine and XI has not given any error message.Accoding to documentation we should use message interface of type outbound inorder to send data to XI.
Does anybody have any idea what could be wrong?
Thanks.
Rekha

Are you using proxy on R/3 side ?
If so then direction does matter in this case. Since the proxy interfaces/classes are generated based on your inbound/outbound interfaces.
To generate inbound proxy you should have inbound interface. But looking at the problem description should'nt be problem since you have used inbound interface MIB on as a sender and receiver.
The messages in R/3 are in open staus or XI ?
You can logon to R/3 and use SXMB_MONI to monitor incoming messages. Check the status of messages in R/3 aswell.
Regards
Anand
Message was edited by: Anand Torgal

Similar Messages

Message interface with two types of message types

Hi experts,
I am having problem that a proxy cannot be generated because of the (mixed) types of the message types that the interface is using.
The first message type is defined in the repository and another is defined as an external definition, imported in from an outside source.
Here is the SAP message I received when I tried to generate the proxy for this interface.
+++++++++++++++++++++++++++++++++++++++++++++
Interface uses external and internal message definitions
Message no. SPRX122
Diagnosis
In a message interface you can use messages from different sources:
1. Message types and fault message types edited in the Integration Repository
2. Messages imported into the Integration Repository (external definitions, RFC, IDoc)
In the current message interface, message types from different sources have been used.
Since messages from these different sources must be handled differently during proxy generation, such a mixture of messages within a message interface is not possible.
System Response
The interface cannot be generated.
Procedure
Change the interface definition accordingly in the Integration Repository.
++++++++++++++++++++++++++++++++++++++++++
The imported xsd is quite large and also contain many large includes. I don't have the option of creating the message type manually.
Any suggestions?
Thank you,
-michelle

Hi all,
I tried several things and the problem is still not resolved. This is what I learned.
First of all, I believed the SAP message about mixing of internal and external message is misleading or even wrong. I tried with both message types being external but I still get the same message that the interface has one internal and the other external message type.
Secondly, since Arvind suggested that I might have used an xml element that is not currently supported by ABAP proxy, I then change to another definition with the most simplest elements. I then attached this other definition to the interface and tried generating the proxy again. I still get the same system message that I am using mixing of message types in one interface.
My conclusion is XI still is not capable of generating ABAP proxy from external definition.
Does anyone have any comments/suggestion/experience on this issue?
Best regards,
-michelle

Data &message types,message interface, interface&message mapping

hi
I am very new to XI, i want to know about
1) Data Types
2)Message Types
3)message interface
4) interface mapping
5)message mapping
i am totally confused with eachother, can you please give me the clear definitions for these things
regards
pradeep

Hi Pradeep,
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
->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.
A data type is an XML Schema Definition (XSD). This definition determines how the valid payload of a message will look. Data types in XML schema are only an abstract description of a structure that you can assign to elements in an XML schema definition. A message type or a fault message type that references a data type determines the name of the root element of a message.
Ref link
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
2)Message Types
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:
· More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.
· When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.
3)message interface
You 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.
4) interface mapping
Interface mappings register your mapping program for an interface pair in the Integration Repository.
5)message mapping
A message mapping refers to a mapping of messages and is supported by a graphical mapping editor. The editor enables you to design a structure mapping between any two XML structures and connect to a value mapping.
Follow these Ref Link for all answers...
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Regards,
Ramesh.

Need of datatype, message type and message interface

hai
can any one tell me..
why we need three level heirarchy for a message in XI
regards,
Madhav

Hi Madhav,
let us recall them by their name and identify their roll.
Data type : suppose that you want to form a message but that comprises of many different types of data . as in numeric, string, characters.So at bottom you will have to define datatype.
Message Type: having defined data type now you want to form a meaningful message and that message can be formed by combining many such different data types in to one message type.
Message interface : No you have created message type but now that you want to use it some where, then you will have to interface it. So you will hace to define a message interface.
Vishal
Please reward with points for useful Help

Expression must return the interface type in Transformation Step in BPM

hi,
We are getting below while activating the IP,
Expression must return the interface type SI_Send_AA
Expression must return the interface type SI_Get_AA
No semantic errors found
We have a Transformation Step in BPM,
In OM, Source is SI_Send_AA and Target is SI_Get_AA
Also Container variable points to the same Abstract SI's.
Few Thread's for Same are error are:
Error in BPM
expression must return the interface type
Transformation step in ccBPM scenario
Error while compiling Business Process
Even after checking these i am getting this Exception.
Please Help!
Thanks,
Mayank

Also Container variable points to the same Abstract SI's
Are you sure that you are using Abstract Message Interfaces only and that these are referring to relevant container variables.
Normally it happens that there is some mis-match between the message types/ interfaces that we use in the mapping and that we use in the BPM.
If still not solved, then delete the Transformation step --> save --> activate......then again Edit the BPM to include the Transformation Step.
Regards,
Abhishek.

Message interface does not exist in any software components

Hi masters,
I'm having problems with this message in my repository when I try to create an Interface determination with two interfaces mapping: "Message interface does not exist in any software components installed on this business system".
note: I have read all the posts about this problem but nothing has solved it.
I will describe more or less how is my SLD.
First all, my Technical System is an Web AS ABAP (non a third party).
I have created two receivers determination, with out problems, then, created the interface determination, with two Inbound interface, BUT, when I create a condition, the message appears, and the XPath doesn't shows the nodes for do the condition..
I have checked the GUID, and that's good.
NOTE: I have a second SWC but this is a third party... and when I test to do the same in this system, I have NO problems... so.. what is wrong with the Web As ABAP?
Regards and thanks

did you mean:
SLD -> Technical System->Technical System Type: WebAsAbap-> Installed Products->Add New Product and add my Software Component???
if is this, I have already done this, and still doesn't works.
Thanks

Creation of Server Proxy for Message interface with External Defination

Dear All,
I am getting a problem while generating a server proxy for the inbound interface . The request message used in the inbound interface is a external definition which is uploaded using a XSD file. The XSD file was supplied by a third party which is having very high complex strucuture and used lot of abstract data types in the design. When i tried to generate the proxy in the R/3 system (Transaction SPROXY) for the inbound interface i am getting following error.
Interface uses external and internal message definitions
Message no. SPRX122 *
Diagnosis
In a message interface you can use messages from different sources:
Message types and fault message types edited in the Enterprise Services Repository
Messages imported into the Enterprise Services Repository (external definitions, RFC, IDoc)
In the current message interface, message types from different sources have been used. Since messages from these different sources must be handled differently during proxy generation, such a mixture of messages within a message interface is not possible.
System Response
The interface cannot be generated.
Procedure
Change the interface definition accordingly in the Enterprise Services Repository.
Please guide me, how to generate the proxy for the interface with external defination message. I could nt geneate manullay, because it is having very high complexity and its a big structure.
Is there is any way to generate the proxy for interface with external definition
Regards
Vijayanand

Hi,
i. Import your message schemas from external definitions, or RFCs or IDocs from SAP systems. These definitions already contain data types.
ii. Create a message interface and reference the messages of the external definition, or the RFC or IDoc message.
Check this, it may help you
http://help.sap.com/saphelp_nw04/helpdata/en/3f/01623c4f69b712e10000000a114084/content.htm
REgards
Seshagiri

Error: Message interface is not used by this process Netweaver PI 7.0

Hi All,
I am receiving this error in file to idoc scenario. The file is being picked up by communication channel. Then through an interface mapping IM_MET_ROUTE is being forwarded to a BPM MET_FILE_ROUTE. The MET_FILE_ROUTE forwards it to different BPM depending on file type. whenever I am posting a file it is not reaching IM_MET_ROUTE and giving an error as shown below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you please suggest any solution to remove the error.

Hi All,
Thanks a lot Vikrant for your suggestion. The error is resolved. This was not a configuration problem. This was a design problem. Initially I also looked for configuration changes but that was correct hence I came to conclusion that this might be a design isuue.
These are the steps that we should follow to resolve the errors
1. First Check your configuration again and again with test tool and payload to find where exactly your configuration is failing.
2. The above step will not be successful since we are already receiving the error.
3. The above test will fail in interface determination step.
4. Please go through the interface determination in Integration repository(PI 7.0).
5. Check whether all interface mapping,source and target message interface are proper or not.
6. if receiver or sender of message is an BPM please look into their receiver and sender element message type.This must match with the one specified in Interface mapping defined within Integration directory( in the interface deterination step).
In my case the sixth step above was the solution.

BPM : Message interface is not used by this process

Hi,
In BPM : to pass the message facing error as below.
Messages not reflecting in BPM monitor.
I have configured Recveiver - transformation - sender in BPM.
In recvier in BPM is configured with Abstract Type as same in the message mapping.
Is there any thing i am missing?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have refered links but not able to get the clue for this error as its from the Call adapter.
error: Message interface is not used by this process Netweaver PI 7.0
BPE_ADAPTER: MESSAGE_NOT_USED
Regards,

Hi,
I just saw your IP design and from this I can see that you have message mapping between Sender(as in Outbound interface MIOASY) and abstract interface (as in MIAASY) and then in that you have used transformation step to utilise Interface mapping which is between same abstract interface which is not required at all as message type for both the interfaces is same. For me, what your configuration would be is
1. Sender agreement to fetch the message from outbound interface(MIOASY) utilising communication channel with whatever adapter you have used
2. Receiver Determination with Sender and sender interface as MIOASY while receiver as IP(Integration process)
3. Interface determination between
    a. Sender and Outbound interface and Abstract interface with interface mapping IM_Sender
    b. IP as sender with abstract interface MIAASY and receiver interface MIIASY with no interface mapping being used as it must be of same type as receiver interface is
4. Receiver agreement with MIIASY being used as receiver interface and communication channel utlililsed to convert it into receiver format.
If I am assuming it correct then if you see then inside BPM we are not using receiver interface MIIASY which is why I feel this error is coming.
However, if you design it something like this then I feel the error would get resolved
Design
1. Make one abstract interface (MIAASY_Sen) of same type as sender, and create another abstract interface (MIAASY_Rec) of same type as your receiver message type
2. Create message mapping between sender message type and receiver message type, Interface mapping IM_ABS - (MM_ABS_ABS) between sender abstract interface (MIAASY_Sen) and receiver abstract interface (MIAASY_Rec)
3. BPM should be something like this
   Container:*
rec Abstract Interface MIAASY_Sen
send Abstract Interface MIAASY_Rec
Receiver (rec) - Transformation (IM_ABS) - sender (send)
Configuration
1. Sender agreement to fetch the message from outbound interface(MIOASY) utilising communication channel with whatever adapter you have used
2. Receiver Determination with Sender and sender interface as MIOASY while receiver as IP(Integration process)
3. Interface determination between
    a. Sender,Outbound interface MIOASY and Abstract interface MIAASY_Sen with no interface mapping
   b. IP as sender with abstract interface MIAASY_Rec and receiver interface MIIASY with no interface mapping being used as it is of same type as receiver interface is
4. Receiver agreement with MIIASY being used as receiver interface and communication channel utlililsed to convert it into receiver format.
Let me know if it works.
Regards,
Amit

Question about message interface

I developed a jdbc to file scenario, it works, but I'm confused.
I designed a message interface for jdbc outbound,
CustomerRow
|--row
|--CUST_NO
|--......
I set Document Name = 'resultset' in jdbc sender adapter.
I can see payload in SXMB_MONI.
<?xml version="1.0" encoding="utf-8" ?>
- <resultset>
- <row>
<CUST_NO>pp3433</CUST_NO>
<SALES_ORG>org1</SALES_ORG>
<DISTRIBUTION_CHANNEL>dis1</DISTRIBUTION_CHANNEL>
<DIVISION>div1</DIVISION>
<FLAG>N</FLAG>
<LAST_UPDATE>2008/11/05 15:24:53:843</LAST_UPDATE>
</row>
- <row>
<CUST_NO>ppy3233</CUST_NO>
<SALES_ORG>org2</SALES_ORG>
<DISTRIBUTION_CHANNEL>dis2</DISTRIBUTION_CHANNEL>
<DIVISION>div2</DIVISION>
<FLAG>N</FLAG>
<LAST_UPDATE>2008/11/05 15:24:53:843</LAST_UPDATE>
</row>
</resultset>
You noticed that resultset is not 'CustomerRow' in message interface which I defined.
I don't know how it can work.

The parameter Document Name should ideallly contain ur Message Type root name. As u have changed it to 'resultset', it is replaced at the sender adapter and then flow continues.
There are very few occasions when success raises a question
Regards,
Prateek

Get/set message interface name in adapter module

Hello,
From an adapter module, I'd like to get or even set the Message Interface name of the message that is handed over to the function "process" of the adapter module.
I've got two context's, sessioncontext and modulecontext. With both contexts, you can get values from that context. I'm not sure which context has the message interface name of the message currently being processed, and I'm also not sure what that value is called (moduleContext.getContextData("name");).
The reason for this is that sometimes you'd like to do something different depending on the type of message being processed.
If anyone knows how to do this, I'd be glad to hear.
Thanks in advance for any advice!
Greetings, Walter.

Hi Walter,
It is fairly easy to get the interface name. When you have extracted the XIMessage there is a parameter, which allows you get the Action, where you can get the interface name.
I have tried to change the interface name. You need to create a new message an copy the content from the old message over to this. This is a little tricky and I'm not able to get any code samples for you.
/daniel

Error - "Message Interface does not exist in any software components"

HI
This is an Idoc sender - SOAP receiver scenario.
When I try to create the receiver determination, I get a warning message -
" Message interface does not exist in any software components installed on this business system"
I checked all the usual things & also reimported the IDoc metadata.
Any suggestions are appreciated!
Thanks
Rachana

Hi Rachana !!
You should also check if the given idoc type in mapping is the same that in the WE20.
Also try to reactivate your integration directory objects by making any dummy changes.
Check your receiver business system (I mean XI), that the logical systems are ok.
Check this document (page 31):
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f2a9fa2-0a01-0010-32ac-d281db722b86
Regards,
Matias.
Message was edited by:
Matias Denker
Message was edited by:
Matias Denker

Integration Process Referencing Message Interfaces In A Different SWCV

Hello Experts!
I am creating an Integration Process IP within SWCV A, using an Interface Mapping Object within SWCV A, Abstract Message Interface MI_A1 from SWCV B and Abstract Message Interface MI_A2 from SWCV B.
Because we have the dependencies set up in the SLD wherein SWCV A is a dependent SWCV of SWCV B, these basis objects can be referenced by the IP during the create process.
However, when I try to execute a "check" or activate the IP, I get the following error:
Expression must return the interface type MI_A1
Expression must return the interface type MI_A2
If I copy the MI objects into SWCV A, the IP is activated successfully.
The question is:
Why is it that while I'm creating the IP I am able to reference these basis objects, but the "check" or "activate" does not allow it? What is this error telling me?
Want more points? Appreciate any insight.

Thanks for pointing me to the right direction, Aamir.
It turned out that the problem was caused by one of the Message Interfaces used by the Interface Mapping. It had errors to where it was pointing to an inactive IDoc object. The bad MI caused the IM to be bad, that eventually caused the problem while creating the Integration Process.
Thanks again!
H.

What is an Abstract in message interface ?

hai pals,
     can anybody clarify ,what is an Abtract in message interface of integration builder of xi.
      Is this,neccessary to specify and create the interface with type abstract.
       if yes , can u pls tell me why?
right answers will be appricited
have a nice day.
raj

you can also take a look at this definition:
"Interface for which no direction is defined initially.
An abstract message interface has no implementation in an
application system. You <b>cannot generate a proxy</b> for this
interface type. You use abstract interfaces in business
processes, for example, to receive or send messages from
application systems. You can use the same abstract
interface to receive or to send."
from:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/3355d5617d0a4cb0fe8e042c752caa/content.htm
Regards,
michal

Outbound and Abstract Sync message Interface difference

Hi Experts,
Is there any difference between the input and output messagetype for Outbound/Inbound Synch Message Interface and Abstract Sync Message Interface.
Do we need to mention the same input and output messagetype for both outbound and Abstract or it should be otherway around?
Regards
Sara

---Is there any difference between the input and output messagetype for Outbound/Inbound Synch Message Interface and Abstract Sync Message Interface.
No there is not. U can select any message type irrespective of the type of message interface.
---Do we need to mention the same input and output messagetype for both outbound and Abstract or it should be otherway around?
Yes. As per ur requirement u can specify the same.
Regards,
Prateek

XI message interface type

Similar Messages

Maybe you are looking for