Hierarchy

⤷

⤷

Basic Data
Data Element | RSTRAN_ALL_FIELD |
Short Description | Set Update Behavior for Fields of End Routine |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RS_BOOL | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | Fields |
Medium | 20 | All Fields |
Long | 40 | All Fields |
Heading | 20 | All Fields |
Documentation
Definition
It might be advisable not to update certain fields of DataStore objects that are not write-optimized or master data attributes. For example, if you want to fill various InfoObjects of a data record from different sources. According to this logic, only InfoObjects for which there is an active rule in the transformation are updated in the target. However, if an end routine is created in the transformation, you might need to update all the fields since they are filled in the end routine. According to the logic described above, these fields would not be updated if there were no active rule for the target InfoObject. In this case you can define in the transformation the update behavior for fields of the end routine for DataStore objects and master data attributes.
Caution: If only the key fields are updated for master data attributes, all the attributes are initialized anyway, whatever the settings described here. More information is available in SAP Note 1096307.
Use
In the transformation there is a pushbutton for defining the update behavior in the toolbar. The default is that fields are updated in the transformation according to the active rules . Another option is to define that all the fields should always be updated. As a result, fields filled in the end routine are not lost if there are no other active rules.
Dependencies
This setting is only available for master data attributes and DataStore objects that are not write-optimized.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 720 |