Actions in Integration Scenario

[Former Member]

Dear all,

1. Can anyone tell the difference between Internal action and External action with respect to products and SWCV?

2. What is the Template option you find when you insert an application component?

Expecting your valid replies; if possible please send some documents or examples.

Thanks,

Harikumar. S

[Former Member]

Closing the question. Thanks to all.

[Former Member]

Hi

Go thru these links to understand what is action:

http://help.sap.com/saphelp_nw04/helpdata/en/68/88a440df800160e10000000a1550b0/content.htm

For modeling actions:

http://help.sap.com/saphelp_nw04/helpdata/en/fd/377fa69c38c54dac82d7e390bdf304/content.htm

To know more about "Action Editor":

http://help.sap.com/saphelp_nw04/helpdata/en/2b/cd6a8bceed26469f3b0952a030c711/content.htm

Regards

biplab

[Former Member]

HI,

Internal Action: Defined for a ‘separate’ software component version.

External Action: Defined for a software component version of a partner or for templates

for more info: http://help.sap.com/saphelp_nw04/helpdata/en/55/7a09d0d7d34b828a9740e322b9222c/frameset.htm

Rgards

[former_member529475]

HI Harikumar,

Actions divide up the process flow of a business scenario. Actions in different application components can exchange messages with each other within a business scenario.

<b>Internal Action</b>

You can use internal actions in application components (of type Product Version or Main Instance) that (by using the product version) contain the same software component version in which the action is implemented.

<b>External Action</b>

You can use external actions in application components (of type Template or Product Version) that (by using the product version) contain the same software component version in which the integration scenario is implemented.

If you want to use an action to represent a function that is already installed in the product of the application component, use an internal action.

If you want to use an action to represent a function that is not yet provided by the product of the application component, use an external action.

In this way, you can enter functions in the integration scenario (for example, for communication parties) that are not yet provided by the product version of the application component.

All interfaces associated with an action are assigned to that action in the Integration Builder.

The exchange of messages between components takes places between two actions from different application components. The interfaces used in the exchange of messages are assigned to the two actions involved.

Cheers...

Vasu

<b>** REward Points if found useful **</b>