In this section, we will learn about the SAP BODS architecture. The illustration displays the architecture of BODS system with performing area.
The source layer contains different data sources like SAP presentations and non-SAP RDBMS system and data integration takes place in performing area.
SAP Business Objects Data Services contains different modules like Data Service Designer, Data Services Management Console, Repository Manager, Data Services Server Manager, Work bench, etc. The target system can be a DW system like SAP HANA, SAP BW or a non-SAP Data warehouse system.
The following screenshot illustrations the different constituents of SAP BODS.
You can also divide BODS architecture in the following layers −
The following illustration displays the BODS architecture.
Act Technology Inc. established SAP Business Objects Data Services and later Business Objects Company learned it. Act Technology Inc. is a US founded company and was responsible for development of first-data integration platform. The two ETL software products developed by Act Inc. was the Data Integration (DI) tool and the Data Management or Data Quality (DQ) tool.
Business Objects, a French company learned Act Technology Inc. in 2002 and later, both the produces were renamed as Business Objects Data Integration (BODI) tool and Business Objects Data Quality (BODQ) tool.
SAP developed Business Objects in 2007 and both the products were renamed as SAP BODI and SAP BODQ. In 2008, SAP integrated both the yields into single software product named as SAP Business Objects Data Services (BODS).
SAP BODS offers data integration and data management clarification and in the earlier version of BODS, the text data-processing solution was included.
All the objects that are used in BO Data Services Designer are called Objects. All the objects like projects, jobs, and metadata and system functions are kept in the local object collection. All the objects are hierarchical in landscape.
The objects mainly hold the following −
There are two types of objects in the system − Reusable objects and Single Use objects. The type of object controls how that object is used and saved.
Most of the objects that are kept in the repository can be reused. When a reusable object is defined and saved in the local repository, you can reuse the object by generating Calls to the explanation. Each reusable object has only one explanation and all the calls to that object refer to that classification. Currently, if description of an object is changed at one place you are changing the object explanation at all the places where that object performs.
An object library is used to hold object explanation and when an object is dragged and dropped from library, a new reference to an existing object is created.
All the objects that are defined specifically to a job or data flow are known as single use objects. For instance, specific transformation used in any data load.
All the objects are hierarchical in landscape. The following illustration displays the object hierarchy in SAP BODS system –
Created on the architecture illustrated below, we have many tools defined in SAP Business Objects Data Services. Each tool has its own function as per system landscape.
At the top, you have Information Platform Services connected for users and rights security management. A BOD depends on Central Management console (CMC) for user access and security article. This is applicable to the 4.x version. In the previous version, it was done in Management Support.
SAP BODS Related Interview Questions
|SAP BO Interview Questions||SAP ABAP Interview Questions|
|SAP BW Interview Questions||Data Stage Interview Questions|
|SAP BPC Interview Questions||SAP BODS Interview Questions|
|SAP BDC Interview Questions||SAP BW on HANA Interview Questions|
|Sap Bapi Interview Questions||Sap Business One Interview Questions|
Sap Bods Tutorial
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.