活动
从 2020-12-14 到 2021-01-12
2021-01-12
- 17:37 错误 #168 (已解决): SO订单 页签信息 结算方式选择acount 时,对应业务类型应为赊销 下推 应收单上业务类型则显示为现销
- 除解决上述问题外,同时希望可以把提供表格中的历史数据 AR对应应收单里的销售类型现为现销都需要刷成赊销
- 14:58 Digi-Key Requirement 支持 #167 (已解决): 顺丰接口路由查询历史数据清理及程序优化
发货通知单中,有大量没有标记为成功的运单号,顺丰这边不会返回错误,金蝶这边也就没有标记为签收,就一直存在系统里面,越积越多
!clipboard-202101121456-n2xiw.png!- 10:50 Digi-Key Issue Tracking List 错误 #166 (新建): SO审核后更改需要重新信用客户解锁的问题
- SO审核后进行更改,发现对结算方式为account的订单,更改时需要重新再次输入解锁密码,但是PO更改时并不需要,针对订单更改操作时,请将此解锁密码的要求去除
!clipboard-202101121050-iaoti.png!
- 10:48 Digi-Key Issue Tracking List 功能 #165 (已解决): 深圳顺丰相关账号在金蝶中权限修改
- 鉴于UPS项目即将开通,后续在发货通知单序时薄里会存在:1,深圳顺丰手动发货的单据;2,上海顺丰发货系统自动产生的单据;如下图无顺丰单号的订单即是UPS模式下系统自动产生的单据。
请修改深圳顺丰相关账号权限,使其查询时只检索有顺... - 10:40 支持 #164 (已解决): 系统上线的接口问题排查
- 1月8日系统上线的接口出现一些问题,进行排查解决处理
2021-01-11
- 14:26 功能 #163: 大学客户资料对应销售员信息按表格刷新
- !clipboard-202101111426-kzour.png!
- 14:19 功能 #163 (已解决): 大学客户资料对应销售员信息按表格刷新
- 更新客户资料中对应销售员信息
2021-01-07
- 20:14 错误 #162 (已解决): SO单基础页签输入“顺丰运输”字段信息,物料明细以及下推PO单均未带出,以及希望在采购收货单序时簿增加“顺丰运输”筛选条件
- 1、SO销售订单界面 上面页签顺丰运输字段输入信息后,物料明细中顺丰运输字段信息未带出。
2、SO销售订单下推PO采购订单顺丰运输字段信息没有带到PO订单。
3、在采购收货单序时簿增加“顺丰运输”筛选条件
!clipboard-... - 19:41 Digi-Key Issue Tracking List 错误 #161 (已关闭): 采购发货单上物料基础资料中“原产地”字段信息取值有误
- 采购收货单中原产地“马其顿”正确名称应为“北马其顿共和国”,856接口过来的英文,系统自动更新成中文,感觉是接口的配置表需要修改
!clipboard-202101071938-jbxm1.png!
- 16:39 Digi-Key Issue Tracking List 错误 #160 (已解决): Order Notes coming as text “null”
- 16:34 Digi-Key Issue Tracking List 错误 #160: Order Notes coming as text “null”
- I found that the value of "ordernotes" is obtained from "company information" in customer information. Now, the value...
- 16:34 Digi-Key Issue Tracking List 错误 #160: Order Notes coming as text “null”
- This issue is with PO approval process and here the url http://10.10.128.126:8078/services/mule/salesorderservi...
- 16:32 Digi-Key Issue Tracking List 错误 #160: Order Notes coming as text “null”
{
"login": {
"username": "kingdee",
"password": "kingdee...- 16:31 Digi-Key Issue Tracking List 错误 #160: Order Notes coming as text “null”
- ISA*00* *00* *ZZ*DKCHINA *12*2186816674 *201216*1823*U*00401*100207833*0*P*^~ GS*PO*DKCHINA*2186816674*20201216*0000*...
- 16:31 Digi-Key Issue Tracking List 错误 #160 (已解决): Order Notes coming as text “null”
- • 12/10 : Kingdee PROD patch is stable after small fixes, working as expected
n Order Notes coming as text “null” i...
2021-01-06
- 16:28 Digi-Key Issue Tracking List 支持 #159 (已解决): EDI850 file update testing
- Here is a sample EDI850 file. You would need to replace the highlighted number with a KD Customer ID for testing:
...
2020-12-28
- 11:58 Digi-Key Requirement 错误 #158 (已解决): UPS补充需求
- 1,在销售订单序时薄里,增加筛选条件: Ship Carrier;
2. 货物离开UPS Shanghai,系统自动生成、提交、审核“采购入库单”,且所入仓库为“UPS 上海商品仓库”;请帮忙确认系统具体是如何/何时触发生成入库单的... - 10:49 Digi-Key Issue Tracking List 错误 #157 (已解决): "OrderNotes":"null"
- 10:48 Digi-Key Issue Tracking List 错误 #157: "OrderNotes":"null"
- Thanks Lanlin for the update, I will discuss with our team and it will be an easy fix our end and we will take care...
- 10:47 Digi-Key Issue Tracking List 错误 #157: "OrderNotes":"null"
- I found that the value of "ordernotes" is obtained from "company information" in customer information. Now, the value...
- 10:46 Digi-Key Issue Tracking List 错误 #157 (已解决): "OrderNotes":"null"
{
"login": {
"username": "kingdee",
"password": "kingdee...
2020-12-23
- 15:05 Digi-Key Issue Tracking List 功能 #156 (已解决): UPS项目上线急需KD优先修复/优化栏目汇总
- 1、在销售订单序时薄里,增加筛选条件: Ship Carrier;
!clipboard-202012231457-jfncw.png!
2、货物到达浦东机场,系统更新抵港时间到--采购收货单”ATA HK”栏位;人工提交、审核采... - 14:48 Digi-Key Issue Tracking List 错误 #155 (反馈): HKEL拦截流程
- 正常情况下HKEL勾选了是的话,该SO就不能继续审核出货,而是应该有弹窗提示的;
现发现一张SO HKEL勾选了是但是仍然有继续审核出货,RMB总金额是1198.65,这单我们就需要销毁处理;
请确认下为何未有拦截并及时修...
2020-12-21
- 14:06 Digi-Key Requirement 错误 #154 (进行中): [Not Started]Order Notes coming as text “null” instead of null during PO Approval call , Raj has a made code change to support both formats
- 14:06 Digi-Key Requirement 错误 #154: [Not Started]Order Notes coming as text “null” instead of null during PO Approval call , Raj has a made code change to support both formats
- 未明确接口,根据提供的json查询,所查询涉及到的代码未修改过,涉及到的视图未修改过
视图为V_WS_PO2WebINFO和V_WS_PO2WebExEntryINFO - 14:04 Digi-Key Requirement 错误 #154 (已解决): [Not Started]Order Notes coming as text “null” instead of null during PO Approval call , Raj has a made code change to support both formats
- Robert,
This is issue is or PO approval, if you look at below payload from Production for Ordernote...
2020-12-17
- 14:04 Digi-Key Requirement 功能 #130 (已解决): UPS项目上线急需KD优先修复/优化栏目汇总
- 14:00 Digi-Key Requirement 功能 #64 (已解决): 07-Mark modified data from Web order PDF onto SO in EAS
2020-12-16
- 16:13 Digi-Key Requirement 错误 #151 (已关闭): 调整销售订单界面展示框顺序
- 与152关联,此处关闭
- 16:09 Digi-Key Issue Tracking List 错误 #153 (已解决): PO单拉式新增采购收货单后,提交报错
- 新增采购收货单时,点击拉式生成按钮,选择多料品收货的采购订单中选取一种料品新增,保存单据后提交报错。 !
!clipboard-202012161607-3homq.png!
! - 14:44 Digi-Key Issue Tracking List 错误 #152 (已解决): 销售订单保存、提交、删除按钮位置需要调整
- 当前按钮位置顺序不对,需要调整按钮位置为正常状态。 !
!clipboard-202012161444-2r0jg.png!
!clipboard-202012161444-bffsu.png!
!
2020-12-14
- 15:42 Digi-Key Requirement 错误 #151 (已关闭): 调整销售订单界面展示框顺序
- 顺序修改为保存、提交、删除 !
!clipboard-202012141542-nc6h4.png!
! - 14:12 Digi-Key Requirement 错误 #144 (已解决): Create Customer CITY and PROVINCE Issue in TEST
- 12:15 错误 #150 (已解决): 带有杂费列PO下推报错处理
- 带有杂费列PO下推报错处理 !
!clipboard-202012141215-0suyd.png!
! - 12:10 错误 #149 (进行中): SF顺丰快递单号升级
- 1. 顺丰运单号段位数升级方案
2. 顺丰快递面单调整
导出 Atom