FVD_SEPA_MANDATE_USAGE SAP (Structure for check of mandate usage consistency) Structure details
Description: Structure for check of mandate usage consistency
Related tables to FVD_SEPA_MANDATE_USAGE
Access table FVD_SEPA_MANDATE_USAGE
Structure field list including key, data, relationships and ABAP select examples
FVD_SEPA_MANDATE_USAGE 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 "Structure for check of mandate usage consistency" 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_FVD_SEPA_MANDATE_USAGE TYPE FVD_SEPA_MANDATE_USAGE.
The FVD_SEPA_MANDATE_USAGE table consists of various fields, each holding specific information or linking keys about Structure for check of mandate usage consistency data available in SAP. These include MANDT (Client), BUKRS (Company Code), RANL (Contract Number), SOBJEKT (Internal key for object for business partner table).. 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 (Deep)
SAP FVD_SEPA_MANDATE_USAGE 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 |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| RANL | Contract Number | RANL | CHAR | 13 | ALPHA | RANL | RAN | ||
| SOBJEKT | Internal key for object for business partner table | VVSOBJGPO | CHAR | 13 | CHAR13 | ||||
| PARTNR | Business Partner Number | BP_PARTNR_NEW | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| ROLETYP | BP Role | BU_PARTNERROLE | CHAR | 6 | Assigned to domain | BU_ROLE | BUPA_ROLE | ||
| DTRANS | Flow data key: System date | VVDTRANS | DATS | 8 | DATUM | ||||
| DGUEL_KK | Date Condition Effective from | DGUEL | DATS | 8 | DATUM | ||||
| NLFD_ANG | Offer consecutive number | NLFD_ANG | NUMC | 3 | LFNR3 | ||||
| SKOART | Condition Type (Smallest Subdivision of Condition Records) | SKOART | NUMC | 4 | Assigned to domain | SKOART | |||
| DGUEL_KP | Condition Item Valid From | DGUEL_KP | DATS | 8 | DATUM | ||||
| NSTUFE | Level number of condition item for recurring payments | NSTUFE | NUMC | 2 | NUMC2 | ||||
| SSIGN | Direction of flow | TB_SSIGN | CHAR | 1 | T_SSIGN | ||||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| DZVERB | Payment details effective from | TB_DZVERB | DATS | 8 | DATUM | ||||
| SBEWART | Flow Type | SBEWART | CHAR | 4 | Assigned to domain | SBEWART | |||
| MNDID | Unique Referene to Mandate per Payment Recipient | SEPA_MNDID | CHAR | 35 | ID035 | ||||
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
| FLG_VZZKOPO | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| FLG_VDGPO | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| FLG_VDZV | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| TEXT | SEPA (Error-)Message (Text) | TB_SEPA_MESSAGE | STRG | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure FVD_SEPA_MANDATE_USAGE using ABAP code?
As FVD_SEPA_MANDATE_USAGE 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 FVD_SEPA_MANDATE_USAGE as there is no data to select.How to access SAP table FVD_SEPA_MANDATE_USAGE
Within an ECC or HANA version of SAP you can also view further information about FVD_SEPA_MANDATE_USAGE 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