Message interface

Hi all,
         In IDOC interface,
sender is IDOC imported from R3
Rec is same IDOC structure with my name space but i it is not created in IR.
Interface mapping is done it is aying outbound it is saying name of IDOC(Order,order04) and at inbound side it is saying(Input message)...
and interface working successfully from two years
i try to click on the inbound interface with my namespace name it is saying unable to read this object..
i try to understand this interface but i am missing some where
( one more thing actually this interface dont need any mapping but they created interface mapping)
thanks
Kumar....

Hi Krishna,
When ever u r doing the scenario with the IDoc either in the sender or in the receiver side there is no need to create the Inbound.Outbound Message Interface in the IR. U can directly import the IDoc to the XI and give the IDoc name directly to the inbound/outbound Interface.
>>target is with the name space of interface but no interface is created in IR..
Check if the Message Interface belongs to the same name space or to the some Generic Message Interface in the different namespace.
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

Similar Messages

  • 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>

  • Using one Message Interface for all mappings

    Hi Folks,
    I am using a BPM in which i m getting a file from file system which have system ID in it.
    I am having three send Synchronous step following that.
    What i need is to use the Message interface for file to be used for receiver determination based on system id in case of Synchronous interfaces.
    DO i need to include this File msg. interface in each mapping, if i do so will it be possible to send req. and get response for synchronous call.
    OR is there any way to to use the file msg. interface for each mapping.
    we are on SP17,I also tried Extended mapping but i am having SYNCHRONOUS send steps.
    Plz help me out
    Sachin

    Bhavesh
    <i>1. You receiver a file in your BPM . This has a field called SYSTEM ID?
    2. On the basis of the System ID field you need to determine the Receiver to which the Synchronous Request message has to be sent?</i>
    Sorry for that...because I was confused with jai's ans.. that's why said like that
    <b>You are absolutely correct</b>
    This is what i want to do.
    i can't use switch step here.  my BPM looks like this
    RecFile->sync send->transformation1->transformation2->sync send2->transformation3->BLOCK
    in BLOCK
    Sync Send3->transformation4 and so on...
    I am using three different Sync ABS Interface for each Sync send steps.
    In receiver determination i want to get the data from respective R/3 system based on system ID i.e. logical system in File MI.
    Say if it T90CLNT90 then get data from BS_SAPR3_4.6 else from BS_4.7
    Sachin
    Message was edited by:
            Sachin Dhingra

  • Error message when opening Outlook: The operation failed. The messaging interfaces have returned an unknown error. If the problem persists, restart Outlook.

    In an Exchange 2010 server/Outlook 2013 environment, one of our users is getting an error message every time they start Outlook. The error message says: "The operation failed. The messaging interfaces have returned an unknown error. If the problem
    persists, restart Outlook."
    The error log message details are as follow:
    System
    Provider
    [ Name]
    Microsoft Office 15 Alerts
    EventID
    300
    [ Qualifiers]
    0
    Level
    4
    Task
    0
    Keywords
    0x80000000000000
    TimeCreated
    [ SystemTime]
    2013-01-08T15:54:49.000000000Z
    EventRecordID
    655
    Channel
    OAlerts
    Computer
    Computer-Name.domain.local
    Security
    EventData
    Microsoft Outlook
    The operation failed. The messaging interfaces have returned an unknown error. If the problem persists, restart Outlook.
    301670
    15.0.4420.1017
    xyfc
    0x8004011B
    The system is as follows:
    Size of .pst file: 2.3 GB (Unicode format so there should be plenty of space left)
    OS: Windows 7 (64-Bit)
    Application: Outlook 2013 (32-Bit)
    The user upgraded from Outlook 2010 a few months ago and the error message has only recently started appearing on startup. I thought it was a corrupt mail profile, so I have already tried creating a new mail profile, as well as the repairing tool in Outlook.
    I even tested another email account and that worked just fine. So apparently it is something wrong with the specific user's account/profile and not something wrong with the computer - since my email account worked fine on his computer.
    Any help would be greatly appreciated.

    I had the same error message, only in my situation Outlook would only open successfully every 4 or 5 attempts. When Outlook would open (versus just hanging at the splash screen), I would get two dialog boxes with the warning/error message. 
    After I clicked okay I could get into Outlook.
    Previously I experienced this problem running my Office 2010 client with my Exchange 2007 mailbox on my old laptop.  The problem followed my mailbox through an Exchange 2010 migration (so new Exchange org), client upgrade to Outlook 2013, and a new
    laptop (so I knew it wasn't a corrupt profile).  This led me to the conclusion that it was a corrupt item(s) in my mailbox.
    To resolve the issue, I archived *everything* in my mailbox to a PST file, ran SCANPST to fix the corruption, and then uploaded everything back into my Exchange mailbox one folder at a time, stopping after each folder to close and restart Outlook so I could
    narrow down which folder had the corrupt item if the problem recurred.  I'm happy to say my issue is now resolved.

  • 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”
    What’s 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

  • Message interface does not exist in any software components installed

    "Message interface does not exist in any software components installed on this business system"
    Essa é a mensagem de erro que estou tendo ao tentar configurar o XPath Receiver Determination do cenário SRVSC_WebAS_Outbound_ServiceStatusCheck.
    Já notei que a mensagem dá porque o meu BS da NFe não está com o SWCV SAP SLL-NFE 1.0. Mas isso só no ID porque no SLD ele aparece. Não sei mais o que fazer pra ele aparecer no ID. Já eliminei o BS, executei um refresh do cache do SLD, depois executei um refresh full e nada! Quando eu crio o BS novamente, ele vem sem o SWCV SAP SLL-NFE 1.0.
    Tive que configurar o XPath na mão para todas as SEFAZes!!!
    Já li vários threads a respeito desse erro e executei vários procedimentos sugeridos, mas nada.
    Alguém já possou por isso?!?

    para ser mais preciso, verifique no payload de envio e recebimento da mensagem de verificacao de status do servico se estao correspondentes ao que estao abaixo, essa mensagem é de verificacao do SEFAZ de SP (35) para o ambiente de homologacao
    (SENDER)
    <?xml version="1.0" encoding="utf-8"?><n0:nfeStatusServicoNF xmlns:n0="http://sap.com/xi/NFE/005a" xmlns:prx="urn:sap.com:proxy:PID:/1SAI/TASE95D30ADB76F1544C2D5:700:2009/02/10" xmlns:n1="http://www.portalfiscal.inf.br/nfe"><n0:cUF>35</n0:cUF><n0:tpEmis>1</n0:tpEmis><n0:tpAmb>2</n0:tpAmb><n0:nfeCabecMsg><n1:cabecMsg versao="1.02"><n1:versaoDados>1.07</n1:versaoDados></n1:cabecMsg></n0:nfeCabecMsg><n0:nfeDadosMsg><n1:consStatServ versao="1.07"><n1:tpAmb>2</n1:tpAmb><n1:cUF>35</n1:cUF><n1:xServ>STATUS</n1:xServ></n1:consStatServ></n0:nfeDadosMsg></n0:nfeStatusServicoNF>
    (RECEIVER)
    <?xml version="1.0" encoding="UTF-8"?>
    <nfeStatusServicoNFResponse xmlns="http://sap.com/xi/NFE/005a"><nfeStatusServicoNFResult><retConsStatServ xmlns="http://www.portalfiscal.inf.br/nfe" versao="1.07"><tpAmb>2</tpAmb><verAplic>SP_NFE_PL_005e</verAplic><cStat>107</cStat><xMotivo>Serviço em Operação</xMotivo><cUF>35</cUF><dhRecbto>2010-05-26T09:37:22</dhRecbto><tMed>1</tMed></retConsStatServ></nfeStatusServicoNFResult></nfeStatusServicoNFResponse>

  • 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

  • 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" ?>
    - <!--
    Call Adapter
      -->
    - <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 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" ?>
    - <!--  Call Adapter
      -->
    - <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

  • Message interface not listed in integration directory

    hi,
    i have created 2 interfaces inside my message interface........
    both are outbound.....!!
    i am actually doing 2 scenario's inside the same name space......
    when i go to integration directory i am no able to get one of the message interface's while creating the receiver determination and all those things.........?

    if ur using business service then just
    add outbound interface in receiver side and 
    inbound interface in sender side.
    or if u r using business system then the problem is in ur SLD.
    just check ur business system over their.
    thanks
    reward point if helpful .

Maybe you are looking for