What is SAP BODS:-

Data Service is the primary tool to extract, transform & load data from one or
more source systems into one or more target systems.
Data Services can access data from a wide variety of applications and file sources and can
consume almost every type of datastructured, semi-structured, and unstructuredfrom
those sources.

Types of Integration:There are different ways of integrating business applications.

Service Integration

Message Integration

Business Process Integration

Data Integration

Different approaches to handle the integration types.

Service Integration.

Establishment of a service oriented architecture.

Message Integration & Business Process Integration.

Enterprise Application Integration or B2B integration.

Data Integration.

Extract, Transform & Load utilities.

Service oriented Architecture

All functionality is published as a services in platform independent manner.

Services can be consumed by other applications.

Enterprise Application Integration.

Process of linking different applications within a single organization together in order

to simplify and automate business processes to the greatest extent possible.

Extract Transform & Load (ETL)

Extracting data from different sources.

Transforming it to fit the operational & analytical needs.

Loading it into end targets.

Out of these SOA & EAI can be managed by SAP PI & ETL can be managed by BODS.
There is overlap between SAP PI & BODS about the functionalities they offer.
Deciding factors about the choice between the PI & BODS are

Technical & functional capabilities of both

Organizational environment

The type of integration to be done.

Technical environment(hardware size)

Other factors.

Process Integration v/s Data Services:

We will discuss the capabilities in detail
Data Volume:

If large no of messages are per second with less or medium amt of data need to be
delivered then SAP PI is the very good choice.

If the data volumes are very large & frequency of data to be transferred is less than
SAP BODS is the choice.
Example:Suppose the requirement is that the data is sent to a business partner twice a
month & the file size is 4 GB. Then in such a case sending the data
to BODS is good
option.
Processing Mode:-

Scheduled / Batch Based:Data services processing is typically scheduled. You can schedule the Batch jobs in
BODS or specifically run it. Pi jobs can also be scheduled but
generally they are
not scheduled.

Event / Trigger Based:BODS has the capability to receive events via web services or other means &
process these events.
PI is typically triggered by incoming data.

Real Time(synchronous/ asynchronous):Data latency for DS is larger( minutes rather than seconds).
PI offers mechanisms for real-time synchronous transactions.
Example:-

Data has to be moved from the database to BW system once in a week or once in a
day then BODS is the goods option.

File has to be picked from the sender system after every 10minutes then SAP PI is the
good option.
Data Processing Level:-

PI is used to exchange messages between systems while data service is used to

exchange data set.
Data Transformation:-

Both data services & PI do well in applying basic transformations. Basic functions
required for transformations are available on both the platforms. eg. String functions,
mathematical functions etc are found in both.

Data service has much fore functionalities related to data cleansing activity. eg.
Validate, Table Comparison, Map_operations etc.
Business Process Management:-

Pi provides full workflow capabilities. System centric & Human centric workflows are
possible in PI.

Data service focus on system centric workflows only. In DS workflows are simple
deals with process sequencing & error handling.
Reliable Messaging:-

Data service doesnt support guaranteed delivery.

PI supports guaranteed delivery with 2 options, Exactly One(EO) &Exactly Once In
Order(EOIO).
Asynchronous messaging (EO & EOIO) is based on WS standard.
Connectivity:-

Both PI & BODS are capable of handling connectivity between SAP & non-SAP
systems.
A.
File Handling, SAP Applications(RFC, IDOCs, Proxy), Legacy protocols(JMS), Databases.

Database handling is the core functionality of BODS. It is able to extract tables in the
complex manner.

For EDI connectivity according industry standards PI is most suitable as EDI

adapters are available in SAP PI.
SOA:-

PI is positioned as a SOA middleware. It is the basis of SOA. You can create a web
service from the interfaces used in PI.

In PI you can publish your web services in service registry which is based on UDDI
3.0, where you can search, manage & consume the web services.

BODS acts as service provider or consumer, but doesnt offer further SOA
functionality.
TCO:-

The cost of using SAP PI as an integration tool is based on the overall processed
message volume expressed in GB/month. SAP PI is free to use for integration between SAP
to SAP systems.

