Conditional Execution: One Process Chain Does the Work of Two

  • by Rajiv Kalra, Independent Consultant
  • March 1, 2008
With a few steps you can simplify process chain maintenance by combining two processes into one process chain. The system determines which process to carry out based on conditional execution. Learn the four steps you need to take to use conditional execution with a process chain.
Key Concept

Conditional execution of a process chain using Business Add- Ins eliminates manual loads when you have data providers that you load periodically (e.g., monthly or quarterly). This allows you to set up one process chain with multiple branches. The system uses a formula that you enter in Formula Builder to determine which path the process chain should follow.

Using Business Add-Ins (BAdIs), user-defined functions, and the Decision Between Multiple Alternatives process type you can set your process chains to execute conditionally. For example, you can set up the process chain to select between alternative paths, stop execution based on certain criteria, or prevent further transactional data loads until master data is fixed.

In most implementations, the system posts monthly snapshots to separate InfoCubes for reporting changes in key figures and key performance indicators (KPIs) as a function of time (time trends). This requires that you create monthly and daily process chains. For example, say you have a process chain that loads data daily into an InfoCube. The business requires that you load a snapshot InfoCube on the last Saturday of every month with records stamped with the system date. Instead of creating two process chains, one for monthly loads and one for daily loads, the same process chain can accomplish the job using conditional execution.

In part 1, I’ll show you the four steps to facilitate conditional process chain execution using a BAdI implementation with a user-defined function in the Formula Builder transformation. This method applies to SAP NetWeaver BI 7.0.

In part 2, I’ll show you another scenario that requires halting additional transactional data loads in process chains if master data is not up to date. In this case, you can set up the process chain to check for the existence of records in the error stack and stop further execution until the master data management (MDM) team fixes the master data. You subsequently execute the error data transfer process (DTP) to load the records from the error stack. Part 2 also applies to SAP NetWeaver BI 7.0.

Rajiv Kalra

Rajiv Kalra is an independent SAP consultant with more than 11 years of SAP experience. With more than five years of BI experience in data modeling, design, configuration, and performance tuning of BI systems, he has helped develop many out-of-the-box solutions to resolve complicated reporting requirements at various client sites. Besides SAP NetWeaver BI, Rajiv has worked on the ERP side for more than seven years and is an SAP-certified ABAP consultant.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.