/
MAF CLOUD - NEW RELEASE + FIX UPDATES MAY 2023

MAF CLOUD - NEW RELEASE + FIX UPDATES MAY 2023

31 MAY 2023 - VERSION 3.1.5

Issue/Request

Type

User Guide

Jira Ticket

Issue/Request

Type

User Guide

Jira Ticket

  1. Receive Invoice - Main Contract No. empty after allocate bug fix

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3857

2. In company data, “PRODUCT” has two different INVOICE NO. with same ITEMS (2), TAX CLASSIFICATION NAME(1234) and same TAX RATE (12 )

But I can only find one record (INVOICE NO. = INV_GROUP_NO2) in dropdown list of ITEMS in issue table

ONCE we choose the contracts from upper table, dropdown list of ITEMS is supposed to show all the possible combinations of INVOICE NO., ITEMS, TAX CLASSIFICATION and TAX RATE under this product.

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3866

3. company data invoice - cannot copy (ctrl + shift + v) bug fixed

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3867

30 MAY 2023 - VERSION 3.1.5

Issue/Request

Type

User Guide

Jira Ticket

Issue/Request

Type

User Guide

Jira Ticket

  1. Optimize the interface above the table

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3855

2. RECEIVE allocate window - UN INV QTY issue fixed: User manually adjusts the quantity and amount of contracts to match the numbers exported from the tax system. However, in the 3rd panel, UN INV QTY still appears in red because the system did not treat “0.0000” as 0.

Amount, below 0.05 will assume as 0

Qty, below 0.0005 will assume as 0

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3861

3. Bug in receive table after assign

After user assigned the contract in the RECEIVE table, they noticed an additional record in the unassigned page. The underlying cause of this bug is similar to MAF-3861, where the system failed to treat "0.00" in INV AMT as 0, resulting in an extra update of a new record.

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3862

4. in Unassigned tab only (phy_trade_id empty)

  • only INVOICE rows with same “开票日期,商品名称,规格型号,单位,税率,销方名称, 税收分类编码“ and recalculate the sum of “发票数量,转换后数量,未开票数量,发票金额,未开票金额, 不含税金额,税额“”

  • DATE will be the latest one

Now we have no tax rate (税率)column in table, FE calculate tax rate

tax rate = 税额/不含税金额

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3860

5. PS LEDGERS

Assigned page: MAIN CONTRACT NO., QTY, PRICE

Allocate window 2nd panel: MAIN CONTRACT NO., QTY, PRICE

QTY use qty and contract actual qty from physical trade (priority: contract actual qty > qty)

PRICE use provisional price and contract actual price (priority: contract actual price > provisional price)

 

RECEIVE

Assigned page: QTY, PRICE, CONTRACT AMT

QTY use qty and contract actual qty from physical trade (priority: contract actual qty > qty)

PRICE contract actual price DO NOT USE PROVISIONAL PRICE

FE calculate CONTRACT AMT (QTY * PRICE)

 

ISSUE

upper table: CONTRACT AMOUNT (from physical trade)

 

Add Created by and Updated by time and date for both ISSUE and RECEIVE

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3857

29 MAY 2023 - VERSION 3.1.5

Issue/Request

Type

User Guide

Jira Ticket

Issue/Request

Type

User Guide

Jira Ticket

  1. Updated settlement filter T not equal to S issue

the correct logic:

  1. if settlement qty != (contract actual qty or qty)

  2. if settlement price (actual_price) != contract_actual_price [ensure null and empty convert to empty]

  3. if tax_rate (settlement tax rate) != contract tax rate [ensure null and empty convert to empty]

use closeto to compare two value.

tot = number of decimal from settings + 1

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3825

2. in issue invoice tab last table un inv qty and un inv amt cannot be positive

same logic as received invoice

if sign of un inv qty and un inv amt is different from initial sign of inv qty, con qty and inv amount, highlight in red and cannot save 

reference:

  1. in RECEIVE window, if any of the point validate check failed, can not save

    1. in the 1st panel, if latest sign of amount is different from initial sign of amount, highlight in red

    2. in the 3rd panel, if sign of un inv amt is different from contract amt, highlight in red

    3. in the 1st panel or in 3rd panel

      1. if one of un inv qty and un inv amt is 0, the other is not 0, highlight in red which which is no 0

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3854

3. issue tab delete bottom table row issue - in issue tab select all rows in top table and they will appear at bottom table but when delete 1 row in the bottom table, all the rows will return in the top table instead of 1

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3859

4. Auto contract

They only can auto generate contract no for one main contract no one by one.

so to solve this issue. We use BE to handle

  1. remove Action column

  2. remove AUT CO popup window code in FE

  3. add AUTO CO button before NEW TRADE

  4. user can multi-select rows

  5. and then click AUTO CO button

  6. FE to call auto_co API to BE to generate contract no for selected row and update in the FE table

  7. press Save button to update in BE

FE

  1. filter out from selected rows

    1. contract no has value

    2. main contract no is empty

  2. pass value to BE:

    1. dict

BE

  1. select all main_contract_nos trade from database

  2. use current FE logic to auto_generate contract_no for each main_contract_no

  3. return format and update contract no based on phy_trade_id

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3786

5. RECALCULATE bug in receive and issue

In invoice receive and issue table, after recalculate, un_inv_qty is not updated.

un_inv_qty = un_inv_qty - (con_qty or psl_qty)

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3850

26 MAY 2023 - VERSION 3.1.5

Issue/Request

Type

User Guide

Jira Ticket

Issue/Request

Type

User Guide

Jira Ticket

  1. Unit convert bug in psl

in psl window or table

when update amt, there is a bug due to no unit to convert. need to handle it

in psl, receive, issue table or window, to test update amt, qty correctly.

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3846

2. PS ledger allocate 2nd panel amt did not change bug fixed

when add new row in 2nd panel and input amt, the amt in 1st panel does not get deducted accordingly

seems like happen for trades with no contracts in 3rd panel

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3847

3. Issue invoice bug fixed:

  • after delete row in last table, it does not return to first table automatically

need to click on search or refresh then can see the row

  • after click a row in first table, it will appear at the bottom table

but after change the unit from MT to kilogram, the con qty does not auto update

  • after click a row in first table, it will appear at the bottom table

    the con qty should auto appear

 

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3848

4. in receive and issue tab - even if unit is same should still show con qty

Enhancement

New Physical Trades

https://mafint.atlassian.net/browse/MAF-3849

5. UN INV QTY IS NOT UPDATE IN ALLOCATE INVOICE RECEIVE bug fixed

Enhancement