PBEDOUT SAP (Output Structure Details Planned Independent Requirements) Structure details
Description: Output Structure Details Planned Independent Requirements
Structure field list including key, data, relationships and ABAP select examples
PBEDOUT 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 "Output Structure Details Planned Independent Requirements" 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_PBEDOUT TYPE PBEDOUT.
The PBEDOUT table consists of various fields, each holding specific information or linking keys about Output Structure Details Planned Independent Requirements data available in SAP. These include FDUMM (Not More Closely Defined Area, Possibly Used for Patchlevels), ENTLU (Period indicator (day, week, month, posting period)), EDATU (Requirements date), PLNMG (Planned 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 PBEDOUT 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 |
| BDZEI | Independent requirements pointer | BDZEI | NUMC | 12 | Assigned to domain | BDZEI | |||
| FDUMM | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
| ENTLU | Period indicator (day, week, month, posting period) | ENTLU | CHAR | 1 | Assigned to domain | PRGBZ | |||
| EDATU | Requirements date | EDATV | CHAR | 10 | CHAR10 | ||||
| PLNMG | Planned quantity | PLNMG | QUAN | 13(3) | MENG13 | ||||
| MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| FDUM2 | Version Number Component | CHAR2 | CHAR | 2 | CHAR2 | ||||
| MSGTY | Message Type | MSGTY | CHAR | 1 | MSGAR | ||||
| MSGID | Message identification | MSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
| MSGNR | System Message Number | MSGNO | CHAR | 3 | Assigned to domain | MSGNR | |||
| MSGV1 | Message variable 01 | MSGV1 | CHAR | 50 | CHAR50 | ||||
| MSGV2 | Message variable 02 | MSGV2 | CHAR | 50 | CHAR50 | ||||
| MSGV3 | Message variable 03 | MSGV3 | CHAR | 50 | CHAR50 | ||||
| MSGTX | Message Text | MSGTXT | CHAR | 100 | TEXT100 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PBEDOUT using ABAP code?
As PBEDOUT 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 PBEDOUT as there is no data to select.How to access SAP table PBEDOUT
Within an ECC or HANA version of SAP you can also view further information about PBEDOUT 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