bw_read_metadata_tables
Read SAP BW object definitions from metadata tables when no REST resource exists, covering transformations, DTPs, DSOs, load history, and process chains.
Instructions
Read a BW object definition from its metadata tables (ADT DataPreview, read-only; needs ADT authorization). The route for objects without a REST resource on this system. object_type → result: TRFN transformation with rules and routine code; DTPA DTP; ODSO classic DSO, CUBE InfoCube, MPRO MultiProvider (parts with their type) — each with load history; ADSO load history only; ANPR analysis process (nodes, field rules, routine code; "Z*" lists them); ISIP InfoPackage (a DataSource name lists its InfoPackages); RSPC process chain definition; RSPCLOG chain runs; PLSE planning function; PLSQ planning sequence; PLCR planning properties; PLDS data slices. Details per type are in the object_type parameter. Prefer the REST tool (bw_get_transformation, bw_get_dtp, …) where the system publishes one.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| object_name | Yes | Technical name of the object (for TRFN the UUID-like transformation ID; for PLCR and PLDS the InfoProvider, not the aggregation level; for RSPCLOG a chain name, a run log id, or a pattern such as "Z*" for the last status per chain; for ANPR a process name or a pattern such as "Z*"; for ISIP the InfoPackage id, or a DataSource name to list its InfoPackages). | |
| object_type | Yes | Object type to read. TRFN: rules incl. start/end/expert and field routine source code. DTPA: settings; the filter definition (selections, filter routine, semantic group, package sizes) is a serialised ABAP object, reported only where the optional helper endpoint of bw75/README.md is installed and named as unreadable where it is not. ADSO: load history only — structure and settings come from bw_get_adso. ODSO, CUBE, MPRO: structure, and for MPRO the part providers with their type, so each can be passed on directly; a name read under the wrong provider type names the right one. ADSO, ODSO, CUBE and MPRO end with the load history (request, status, update mode, start, user, duration, records, source) — on a classic release the only route to load status. RSPC: steps with variant parameters in execution order; parallel branches have no order among themselves, so read the "After" line of each step. RSPCLOG: process chain runs — a chain name gives the run history plus the steps of the newest run, a 25-character log id the steps of that run, a pattern with * the last status of every matching chain; the message log of a failed step is not readable here. PLSE: planning function type, aggregation level, characteristic usage, conditions, parameters, FOX formula as source code. PLSQ: planning sequence steps in execution order. PLCR: planning properties and characteristic relationships. PLDS: data slices (no REST resource on any release). PLCR and PLDS are keyed by the InfoProvider, not the aggregation level. ANPR: analysis process (APD, classic only) — nodes in execution order with the object each source reads and each target writes, the edges with their field rules (copies and constants), filters, formulas and routine code; a pattern with * lists the analysis processes, which bw_search cannot find. ISIP: InfoPackage (classic only) — DataSource, file settings, selections with routines, deletion settings, the process chains using it, load history. |