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_BLP_OPERATION |
| Short Description | Operation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ASR_BLP_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_PT (Time Management infotypes) supports the following operations:
- Create
- Change (restricted)
- Delete
The effectiveness of the operation, that is, the date on which the change to the info object is made, is determined by the required entry fields EFFECTIVE_BEGDA and EFFECTIVE_ENDDA. Alternatively, you can map the start and end dates of the infotype manually to the corresponding form fields.
The Change operation is only available in a restricted capacity. You should use the operation only if the Time Management infotype behaves like an infotype with time constraint 1 or 2, in other words, a maximum of one data record exists in the database at all times.
Dependencies
Example
History
| Last changed by/on | SAP | 20050411 |
| SAP Release Created in | 600 |