In BODS with one application we can cover multiple data management processes so
it lowers TCO.
Example:-

So for SAP to SAP integration SAP PI is most suitable.

And for data migration, cleansing & validation of data from source to target system
BODS is most suitable.
Type of Integration:-

For Service, Enterprise Application Integration & Business-Business(B2B) integration

SAP PI is the best choice.
For Data integration SAP BODS is the best choice.
Example:-

If user need to know the details about the number of materials created in an working
unit then creating the web service for this purpose & consuming it across anywhere is the
right choice & for this SAP Pi is the best option.

Data service is the best option for data integration with SAP Netweaver BW, SAP
HANA & entire Business Objects BI Platform. Data Services is the preferred tool for loading
non-SAP data into SAP HANA. In fact, the data integration capabilities of Data Services are

included with SAP HANA. Additionally, SAP is making major improvements for a seamless
user interface between Data Services and SAP HANA.
Integration Content:SAP delivers prepackaged integration content, which is created based on the SAP
SOA design methodology. This business content includes global data types, service
interfaces, and mapping definitions. IT professionals can use this predelivered content from
SAP to jump-start their SOA implementations in SAP PI.
Third party adapters are also available in SAP PI to meet particular industry
standards.eg. EDI adapters by Seeburger
Development Interface:In BODS all generation & data quality processes are developed & managed in a single
interface i.e. Data Service Designer.
In PI creation of Design & Configuration objects are separated in Integration
Repository & Integration Directory respectively.
Summary:As we have seen the overlap between SAP PI & BODS we came to know that both
are important tools & depending upon the business requirement, cost, available resources,
connectivity options & data volume one would choose SAP PI or SAP BODS for their
integration requirement.

Sending IDOC from Business Objects Data Services

(BODS) to SAPinShare1
Document Purpose
This document provides steps required to load data in SAP using one of the SAP interfaces.
This document will be used at the time of proof of concept to demonstrate the ability of
Business Objects Data Services (BODS) to invoke IDOC interface to load data in SAP.
The main objectives are:

Loading data in SAP using IDOC

Demonstrate how BODS can be used to load data using IDOC

Display required configurations step-by-step & invocation

Demonstrate actual sample load using BODS job

Overview:

1.
2.
3.

This document provides systematic approach for the data load in three sections:
Configuration Required at SAP Side:
Configuration Required at BODS Side:
Demonstration Sample Load using BODS Job:
Each of above sections provide information as in how to configure the specific parameters
required to get both SAP & BODS ready to communicate with each other. Screen shots
provided for better understanding of the parameters & their configuration.
Configuration Required On SAP (ECC 6.0) Side
Following is the required configuration on SAP side.
1.Display IMG [ /nsale ]
Connect to SAP System using SAP GUI

Use Transaction Code (TCODE) /nsale to Display IMG

1: Display IMG screen

Expand Logical Systems tree & click on the Clock icon in front of Define Logical
System
2.

Defining Logical System

2: Defining Logical System screen

Click on the New Entry Button
For SAP Inbound IDOC One Logical system (FRMDICL100) is required
Create a Logical system as shown below

3. Overview of added entries

Click on the SAVE Button to save both the Logical System.
Verify that the LS FRMDICL100 is present in the SAP system

4. Overview of Logical Systems

3.

Create Partner Profile [ /nwe20 ]

Use TCODE /nwe20 to configure partner profile.

5. Partner Profile screen

Click on Create button to create new partner profile
Create partner profile as shown below
Note :
1.
Provide partner no. FRMDICL100 i.e same as BODS Logical System.
2.
Agent 50010120 EDI Department is necessary for communication with non-SAP
systems like BODS. Without this agent IDOC communication will not be successful.

6. Partner Profile deatil screen

Click on the Save button to save the partner profile
After saving; the Create Inbound parameter will be activated in Inbound paramtrs

7. Partner Profile create Inbound paramtrs screen

Click on Create Inbound parameter in Inbound paramtrs section

8. Partner Profile Inbound parameters screen

Note :
In Inbound options tab, select appropriate process code relevant to message type.
(In this case; for MATMAS message type, process code is MATM)

In "Post processing : permitted agent" tab provide details as shown above.

