Book Image

SAP Data Services 4.x Cookbook

Book Image

SAP Data Services 4.x Cookbook

Overview of this book

Want to cost effectively deliver trusted information to all of your crucial business functions? SAP Data Services delivers one enterprise-class solution for data integration, data quality, data profiling, and text data processing. It boosts productivity with a single solution for data quality and data integration. SAP Data Services also enables you to move, improve, govern, and unlock big data. This book will lead you through the SAP Data Services environment to efficiently develop ETL processes. To begin with, you’ll learn to install, configure, and prepare the ETL development environment. You will get familiarized with the concepts of developing ETL processes with SAP Data Services. Starting from smallest unit of work- the data flow, the chapters will lead you to the highest organizational unit—the Data Services job, revealing the advanced techniques of ETL design. You will learn to import XML files by creating and implementing real-time jobs. It will then guide you through the ETL development patterns that enable the most effective performance when extracting, transforming, and loading data. You will also find out how to create validation functions and transforms. Finally, the book will show you the benefits of data quality management with the help of another SAP solution—Information Steward.
Table of Contents (19 chapters)
SAP Data Services 4.x Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Creating a workflow object


A workflow object is a reusable object in Data Services. Once created, the same object can be used in different places of your ETL code. For example, you can place the same workflow in different jobs or nest it in other workflow objects by placing them in the workflow workspace.

Note

Note that a workflow object cannot be nested inside a dataflow object. Workflows are used to group dataflow objects and other workflows so that you can control their execution order.

Every workflow object has its own local variable scope and can have a set of input/output parameters so that it can "communicate" with the parent object (in which it is nested) by accepting input parameter values or sending values back through output parameters. A script object placed inside the workflow becomes part of the workflow and shares its variable scope. That is why all workflow local variables can be used within the scripts placed directly into the workflow or passed to the child objects by going...