You are on page 1of 28

Item Type CR Owner Topic

To reconcile the gap between VSE summary report and


28 CR FIN OPS Commercial P&L report, need to add 4 columns in VSE summary
report for accrual amount of Transfer/Delivery/Handling/Rental.
Enhance Consumption and DLOC reports by adding cost
29 CR FIN OPS
estimation for NPD with BOM not yet maintained.
1. to correct the record which was input in wrong format (write
off) 2. add 'company code' dimension for Budget Contract Price
30 CR FIN OPS
upload to allow different price for one material in different
company (PPV)
To improve accuracy of STD cost in Production result reports
34 CR FIN OPS regarding those common SKUs that planned for one plant but
actually produced in another plant.
Change BI report provision calculation rule according to
35 CR FIN OPS business change

For NPD and trial cost, 1> to allow shift NPD cost to corresponding
36 CR FIN OPS manufacturing type cost when a NPD output is released 2> add
logic to split company level NPD cost to plant level for P&L report

Enhance forecast PR report by adding a set of top-down


37 CR FIN OPS calculation logic for DPC variance to better support business usage
and improve accuracy of prod P&L report.
Improve actual PR accuracy by adding logic for the new business
needs and reconcile the gap identified between BI report and
offline version: 1>to split cost of SFG manufacturing types to FG
38 CR FIN OPS manufacturing types (for new product imported from Vietnam) 2>
to take NPD release into consideration 3> delete the restriction of
PO date

Open PO
The CR is raised to enhance the data capturing logic of condition
40 CR FIN OPS types related to 'Freight/Quantity' field in R222.
1. Modify the data source of the currency unit 2. Capture data of
PER column to calculate per unit price.

R077中QI provision的mapping表需增加这三个location,计提规
49 CR FIN OPS
则同0002

#Classification: Internal
Overall Status
(Planning/Not Start/In Expected
Priority Biz Owner BI Owner CR Raise date
process /Completed/ Start Date
Cancelled/TBD)
Jim Yan:
for part 1 will start at
Completed 1/14/2022 Medium
9th May
Amanda 1/7/2022

In process 3/25/2022 Medium Amanda 2/8/2022

Completed 2/24/2022 Medium Amanda 2/17/2022

Completed 4/1/2022 High Amanda 2/25/2022

In process 4/20/2022 Critical Amanda 4/12/2022

Planning 5/9/2022 High Amanda 4/20/2022

Planning 5/30/2022 Amanda 4/20/2022

In process 4/20/2022 High Amanda 4/20/2022

In process 5/5/2022 Critical Alva Wang 4/27/2022

In process 5/25/2022 Medium Xifeng Amanda 5/13/2022

#Classification: Internal
Business Solution Status CR Status
(Solution sourcing / Solution (No CR / CR raised / CR CR No
confirmed / TBD) approved / TBD)

Solution confirmed CR approved CRF202201011

Solution confirmed CR approved CRF202202001

Solution confirmed CR approved CRF202202013

Solution confirmed CR approved CRF202202036

Solution confirmed CR raised CRF202204014

Solution confirmed CR raised CRF202204028

TBD CR raised CRF202204029

TBD CR raised CRF202204030

CR raised CRF202204037

CR raised CRF202205012

#Classification: Internal
IT Resource
IT Owner IT Receive CR date
(External / Internal / Both)

External 陈建林 1/11/2022

External 陈建林 2/24/2022

Internal Cindy Hao 2/21/2022

Internal Cindy Hao 3/1/2022

Internal Cindy Hao 4/12/2022

External 谢玲亮

Internal Cindy Hao/Jim Yan 4/28/2022

Internal Cindy 5/23/2022

#Classification: Internal
IT Status
PR PO PO Price w/VAT
(Not start/ Developing / SIT /
(Only for external) (Only for external) (Only for external)
UAT / Completed / TBD)

Completed 7000029668 4500161394 18,000.00

Completed 7000030401 4500163106 100,000.00

Completed

Completed

Completed

Not start

Not start

UAT

Completed

#Classification: Internal
Dep IBM IT Total
GR Date
(BI or IT) Days Days Days

J04 BI 4 4 2/15/2022

J04 BI 20 20

4 4

15 15

3 3

4 4

4 4

0.5 0.5

#Classification: Internal
IT Comment Launch date Detail Info link

1/16/2022

#Classification: Internal
Remark

part 1:BI need to help confirm final logic -5/23


logic confirm-5/25
As talked with Alva, need to start dev on 6/8 after month end closing,plan to UAT on
6/15
part 2 completed

logic confirm-5/24 modify in P&L ,not in R212 fcst PR

