Hierarchy
EA-HRRXX (Software Component) Sub component EA-HRRXX of EA-HR⤷
PA-ESS-XX (Application Component) Common Parts⤷
PAOC_FACE_ESS_PERSINFO (Package) Personnel information
Basic Data
| Data Element | XSS_PER_CASE |
| Short Description | Use Case for Date Handling in ESS Personal Information |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XSS_PER_CASE | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | 0 | |
| Long | 0 | |
| Heading | 0 |
Documentation
Definition
Two-character alphanumeric key that steers the behavior of the Self-Service user interface for Personal Information.
Use
The use of the key is specified per infotype and per country; if that infotype has subtypes then it is specified per subtype also.
The first character of the key is the validity indicator. This indicates whether an employee is exposed to date handling in ESS Personal Information scenarios.
A: A record can be created specifying the valid start and/or end date Multiple records can exist.. By default the ESS scenario's will allow you specify the start date as today or future date. If you wish to enable ESS scenario's to accept a start date in the past, Business Add-in "HRXSS_PER_BEGDA" can be implemented.
For more information, please refer to IMG activity "Change Default Start Date".
B: A record can be created without specifying the valid start and/or end date. Multiple records are not possible.
The second character of the key indicates other UI behaviors for a specific infotype/subtype as described below:
B1: One infotype record must exist for the entire period of an employee's activity in the enterprise. Once a record for an infotype/subtype is available "New <infotype/subtype>" button will not be available on the overview screen of the concerned scenario. For E.g., suitable to scenario Personal Data
B2: Once a record for an infotype/subtype is available "New <infotype/subtype>" button will not be available on the overview screen of the concerned scenario. For E.g., suitable toscenario Spouse
B3: "New <infotype/subtype>" button will always be available on the overview screen of the concerned scenario. For e.g., suitable to scenario Child.
B4: Variant of B1. In addition behavior of B1, "New <infotype/subtype>" button will always be available on the overview screen of the concerned scenario. E.g., suitable to scenario Permanent address
B5: Variant of B2. In addition to behavior of B2, "New <infotype/subtype>" button will always be available on the overview screen of the concerned scenario. E.g., suitable to scenario Mailing address
A1: One infotype record must exist for the entire period of an employee's activity in the enterprise. Once a record for an infotype/subtype is available "New <infotype/subtype>" button will not be available on the overview screen of the concerned scenario. E.g., suitable to scenario Personal Data
A2: Once a record for an infotype/subtype is available "New <infotype/subtype>" button will not be available on the overview screen of the concerned scenario. E.g., suitable to scenarioSpouse
A3: Multiple Infotype records of same entity (for e.g., 1st Child) can not exist at the same time. "New <infotype/subtype>" button will always be available on the overview screen of the concerned scenario. E.g., suitable to scenario Child
A4: Variant of A1, Difference to A1 being, "New <infotype/subtype>" button will always be available on the overview screen of the concerned scenario. E.g., suitable in Permanent address.
A5: Variant of A2. Difference to A2 being, "New <infotype/subtype>" button will always be available on the overview screen of the concerned scenario. E.g., suitable in Mailingaddress
A6: Multiple infotype records of the same type (e.g. other bank) may exist for an employee at the same time. "New <infotype/subtype>" button will always be available on the overview screen of the concerned scenario. E.g., suitable in Other bank.
Important Note:
1) In case the first character is B, future records, if already exist, will not be displayed.
2) A3: This can be used only if the time constraint of the concerned infotype/subtype is 2 and it object identification is permitted.
3) A6: This can be used only if the time constraint of the concerned infotype/subtype is 3.
4) B3: This is applicable for both time constraint 2 with object identification permitted and time constraint 3.
Example
History
| Last changed by/on | SAP | 20050409 |
| SAP Release Created in | 100 |
