Wait Process Type Offers an Alternative to Third-Party Job Schedulers

  • by Shailesh Unny, Senior Consultant, BearingPoint
  • October 1, 2007
Find out how you can create a wait process type to handle dependencies across process chains. When combined with the standard start process type, the wait process type ensures that only one dependent program runs at a given time, which prevents conflicting processes from running.
Key Concept

A process type determines how events in a process chain run. For example, you could use the standard process type “and” to permit two programs to run at the same time. Other standard process types include “or,” “interrupt,” and “start.”

When designing data models, I often encounter conflicts during a load. For example, I may need to load the same object — such as a DataStore object (formerly operational data store [ODS] object), InfoCube, or master data — from multiple sources. I cannot control the order in which these objects load. Other times, when an attribute change runs, I need to sequence an event-driven transaction data load manually.

To address these situations you could use an independent third-party job scheduler to define and control job streams. However, these tools are not available in all installations. They also might not be cost-effective if the benefits for your company are limited to a select few cases that need special handling.

For these situations, I use what I call a “wait” process type. This is a custom process type that you can implement using ABAP objects. It simplifies the design of data models and the corresponding load process chains. This allows you to develop and deploy process chains that have dependencies between nodes either in the same chain or in multiple chains in the BW system.

You can implement this process type using a custom ABAP object-oriented (OO) class. This functionality applies to any BW version starting with 3.0, including SAP NetWeaver BI 7.0. You can also expand the concept to meet specific business requirements. To implement the wait process type, you need some familiarity with ABAP development. In addition, you need a developer key to create the report and custom class I use in my example.

I’ll explain the concept behind the wait process type and provide three example scenarios in which you could use it. Then, I’ll describe the four-step process to set up the wait process type and show you how to test it.

Shailesh Unny

Shailesh Unny is a technology architect with more than eight years of BI experience, primarily focusing on translating business requirements into effective functional and technical specifications. He has extensive experience in data modeling, design, configuration, and performance tuning of BI systems. He has also helped adapt SAP’s standard offerings to implement several specific customer requirements. Shailesh is currently involved with working on BI-Integrated Planning and SAP BusinessObjects Planning and Consolidation solutions in the SAP NetWeaver BW 7.0 environment.

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.