PDBD1 SAP (Shift Planning: Screen Fields for Requirements Definition) Structure details
Description: Shift Planning: Screen Fields for Requirements Definition
Structure field list including key, data, relationships and ABAP select examples
PDBD1 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 "Shift Planning: Screen Fields for Requirements Definition" 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_PDBD1 TYPE PDBD1.
The PDBD1 table consists of various fields, each holding specific information or linking keys about Shift Planning: Screen Fields for Requirements Definition data available in SAP. These include ENTRY (Current entry), ENTRIES (Number of entries), BEGDA (Start Date), ENDDA (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: Cannot Be Enhanced
SAP PDBD1 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 |
| FRAME1 | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| ENTRY | Current entry | PD_ENTRY | DEC | 3 | DEC3 | ||||
| ENTRIES | Number of entries | PD_ENTRIES | DEC | 3 | DEC3 | ||||
| BEGDA | Start Date | BEGDATUM | DATS | 8 | DATUM | BEG | |||
| ENDDA | End Date | ENDDATUM | DATS | 8 | DATUM | END | |||
| RCASC | Expand requirements entry to include shift abbreviation/job | RCASC | CHAR | 1 | CHAR1_X |
| Key field | Non-key field |
How do I retrieve data from SAP structure PDBD1 using ABAP code?
As PDBD1 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 PDBD1 as there is no data to select.How to access SAP table PDBD1
Within an ECC or HANA version of SAP you can also view further information about PDBD1 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