Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-HR (Application Component) Cross-Application Objects in HR⤷
BP (Package) Cross-Application Objects in HR
Basic Data
| Data Element | OBJPS |
| Short Description | Object Identification |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OBJPS | |
| 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 | OPS | |
| Default Component name | OBJECT_IDENTIFICATION | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Object ID |
| Medium | 12 | Object ID |
| Long | 20 | Object ID |
| Heading | 5 | ObjID |
Documentation
Definition
The object identification (object ID) is used to make a distinction between data records with the same infotype, subtype, lock indicator, start date, and end date.
Examples
- The Sequential number field in infotypes 0026 Company Insurance and 0045 Company Loans.
- The Child number field in infotype 0021 Family/Related Person.
Supplementary Documentation - OBJPS 0001
Use
In the Leave Entitlement infotype, this field is used to store different leave records for the calendar record.
You can access each of these records by entering the 'leave year' and 'object ID' combination. You must specify this data combination, for example, when you enter leave compensation in the Leave Compensation infotype (0083).
The object ID is assigned by the system and cannot be overwritten.
Example
Calendar year Object ID Leave type
1995 01 01 02 ...
1995 02 01 05 ...
Dependencies
Supplementary Documentation - OBJPS 0002
Use
The sequential number links the absence records you have entered on this screen.
Procedure
Example
Dependencies
Supplementary Documentation - OBJPS 0003
Use
This number establishes a link between the absence records you enter on this screen and the Military Service records. Each absence record has the sequential number of the Military Service record which contains the absence data.
Procedure
Example
Dependencies
Supplementary Documentation - OBJPS 0004
Use
Key used to read the child allowance data (last name, first name, birthdate) from infotype 0021.
Procedure
Example
Dependencies
Supplementary Documentation - OBJPS 0005
Use
In the Leave entitlement infotype (0005), this field is used to store different leave records for one calendar year.
Each of these leave records can be accessed by entering the leave year and object ID combination; this is used in the Leave compensation infotype (0083).
If you do not specify an object ID, the default value '01' is automatically used.
Procedure
Examples
Example: Calendar year Object Id Leave type
1995 01 01 02 ....
1995 02 01 05 ....
Dependencies
Supplementary Documentation - OBJPS 0006
Use
Germany only
Supplementary Documentation - OBJPS 0007
Use
Germany only
Supplementary Documentation - OBJPS 0008
Use
Germany only
Supplementary Documentation - OBJPS 0009
Use
Germany only
Supplementary Documentation - OBJPS 0010
Use
The object ID is a sequential number which defines order types. Each number identifies an order type.
Supplementary Documentation - OBJPS 0011
Use
The sequence number allows you to create several adjustments for one garnishment.
If you use the menu in an adjustment, the system displays different screens which depend on the Reason you set. Please note that the same infotype is displayed for all reasons.
The sequence number covers all reasons and not only specific ones.
Supplementary Documentation - OBJPS 0012
Use
This number identifies a saving in the same property accumulation saving type that exists in the same saving type. If more than one saving in the same saving type exists, all the savings in the same saving type have different numbers.
Procedure
When a new saving is entered, automatic numbering assigns a new incremental number to a new accumulation saving. It distinguishes one saving and the other saving.
Examples
- When a saving of property accumulation is entered for the first time, record will be created with a number automatically assigned as below.
Property accumulation saving type: COMMON PROP.ACC. SAV.
Object ID: 01
- When another saving in the same type is entered for the second time, record will be created with an incremented number automatically assigned.
Property accumulation saving type: COMMON PROP.ACC. SAV.
Object ID: 02
- When a new PROPERTY ACC. SAV. FOR HOUSING, another saving type, is entered for the first time, another stream of numbering assigns the number automatically.
Property accumulation saving type: PROPERTY ACC. SAV. FOR HOUSING
Object ID: 01
Supplementary Documentation - OBJPS 0013
Use
This number identifies a member of the family among other family members who exists in the same member type. If more than one member in the same member type exists, all the members in the same member type have different numbers.
Procedure
When new family is entered, automatic numbering assigns a new incremental number to a new person. It distinguishes one member of family and the other member.
Examples
- When a child is entered for the first time, record will be created with a number automatically assigned as below.
Member type: Child
Object ID: 01
- When another child in the same type is entered for the second time, record will be created with the incremented number automatically assigned
Member type: Child
Object ID: 02
- When a new related person, another member type, is entered for the first time, another stream of numbering assigns the number automatically.
Member type: Related persons
Object ID: 01
Dependencies
Some family type requires Object ID and others don't require Object ID. Determining which family type requires Object ID is done through customizing setup in Implementation Guide: Subtype Characteristics for Family/Related Person under Personnel Administration.
Supplementary Documentation - OBJPS 0014
Use
This number identifies a contract in the same insurance type that exists in the same insurance type. If more than one contract in the same insurance type exists, all the contracts in the same insurance type have different numbers.
Procedure
When new contract is entered, automatic numbering assigns a new incremental number to a new insurance contract. It distinguishes one contract and the other contract.
Examples
- When a contract of insurance is entered for the first time, record will be created with a number automatically assigned as below.
Insurance type: common insurance through company
Object ID: 01
- When another contract in the same type is entered for the second time, record will be created with an incremented number automatically assigned
Insurance type: common insurance through company
Object ID: 02
- When a new casualty insurance through company, another insurance type, is entered for the first time, another stream of numbering assigns the number automatically.
Insurance type: casualty insurance through company
Object ID: 01
Supplementary Documentation - OBJPS 0063
Procedure
The system automatically assigns the object ID. This field is therefore not in the input mode.
Object IDs are assigned in the same order as infotype records are created.
Examples
Dependencies
Supplementary Documentation - OBJPS 0195
In Infotype 0195, this field contains the sequence number assigned to every garnishment order within a garnishment document. Each new order is assigned a new sequence number within the document, and sequence numbers rise in succession.
In essence, this field functions as a counter for different garnishment orders under the same garnishment document.
History
| Last changed by/on | SAP | 19980909 |
| SAP Release Created in |
