Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BMT-OM (Application Component) Organizational Management⤷
SP00 (Package) Organization and Planning
Basic Data
| Data Element | EXT_INFTY |
| Short Description | Indicator: External Infotype |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1_X | |
| 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 | Extern.IT |
| Medium | 15 | Extern.infotype |
| Long | 20 | External infotype |
| Heading | 1 | E |
Documentation
Flag I777D-EXT shows whether the infotype is external in regards to Organizational Management.
This means that the external infotype does not use the HRP/HRT tables for saving data, but instead uses infotype-specific tables. For infotypes delivered by SAP, this flag is pre-set if the infotype is external.
Procedure
You must not make and changes here before consulting with SAP. Create your own infotypes for Organizational Management using transaction PPCI. This way, the flag does not have to be set. You must only set this flag when you generate your own external infotypes.
More Information
In this context, please also note our table T77ID. This table stores information about how the data for these infotypes is read and saved. This is done via function modules. If you want to see an example, navigatie to infotype 1610. The logic is infotype-specific.
Example
Infotypes 1610 and 1613.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |
