cancel
Showing results for 
Search instead for 
Did you mean: 

Regarding Abstract Interface

Former Member
0 Kudos

Hello,

What makes the difference between the Normal Interfaces and Abstract Interfaces. Is there any technical differences between these two interfaces.

Thank you

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

HI

Abstract message interface donu2019t have a direction and arenu2019t implemented in an application system. We use them to define the process signature of an integration process.These are also called as hidden Interfaces.

The Message interface is the highest level representation of XML meta data. It has two important attributes: mode (Synchronous or Asynchronous) and direction (inbound or outbound). For Business processes, Abstract interfaces are used; these have a mode, but no direction.

oReferences fault message types for exception handling

oContext objects can be assigned.

oWSDL representation available for export

oStarting point for Proxy generation (ABAP and Java).

cheers

Former Member
0 Kudos

Hi Ravi Kumar,

There are three types of interfaces

1) Outbound Interface

2) Inbound Interface

3) Abstract Interface

Outbound Interface: It can send and cast the messages.

Inbound Interface: It can receive and collect the messages.

Abstract Interface: It can nothing but both Inbound & Outbound interfaces.

Abstract interfaces are used BPM ( Business Process Management) Scenarios.

Regards,

Skumar

Former Member
0 Kudos

Abstract Interface have been used when ur using XI without IR

For Abstract interface sender & receiver interface must be on same namespace

former_member193376
Active Contributor
0 Kudos

Hi

In short, Abstract interfaces can be used as inbound or outbound. Incase of Normal interfaces, you have to specify whether its an inbound or outbound.

BPM understands only Abstract Interfaces

Thanks

Saiyog

Former Member
0 Kudos

hi,

What makes the difference between the Normal Interfaces and Abstract Interfaces.

Abstract interfaces are hiddeen interface.

BPM can understood these interfaces, these are directional less, i mean not as inbound or outboud.where normal interfaces has the direction like inbound, outbound and mode as synchronous or asynchronous..

Is there any technical differences between these two interfaces.

BPM can interact and deal with only Abstract Interfaces. And so, if you have a transformation step inside the BPM , the source and target interface will have to be abstract interfaces.

The interface mapping will be between Abs Interfaces in the IR.

Normal interfaces are used when we are not using any BPMs..

please check the following link.

http://help.sap.com/saphelp_nw04/helpdata/en/55/c5633c3a892251e10000000a114084/frameset.htm

Thanks,

Vijaya.

Former Member
0 Kudos

Hi,

You use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure.

When you create a message interface you define the communication parameters by using the attributes Mode and Category as Sync/Async, Inbound/Outbound or Abstract.

Message interfaces of this category can perform the role of an inbound or outbound interface within integration processes, depending on whether it is used to send or receive a message. For this reason, no direction is specified during definition. In integration processes, you can use the same abstract interface to receive and send a message. Abstract message interfaces generally receive the message from an outbound interface of a sender system and send it to an inbound interface of a receiver system, thus performing a complementary role.

BPM can interact and deal with only Abstract Interfaces. And so, if you have a transformation step inside the BPM , the source and target interface will have to be abstract interfaces.

These characteristics determine the direction of an interface:

· An outbound interface sends a request message that is only used to make a communication party aware of data sent, without waiting for a response message. In the case of the latter, we also refer to publishing interfaces.

· An inbound interface receives a request message that you reply to with a direct response message or whose data you can process in the system without a response.

Thanks

Swarup

Former Member
0 Kudos

BPM understands only abstract interface. So you will have to define a abstract interface for each message going into BPM and inbound interface going out of BPM.

So for example if you have a bpm scenario where in data is passed from file adapter to BPM to file adapter. If your outbound message is Vendor_Outbound you have to create a new message interface Vendor_Abstract. This message will pass through BPM and undergo transformation to become Vendor_Abstract_after_Mapping. This message again can't be undertstood by communication channels and hence needs to be mapped to a similar message inbound interface structure. So the final message outside the BPM would be Vendor_Inbound_after_Mapping

Also you can only declare asynchronous abstarct interface as the container elements. So no synchronous abstract interfaces can be defined as container element.