SAP table VTBKORTMS (Treasury: TemSe Administration Data for Confirmation Runs)
SAP table VTBKORTMS has 6 primary key fields being MANDT,BBUKR,LAUFD,LAUFI,DTKEY,LFDNR.
If you're only analyzing data from a single SAP instance you may omit field MANT in your relationships as it will we the same across the entire dataset. On the other hand, if you're combining data from multiple SAP instances you need to take MANDT into account.
| Field | Description | Data Type | Length | Decimals | Checktable | Data Element | |
|---|---|---|---|---|---|---|---|
| MANDT | Client | CLNT | 3 | 0 | * | MANDT | |
| BBUKR | Company Code | CHAR | 4 | 0 | * | BUKRS | |
| LAUFD | SWIFT: Date of Confirmation Run | DATS | 8 | 0 | LAUFDT | ||
| LAUFI | Additional identification | CHAR | 6 | 0 | LAUFIT | ||
| DTKEY | Additional field for the TemSe key fields | CHAR | 16 | 0 | TDTKEY_D | ||
| LFDNR | Sequence Number | NUMC | 3 | 0 | TLFDNU | ||
| RENUM | Reference Number | CHAR | 16 | 0 | TB_RENUM | ||
| DTFOR | File Format for Data Medium Exchange | CHAR | 10 | 0 | TB_DTFOR | ||
| TSNAM | TemSe File Name | CHAR | 20 | 0 | TB_TSNAM | ||
| TSDAT | File Creation Date | DATS | 8 | 0 | TB_TSDAT | ||
| TSTIM | File Creation Time | TIMS | 6 | 0 | TB_TSTIM | ||
| TSUSR | Name of the User Who Creates the TemSe File | CHAR | 12 | 0 | TB_TSUSR | ||
| DWNAM | File Name for Download | CHAR | 255 | 0 | TB_DONAM | ||
| DWDAT | Date of Download | DATS | 8 | 0 | TB_DODAT | ||
| DWTIM | Time of Download | TIMS | 6 | 0 | TB_DOTIM | ||
| DWUSR | User Name for Carrying Out Download | CHAR | 12 | 0 | TB_DOUSR | ||
| REPORT | Report Program | CHAR | 40 | 0 | TB_REPORT_D | ||
| FSNAM | File Name in the File System | CHAR | 255 | 0 | TB_FSNAM | ||
| USREX | Identifier ###, If Data Medium Modified by User Exit | CHAR | 3 | 0 | TB_USREX | ||
| EDINUM | IDoc Number | NUMC | 16 | 0 | TB_EDINUM | ||
| KONTRH | Business Partner Number | CHAR | 10 | 0 | * | TB_KUNNR_NEW | |
| PCPATH | File Name for Download | CHAR | 255 | 0 | TB_DONAM |