Professional Documents
Culture Documents
Introduction To Process Chains in SAP BI 7.0
Introduction To Process Chains in SAP BI 7.0
Applies to:
SAP BI 7.0. For more information, visit the Business Intelligence Homepage.
Summary
Process chains are a robust graphical scheduling & monitoring tool to maintain automation, visualization & monitoring of tasks/processes. These chained processes are designed to carry specific tasks. In this article, well discuss an introduction on process chains with a demo example - loading data into an info provider. Author: Arun Bala Ganesan
Author Bio
The author is presently working in Wipro Technologies with 1+ experience as Associate SAP BI Developer. His expertise includes SAP BI 7.0 and ABAP.
Table of Contents
Introduction ......................................................................................................................................................... 3 Usage of Process Chains ................................................................................................................................... 3 Process chains in SAP Business Intelligence .................................................................................................... 4 Process Chain Views ...................................................................................................................................... 4
Planning View: ....................................................................................................................................................... 4 Checking View: ...................................................................................................................................................... 4 Log View: ............................................................................................................................................................... 4
Step-by-Step Guide......................................................................................................................................... 4
Step 1: Creating a Data Model ..................................................................................................................................... 4 Step 2: Accessing Data from AL11 .............................................................................................................................. 5 Step 3: Creation of Transformation .............................................................................................................................. 8 Step 4 - Process Chain Planning ................................................................................................................................. 9
Trouble Shooting Process Chains ................................................................................................................ 13 Rescheduling Process Chains ...................................................................................................................... 14 Related Content ................................................................................................................................................ 16 Disclaimer and Liability Notice .......................................................................................................................... 17
Introduction
Process chains are a robust graphical scheduling & monitoring tool to maintain automation, visualization & monitoring of tasks/processes. These chained processes are designed to carry specific tasks. Process chains are integrated into CCMS, which is in turn integrated into portal based BI administration cockpit. What Process Chains does is simply automate complex tasks/process scheduling, visualization of these processes plus central controlling of these tasks (either in same or linked process chains). If a process chain isnt available for a specific task, SAP provides customers with an easy way to create custom process types, wherein one can still run customer programs using Business Content ABAP process types . A process chain consists of a start process, individual application processes and the so-called collection processes. The application processes are the actual processes. SAP BI supports process types like load process and post processing processes, Data target administration processes and other processes
Step-by-Step Guide Step 1: Creating a Data Model Create a process flow model for data to be loaded into some provider (say Info Cube/DSO). In the following diagrams we will see how to create one.
Fig.1.1 - Initially we first create an Info area (as in above example) in RSA1 (Data warehousing workbench), following which we create an Info cube.
Fig.1.2 Its to be noted that Info cube we have considered for demo has a template as SAP Demo cube. (SAP Purchase Cube: 0D_PU_C01). This cube we created abstracts only skeleton of original cube.
Choose Create Application Component Fig.1.3 Now, we go to Data sources, wherein here we create an application component. Before that care must be taken to change the Source system type (say, BI, File and Web Service etc)
Fig.1.4 Further to it we create a Data source. Right click the application component area & create a Transaction Data type data source, which is from a source system called FLAT_FILE.
Fig.1.5 The data source (As in example: ds_gods) has the above settings as extraction parameters. Here, we are loading the file from Application Server (Viz. AL11), so we have chosen the adapter as Load Text Type File from Application Server. Following this here this being a fixed length f ormat & usage of delta process we choose the respective options as stated in above figure. Step 2: Accessing Data from AL11
Fig.2.1 After choosing to load data from Application Server folder, well be prompted to choose data from 2 options as in above figure. We now choose AL11 files & proceed to choose DIR_HOME 0D_PU_C01_TD_2003_2004.csv, which is a test data in the AL11.
Fig.2.2 The AL11 Application server files would look something as this. Herein we need to proceed to Copy name option to choose particular test data file (0D_PU_C01_TD_2003_2004.csv)
Fig.2.3 Click on Load Example Data in the Proposal tab of data source (as in example: ds_gods) & start we can see as in right side list of all fields, its description, data type & length.
Trouble Shooting: Its to be noted that here not all fields are copied. If you scroll down, youd know why.
Fig.2.4 Here we need to fill up these values in the template as in the field names in the particular data source. We need to update the information here & activate. Following this we see a preview as below.
Fig.2.5 Read preview data option is clicked & data is viewed as below in Preview tab of the data source.
Fig.2.7 We must not start this now, thats what we intend to do using process chains. Step 3: Creation of Transformation
Fig.3.1 Create a transformation with the target info providers (Cube: TEST_B2) & data source names.
Fig.3.2 Once done, the next step is to create a Data Transfer process, by right clicking the cube & creating a DTP as shown in above figure. As above i.e. for transformation, we have the source as Data source (DS_GODS) & target DTP as Info Cube (TEST_B2) (Pl. refer figure 3.1 reg. transformation).
Fig.3.3 As of now the pipeline has been created, and now for loading data by Process Chain Step 4 - Process Chain Planning
Fig.4.1 Start Transaction code RSPC. Go to planning view & process list. Click on Create & enter the name of the process variant & long description for the same. Now once done, click on command button Change Selections
Fig.4.2 in start time panel there are a list of options like Immediate / Date-Time / after Job / after Event etc. We need to choose the appropriate scheduling the process chain requires. For demo purpose, weve chosen Immediate as the option & click on Save
Fig.4.3 The top row displays the name of variant, details like last changed by etc. There are 2 options like 1. Direct Scheduling: The job will be scheduled when the process chain is activated 2. Start using Meta Chain or API: No triggers are scheduled. The start of the process chain will be done via FM, RSPC_API_CHAIN_START or with another process chains. In our example, we are processing single process chain, so weve chosen Direct Scheduling
Fig.4.4 Enter name of start process for the particular trigger; each process type is very generic. Example: Load data into an Info cube. Here, each process needs a variant, which tells us the process exactly which objects to work on.
Fig.4.5 A special type of process is the Start process. Every chain must have one. Again, a Start process without a variant is worthless. The variant provides information about when to start.
Fig.4.6 Choose the Search help here & please note to copy the IP name from RSA1: ZPAK_D3GY6M7MA9YVYBLKYRG0HX3N2
Fig.4.7 - Once you drag and drop Execute info package we get a popup. We need to key in the Info package name. To do this click on F4 and chose corresponding Info package and click on 'Enter'
Fig.4.8 - Click on the icon process types as shown in the figure, when a list of options will be displayed. In our demo example we are loading data to an Info provider.
Fig.4.9 - To process this we need to have Info Package, DTPs for the corresponding DSO. Open tree Load Process and Post Processing, We need to drag and drop Execute Info Package
Fig.4.10 - The process chain log view gives an whole picture of status of all BI tasks, where one can monitor special BI processes (change runs or reporting agent) & common activities (Info packages, DTP, drops/create index )
Fig.4.11 - When we right click a process icon, we get a list of all available log functions as in above figure. Using the Legend icon you can find the list of meanings for the colors. You can go directly to specific chain by choosing RSPC Log View, but there are better options for overall system monitoring. Trouble Shooting Process Chains
Fig.4.12 -- Theres some simple error which well debug now. The possible error as of now is shown above, the value PERI6 is listed for 0CALMONTH, which needs to be changed from External to Internal parameter.
Fig.4.13 Once you drag & drop the Info Package, the corresponding DTPs and the corresponding Active Data table are automatically called. Further, save & execute the process. Once the process is completed, we can see the whole chain converted to Green, which indicates the process is successfully completed. On selecting Administer Data Target, will lead you to Info Provider Administration.
Fig.4.14 Info provider request IDs now display green, which means data has been successfully loaded.
Fig.4.15 Fig. displays data present in the info cube, a successful completion of our process chain. Further as specified on SDN, the following are list of checks & legends in RSPC. Checks for consistency: Double start variants, Missing index deletion, incorrect references in variants Meaning of colors: Green Error free process; Yellow Process with warnings; Red Errors
Related Content
Using Process Chains in SAP Business Information Warehouse Event Chains replaced by Process chains Enhanced decision process type for BW process chains SAP Central Process Scheduling - Increasing value of SAP Business Intelligence For more information, visit the Business Intelligence homepage.