Hierarchy
INSURANCE (Software Component) SAP Insurance⤷
FS-CM (Application Component) Claims Management⤷
ICL_CDC (Package) FS-CM: Data Capture
Basic Data
| Data Element | ICL_REQFLDCHECK |
| Short Description | Setting Regarding When Required Field Check Is Performed |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ICL_REQFLDCHECK | |
| 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 | 15 | Req.Field Check |
| Long | 20 | Required Field Check |
| Heading | 15 | Req.Field Check |
Documentation
Definition
Use
The following settings are possible:
- Required Field Check Online Only If User Selects Screen
With this setting, the system only performs the required field check online. The system checks the required fields of a screen when the user navigates to this screen. This functionality corresponds to that of the required field check in Release 4.71 and in previous releases.
If you choose this setting, you do not need to do anything else.
- Extensive Required Field Check Upon Save
The system performs the required field check online at the following events
- when the user selects the screen (see above description of setting Required field check online only if user selects screen)
- when the claim is saved
The required field check is performed in direct input in the same way as in dialog (online) mode.
If you choose the Extensive Required Field Check Upon Save, this might mean that you can no longer define required fields for a field group in customizing and instead you have to do this in Business Add-In (BAdI) FMOD2 for Field Groups in Standard (ICL_FMOD2).
Dependencies
Note: The following special explanations for IMG activities are only relevant if you opt for the Extensive Required Field Check Upon Save setting:
- BAdI ICL_FMOD2
If the claim subobject category is one where there might be several claim subobjects per claim, and they each have a different meaning (such as instances of the claim subobject category Claim Item Grouping in the line of health insurance, like prescription and invoice), you must implement the required field check in BAdI ICL_FMOD2.
You thereby ensure that the required field check only sends an error message for fields with empty field contents if certain conditions are met (for example, if a prescription is involved). - You can define required fields in IMG activity Configure Field Attributes for Each Activity.
Note:
Here you may only define required fields for claim subobject categories - for which there can only be a maximum of one claim subobject per claim (such as in the claim header)
- for which there can be several claim subobjects that all have the same meaning, with the result that they can all be treated in the same way as far as the required fields are concerned. The same fields are used in each case (for example, with diagnoses in the line of health insurance).
- You can also define required fields in IMG activity Configure Field Attributes for Each Internal Claim Type for Expert Mode.
The same note applies as for Configure Field Attributes for Each Activity. - You can also define required fields in IMG activity Configure Field Attributes for Each Internal Claim Type for Other Processing Modes.
The same note applies as for Configure Field Attributes for Each Activity.
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 472 |