Save "Partner profile: Inbound parameters" using Save button
After saving verify Partner Profile & Inbound Parameter added.

Configuration Required On BODS Side:

Following is the required configuration on BODS side
1.

Create SAP Datastores

Create SAP Datastore by providing required SAP Application Server Information &
creadentials

11. SAP Datastore in BODS

Right click on IDOCs and select Import By Name

12. IDOC list under SAP datastore in BODS

13. Import IDOC screen

Provide Type and Name as shown above and click on Import to import IDOC in data
store
2.

Generating input XML schema

To create the input XML structure with the correct datatypes quickly drop the IDOC as
message source onto the dataflow, go into this object and right click the schema. There,
you can ask the Designer to generate the entire structure as XML schema, thus you get
all columns, schemas including the datatypes.

14. MATMAS01 IDOC screen

MATMAS01_OUT this XML file source is created using generated schema inFile Format
tab.

15. XML Schema screen

3. Build Batch Job
Build a Batch Job with a DataFlow inside
Data Flow is as Follows

16: Batch Job screen

Double click on source XML File Source configure it as shown below.
Note: For demonstration purpose we have used XML file that was output of the Real-Time
Job designed in article"Receiving IDOC In BODS from SAP".

Important : Make sure that in XML file Sending Partner setting i.e. <SNDPRN> should
be same as BODS logical system name. (FRMIDCL100) as shown below.

18: IDOC out XML file strucutre screen

Un-nest by right clicking on MATMAS01_OUT schema in "Query" as shown below

19: IDOC structre screen

Drag the IDOC MATMAS01 from SAP DataStore as shown

20. IDOC in SAP Datastore

Note: Make sure to select option "Make IDOC Message Target"
Configure IDOC Message Target

21. BODS side IDOC configuration

BODS BASICS Objects Information:

Objective

Pre Requisites

Inclusions and Exclusions

Introduction to BODS

Common terms and terminologies

BODS Architecture

Getting started
o

Repository Creation

Job Server Configuration

Registering with CMC

Starting up BODS Launching the Designer

Creating, Executing and Debugging BODS Jobs

o

Creating our first job

Executing jobs

Debugging jobs

ETL using files

Exporting Importing ATLS

Data Profiling

Dos and Donts and Programmer tips

Objective

After reading this article, a normal person with elementary programming knowledge would
be able to work on SAP Business Objects Data Services (which will be referred to as tool,
BODS, Data services or BODI hereafter), and would be in a position to understand its basics
and working. The person reading this book would be able to get acquainted to BODS in less
than a weeks time .This book will also be an entry for professionals who are eager to get on
to the Business Objects Data services world and a confidence booster to attend interviews .
Pre-requisites
Hardware
PC with minimum 8 GB RAM and Processor 3i and above
Software
SAP Business Objects Data Services 4.0 preinstalled. Any RDMS preinstalled (SQL Express
2008 preferred as that will be used for examples and illustration throughout the book).The
RDMS would have to be installed prior to BODS.
Programmer/Consultant/Resource
Basic programming knowledge and basic SQL knowledge. In other words anyone who
understands the terms such as, If then else, Loops, Database, Tables, Query, DML and
DDL statements should be able to follow this tutorial without any trouble. Also someone who
recognizes or is aware of business terms like Data, Transformation, ETL, Data
warehousing, Data Migration, ERP (some these terms are explained briefly in the
following chapters) and familiarity with names of popular databases and softwares and ERPs
like SAP, Oracle, SQL Server.
Exclusions and Inclusions

Not all the functions, transforms, objects, methods or buttons or menus are not
covered in the book.

The latest release Data services 4.0 would be used for illustrations and examples.

Installation of the tool is not covered in this book.

Other tools that are installed with the BODS suite including Information steward,
Management console are not covered in the scope of this book.

Any logic building or solution design is not an objective of this book.

Introduction

What is SAP Business Objects Data Services?

This is a software tool designed by Business Object ( a company that got acquired by SAP in
2007). Some of the basic purpose of this tool is to perform jobs like

