SAPFree referencePDF, Excel, Word exportSAP BW/4HANAAll SAP BW and BW/4HANA tools

SAP BW and BW/4HANA Metadata Tables Reference

This reference maps BW metadata objects to the tables that store them, with key fields, what you find there and whether the table still applies in BW/4HANA. Use it to write lineage, impact and monitoring queries in SE16, SQL or an ABAP report on BW 7.x and BW/4HANA.

Download:

Table	Object	Key fields	What you find there	BW 7.x / BW/4HANA	Join tip
RSTRAN	Transformation	TRANID, OBJVERS	Header: SOURCETYPE, SOURCENAME, TARGETTYPE, TARGETNAME, start and end routine IDs	Both	Filter OBJVERS = 'A'. Find all transformations into a target with TARGETNAME.
RSTRANRULE	Transformation rules	TRANID, OBJVERS, RULEID	One row per rule in a transformation	Both	Join to RSTRAN on TRANID and OBJVERS.
RSTRANFIELD	Rule fields	TRANID, OBJVERS, RULEID, ...	Source and target fields used by each rule	Both	Join to RSTRANRULE on TRANID, OBJVERS, RULEID to map source to target fields.
RSAABAP	ABAP routine code	CODEID, OBJVERS, LINE_NO	Source lines of routines in transformations and DTP filters	Both	Search the LINE field to find which routines read a given table.
RSBKDTP	Data transfer process	DTP, OBJVERS	DTP definition with source (SRC, SRCTP) and target (TGT, TGTTP)	Both	Match SRC and TGT to RSTRAN SOURCENAME and TARGETNAME.
RSBKDTPT	DTP texts	LANGU, DTP, OBJVERS	DTP descriptions	Both	Join on DTP and OBJVERS with LANGU = 'E' or your logon language.
RSBKREQUEST	DTP request (classic)	REQUID	DTP requests and their status in classic request management	BW 7.x; replaced by RSPM request management in BW/4HANA	Join DTP to RSBKDTP.
RSPMREQUEST	Request (RSPM)	Request TSN	Requests identified by transaction sequence number, with REQUEST_STATUS and REQUEST_IS_IN_PROCESS flags	BW 7.5 ADSO and BW/4HANA	Do not update directly; change request status in the request administration of the ADSO Manage screen.
RSPCCHAIN	Process chain steps	CHAIN_ID, OBJVERS, TYPE, VARIANTE	Each process in a chain with its process type and variant	Both	TYPE = 'DTP_LOAD' rows have the DTP name in VARIANTE.
RSPCCHAINT	Process chain texts	LANGU, CHAIN_ID, OBJVERS	Chain descriptions	Both	Join on CHAIN_ID and OBJVERS.
RSPCLOGCHAIN	Process chain runs	CHAIN_ID, LOG_ID	One row per chain run with date, time and status	Both	LOG_ID links to RSPCPROCESSLOG.
RSPCPROCESSLOG	Process run status	LOG_ID, TYPE, VARIANTE, INSTANCE	Status of each process in a run, with start and end time	Both	Join to RSPCLOGCHAIN on LOG_ID to find failed steps per run.
RSPCVARIANT	Process variants	TYPE, VARIANTE, OBJVERS	Parameters of process variants	Both	Join on TYPE and VARIANTE from RSPCCHAIN.
RSOADSO	DataStore object (advanced)	ADSONM, OBJVERS	ADSO definition and settings	BW 7.4 SP and later, BW/4HANA	Generated tables use the prefix /BIC/A plus the ADSO name.
RSOADSOT	ADSO texts	LANGU, ADSONM, OBJVERS	ADSO descriptions	BW 7.4 SP and later, BW/4HANA	Join on ADSONM and OBJVERS.
RSDODSO	Classic DSO	ODSOBJECT, OBJVERS	Classic DataStore object definitions	BW 7.x only; classic DSOs are not supported in BW/4HANA	Active table /BIC/A<name>00, activation queue /BIC/A<name>40.
RSDCUBE	InfoCube	INFOCUBE, OBJVERS	InfoCube header	BW 7.x only; InfoCubes are not supported in BW/4HANA	Fact tables /BIC/F<cube> and /BIC/E<cube>.
RSOHCPR	CompositeProvider	HCPRNM, OBJVERS	CompositeProvider definitions	BW 7.4 SP and later, BW/4HANA	Replaces MultiProviders in BW/4HANA.
RSDIOBJ	InfoObject	IOBJNM, OBJVERS	InfoObject type (IOBJTP), data type, length and settings	Both	Master data tables: /BIC/P (attributes), /BIC/Q (time-dependent), /BIC/T (texts), /BIC/S (SIDs), /BIC/H (hierarchy).
RSDIOBJT	InfoObject texts	LANGU, IOBJNM, OBJVERS	Short and long descriptions TXTSH, TXTLG	Both	Join on IOBJNM and OBJVERS.
RSZCOMPDIR	Query components directory	COMPUID, OBJVERS	Technical name COMPID and component type DEFTP (REP for a query)	Both	COMPUID links to RSZELTDIR and RSZELTTXT ELTUID.
RSZELTDIR	Query elements	ELTUID, OBJVERS	Directory of query elements (queries, structures, key figures, variables)	Both	DEFTP gives the element type.
RSZELTTXT	Query element texts	ELTUID, OBJVERS, LANGU	Query and element descriptions TXTLG	Both	Query description: RSZCOMPDIR.COMPUID = RSZELTTXT.ELTUID with DEFTP = 'REP'.
RSRREPDIR	Query directory	COMPUID	Query technical name and the InfoProvider (INFOCUBE field) it runs on	Both	Fastest way to list queries per InfoProvider.
RSDS	DataSource	DATASOURCE, LOGSYS, OBJVERS	DataSource definitions in BW	Both (BW/4HANA uses ODP and other source types)	Join to ROOSOURCE in the source system on the DataSource name.
RSLDPIO	InfoPackage	LOGDPID, OBJVERS	InfoPackage settings with the DataSource (OLTPSOURCE) and source system (LOGSYS)	BW 7.x only; InfoPackages are not used in BW/4HANA	Texts in RSLDPIOT.
RSTSODS	PSA table mapping	ODSNAME, ...	Maps a DataSource PSA to its generated /BIC/B table (ODSNAME_TECH)	BW 7.x; BW/4HANA uses an inbound ADSO table instead of PSA	Look up the /BIC/B000... table name for a DataSource.
RSHIEDIR	Hierarchy directory	HIEID, OBJVERS	Hierarchies with InfoObject IOBJNM and hierarchy name HIENM	Both	Nodes in /BIC/H<iobj>.
ROOSOURCE	DataSource (source system)	OLTPSOURCE, OBJVERS	DataSource header in the source ERP: extractor, delta process, extract structure	Source system table	Read it in the ECC or S/4HANA system, not in BW.
/BIC/A<name>1	ADSO inbound table	Request TSN, data package, record	Data loaded but not yet activated	ADSO in BW 7.4 SP and later, BW/4HANA	Empty after activation for standard ADSOs.
/BIC/A<name>2	ADSO active data table	Semantic key of the ADSO	Active data used for reporting	ADSO in BW 7.4 SP and later, BW/4HANA	Query this for current values.
/BIC/A<name>3	ADSO change log	Request TSN, data package, record	Before and after images for delta to further targets	ADSO in BW 7.4 SP and later, BW/4HANA	Grows fast: plan request housekeeping.
OBJVERS values	Object version	A, M, D	A active, M modified (revised, not yet active), D delivered (Business Content)	Both	Always filter OBJVERS = 'A' unless you are comparing versions.

