Sap Psa Table



  1. Sap Bw Delete Psa Table

A PSA table is generated when the 3.x transfer rules are activated, thus activating the 3.x transfer structure. Data can be loaded into this PSA table. If your dataflow is modeled using objects that are based on the old concept (3.x Info Sources, 3.x transfer rules, 3.x update rules) and the process design is built on these objects, you can. At PSA manage, we could see at tops the PSA table which /BIC/B0000106 and to view the data in SE16, we add additional 3 zero which ' /BIC/B' Here my confusing, when I did the deletion using process chain, the old data still exits in this PSA table, then the total data in PSA table will increase which plus with new data extraction as.

Skip to end of metadataGo to start of metadata
Before executing any report below is recommended to search for correction and implement them first
REPORT DESCRIPTION SAP NOTES
1 RSAR_PSA_CLEANUP_DIRECTORY/_MSThis report is used to check the PSA tables against the directory entries and the partition related inconsistencies.It is useful in scenarios when the PSA requests are deleted from the administrative data but not from the database, requests are not available in the PSA tree but exist in the corresponding PSA table, all the requests in a partition are deleted but the partition is not dropped and to check if data has been deleted or written into incorrect partitions1063105 (7.X)
1102626 (3.X)
2 SAP_PSA_PARTNO_CORRECTThis report is used to correct the incorrect partition assignment ie. requests getting assigned to PARTNO '0' in the PSA table.This report also helps reassigning the requests to the correct partition1051664(7.X)
1102626(3.X)
3RSAR_PSA_PARTITION_CHECKThis check report is used to detect the possible problems of indices and other database related issues of the PSA. This report helps in detecting the following inconsistencies:
a) Partitioning with global index
b) Inconsistencies between DDIC definition and DB tables
c) PSA definition without DDIC entry and vice-versa.
1012607,1338941 (7.X)
1360680(3.X)
4RSAR_PSA_CLEANUP_DEFINITION

This report checks the PSA tables in the system for consistency of the metaobjects and has correction options. If necessary the system set the status to INA in case an old version of the PSA table does not exists in the system anymore. In order to be able to extract data from an old PSA version some points has to be considered (see SAP note 2129192) and also the status has to be ACT in table RSTSODS.

There are three options provided:
a) Delete table definitions without DB
b) Delete PSA definitions that are no longer in use
c) Delete initial PSA tables that are not in use

939383,1332091, 2191080
(7.X)
768023 (3.X)

5 RSAR_RSTSODSPART_DUPLICATES

The report checks whether a single request is splitted with two PARTNO values in RSTSODSPART but assigned to single partition in the database.

1268933

6RSAR_RSTSODS_DUPLICATESThe 'RSAR_RSTSODS_DUPLICATES' program checks whether the same PSA
database table was used multiple times in the contents of the 'RSTSODS'
table.This table defines the usually unique assignment of a PSA table to a
DataSource of a source system.
765798
1344040
7 RSAR_RSTSODS_CHANGELOG_VRSThis report check whether a standard DSO has versioned changelog. It tries to Inactivate the definition of that version of changelog which has no data 1135256
8RSAR_PSA_NEWDS_MAPPING_CHECKused to find the psa's which are not mapped to any NEW_DS (entry in RSTSODS, no entry in RSDSSEG, entry in RSDS) 1377274, 1649615
9ZRS_CHECK_ORPHANPSA_NEWDSSets the Objstat = ACT in RSTSODS for entries with RSDSSEG = A , RSTSODS = INA provided the table should be active in the DB. 1649615
10RSAR_NEWDS_PSA_USEROBJ_CHECKused to cross check the field USEROBJ in RSTSODS with the fields(DATASOURCE , LOGSYS) of RSDSSEG 1435104
11RSAR_PSA_SPLIT_PARTNO_CORRECTHelps to find and repair duplicate entries in RSTSODSPART. One request should not be stored in multiple partitions. Move records to highest partition and adjust RSTSODSPART 1475255
12 RSDU_WODSO_REPART_HDB

only for HANA database; conversion or subsequent partitioning of DSO objects

1924115, 1776749, 1785116
13 RSAR_PSA_REPARTITION repartitioning in case max. partion 9999 has been reached 2002607, 2247910

ZRS_PSA_NEWDS_DELTA_DTP_CHECK

SapSap pa psa table

RS_PSA_PART_HIGH_VALUE_CHECK

Sap psa tableSap bw psa table size

SAP_PSA_ZEROCORRECT

RSPSADEL_SWITCH_DEL_CLASS

Sap Bw Delete Psa Table

Z_RSAR_RSTSODSFIELD_CORR