0

Process Chains

Contents
Design of process chains
Properties of process chains

SAP AG 2003

SAP AG

BW360

10-1

0.2
Process Chains: Unit Objectives

At the conclusion of this unit, you will be able to:

Use process chains

SAP AG 2003

SAP AG

BW360

10-2

0.3
Process Chains: Overview Diagram
Architecture and Customizing

InfoCube Data Model

Transactional Data Targets

Transport Management

ODS Objects

Indexing

Process Chains

BW Statistics
Extraction and Dataload
Reporting Performance
Partitioning
Aggregates

SAP AG 2003

SAP AG

BW360

10-3

0.4
Introduction: Typical Data Load Cycle
Load into PSA

Load into ODS

Data Load
Monitor
Activate
Data in ODS

Drop Indices
Roll up
Aggregates

Build DB
Statistics

Data Target
Maintenance

Load into Cube

Build Indices

SAP AG 2003

SAP AG

BW360

10-4

0.5
Job Scheduling and Monitoring with BW 2.0B/2.1C
Monitoring of entire load process not possible (different logs
for InfoCubes, attribute changerun, drop index, )
Complex event chain scenarios necessary
Complicate restart of terminated processes

SAP AG 2003

There were certain limitations of event chains (BW 2.x), which have been solved with the
introduction of process chains.

PC monitoring extends beyond the data load process itself.

Moving responsibility means that the predecessor process is not responsible to start the successor
process(es). When a process is complete, an event is raised to indicate the completion of the process.

This event triggers the successor process to receive the status of the predecessor, request any needed
additional information, and then execute. The successor process is responsible to gather information
and run correctly.

SAP AG

BW360

10-5

0.6
Transaction RSPC: Process Chains Maintenence

General Services
Start Process
AND (Last)
OR (Each)
EXOR (First)
ABAP Program
Operating System Command
Local Process Chain
Remote Process Chain
Load Process and Subsequent Processing
Data Loading Process
Read PSA and update data target
Save Hierarchy
Further Processing of ODS Object Data
Data Export into External Systems
Delete Overlapping Requests from InfoCube
Data Target Administration
Delete Index
Generate Index
Construct Database Statistics
Initial Fill of New Aggregates
Roll Up of Filled Aggregates
Compression of the InfoCube
Activate ODS Object Data
Complete Deletion of Data Target Contents
Other BW Processes
Attribute Change Run
Adjustment of Time-Dependent Aggregates
Deletion of Requests from PSA

Start
PC Immediate

Load Data
PC Customer Attributes

Attrib. Change
PC Change Run

Data Target Contents

PC Cube Deletion

Load Data
PC Transaction Data

ODSO Data
PC Activate just loaded request

AND
PC Cube deleted and ODS data activated

SAP AG 2003

Easy creation of process chains via Drag & Drop.

Creation of items possible.

SAP AG

BW360

10-6

0.7
RSPC User Interface: Building a Process Chain
Load Process and Subsequent Processing
Data Loading Process
Read PSA and update data target
Save Hierarchy
Further Processing of ODS Object Data
Data Export into External Systems
Delete Overlapping Requests from InfoCube
Data Target Administration
Delete Index
Generate Index
Construct Database Statistics
Initial Fill of New Aggregates
Roll Up of Filled Aggregates
Drag and
Compression of the InfoCube
Activate ODS Object Data
Complete Deletion of Data Target Contents
Other BW Processes
Attribute Change Run
Adjustment of Time-Dependent Aggregates
Deletion of Requests from PSA
General Services
Start Process
AND (Last)
OR (Each)
EXOR (First)

Start
TR

Load Data

drop

TR Texts

Draw line to
connect
processes

Attrib. Change
TR Characteristics

SAP AG 2003

When you draw a line to connect processes, you are prompted to indicate whether the subsequent
process should execute based on the success or the failure of the predecessor process. In other words,
it is possible to schedule a process to run only if the predecessor process fails.

SAP AG

BW360

10-7

0.8
Automatic Insertion of Corresponding Process
Types
If a process is inserted into the process chain the corresponding process
variants are inserted into the process chain automatically:

Example:
You drag and drop a data load
process to your process chain,
the Index drop and the Index
create process are automatically
inserted.
If you want no corresponding
processes to be inserted
automatically, flag the (user
specific) setting in the menu
under Settings Default
Chains

