Requirement of a abstract message interface

Hello,
I wonder when to use abstract message interfaces?
The documentations says:
An abstract message interface has no implementation in an application system. You cannot generate a proxy 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.
What does IMPLEMENTATION mean in this context? Can anybody discribe a concrete need for abstract message interfaces?
Thank You

Hi Mario,
you only use those interfaces inside a BPM:
send step, receive step, transformations etc
(no other use)
- you cannot create proxies from it
- you must have an normal (not abstract) interface
to send data to XI or to receive data
(so once you create everything inside your integration process - with the use of abstract interfaces)
inside ID you still have to use standard interfaces
(outbound or inbound)
Regards,
michal
Message was edited by: Michal Krawczyk

Similar Messages

  • 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

  • SOAP XI scenario, ambiguity in Abstract Message Interface

    Hi Forum,
    I have a SOAP client(synchronous)--->XI scenario,
    let me describe the scenario,
    Step1. SOAP client sends a SOAP request to the BPM in XI, using a synchronous receive step (Abstract synchronous MI),
    Step 2. in BPM, it does some transformation
    Step 3. the response of the step 2, is then sent as the response for the SOAP client request, using a Synchronous send (sync async bridge maintained),
    Step 4. i use the abstract Synchronous MI (for the SOAP client to send request), to create a WSDL, and use it in ALTOVA to create SOAP request automatically,
    now the problem is,  In integration builder, Design,.........
    when i make the abstract Synchronous MI (for the SOAP client to send request), i use 2 message types RequestMessage (output message) and ResponseMessage (input message), ******sounds bit oppsosite ..but it is like that only......but the source of ambiguity
    but when i create the WSDL using the web service creation tool, in integration builder, Configuration, ....... the WSDL is bit unexpected, it shows input as ResponeMessage and output as RequestMessage....hmm.....as such i cant use that WSDL in any tool like altova to create the SOAP request automatically....
    ****the source of all ambiguity is....in the screen for creating the Message interface (as Synchronous abstract/outboud), we give OUTPUT MESSAGE as the input message type and vice versa...
    do u agree.......
    am i wrong?
    in that case how can i make a correct WSDL

    Let us discuss point by point.
    You are doing a scenario SOAP to XI with no end point on the other side. Means you are using XI as the end point for simulating. This is my assumption.
    Step1. SOAP client sends a SOAP request to the BPM in XI, using a synchronous receive step (Abstract synchronous MI),
    Ok.
    Step 2. in BPM, it does some transformation
    Ok
    Step 3. the response of the step 2, is then sent as the response for the SOAP client request, using a Synchronous send (sync async bridge maintained),
    You should not use a synchronous send step here. You should be using an Async send here. The sync asyn bridge must start in the first receive step and end here.
    Step 4. i use the abstract Synchronous MI (for the SOAP client to send request), to create a WSDL, and use it in ALTOVA to create SOAP request automatically,
    You shuld create the WSDL for the Outbound Synchronous message interface which should have been created to supply the message to Abstract Synchronous interface. Then only you will be able to test the message.
    So.. you need totally
    1. OB Syn MI
    2. Abstrac Syn MI (Receive in BPM)
    3. Abstract Async MI (to send response to SOAP caller)
    VJ

  • 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

  • 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

  • Why BPM contains only ABSTRACT messgae interfaces

    Hi Forum,
    Can u please help me in finding why BPM can only support ABSTRACT Message Interfaces.....
    thanks
    Edited by: sudeep dhar on Jan 16, 2008 9:28 AM

    Sudeep,
    Refer to http://help.sap.com/saphelp_nw04/helpdata/en/4b/d26b3d32390968e10000000a114084/frameset.htm for a description of the Communication Parameters
    Alternatively, from the SDN SAP on DB2 for Linux, UNIX, and Windows you can pull up the SAP documentation for SAP XI 3.0 and enter the search term 'Abstract message'
    Hope this helps,
    Mike

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

  • 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

  • Do we need to create message interfaces for idocs and rfcs thatare imported

    do we need to create message interfaces for idocs and rfcs thatare imported
    from sap server
    in scenarios from sap system to file or vice versa
    i knew that we need not create message types
    do we also skip creating message interfaces

    hi,
    you create an abstract message interface for IDOC only if you want to use
    them in a BPM (integration process)
    for more about IDOCs have a look at my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    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>

  • 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

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

  • Abstract message

    hi expect,
       why should we are creating abstract message?in bpm why we are using abstract message?

    HI rohit,
    we create abstract interface in bpm because this type of interface has no direction i.e. inbound or outbond. so as per our requirement we can use this interface for any direction
    also check these links
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm - Walk through BPM
    /people/siva.maranani/blog/2005/05/22/schedule-your-bpm - Schedule BPM
    /people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - Use of Synch - Asynch bridge in ccBPM
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
    reward if help
    regards
    Trapti

  • 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

  • Sync to Asyn Message interface mapping

    Hi all,
    I have a scenario where source message interface is a sync interface and target is async. Can any body suggest if it is possible to map the request message structure of source to target (async) and the response need to have a fixed value.
    Is it required to use BPM or is it possible without BPM. Can any body please suggest? Any help will be appreciated.
    Thanks
    -Kulwant

    Hi,
    Defining Sync/Async Communication
    Use
    To enable the communication between a synchronously calling business system (synchronous outbound interface) and an asynchronously called business system (asynchronous inbound and outbound interface), you can define a sync/async bridge in an integration process. You can only define one sync/async bridge for each integration process.
    You can also achieve sync/async communication by using the JMS adapter. If you do not have any particular demand for monitoring or for troubleshooting, SAP recommends that you use sync/async communication in the JMS adapter instead. The advantage of using the JMS adapter over synch/async communication using an integration process is a significant increase in system performance.
    See: Async/Sync and Sync/Async Bridge in JMS Adapter
    We use Sync/Async bridge to establish the Sync communication between the Applications.
    Normally the Technical adapters like File will not support the Sync communication to send back the Response to the Sender system from the File system.
    So in this case we will use Sync/Async bridge to establish the connection using BPM.
    Check these
    Bridging the Sync-Async bridge with Fork (XI)
    Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi
    Structure of a Sync/Async Bridge
    The following table outlines the minimum components of a sync/async bridge:
    *Step
    Use*
    Receive step to open the sync/async bridge
    Receives the message request from the synchronously calling business system and opens the sync/async bridge
    Asynchronous send step
    Sends the received message asynchronously to the asynchronously called business system
    Receive step
    Receives the message from the asynchronously called business system
    Send step to close the sync/async bridge
    Sends, for example, the response from the asynchronously called business system to the synchronously calling business system
    Performance Considerations
    If you insert additional steps in the sync/async bridge, the synchronous time is increased correspondingly. If the time that elapses before the sync/async bridge is closed is too long, this can lead to problems.
    Fault Messages
    It is currently not possible to send fault messages back to the synchronously calling business system. If you want to return error statuses to the synchronously calling business system, you can define a field for an error indicator in the message that is sent to the synchronous interface.
    Procedure
    Define a Receive Step to Open the Sync/Async Bridge
    1. Insert the receive step to open the sync/async bridge in the integration process.
    *You can do this at the following points: *
    Directly after the start marker
    As the first step in a block if the block is the first step of the integration process and if it has the mode Standard
    As the first step in a fork. If the fork already contains some starting receive steps, the Start Process indicator is automatically reset for these steps.
    2. In the object area, define the container element that receives the synchronously sent message.
    Specify an asynchronous, abstract interface in the container element. The message must correspond to the request message of the synchronous interface used to receive the message.
    3. Select this container element in the Message field in the properties area of the receive step.
    4. In the Mode field, select Open S/A Bridge.
    5. Select the Start Process field.
    The receive step to open the sync/async bridge must start the integration process. There must be no other receive steps to start the integration process.
    6. Specify the synchronous interface for receiving the message from the synchronously calling business system. The message type of the message to be received and the request message from the synchronous interface must be identical.
    Define an Asynchronous Send Step
    7. Insert a send step that sends the received message asynchronously to the asynchronously called business system.
    See also: Sending Messages from Integration Processes Asynchronously
    Define a Receive Step
    8. Insert a receive step that receives the message from the asynchronously called business system.
    Define a Send Step to Close the Sync/Async Bridge
    9. Insert the send step at the required position in the process definition.
    Do not insert the send step in a loop, block, or fork.
    10. In the Mode field, select Close S/A Bridge.
    The integration process must not contain any further send steps to close a sync/async bridge.
    11. In the Opened By field, specify the receive step that opened the sync/async bridge.
    12. In the message field, specify the message that is sent to the synchronous interface.
    This message must be of the same type as the response message from the synchronous interface that you specified in the opening receive step.
    Example
    You can find an example of a sync/async bridge in the Integration Repository under SAP Basis à SAP Basis 6.40, namespace http://sap.com/xi/XI/System/Patterns under BpmPatternSyncAsyncBridge.
    For a description of the example, see Example: Sync/Async Communication.
    BPM is an additional advantage of Netweaver XI. it provides features like Sync-Async Bridge, Async-Sync Bridge, stateful msgt processing.....so on.
    Sync-Async Bridge acts as a bridge between a synchronous Business system and Asynchronous business system.
    forex: if u r communicating with a synchronous RFC to a File system(always asynchronous, which is not able to send any response to synchronous RFC Interface).
    In this kind of scenarios BPM Sync-Async Bridge enables communication between a Synchronous RFC to Asynchronous File system or vice versa..
    Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages
    Plz go thru the following:
    - Use of Synch - Asynch bridge in ccBPM
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] - Use of Synch - Asynch bridge in ccBPM
    Asyn - Synch BPM -
    http://help.sap.com/saphelp_nw70/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/43/65d4dab39b0398e10000000a1553f6/content.htm
    Example on Sync/Async communication:
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/65d4dab39b0398e10000000a1553f6/frameset.htm
    Thanks,
    Swathi