part 1&2: BI need to help confirm final logic -5/23


part 3: completed

BI need to confirm with users the currency logic -5/7


logic confirm -5/10
Need RSO to enhance data source, plan UAT around 5/20
deliver to UAT 5/18

#Classification: Internal
Item Batch Type CR Owner Topic
R234 FCST Accuracy -Primary Sales & Effective Order
6 batch 1 CR COM
& RRFhike
Price BC3 Update impacted by price hike
1.BC3硬切--Report呈现,除涨价部分均使用最新主
8 batch 1 CR COM
数据
2.DT Inventory期初Adjustment
9 batch 1 CR COM 添加LE0 Version
Factbook / Mix / NPD
7.Add EC portion for MTD, YTD<NPD>

10/45 batch 1 CR COM

11 CR COM Factbook/Mix/NPD planning数据源切换至R066

12 CR COM Cooked v1 & v2 & Copa Check表

13 CR COM Factbook-MS buckets调整:使用Primary PL(Global B)第


二层
14 CR COM RSP/Trade Margin/Ex-factory price/3-star Price 体现涨
价前后价格

15 batch 2 CR COM PL-VSE/Rental Cost-DB二级有未分摊的量

17 CR COM R066 Module B重新设计模板,以及重新做


allocation logic
19 batch 2 PCR IC AI Report
20 batch 2 CR COM R002优化
PL, R066 :SKU使用最新主数据,不使用YTD Closing
25 CR COM
数据
27 CR AR Credit limit CR

For customer service dashboard, replace 'Order


completion date' with release-based 'Required
33 batch 2 CR SC
Delivery date' for monthly OTIF measuring to get in
line with the group KPI definition.

COOKED R066&PL change


1.针对COOKED R066 wave2a的部分:是否能根据
batch 2 TPM level2 限制渠道后进行全摊,主要是需要去除
B2C YTD二级销量进行拆分
39 CR COM 2.PL OVH-Cost Center: Sales adj -General Allocation
(B2C excl.),按照全渠道(去除B2C)的YTD二级销量分
摊,然后再分摊到SKU
#Classification: Internal
COOKED R066&PL change
1.针对COOKED R066 wave2a的部分:是否能根据
TPM level2 限制渠道后进行全摊,主要是需要去除
B2C YTD二级销量进行拆分
39 CR COM 2.PL OVH-Cost Center: Sales adj -General Allocation
(B2C excl.),按照全渠道(去除B2C)的YTD二级销量分
摊,然后再分摊到SKU

Open PO
The CR is raised to enhance the data capturing logic
of condition types related to 'Freight/Quantity' field in
batch 2 R222.
40 CR FIN OPS 1. Modify the data source of the currency unit 2.
Capture data of PER column to calculate per unit
price.

COM P&L BC3 切换


1.sales 部分 BC3切换,增加销售订单月份  
2.lisa TS/MS 增加 PHASING 期间(BC3送给PL) 

42 CR COM
batch 2

Long term 优化策略  10 天


Allocation和P/L相关报表:
1、Allocation和P/L相关报表执行任务合理优化  --
印翔
2、Allocation和P/L相关报表后台数据合理分配存储
空间---TOP50 HANA表,自定义表,数据量
43 CR IT 3、Allocation模型C的历史数据转存到其他服务器
batch 2 ,合理利用HANA内存空间--提供服务器,DS配置

4、提供Allocation和P/L的长期数据存储策略,以保
证长期使用稳定 --提供文档
5、基于第2条服务器中有无重复数据,决定后续操

1.PL 的TREE 按月份落地取数
2. Company PL ,
3.Company Sales PL
4. CM by Brand
batch 2 5.Factbook
6.Mix 报表

44 CR COM

#Classification: Internal
44 CR COM

46 batch 2 CR COM R072中新增字段(参考R066)


47 batch 2 CR COM 二级销售需要区分手工上传和系统直连
New added cost center: MKT-Region affacted Sales
48 batch 2 CR COM
Result

#Classification: Internal
Status IT Start Date IT Complete Date Owner
5/18 Go live
4/11/2022 4/13/2022 何老师
5/18 Go live except
COM PL 潘老师
5/18 Go live
潘老师
5/18 UAT

5/11/2022 5/18/2022 谢老师

5/18 TBC

5/18 TBC

5/18 TBC

5/18 TBC

5/18 UAT
5/5/2022 5/7/2022 何老师

5/18 TBC

5/18 IT evaluation 潘老师


5/18 IT evaluation 何老师

Yin Xiang
5/18 IT Deployment

