FKKPOH_MSG SAP (Payment Order: Header Data with Messages) Structure details
Description: Payment Order: Header Data with Messages
Structure field list including key, data, relationships and ABAP select examples
FKKPOH_MSG 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 "Payment Order: Header Data with Messages" 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_FKKPOH_MSG TYPE FKKPOH_MSG.
The FKKPOH_MSG table consists of various fields, each holding specific information or linking keys about Payment Order: Header Data with Messages data available in SAP. These include MANDT (Client), PYORD (Payment Order), ORG1T (Type of Organization), ORG1R (Reference for Organization).. 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 FKKPOH_MSG 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 | Assigned to domain | MANDT | |||
| PYORD | Payment Order | PYORD_KK | CHAR | 10 | ALPHA | PYORD | |||
| ORG1T | Type of Organization | ORG1T_PAY | CHAR | 2 | ORGTP_PAY | ||||
| ORG1R | Reference for Organization | ORG1R_PAY | CHAR | 8 | CHAR8 | ||||
| HBKID | Short Key for a House Bank | HBKID | CHAR | 5 | Assigned to domain | HBKID | |||
| HKTID | ID for account details | HKTID | CHAR | 5 | Assigned to domain | HKTID | |||
| RZAWE | Payment Method | PYMET_KK | CHAR | 1 | Assigned to domain | PYMET_KK | |||
| AUSFD | Due date of the paid items | AUSFD | DATS | 8 | DATUM | ||||
| VERFD | Expiration Date of Payment Order | VERFD_KK | DATS | 8 | DATUM | ||||
| STAZA | Status of Payment Order | STAZA_KK | CHAR | 1 | STAZA_KK | ||||
| GPA1T | Business Partner Category | GPA1T_PAY | CHAR | 2 | GPATP_PAY | ||||
| GPA1R | Business Partner Reference | GPA1R_PAY | CHAR | 12 | CHAR12 | ||||
| RFORD | External Reference Number of Payment Order | RFORD_KK | CHAR | 30 | RFORD_KK | ||||
| LAUFD | Date ID | LAUFD_KK | DATS | 8 | DATUM | ||||
| LAUFI | Identification for the payment run | LAUFI_PAY | CHAR | 5 | LAUFI_PAY | ||||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| NWBTR | Net Payment Amount with +/- Sign | NWBTRV_KK | CURR | 13(2) | WRTV7 | ||||
| RWBTR | Amount Paid in the Payment Currency | RWBTR | CURR | 13(2) | WRTV7 | ||||
| RBETR | Amount in Local Currency | RBETR | CURR | 13(2) | WRTV7 | ||||
| DIFFB | Difference Amount in Clearing Processing | DIFFB_KK | CURR | 13(2) | WRTV7 | ||||
| VALUT | Value date | VALUT | DATS | 8 | DATUM | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| CPUDT | Day On Which Accounting Document Was Entered | CPUDT | DATS | 8 | DATUM | ||||
| CPUTM | Time of Entry | CPUTM | TIMS | 6 | UZEIT | ||||
| AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| AETIM | Time changed | CDUZEIT | TIMS | 6 | UZEIT | ||||
| FDLEV | Planning level | FDLEV | CHAR | 2 | Assigned to domain | FDLEV | FFE | ||
| BNKKO | Bank account/bank clearing account (G/L account) | BNKKO | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | ||
| GSBER | Business Area | GSBER | CHAR | 4 | Assigned to domain | GSBER | GSB | ||
| PRCTR | Profit Center | PRCTR | CHAR | 10 | Assigned to domain | ALPHA | PRCTR | PRC | PRCTR_EMPTY |
| ZLAND | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| APPLK | Application area | APPLK_KK | CHAR | 1 | APPLK_KK | ||||
| PYBEL | Number of Payment Document | PYBEL_KK | CHAR | 12 | Assigned to domain | ALPHA | OPBEL_KK | ||
| PPKEY | Identification of Promise to Pay | PPKEY_KK | CHAR | 12 | DFKKPP | ALPHA | PPKEY_KK | 8P2P | |
| MSGID | Message Class | SYMSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
| MSGNO | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
| MSGTX | Text (80 Characters) | TEXT80 | CHAR | 80 | TEXT80UEB |
| Key field | Non-key field |
How do I retrieve data from SAP structure FKKPOH_MSG using ABAP code?
As FKKPOH_MSG 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 FKKPOH_MSG as there is no data to select.How to access SAP table FKKPOH_MSG
Within an ECC or HANA version of SAP you can also view further information about FKKPOH_MSG 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