SAP AG 2003

SAP AG

BW360

10-8

0.9
Collector Processes
Collectors are used to manage multiple processes that feed into
the same subsequent process. The collectors available for BW
are:
AND: All of the processes that are direct predecessors must send
an event in order for subsequent processes to be executed
OR: A least one predecessor process must send an event

The first predecessor process that sends an event triggers the

subsequent process

EXOR: Exclusive OR

Similar to regular OR, but there is only ONE execution of the

successor processes, even if several predecessor processes
raise an event

SAP AG 2003

Collector processes allow the designer of a process chain to trigger a subsequent process based on
whether certain conditions are met by multiple predecessor processes.

Application processes are the other type of processes these represent BW activities such as
aggregate rollup, etc.

Although the AND condition is implemented for process chains using the event chain functionality
from 2.x, this event chain is internal and cannot be edited.

SAP AG

BW360

10-9

0.10
Application Processes
Application processes represent BW activities that are typically
performed as part of BW operations. Examples include:
Data load
Attribute/Hierarchy Change run
Aggregate rollup
Reporting Agent Settings

Other special types of application processes exist:

Starter process that exists to trigger process chain execution
ABAP program
Another process chain
Remote process chains
Operating System command
Customer built process

SAP AG 2003

A starter process is part of every process chain.

SAP AG

BW360

10-10

0.11
Start Process

Variant
name and
description

Direct scheduling:
Job BI_PROCESS_TRIGGER will be
scheduled when the process chain
is acitvated.

Start using Meta Chain of API:

No BI_PROCESS_TRIGGER will be scheduled.
Start of the process chain have to be done
via FM RSPC_API_CHAIN_START
or
with another process chain

Scheduling Options for

SAP Basis Job Scheduler
(only used when direct
scheduling is chosen)

SAP AG 2003

The process variant could be used just by one process chain.

Each process chain could be started manually or via RFC connection with the function module
RSPC_API_CHAIN_START.

SAP AG

BW360

10-11

0.12
Basic Principles
Openness abstract meaning of process: Any activity with
defined start and defined ending
Security founding on the batch administration:
Processes get planned before they run and can be viewed with
standard batch-monitor
Dumps and Aborts are caught and thus can be treated as failures

Responsibility:
Each process have to care for all necessary information and
dependencies for its own, when it is added to the process chain.
Predecessor process is not responsible to start the correct
successors and provide them with necessary information

SAP AG 2003

Functions of the predecessor and successor processes:

Predecessor process runs then signals when it has completed, writing information about the
completed task to a database table (RSPCPROCESSLOG).
Successor process reacts to the event which is triggered by the predecessor, reads the database
table (RSPCVARIANT, RSPCVARIANTATTR) to obtain any needed information, then executes.
Additional administrative process is to check the sequence of the processes.

SAP AG

BW360

10-12

0.13
Structure of a Process
Attribute Change Run

Type Kind of task

ps_attrib2_long
PA_ATTRIB2
Execute InfoPackage: ZPAK_4QVBBF65GZONPAP96APH2P3KQ

Variant Configuration

Process = process type + variant

Additionally:
Sequence at Runtime:

Get the variant and predecessor list

Check status information from predecessors

Execution of the process

Report ending with status

Instance: Messages and information written to table

RSPCINSTANCE and RSPCPROCESSLOG at runtime

SAP AG 2003

RSPCINSTANCE are storing meta data for the successor

process (process type, variant ...)
RSPCPROCESSLOG: log information about the different
processes collected at runtime

A process type is an ABAP OO object.

The object is initiated when it is time for a process to run.

The variant holds the specific configuration information for a process.

Variant Configuration
Each process can have one or several variants
Maintenance of variant is specific for every process type

Instance: (instance for process is like request for infopackage)

snapshot of the variant configuration (table RSPCVARIANT*) at runtime and written to table
RSPCINSTANCE
Log information about the different processes collected at runtime and written to table
RSPCPROCESSLOG

SAP AG

BW360

10-13

0.14
Example: Structure of a Process Process Type
Other BW Processes

Type Attribute Change Run

Attribute Change Run

Execute the hierarchy and attribute change run

Process types can be maintained via Settings Process Types

Do not change standard process types (if allowed)

Change View "Possible Process Types": Details

SAP AG 2003

If standard process types can be changed depending on its name range (transaction SE06).

