MAF CLOUD - NEW RELEASE + FIX UPDATES SEP 2023
29 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
Petro Win New app requirement -P/L & Position Change From Daily Open Position app 当日开仓持仓盈亏和仓位变动 | Enhancement |
| |
230927 开票页面添加出入库日期 在开票页面的上面框里,添加列:出入库日期(带入合同页的出入库日期)
| Enhancement |
| |
| Enhancement |
| |
| Enhancement |
| |
| Enhancement |
| |
| Enhancement |
|
27 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
issue invoice can not save, FE exception urgent! | Enhancement |
| |
230925 实际价格为0的合同 我们有一部分合同实际价格为0的合同,是否终价显示的为否,能否改为实际价格为0的合同,是否终价显示为是?因为在我们理解中,合同实际价格空着不填的才是否,有些合同确实价格为0,比如盘盈盘亏,还有一些样品出口的合同,如果显示为否,我们在一些报表里就会看到这些合同(未点价合同表,未了结合同表等等) if empty or null, it is false, if having value including 0, then true.
| Enhancement |
| |
add total_actual_stock_qty in phy trade database
| Enhancement |
| |
new requirements VAR report (Background) Each portfolio has a max allowed loss amt, so they want to a % to show % of VAR and Shortfall value. 2 things needed for this new requirement:
Please add two percentage parameters in the Var chart. The formula is as follows:
VaR% = |VaR| / |Max allowed loss amt| * 100 Shortfall % = |Shortfall| / |Max allowed loss amt| * 100 var% and shortfall% keep to 2 dp change to 最大亏损金额(自定义 put sample below shortfall % | Enhancement |
|
26 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
230925 开票 FE exception |
|
| https://mafint.atlassian.net/browse/MAF-4262 https://mafint.atlassian.net/browse/MAF-4272 |
230925 报表更新
1) 添加列:追保价(含升贴水)---在现在追保价的基础上,加上升贴水,计算得出追保价(含升贴水)contract_prem 2) 添加列:合同约定追保比例 ---带入现货合同页的合同约定追保比例
添加列:采/销---带入现货合同页的采/销
添加列:公司名称---带入现货合同页的公司名称
添加列:交易日期---带入现货合同页的交易日期 |
|
|
25 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
230922 采/销售量汇总 ensure they have the same settings to get correct result. we use group or company level to control data access scope.
| Enhancement |
| |
230922 出入库计划表 -group账号查看 open settings, change the group keys and resubmit. issue 1: change settings or close app and create a new app issue 2: change it to group level if it is group level. | Enhancement |
| |
add ? logic explanation in column header try to list down necessary column in this ticket to add going forward.
| Enhancement |
| |
cannot enter market data | Enhancement |
|
22 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
|
|
| |
|
|
| |
|
|
|
21 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
|
20 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
|
19 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
add custom tax rate 关税日期 column in updated settlement table | Enhancement |
| |
230918 日期输入方法 in phy trade table, if trade_date not in this year (2023) before saving, show yellow color, so at least to warning user that the date may incorrect. | Enhancement |
| |
230918 商务报表更新 现货追保及止损表 bug fixed | Enhancement |
| |
phy trade page FE exception can not save after updating edit or add new row in phy trade table and save see can save successfully or not. | Enhancement |
|
18 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
230816 库存明细 上级group add username, group and created by etc columns in back to back table add product column in back to back table | Enhancement |
| |
230831 更新的结算价 价格不一致 enhancements settlement tax rate (结算税率) is empty , most of the trade modes except OFFSHORE are depends on it to calculate price before tax ,if settlement tax rate is not filled , price before tax would not be calculated and thus settlement amt before tax would not be calculated as well. if it is not filled, then treat it as 0 tax rate. | Enhancement |
| |
group pl duplicate issue it is empty list issue. anyway, if it is empty list, then BE would not yield to FE. seems like it work now.
| Enhancement |
| |
发票存量表 enhancements; invoice balance report it happened when there is not match_id value in stock_mgmt data. I have made some modification in code to cover this kinds of case.
| Enhancement |
| |
230915 库存明细-默认出入库 in stock mgmt and bulk stock mgmt (in new phy trade) if purchase → stock action auto stock in else stock out | Enhancement |
| |
230915 取消的合同 add status column in cancelled trades to determine which contracts have their settlement deleted | Enhancement |
|
15 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
发票存量表 enhancements; invoice balance report in settings: group keys should be
in table, keys are:
BE has done is_pair part, need FE to update something to work
| Enhancement |
| |
230915 开票-单价小数位显示错误 今天有一笔开票,数量为33.234吨,单价为8001.151,金额为265910.25,数量和金额都没问题,但是单价只显示两位小数点,点全电开票以后下载的开票申请里的单价是8001.15,导致产生错误,请帮忙修改一下单价的显示,不要保留两位小数,显示为我们实际的价格,开票的时候,数量和单价都可能会有多位小数点,只有发票金额需要保留两位小数点。 都显示实际的价格吧
| Enhancement |
|
14 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
230911 合同拆分后续 2) 合同拆分后,原合同和新拆分来的合同的约定仓储名称和约定仓储地址都没有了 3) 合同拆分后,原合同和新拆分的合同的合同实际数量还是原来的合同实际数量(修改为原来的合同实际数量就留在原合同里,新拆分出来的合同的合同实际数量空着) 4) 合同拆分后,新合同以下信息缺失:签署、合同版本、合同类别、收付款方式、约定收付款日(这些应该都与原合同保持一致) 5) 合同拆分后,新合同是否可以自动生成合同编号?不用再手动点一下生成合同编号 目前拆分合同只能拆分数量,是否可以在拆分框里多加点信息? 1) 在均分交易后面显示合同号和客户名称(不允许修改,只是方便商务在拆分的时候知道自己在拆哪个合同) 2) 在拆分数据信息里增加:客户名称, 品牌,产品规格,临时价格,合同实际价格,合同升贴水(这些信息自动带入原合同信息,但允许修改) | Enhancement |
| |
商务报表-未了结合同表 enhancements 1)未开票数量为0的合同还显示为部分开票,以下合同应该为已完结,不显示在未了结合同表里(第一个浙江济桐的合同不知道为什么有两个已结算) 2) 请添加列:采/销 目前合同数量采购和销售都是正数,因此请添加列:采/销,并将销售合同数量显示为负值,方便我们看报表的时候检查一下 | Enhancement |
| |
230914 收票录入重复 今天在补录进口收票的时候,发现记录也重复了,但是很奇怪,53.62吨的收票在刚保存的时候看是重复了,结果刷新以后再看又不重复了,但是48.655吨的收票刷新以后仍然是重复的 | Enhancement |
|
14 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
230816 库存明细 上级group
| Enhancement |
| |
230831 商务报表-未了结合同表 PHY TRADE ON GOING STATUS
| Enhancement |
| |
出入库计划表 stock mgmt plan enhancements missing columns added
| Enhancement |
| |
230911 款项余额为0的合同如何进行收付款认领 currently, in psl table, dropdown list only show un_payment_amt is not 0 contract to assign. they have some special case to handle. sometimes, they need assign psl to un_payment_amt is 0 contract. such as refund, top-up margin etc. so our solution
| Enhancement |
| |
230913 采销资金 无法认领 allow changing of ledger type in ps ledger table and ps ledger allocate (middle table); invoice and received invoice remain unchanged | Enhancement |
| |
change phy trade qty new logic to settlement:
| Enhancement |
| |
dashboard - the dashboard data cannot be refreshed in real time for certain account | Enhancement |
|
13 Sep 2023 -VERSION 3.1.7.0
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
issue invoice cannot save after changing from usd value to cny value
| Enhancement |
| |
stock mgmt plan enhancements the correct logic below:
| Enhancement |
| |
230904 合同页未收货/出库数量计算不对 qty, actualQty, contractActualQty is under phy trade directly. buy is positive and sell is negative. so we keep them stock_qty different, BE will do calculation of stock qty. so we should keep sign of stock_qty from BE. | Enhancement |
| |
230831 更新的结算价 价格不一致 enhancements
Exchange Rate is treated as 1 if they didnt input anything on that column
If phy trade mode is IMPORT / EXPORT (转口) or OFFSHORE-CROSS CCY (转口), | Enhancement |
| |
split trade action in phy trade table | Enhancement |
|
|