SAP ABAP Data Element INTUSE (Is the field group allocated internally)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
Data Element | INTUSE |
Short Description | Is the field group allocated internally |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MKNFLAG | |
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 | Internal |
Medium | 15 | Internal |
Long | 20 | Allocate internally |
Heading | 1 | I |
Documentation
Definition
This indicator controls whether the relevant field group is allocated internally (that is, by defining sender and receiver). If you do not allocate internally, you can still update the field group. In this case, however, you have to specify an alternative source.
For example, in Special Purpose Ledger, you can update the transaction currency without having to allocate it directly (internally). You would normally select the group currency as the alternative source for the data. The group currency converted into the transaction currency unit would then be updated in the transaction currency fields.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in |