Dont modify standard process types, but you can create your own process types (see HOW TO
Guides on service.sap.com/bw service&implemation How To ... Guide).

RSPC Settings Maintain Process type (= Table/maintenance view RSPROCESSTYPES)

(SM30)) contains all information about the defined process types.

SAP AG

BW360

10-14

0.15
Example: Structure of a Process Variant
Variant Configure the Hierarchy and Attribute Change run
Execute the specific hierarchy and attribute change run for which
hierarchy, which InfoObject or which data loading process

Process Maintenance: Attribute Change Run

Variant
ASUG_COST_HIER_CHANGE
ASUG cost center hierarchy attrib...

Selection (1) 4 Entries found

Restrictions

To Select, Press F4 On The Object Typ

Object
Execute Typ
Object Na HIERARCHY
Execute InfoPackage
INFOOBJECT
LOADING
REPORTVARI

Object
Hierarchy
InfoObject
Execute InfoPacka.
Report Variants

4 Entries found

SAP AG 2003

Variants have to be created for the process types. With variant settings the process type gets
necessary information for execution.

For example:
If you assign the process type Attribute Change run to a process chain you must define a variant.
With this variant you have to define the InfoObjects for which you want to activate the master
data. There are four different possibilities:
HIERARCHY: direct selection of the hierarchy which need to be activated
INFOOBJECT: direct selection of the infoobjects which need to be activated
LOADING: indirect selection: reference to an InfoPackage, which must be loaded before in the
process chain. Combined with the meta data of these objects and the instance information the
system derives the affected InfoObjects and hierarchies. If the chosen LOADING object is not
in the process chain, the system automatically inserts the chosen infopackage in process chain.
REPORTVARIANT: indirect selection: reference to a change run variant which you can
define with RSDDS_AGGREGATES_MAINTAIN (SE38) or TCode RSATTR Executing
the Attribute/hierarchy change run with Variant:
Instead of applying the InfoObjects or hierarachies directly to the process variant in RSPC you
can create a central variant for the report RSDDS_AGGREGATES_MAINTAIN. You can
assign InfoObjects and hierarchies to this report variant. This central variant could be used by
several process variants in RSPC. The benefits are central maintenance, ..

Using a reference object like LOADING or REPORTVARIANT is sometimes more flexible.

SAP AG

BW360

10-15

0.16
3 Different Views to Process Chains

Planning view for

checking the plan
status of the
process chain

Checking view for

check consistency
of the process
chain

Log View for

monitoring
maintenance activities
and executions

Views related to the working area

working
area

Different views to the

the activities which
are possible:
Process chains
Process types
Data targets
InfoSources
Logs

SAP AG 2003

There are three main views in the icon bar with different views:
Planning view (shows if the process chain is active)
- Grey: unplanned processes (e.g. not activated process chain)
- Green: planned processes (process chain is active and start process is released)
- Yellow: planned but unknown processes
- Red: multiple planned processes
Checking view (consistency check like double used start variants, missing index deletion and
recreation, wrong references in variants, ...)
- Green: Error-free processes
- Yellow: Process with warnings
- Red: Process with errors
Log view
- Grey: Not yet run
- Green: Finished without error
- Yellow: running
- Red: aborted or failed
note that the log information is a usually mixture of
- log information of maintenance activites (e.g. new process, change of design, activation)
- log information of WHM activites (like previous executions of process chains)

SAP AG

BW360

10-16

0.17
Different Object Trees for Process Chain
Administration (1)
For easy administration on process chains different object trees

can be displayed.
Display
component

Process Types
Available process
types

Process
chain

Process types can be created via

Settings Process Types

Creation and assignment of Display

Components via menu or via button

Further information included in

section Implementing a process

SAP AG 2003

Folders in the process chain are called display components.

For mainentance of display components you have to use process chains attributes display
components.
For reassignment of process chain to different display component
For creation of new display component

SAP AG

BW360

10-17

0.18
Different Object Trees for Process Chain
Administration (2)
For easy administration on process chains, different object trees

can be displayed.

Log
Display the log tree

InfoAreas

InfoSources

Search in
InfoProvider tree

Search in InfoSources
tree for InfoPackages

Possible processes on data

target are displayed

In InfoPackage reference to
process chain is displayed

SAP AG 2003

SAP AG

BW360

10-18