Maybe you are looking for

  • It changes my font!

    I've downloaded a font on dafont.com and used it all over my website. But if I go see my website on another computer, it changes to another font. How can I lock my font? So it won't change?

  • CiscoWorks LMS 4.0.1 login issue.

    Hello. We are using CiscoWorks LMS 4.0.1 with TACACS login module enabled. We have an issue with an account, and only this account. I can successfully login with any other account, newly created also. I have deleted and created it without success. An

  • Erec-Unfortunately, the system is unavailable at the moment;try again later

    Hi, I am trying to open Erecruitment from portal Employee Self-Service -> My HCMS Profile & Career Opportunities. It takes me to eRecruiting page. But I am not able to see the eRecruiting page. It is giving "Unfortunately, the system is unavailable a

  • Image Backgrounds - .gif

    Hi. Im making an rpg, and while trying to add the image of the person ontop, i noticed that, unlike on websites, the background of black isnt transparent. Could someone please help. Is there a color that java reconizes as see-through for a .gif? Than

  • SQL Server Compact 3.5/4.0 - Client / Server .sdf database file compatibility

    I am considering connecting autonomous Windows Desktop PCs with SQL Server Compact 3.5 SP2 databases via an ASP Website and would like to provide database upload/download capabilities. If I use SQL Server Compact 4.0 as the Website database, will the