MAF CLOUD - NEW RELEASE + FIX UPDATES JUL 2023
31 JUL 2023 - VERSION 3.1.7
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
data migration excel upload
file upload:
|
|
| |
physical trade - contract delivery date should not be highlighted once conditions are fulfilled, so it is caused by decimal point bug fixed 库存明细数据带入合同页小数点问题 |
|
| |
issue invoice table - change position of the save and undo button to the red area |
|
|
28 JUL 2023 - VERSION 3.1.7
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
Make columns no editable in PSL & Invoice update restriction (it means those rows have psl_id) In PSL, RECEIVE and ISSUE, both assigned and unassigned (only tables, not include allocate window), set all columns no editable except CONTRACT NO.
for insert new one, still allow user to edit before saving. | Enhancement |
| |
1) in new phy trade, if the trade mode is import/export, contract ccy is USD but the received invoice is in CNY, because the value added tax invoice is issued by the customs and not the counterparty, so there will be 2 issues
so in these situations, how they assign the contract no? the issue is:
2) domestic purchase contract, export sale contract (similar to import purchase contract) for domestic purchase contract they will receive value added tax invoice from counterparty. for domestic sale contract they will issue a value added tax invoice, so the input tax can be offset against the output tax however, for domestic purchase contract that correspond to export sale contract, the export sale contract is usually denominated in USD. In this case, they will need to deduct the quantity and amount corresponding to the purchase contract from the invoice reserve. This means they have to virtually issue an invoice with a quantity matching the contract qty and an amount matching the corresponding purchase contract's amount. The problem arises when the sales contract is in USD, but the invoicing currency is CNY. In this situation, the invoice and the contract will have the same quantities, but the invoice amount should correspond to the amount in the purchase contract, not the USD amount in the export sales contract. As a result, the invoice amount will not match the contract amount. How should we handle this situation?
| Enhancement |
| |
Copy paste the value, the value is parsed as 29 instead and does not consist any comma on it
dashboard some apps cannot open | Enhancement |
| https://mafint.atlassian.net/browse/MAF-4057 |
estimated price and settlement price in updated settlement table
| Enhancement |
| |
BE: KGI 2 yrs note pricing issue. | Enhancement |
| |
enter any trade execution and click on save got this error | Enhancement |
| |
stock mgmt table
stock mgmt table - back to back page:
| Enhancement |
|
22 JUL 2023 - VERSION 3.1.7
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
phy trade settlement issue trade qty different from settlement actual qty this issue is because update phy trade access level is group, which makes user can not update phy_pricing, trade and portfolio calculation accordingly. How test:
if it is correct, then this ticket fixed. | Enhancement |
| |
stock management pair details update stock in/out page branch out into 2 pages - stock in/out and back to back if btb, user will input in btb page directly
so new logic for stock in/out - user will not add new row in stock in/out page to input. user will only input stock in and out details and then pair them directly via the pair button in stock details page, and all paired items will appear in the stock in/out page.
so in BTB page, when select contract no., same current logic remains but dont need to auto fill these qty cus they will usually manually input qty
so above written logic is correct, they will only need to input qty (out), so qty (in) and contract qty (in) will be autofilled with qty (out) qty variation column formula in BTB table = qty (in) - qty (out) so this should match with bal qty in stock details page | Enhancement |
| |
table auto size issue fixed | Enhancement |
| |
in new phy trade table, the stock qty column should use contract qty in stock management page, if dont have then use qty in stock management page, unstock qty calculation is the same logic = UNSTOCK QTY = CONTRACT ACTUAL QTY/QTY(physical trade table) - STOCK QTY (physical trade table) [for reference stock qty is also CONTRACT QTY(stock details)] | Enhancement |
| |
in settlement table, the summary calculation at the bottom is wrong | Enhancement |
|
21 JUL 2023 - VERSION 3.1.7
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
stock management add columns qty variation calculation update | Enhancement |
|
20 JUL 2023 - VERSION 3.1.7
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
Minimise column should not auto go back to default when input data or copy and paste data, or switch page | Enhancement |
| |
Ps ledger/invoice (receive and issue) - can view assigned table even though is group level bug fixed | Enhancement |
| |
| Enhancement |
|
19 JUL 2023 - VERSION 3.1.7
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
add pricing price, contract premium and contract tax rate columns (from trades table) into settlement table when input contract tax rate in trades table, it should auto fill both contract tax rate and settlement tax rate in settlement table settlement tax rate should be editable, same logic as settlement qty and settlement price if settlement tax rate is empty, auto fill it based on contract tax rate. (if empty only) | Enhancement |
| |
settlement tab match product and category product is input in trades table, will be auto filled in settlement tab user can input category in settlement table, and category will be linked to the product so when the same product is shown in settlement table, the category will be auto filled. but category is also editable in settlement and updated settlement table if edit category in settlement or updated settlement table, the category will be updated for the product in settlement table but existing row with old category in updated settlement will not change | Enhancement |
| |
add date to psl combination logic current psl logic: only PSL with same THIRD PARTY, LEDGER TYPE, CCY and COMPANY are allowed to combine, will sum up all AMOUNT new logic: please add DATE too, so only psl with the same DATE, THIRD PARTY, LEDGER TYPE, CCY and COMPANY are allowed to combine | Enhancement |
| |
add contract amt column in settlement table | Enhancement |
| |
settlement table and updated settlement table: positive/negative signs for all qty and amount columns to follow trade table’s logic: purchase will be positive, sale will be negative | Enhancement |
|