This activity defines a process flow consisting of one or more activities as a single coherent processing unit.
The following figure shows processing units that use scope activities.
Figure 5-11 Setting up processing units using scope activities
When you define a scope activity, you can handle the processing flow inside the scope as a single coherent unit. You can also define a scope inside the processing flow of another scope, as exemplified by Scope 3 in the figure above.
Note that variables defined inside a scope are valid only within that scope. For details about the scopes and the valid range for variables, see 5.5.1(5)(a) Use of variables when scope activities are used.
To define a receive activity:
You can set the scope activity such that transaction is not committed in the internally defined activity.
When you select Commit at the time of start and end of this scope radio button in High level settings of Scope activity dialog, transaction is committed at the time of start and end of the scope activity. The activity defined in the scope activity is not committed.
When you select Commit in the activity unit radio button, activity is not committed at the time of start and end of the end activity. Activity to execute commit defined in the scope activity is committed.
By default, Commit in activity unit radio button is in selected status.
For details on Scope activity dialog, see "1.4.18 Scope activity dialog" in the "Service Platform Reference Guide".
For details on the transaction when you select Commit only at the time of start and end of this scope radio button, see "3.4.5 Transaction when selecting the settings of committing at the time of start and end of scope" in the "Service Platform Function Guide".
You must note the following points to be noted when defining the scope activity for which Commit only at the time of start and end of this cope radio button: