3.8 Cashflow Transaction
This topics describes the information to perform the bulk upload for the Cashflow Transaction in Oracle Banking Cash Management.
Table 3-10 Cashflow Transaction File Upload
| S.No | Attribute Name | Type | Character | Mandatory/Optional | Description |
|---|---|---|---|---|---|
| 1 | EXTERNAL_REFERENCE_NO | VARCHAR2 | 50 | M | The reference number of the record from external system. This number has to be unique for the source system. In case of updates / modifications ; system will match on this reference number and refresh (drop and recreate). |
| 2 | CASHFLOW_INDICATOR | VARCHAR2 | 1 | M | Cashflow Indicator |
| 3 | CORPORATE_ID | VARCHAR2 | 50 | M | The CIF of the corporate for whom this cashflow is sent. |
| 4 | CODE | VARCHAR2 | 10 | M | The code maintained in OBCMS else new code. |
| 5 | DESCRIPTION | VARCHAR2 | 50 | O | The description of the code, which will display on Reports /UI.
In case if the code is already maintained but with a different description; reports will display the description that has come in the message. When a txn is received ; the description if available in txn will be stored else will be taken from Code master table. In case a new code comes with blank description ; code will be stored as description. |
| 6 | BANK_ACCOUNT_NUMBER | VARCHAR2 | 50 | O | The bank account number of the corporate from or to where the Inflow / outflow event will happen. |
| 7 | VIRTUAL_ACCOUNT_NUMBER | VARCHAR2 | 35 | O | Virtual account number linked to the bank account number which may be used for reconciliation or allocation. |
| 8 | AMOUNT | NUMBER | (28,4) | M | The amount of cashflow . |
| 9 | ACTUAL_AMOUNT | NUMBER | (28,4) | O | The actual amount that was to be paid / recd. If blank Amount field can be copied here. |
| 10 | CCY | VARCHAR2 | 3 | M | The currency code for the amount. |
| 11 | EXPECTED_DATE | DATE | - | M | The expected date on which the cashflow i.e. inflow or outflow will happen. Maximum can be upto 6 months in future or past from Current Date i.e. Current + 6 months and / or Current Month - 6 months. |
| 12 | REVISED_EXPECTED_DATE | DATE | - | O | The date on which the cashflow is envisaged i.e. suppose a invoice is due in Mar 2020 but the vendor has already mentioned that payment will be made in May 2020; so revised expected date is deviation of date on which the payment will release ; if blank will be defaulted to “Expected Date”. |
| 13 | ACTUAL_DATE | DATE | - | CM | The date on which this inflow / outflow actually happened. This date cannot be greater than Branch CBD. The date can be less than or equal to branch CBD. This will flow for historic records i.e. where payments have been received till CBD. If blank default to Revised Expected Date. |
| 14 | CHANNEL | VARCHAR2 | 10 | O | The channel from where the cashflow data is flowing. |
| 15 | APPLICATION_NAME | VARCHAR2 | 50 | M | The specific module within the channel where this cashflow will get impacted. |
| 16 | PARTY_NAME | VARCHAR2 | 50 | O | The name of the party to / from whom the cash flow will be impacted in case of outflow this will be name of the recipient and in case of an inflow it will be the name of the payee |
| 17 | PARTY_ID | VARCHAR2 | 30 | O | This is the party id from / to whom the cashflow will be impacted. This id may or may not exist in OBCMS ; however it will be the basis on which the cashflow will be rolled up , grouped by etc. |
| 18 | STATUS | VARCHAR2 | 30 | O | Cashflow Transaction Status. If blank or Active, it will be considered as ‘Active’. If user sends values as ‘Delete’, record will be considered as soft delete and will not be picked by Reports, screen etc. |
| 19 | NARRATION | VARCHAR2 | 50 | M | This field will capture narration; this will be only stored for now and not displayed anywhere. |
| 20 | T_UDF_TXT_1 | VARCHAR2 | 100 | O | User Defined Field 1 |
| 21 | T_UDF_TXT_2 | VARCHAR2 | 100 | O | User Defined Field 2 |
| 22 | T_UDF_TXT_3 | VARCHAR2 | 100 | O | User Defined Field 3 |
| 23 | T_UDF_TXT_4 | VARCHAR2 | 100 | O | User Defined Field 4 |
| 24 | T_UDF_TXT_5 | VARCHAR2 | 100 | O | User Defined Field 5 |
| 25 | T_UDF_TXT_6 | VARCHAR2 | 100 | O | User Defined Field 6 |
| 26 | T_UDF_TXT_7 | VARCHAR2 | 100 | O | User Defined Field 7 |
| 27 | T_UDF_TXT_8 | VARCHAR2 | 100 | O | User Defined Field 8 |
| 28 | T_UDF_TXT_9 | VARCHAR2 | 100 | O | User Defined Field 9 |
| 29 | T_UDF_TXT_10 | VARCHAR2 | 100 | O | User Defined Field 10 |
| 30 | CUSTOMER_REF_NO | VARCHAR2 | 50 | O | Customer Reference Number |
| 31 | EXCLUDE_RECON | VARCHAR2 | 1 | O | Exclude Recon Flag |
| 32 | CORPORATE_REF_NO | VARCHAR2 | 50 | O | Corporate Ref No |
| 33 | SOURCE | VARCHAR2 | 20 | O | Source |
| 34 | BIC_CODE | VARCHAR2 | 15 | O | BIC Code |
| 35 | OWN_BANK_YN | VARCHAR2 | 1 | O | Own Bank Flag |
Parent topic: File Upload