using process chains in sap business information warehouse

© 2003 SAP AG BW 255, Peter/Rinneberg 1

SAP TechEd ‘03 Basel

Using Process Chains in SAP Business Information WarehouseAlexander PeterProduct Management BI, SAP AG

Thomas RinnebergDevelopment BI, SAP AG

2003 SAP AG, TechED EMEA, BW 255, Peter/Rinneberg 2

Learning Objectives

At the end of this lecture, you will be able to:

Understand Process Chains as an intuitive and easy way to administer your SAP BW

Explain which process types are delivered by SAP

Implement your own process types




SAP NetWeaver™Turning Enterprise Services Architecture Vision Into Reality

The open integration and application platform for TCO reduction

Integrate people, information and processes…… in 1 hub …… across technologiesand organizations.Enterprise-scale Java and ABAP application platform.NET and WebSphere interoperability and extensibilityPre-configured with business contentAdapters to non-SAP

SAP NetWeaver™

Com

posi

te A

pplic

atio

n Fr

amew

ork

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus. Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

Integration Broker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAP

Life Cycle M

gmt

…


Agenda

Building and Monitoring Process Chains

Process Chain Architecture

Selected Process Types

Behind the Scenes

Process Structure

Building your own Process Type




Agenda




Behind the Scenes

Process Structure



Introduction: Typical Data Load Cycle

Data Load Monitor

Data Target Maintenance

Start

Load into PSA

Load into ODS

Activate Data in ODS

Load into Cube

Build Indices

Build DB Statistics

Roll up Aggregates

Drop Indices




Process Chains: Concepts

Start

Data Load A

Data Load X

Drop IC Indices

Email System Admin

Failure? Success?

Concept Example:Building a process

control flow

Data Load B

Data Load C

Success off all 3?

Failure?

Email System Admin

Failure?

Email System Admin

Load 3 InfoPackages in Parallel into 1 InfoCube

Build IC Indices


Development Model for Process Chain Functionality

Automating BW activities

Graphical modelling and monitoring

Central monitoring of BW processes

Openness for all kinds of processes

High termination security

Moving “responsibility” into the individual processes

Outside in

Inside out




Basic principles (1)

Openness ⇒ abstract meaning of “process“: “Any activity with defined start and defined ending”

Security ⇒ founding on the batch job 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


Basic principles (2)

⇒ Responsibility:Predecessor process is not responsible to start the correct successors and provide them with necessary information The successor processes are only responsible to run correctly and gather the necessary information

⇒ Programming model:

Communication between processes: Check the status info of the predecessor process

Loose coupling of the processes to guarantees extensibility (ability to implement your own process using ABAP OO)




Process Chains Maintenance

Note the

available

process

types


Agenda




Behind the Scenes

Process Structure





Structure of a process

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

Variant – ConfigurationDefines characteristics of this process objectMaintenance of variant is specific for every process type

Instance – Messages and information for the successorsThe process object is instantiated at runtime

Runtime:Get the variant and predecessor listInstantiate process objectAsk predecessors for information Execution of the defined processReport ending with status and instance


Process Chains: Flow for Object Instantiation

Start

Data Load

Data Load X

Drop ICIndices

Email System Admin

Failure? Success?

Sequence of Object Instantiation of a

Process at Runtime

Success?Failure?

Email System Admin

Predecessor Process

Successor Process

input Information

Write Status, also:Any Additional Information?

Execute

Drop IC Indices

Drop ICIndices

Build IC Indices




Structure of a process – Example of process type

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

Do not change standard process types (if allowed)


Structure of a process – Example of variant

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




Variant Maintenance: References to Predecessor

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

Process Variants can have the objects to be worked on entered directly

ora reference to a preceding (loading) process, which

knows the objects


Structure of a process – Example of instance

InstanceThe instance is defined by a unique handle (instance number, a GUID)Store Worklist with instance – this information canbe given to successorsStore logs and protocols with instanceThe instance has an execution statusEach instance is a batch job – a job count isattached to it




Agenda




Behind the Scenes

Process Structure



Collector Processes

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

AND : All of the direct predecessor processes must raise an event in order for subsequent processes to be executed

