EREC_S_API_DOCUMENT_HISTORY SAP (Assessment Document History from E-Recruiting) Structure details
Description: Assessment Document History from E-Recruiting
Related tables to EREC_S_API_DOCUMENT_HISTORY
Access table EREC_S_API_DOCUMENT_HISTORY
Structure field list including key, data, relationships and ABAP select examples
EREC_S_API_DOCUMENT_HISTORY 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 "Assessment Document History from E-Recruiting" 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_EREC_S_API_DOCUMENT_HISTORY TYPE EREC_S_API_DOCUMENT_HISTORY.
The EREC_S_API_DOCUMENT_HISTORY table consists of various fields, each holding specific information or linking keys about Assessment Document History from E-Recruiting data available in SAP. These include ACT_TYPE (Not More Closely Defined Area, Possibly Used for Patchlevels), ACT_GUID (Character field, length 32), STATUS (EREC Requisition Status), DUE_DATE (Application End Date).. 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: Can Be Enhanced (Deep)
SAP EREC_S_API_DOCUMENT_HISTORY 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 |
ACT_TYPE | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
ACT_GUID | Character field, length 32 | CHAR32 | CHAR | 32 | CHAR32 | ||||
STATUS | EREC Requisition Status | EREC_REQUISITION_STATUS | NUMC | 1 | NUMC01 | ||||
DUE_DATE | Application End Date | EREC_APPLICATION_END_DATE | DATS | 8 | DATS08 | ||||
RES_SCLAS | Version Number Component | CHAR2 | CHAR | 2 | CHAR2 | ||||
RES_SOBID | Char45 | CHAR45 | CHAR | 45 | CHAR45 | ||||
NOTE | Numeric field: Length 6 | NUM06 | NUMC | 6 | NUM06 | ||||
ACT_CAT | Two digit number | NUMC2 | NUMC | 2 | NUMC2 | ||||
DATE_EXECUTED | Application End Date | EREC_APPLICATION_END_DATE | DATS | 8 | DATS08 | ||||
EXECUTER | Character Field of Length 12 | CHAR12 | CHAR | 12 | CHAR12 | ||||
ACT_PROC | Two digit number | NUMC2 | NUMC | 2 | NUMC2 | ||||
QA_TPL_OBJID | Numeric field length 8 | NUM08 | NUMC | 8 | NUM08 | ||||
QA_DOC_GUID | Character field, length 32 | CHAR32 | CHAR | 32 | CHAR32 | ||||
QA_VISIBLE | Character Field Length 1 | CHAR01 | CHAR | 1 | CHAR1 | ||||
ACT_TYPE_TXT | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
STATUS_TXT | Field of length 60 | CHAR060 | CHAR | 60 | CHAR60 | ||||
ACT_CAT_TXT | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
RES_NAME | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
ACT_PROC_TXT | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
EXECUTER_NAME | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
ACT_PROC_SEQ_NR | Numc3, internal use | NUMC3 | NUMC | 3 | NUMC3 | ||||
CDCY_HROBJECT | 0 | ||||||||
PLVAR | Plan Version | PLVAR | CHAR | 2 | Assigned to domain | PLVAR | POP | ||
OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
OBJID | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
CDCY_CREATE_DATE | Date in CHAR format | DATE8 | DATS | 8 | DATE | ||||
CDCY_STATUS | Numeric 1-character | NUM1 | NUMC | 1 | NUM1 | ||||
CDCY_STATUS_TXT | Field of length 60 | CHAR060 | CHAR | 60 | CHAR60 | ||||
REQ_HEADER | Char 80 | CHAR80 | CHAR | 80 | CHAR80 | ||||
REQ_HROBJECT | 0 | ||||||||
PLVAR | Plan Version | PLVAR | CHAR | 2 | Assigned to domain | PLVAR | POP | ||
OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
OBJID | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
CAND_NAME | Char 80 | CHAR80 | CHAR | 80 | CHAR80 | ||||
CAND_HROBJECT | 0 | ||||||||
PLVAR | Plan Version | PLVAR | CHAR | 2 | Assigned to domain | PLVAR | POP | ||
OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
OBJID | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
APPL_HROBJECT | 0 | ||||||||
PLVAR | Plan Version | PLVAR | CHAR | 2 | Assigned to domain | PLVAR | POP | ||
OTYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
OBJID | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
APPL_DATE | Date in CHAR format | DATE8 | DATS | 8 | DATE | ||||
IS_EMPLOYEE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
EMPLOYEEID | Numeric 8-figures | NUMC08 | NUMC | 8 | NUMC08 | ||||
IS_APPLICATION | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
IS_ORIG_CDCY | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
QA_TPL_TITLE | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 |
Key field | Non-key field |
How do I retrieve data from SAP structure EREC_S_API_DOCUMENT_HISTORY using ABAP code?
As EREC_S_API_DOCUMENT_HISTORY 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 EREC_S_API_DOCUMENT_HISTORY as there is no data to select.How to access SAP table EREC_S_API_DOCUMENT_HISTORY
Within an ECC or HANA version of SAP you can also view further information about EREC_S_API_DOCUMENT_HISTORY 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