0.19
Maintain Process Chains Detail View

RSPC > View > Detail

View:
Technical names
Ability to move boxes
to re-design the
process chain
Hidden collector
processes are
displayed

Note: In detail view, a collector

process is displayed as multiple
collector processes (needed for
conditions)

SAP AG 2003

When collector processes are built into a process chain, there are actually several background jobs
scheduled with events in order to construct the conditional nature of collector processes.

The simple view displays the processing chain as it exists logically. The detail view displays the
processing chain with the extra collector processes.

SAP AG

BW360

10-19

0.20
Maintain Message

Write a message and fill

in recipient and type. Info
saved within process
variant.

Send with Note

Planning view
context menu

Bwadmin@sap.com
BWADMIN@sap.com

SAP AG 2003

Email can be sent to indicate successful or completion of a process too.

SAP AG

BW360

10-20

0.21
Monitoring Features of the Log View (RSPC)

Log View: Double Click on Process to

Launch Job Log Viewer
The log view is the tool for monitoring
the process chain execution

SAP AG 2003

SAP AG

BW360

10-21

0.22
Process Chain and Data Target Administration
You can call the administration of the current data target
by using the context menu for the following processes:
Construct Indexes
Delete Indexes
Construct database statistics
Roll-Up filled aggregates
Compress InfoCube
Activate ODS object data

SAP AG 2003

SAP AG

BW360

10-22

0.23
Process Chains: Facts
Process chains are transportable
There are icons for writing to a change request when maintaining a
process chain in RSPC
Process chains can be selected from the transport connection
wizard within the administrator workbench

Special background jobs are run to facilitate the execution of

the process chain
BI_PROCESS_TRIGGER
Generated jobs BI_EVEN*

SAP AG 2003

SAP AG

BW360

10-23

0.24
Activation, Execution and Runtime
Activation of process chain (Pressing activation button)
Process chain is copied to active version
No scheduling of any batch jobs (since SP 5, BW3.0B)

Execution of process chain (Pressing execution button)

Process BI_PROCESS_TRIGGER is scheduled and released with the
configured options (only if direct scheduling is applied for the start
process)
The subsequent application processes are scheduled and released

Event triggered
As program RSPROCESS with type and variant given as
parameters
With job name BI_PROCESS_<TYPE> (except AND-process,
which is BI_EVEN<GUID>)

Runtime of process chain

Instance information is written to table RSPCINSTANCE
Log information is written to table RSPCPROCESSLOG

SAP AG 2003

Activation:
process chain is set to version active
RSPCVARIANT, RSPCVARIANTATTR, contain information about the configuration

Execution:
Start process is set to direct scheduling:
BI_PROCESS_TRIGGER is released with configured start options
Subsequent application processes are scheduled and released as event triggered jobs.
Start process is set to Start Using Meta Chain or API
No BI_PROCESS_TRIGGER is scheduled or released. You have to start the process chain via
other process chain or API (Function module: RSPC_API_CHAIN_START).
Subsequent application processes are scheduled and released as event triggered jobs.

All scheduled jobs are using ABAP Report RSPROCESS with certain parameters

Separation between Activation and Execution with two buttons available since BW3.0B SP5

The application processes themselves care for sending log information, .

There are no further specific process chain jobs in background for controlling the application
processes(except: periodic CCMS job: SAP_CCMS_MONI_BATCH_DP)

SAP AG

BW360

10-24

0.25
Polling Flag

With setting the polling flag you can control the behavior of the
main process when you have distributed processes (Process
Chain Attributes Polling).
The main job run all the time in parallel (flag is set) or is only
triggered by a finished process of the process chain (flag is not
set: default).

SAP AG 2003

With setting the polling flag you can control the behavior of the main process when you have
distributed processes. Distributed processes, such as the loading process, are characterized as having
different work processes involved in specific tasks.

With the polling flag you determine whether the main process needs to be kept as long as the actual
process has ended.

Setting the indicator has the following advantages:

A high level of process security is guaranteed
External scheduling tools that react only to the SAP internal event 'Batch Process Complete', are
also informed about the status of distributed processes.

Setting the indicator also has the following disadvantages:

Increased demand on resources. Although the CPU is not under pressure during the waiting time, it
is during the status checks that run at two minute intervals.
You require one more background process.

SAP AG

BW360

10-25

0.26
Monitoring of Individual Process Chain

