Persistent Staging Area 

Description

If you use the new data flow, the PSA is always the entry layer for data in BI. During the loading process, the data is updated to PSA tables, which were generated for active DataSources. The PSA is managed using the DataSource.

The previously used technology of the PSA was based on the transfer structure. The PSA table is generated for an active transfer structure in this case. Prior to SAP NetWeaver 7.0, the PSA as a standalone application was managed in an object tree of the Administrator Workbench. The functions that you could previously execute in the PSA tree have now been replaced by functions in other trees (such as the Manage context menu option for a DataSource).

For more information, see Persistent Staging Area.

General Practices with Migration

When you switch to the new data flow and migrate the 3.x DataSource, an existing PSA for this 3.x DataSource is copied to the migrated DataSource with the previously loaded requests.  Exceptions are DB Connect and UD Connect DataSources. Since the switch involves a copy, a new PSA is generated for each DataSource upon activation.

After migration, you can no longer use the process type Read PSA and Update Data Target. This must be replaced by the process type Data Transfer Process.