RREPAY_ADMIN SAP (Administration Data for Payoff) Structure details
Description: Administration Data for Payoff
Structure field list including key, data, relationships and ABAP select examples
RREPAY_ADMIN 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 "Administration Data for Payoff" 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_RREPAY_ADMIN TYPE RREPAY_ADMIN.
The RREPAY_ADMIN table consists of various fields, each holding specific information or linking keys about Administration Data for Payoff data available in SAP. These include ZLSCH (Payment Method), BVTYP (Bank Details ID), SZART (Payment transaction), JNODOIP (Blocked by Payoff: No Open Item Clearing for Loan).. 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)
SAP RREPAY_ADMIN 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 |
| PARTNR | Payer of Payoff | TB_PARTNR_REPAY | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| ZLSCH | Payment Method | DZLSCH | CHAR | 1 | Assigned to domain | ZLSCH | |||
| BVTYP | Bank Details ID | TB_BVTYP | CHAR | 4 | BVTYP | ||||
| SZART | Payment transaction | TB_SZART | CHAR | 1 | XFELD | ||||
| JNODOIP | Blocked by Payoff: No Open Item Clearing for Loan | TB_JNODOIP | CHAR | 1 | XFELD | ||||
| XNODUNN | Exclude Loan from Dunning Run | XNODUNN | CHAR | 1 | XFELD | ||||
| KOSTL | Cost Center | KOSTL | CHAR | 10 | Assigned to domain | ALPHA | KOSTL | KOS | |
| SBUST | Posting control key | VVSBUST | NUMC | 2 | TZB09 | VVSBUST | |||
| SZEGEN | Generate incoming payment immediately | SZEGEN | NUMC | 2 | TD21 | SZEGEN | |||
| DANGAM | Creation Date for the Offer | TB_DANGAM_REPAY | DATS | 8 | DATUM | ||||
| DANGBIS | End of the Validity Period of the Offer | TB_DANGBIS_REPAY | DATS | 8 | DATUM | ||||
| DANNAHME | Acceptance Date of the Offer | TB_DANNAHME_REPAY | DATS | 8 | DATUM | ||||
| DKUENDDG | Date of Receipt of Notice | TB_DKUEND_REPAY | DATS | 8 | DATUM | ||||
| SKUEND | Reason for Notice | TB_SKUEND_REPAY | NUMC | 3 | TD04 | SKUEART | |||
| RREJECT_REASON | Reason for Rejection | TB_REJECT_REASON | CHAR | 3 | TDREPAY_REJECT | T_REASON | |||
| RREPAY_REASON | Payoff Reason | TB_REPAY_REASON | NUMC | 3 | TD04 | SKUEART | |||
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
| ZAHLS | Block Key for Payment | DZAHLS | CHAR | 1 | T008 | ZAHLS | |||
| XCONDPAYDATA | Keep Payment Data for Condition-Based Flows Acc to Cond. | XCONDPAYDATA | CHAR | 1 | XFELD | ||||
| MABER | Dunning Area | MABER | CHAR | 2 | T047M | MABER | |||
| MANSP | Dunning block | MANSP | CHAR | 1 | T040S | MANSP | |||
| REMIT_INFO | Payment Notes Info | TB_REMIT_INFO | CHAR | 140 | T_REMIT_INFO | ||||
| MNDID | Unique Referene to Mandate per Payment Recipient | SEPA_MNDID | CHAR | 35 | ID035 | ||||
| UZAWE | Payment Method Supplement | UZAWE | CHAR | 2 | Assigned to domain | UZAWE |
| Key field | Non-key field |
How do I retrieve data from SAP structure RREPAY_ADMIN using ABAP code?
As RREPAY_ADMIN 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 RREPAY_ADMIN as there is no data to select.How to access SAP table RREPAY_ADMIN
Within an ECC or HANA version of SAP you can also view further information about RREPAY_ADMIN 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