right

Execution of
process chain

SAP AG 2003

Use Right mouse click in order to see the available functionality.

With the log view of a process chain, monitoring of special BW processes (like infopackages, change
run, precalculation) and common activities (like drop/create index) is possible. Right mouse click on
a process icon gives you the available log functionality.

Different processes are clearly arranged in one view and directly linked to the corresponding logs.

Some processes (depending on the process type) are restartable.

SAP AG

BW360

10-26

0.27
Restartability of Process Types
For each process type (self defined
or standard) re-starting is a feature
which is set in table:
RSPROCESSTYPES

SAP AG 2003

SAP AG

BW360

10-27

0.28
Overview:
Systemwide Monitoring of Process Chains

Monitoring of process chain

BWCCMS

Metachain

AWB-Monitoring of
individual
InfoPackages,
monitoring of
application log via
Tcode SLG1

External monitoring
tools

SAP AG 2003

Four different ways for monitoring all process chains are possible
Via CCMS (either T-Code: RZ20 or BWCCMS)
Via Metachain: create a matachain including all your different process chains of your company.
With status colour green, yellow or red you get a quick overview to the overall status of processes
on your system
Via monitoring different processes in process chains for themselves
Via external monitoring tools (alias: softwarepartner on service.sap.com)

SAP AG

BW360

10-28

0.29
Systemwide Monitoring BWCCMS
Recommended way:
Monitoring via SAP-central computing center management system (CCMS):
Menu path: Tools CCMS Control / Monitoring Alert Monitor SAP BW Monitors
BW Monitor (Tcode: BWCCMS)

SAP BW Monitors (BW Monitor) Mainenance Functions OFF

SAP AG 2003

Process chains are included automatically in BWCCMS

Job SAP_CCMS_MONI_BATCH_DP checks hourly the status of process chains.

Activation of SAP_CCMS_MONI_BATCH_DP is necessary for CCMS monitoring generally
once after installation
RZ21: technical infrastructure method execution activate background dispatching

SAP AG

BW360

10-29

0.30
Systemwide Monitoring BWCCMS
Advantages and disadvantages of BWCCMS
Advantages:
Self-definition of alerts possible
Clearly arranged
Alerts linked to detailed monitors
Application log and BW log combined

Disadvantages:
Maintenance not easy

SAP AG 2003

Process chains are assigned to BWCCMS per default.

SAP AG

BW360

10-30

0.31
Systemwide Monitoring Metachain
Meta chain means = chain with process type process chain

Process Chain Maintenance Log View ps_metachain for systemwide...

Start process

Process chains

SAP AG 2003

Advantages:
Graphical view
Easy to find the logs

Disadvantages:
It is not possible to filter the terminated parts of the metachain. Therefore, the view gets confusing
if you build a complex scenario with too many different process chains.
Performance is influenced by graphical design (to much navigation to see the detailed logs)
Sometimes low performance in execution log views

SAP AG

BW360

10-31

0.32
Systemwide Monitoring AWB Monitor, Appl.log
Not using the new BW 3.0
functionality of process
chain for analyze the BW
processes means checking
different logs areas
manually:
Load monitors (AWB)
Changerun monitor (AWB)
Application log (AWB)
(SLG1),
...

SAP AG 2003

Advantages:
Fast access to detailed logs

Disadvantage:
Each log is only part of the entire process. You have to look for the different logs yourself.
Monitoring of the entire process not possible
Very complex in large environments
Detailed expert knowledge about the different log areas necessary.

SAP AG

BW360

10-32

0.33
Migration (1)
Process Chains are new functionality
Old Event-Chains, InfoPackages and InfoPackage Groups still
working, even after migration
In process chains automatic flags (auto rollup, auto drop index,
auto activation) are not working anymore
It is recommended to switch to process chains
If an InfoPackage is started via a process chain, the flags for
automatic processing within the BW are ignored even if they are
set, thus the respective task must be added to the process chain

SAP AG 2003

Old Event-Chains, InfoPackages and InfoPackage Groups continue to work, even after migration
You do not have to migrate.

New 3.0 projects shall be modeled with process chains, as there will be no more Support via the SAP
Service Marketplace for problems with the automatism-flags like automatic rollup, automatic
ODS-activation

SAP AG

BW360

10-33

