VA Bank Statement (VA012_)

1. On Bank Statement Form - When user imports a bank statement into an account having account type as Credit card, the system will display a checkbox labeled "Statement date as Account date." When the user selects this checkbox, the system will import the transaction line into the banking journal line with the statement date from the journal header as account date. 

DB Changes

Screen: Bank

Tab: Bank Account

Field: Bank Account Type

Added new type as Credit Card

Bank Account and Bank Statement Form

On Bank Statement Form: 

1. Handle Confirm dialog for Delete button. 

2. Handle Busy Indicator for Process and Unmatch button. 

On Bank Statement Form:

1. Mandatory validation on fields like Show Label with Astrik if fields are mandatory.  
1.2 Bank Account Organization is different from the Login Organization at that time system should show the Business Partner info data or records as per the Bank Account organization. 
1.3 Handle Message for Currency and Conversion Type.

2. Bank Statement Form:  During load statement against different account number which is exist on Excel file then System will give the message: Statement with Different Bank Account. Can't Import.  

3. Handle Please Enter Amount Message when Voucher is selected as payment and Difference type is selected as Charge without any selection of Payment / Invoice / Order reference.

4. Bank Statement Form:  In Payment Control – not to show reconciled payment. 

5. Handled issue to enable/disable the check date field on bank statement form according to EFT Effective date field on statement line tab.

6. Implemented zoom functionality now when a user clicks on the zoom for the prepay order field in Bank statement form then it will redirect to the sales order window.

7. Implemented zoom functionality now, when a user clicks on the zoom for the Trx organization field in the Bank Statement form, it will redirect to the Organization Units window. 

8. Handle amount in German culture. Example- When user input amount (1400,00) system will convert it to (1,40). 

9. Previously, if a user matched a statement, the system would generate duplicate data after matching the record. Now, the system no longer duplicates data.

10. Appended the Callout code for C_Charge_ID in CashLine Tab on Cash Journal Window.  

10.1. Changed Entity Type as "Other Customization, added check in where clause, if is not customized then only this script will work.  

11. Previously, when user use "Match Statement" option for matching statement then after matching statement system was not showing the amount in match statement grid with culture. Now, system will show the amount according to culture. 

12. Previously, when user use Match Statement" option for matching statement then system was matching the amount up to 2 precision value amounts. Now, system will match payment (transaction amount) with statement amount beyond 2 precisions. 

13. On Bank Statement Form - Previously, when either payment or cash journal record was created with Invoice / Order reference and the record is not completed then system showing the same Invoice / Order reference. Now, system will not display those transaction record whose reference is exist either on Payment or Cash journal in other than completed status.

On Bank Statement Form-The statement date entered by the user should not surpass the current date when different time zones are taken. 

1. Handling issue of trailing junk after numeric literal on PostgreSQL 15.

2. On Bank Statement Form - Previously, when either payment or cash journal record was created with Invoice / Order reference and the record is not completed then system showing the same Invoice / Order reference . Now, system will not display those transaction record whose reference is exist either on Payment or Cash journal in other than completed status.