BPHEADDYN SAP (Budget Entry Document Header Screen) Structure details
Description: Budget Entry Document Header Screen
Structure field list including key, data, relationships and ABAP select examples
BPHEADDYN 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 "Budget Entry Document Header Screen" 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_BPHEADDYN TYPE BPHEADDYN.
The BPHEADDYN table consists of various fields, each holding specific information or linking keys about Budget Entry Document Header Screen data available in SAP. These include BUPER (Posting period), BLDAT (Document Date), EJAHR (Receiver year), E_GEBER (Receiver fund).. 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)
SAP BPHEADDYN 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 |
| BUDAT | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
| BUPER | Posting period | POPER | NUMC | 3 | POPER | POPR | |||
| BLDAT | Document Date | BP_BLDAT | DATS | 8 | DATUM | ||||
| EJAHR | Receiver year | BP_U_EJAHR | NUMC | 4 | GJAHR | GJAHR | GJV | ||
| E_GEBER | Receiver fund | BP_E_GEBER | CHAR | 10 | Assigned to domain | BP_GEBER | FIE | ||
| E_GNJHR | FM_BK_E_GJ | NUMC | 4 | GJAHR | GJAHR | ||||
| E_PERIO | Receiver period: Budgeting/planning | BP_E_PERIO | NUMC | 3 | POPER | BPE | |||
| FCODE | Budgeting/planning function | BP_FCODE | CHAR | 6 | BP_FCODE | ||||
| FICTR | Funds Center | FM_FICTR | CHAR | 16 | Assigned to domain | FISTL | FIS | ||
| FIKRS | Financial Management Area | FIKRS | CHAR | 4 | Assigned to domain | FIKRS | FIK | ||
| FIPOS | Commitment Item | FIPOS | CHAR | 14 | Assigned to domain | FIPOS | FIP | ||
| FIPEX | Commitment Item | FM_FIPEX | CHAR | 24 | Assigned to domain | FM_FIPEX | FPS | ||
| SJAHR | Sender year | BP_U_SJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| SUBVO | Budget Subtype | BP_SUBVO | CHAR | 4 | Assigned to domain | BP_SUBVO | |||
| S_GEBER | Sender fund | BP_S_GEBER | CHAR | 10 | Assigned to domain | BP_GEBER | FIC | ||
| S_GNJHR | FM_BK_S_GJ | NUMC | 4 | GJAHR | GJAHR | ||||
| S_PERIO | Sender period: Budgeting/planning | BP_S_PERIO | NUMC | 3 | POPER | VPE | |||
| TDNAME | Text Name | BP_TDNAM | CHAR | 32 | CHAR32 | ||||
| TECH | Budgeting/Planning Technique | BP_TECH | CHAR | 1 | BP_TECH | ||||
| TEXT | Document Header Text | BP_BLTXT | CHAR | 50 | TEXT50 | ||||
| VADAT | Planning/budgeting value date | BD_VADAT | DATS | 8 | DATUM | ||||
| VALKEY | Validation Key Budget/Planning | BP_VALKEY | CHAR | 10 | BP_VALKEY | ||||
| VERANT | Person Responsible for Planning/Budgeting | BP_VERANT | CHAR | 20 | VERAB | BPV | |||
| RPUBLAW | Public Law Cited | FM_PUBLAW | CHAR | 20 | FM_PUBLAW | ||||
| RLEGIS | Type of Legislation | FM_LEGIS | CHAR | 1 | FM_LEGIS | ||||
| RCOHORT | Reporting Year for Cohort | FM_COHORT | CHAR | 4 | FM_COHORT | ||||
| DOCTYPE | Budget entry document type | BUED_DOCTYPE | CHAR | 4 | Assigned to domain | BUED_DOCTYPE | DOTY | ||
| VERSN | Planning/budgeting version | BP_VERSION | CHAR | 3 | Assigned to domain | ALPHA | BP_VERSION | BP2 | |
| VORGA | Budget Type Budgeting/Planning | BP_VORGANG | CHAR | 4 | Assigned to domain | ACTIVITY | |||
| WGES | Overall values too | BP_WGES | CHAR | 1 | X | ||||
| XPB | Payment budget | BP_PB | CHAR | 1 | X | BZA | |||
| XCB | Commitment budget | BP_CB | CHAR | 1 | X | BVE |
| Key field | Non-key field |
How do I retrieve data from SAP structure BPHEADDYN using ABAP code?
As BPHEADDYN 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 BPHEADDYN as there is no data to select.How to access SAP table BPHEADDYN
Within an ECC or HANA version of SAP you can also view further information about BPHEADDYN 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