Process Chains

Operating BW 3.0 usingProcess Chains

Rudolf HenneckeSAP AG, RIG BI

01

SAP AG 2001, Title of Presentation, Speaker Name 2

Introduction

Data LoadMonitor

Data TargetMaintenance

Start

Load into PSA

Load into ODS

ActivateData in ODS

Load into Cube

Build Indices

Build DBStatistics

Roll upAggregates

Drop Indices

02


Motivation

Automating the BW administration

Graphical modelling and monitoring

Central monitoring of all BW processes

Openness for all kinds of processes

High termination security

Moving responsibility into the individual processes

Outside in

Inside out

03


Basic principles

Openness abstract meaning of „process“: „Any activity with definedstart and defined ending“

Security founding on the batch administration:Processes get planned before they run and can be viewed with standard batch-monitorStarting of successors via batch-eventsDumps and Aborts are caught and thus can be treated as failures

Responsibility:Not the predecessor is responsible to start the correct successors and providethem with the information they need,but the successors are responsible to run correctly and gather the informationthey need

Programming model:

Communication between processes via asking the predecessors

loose coupling of the processes to guarantee extensibility 04


Maintenance: Example

Transaction:

RSPC

05


Collector processes are used to manage multiple predecessorprocesses that feed into the same subsequent process. The collectorprocesses available for BW are:

AND: All of the processes that are direct predecessors must sendan event in order for subsequent processes to be executedOR: A least one predecessor process must send an event

The first predecessor process that sends an event triggers thesubsequent processAny additional predecessor processes that send an event will againtrigger subsequent process (Only if the chain is planned as“periodic”)

EXOR: Exclusive “OR”Similar to regular “OR”, but there is only ONE execution of thesuccessor processes, even if several predecessor processes raise anevent

06Collector Processes


Application Processes

Application processes represent BW activities that are typicallyperformed as part of BW operations. Examples include:

Data loadAttribute/Hierarchy Change runAggregate rollup

Other special types of application processes exist:

Starter – process that exists to trigger process chain executionABAP programAnother event chainRemote process chainsOperating System commandCustomer built process

07


Structure of a process

Type – Kind of taskOne ABAP-OO-Class per type

Variant – ConfigurationEach process can have one or several variantsMaintenance of variant is specific for every process type

Instance – Messages and information for the successorsGets fixed at runtime

Runtime:Get the variant and predecessor listInstantiateEvt. ask predecessorsExecutionReport ending with status and instance

08


Structure of a process – Example on process type

Type – Attribute Change RunExecute the hierarchy and attribute change runProcess types can be maintained via Settings – Process Types

Do not change standard process types (if allowed)

09


Structure of a process – Example on variant

Variant – Configure the Hierarchy and Attribute Change runExecute the specific hierarchy and attribute change run for whichhierarchy, which InfoObject or which data loading process

10


Variant Maintenance: References

Example: Start chain, load master data, upon success,perform change run

Process Variants can have the objectsto be worked on entered directly

ora reference to a preceding(loading) process, which

knows the objects

11


Structure of a process – Example on instance

Instance – and RuntimeDid the successor finish in the expected way ?

Depends on the successor process typeDepends on the colour of the link (condition)

Get information about the variantGet information from the predecessor process

(p.eg. request number)Execute the hierarchy and attribute change runReport ending with status and instance for successor

12


Maintenance: Views (Coloring of Processes)

Planning view: Build and change process chainsGrey: unplanned processesGreen: planned processesYellow: planned but unknown processesRed: multiple planned processes

Check view: Check for errors in designGreen: Error-free processesYellow: Process with warningsRed: Process with errors

Log view: Monitoring of process chainsGrey: Not yet runGreen: Finished without errorYellow: runningRed: broken or failed

13


Different object trees for process chain administration

For easy administration on process chains different objecttrees can be displayed.

Process ChainsAvailable processchains (displaycomponents)

Process TypesAvailable processtypes

14Creation and assignment of displaycomponents via menu or via button

Process types can be created viaSettings – Process TypesFurther information included insection „Implementing aprocess“


For easy administration on process chains different objecttrees can be displayed. Log

Display the log tree

InfoAreasSearch inInfoProvider tree

InfoSourcesSearch in InfoSourcestree for InfoPackages

15Possible processes on data targetare displayed

In InfoPackage reference toprocess chain is displayed

Different object trees for process chain administration


Basic Process Chain: Planning View

Example: Start chain, load master data, upon success,perform change run

Line shows as green because theevent to trigger the subsequentprocess is raised at successful

ending of the process.

Line shows as black because theprocess can only run and end (no

difference between unsuccessful andsuccessful ending).

16


Maintain Process Chains – Detail View

RSPC > View > DetailView

Technical names

Ability to move boxesto re-design theprocess chain

“Hidden” collectorprocesses aredisplayed

Note: In detail view, a collector process is displayed asmultiple collector processes (needed for conditions) 17


Failed processes can send email!

Planning viewcontext menu

