Hierarchy
BBPCRM (Software Component) BBPCRM⤷
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
IMG Activity
| ID | SIMG_CFMENUOFDIFODP | Set Preset User Fields |
| Transaction Code | S_ALR_87007282 | IMG Activity: SIMG_CFMENUOFDIFODP |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOFDIFODP | User Fields |
| Customizing Activity | SIMG_CFMENUOFDIFODP | User Fields |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOFDIFODP |
In this section, you define individual user fields that you want to include in addition to the fields in the master data maintenance.
For the real estate objects, you can define several sets of fields that are stored under a field key.
Within the user fields, the following types of fields are distinguished:
- General fields for texts (a set of 2 fields with 20 or 10 characters)
There you can store any information as text
- Quantity fields and their units
- Value fields and their units
- Deadline fields
You then determine which sets of user fields are to be used (field key) for which real estate objects.
Example:
You want to define nature conservation data in the user fields for your properties.
To do this, you define a field key "NATUR" with the following identifiers for the fields (examples):
Text (20) Valid nature conservation Regulation no.
Text (10) Approp. authorities Clerk
Quantity ......... .........
Value ........ ........
Date Nature conserv. since: .....
Checkbox Biosphere reserve .............
You then determine that the field key "NATUR" may be used for properties:
0052 NATUR nature conservation characteristics
Activities
- Define your user fields for each key ID and determine the field descriptions.
- Assign your user fields to the objects in question by means of the field key.
You can assign as many key words as you want to one object. All assigned key words are then displayed for selection in the maintenance of the corresponding master data.
In this case, you can only assign one data record of the user fields to the respective object when you maintain the master data. If there are entries for a master record for one of the key words, all other key words are no longer available for input.
Further notes
The system does not check the contents of the user fields. You yourself are responsible for the contents of the fields.
This functionality is used in conjunction with the Project System component. If you have installed PS, if you should make sure you do not change any PS entries during processing.
Business Attributes
| ASAP Roadmap ID | 261 | Define Screen Control |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOFDIFODP | 0 | I090004603 | Basic Data |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TCN01 | V - View | SM30 | V_TCN01 | Field Keys and Field Names | ||
| V_TZS12 | V - View | SM30 | V_TZS12 | Assignment of Field Keys to Objects |
History
| Last changed by/on | SAP | 19990326 |
| SAP Release Created in |
