EPIC_S_FILE SAP (Structure of Payment File) Structure details
Description: Structure of Payment File
Structure field list including key, data, relationships and ABAP select examples
EPIC_S_FILE 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 of Payment File" 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_EPIC_S_FILE TYPE EPIC_S_FILE.
The EPIC_S_FILE table consists of various fields, each holding specific information or linking keys about Structure of Payment File data available in SAP. These include MANDT (Client), ZBUKR (Paying company code), BANKS (Bank country key), LAUFD (Date on Which the Program Is to Be Run).. 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 EPIC_S_FILE 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 | T000 | MANDT | |||
ZBUKR | Paying company code | DZBUKR | CHAR | 4 | T001 | BUKRS | |||
BANKS | Bank country key | BANKS | CHAR | 3 | T005 | LAND1 | BKL | ||
LAUFD | Date on Which the Program Is to Be Run | LAUFD | DATS | 8 | DATUM | ||||
LAUFI | Additional Identification | LAUFI | CHAR | 6 | LAUFI | ||||
XVORL | Indicator: Only Proposal Run? | XVORL | CHAR | 1 | XFELD | ||||
DTKEY | Additional Field for the TemSe Key Fields | DTKEY_D | CHAR | 16 | TEXT16 | ||||
LFDNR | Sequential Number | LFDNU | NUMC | 3 | NUMC3 | ||||
WAERS | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
RBETR | Amount in Local Currency | RBETR | CURR | 13(2) | WRTV7 | ||||
RENUM | Reference Number | RENUM | CHAR | 16 | TEXT16 | ||||
DTFOR | Payment Medium Format | FORMI_FPM | CHAR | 30 | Assigned to domain | FORMI_FPM | |||
TSNAM | TemSe File Name | TSNAM | CHAR | 20 | TEXT20 | ||||
TSDAT | File Creation Date | TSDAT | DATS | 8 | DATS | ||||
TSTIM | File Creation Time | TSTIM | TIMS | 6 | UZEIT | ||||
TSUSR | Name of the User who Created the TemSe File | TSUSR | CHAR | 12 | UNAME | ||||
DWNAM | File Name for Download | DONAM | CHAR | 255 | TEXT255 | ||||
DWDAT | Date of Download | DODAT | DATS | 8 | DATS | ||||
DWTIM | Time of Download | DOTIM | TIMS | 6 | UZEIT | ||||
DWUSR | User Name for Carrying Out Download | DOUSR | CHAR | 12 | UNAME | ||||
KADAT | Electronic Account Statement Date | KADAT | DATS | 8 | DATUM | ||||
KATIM | Electronic Account Statement Time | KATIM | TIMS | 6 | UZEIT | ||||
KAUSR | Electronic Account Statement User | KAUSR | CHAR | 12 | UNAME | ||||
REPORT | ABAP Program Name | PROGNAME | CHAR | 40 | PROGNAME | ||||
FSNAM | File Name in the File System | FSNAM | CHAR | 255 | TEXT255 | ||||
USREX | Identifier ###, if Data Medium Modified by User Exit | USREX | CHAR | 3 | CHAR3 | ||||
EDINUM | Number of Document Extract | EDINUM | NUMC | 16 | EDI_DOCNUM | ||||
GRPNO | Grouping Criterium for Payments | GRPNO_FPM | INT4 | 10 | DFPAYG | GRPNO_FPM | |||
DTTYP | Type of Payment Medium w/o Documents | DTTYP_FPM | CHAR | 2 | DTTYP_FPM | ||||
GUID | UUID in character form | SYSUUID_C | CHAR | 32 | SYSUUID_C | ||||
SAPRL | Release of SAP System | SYSAPRL | CHAR | 4 | SYCHAR04 | ||||
CODEPAGE | SAP Character Set ID | CPCODEPAGE | NUMC | 4 | Assigned to domain | CPCODEPAGE | |||
.INCLU--AP | 0 | ||||||||
STATUS | Payment File Status | EPIC_REGUT_STATUS | CHAR | 3 | EPIC_REGUT_STATUS | ||||
EPIC_STATUS_ICON | File Status | EPIC_FILE_STATUS_ICON | CHAR | 30 | |||||
EPIC_STATUS_DESCR | File Status Description | EPIC_FILE_STATUS_DESCR | CHAR | 40 | TEXT40 | ||||
EPIC_CELLTAB | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure EPIC_S_FILE using ABAP code?
As EPIC_S_FILE 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 EPIC_S_FILE as there is no data to select.How to access SAP table EPIC_S_FILE
Within an ECC or HANA version of SAP you can also view further information about EPIC_S_FILE 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