Write a messageand fill in recipient

and type. Infosaved within

process variant.

18


Process Chain and Data Target administration

From BW 3.0A SP7 you can call the administration of the current datatarget by using the context menu for the following processes:

Construct IndexesDelete IndexesConstruct database statisticsRoll-Up filled aggregatesCompress InfoCubeActivate ODS object data

19


Automatic insertion of corresponding process types

If a process is inserted to the process chain that is linked by defaultto other processes the corresponding process variants are insertedinto the process chain automatically:

Example: you drag and drop a data load process to your process chainand the Index drop and the Index create process are automaticallyinserted

If you want want no corresponding processes to be insertedautomatically please flag the (user specific) setting in the menu underSettings Default Chains

20


Process Chains: Facts

Process chains are transportableThere are icons for writing to a change request when maintaining aprocess chain in RSPCProcess chains can be selected from the transport connection wizardwithin the administrator workbench

If a process “dumps”, it is treated in the same manner as a failedprocess

The graphical display of the RSPC transaction requires the BW 3.0AFront-end GUI, as special OCX’s are delivered

Special background jobs are run to facilitate the execution of theprocess chain

Note your BTC process distribution, and make sure that an extra BTC isfree so the supporting background jobs can run

21


Interaction with Batch

When a chain gets activatedit will be copied into active versionthe processes will be planned in batch• as program RSPROCESS with type and variant given as

parameters• with jobname BI_PROCESS_<TYPE> (except AND-process,

which is BI_EVEN<GUID>)• waiting for event, except the trigger• The trigger is planned as specified in its variant, if “start

via meta-chain” it is not planned to batch

The jobs are identified by the frameworkas long as they did not yet run• via their jobname and• via the event, on which they wait and• via the program variant, which is stored in the steplist of

the jobat runtime via GET_JOB_RUNTIME_INFO. The jobcountis stored in the log.for the log-display via jobname and jobcount 22


Migration (I)

The Process Chain functionality is set aside the current functions

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

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

If an InfoPackage is started in the old fashion, these flags will workas in 2.0B

If an InfoPackage is started via a process chain, the flags areignored, thus the respective task must be added to the process chain

23


Migration (II)

InfoPackage GroupsFrom within the InfoPackage Group maintenance the button “ProcessChain” generates a process chain alike the group.This can be executed manually with the function moduleRSPC_MIGRATE_INFOPACKAGE_GROUP

Event ChainsThe Event Collector (formerly also called Event Chain) is now the AND-Process of the process chainMigrating a manually created chain of events into a process chain isdifficult and fuzzyThere exists a report RSPC_MIGRATE_EVENT_CHAIN which browsesthe system for reports planned waiting for an event and reports raisingan event, however the generated process chain may differ from theexisting event chain

In both cases the generated chain needs to be verified and adaptedmanually 24


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 anotherprogram or user

...then you can use the process type ‚ABAP‘ to run yourprogram in a chain.However if you...

...Want to ask predecessor processes of your program

...Write an own log, which shall be displayed in the processmonitor...Have implemented an own monitor...Have a customizing screen, which is more difficult than the„parameters“ of a program

...then it is recommended to implement an own process type 25



Interfaces: IF_RSPC_*EXECUTE – Execution of the processGET_INFO – Give Information to successorsGET_LOG – Give back messagesMAINTAIN – Maintenance of variantsGET_VARIANT – F4 for variantsGET_DEFAULT_CHAIN – Give default-chain for a processCHECK – Check consistenyGET_STATUS – Give status of instanceCALL_MONITOR – own monitoring toolTRANSPORT – give back TLOGO-entryCONTEXT_MENU – Enhance context-menu

Make entry in view RSPROCESSTYPES

The interfaces are documented in the system26



XXTRANSPORT

XXCONTEXT_MENU

XXCALL_MONITORXXXGET_STATUSXXCHECKXXGET_DEFAULT_CHAIN

XXGET_VARIANT

XXMAINTAINXXXGET_LOGXXXGET_INFO

XXEXECUTE

optionalalterna-tively

manda-tory

LogView

RuntimeMain-tainance

Interfaces:Implementing is...Method called at...

27


Outlook: 3.0B and Beyond

Process type „Reporting Agent Setting“

Process type „Archiving Run“

Integration with SAP Workflow

28


Further information

Further information can be found...In SAP Service Marketplace alias BW infolder Documentation DocumentationEnhancements

3.0A SP05 Process Chains3.0A SP07 Process Chains

In SAP Service Marketplace alias BW infolder Documentation

3.0A Online Documentation

29


No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software componentsof other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks ofMicrosoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, andOS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM are registered trademarks of Informix SoftwareIncorporated.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® andother Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technologyinvented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other productsmentioned are trademarks or registered trademarks of their respective companies.

Copyright 2001 SAP AG. All rights reserved

Date post:	12-Dec-2015
Category:	Documents
Upload:	elky-gonzales
View:	227 times
Download:	2 times

Process Chains

Documents