Best Practices in SAP BusinessObjects Data Services Data Flow and Job Design

  • by Don Loden, Director - Data & Analytics, Protiviti
  • February 4, 2011
Review these best practices in developing a data flow and understand the importance of reusability in SAP BusinessObjects Data Services job design. When constructing a good data flow, it is important to minimize the effort by thinking in terms of reusability up front in the design process. Considering the code as a reusable object is the best way to approach extraction, transformation, and loading and development with SAP BusinessObjects Data Services.
Key Concept
SAP BusinessObjects Data Services is SAP’s data integration and data quality solution. SAP BusinessObjects Data Services composes both batch and real-time jobs to fulfill a wide variety of enterprise information management (EIM) needs. The SAP BusinessObjects Data Services data quality engine is embedded natively in SAP NetWeaver Master Data Management (SAP NetWeaver MDM). SAP has established SAP BusinessObjects Data Services as the go-to extraction, transformation, and loading and data quality solution for SAP applications.

Extraction, transformation, and loading (ETL) is an integral task in every IT organization. ETL is used in a variety of tasks, from porting an operational application from an aging platform to a modern platform, to converting ERP data from one version to another, or loading a BI construct such as a data warehouse or data mart.

SAP BusinessObjects Data Services is a tool for ETL tasks within your organization. Connectors for SAP BusinessObjects Data Services are available for most common database platforms, as well as application-specific adapters that consume operational processing logic. Adapters for SAP BusinessObjects Data Services are available for systems such as SAP, Siebel, and Oracle. The examples I use demonstrate customer and customer_address data merging to form a customer dimension in a data mart. SAP BusinessObjects Data Services is ideal for operations like these, using its graphical transforms to fulfill dimensional needs right out of the box.

I frame my discussion around loading data into a data warehouse and examining best practices in constructing data flows within an SAP BusinessObjects Data Services job. Through examples, I demonstrate the nature of a properly constructed data flow that lends itself toward efficient processing on the SAP BusinessObjects Data Services job server, as well as proper job design and construction. SAP BusinessObjects Data Services is an object-oriented tool, which allows solutions to be delivered faster and cheaper with less code to maintain in the future.

Don Loden

Don Loden is an information management and information governance professional with experience in multiple verticals. He is an SAP-certified application associate on SAP EIM products.  He has more than 15 years of information technology experience in the following areas: ETL architecture, development, and tuning; logical and physical data modeling; and mentoring on data warehouse, data quality, information governance, and ETL concepts. Don speaks globally and mentors on information management, governance, and quality. He authored the book SAP Information Steward: Monitoring Data in Real Time and is the co-author of two books: Implementing SAP HANA, as well as Creating SAP HANA Information Views. Don has also authored numerous articles for publications such as SAPinsider magazine, Tech Target, and Information Management magazine.

See more by this author


Comments

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.