Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
PM-EQM-ON (Application Component) Object Networking⤷
INET (Package) Application Development R/3 Object Networking
Basic Data
| Data Element | TPKANT |
| Short Description | Link object is a functional location |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TPLNR | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 40 | |
| Value Table | IFLOT |
Further Characteristics
| Search Help: Name | IFLM | |
| Search Help: Parameters | TPLNR | |
| 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 | LinkObject |
| Medium | 15 | FL LinkObjct |
| Long | 15 | Link object |
| Heading | 30 | Link object |
Documentation
Definition
Number of the linking functional location
The linking functional location represents the link between the two functional locations above.
Supplementary Documentation - TPKANT 0001
Use
The link between two functional locations is defined by the link number and the short text. A link object does not have be entered. However, if you want to have the link that exists physically, in other words the link element, represented in the system, the linking functional location must be entered here.
Procedure
Examples
Dependencies
If you want to carry our maintenance work on the physical link using maintenance orders, a linking functional location must exist as the link object, as orders can only be created for equipment and functional locations.
Note that two functional locations can only be linked by another functional location and not by a piece of equipment.
History
| Last changed by/on | SAP | 19971105 |
| SAP Release Created in |
