Hierarchy
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR⤷
PA-AS (Application Component) HR Administrative Services⤷
PAOC_ASR_INFTY_CONTROLLER (Package) Control Infotypes
Basic Data
| Data Element | ASR_PAITF_OPERATION |
| Short Description | Operation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ASR_PAITF_OPERATION | |
| 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 | 10 | Operation |
| Medium | 15 | Operation |
| Long | 20 | Operation |
| Heading | 9 | Operation |
Documentation
Definition
Operations are used to define how the infotypes in the form scenario are processed. Operations are not defined directly for infotypes, but rather for so-called info objects that contain the subtype and the object ID as well as the infotype.
Use
The backend service SAP_PA (Personnel Administration infotypes) supports the following operations:
- Create
- Change
- Change Without Delimiting
- Delete
The selected operation should always be consistent with the time constraint of the info object. A differentiation is generally made between the following three time constraints:
- Time constraint 1: Exactly one data record exists for each time constraint
- Time constraint 2: Exactly one or no data record exists for each time constraint
- Time constraint 3: Any number of data records exists for each time constraint.
The operation can have a different effect, depending on the time constraint of the info object. For example, the "Create" operation always creates a new data record for an info object with time constraint 3. By comparison, an existing data record is first delimited for an info object with time constraint 1 or 2.
The effectiveness of the operation, that is, the date on which the change to the info object is made, is determined by the effective date. Alternatively, you can map the start and end dates of the infotype manually to the corresponding form fields.
Dependencies
Example
Examples for info objects
[0002, space, space] - Basic Data Person
[0006, space, space] - Any Address
[0006, 1, space] - Main Address
[0021, 1, space] - Spouse
[0279, N001, 01] - Individual values for product 01 (= "Retirement Scheme") of the pension fund N001
History
| Last changed by/on | SAP | 20050411 |
| SAP Release Created in | 600 |
