FKK_CRM_PAYMENT_ITEM SAP (FI-CA Payment Item) Structure details
Description: FI-CA Payment Item
Related tables to FKK_CRM_PAYMENT_ITEM
Access table FKK_CRM_PAYMENT_ITEM
Structure field list including key, data, relationships and ABAP select examples
FKK_CRM_PAYMENT_ITEM 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 "FI-CA Payment Item" 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_FKK_CRM_PAYMENT_ITEM TYPE FKK_CRM_PAYMENT_ITEM.
The FKK_CRM_PAYMENT_ITEM table consists of various fields, each holding specific information or linking keys about FI-CA Payment Item data available in SAP. These include POSZA (Item number in a payment lot), BETRZ (Payment amount in transaction currency), WAERS (Currency Key), KOINH (Name of Holder of Bank Account/Check Issuer/Cardholder).. 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 FKK_CRM_PAYMENT_ITEM 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 |
| KEYZ1 | Payment Lot | KEYZ1_KK | CHAR | 12 | KEYZ1_KK | ||||
| POSZA | Item number in a payment lot | POSZA_KK | NUMC | 6 | NUM06 | ||||
| BETRZ | Payment amount in transaction currency | BETRZ_KK | CURR | 13(2) | WRTV7 | ||||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| KOINH | Name of Holder of Bank Account/Check Issuer/Cardholder | KOINH_KK | CHAR | 60 | KOINH | ||||
| CHCKN | Check number | CHCKN_KK | CHAR | 13 | CHCKN | ||||
| BANKN | Bank account number | BANKN | CHAR | 18 | BANKN | ||||
| BANKL | Bank number | BANKL | CHAR | 15 | BANKL | BLZ | |||
| CCNUM | Payment cards: Card number | CCNUM | CHAR | 25 | Assigned to domain | CCNUM | |||
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| GSBER | Business Area | GSBER | CHAR | 4 | Assigned to domain | GSBER | GSB | ||
| BUDAT | Posting Date in the Document | BUDAT_KK | DATS | 8 | DATUM | ||||
| BLDAT | Document Date in Document | BLDAT | DATS | 8 | DATUM | ||||
| VALUT | Value date | VALUT | DATS | 8 | DATUM | ||||
| XCLAR | Line item included in clarification worklist | XCLAR_KK | CHAR | 1 | XFELD | ||||
| RUEBL | Number of the resetting document | RUEBL_KK | CHAR | 12 | Assigned to domain | ALPHA | OPBEL_KK | ||
| CCINSTXT | Text 50 Characters | TXT50_KK | CHAR | 50 | TEXT50 | ||||
| OPBEL | Number of Contract Accts Rec. & Payable Doc. | OPBEL_KK | CHAR | 12 | Assigned to domain | ALPHA | OPBEL_KK | 80B | |
| KLAEB | Number of Clarification Document | KLAEB_KK | CHAR | 12 | Assigned to domain | ALPHA | OPBEL_KK | ||
| STATTXT | Text (80 Characters) | TEXT80 | CHAR | 80 | TEXT80UEB | ||||
| PYSTA | Payment Status of Payment Lot Item | PYSTA_KK | CHAR | 3 | PYSTA_KK | ||||
| IBAN | IBAN (International Bank Account Number) | IBAN_KK | CHAR | 34 | IBAN | ||||
| IDISP2 | Object Is Assigned to a Dispute Case | IDISP2_KK | CHAR | 1 | IDISP2_KK |
| Key field | Non-key field |
How do I retrieve data from SAP structure FKK_CRM_PAYMENT_ITEM using ABAP code?
As FKK_CRM_PAYMENT_ITEM 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 FKK_CRM_PAYMENT_ITEM as there is no data to select.How to access SAP table FKK_CRM_PAYMENT_ITEM
Within an ECC or HANA version of SAP you can also view further information about FKK_CRM_PAYMENT_ITEM 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