ETL (Extraction Transformation and Loading) Pulling out data from any
system/database/tables ,applying changes to modify the data or applying
programming logic to enhance the extracted data ,and loading data into any other
system/database or tables. E.g.: ETL of data from SQL server database to Oracle.

Data Ware Housing A database specifically designed and developed in a

particular format to enable easy data analysis or reporting. This could be developed
using data from various databases or any other data sources.

Data Migration - Moving of data from one place to another. This is a subset of ETL
where data is relocated from one software system or database to another .This also
involves modification and alteration of data.

Business Intelligence A concept which combines the data warehousing system

and reporting. This is applied to analyze data of organization to effectively perform
functions like Business performance improvement.

Why SAP Business Objects Data Services?

There are many other software tools in the market which are capable of doing the same
functions or activities as mentioned above or even more. They are the direct competitors for
Business Objects. They are Informatica, Datastage, Cognos, and SSIS etc. The above
mentioned activities can also be performed using programming tools like .Net or even Java
and also directly within database end like SQL Server or Oracle.
The tool BODS provides a very easy and efficient interface to perform these specialist tasks
which involve data manipulation. The objects and functions within BODS are specifically
designed to perform manipulations and transformation of huge and complex volume of data
very efficiently. There are system provided objects and functions which can be dragged and
dropped easily and jobs can be created. And, being a SAP tool has very god compatibility
with SAP applications compared to any other similar tool.
Common terms and terminologies
Designer
Designer is the graphical user interface that lets you create, test, execute and debug BODS
Job. This is the space where the data transformations take place.
Repository
Repository is like a database that stores the objects in a designer. The job metadata, the
transformation rules and the source and target metadata also. There are primarily three
types of repositories Local, Central and Profiler. The designer cannot even be opened for any

task without having a local repository. In other words local repository is a mandatory
repository for BODS functioning. At this point we are not bothered about the other two
repositories.
Engine
The BODS Engine executes the jobs created using the Designer. When the BODS application
is started, there are enough Engines launched to effectively accomplish defined tasks.
Job Server
The Job Server is an application that launches the Data Services processing engine and
serves as an interface to the engine and other components in the Data Services suite.
Access Server
The Access Server passes messages between web applications and the Data Services Job
Server and engines.
Datastore
A datastore provides a connection to a data source such as a database. This is a linking
interface between the actual backend database and Data services. Through the datastore
connection, Data Services is able to import descriptions of the data source such as its
metadata.
CMC (Central Management Console)
This is a web based administration tool for BODS which is used for some basic functions such
as repository registration, User Management etc.

These terms should be at the finger tips of a BODS programmer as these would be used very
often while working on BODS.

BODS Architecture:

The

illustration

below

(Figure

1.1)

shows

the

basic

architecture

of

BODS.

Figure 1.1
Above diagram explains the relation among Designer, central and local repository and web
application. We will gradually understand these later. In the next page we will start creating
our first BODS application.Click

About BODS Migration:

Purpose:
The purpose of this document is to up-grade SAP Business Objects Data Services from
11.7/3.X/4.X to SAP Data Services 4.2
Overview:
Environment Details:
Operating system: Windows Server 2008 64 Bit
Database: Microsoft SQL Server 2008 R2
Web Application: Tomcat
SAP Business Objects Tools: SAP Business Objects Information Platform Services 4.1 SP2;
SAP Data Services 4.1 SP2
Migration Tools: Data Services Repository Manager
Repository version: BODI 11.7 or BODS 3.X or BODS 4.X
Installation & Configuration steps to upgrade SAP BODS 3.X/4.X to SAP BODS 4.2:

Pre Installation Check List:

o
o

Backup of repositories, configuration files & Data Cleanse files:

Backup of Local, Profile & Central Repository
Backup of Following Configuration Files:
admin.xml
sapconnections.xml
as.xml
dsconfig.txt
Backup of Data Cleanse Files
Create a Check list of Number of Batch Jobs/Real Time Jobs, Number of Access Server,
Number of Job Server & Configuration Path (Datastore) of Source & Target Systems
Create a Check list of Jobs Scheduling in SAP Business Objects Data Services
Management Console
Create a Check list of Groups & Users Available in SAP Business Objects Data Services
Management Console

Post Installation Check List:

