Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
USMD1 (Package) Master Data: Data Modeling
Basic Data
| Data Element | USMD_FLD_PROP |
| Short Description | Field Properties |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | USMD_FLD_PROP | |
| 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 | 0 | |
| Medium | 20 | Field Properties |
| Long | 20 | Field Properties |
| Heading | 20 | Field Properties |
Documentation
Definition
Identifies which fields are relevant to a change request step, and which of the relevant fields are required.
If you keep the Standard setting for an entity type, you can overrule this setting for some of its attributes.
If however, you select No Required Field Check or Not Relevant for an entity type, the system copies your selection to all of its attributes and you cannot change attribute settings.
Use
Dependencies
Standard
If you apply this setting to an attribute, the system determines whether the field is optional or required using the following logic.
- The system checks if the Required Field setting is selected within the data model.
Note
You can apply the Required Field setting in the following locations:
- The Attributes tab page of the Configuration Workbench.
- To access this tab page, you must first select a data model and an entity type.
- The Attributes view of the Edit Data Model activity
- Depending on the Required Field setting, the system takes the following action:
- If the Required Field setting is selected, the Standard Setting is required.
- If the Required Field setting is deselected, the Standard setting is derived from custom code (see BAdI: Access to Customer-Dependent Field Property Settings) or from the Reuse Active Area.
Note
You can specify a class for the Reuse Active Area in the following locations:
- The Reuse Active Area field in the Data Model Details section of the Configuration Workbench.
- To access this section, you must first select a data model.
- The Reuse Active Area of the Edit Data Model activity.
No Required Field Check
If you apply this setting to an entity type, all required attributes for that entity type become optional attributes for the selected change request step only.
Caution
For required fields, you must ensure that the Standard setting is at least applied to the last step. You cannot activate a change request if required fields have no entries.
Not Relevant
If you apply this setting to an attribute, the system ignores the attribute. No checks are conducted and the field is read-only. You can exclude the fields that are Not Relevant from the user interface by using custom Web Dynpro configurations. You can define these Web Dynpro configurations in the User Interface Per Change Request Step view of this Customizing activity.
Example
If you create a supplier, the reconciliation account ID is a required field. The first processor who creates a supplier usually does not know what the reconciliation account ID is, but sometimes does know what the reconciliation ID number is. You want the field to be optional in the first step, but required in subsequent steps. So you select No Required Field Check for the first step.
If you are sure that a processor does not know what a reconciliation account ID is, you can go one step further and set the field to Not Relevant. In this case, the user cannot input incorrect values and is not confused by the presence of an input field. You can also hide fields you have set to Not Relevant.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 731 |
