BAPIHR1000 SAP (HR: Infotype 1000 Object/Description) Structure details
Description: HR: Infotype 1000 Object/Description
Structure field list including key, data, relationships and ABAP select examples
BAPIHR1000 is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "HR: Infotype 1000 Object/Description" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_BAPIHR1000 TYPE BAPIHR1000.
The BAPIHR1000 table consists of various fields, each holding specific information or linking keys about HR: Infotype 1000 Object/Description data available in SAP. These include CLIENT (Client), PLAN_VER (Plan Version), OBJ_TYPE (Object Type), OBJ_ID (Object ID).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified
SAP BAPIHR1000 structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
CLIENT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
PLAN_VER | Plan Version | PLVAR | CHAR | 2 | T778P | PLVAR | POP | ||
OBJ_TYPE | Object Type | OTYPE | CHAR | 2 | T778O | OTYPE | POT | ||
OBJ_ID | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
INFOTYPE | Infotype | INFOTYP | CHAR | 4 | T778T | INFOTYP | HRBAS00INFTY | ||
SUBTYPE | Subtype | SUBTYP | CHAR | 4 | T778U | SUBTYP | |||
PL_STATUS | Planning Status | ISTAT_D | CHAR | 1 | T778S | ISTAT | PST | ||
PRIORITY | Priority | PRIOX | CHAR | 2 | CHAR2 | ||||
FROM_DATE | Start Date | BEGDATUM | DATS | 8 | DATUM | BEG | |||
TO_DATE | End Date | ENDDATUM | DATS | 8 | DATUM | END | |||
LANGU | Language Key | LANGU | LANG | 1 | T002 | ISOLA | SPRAS | ||
DUMMY_9 | Dummy Function With Length 9 | DUMMY_9 | CHAR | 9 | CHAR9 | ||||
IT_REC_NO | Number of Infotype Record with Same Key | SEQNR | NUMC | 3 | NUM03 | ||||
CHANGED_ON | Changed on | AEDTM | DATS | 8 | DATUM | ||||
CHANGED_BY | User Name | USRNAME | CHAR | 12 | CHAR12 | ||||
REASON | Reason | REASN | CHAR | 2 | CHAR2 | ||||
HIST_FLAG | Historical Record Flag | HISTO | CHAR | 1 | CHAR1 | ||||
IT_TXT_MOD | Text Module for Infotype | ITXNR | NUMC | 8 | NUM08 | ||||
OBJ_ABB | Object Abbreviation | SHORT_D | CHAR | 12 | TEXT12 | ||||
OBJ_NAME | Object Name | STEXT | CHAR | 40 | TEXT40 | ||||
DELIM_DATE | Delimitation date | GDATE | DATS | 8 | DATUM | ||||
LANGU_ISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO |
Key field | Non-key field |
How do I retrieve data from SAP structure BAPIHR1000 using ABAP code?
As BAPIHR1000 is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on BAPIHR1000 as there is no data to select.How to access SAP table BAPIHR1000
Within an ECC or HANA version of SAP you can also view further information about BAPIHR1000 and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects