FPAYHX_MDT SAP (Payment Medium: Mandate) Structure details
Description: Payment Medium: Mandate
Structure field list including key, data, relationships and ABAP select examples
FPAYHX_MDT 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 Medium: Mandate" 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_FPAYHX_MDT TYPE FPAYHX_MDT.
The FPAYHX_MDT table consists of various fields, each holding specific information or linking keys about Payment Medium: Mandate data available in SAP. These include SIGN_DATE (Date of Signature (Mandate)), B2B (B2B Mandate), REC_CRDID (Vendor ID (Unique Cross-Country)), SEQ_TYPE (Sequence Type for Automatic Debit).. 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 FPAYHX_MDT 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 |
| MNDID | Mandate ID (SEPA) | FPM_MNDID | CHAR | 35 | |||||
| SIGN_DATE | Date of Signature (Mandate) | FPM_MND_SIGN_DATE | DATS | 8 | DATUM | ||||
| B2B | B2B Mandate | FPM_B2B | CHAR | 1 | BOOLEAN | ||||
| REC_CRDID | Vendor ID (Unique Cross-Country) | FPM_CRDID | CHAR | 35 | |||||
| SEQ_TYPE | Sequence Type for Automatic Debit | FPM_SEQ_TYPE | CHAR | 4 | FPM_SEQ_TYPE | ||||
| INST_CODE | Local Instrument Code (Direct Debit Type) | FPM_INST_CODE | CHAR | 4 | CHAR4 | ||||
| AMEND_IND | Amendment Indicator for Mandate | FPM_AMEND_IND | CHAR | 1 | BOOLEAN | ||||
| ORIG_MNDID | Mandate ID (SEPA) | FPM_MNDID | CHAR | 35 | |||||
| ORIG_REC_CRDID | Vendor ID (Unique Cross-Country) | FPM_CRDID | CHAR | 35 | |||||
| ORIG_REC_NAME1 | Name of the Payee | FPM_NAME | CHAR | 40 | TEXT40 | ||||
| ORIG_REC_NAME2 | Name of the Payee | FPM_NAME | CHAR | 40 | TEXT40 | ||||
| ORIG_IBAN | IBAN (International Bank Account Number) | IBAN | CHAR | 34 | IBAN | ||||
| ORIG_BIC | SWIFT/BIC for International Payments | SWIFT | CHAR | 11 | SWIFT | ||||
| SND_DEBTOR_ID | Identification Number of Sender (Ext. Reference) | FPM_SND_DEBTOR_ID | CHAR | 35 | ID035 |
| Key field | Non-key field |
How do I retrieve data from SAP structure FPAYHX_MDT using ABAP code?
As FPAYHX_MDT 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 FPAYHX_MDT as there is no data to select.How to access SAP table FPAYHX_MDT
Within an ECC or HANA version of SAP you can also view further information about FPAYHX_MDT 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