5/11/2022 6/6/2022 陈老师

5/18 Part 1 IT
Deployment Part 1 Part 1 Part 1
Part 2 UAT 2022/5/23 2022/5/30 Yin xiang

#Classification: Internal
5/18 Part 1 IT
Deployment
Part 2 UAT

Part 2 Part 2 Part 2


2022/5/6 2022/5/7 何老师

5/18 UAT

5/13/2022 5/16/2022 Cindy

5/18 Part 1 IT
Deployment
Part 2 UAT Part 1 Part 1 Part 1
2022/5/23 2022/5/27 何老师

Part 2 Part 2 Part 2


2022/5/10 2022/5/12 潘老师

5/18
Pending ,waiting for TREE 按月份落地 TREE 按月份落 TREE 按月份落
the confrimation 取数 地取数 地取数
from COM FI 2022/05/16 2022/05/17 何老师

Company PL & Company PL &


Company PL & Company Sales
Company Sales
Company Sales PL PL
PL
2022/05/12 2022/05/20 潘老师

CM by Brand CM by Brand CM by Brand


2022/05/30 2022/05/31 何老师

#Classification: Internal
Factbook & Mix Factbook & Mix Factbook & Mix
2022/05/19 2022/05/24 谢老师

Yin Xiang
罗老师
Yin Xiang

#Classification: Internal
IT Solution

1、模型设计(2天)
(1)原有R029模型挑选部分字段
(2)从P&L Database取值模型开发,新增12个字段
(3)拼接及计算所有需要的字段
2、增加报表Sheet页面,包含以上字段(1天)
3、报表测试(1天)
Total 4 天

Need 4 days efforts (IBM),


2.5 day for development and initial testing ,1.5 day for UAT
Total 4 天

customer service报告修改:
1) release item新增billing状态的箱数/重量/体积/金额
2) intake item新增最新的effective order,GIT,SIT的箱数/重量/体积/金额
3)新增发货地疫情影响逻辑
customer service dashboard修改
1) 新增月结版effective order
2) 修改TOP20逻辑
3) 通过控制器latest/Closing及控制器intake/release确认Case Fill及OTIF计算口径:
a)closing version 月结版本
b)latest version 最新状态 + intake
c)latest version 最新状态 + release
Total 20 天

Part 1 :will change internally


Part 2 :Need 1 day effort (IBM)
Total 1 天

#Classification: Internal
Part 1 :will change internally
Part 2 :Need 1 day effort (IBM)
Total 1 天

Will change internally

1.       sales 部分 BC3切换,

增加销售订单月份   ----源CR评估未评估部分,预估4天
2.lisa TS/MS 增加 PHASING 期间(改为增加送BC3英文给PL)  -共3天
     1.R066ForP&L模型 增加BC3(PY也取查询月份),落地存储过程修改送PL落地表 1天
     2.PL模型存储过程处理1天
      3.所有月份数据间歇性查重跑 0天 no charge
      4.测试1天
Total 7 天

Already have PR/PO , 10 days

1. Commerical PL 模型替换1天,测试1天  共2天


2. Company PL    开发4天(含单元测试) + 1天UAT测试 共5天
      说明:YTD,FULL YEAR 取查询月份的tree
                  1.把tree按月保存下来,存储过程开发
                  2.有KPI维度的模型按CM,FULL YEAR,YTD,PPY,PY 分别用KPI_CODE和查询月份关联 查询
月份
                   的Tree
                  3.没有KPI维度的模型(CVC_TPM_R205_MS_TS_FCST_BASE)按LEVEL2 关联mapping表 取

       KPI_CODE 和查询月份关联查询月份的 tree
                  4.把两部分数据拼起来
问题:R066的tree是每一个月带数据存,且数据不能变,但是目前Tree的1-5月没有存 ---lisa决定
彻底性
3. Company Sales PL   模型替换1天,测试1天 共2天
说明,YTD,FULL YEAR,YTG,PY CM 取查询月份的 Tree
FULL YEAR 取法 ACT 数取 period = YTD,如果是过去年份,取YTD,限制月=12月
FULL YEAR 取法 BGT,LE,RRF, 取 period =  YTD,月份取查询月份对应的当年12月, TBD--何老师,等
数据全了,调试执行源代码是否能用,暂时不处理,后续据实估计
4. CM by Brand  开发1天,测试1天 共2天
5. Factbook  开发1天 + UAT测试1天 共2天

