Hierarchy
⤷ BW-WHM-DST (Application Component) Data Staging
⤷ RSTRAN (Package) Transformation
Basic Data
Data Element | RSTRAN_RULETYPE |
Short Description | Type of Rule |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RSTRAN_RULETYPE | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Rule Type |
Medium | 15 | Rule Type |
Long | 20 | Rule Type |
Heading | 8 | RuleType |
Documentation
Definition
The rule type determines whether and how a characteristic or key figure, or a data field or key field is updated to the target.
Use
The following options are available:
Direct assignment: The field is filled directly from the chosen source InfoObject.
Constant: The field is not filled by the InfoObject but is filled directly with the value specified.
Formula: The InfoObject is updated with a value determined using a formula.
Read master data: The InfoObject is updated by reading the master data table of a characteristic that is included in the source with a key and a value and that contains the corresponding InfoObject as an attribute.
Read from DataStore object: The InfoObject is updated by reading a characteristic in a DataStore object (similar to reading master data). Data is read from both the database and near-line storage.
When reading from the DataStore object or the master data table, the system reads data from the database in one step. In this case, performance is higher than with manually implemented routines, which usually just read single records.
Routine: The field is filled by the transformation routine you wrote. With InfoCubes, you can also select Routine with Unit. The return parameter 'UNIT' is then also added to the routine.
Time update: When a time update is performed, automatic time conversion and time distribution are available.
You can update source time characteristics to target time characteristics using automatic time conversion. This function is not available for DataStore objects, since time characteristics are treated as normal data fields.
You can update time characteristics with time split. All the key figures that can be added are split into correspondingly smaller units of time. If the source contains a time characteristic (such as 0CALMONTH) that is not as precise as a time characteristic of the target (such as 0CALWEEK), you can combine these characteristics in the rule.
Derive Hierarchy Characteristic: The InfoObject 0H_IOBJNM (characteristics for hierarchies) is used to derive node names from the InfoObject names. To do this, assign the InfoObject 0H_IOBJNM to the field FIELDM (field name). In the rule details, select the rule type Derive Hierarchy Characteristic. At runtime the InfoObject is automatically entered in the field 0H_IOBJNM. The InfoObject is assigned to the same field name that is contained in FIELDNM at runtime.
Hierarchy Split: The Hierarchy Split rule type is used if the NODENAME field from hierarchy structures in IDoc format is assigned to the target InfoObjects of the hierarchy. The NODENAME field has to be assigned to the basis characteristic and external characteristics of the hierarchy. The Hierarchy Split rule type is used dialog as the rule type in the rule detail. The value in the 0H_IOBJNM field must contain the name of the node InfoObject. At runtime, the hierarchy split takes the relevant part of the value from the NODENAME field and enters it in the corresponding compound components of the target InfoObject.
Initial: The field is not filled. It remains empty.
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 400 |