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 source data object


In a couple of previous recipes, you have already become familiar with data sources, importing tables, and using imported tables inside dataflows as source and target objects. In this recipe, we will create the rest of the datastore objects linking all our existing databases to a Data Services repository and will spend more time explaining this process.

How to do it…

In the Understanding the Designer tool recipe in Chapter 2, Configuring the Data Services Environment, we already created our first datastore object, STAGE, for the "Hello World" example.

So, why do you need a datastore object and what is it exactly? Datastore objects are containers representing the connections to specific databases and storing imported database structures that can be used in your Data Services ETL code. In reality, datastore objects do not store the database objects themselves but rather the metadata for the objects belonging to the application system or database that the datastore...