#Classification: Internal
1) MTD、YTD、Full Year:取查询年月的tree
2) Full Year:根据查询年月,获取Full Year年月的YTD数据:历史年取12月,当前年取上月,要
注意,tree取的是查询年月的tree
3) tree按月存储,通过存储过程实现
6. Mix 报表 开发1天 + UAT测试1天 共2天
1) MTD、YTD、Full Year:取查询年月的tree
2) Full Year:根据查询年月,获取Full Year年月的YTD数据:历史年取12月,当前年取上月,要
注意,tree取的是查询年月的tree
3) tree按月存储,通过存储过程实现
Total  15 天

#Classification: Internal
Remarks

#Classification: Internal
#Classification: Internal
#Classification: Internal
Back

# Dashbaord Issue list-CN Issue list-EN


Move up the first
所有dashboard 第一个标题 往上 title of all
1 ALL A1
挪动 dashboards.
Evaluate whether
adding a RESET
Region+ office 是否开个加reset button for Region+
2 Sales perform A5
重置 按钮,评估是否可行 office is feasible.

3 ALL
Make the font color
所有dashboard 第二标题 字体颜 of second titles
4 ALL A2
色一致 consistent.
The selected filter
should have a more
contrasting color
所有筛选器,选了某个区/某个选 than the unselected
项的话,跟没被选的选项,颜色 ones.(When we
5 ALL
设得对比鲜明一点(选择东区 其 select East Region,
the other regions
他颜色暗一点,颜色区分) will be darker.

The layout of A&B


is too loose on the
top and too tight on
A+B 布局上都是上面太宽松,下 the bottom. Move
up the whole
面太紧, 整体上移, layout.
6 ALL
部分用户大区办事处 无法显示完 The regional offices
整 of some users
cannot be displayed
in full.

Blank space: this


part has too much
space and needs to
Blank space:这部分太空 需要 adjust, while the
following
调整下,下面筛选器(大区 办事 filters(regions,
7 Sales perform A3
处)太挤,有些用户都挤在一起, offices) of some
整体上移一些 users are too
crowded. Move up
the whole layout.

Add vs.PY in the red


8 Sales perform A4 红圈中 + vs. py circle.
Evaluate the
feasibility of adding
整表增加MTD/YTD 按钮,请评 MTD/YTD to the
9 Sales performace
估性能 dashboard.

#Classification: Internal
Add a PY line chart
that does not
‘+PY曲线图 不参与互动(点击 participate in the
10 Sales Trend B1
某天显示 ,显示表头数据) interaction.

Add Sales sort, click


11 Sales Trend B2 rank 销量排序(点指标 rank) Sales to sort.

中间那个折线图,还未发生的日期 Hide the future


12 Sales Trend B3 dates in the line
,曲线不要为零 不需要显示 chart.
The dates display of
13 Sales Trend B4 日期部分用户显示不全
some users are not
complete.

14 Sales order C1 Space-请调整对齐 Align the space.


增加销量排序,点击order 进行排 Add Sales sort, click
15 Sales order C2 order to sort.

16 ALL 字体一样

17 Sales order

#Classification: Internal
Next Step 红色是Cherry的反馈
需要apple 认证,待商议 所有dashboard 第一个标题 往上挪动
一点

陈老师 investigate, office可以reset,但是re+F10:G10gion


是以一个crosstable作筛选器用,无
法reset---不在tableau做,在
dashboard 层面做一个恢复到初始界

去掉画竖线的这些边框
Cherry三个dashboard 确定一个 样式 Calibri 黑色 大小一致

选中的字体可以改个颜色--字改成黑
色East, office 和 this month 一致

可调整
陈老师 investigate

可调整

陈老师 investigate, 可以添加


4 Months data

24 Months data,影响性能 不建议添加,

#Classification: Internal
Cherry 确认,2条线都会互动,是否需 可以互动
要开发 但灰色banner 不显示PY信息 仅显示
Current Year

Cherry 确认,目前加标记 没反应,确实 默认改到 sales act 排序


act or bdg 排序
陈老师 开发,为发生天为空 可调整

同问题2,改布局 可调整

陈老师 investigate 可调整


Cherry 确认,目前加标记 没反应,确实
act or bdg 排序
同一个页面中的标
题,filter、crosstable用的字体是不
陈老师 investigate 字体 是否一致
一致的,sales order字体Shaun设置
的,是否按这版调整---
Sales order dashobard 去掉框

#Classification: Internal
16.2

备注 A
CR+苹果重新发布 A
1

CR+苹果重新发布

CR+苹果重新发布
A2

A3

A4
CR

CR

#Classification: Internal
CR

CR

#Classification: Internal
B C
A
1

B4 C
2

A2

C
1

B1

A5

#Classification: Internal
B2

B3

#Classification: Internal

You might also like