Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
Basic Data
Data Element | VVJEQM_AUTO |
Short Description | Automatic creation of functional location for RE object |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | JANE | |
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 | Aut. FL |
Medium | 15 | Aut.create FL |
Long | 20 | Aut.create FL |
Heading | 10 | Aut. FL |
Documentation
Definition
Indicates whether a functional location should be automatically generated in the background in Plant Management when a Real Estate object (business entity, property, building or rental unit) is created.
A customer exit is used to merge data from IS-RE and PM. If the Real Estate object is changed, you can copy any changes to the functional location using a customer exit.
Example
There is a 1:1 relationship between the objects in IS-RE and the functional locations in PM. When you create a building, the system will automatically generate a functional location and assign it to the building.
The location hierarchy is also automatically maintained so that the Real Estate object hierarchy always matches the functional location hierarchy.
If you change the address of the Real Estate object, the new address can be copied to the functional location. Any changes to the status of a Real Estate object also influence the status of the functional location.
History
Last changed by/on | SAP | 19981211 |
SAP Release Created in |