Regarding Message Interfaces

Hi Guys,
I am new to SAP XI. Only thing I know is Message Interfaces are very key role to play in SAPXI. In case of any IDOC Are BAPI you can directly import them to I.R as interface objects. for example there are lots of IDOCS Available like BATMAS, MATMAS, ORDERS, CREMAS, there is lot of confusion on this what information this IDOCS contain how can we Know that particular IDOC contains the information Meeting our requirement. In case I am integrating MM Module Are SD module with SAP what interfaces I need to use pls any one explain me with clear scenario. and also pls help with some realtime docs so I can understand the things better. Thanks in advance.
Regard's
Kiran.B

Hi Kiran,
       There is no confusion about IDOCs. The requirement shows the what type of IDOC u want to used.
The XI guys will take care of the Import the IDOC from particular R/3 system.
Like same RFC Function Modules also..
When ever we used IDOC we need configured setting in R/3 & XI Systems.
__Configured steps in R/3 System:__
1) RFC Destination-- SM59
    --> Create the RFC Destination
   --->Crate the RFC Destination type 3(R/3 system)
   ---> specify the server address of the Integration server as target hosts
2) Port----WE21
   _---->Create the port for transaction RFC
> Enter the RFC Destination
3) Partner Profiles--WE20
Configure the steps in XI System:
1) Create the RFC destination (SM59)
2) Create the IDOC port into IDOC adapter(IDX1)
3) Load the meta data of IDOC into IDOC Port(IDX2)
Regards,
Nskumar

Similar Messages

Regarding Message Interface Working

Hi All,
Can anybody give some help in finding wht actually happens when we create a message interface.
means in which format information entered in Message Interface gets stored.
where this object gets stored and how we can retirve information for this.
Best Regards,
Amit

Hi Amit,
The Objects of Message Interface will be obviously in IR Objects only.. for further info on Message Interface u just go thru the link below..
http://help.sap.com/saphelp_erp2005/helpdata/en/34/3d8942ecd55551e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/3f/01623c4f69b712e10000000a114084/frameset.htm
Regards,
Raj

Regarding message interfaces in JDBC implementation

Hi Bhavesh,
I have been trying to implement the jDBC scenario as mentioned by you in the blog "JDBC Receiver Adapter -- Synchronous Select Step by Step",could you please help me out with interfaces(how many interfaces do we need on the whole).
Regards
Madhu

Madhu,
Please refrain from directing questions to someone in particular. There are lots of XI experts around here who can surely help and directing questions to one person is going to discourage others from answering .
Answering your question~~ refer into this blog by Arpit and use the same concepts as he has described for File - RFC - File. The only difference will be in the datatypes and message types,
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Regards
Bhavesh

Regarding Message Interface , Service Interface

Hi All
My scenario is File to File from 1 application server to another application server ,without any transformation in PI 7.1 for service interface to be involved for Interface Pattern Stateless and Stateless (XI 3.0) compatible can only be used with Category Abstract
only abstract catgory is possible , can'nt i make 1 outbound & another inbound for this ?
Regards
Abhishek
Edited by: Abhishek Agrahari on Feb 9, 2009 11:08 AM

Search SDN for this there is Blog for this i dont have info on this
Need to do follwoing in the ID
1. Sender and receiver Business system/services
2. respective File communication channels
3. Receiver Agreement
4. interface determination
5. Finally receiver agreement and sender agreement
Rajesh

Regarding Message Interface

Hi All,
If We Are Developing a Sysnchronous Interface Say RFC -XI--SOAP
Then here How many Msg Interfaces We need to Develop ????
What Are those Intefaces with Mode And the Directions ???? ( Ex: Sysch,,,Outbound )
Please let me Know
Regards
Vamsi

Hi
For HTTP-XI-RFC Go through this
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/e80440a832e369e10000000a155106/content.htm
Thanks

Message Interface no longer exist in Integartion Repository

Hi,
I am working on a IDOC to file case, in which I want to determine the receiver at runtime using a value in IDOC, with the help of Context objects/ XPATH. In Receiver determination of ID, after selecting Sender and Sender Interface, when I try to select Receiver, it's giving message "Message Interface no longer exist in Integration Repository" and I am not able to see the Sender IDOC in the conditions field before the Receiver selection. Anybody having any idea why I am getting that error message.

hi,
check if the system that you're using has this message interfaces in sender/receiver tab (double click on the
system in directory)
if not maybe the you need to add dependencies
to the software object (product/software component) which has this message interface - this idoc
(if you do remember to refresh sld cache)
/people/michal.krawczyk2/blog/2005/08/26/xi-are-you-independentfrom-your-dependencies
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

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

Message Interface does not exist in IR u0096 but it does!

Hi, well again i have a problem. I am still trying to get the XI-demo Checkflight. to run but there are some obstacles on my way.
I just wanted to check a MI given in the ID to check the attributes and picked it in the ID to get linked to the IR but a pop-up appears saying
Message Interface does not exists in Integration Repository
Whats the reason for this because obviously it is there, still existing.
I tried to refresh the cache of all XI-components, did a server restart but nothing seems to be working.
On the other hand I have some other questions:
-     Why is it not possible to delete an object (business system) from the ID? I know because of the dependencies of the different channels but it should be possible because of re-generation of the communication-channels (this was also my approach for solving the problem mentioned above!)
-     When do I have to refresh the cache in general? Is it indefinite whenever I want to or it seems to be the right time because something is not running the way it should and it seems a little odd

Hi Carsten Heinrich,
This will help you,
1)     Cache Connectivity Test
In RWB component monitoring, we now have the option of checking whether the cache-connectivity is functioning correctly. This is useful when we are experiencing problems when updating the runtime cache. The system displays a separate window in which we perform the test. If no previous tests have been performed, the system displays a corresponding message. Otherwise, the system shows when and by whom the last test run was started, together with the result of this test.
To start a new test run, choose Start Test.
The system displays the first results of the test run. Since the whole test takes some time, we can update the displayed results if necessary.
To Update the displayed results, choose Refresh Display.
The overall result for each component is displayed as a green, yellow, red, or gray symbol. A green symbol is only displayed if both update steps for the runtime cache were successful, that is, they both have a green symbol.
2)     Cache notification status
a)     Start the Integration Repository.
b)     Select Environment ® Cache notification.
c)   Have a look at the entries for the relevant user and date.
d)   Have a look at the entries for the relevant cache instance, user and date.
               3)    Cache update and resend the message
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
c)     Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.
         4)     Deleting the SLD Cache
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

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

Message interface does not exist in any software components installed on th

Message interface does not exist in any software components installed on this business system.
hello,
When I check the interfaces on the business systems of 1 technical system, none of them have sender or receiver interfaces, hance I can't use them. The interfaces should ofcourse be on the Directory.
I have deleted the business systems and the technical system and created them again, but no result.
The product and software componets are in the technical sytem and business systems.
Any help would be usefull.
thanks,
Job

Hello!
If someone will search in the future for this error, here is the solution:
The error occurs if the GUID of the software component at the SLD is different to the one at the repository. Please compare the GUID at the SLD -> Administration -> Content Maintenance -> Dropdown "Component Version" -> Dropdown "Software Component Version". At the Integration Repository you select the Software Component Version at at the tab "Keys" you find the related GUID.
The error occured because the Software component has been created manually at the system. The repository content came from another system via import with own SLD (and because of that with another GUID for the software component).
Kind regards,
Klaus

Usage of Abstract Message Interface for non-BPM

Hi,
I have a message that I am using as both as an inbound and an outbound for 2 different mapping. I am not using BPM. Is it better to create 2 message interfacesone for outbound and one for inboundor should I just create 1 abstract message interface that can be used in both mappings? What are the advantages and disadvantages of using 2 message interfaces (1 inbound and 1 outbound) against 1 abstract message interface? Would using abstract cause a lot of problems or performance problems in the future?
Thanks in advance.
Regards,
Elbert

hi,
abstract messages are only used for BPMs
so I suggest creating 2 instead if you don's use a BPM
http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/3355d5617d0a4cb0fe8e042c752caa/content.htm
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

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

Unable to view Abstract Message Interface(Sync) in Container Step of BPM

Dear Friends,
This is IDOC---SOAP Sync Communication Interface
I have created the External Def by exporting & importing the Standard Idoc
and Imported the WSDL File which has the Request & response Structure
I have created the Outbound Sync message Interface for Idoc side
and Abstract Sync message Interface for the same to use in BPM
and also created Inbound Sync Message Interface for Webservice side
and Abstract Sync Message Interface for the same to use in BPM
Problem is::::
While creating the Container varible inside the Integration Process, i have to select the Abstract Message Interface which i created for Idoc.
But it is not at all visible in the list.
What might be the problem
REgards
Seshagiri

Hi,
I have created
For Idoc side
1) Create O/b Sync by having request of Idoc and response structure of Idoc
2) Create ABS Sync by having the request of Idoc and response structure of Idoc
3) Create ABS Async by having the Request of Idoc Only
For Webservice side
1) Create I/b Sync by having the request of webservice and response of that
2) Create ABS Sync by having the request of webservice and response of that
3) Create ABS Async by having the Response of Webservice only
I created the Steps inside the Integration Process as showed in the screens.
1)Integration Process graph
http://img145.imageshack.us/img145/4848/ipviewwv1.jpg
2)Receive Step
http://img293.imageshack.us/img293/1756/receivepropng8.jpg
3)Send step1
http://img179.imageshack.us/img179/2200/send1bd0.jpg
4)Send Step2
http://img182.imageshack.us/img182/8468/send2wl1.jpg
When i check the F7, it is throwing the error like
http://img247.imageshack.us/img247/4356/errortx3.jpg
Regards
Seshagiri

BPM - Message interfaces of one component are not appearing in another comp

Hi,
We have created 2 software components(X and Y) for File to RFC scenario.
"X" SWC is dependent on "Y" SWC.
We are building sync-async bridge using BPM. We have created one BPM in X component. This BPM has the visibility of message interfaces only particular to that component only, not the other component. Though wehave created dependency between these 2 components. But without this we cannot build sync-Async bridge.
Please could you provide the inputs, so that we can proceed further.
Thanks,
Ramesh

Hi,
Where are you developing your BPM objects in X or Y ?
If X is dependendent on Y , then you can access Abstract interfaces created in the X in Y.
After creating SWC dependency, then refresh the cache and check out is it working ..
for dependency-/people/michal.krawczyk2/blog/2005/08/26/xi-are-you-independentfrom-your-dependencies
Regards,
Moorthy

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

Regarding Message Interfaces

Similar Messages

Maybe you are looking for