bw_get_infoarea

add a field-based (pure) field without an InfoObject

Reassign an existing BW object to a different package (Development Class) and record the change on a transport request via the CTO write endpoint. A single write, no activation — afterwards the object is inactive and must be re-activated with bwactivate (passing the same transport). For DataSources

Create a new aDSO. Supports two modes: fromtemplate (copies structure from an existing aDSO) or empty. Supports all aDSO type presets including write-interface (pushMode).

Create a new DTP on a Transformation. Source and target are derived from the Transformation automatically. For a DataSource source, set sourcetype="RSDS" and pass sourcesystem. For an InfoObject target (targettype="IOBJ"), select the loaded sub-object with targetobjectsubtype — ATTR (attributes / ma

Create a new InfoArea. Immediately active after creation, no activation step needed.

Create a new InfoObject. Supports:

Create a new InfoSource with full field definitions.

Create a new, consistent Query (TLOGO ELEM) on an InfoProvider in package $TMP. Without copyfrom the query is created empty and consistent (no rows, columns, or key figures yet). With copyfrom it is created as a full copy of an existing query (layout, filter, variables, key figures); when no infopro

Create a new Transformation. Supports all source types (aDSO, InfoSource, DataSource/RSDS) and all target types (aDSO). For InfoObject (IOBJ) sources or targets, set sourceobjectsubtype / targetobjectsubtype to select the facet — TEXT (text table), ATTR (attributes / master data), or HIER (hierarchy

Add a task (sub-request) for a user to an existing workbench transport request.

Remove an existing routine from a Transformation field.

Read the full structure of an aDSO — fields, key fields, settings, version state.

Read the full definition of a single DTP — source, target, transformation reference, extraction settings (mode, package size), and all filter fields including value selections and routine code. DTP names are UUID-like keys — use bwxref or bwgetdtps to find them.

List all DTPs that depend on a given BW object or Transformation.

Read an InfoObject definition (Characteristic or Key Figure).

Read an InfoSource (TRCS) structure — fields, key fields, label, InfoArea, version status.

Get the expected JSON schema for pushing data into a write-interface aDSO.

Read a Transformation structure including all field mapping rules, routines, source, and target. Transformation names are UUID-like keys — use bwxref on the target aDSO to find them.

List transport requests and their tasks via the BW transport state (cto/check).

Move any BW object (aDSO, InfoObject, InfoArea, etc.) to a different InfoArea.

Push a JSON record array directly into a write-interface aDSO via the BW Push API (/sap/bw4/v1/push/).

Start (execute) a run of an existing, active DTP. Returns the new run request id (an RSPM TSN) that can be passed directly to bwgetrequest for monitoring.

Search BW objects by name or description. Supports wildcards (). Optionally filter by object type (ADSO, IOBJ, TRFN, DTPA, etc.).

Set an ABAP routine filter on a DTP field. The generated routine's inactive version is syntax-checked before activation — broken code is reported with the ABAP messages and the DTP is left unchanged, instead of being falsely reported as activated.

Write the code of an existing Start/End/Expert routine into the Transformation master so it survives activation and transport. Unlike a raw WriteSource on the generated class, this re-saves the master and keeps the routine code transport-stable.

Set a field routine, start routine, or end routine on a Transformation. Supports both ABAP and AMDP (SQLScript). The routine code is written in combination with an ADT MCP server.

Switch the Transformation runtime between ABAP and HANA (AMDP). The current runtime is read from the active version, the change is activated automatically, and the result is verified against the active version — no separate bwactivate call is needed. If the switch does not persist (e.g. the server r

Modify an existing aDSO. Actions:

Update a DTP — description, value filters on fields, and extraction mode (extractionmode = full / delta). Note: switching between Delta and Full has BW delta-init implications — a later delta load may require re-initialization.

Add or remove display (DIS) and navigation (NAV) attributes on an existing Characteristic.

Update an existing InfoSource — fields and description.

Edit the query layout — add/remove rows, columns, structures, and free characteristics. Accepts an optional transport request number for queries on a transportable package.

Modify field mappings in an existing Transformation:

Find all objects that reference a given BW object (where-used analysis). Use this to find Transformations and DTPs connected to an aDSO, or to find the process chain(s) a DTP belongs to (objecttype=DTPA).

set or update key fields

remove a field

change aggregation, data type, length, etc.

change aDSO type preset, flags, or description