Installation of EIM(Enterprise Information Management) or IPS(Information Platform

Services) Package in New Landscape
Installation of SAP BODS 4.2
Installation & Configuration of Address Cleansing Package 4.2
Best Practices says use the same Data base that you have use in SAP BODS 4.1 make
a cloned copy and Use in SAP BODS 4.2 environment
Up-gradation of Local /Central repository Using Data Services Repository Manager
Configuration of Repository in EIM or IPS (Package Name) Central management
Console.
Configuration of SAP RFC in Data Services Management Console 4.2
Configuration of Adapters in Data Services Management Console 4.2
Apply Rights & Security according to your requirement in BIM or IPS (Package Name)
Central management Console
Now Login in SAP BODS Designer 4.2 and configure Jobs (Real Time/Batch Jobs)
Configuration of Datastore (SAPR3,SAP BW, RDBMS), Substitution Parameters, Job
Server, Access Server, Format Data Type (Flat Files, CSV)
Now validate the Jobs at Top Level and if error comes fix those errors
Now Execute the Jobs using Scheduler or other BI Tools

SAP Business Objects Information Platform Services 4.1 SP2 Installation &
Configuration Documents:
Prerequisite:
SAP BusinessObjects Business Intelligence (BI) 4.1 SP2 or its higher compatible patches*
OR
SAP BusinessObjects Information Platform Services (IPS) 4.1 SP2 or its higher compatible
patches*
Up gradation & Configuration Documents:
When the prerequisite system check completes successfully, click Next

On the "SAP BusinessObjects Information platform services 4.1 SP2 setup" page, click Next.

Accept the License Agreement, and click Next.

Type a password for the CMS Administrator account, and click Next

To start the installation, click Next.

Installation is in progress

Finish

Up gradation & Configuration Documents of Data Services:

When the prerequisite system check completes successfully, click Next

On the "SAP BusinessObjects Data Services 4.2 SP1 setup" page, click Next.

Accept the License Agreement, and click Next.

Click Next to accept the default path to the folder where the program will be installed.

Click Next to accept the default language (English).

Type a password for the CMS Administrator account, and click Next.

Click Yes to restart the BOIPS services

To start the installation, click Next.

Installation is in progress

Finish

SAP Business Objects Data Services 4.0 Configuration Documents:

Before upgrade of local repository below are the error in SAP Business Objects Data Services
Designer

So before login upgrade the repository using SAP Business Objects Repository
manager.Below are the steps for upgrade of local repository details:
Below are the steps for upgrade of local repository & upgrade of secure central repository
Upgrade of Local Repository:

Upgrade of Secure Central Repository:

After Installation & Up-gradation of SAP business Objects BOE/IPS Server, SAP Business
Objects Data Services 4.2SP1 below are the status that i upgraded in VM Ware

Login to Central Management Console -> Go to Data Services

Then Click on Data Services and update the repository details of SAP Business Objects Data
Services repository.

Now try to login in SAP Business Objects Data Services Designer

Click on Logon

Click on ok

Now login in SAP Business Objects Data Services management console

Click on "Administrator" tab

New features are added in SAP Business Objects Data Services management console 4.2":

Object Promotion:

Import Configuration
Export Configuration

Export Configuration using two way:

FTP
Shared Directory

Substitution Parameter : Now we can change the "Substitution Parameter" settings

through SAP Business Objects Data Services Mananegment console also.

New Features added in Adapter like "Hive Adapter & VCF Adapter"

Changes in "Query and Validation" transform in SAP Business Objects Data Services
Designer 4.2

Changes in "Architecture" of SAP Business Objects Data Services please refer below
upgrade guide for more details.

New Features added like "REST web services": Representational State Transfer (REST or
RESTful) web service is a design pattern for the World Wide Web. Data Services now allows
you to call the REST server and then browse through and use the data the server returns

Relevant Systems

These enhancements were successfully implemented in the following systems:

SAP Business Objects Information Platform Services 4.1 SP2/SAP Business Objects
Enterprise Information Management 4.1 SP2
SAP Business Objects Data Services 4.1 SP2

This document is relevant for:

SAP Business Objects Data Services Administrator

This blog does not cover:

SAP Business Objects Data Quality Management Up-Gradation

Reference Material:

Upgrade Guide:

https://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_upgrade_en.pdf

Installation Guide Windows:

https://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_install_win_en.pdf

Installation Guide UNIX:

https://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_install_unix_en.pdf

SAP Data Services 4.2:

https://help.sap.com/bods

ABOUT CDC:

About

Articles Related

CDC mechanisms

Type of Integration

Which CDC strategy to choose?

Documentation / Reference

Integration - Change Data Capture (Incremental Load, ...)

About
During the data warehouse's initial historic load, capturing source data content changes is not
important since you are loading all data.
However, most data warehouse tables are so large that they cannot be refreshed during every
load cycle. You must have a capability to transfer only the relevant changes to the source data
since the last update. Isolating the latest source data is called change data capture (CDC). The
idea behind change data capture is simple enough: just transfer the data that has been changed
since the last load.

It's why generally the use of a publish-subscribe model is made.

Reference LINKS for CDC

ORACLE - Streams / Change Data Capture

Data Integration - ETL Moving to Pervasive Integration

Data Integration - Pattern

ODI - Change Data Capture

Data Warehousing - Data Loading (Fast Refresh)

DataWarehouse - Fundamental / Operational Data Store

Data Warehousing - Subsytem

OBIA - Creating Custom Indexes in Oracle EBS Source Databases for Incremental Load
Performance

OWB - Change Data Capture

CDC mechanisms

Database Log Miner (Log-based Change Data Capture or Database Log Readers)

Database Triggers. This DBMS feature invokes a prewritten routine each time a specific
set of conditions are met, such as the addition or updating of a record in the database. In
concept, the code that the trigger launches can be written to write a record of the transaction
to a database table and the ETL tool can then poll those tables on a periodic basis. In
practice, this approach is far from foolproof. For example triggers can regularly be
deleted/disabled then re-added/re-enabled in the normal course of a business operation.
Triggers also place a relatively high overhead burden on the source database server

Message Queues. An obvious disadvantage is that they are not a completely reliable
source of change information since they only know about data changes that are sent to them
by the applications and not updates in the database.

Date and time stamps many ERP applications and other data sources maintain data
fields within each record that indicate when it was last changed. The fatal flaw in this
approach is that it relies on the programs that change data to unfailingly update this field. In
addition, this approach can lose track of deletions since the entire record including the time
stamps are gone.

Table comparison with a hash function: OWB - How to implement a type 2 slowly

changing dimension with a hash function ?

Type of Integration

data-based,

event-based

or services-based integration.

Which CDC strategy to choose?

The CDC mechanism selected must be absolutely fool proof all changed data must be
identified. Finding the most comprehensive strategy can be elusive; many times updates to
source system tables can occur outside the application itself. A mistake here will result in
inconsistent results that can't be easily explained; often it takes significant data reconciliation to
identify the culprit. Problems can be a very costly in terms of rework not to mention
embarrassing. In short, capturing data changes is far from a trivial task, and you must clearly
understand the source data systems. This knowledge will help the ETL team evaluate data
sources, identify change data capture problems and determine the most appropriate strategy.

Documentation / Reference
Kimball University: Six Key Decisions for ETL Architectures

Architecture of SAP BusinessObjects Data

Services (BODS):
SAP BusinessObjects Data Services is a data warehousing product that
delivers a single enterprise-class software solution for data integration (ETL),
data management (data quality) and text data processing.

Data Integrationis the Extraction, Transformation and Loading (ETL)

technologyof enterprise data between heterogeneous sources and
targets.

Sources and Targets can be SAP Applications (ERP, CRM etc.), SAP BW, SAP
HANA, Any Relational Database (MS SQL Server, Oracle etc.), Any File (Excel
Workbook, Flat file, XML, HDFS etc.), unstructured text, Web services etc.

ETL technology of SAP BODS can be done in both Batch mode and Real time
mode data integration.

Data Managementor Data Qualityprocess Cleanses, Enhances,

Matches and Consolidates the enterprise data to get an accurate or
quality form of data.

Text Data Processing analyzes and extracts specific information