0.34
Migration (2)
InfoPackage Groups
From within the InfoPackage Group maintenance the button
Process Chain generates a process chain similar to a group, but
manual ajustment is necessary.
This can be executed manually with the function module
RSPC_MIGRATE_INFOPACKAGE_GROUP

Event Chains
The Event Collector (formerly also called Event Chain) is now the
AND-Process of the process chain
Migrating a manually created chain of events into a process chain is
difficult and fuzzy
There exists a report RSPC_MIGRATE_EVENT_CHAIN which
browses the system for reports planned waiting for an event and
reports raising an event, however the generated process chain may
differ from the existing event chain

Note: In both cases the generated chain needs to be verified and

adapted manually

SAP AG 2003

SAP AG

BW360

10-34

0.35
Openness: Implementing a Process
If you ...
... have a simple, stand alone program to run in a chain
... have a program, which is planned in batch by another program or
user

... then you can use the process type ABAP to run your
program in a chain.

However if you ...

... want to ask predecessor processes of your program
... write a log, which shall be displayed in the process monitor
... have implemented an user monitor
... have a customizing screen, which is more difficult than the
parameters of a program

... then it is recommended to implement your own process type

SAP AG 2003

It is possible for the customer project to custom build a process. An entirely new type of task can be
created and included in the chain. Use of ABAP OO is required to implement this.

For building your own process types, please check HOW TO-Guide: service.sap.com/bw
service&implemation How To ... Guide.

Dont modify standard process types.

SAP AG

BW360

10-35

0.36
Process Chains in BW: Unit Summary

Now you will be able to:

To use and customize process chains.

SAP AG 2003

SAP AG

BW360

10-36

0.37 Exercises
Unit:

Process Chains

Topic:

Creation and monitoring of a process chain

At the conclusion of this exercise, you will be able to:

Manage process chains

In order to have a fully automated BW system you want to set up all

processes with process chains.

1-1

Check settings for process chains

1-1-1

1-2

Goto planning view and check that automatic suggestion of processes

is switched on(settings default chains)

Define your own process chain pc_gr##

1-2-1

Define variant for start process startpr##. Scheduling it immediately.

1-2-2

Define variant loadpack## for dataload with infopack_slflight##

1-2-3

Disperge the different objects placed in the planning view

1-3

Switch to check view and check your process chain

1-4

Activate and execute the process chain

1-5

Switch to log view and monitor the different processes.

SAP AG

BW360

10-37

 SAP AG

BW360

10-38

0.38 Solutions
Unit:

Process Chains

Topic:

Creation and monitoring of a process chain

Create DataSource, InfoObjects, InfoSource and InfoCube for later transportation

1-1

Check settings for process chains

1-1-1

Goto planning view and check that automatic suggestion of processes is

switched on(settings default chains)
Goto transaction RSPC. Goto planning view and choose any existing
process chain via double click. Then goto settingss default chains....

1-2

Define your own process chain pc_gr##

1-2-1

Define variant for start process startpr##. Scheduling it immediately.

Start planning view in RSPC. Mark display component BW Training
Click icon create.
Field Name

Values

Process Chain

PC_GR##

Long Description

process chain group ##

Create start proces variant:

Field Name

Values

Process Variants

startpr##

Long Description

start process group ##

Choose direct scheduling.

Press on change selections. Choose Immediate. Save!
Next screen. Press: Save! (for saving the process chain itself)
Go back. Press O.K. button.

SAP AG

BW360

10-39

1-2-2

Define variant loadpack## for dataload with infopack_slflight##

Goto the process type View. Drag and drop Execute Infoackage to the
workarea.
Next Popup: Press F4 on Process variants. Choose Infoackage
infopack_sflight## and press O.k.-button.
Now drop and create index item is automatically applied to the process
chain.

1-2-3

Disperge the different objects placed in the planning view.

Move the start process icon to the top of the work area.
Then place the index drop icon beneath the start process icon.
Then place the execute infopackage icon beneath the index drop icon.
Then place the create index icon beneath the execute Infopackage icon.
Create the connection between start process icon and drop index icon
(create black arrow)

1-3

Switch to check view and check your process chain

1-4

Activate and execute the process chain

Press at first activation button. Then press execution button.

1-5

Switch to log view and monitor the different processes.

Refresh periodically. The running process appears in yellow colour. The sucessfully
finished processes appear in green colour.

SAP AG

BW360

10-40