BPM - Message Interface

Hello all,
I have some doubts about Messages Interface used in BPM.
BPM just used Abstract Message Interfaces, but to expose the Interface to sender aplication, XI need the same Message Interfaces that is declared abstract but no abstract.
My question is how the Business Process Engine that the Outbound Message Interface, that my application is using, is the Abstract Interface that activate my Integration Process???
Regards,
Luiz

Hi
BPM can process only through abstract interfaces.
Those abstract interfaces attached to a receive step in BPM(Receive step is a mandatory step to start the integration process) are automatically assigned as inbound interfaces with respect to BPM and will be outbound interfaces with respect to sender side and similarly in the receiver side.
I didnt get your question properly.hope i am giving the answer you needed.
Thanks and Regards,
Vineetha

Similar Messages

  • 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

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

  • 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

  • Reuse Message Interface from others software component in BPM

    Hi.
    I have created new ccBPM scenario, in the first step always receiver step. so in this receiver i want to use message interface (IM) that already difined in others software component.
    Why i can't see this MI from my Integration Process (IP) ? how to configure so i can see all the MI from others software component ?
    Thank you
    Fernand

    Hi,
    Have u added abstract interfaces in Object area(IP).If u specify in object area u can add those interfaces to step.
    If u want to add other SWCV's interfaces u vave to configure usage dependency.
    look into below links for usage dependency:
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/e95ac0a0302d56e10000000a422035/frameset.htm
    /people/michal.krawczyk2/blog/2005/08/26/xi-are-you-independentfrom-your-dependencies

  • 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

  • BPM - Message has error on the outbound side

    I get this error 'Message has error on the outbound side" . I am using IDOC - BPM - JDBC. I checked SXI_CACHE and I see ret code 99 for this Integration Process. I tried to activate it. I see an error saying that ZCUST_NUMBER is not a component object of PAYLOAD. I have this context object defined on the Abstract Message Interface built to store the IDOC.
    Any ideas are helpful

    Michael,
    <i>The program outputs a returncode = 99 during the cache refresh of an integration process (ccBPM), with an error message that says that 'xxxx' is not a component of the 'PAYLOAD' data object.</i>
    If you are getting the above error, check OSS NOte 890760

  • 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, abstract interface unavailable

    Hello,
    I want to build a business process. Therefore I need some container elements. One container element has the type abstract interface. The message interface is defined in some namespace of some software component. But unfortunately I can't select this message interface in the dialog. Of course I have already activated my change list. I also refreshed the CPA cache, but this doesn't help a lot. What can I do in order to see this abstract interface.
    Thank you very much,
    Oliver

    Hallo Oliver,
    XI currently only allows BPM to use interfaces within the same software component or within a software component with which you have a based on relationship defined.
    I think, that this does not make too much sense, but that's the answer we got to an according OSS message.
    Best Regards
    Christine

  • Message Interface in Integration Directory

    Hi,
    In Integration Repository, I have one send step in BPM.
    I am sending one Abstract Interface from BPM. While creating Receiver Determination in Integration Directory,
    I am unable to find the message interface which is created in Integration Repository.
    Please let me know, if you have any thoughts on this.
    Thanks & Regards
    Katta Mohan Reddy

    Hi,
    https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1822. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    I think this is a good weblog to clear doubts with BPM. Hope it helps,
    Cheers,
    Divya

  • IDOC created in BPM, Message in SXMB_MONI = error

    Hello everybody,
    we generated a IDOC in BPM.
    In ID we got for the corresponding IDOC-Message-Interface
    a) Receiver determination
    b) interface determination
    c) receiver agreement
    In SXMB_MONI we got the error "IDoc Interface XYZ could not be interpreted"
    This error only occurs when the receiver is out R/3 system.
    If we change the receiver e.g. to FTP, everything works find?
    (IDOC is not standard SAP!)
    Any ideas?
    Regards Mario

    Hi,
    Make sure that you are using the idoc imported from R/3 as your interface in the configurations and not the external definition.
    Also the receiver determination and receiver agreement should have the BPM as the sender service and R/3 as the receiver service.
    Regards,
    Smitha.
    Message was edited by: Smitha Rao

  • Message interface is not used by this process

    Hi,
    I´ve  created a process to get a txt file in the O.S., verify this file and create another file. This verify I´m using BPM but there is an error message:
    "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>"
    Could you help me,
    thanks,
    Renato

    Hi Renato,
    Can you please elaborate what you did you do to eliminate the problem. I am facing the same one now.
    A file is received followed by FCC and then a interface mapping is to be called. somehow the system is unable to find the necessary mapping and giving this error.

  • Message Interface : Outbound, Inbound, Abstract  ?

    Hi all,
    does anyone have tips to use an Outbound, an Inbound or an Abstract Message Interface ? When data is sent from XI, should we use an outbound one ?
    Thx to all.

    Hi Elliot,
    Always think in perspective of the sender and receiver systems.
    For sender system, it is output to sender so, Outbound
    For receiver system, it is input to receiver so, Inbound
    Abstract is used for BPM it can act as both inbound and outbound.
    Regards,
    Sreenivas
    Message was edited by:
            Sreenivas Nettem

  • Abstract asynchronous message interface for fault (exception) messages

    Hi,
    Has anyone yet discovered how to create an abstract asynchronous message interface for a fault message so that said message can be referenced in an Integration Process? I am currently at a loss as to how to reference the exception message returned by a synchronous RFC call, and how to return the fault message of a synchronous MI from a BPM.
    Thanks for any help you can provide on this issue - please do not refer me to existing blogs or forum messages if they do not specifically answer this question in a positive manner. I have just been through the SAP Notes and the SDN forum and Google and while I have seen many questions about this topic I have not seen any answers. 
    Stephen

    hi stephen,
    never worked on this but out ofcuriosity after seeing ur question i tried to  create one:
    but i found these:
    fault message types will only be used in case of synchronous messages.....if it is asynchronous the fault message type radio button it self will not seen while creating message interface..just check.
    you need to create a Fault message type to use it in an interface...u can add your own fields also if u want.
    in your present case you mentioned you are using synchronous RFC...try creating a synchronous abstract interface there you can give fault message type also...just check by creating one...
    correct me if i am wrong...
    regards.

Maybe you are looking for