Data Source:

The Data Source is a set of logically-related fields that are provided to transfer data into BI in a flat structure (the extraction structure), or in multiple flat structures (for hierarchies). There are four types of Data Source: Data Source for transaction data Data Source for master data Data Source for attributes Data Source for texts Data Source for hierarchies

Use
Data Source is used to extract data from a source system and to transfer the data to the BI system. They are also used for direct access to the source data from the BI system. The following image illustrates the role of the DataSource in the BI data flow:

The data can be loaded into the BI system from any source in the DataSource structure using an InfoPackage. We determine the target into which data from the DataSource is to be updated during the transformation.

Restriction
The new DataSource concept cannot be used for transferring data from external systems (metadata and data transfer using staging BAPIs).

Persistent Staging Area:

Purpose
The Persistent Staging Area (PSA) is the inbound storage area for data from the source systems in the SAP Business Information Warehouse. The requested data is saved, unchanged from the source system. Request data is stored in the transfer structure format in transparent, relational database tables in the Business Information Warehouse.

Functions Checking and changing data

Since the requested data is stored unchanged in the PSA, it can have errors if it already had errors in the source system. The PSA offers us the option of checking and changing data before we update it further from the PSA table in the communication structure and in the current data target. As a result corrected data is now available for continued updates. PSA Partition Size (Performance Tuning)

Using partitioning, we can separate the dataset of a PSA table into several smaller, physically independent, and redundancy-free units. This separation can mean improved performance when we update data from the PSA. In transaction RSCUSTV6 the size of each PSA partition can be defined. This size defines the number of records that must be exceeded to create a new PSA partition.

Deleting Requests from the PSA

If we do not regularly delete data from the PSA, the PSA tables can grow to an unlimited size. Large tables increase the costs of data retention, the downtime for maintenance tasks and the performance of the loading process. As a Result, Delete requests from the PSA, they remain physically in a partitioned PSA table for the time being. The requests are first deleted logically (from table RSTSODSREQUEST) and are given a deletion flag in PSA partitioning administration (table RSTSODSPART).We can no longer access these requests.

What is the use of PSA table?

You need PSA for following reasons. 1. To edit bad data or bad characters: We can edit them in PSA and then load them further into the data targets. This is not possible without PSA.

2. As a back-up for repeat loads: We can do repeat data loads from PSA without the need to load all the way from source system again. This is particularly useful for the datasources that doesn't support repeat delta. If there are any errors during transformation you will lose data if you do not have PSA in such cases. 3. Troubleshooting and testing Purpose: We can test your transformation logic by comparing the data between PSA and data targets.

InfoObject:
Definition
Business evaluation objects are known in BI as InfoObjects. They are divide into Characteristics (for example, customers), Key figures (for example, revenue), Units (for example, currency, amount unit), Time characteristics (for example, fiscal year) and Technical characteristics (for example, request number).

Use
InfoObjects are the smallest units of BI. Used to map the information in a structured form. This is required for constructing InfoProviders. InfoObjects with attributes or texts can themselves also be InfoProviders (When we declared it as Characteristics InfoProvider).

Naming Convention
SAP Delivered Info object starts with 0<Info object name> Object created by us should not start with 0 or any number and special character. Length of the Info Object should be between 3 and 9 character length.

Characteristics: Characteristics hold business information which is used to analyze key figures or these are business reference objects. Examples: Customer (0CUSTOMER) Material (0MATERIAL) Cost Center (0COSTCENTER) Key Figures: Key figures describe numeric information that is reported in a query. Example: Quantity (0QUANTITY) Amount (0AMOUNT) Revenue (0REVENUE) Unit Characteristics: Unit characteristics provide a means of key figures values, stores currencies or units of measure. EUR, and so on) Time Characteristics: Time characteristics form the time reference frame for many data analyses and

evaluations. They are delivered with BI Content.

smallest granularity Note: System does not allow creating our own time characteristics. Technical Characteristics: Technical characteristics have administrative purposes. Example: Request ID (0REQUID) Change ID (0CHNGID) Different Types of Tables When we activate a characteristic, based on the settings we chose while creating characteristic below tables will generate. 1) Master data table 2) Text table 3) SID Table 4) Attribute tables 5) Hierarchy tables.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10db929a-7abb-2e10-6fa5d8d45ca028ed?QuickLink=index&overridelayout=true