bw_adso_add_field
Add a field to an SAP BW ADSO, with optional activation. Handles XML internally, accepts field properties like name, type, length, and scale. Returns save/activation status.
Instructions
Atomic edit: add a local 'field'-type field to an ADSO and save (activate optional via autoActivate, default true). success reflects save/activate outcome; activated only means activation was attempted. Internally reads current XML, inserts the field, and saves — no large XML handling by the caller.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| name | Yes | Field technical name. | |
| label | No | ||
| scale | No | ||
| length | No | ||
| dataType | No | ||
| dimension | No | ||
| precision | No | ||
| transport | No | ||
| outputPath | No | If provided, the full result is written to this path (under the workdir) and the tool returns only a small summary envelope { ok, outputPath, bytes, summary }. Objects/arrays are written as JSON; ONLY the bw_*_get_xml family writes the raw XML string as plain text (that file is directly reusable as xmlPath in a later save call). Other *_get tools (e.g. bw_dtp_get, bw_trfn_get) write the PARSED XML-to-JSON tree, not raw XML — use the matching bw_*_get_xml tool when you need the raw XML string. Use outputPath for large responses (XML, table data, logs, dataflow graphs). When set, tools skip inline pagination/projection so the file contains the complete payload. | |
| autoActivate | No | ||
| semanticType | No | ||
| createTransport | No | ||
| transportDescription | No |