| Table | Table Description | Column# | Alias | Column Description | Data Type | Length | Decimals | Default Value | Constraints |
|---|
| 1 | TREAT_FLOW_PM | Treasury: TREA Flow Payment Details | 13 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| TOPBack Office |
| 2 | TRFT_PACC_BANK | Payment Information | 17 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 3 | TRST_CLASFLO | CFM: Class Flows in Securities Account | 47 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 4 | TRST_CLASFLO_REV | CFM: Reversed Class Flows in Securities Account | 47 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 5 | TRST_SECACC_BANK | Payment Details for Securities Account | 17 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 6 | TRST_SECACC_PAY | Downport Payment Information for Securities Management | 16 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| TOPBusiness Partner |
| 7 | VTBSTC1 | Components of Payment Details for Standing Instruction | 17 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| TOPLoans Management |
| 8 | TTONFTVZZBEPP | Test neue FIMA: VZZBEPP | 249 | SCSPAY | gleiche Richtung für gemeinsame Regulierung erforderlich? | nvarchar | 1 | 0 | | |
| 9 | VDBEPI | Posted line items for document header | 136 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 10 | VDBEPI_SHADOW | Shadow Table for VDBEPI (Restrictions) | 136 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 11 | VDBEPP | Flow Data - Planned Item | 160 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 12 | VDBOBEPP | Business Operation: Entered and Activated Flow Data | 160 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 13 | VDORDER | Borrower's note loan order data | 75 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 14 | VDZV | Payment Details for the Loan | 24 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 15 | VZFZE_VDBEPP | Central Entry Table for Release Procedure | 163 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| TOPTransaction Manager |
| 16 | OTC_CONV_FHAPO | Backup Table for Financial Transaction Flows | 37 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 17 | SLDT_FLOW | Subledger Distributor Transactions | 62 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 18 | TERT_FLOW | Flow Table for Rights that can be Exercised | 31 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 19 | TRDT_FLOW | Persistent distributor flows | 60 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 20 | VTBFHAPO | Transaction Flow | 37 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 21 | VTBFHAPO_MIGR | Migrated Financial Flows | 37 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 22 | VTBFHAPO_UNFIXED | Non-Fixed Financial Transaction Flows | 37 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| 23 | VTBZV | Payment Details for Transaction | 24 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| TOPTransfer to Financial Accounting |
| 24 | TRPRT_PAYMENTS | Persistent Data for Payment Requests | 18 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
| TOPTreasury and Risk Management |
| 25 | TREAT_EXT_ACC_PM | Treasury: External Account Payment Details | 17 | SCSPAY | Same direction necessary for joint payment? | nvarchar | 1 | 0 | | |
