P1500 SAP (Infotype 1500: Budget Administration) Structure details
Description: Infotype 1500: Budget Administration
Structure field list including key, data, relationships and ABAP select examples
P1500 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 "Infotype 1500: Budget Administration" 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_P1500 TYPE P1500.
The P1500 table consists of various fields, each holding specific information or linking keys about Infotype 1500: Budget Administration data available in SAP. These include MANDT (Client), PLVAR (Plan Version), OTYPE (Object Type), OBJID (Object ID).. 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 P1500 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 |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| PLVAR | Plan Version | PLVAR | CHAR | 2 | T778P | PLVAR | POP | ||
| OTYPE | Object Type | OTYPE | CHAR | 2 | T778O | OTYPE | POT | ||
| OBJID | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
| INFTY | Infotype | INFOTYP | CHAR | 4 | T778T | INFOTYP | HRBAS00INFTY | ||
| SUBTY | Subtype | SUBTYP | CHAR | 4 | T778U | SUBTYP | |||
| ISTAT | Planning Status | ISTAT_D | CHAR | 1 | T778S | ISTAT | PST | ||
| PRIOX | Priority | PRIOX | CHAR | 2 | CHAR2 | ||||
| BEGDA | Start Date | BEGDATUM | DATS | 8 | DATUM | BEG | |||
| ENDDA | End Date | ENDDATUM | DATS | 8 | DATUM | END | |||
| VARYF | Variation Field for File PLOG | VARYF | CHAR | 10 | CHAR10 | ||||
| SEQNR | Number of Infotype Record with Same Key | SEQNR | NUMC | 3 | NUM03 | ||||
| AEDTM | Changed on | AEDTM | DATS | 8 | DATUM | ||||
| UNAME | User Name | USRNAME | CHAR | 12 | CHAR12 | ||||
| REASN | Reason | REASN | CHAR | 2 | CHAR2 | ||||
| HISTO | Historical Record Flag | HISTO | CHAR | 1 | CHAR1 | ||||
| ITXNR | Text Module for Infotype | ITXNR | NUMC | 8 | NUM08 | ||||
| BUTGR | Section of Overall Budget | BUTGR | CHAR | 2 | T7PM0 | BUTGR | |||
| BUTYP | Budget structure element type | BUTYP | CHAR | 4 | T7PM3 | PM_BUTYP | PBU | ||
| BSTAT | Budget status | PMBSTAT | CHAR | 1 | T7PMQ | CHAR1 | |||
| NOFIN | 'No Reference to Financial Year' flag | NOFIN | CHAR | 1 | CHAR1 | ||||
| AKTE | Record Number | AKTE | CHAR | 15 | TEXT15 | ||||
| KOMM | Reason | KOMM | CHAR | 40 | TEXT40 | ||||
| EXT_NUMBER | External number | EXT_NUM | CHAR | 20 | TEXT20 | ||||
| EXT_TEXT | External name | EXT_TEXT | CHAR | 45 | TEXT45 | ||||
| KACTIVE | 'Allocatable' Flag | KACTIV | CHAR | 1 | FLAG | ||||
| FINYR | Financial Year | FINYR | CHAR | 10 | T7PM9 | CHAR10 | PFY | ||
| GENERATED | 'Generated object' indicator | KGENE | CHAR | 1 | FLAG | ||||
| KADD | 'Added During Financial Year' Flag | KADD | CHAR | 1 | FLAG | ||||
| AUSART | Expenditure type | AUSART | CHAR | 4 | T7PM6 | AUSART | |||
| FYEAR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| LIMIT_BEG | Start of validity period | LIMIT_BEG | DATS | 8 | DATUM | ||||
| LIMIT_END | End of validity period | LIMIT_END | DATS | 8 | DATUM | ||||
| EXT_RULE | 'External Rules Carried Forward' Flag | KEXT_RULE | CHAR | 1 | FLAG | ||||
| EXT_AKT | Indicator 'Carry forward budget update' | KEXT_AKT | CHAR | 1 | FLAG |
| Key field | Non-key field |
How do I retrieve data from SAP structure P1500 using ABAP code?
As P1500 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 P1500 as there is no data to select.How to access SAP table P1500
Within an ECC or HANA version of SAP you can also view further information about P1500 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