OR : A least one predecessor process must send an eventThe first predecessor process that sends an event triggers the subsequent processAny additional predecessor processes that send an event will again trigger subsequent process (Only if the chain is planned as “periodic”)

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




Process Chains: Concepts

Start

Data Load A

Data Load X

Drop IC Indices

Email System Admin

Failure? Success?

Concept Example:Building a process

control flow

Data Load B

Data Load C

Failure?

Email System Admin

Failure?

Email System Admin


Build IC Indices

AND Collector


Application Processes

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

Data loadAttribute/Hierarchy Change runAggregate rollupReporting Agent Settings

Other special types of application processes exist:

Starter – process that exists to initiate process chain executionABAP programAnother process chainCustomer built process




Application Process Types

Operating system commandAccess to OS commands like ‘dir’ (list contents of application server file system)Note: There is only an call “out” to OS, only Standard-Out is given back to BW

Remote process chainsSupports process chains in a data mart environment

Master data reorganizationReporting Agent Settings

Exception reportingPrint queries in backgroundPre-calculating web templatesPre-calculating characteristic variables of type pre-calculated value sets


Reporting Agent Process Parameterization

Process Variant requires Reporting Agent Package as only parameter




Agenda




Behind the Scenes

Process Structure



User Interface: Building a Process Chain

Drag and drop

Draw line to connect

processes




Building a Process Chain: Example

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

Line shows as green because the event to trigger the subsequent process is raised at successful

ending of the process.

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

difference between unsuccessful and successful ending).


Three Different Views in the Transaction

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




Different object trees when building process chains 1

For easy administration on process chains different object trees can be displayed.

Process Chains Available process chains (display components)

Process Types Available process types

Creation and assignment of display components via menu or via button

Process types can be created via Settings – Process Types

Further information included in section „Implementing a process“


Different object trees when building process chains 2

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

Display the log tree

InfoAreas Search in InfoProvider tree

InfoSources Search in InfoSources tree for InfoPackages

Possible processes on data target are displayed

In InfoPackage reference to process chain is displayed




Process Chains: Failed processes can send email!

Planning view context menu

Write a message and fill in recipient

and type. Info saved within

process variant.


Monitoring Features of the Log View

Log View: Double Click on Process to Launch Job Log Viewer

The log view is the tool for monitoringthe process chain execution




Agenda




Behind the Scenes

Process Structure



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 should be displayed in the process monitor...Have implemented an own monitor...Have a customizing screen, which is more difficult than the “parameters“ of a program

...then it is recommended to custom develop own process type




Implementing a Custom Designed Process

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 system


Implementing a Custom Designed Process

XXTRANSPORT

XXCONTEXT_MENU

XXCALL_MONITORXXXGET_STATUSXXCHECKXXGET_DEFAULT_CHAIN

XXGET_VARIANTXXMAINTAIN

XXXGET_LOGXXXGET_INFO

XXEXECUTE

optionalalterna-tively

manda-tory

Log View

RuntimeMain-tainance

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




Generic Services

There are several services for RSPC whichshall help you implementing a processtype:

Generic variant storage class: CL_RSPC_VARIANTGeneric dynpro service for variantmaintainance: Function moduleRSPC_VARIANT_MAINTAINGeneric instance storage class: CL_RSPC_INSTANCEWrapper class for application log forunambigous assignment of logs to instance CL_RSPC_APPL_LOGService function group: RSPC_SERVICES


Variant Storage Class

CL_RSPC_VARIANTCan be used, if your static worklist (cf. object model) can be saved as table RSPC_T_RSCEDST, that is

FNAM, (SIGN), (OPTION), LOW, (HIGH)Does the transport connection for you

You object will be known to TP as ‚R3TR‘ ‚RSPV‘ ‚<TYPE><VARIANT>‘If you need...

After ImportRelated ObjectsAdditional Objects

...you can implement the interface IF_RSPV_TRANSPORTDoes object locking for youDoes deletion of variants for youProvides an F4-help which is able to select...

with wildcardsby variant contents




Variant Maintainance Dynpro

Function module RSPC_VARIANT_MAINTAINRequires usage of CL_RSPC_VARIANTProvides a dynpro, which does...

Variant (re)-namingVariant documentation linkTransport linkLast changed byNavigation through variantsCreation of new variantsDeletion of variants