Key fields show the main keys; open each table in SE11 on your release for the full list. SAP-delivered objects use /BI0/ instead of /BIC/. Read these tables, never update them directly.

Get a BW lineage query

Tell us the ADSO or query you care about and we will send a ready SQL or ABAP lineage query for your BW release.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Search by object (transformation, DTP, chain, query) or by table name. Each row gives the keys to join on and a tip for the most common question. Almost every metadata table has OBJVERS: filter OBJVERS = 'A' to read the active version, or you get the modified and delivered versions as duplicates. Text tables end in T and have LANGU in the key. For SAP-delivered content, generated table names start with /BI0/ instead of /BIC/.

Lineage: RSTRAN (source to target), RSBKDTP (DTP), RSPCCHAIN (which chain runs the DTP).
Monitoring: RSPCLOGCHAIN and RSPCPROCESSLOG.
Query catalog: RSRREPDIR, RSZCOMPDIR, RSZELTTXT.

Worked example: which chain loads an ADSO

To find what loads ADSO ZSALES01, read RSTRAN with TARGETNAME = 'ZSALES01' and OBJVERS = 'A' to get the source objects. Read RSBKDTP with TGT = 'ZSALES01' to get the DTP names. Then read RSPCCHAIN with TYPE = 'DTP_LOAD' and VARIANTE equal to each DTP name to get the CHAIN_ID, and RSPCCHAINT for the chain text. To see last night's run, take the latest LOG_ID for that CHAIN_ID from RSPCLOGCHAIN and read the step statuses in RSPCPROCESSLOG.

