PAYHX_MDT SAP (Payment Medium: Mandate) Structure details
Description: Payment Medium: Mandate
Structure field list including key, data, relationships and ABAP select examples
PAYHX_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_PAYHX_MDT TYPE PAYHX_MDT.
The PAYHX_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), B2B (SEPA-Mandate: B2B Mandate), REC_CRDID (Creditor Identification Number), SEQ_TYPE (SEPA: Sequence Type).. 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 PAYHX_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 | Unique Referene to Mandate per Payment Recipient | SEPA_MNDID | CHAR | 35 | ID035 | ||||
SIGN_DATE | Date of Signature | SEPA_SIGN_DATE | DATS | 8 | DATUM | ||||
B2B | SEPA-Mandate: B2B Mandate | SEPA_B2B | CHAR | 1 | XFELD | ||||
REC_CRDID | Creditor Identification Number | SEPA_CRDID | CHAR | 35 | ID035 | ||||
SEQ_TYPE | SEPA: Sequence Type | SEPA_SEQ_TYPE | CHAR | 4 | SEPA_SEQ_TYPE | ||||
AMEND_IND | SEPA Amendment Indicator for Mandate | SEPA_AMEND_IND | CHAR | 1 | BOOLEAN | ||||
ORIG_MNDID | SEPA Mandate: Original Mandate of Mandate | SEPA_MNDID_ORIGIN | CHAR | 35 | ID035 | ||||
ORIG_REC_CRDID | SEPA Mandate: Original Creditor ID of Mandate | SEPA_CRDID_ORIGIN | CHAR | 35 | ID035 | ||||
ORIG_REC_NAME1 | Name 1 of organization | BU_NAMEOR1 | CHAR | 40 | BU_NAME | ||||
ORIG_REC_NAME2 | Name 2 of organization | BU_NAMEOR2 | CHAR | 40 | BU_NAME | ||||
ORIG_IBAN | IBAN (International Bank Account Number) | IBAN | CHAR | 34 | IBAN | ||||
ORIG_BIC | SWIFT/BIC for International Payments | SWIFT | CHAR | 11 | SWIFT | ||||
XSEPA | SEPA Mandate Required | XSEPA_KK | CHAR | 1 | XFELD | ||||
SND_DEBTOR_ID | SEPA: ID Number of Sender (External Reference) | SEPA_SND_DEBTOR_ID_KK | CHAR | 35 | ID035 | ||||
INST_CODE | Local Instrument Code (Direct Debit Type) | FSEPA_INST_CODE | CHAR | 4 | FSEPA_INST_CODE |
Key field | Non-key field |
How do I retrieve data from SAP structure PAYHX_MDT using ABAP code?
As PAYHX_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 PAYHX_MDT as there is no data to select.How to access SAP table PAYHX_MDT
Within an ECC or HANA version of SAP you can also view further information about PAYHX_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