Hierarchy
EA-HRCUS (Software Component) Sub component EA-HRCUS of EA-HR⤷
PA-PA-US (Application Component) USA⤷
PAOC_PAD_US_FD (Package) US Federal Public Sector
IMG Activity
| ID | OHPSUSCPDF110 | Define Validation Field Groups |
| Transaction Code | S_AEN_10000436 | (empty) |
| Created on | 20050225 | |
| Customizing Attributes | OHPSUSCPDF110 | Define Validation Field Groups |
| Customizing Activity | OHPSUSCPDF110 | Define Validation Field Groups |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHPSUSCPDF110 |
Use
The validation field groups are used to define the fields that are available for validation in the validation rules.
When you have created the validation rule, the fields will be available as configured. By opting to include a field in the NEW and/or PRIOR structures, the field will be available in the validation configuration under the technical name NEW-(CONFIGURED_NAME) or PRIOR-(CONFIGURED_NAME) respectively. If selected to be in the PRIOR structure, then the text will be the same as the text for the NEW field, but will be preceded by the word 'Prior'.
If selected to be in the SUBSTITUTION structure, then it is available in the validation configuration for substitution.
Requirements
Prior to creating the field group, determine the technical names and texts for the fields to be included in the validation rules to be configured under the field group. Determine if the individual fields should be available in the NEW structure, PRIOR structure, and SUBSTITUTION structure.
Activities
- Create a field group by creating a name and text for the group.
- Create fields in the field group.
- Enter a technical name for the field.
- Enter a type for the field. The type must refer only to a single data element, and cannot refer to a structure or table type.
- A default text is determined for the field based on the type; you can overwrite this text if desired.
- Select the appropriate check boxes to determine if the field is available in the NEW, PRIOR, and SUBSTITUTION structures.
Tips
If you are creating a field group that is to be attached to a validation with another field group, be sure that any fields with the same technical name have the same type. An error will be raised if there is an attempt to attach two field groups with a field with the same technical name having different types.
You may opt to include all fields in the NEW structure if desired, if this includes all 'Prior' fields as well. For example, you may want to include all CPDF fields as NEW fields, including fields such as 'Prior Pay Grade', etc. If this option is chosen, you should not also include the fields in the PRIOR structure because this may lead to confusion during rule configuration.
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHPSUSCPDF110 | US | USA |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHPSUSCPDF110 | 0 | ALN0000203 | Functions for U.S. Federal Government |
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 |
| VC_T5UPBSPA20 | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20050225 |
| SAP Release Created in | 600 |
