FMED_S_HEADER SAP (Entry document header structure) Structure details
Description: Entry document header structure
Related tables to FMED_S_HEADER
Access table FMED_S_HEADER
Structure field list including key, data, relationships and ABAP select examples
FMED_S_HEADER 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 "Entry document header structure" 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_FMED_S_HEADER TYPE FMED_S_HEADER.
The FMED_S_HEADER table consists of various fields, each holding specific information or linking keys about Entry document header structure data available in SAP. These include DOCFAM (Document Family Number), EXT_DOCNR (External Number for Budget Entry Document), TECHORG (Original Application), VERSION (Budget version).. 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 FMED_S_HEADER 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 |
PROCESS_UI | Budgeting Process | BUKU_PROCESS_UI | CHAR | 4 | Assigned to domain | BUKU_PROCESS_UI | |||
DOCFAM | Document Family Number | BUED_DOCFAM | CHAR | 10 | ALPHA | BELNR | |||
EXT_DOCNR | External Number for Budget Entry Document | BUED_EXT_DOCNR | CHAR | 10 | ALPHA | BELNR | |||
TECHORG | Original Application | BUKU_TECHORG | CHAR | 10 | Assigned to domain | BUKU_TECHORG | |||
VERSION | Budget version | BUKU_VERSION | CHAR | 3 | Assigned to domain | ALPHA | COVERSI | BP2 | |
CRTUSER | User Who Created or Updated the Object | BUKU_CRTUSER | CHAR | 12 | USERNAME | ||||
CRTDATE | Date on which the object was created or updated | BUKU_CRTDATE | DATS | 8 | DATE | ||||
CRTTIME | Time at which the object was created or updated | BUKU_CRTTIME | TIMS | 6 | TIME | ||||
CHGUSER | Last user to change object | BUKU_CHGUSER | CHAR | 12 | USERNAME | ||||
CHGDATE | Date on which the object was changed | BUKU_CHGDATE | DATS | 8 | DATE | ||||
CHGTIME | Time at which the object was changed | BUKU_CHGTIME | TIMS | 6 | TIME | ||||
DOCDATE | Document Date | BP_BLDAT | DATS | 8 | DATUM | ||||
POSTDATE | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
REASON_REV | Reason for Reversal of Budget Document | FMREV_STGRD | CHAR | 2 | Assigned to domain | STGRD | FSG | ||
POSTING_PERIOD | Posting period | POPER | NUMC | 3 | POPER | POPR | |||
RESPPERS | Person Responsible for Planning/Budgeting | BP_VERANT | CHAR | 20 | VERAB | BPV | |||
TEXT50 | Item Text | SGTXT | CHAR | 50 | TEXT50 | ||||
TEXTNAME | Text Name | BP_TDNAM | CHAR | 32 | CHAR32 | ||||
LTXT_IND | Long Text Exists | BP_LTEXT | CHAR | 1 | XFELD | ||||
DOCSTATE | Status of a budget entry document | BUED_DOCSTATE | CHAR | 1 | BUED_DOCSTATE | ||||
REVSTATE | Reversal status | BP_RSTAT | CHAR | 1 | BP_RSTAT | ||||
REV_REFNR | Reversal Reference Document Number | BUED_REV_REFNR | CHAR | 10 | ALPHA | BELNR | |||
DOCTYPE | Budget entry document type | BUED_DOCTYPE | CHAR | 4 | Assigned to domain | BUED_DOCTYPE | DOTY | ||
LOGSYS | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
COHORT | Reporting Year for Cohort | FM_COHORT | CHAR | 4 | FM_COHORT | ||||
PUBLAW | Public Law Cited | FM_PUBLAW | CHAR | 20 | FM_PUBLAW | ||||
LEGIS | Type of Legislation | FM_LEGIS | CHAR | 1 | FM_LEGIS | ||||
XBLNR | Reference Document Number | XBLNR1 | CHAR | 16 | XBLNR1 | ||||
AWORG | Reference Organizational Units | AWORG | CHAR | 10 | AWORG | ||||
AWREF | Reference Document Number | AWREF | CHAR | 10 | ALPHA | AWREF | |||
AWSYS | Logical system of source document | AWSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
AWTYP | Reference Transaction | AWTYP | CHAR | 5 | Assigned to domain | AWTYP | |||
AWORG_REV | Reversal: Reverse Document Reference Organization | AWORG_REV | CHAR | 10 | AWORG | ||||
AWREF_REV | Reversal: Reverse Document Reference Document Number | AWREF_REV | CHAR | 10 | ALPHA | AWREF | |||
LAYOUTVAR | Layout variant - Layout management in budgeting | FMLA_LAYOUTVAR | CHAR | 6 | FMLA | FMLA_LAYOUTVAR | LAY | ||
TRANSFER_AGENCY | Transfer Agency | FMFG_TRANSFER_AGCY | CHAR | 2 | Assigned to domain | FMFG_TRANSFER | |||
TRANSFER_ACCOUNT | Transfer Account | FMFG_TRANSFER_ACCT | CHAR | 4 | Assigned to domain | FMFG_TRAN_ACCT | |||
RCOMP | Company ID of trading partner | RASSC | CHAR | 6 | Assigned to domain | ALPHA | RCOMP | PGS | |
.INCLU--AP | 0 | ||||||||
/SAPF15/STATUS | /SAPF15/STATUS | CHAR | 1 | /SAPF15/STATUS |
Key field | Non-key field |
How do I retrieve data from SAP structure FMED_S_HEADER using ABAP code?
As FMED_S_HEADER 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 FMED_S_HEADER as there is no data to select.How to access SAP table FMED_S_HEADER
Within an ECC or HANA version of SAP you can also view further information about FMED_S_HEADER 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