Start of Content Area

Component documentation Persistent Staging Area  Locate the document in its SAP Library structure

Purpose

The Persistent Staging Area (PSA) is the inbound storage area for data from the source systems in the BI system. The requested data is saved, unchanged from the source system. Request data is stored in the transfer structure format in transparent, relational database tables of the BI system in which the request data is stored in the format of the DataSource. The data format remains unchanged, meaning that no summarization or transformations take place, as is the case with InfoCubes.

Note

When loading flat files, the data does not remain completely unchanged, since it is adjusted by conversion routines if necessary (for example, the date format 31.21.1999 is converted to 19991231 in order to ensure uniformity of data).

The possible coupling of the load process from the further processing in BI contributes to an improved load performance. The operative system is not debited if data errors first appear with further processing.

The PSA delivers the backup status for the ODS layer (until the total staging process is confirmed). The duration of the data storage in the PSA is medium-term, since the data can still be used for reorganization. However, for updates to DataStore objects, data is stored only for the short-term.

Features

A transparent PSA table is created for every DataSource that is activated. The PSA tables each have the same structure as their respective DataSource. They are also flagged with key fields for the request ID, the data package number, and the data record number.

InfoPackages load the data from the source into the PSA. The data from the PSA is processed with data transfer processes.

With the context menu entry Manage for a DataSource in the Data Warehousing Workbench you can go to the PSA maintenance for data records of a request or delete request data from the PSA table of this DataSource. You can also go to the PSA maintenance from the monitor for requests of the load process.

Using partitioning, you can separate the dataset of a PSA table into several smaller, physically independent, and redundancy-free units. This separation can mean improved performance when you update data from the PSA. In the Implementation Guide with SAP NetWeaver  Business Intelligence   Connections to Other Systems    Maintain Control Parameters for Data Transfer you define the number of data records needed to create a new partition. Only data records from a complete request are stored in a partition. The specified value is a threshold value.

Constraints

The number of fields is limited to a maximum of 255 when using TRFCs to transfer data. The length of the data record is limited to 1962 bytes when you use TRFCs.

 

 

End of Content Area