SAP ABAP Data Element RONOTEXRE (Only Known in Exit)
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷ BC-BW (Application Component) BW Service API
⤷ RSUM (Package) BW Service API: Metadata
⤷ BC-BW (Application Component) BW Service API
⤷ RSUM (Package) BW Service API: Metadata
Basic Data
Data Element | RONOTEXRE |
Short Description | Only Known in Exit |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ROFLAG | |
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 | Only Exit |
Medium | 15 | Only in Exit |
Long | 30 | Only Known in Exit |
Heading | 30 | Only Known in Exit |
Documentation
Definition
Fields with the Field Only Known in Exit indicator are not passed to the extractor in the field list and the selection table.
This setting is required to avoid runtime errors in the extractor since it is possible that the extractor is coded only to those fields that existed when the DataSource was defined.
For fields of an append structure that were added to a customer scenario, the Field Only Known in Exit indicator should therefore be set.
Use
Procedure
- If a field (from an append structure, for example) is not to be passed to the extractor at runtime, select this indicator.
- If a field is to be passed to the extractor, deselect Field Known Only in Exit.
This is only effective if the extractor is coded generically and can react to the added fields.
Examples
Dependencies
History
Last changed by/on | SAP | 20080415 |
SAP Release Created in |