Steps

[Former Member]

Explain the different types of steps in detail while processing the integartion process?

[Former Member · Accepted solution]

Dear Mahesh,

You use step types to define the individual processing steps of an integration process. The individual steps are displayed in the editor area of the graphical process editor. You insert a step into the definition of an integration process by using Drag&Drop.

1.Recieve step:

You can use a receive step for the following purposes:

Starting an Integration Process

Receiving Messages in Integration Processes

Defining Sync/Async Communication

For a description about how to process received messages at runtime, see:

Setting Up Inbound Processing

Assigning Messages to Receive Steps.

2.Send step:

You can use a send step () for the following purposes:

· Sending Messages from Integration Processes Asynchronously

· Sending Messages from Integration Processes Synchronously

· Sending Acknowledgements from Integration Processes

· Defining Sync/Async Communication

3.Reciever Determination:

You use a receiver determination step () to get a list of receivers for a subsequent send step. The receiver determination step calls the receiver determination that you configured in the Integration Directory and returns the receiver list.

4.Send Context

In the receiver determination step, specify the send context and the multiline container element for the receiver list. You must specify the send context to be able to send messages from the same interface to different receivers in different send steps.

The send context is an arbitrary string. You query this context in a condition in the receiver determination in the Integration Directory.

5.Transformation step:

You use a transformation step ( ) to do the following:

● n:1 Transformation

Bundles multiple messages into one message, for example, individual purchase order items into one purchase order.

● 1:n Transformation

Splits a message into multiple messages, for example, a purchase order into the individual purchase order items.

● 1:1 Transformation

Converts a message into another message, for example, a message that is defined by interface A is converted to message that is defined by interface B.

Since no receiver information is available in the transformation step, there can be no value mapping within the transformation step. If the messages to be transformed give values in different formats, for example different date formats, you must first ‘normalize’ the values before the messages can be processed in the process. To do so, define a message mapping with a corresponding value mapping.

For more information about making correct use of transformation steps and mappings

6.Switch:

You use a switch () to define different processing branches for a process. The Otherwise processing branch is created automatically.

You define a condition for each processing branch (see also: Condition Editor). The condition is checked at runtime. The process is continued in the branch that is first to return the value true. If no branch returns the value true, then the process is continued in the Otherwise branch.

The system checks the conditions in the order that they are numbered. This corresponds to the following sequence:

· Vertical layout: From top to bottom

· Horizontal layout: From left to right

7.Container operation:

You use a container operation () to set a value for a target container element at runtime (see also: Defining the Data of a Process in Containers). The target container element and the assigned value must have the same data type. To specify the value, use the expression editor (see also: Using the Expression Editor .

You can:

· Assign

Assigns a value to a single line or multi-line container element. This value overwrites the previous value. You can use this container operation to count a counter variable, for example.

· Append

Appends a value to a multiline container element. For example, you can use this container operation to append individual messages to multiline container elements when gathering messages together.

8.Control step:

You use a control step () to do the following:

· Terminate the current process

· Trigger an exception

· Trigger an alert for Alert Management (see also: Triggering an Alert)

Activities

9.Block:

You use a block () to combine steps that you want to execute one after the other and which are to access the same local data (see also: Containers). You can also use a block to combine steps that you want to have the same deadline or exception handler, or to define a local correlation.

You can define the mode Parallel For Each(ParForEach) for a block or Dynamic Sequence (ForEach). This means that the block is executed for all elements of a multi-line container element

10.Fork:

You use a fork () when you want to continue a process in branches that are independent of each other, for example, to communicate with two systems that are independent of each other. The branches of the fork join in a union operator.

You can specify the required number of branches and then define whether the process must run through all branches, or just a particular number of branches. Furthermore, you can define an end condition for the fork (see also: Condition Editor).

As soon as a branch reaches the union operator at runtime, the system checks the following conditions in the specified order:

· The process has run through the required number of branches

· The specified end condition has returned true

The step is complete as soon as one of the conditions returns true.

11.Loop:

You use a loop ( ) to repeat the execution of steps within the loop. The loop continues to run while the end condition returns true (while loop).

To specify the end condition, use the condition editor.

12.Wait:

You use a wait step () to incorporate a delay in a process. Usually, you use a delay to define when the next step in the process is to start. You can define a delay as either a point in time or a period of time.

At runtime, the step waits until the specified point in time is reached or the specified period of time has passed. The system then continues the process by proceeding with the next step.

13.Undefined Step:

An undefined step () has no influence on the process flow. You can use an undefined step for the following purposes:

· As a placeholder for a step that has not yet been defined

· As a step with no functions for test purposes

[Former Member]

Hello,

they are all explained here:

http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/frameset.htm

Regards

Patrick

[Former Member]

hi..

Refer to this link below for the details.

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm