PBET SAP (Table for splitting data for ind. reequirements) Structure details
Description: Table for splitting data for ind. reequirements
Structure field list including key, data, relationships and ABAP select examples
PBET 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 "Table for splitting data for ind. reequirements" 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_PBET TYPE PBET.
The PBET table consists of various fields, each holding specific information or linking keys about Table for splitting data for ind. reequirements data available in SAP. These include PDATU (Delivery/order finish date), WDATU (Reqstd date), PLNMG (Planned quantity), ENTMG (Withdrawal quantity).. 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 PBET 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 |
| POSNR | Requirements plan item | BEDPP | NUMC | 6 | NUM06 | BDP | |||
| PDATU | Delivery/order finish date | DAT01 | DATS | 8 | DATUM | ||||
| WDATU | Reqstd date | WDATU | DATS | 8 | DATUM | ||||
| PLNMG | Planned quantity | PLNMG | QUAN | 13(3) | MENG13 | ||||
| ENTMG | Withdrawal quantity | ENTMG | QUAN | 13(3) | MENG13 | ||||
| UPLMG | Originally planned quantity | UPLMG | QUAN | 13(3) | MENG13 | ||||
| ENTLI | Date type (day, week, month, interval) | PRGRS | CHAR | 1 | PRGRS | ||||
| ENTLU | Period indicator (day, week, month, posting period) | ENTLU | CHAR | 1 | Assigned to domain | PRGBZ | |||
| PERXX | Planning period | PERXX | CHAR | 6 | PERIOD | ||||
| ZUOKR | Criterion for allocation | DZUOKR | CHAR | 16 | ZUOKR | ||||
| UPDKZ | Update indicator | UPDKZ_D | CHAR | 1 | UPDKZ | ||||
| LOEKZ | Deletion indicator | LOEIN | CHAR | 1 | CHAR1 | ||||
| DBVKZ | Indicator: reqmts date already exists in database | DBVKZ | CHAR | 1 | X | ||||
| FIXMG | Planned quantity | PLNMG | QUAN | 13(3) | MENG13 | ||||
| SPRAS | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| DBMNG | Planned quantity in the data base | DBMNG | QUAN | 13(3) | MENG13 | ||||
| SERNR | BOM explosion number | SERNR | CHAR | 8 | Assigned to domain | SERNR | |||
| VERID | Production Version | VERID | CHAR | 4 | Assigned to domain | VERID | VER | ||
| ERFME | Unit of Entry | ERFME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| ERFMG | Quantity in Unit of Entry | ERFMG | QUAN | 13(3) | MENG13 | ||||
| UMREZ | Numerator for Conversion to Base Units of Measure | UMREZ | DEC | 5 | UMBSZ | ||||
| UMREN | Denominator for conversion to base units of measure | UMREN | DEC | 5 | UMBSN | ||||
| MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| TXTET | Indicator: long text exists | TXTKZ | CHAR | 1 | FLAG | ||||
| TXTVB | Indicator: long text exists | TXTKZ | CHAR | 1 | FLAG | ||||
| LAEDA | Date of Last Change | LAEDA | DATS | 8 | DATUM | ||||
| UZEIT | Time | UZEIT | TIMS | 6 | UZEIT | ||||
| AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| HISET | Processing a plan with or without history | HISET | CHAR | 1 | HISPO | ||||
| AUFTV | Split already exists | AUFTV | CHAR | 1 | CHAR1 | ||||
| CUOBA | Configuration (internal object number) | CUOBJ | NUMC | 18 | CUOBJ | CUX | |||
| CUOBJ | Configuration (internal object number) | CUOBJ | NUMC | 18 | CUOBJ | CUX | |||
| WERTP | Independent requirements value per period | WERTPB | CURR | 13(2) | WERT | ||||
| UPDPA | UPDKZ Period split | UPDPA | CHAR | 1 | UPDKZ | ||||
| UPDKO | UPDKZ Configuration | UPDKO | CHAR | 1 | UPDKZ | ||||
| STPKT | Supporting point for independent requirements | STPKT | CHAR | 1 | CHAR1 | ||||
| VRMNG | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | ||||
| DYVKZ | Indicator: reqmts date already exists in database | DBVKZ | CHAR | 1 | X | ||||
| SHVIS | Schedule line visible | SHVIS | CHAR | 1 | CHAR1 | ||||
| TECHS | Parameter Variant/Standard Variant | TECHS | CHAR | 12 | TECHS | ||||
| OLDTECHS | Parameter Variant/Standard Variant | TECHS | CHAR | 12 | TECHS | ||||
| DATPO | Date postponed | DATPO | CHAR | 1 | CHAR1 | ||||
| DBEMG | Withdrawal quantity | ENTMG | QUAN | 13(3) | MENG13 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PBET using ABAP code?
As PBET 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 PBET as there is no data to select.How to access SAP table PBET
Within an ECC or HANA version of SAP you can also view further information about PBET 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