PPTQ3 SAP (HR-PT: Employment Survey in Structured Sector - TemSe) Structure details
Description: HR-PT: Employment Survey in Structured Sector - TemSe
Structure field list including key, data, relationships and ABAP select examples
PPTQ3 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-PT: Employment Survey in Structured Sector - TemSe" 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_PPTQ3 TYPE PPTQ3.
The PPTQ3 table consists of various fields, each holding specific information or linking keys about HR-PT: Employment Survey in Structured Sector - TemSe data available in SAP. These include BTRTL (Personnel Subarea), PERNR (Personnel Number), GESCH (Gender Key), AGE (3-Byte field).. 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 PPTQ3 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 |
| WERKS | Personnel Area | PERSA | CHAR | 4 | Assigned to domain | PERSA | PBR | ||
| BTRTL | Personnel Subarea | BTRTL_001P | CHAR | 4 | Assigned to domain | BTRTL | |||
| PERNR | Personnel Number | P_PERNR | NUMC | 8 | PERNR | ||||
| GESCH | Gender Key | GESCH | CHAR | 1 | GESCH | ||||
| AGE | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| FL_AGE | St - Flag if employee is under certain age | PPT_STFAG | CHAR | 1 | CHAR1 | ||||
| PRSIT | Professional situation | PPT_PRSIT | NUMC | 1 | PPT_PRSIT | ||||
| STGSI | St - Grouping for situation in profession | PPT_STGSI | CHAR | 3 | CHAR3 | ||||
| STCTTYP | Contract type | PPT_CTTYP | CHAR | 1 | Assigned to domain | PPT_CTTYP | |||
| STGCTYP | St - Grouping for contract type | PPT_STGCT | CHAR | 3 | CHAR3 | ||||
| FL_PART | St - Flag for part-time contracts | PPT_STFPT | CHAR | 1 | CHAR1 | ||||
| FL_SELFE | St - Flag for self-employed | PPT_STSEE | CHAR | 1 | CHAR1 | ||||
| PRCNP | Professional classification (CNP or CPP) | PPT_PRCNP | CHAR | 6 | Assigned to domain | PPT_PRCNP | |||
| STCNP | St - Group of professions | PPT_STCNP | CHAR | 2 | CHAR2 | ||||
| FL_BEGIN | St - Flag present at start of period | PPT_STFBG | CHAR | 1 | CHAR1 | ||||
| FL_END | St - Flag present end of period | PPT_STFED | CHAR | 1 | CHAR1 | ||||
| FL_ENTRY | St - Flag incoming employee | PPT_STFHR | CHAR | 1 | CHAR1 | ||||
| FL_FIRE | St - Flag outgoing employee | PPT_STFFR | CHAR | 1 | CHAR1 | ||||
| FL_TRNSF | St - Flag for establishment transfer | PPT_STFTR | CHAR | 1 | CHAR1 | ||||
| STREASN | Reason for action | PPT_REASN | CHAR | 2 | Assigned to domain | PPT_REASN | |||
| FL_MCON | St - Flag for change from fixed term contract to perm.contr. | PPT_STFMC | CHAR | 1 | CHAR1 | ||||
| FL_HRS | St - Hours flag | PPT_STFHS | CHAR | 1 | CHAR1 | ||||
| WK_HRS | Character Field with Length 5 | CHAR05 | CHAR | 5 | CHAR005 | ||||
| OV_HRS | Character Field with Length 5 | CHAR05 | CHAR | 5 | CHAR005 | ||||
| VA_HRS | Character Field with Length 5 | CHAR05 | CHAR | 5 | CHAR005 | ||||
| IL_HRS | Character Field with Length 5 | CHAR05 | CHAR | 5 | CHAR005 | ||||
| AC_HRS | Character Field with Length 5 | CHAR05 | CHAR | 5 | CHAR005 | ||||
| FA_HRS | Character Field with Length 5 | CHAR05 | CHAR | 5 | CHAR005 | ||||
| TR_HRS | Character Field with Length 5 | CHAR05 | CHAR | 5 | CHAR005 | ||||
| OT_HRS | Character Field with Length 5 | CHAR05 | CHAR | 5 | CHAR005 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PPTQ3 using ABAP code?
As PPTQ3 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 PPTQ3 as there is no data to select.How to access SAP table PPTQ3
Within an ECC or HANA version of SAP you can also view further information about PPTQ3 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