bw_update_transformation

Added value: +{
+  "description": "Aggregation type of the rule on a target key figure: \"SUM\" (summation), \"MOV\" (overwrite), \"MIN\", \"MAX\" or \"NOP\" (no aggregation). It decides what happens when several source records end up in one target record. Given alone (with transformation_name and target_infoobject only), it changes the aggregation and leaves the rule as it is; given with a rule change, both are saved together. Refused for a target field whose aggregation the target does not let a transformation override.",
+  "enum": [
+    "SUM",
+    "MOV",
+    "MIN",
+    "MAX",
+    "NOP"
+  ],
+  "type": "string"
+}

Added value: +{
+  "description": "Currency or unit conversion for a direct rule on a key figure with a currency or unit (rule_type=\"direct\"). Omitted or type \"none\": no conversion — the value is taken over as it is, which is also what direct, formula and constant rules on such a key figure get by default. Type \"currency\": convert with a currency translation type; type \"unit\": convert with a unit conversion type. The name is checked against the types defined on the system, and an unknown name is refused with the list of available ones. The source currency/unit comes from source_unit_field, else from the source key figure's own unit reference; a conversion type with a fixed source needs neither. The transformation's currency/unit handling is switched on.",
+  "properties": {
+    "name": {
+      "description": "Currency translation type or unit conversion type (e.g. \"CONV_TYPE\").",
+      "type": "string"
+    },
+    "source_unit_field": {
+      "description": "Source field holding the source currency or unit (e.g. \"CURRENCY_FIELD\").",
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "none",
+        "currency",
+        "unit"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "type"
+  ],
+  "type": "object"
+}

Previous value: -"Additional source fields for rule_type=\"formula\" when the formula references more than one source field. Combined with source_field, all listed fields are registered as inputs on the StepFormula rule. Example: [\"QUANTITY_SOLD\", \"COST_PER_UNIT\"]."New value: +"Additional source fields for rule_type=\"formula\" when the formula references more than one source field. Combined with source_field, all listed fields are registered as inputs on the StepFormula rule — alongside the operands read out of the formula itself, so this is only needed for a field the expression does not name under its source-segment name. Example: [\"QUANTITY_SOLD\", \"COST_PER_UNIT\"]."

Previous value: -"Formula expression for rule_type=\"formula\" (required). Source fields are referenced by their technical field name: use /BIC/FIELDNAME for custom InfoObjects (e.g. \"/BIC/FIELD_NAME + 10\"), or the direct field name for standard InfoObjects. Operators: +, -, *, /. Functions: IF, ABS, CONCATENATE, DATE_YEAR, etc. Comparison operators < > <= >= <> are supported (will be XML-escaped automatically)."New value: +"Formula expression for rule_type=\"formula\" (required). Source fields are referenced by their technical field name: use /BIC/FIELDNAME for custom InfoObjects (e.g. \"/BIC/FIELD_NAME + 10\"), or the direct field name for standard InfoObjects. Operators: +, -, *, /. Functions: IF, ABS, CONCATENATE, DATE_YEAR, etc. Comparison operators < > <= >= <> are supported (escaping is handled automatically, in either spelling). Every operand of the expression is wired up as a source of the rule; operands that name a source-segment field are recognised in the expression itself, so a multi-operand formula works without listing them."

Previous value: -"Rule type to assign. \"direct\" (default): maps source field directly (StepDirect). \"routine\": converts the rule to an AMDP field routine (StepRoutine) — the server generates the ABAP class automatically. \"formula\": converts the rule to a formula rule (StepFormula) — requires the formula parameter. \"constant\": sets a fixed constant value (StepConstant) — requires the constant_value parameter, source_field is ignored. \"lookup\": converts the rule to a StepRead (Lookup) rule — requires lookup_object and lookup_object_type. \"no_update\": reverts any existing mapping back to StepNoUpdate (no mapping, field stays empty). IMPORTANT: AMDP SQLSCRIPT methods only allow ASCII 7-bit characters — no German umlauts or special symbols in code or comments."New value: +"Rule type to assign. \"direct\" (default): maps source field directly (StepDirect). \"routine\": converts the rule to an AMDP field routine (StepRoutine) — the server generates the ABAP class automatically. \"formula\": writes the rule as a formula rule (StepFormula) — requires the formula parameter; also used to change the formula text of an existing formula rule. \"constant\": sets a fixed constant value (StepConstant) — requires the constant_value parameter, source_field is ignored. \"lookup\": converts the rule to a StepRead (Lookup) rule — requires lookup_object and lookup_object_type. \"no_update\": reverts any existing mapping back to StepNoUpdate (no mapping, field stays empty). IMPORTANT: AMDP SQLSCRIPT methods only allow ASCII 7-bit characters — no German umlauts or special symbols in code or comments."

Added value: +{
+  "description": "Source unit/currency field for a COMBINED key-figure + unit/currency direct rule (rule_type=\"direct\"). When set, target_infoobject is the key figure and this is the source field that fills its unit or currency. The target unit/currency field is derived automatically from the key figure's unit reference in the aDSO (the target key figure must reference a unit/currency field). The standalone unit/currency rule is folded into the combined rule and the transformation's currency/unit handling is switched on. Example: target_infoobject=\"QUANTITY\", unit_source_field=\"QUANTITYUNIT\".",
+  "type": "string"
+}