(entities or facts) from large volumes of unstructured text like emails,
paragraphs etc,

Architecture:
The following figure outlines the architecture of standard
components of SAP BusinessObjects Data Services.

Note: On top of SAP BODS, a

full SAP BusinessObjects BI Platform or SAP BusinessObjects Information

Platform Services (IPS) should be installed for User and Rights security
management from 4.x versions. Data Services relies on CMC (Central
Management Console) for Authentication and Security features. In earlier
versions it was done is Management console of SAP BODS.
BODS Designer:
SAP BusinessObjects Data Services Designer is a developer or designer tool.
It is an easy-to-use graphical user interface wheredevelopers can design
objects that consist of data mappings, transformations, and control logic.
Repository
Repository is the space in a database server which stores the
metadata of the objects used in SAP BusinessObjects Data Services. Each
repositorymust be registered in the Central Management Console (CMC) and
associated with one or more Job Servers which run the jobs you create.
There are three types of repositories used with SAP BODS:

Local repository:

A local repository stores the metadata of all the objects (like projects, jobs,
work flows, and data flows) and source/target metadata defined by
developers in SAP BODS Desinger.

Central repository:

A central repository is used for multi-user development and version

management of objects. Developers can check objects in and out of their
local repositories to a shared object library provided by central repository.
The central repository preserves all versions of an applications objects, so
you can revert to a previous version if needed.

Profiler repository:

A profiler repository is used to store all the metadata of profiling tasks

performed in SAP BODS designer.

Where, CMS repository is used to store the metadata of all the tasks done in
CMC of SAP BO BI platform or IPS.
Information Steward Repository is used to store the metadata of profiling
tasks and objects defined in SAP Information Steward.
Job Server
The SAP BusinessObjects Data Services Job Server retrieves the job
information from its respected repository and starts the data engine to
process the job.
The Job Server can move data in either batch or real-time mode and uses
distributed query optimization, multi-threading, in-memory caching, inmemory data transformations, and parallel processing to deliver high data
throughput and scalability.
Access Server
The SAP BusinessObjects Data Services Access Server is a real-time, requestreply message broker that collects message requests, routes them to a realtime service, and delivers a message reply within a user-specified time
frame.
Management Console
SAP BusinessObjects Data Services Management Console is the Web-based
application with the following properties.
Administration, Impact and Lineage Analysis, Operational Dashboard, Auto
Documentation, Data Validation and Data Quality Reports.

ABOUT BODS transformations:

Follow below links for about SCD type transformations:

http://scn.sap.com/community/data-services/blog/2013/07/05/scdtype-implementation-in-bods
http://www.dwbi.org/etl/sap-data-services/104-how-to-implementscd-type-2-using-history-preserve-transform-in-data-services
http://wiki.scn.sap.com/wiki/display/EIM/Loading+a+table+with+sur
rogate+key

Follow below link about Query transformation:

http://sapsimplified.com/sap-bods/query-transformation-in-sapbods/

About Merge transformation:

http://scn.sap.com/community/data-services/blog/2013/05/07/howto-use-merge-transform
https://www.youtube.com/watch?v=1rQRgJXdpXQ
http://dwbi.org/etl/sap-data-services/93-sap-data-services-mergetransform
ALL BODS transforms information available follow below link:
http://dwbi.org/etl/sap-data-services/83-sap-bods-transforms

Advanced transformations like DATA CLEASING AND ADRESS

CLEASING:

https://www.youtube.com/watch?v=EhM1r2VLryA
http://wiki.scn.sap.com/wiki/display/EIM/Data+Cleanse+Transform
http://wiki.scn.sap.com/wiki/display/EIM/Data+Quality

Follow below link regarding TDP (Text Data Processing), Global Address
Cleanse Transform, Data Cleanse transform, Address Reference Data, Geocoder
transform, DQM for SAP:

http://wiki.scn.sap.com/wiki/display/EIM/Data+Services+Product+Tu
torials

Follow Below Link ABOUT INFORMATION STEWARD:

http://wiki.scn.sap.com/wiki/display/EIM/Video+Tutorials

Sap bods sample project examples:

Follow below link :
http://scn.sap.com/docs/DOC-57615