FMKU_S_HEADER SAP (FM - Kernel Utilities- Header structure) Structure details
Description: FM - Kernel Utilities- Header structure
Related tables to FMKU_S_HEADER
Access table FMKU_S_HEADER
Structure field list including key, data, relationships and ABAP select examples
FMKU_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 "FM - Kernel Utilities- 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_FMKU_S_HEADER TYPE FMKU_S_HEADER.
The FMKU_S_HEADER table consists of various fields, each holding specific information or linking keys about FM - Kernel Utilities- Header structure data available in SAP. These include FM_AREA (Financial Management Area), DOCYEAR (Document Year), VERSION (Budget version), DOCDATE (Document Date).. 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 FMKU_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 |
CLIENT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
FM_AREA | Financial Management Area | FIKRS | CHAR | 4 | FM01 | FIKRS | FIK | ||
DOCYEAR | Document Year | BUKU_DOCYEAR | NUMC | 4 | GJAHR | GJAHR | BUKU_DOCYEAR | ||
VERSION | Budget version | BUKU_VERSION | CHAR | 3 | TKVS | ALPHA | COVERSI | BP2 | |
DOCDATE | Document Date | BP_BLDAT | DATS | 8 | DATUM | ||||
POSTDATE | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
DOCNR | Budget entry document number | BUED_DOCNR | CHAR | 10 | ALPHA | BELNR | BUED_DOCNR | ||
RESPPERS | Person Responsible for Planning/Budgeting | BP_VERANT | CHAR | 20 | VERAB | BPV | |||
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 | ||||
TECHORG | Original Application | BUKU_TECHORG | CHAR | 10 | BUTECHORG | BUKU_TECHORG | |||
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 | FMEDDOCTYPE | 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 | ||||
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 | |||
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 |
Key field | Non-key field |
How do I retrieve data from SAP structure FMKU_S_HEADER using ABAP code?
As FMKU_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 FMKU_S_HEADER as there is no data to select.How to access SAP table FMKU_S_HEADER
Within an ECC or HANA version of SAP you can also view further information about FMKU_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