You provide a subscreen and a form-routine, which checks forchanges on the subscreenOk-Codes, which you must react on in PAI of your subscreen:

SAVE: Save the variantEXIT, BACK and CREA: Check if something has changed, and eventually save the variant


Generic Variant Maintainance Services

VariantService

YourSubscreen

DynproService

Your Abapclass

PAIRSPC_VARIANT_GET

Save

Free

RSPC_VARIANT_MAINTAIN

Create (Factory)

Get_info

PBO

Create (Factory)

IF_RSPC_MAINTAIN

This slide explains how RSPC_VARIANT_MAINTAIN and CL_RSPC_VARIANT work together and how to use them




Instance Storage Class / Application Log Class

CL_RSPC_INSTANCEFormat RS_T_RSCEDSTSaveGet_InfoF4, selecting by one field of instance content

CL_RSPC_APPL_LOGSaves mapping log handle vs. instanceObject = ‚BW_PROCESS‘, Subobject = <Type> Entry in slg0 requiredGenerates external numberProvides a display and retrieval method for the instance log


Agenda




Behind the Scenes

Process Structure





Process Chains: Facts

Process chains are transportableButton for writing to a change request when maintaining a process chain in RSPCProcess chains available in the transport connection wizard (administrator workbench)

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

Graphical display of Process Chain Maintenance requires the 620 SAPGUI and SAP BW 3.0B Front-end GUI

Recent front-end patches for both types!

A special control background job runs to facilitate the execution of the of the other batch jobs of the process chain

Note your BTC process distribution, and make sure that an extra BTC process is available so the supporting control job can run immediately


Collector Processes and the Detail View

Start

Data Load A

Data Load X

Drop IC Indices

Email System Admin

Failure? Success?

Data Load B

Data Load C

Failure?

Email System Admin

Failure?

Email System Admin


Build IC Indices

AND Collector

Remember the AND collector process?




Detail View and the AND Collector Process

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)


Process Chains and Data Target administration

You can call the administration of the current data target by using the context menu for the following processes:

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




Automatic insertion of corresponding process types

If a process is inserted to the process chain that is linked by default to other processes, the corresponding process variants are inserted into the process chain automatically:

Example: drag and drop a data load process to your process chainand the Index drop and the Index create processes are automatically inserted

Turn this feature off: (user specific) menu Settings Default Chains


Process Chains: Interaction with Batch Framework

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 job name BI_PROCESS_<TYPE>• 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 job name and• via the event, on which they wait and• via the program variant, which is stored in the step list of

the jobat runtime via GET_JOB_RUNTIME_INFO. The job count is stored in the log. for the log-display via job name and job count




Process Chains: CCMS integration

Monitoring via SAP Computing Center Management System (CCMS): Menu path: Tools CCMS Control / Monitoring Alert Monitor SAP BW Monitors BW Monitor


Migration to Process Chains (I)

Process Chains are a SAP BW 3.x feature

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

New 3.0 projects should be modeled with process chains, as there will be no more support for problems with the “automatism-flags” like “automatic rollup”, “automatic ODS-activation”…

If an InfoPackage is started in the old fashion, these flags will work as in SAP BW 2.x

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




Migration to Process Chains (II)

InfoPackage GroupsFrom within the InfoPackage Group maintenance the button “Process Chain” generates a process chain alike the group.This migration 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 is difficult and fuzzyThere 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

Each generated chain must verified and adapted manually!


Summary

Now you are able to:

Understand Process Chains as an intuitive and easy way to administer your SAP BW

Explain which process types are delivered by SAP

Implement your own process types




Further Information

Public Web:www.sap.com/biSAP Customer Services Network: www.sap.com/services/

Related SAP Education Training Opportunitieshttp://www.sap.com/education/BW 310 – BW Data WarehousingBW 340 – BW Data Staging

Consulting ContactRoy Wood, VP SAP NetWeaver Consulting Practice ([email protected])


Q&A

Questions?




Please complete your session evaluation anddrop it in the box on your way out.

Feedback

Thank You !

The SAP TechEd ’03 Basel Team


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express 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 components of other software vendors.

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

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

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® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, 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 technology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies.

Copyright 2002 SAP AG. All Rights Reserved

using process chains in sap business information warehouse

Documents