Version differences and gotchas

BW/4HANA removed InfoCubes, classic DSOs, MultiProviders, InfoPackages and the PSA, so RSDCUBE, RSDODSO, RSLDPIO and RSTSODS describe objects that only exist in BW 7.x. Their replacements are ADSOs (RSOADSO) and CompositeProviders (RSOHCPR). Request handling also changed: ADSO loads in BW 7.5 and all loads in BW/4HANA use RSPM request management with request TSNs instead of request IDs, stored in RSPMREQUEST. Do not edit RSPMREQUEST to unlock a request; use the request administration in the ADSO Manage screen. ADSO tables use suffix 1 (inbound), 2 (active) and 3 (change log).

How to check the result in the system

Open the table in SE11 to confirm fields on your release, and SE16 or SE16N to read data. Compare what you find with the BW modeling tools in Eclipse or RSA1, for example the transformation source and target or the DTP filter. For process chains, RSPC shows the same runs as RSPCLOGCHAIN. For ADSO tables, the Manage screen of the ADSO lists requests and the generated table names. Where a table is missing on BW/4HANA, the object type itself does not exist there.

Frequently Asked Questions

Which table stores BW transformations?

RSTRAN holds the transformation header with TRANID, source and target type and name. Rules are in RSTRANRULE and the fields per rule in RSTRANFIELD. Routine code is in RSAABAP. Always filter OBJVERS = 'A' for the active version.

What is the DTP table in SAP BW?

RSBKDTP stores DTP definitions with source (SRC, SRCTP) and target (TGT, TGTTP); texts are in RSBKDTPT. Classic DTP requests are in RSBKREQUEST, while BW/4HANA and BW 7.5 ADSO loads use RSPM request management and RSPMREQUEST.

Which table has the BW query description?

Join RSZCOMPDIR (technical name COMPID, DEFTP = 'REP' for queries) to RSZELTTXT on COMPUID = ELTUID and filter the language; TXTLG is the description. RSRREPDIR tells you which InfoProvider each query runs on.

What are the ADSO table names?

An ADSO generates /BIC/A<name>1 for the inbound table, /BIC/A<name>2 for active data and /BIC/A<name>3 for the change log, depending on the ADSO type. SAP-delivered ADSOs use /BI0/A. Definitions are in RSOADSO.

If you want your BW team to ask lineage and load-status questions in plain English on your own servers, Netray can add that AI layer over your BW metadata.

Talk to an Expert Explore More Free Tools