RFKIP_GRP SAP (Payment Specification: Payment Data) Structure details
Dictionary Type: Structure
Description: Payment Specification: Payment Data
Description: Payment Specification: Payment Data
Structure field list including key, data, relationships and ABAP select examples
RFKIP_GRP 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 Specification: Payment Data" 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_RFKIP_GRP TYPE RFKIP_GRP.
The RFKIP_GRP table consists of various fields, each holding specific information or linking keys about Payment Specification: Payment Data data available in SAP. These include PDKEY (Number of Payment Specification), PDTYP (Category of Payment Specification), GPARV (Business Partner Acting as Payer in Payment Transactions), VKONV (Contract account used for payment transactions).. 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 RFKIP_GRP 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 |
| PDKEY | Number of Payment Specification | PDKEY_KK | NUMC | 12 | PDKEY_KK | 80B | |||
| PDTYP | Category of Payment Specification | PDTYP_KK | CHAR | 1 | PDTYP_KK | ||||
| GPARV | Business Partner Acting as Payer in Payment Transactions | GPARV_KK | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | ||
| VKONV | Contract account used for payment transactions | VKONV_IP | CHAR | 12 | Assigned to domain | ALPHA | VKONT_KK | ||
| PDREF | Reference Number of Payment Specification | PDREF_KK | CHAR | 16 | PDREF_KK | ||||
| EIGBV | Own Bank Details | EIGBV_KK | CHAR | 25 | TFK042H | EIGBV_KK | |||
| PYMET | Payment Method | PYMET_KK | CHAR | 1 | TFK042Z | PYMET_KK | |||
| BKVID | Bank details ID | BU_BKVID | CHAR | 4 | BUT0BK | CHAR4 | |||
| MNDID | Unique Referene to Mandate per Payment Recipient | SEPA_MNDID | CHAR | 35 | ID035 | ||||
| CCARD_ID | Payment Card ID | BU_CCID | CHAR | 6 | BUT0CC | CHAR6 | |||
| PYBUK | Company Code for Automatic Payment Transactions | PYBUK_KK | CHAR | 4 | T001 | BUKRS | |||
| BETRW | Payment Amount of Payment Specification | BETRW_INDPAY | CURR | 13(2) | WRTV7 | ||||
| WAERS | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| ERTIM | 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 of Entry | CPUTM | TIMS | 6 | UZEIT | ||||
| DOC1T | Payment Document Category | DOC1T_KK | CHAR | 2 | DOCTP_KK | ||||
| DOC1R | Reference to Payment Document | DOC1R_KK | CHAR | 24 | CHAR24 | ||||
| LAUFD | Date ID | LAUFD_KK | DATS | 8 | DATUM | ||||
| LAUFI | Identification for the payment run | LAUFI_PAY | CHAR | 5 | LAUFI_PAY | ||||
| C4EYE | Check Reason for Workflows Acc. to Dual Control Principle | C4EYE_KK | CHAR | 2 | TFK4EYE | C4EYE_KK | |||
| DTAWS | Instruction key for data medium exchange | DTAWS | CHAR | 2 | T015W | DTAWS | |||
| DTAMS | Indicator for Data Medium Exchange | DTAMS | CHAR | 1 | DTAMS | ||||
| TXTSL | Text key for the code line on the form | TXTSL_042Z | CHAR | 2 | CHAR2 | ||||
| TXERG | Text key supplement | TXERG | CHAR | 3 | CHAR3 | ||||
| STAIP | Payment Specification: Status | STAIP_KK | CHAR | 1 | STAIP_KK | ||||
| AUSFD | Payment Specification: Execution Date | AUSFD_INDPAY | DATS | 8 | DATUM | ||||
| PYTXT | Text for Payment | PYTXT_KK | CHAR | 50 | TXT50 | ||||
| XFINI | Processing Status for Payment Specification | XFINI_INDPAY | CHAR | 1 | XFINI_IP | ||||
| VALTO | Expiry Date of Payment Specification | VALTO_IP | DATS | 8 | DATUM | ||||
| PYTYP | Payment Type Notified | PYTYP_KK | CHAR | 1 | PYTYP_KK | ||||
| FDGRP | Planning Group | FDGRP_KK | CHAR | 10 | T035 | ALPHA | FDGRP | FFG | |
| FDLEV | Planning level | FDLEV_KK | CHAR | 2 | T036 | FDLEV | FFE | ||
| FDZTG | Additional Days for Cash Management | FDZTG_KK | NUMC | 2 | NUM2 | ||||
| FDWBT | Planning amount in document currency | FDWBT | CURR | 13(2) | WERTV7 | ||||
| SPZAH | Lock Reason for Automatic Payment | SPZAH_KK | CHAR | 1 | TFK008 | SPZAH_KK | |||
| BETRH | Amount In Local Currency With +/- Signs | BETRH_KK | CURR | 13(2) | WRTV7 | ||||
| HERKF | Origin of Payment Specification | HERKF_IP_KK | CHAR | 2 | HERKF_IP_KK | ||||
| CCINS | Payment card type | CC_INSTITUTE | CHAR | 4 | TB033 | CC_INSTITUTE | |||
| CCNUM | Payment cards: Card number | CCNUM | CHAR | 25 | Assigned to domain | CCNUM | |||
| CCFOL | Payment cards: Payment card suffix | CCFOL | CHAR | 10 | CHAR10 | ||||
| DATAB | Payment cards: Valid from | CC_DATAB | DATS | 8 | DATUM | ||||
| DATBI | Payment Cards: Valid To | CC_DATBI | DATS | 8 | DATUM | ||||
| CCNAME | Payment cards: Name of cardholder | CCNAME | CHAR | 40 | TEXT40 | ||||
| AUNUM | Payment cards: Authorization number | AUNUM_KK | CHAR | 25 | CHAR25 | ||||
| AUDAT | Payment cards: Authorization date | AUDAT_CC | DATS | 8 | DATUM | ||||
| AUTIM | Payment cards: Authorization time | AUTIM | TIMS | 6 | UZEIT | ||||
| CGUID | GUID of a Payment Card | CARD_GUID | RAW | 16 | SYSUUID | ||||
| ENCTP | Type of Encryption | CCSECA_ENCTYPE | CHAR | 1 | CCSECA_ENCTYPE | ||||
| SKTOW | Cash Discount Amount in Currency of Payment Specification | SKTOW_INDPAY | CURR | 13(2) | WRTV7 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RFKIP_GRP using ABAP code?
As RFKIP_GRP 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 RFKIP_GRP as there is no data to select.How to access SAP table RFKIP_GRP
Within an ECC or HANA version of SAP you can also view further information about RFKIP_GRP 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