PAD940_QUE SAP (General Structure for Additional Data in Query 940) Structure details
Description: General Structure for Additional Data in Query 940
Structure field list including key, data, relationships and ABAP select examples
PAD940_QUE 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 "General Structure for Additional Data in Query 940" 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_PAD940_QUE TYPE PAD940_QUE.
The PAD940_QUE table consists of various fields, each holding specific information or linking keys about General Structure for Additional Data in Query 940 data available in SAP. These include PLVAR (Plan Version), OTYPE (Object Type), OBJID (Object ID), IT0_INFTY (Infotype).. 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 (character-type or numeric)
SAP PAD940_QUE 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 |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| 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 | |||
| IT0_INFTY | Infotype | INFOTYP | CHAR | 4 | INFOTYP | HRBAS00INFTY | |||
| IT0_SUBTY | Subtype | SUBTYP | CHAR | 4 | Assigned to domain | SUBTYP | |||
| IT0_ISTAT | Planning Status | ISTAT_D | CHAR | 1 | Assigned to domain | ISTAT | PST | ||
| IT0_PRIOX | Priority | PRIOX | CHAR | 2 | CHAR2 | ||||
| BEGDA | Start Date | BEGDATUM | DATS | 8 | DATUM | BEG | |||
| ENDDA | End Date | ENDDATUM | DATS | 8 | DATUM | END | |||
| IT0_LANGU | Language Key | LANGU | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
| IT0_SEQNR | Number of Infotype Record with Same Key | SEQNR | NUMC | 3 | NUM03 | ||||
| IT0_AEDTM | Changed on | AEDTM | DATS | 8 | DATUM | ||||
| IT0_UNAME | User Name | USRNAME | CHAR | 12 | CHAR12 | ||||
| IT0_REASN | Reason | REASN | CHAR | 2 | CHAR2 | ||||
| IT0_HISTO | Historical Record Flag | HISTO | CHAR | 1 | CHAR1 | ||||
| IT0_ITXNR | Text Module for Infotype | ITXNR | NUMC | 8 | NUM08 | ||||
| SHORT | Object Abbreviation | SHORT_D | CHAR | 12 | TEXT12 | ||||
| STEXT | Object Name | STEXT | CHAR | 40 | TEXT40 | ||||
| GDATE | Delimitation date | GDATE | DATS | 8 | DATUM | ||||
| IT1_RSIGN | Relationship Specification | RSIGN | CHAR | 1 | RSIGN | ||||
| IT1_RELAT | Relationship Between Objects | RELAT | CHAR | 3 | Assigned to domain | RELAT | |||
| IT1_ISTAT | Planning Status | ISTAT_D | CHAR | 1 | Assigned to domain | ISTAT | PST | ||
| IT1_PRIOX | Priority | PRIOX | CHAR | 2 | CHAR2 | ||||
| IT1_BEGDA | Start Date | BEGDATUM | DATS | 8 | DATUM | BEG | |||
| IT1_ENDDA | End Date | ENDDATUM | DATS | 8 | DATUM | END | |||
| IT1_AEDTM | Changed on | AEDTM | DATS | 8 | DATUM | ||||
| IT1_UNAME | User Name | USRNAME | CHAR | 12 | CHAR12 | ||||
| IT1_REASN | Reason | REASN | CHAR | 2 | CHAR2 | ||||
| IT1_HISTO | Historical Record Flag | HISTO | CHAR | 1 | CHAR1 | ||||
| IT1_ITXNR | Text Module for Infotype | ITXNR | NUMC | 8 | NUM08 | ||||
| IT1_SCLAS | Type of Related Object | SCLAS | CHAR | 2 | Assigned to domain | OTYPE | |||
| IT1_SOBID | ID of Related Object | SOBID | CHAR | 45 | CHAR45 | ||||
| IT1_PROZT | Weighting Percentage | PROZT | DEC | 5(2) | DEC3_2 | ||||
| .INCLU-_X | 0 | ||||||||
| WERKS_X | Personnel Area | PERSA | CHAR | 4 | T500P | PERSA | PBR | ||
| BTRTL_X | Personnel Subarea | BTRTL | CHAR | 4 | T001P | BTRTL | PBS | ||
| NBPER_X | Total of Attendees | HRTNM_NBPER | NUMC | 6 | NUMC6 | ||||
| NBWOM_X | Number of Women | HRTNM_NBWOM | NUMC | 6 | NUMC6 | ||||
| FTEGC_X | Training Employee Group | HRTNM_TEGRC | CHAR | 4 | T77TNM_TE | CHAR4 | |||
| SIGN_X | Type of SIGN component in row type of a Ranges type | DDSIGN | CHAR | 1 | DDSIGN | ||||
| OPTI_X | Type of OPTION component in row type of a Ranges type | DDOPTION | CHAR | 2 | DDOPTION | ||||
| AGE_MIN_X | Training Needs Minimum Age | HRTNM_MIN_AGE | NUMC | 3 | NUMC3 | ||||
| AGE_MAX_X | Training Needs Maximum Age | HRTNM_MAX_AGE | NUMC | 3 | NUMC3 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PAD940_QUE using ABAP code?
As PAD940_QUE 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 PAD940_QUE as there is no data to select.How to access SAP table PAD940_QUE
Within an ECC or HANA version of SAP you can also view further information about PAD940_QUE 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