报表设计说明书样例rddv1抄表计划

1、BW 报表设计说明书2008-12-5BW 设计标准文档抄表计划BW 报表设计说明书（RDD）- 样例Business Information Warehouse (BIW)Page 1 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott Zhu模块DM 抄表与计量管理业务流程参见 CCS 抄表日程（抄表单元）定义流程编号：L5DM - L5DM0005301报表 IDRDDV1.0_DM001报表名称抄表计划报表需求提交部门部报表需求提交程昊创建日期2008.12.05 - 10:

2、14业务分析员张丽娟最后更新日期07.03.21 12:20RDD 状态open, in progress, reviewed, finished关闭BW 报表设计说明书文档说明：ü本文档定义了 BW 报表的需求规格说明，描述了报表设计的要素，是明确需求和进行成果验收的重要依据。文档包含三部分内容：1）业务需求的定义和说明；2）BW 原型设计说明；3）技术设计说明本文档的第 1 部分，即业务需求的定义和说明，应当在需求分析阶段完成；文档的第 2、3 部分，应当在设计阶段完成。文档的当前状态分为：开放、制定中、已审核、关闭四个状态。需求分析阶段开始时，文档属于起草阶段，应当设为开放状态

3、。与用户讨论签收的过程中，可设置为制定中状态。需求分析结束时，用户签收文档，状态设置为已审核。报表设计结束后，即文档的第 2、3 部分完成时， 状态设定为关闭。对于已关闭的文档如需要修改，必须通过 Change Request 审批流程。üüü版本管理：Page 2 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott Zhu审阅审阅人审阅日期版本签字更改版本更改日期更改人更改内容描述1.0BW 报表设计说明书目录目录31业务需求41.1报表描述41.1.

4、11.1.21.1.31.1.41.1.5业务背景4报表的使用目的4报表内容4报表使用. 4其他信息41.2报表界面51.2.11.2.21.2.3表5图5报表展示的特殊需求51.3报表选择条件和分析维度的要求61.3.11.3.2报表可供选择的条件6报表可供分析的维度61.41.51.6数据核对方法和数据粒度6报表使用说明6报表使用范围72原型设计82.12.2数据流8设计分析92.2.12.2.22.2.32.2.42.2.5数据源系统信息9BW系统信息9版本信息9权限10分布式架构的影响102.3业务分析维度122.3.12.3.22.3.32.3.42.3.52.3.6固定过滤器12变

5、量过滤器13自由特性17关键指标19计算指标21其他要求（层级/条件/例外/单元格定义）213技术设计223.1前端配置223.1.13.1.2变量输入屏幕22最终报表展现样式233.2报表WEB页面开发类25Page 3 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuBW 报表设计说明书1业务需求1.1 报表描述1.1.1业务背景üüüü本报表供各供电局报表专责在每周的部例会上使用各供电局专责负责维护抄表单元的年度抄表日程抄表日程

6、可能被多次更新抄表单元和抄表日程的关系与时间无关（即不要求考查主数据的历史变化，仅以 当前时间点的抄表单元的抄表日程来决定所有历史数据）1.1.2报表的使用目的ü本报表的用途是各供电局、营业所的抄表员的工作量是否平衡。1.1.3报表内容ü该报表包含的主要指标是抄表数，支持用户从组织结构和时间维度分析抄表工作 量的分布是否均衡。数据范围包括 2005 年-2009 年 CCS 系统上线以来所有 12 家供电局的抄表计划数据。ü1.1.4ü报表使用部专责和各供电局报表专责1.1.5其他信息üü每年 11 月份，各供电局专责负责维护下一年的

7、年度抄表计划。BW 在每月的月末完全更新未来 12 月的抄表数据。Page 4 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuBW 报表设计说明书1.2 报表界面1.2.1表1.2.2图该报表可使用柱状图比较各供电局抄表工作量。1.2.3报表展示的特殊需求以及此后未来 11（共计 12报表默认展现当前日期前一）的抄表计划数据，并且要求将当前月用不同的颜分出来。类似地，如果追溯到日历周/日，也要求用不同的颜色把当前周/日凸现出来。Page 5 of 26Created: 1

8、6.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuBW 报表设计说明书1.3 报表选择条件和分析维度的需求1.3.1报表可供选择的条件1.3.2报表可供分析的维度* Only available on the chilled version of the report1.4 数据核对方法和数据粒度本报表的数据源直接来自于 CCS 的抄表日程客制化表（ZCQCBDYRC）。因此可直接使用事物代码（SE16），基于读表单元来验证 BW 数据是否准确。具体条件如下：方法和本报表的数据粒度要求明细到抄表员和日历日

9、级别。1.5 报表使用说明ü本报表的数据每月末进行一次完全更新。用户可以在工作日的 9:00 至 20:00 期间正常使用报表。每月的第一天会刷新抄表计划内容。Page 6 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuProductAPO Planning AreaShelf StableGT15DP PLAWChilledGT15DP_PLADField NameSource SystemDistribution ChannelAPOSales Organi

10、sationAPOCustomer Level 4APOAPO LocationAPOMaterial Group 1APOAPO ProductAPOMonth NumberAPOWeek NumberAPODay Number *APOField NameSource SystemOther Selection InformationDistribution ChannelAPOSelection Option, OptionalSales OrganisationAPOSelection Option, OptionalCustomer Level 4APOSelection Optio

11、n, OptionalAPO LocationAPOSelection Option, OptionalMaterial Group 1APOSelection Option, OptionalAPO ProductAPOSelection Option, OptionalMonth NumberAPOSelection Option, OptionalWeek NumberAPOSelection Option, OptionalDay Number *APOSelection Option, OptionalBW 报表设计说明书ü如果在供电局、营业所、或日历月等汇总层级秒以内。报

12、表，报表预计运行时间在 15ü如果报表时展开到明细级别（如：所有抄表员、30 个日历日），其结果将涉及大量数据的检索，报表预计运行时间需要 15 分钟（假设：一个营业所 12000 条数）。1.6 报表使用范围本报表可供下列的用户使用·········Demand PlannerSRP Planner Receiver SRP Planner Producer MPP PlannerDPS Planer MRP PlanerDemand Planning Manager Supply plann

13、er Manager DSP Report本报表的菜单路径如下：Demand and Supply Planning > Demand Planning > Demand Plan and Historical DataPage 7 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuBW 报表设计说明书2原型设计2.1数据流Data is sourced from the Demand Planning application in the APO system.

14、 Separate planning areas exist in the APO system for shelf stable and chilled products. This is reflected in the extraction and storage of data in BW. There is a complex loading strategy in order to optimize data load timings. Each report is based on a MultiProvider involving two basic InfoCubes.Dat

15、a is extracted into the Future InfoCubes YGTDS_C20 & YGTDS_C30 from APO. The data arrives in the Planning Unit of Measure and only a small number of ABAP transformations take place at this stage in order to minimize the extraction overhead.Page 8 of 26Created: 16.02.20058Printed: 07.03.2021 12:2

16、0报表设计说明书样例rddv1抄表计划Author: Scott ZhuBW 报表设计说明书Further data loads take place from these InfoCubes via Export DataSources into similar InfoCubes containing different units of measure. The key figures are converted into other units of measure via ABAP coding. This architecture has been designed in effo

17、rt to optimize extraction and reporting performance.2.2 设计分析2.2.1数据源系统信息The source system is APO Demand Planning Application. This application was part of the GLOBE Template v1.0 design. However, new planning areas have been created for the GLOBE Template v1.5 design:··GT15DP_PLAD GT15DP_P

18、LAWThese planning areas contain a reduced number of characteristics and some changes to the key figures. Data extraction from the new planning areas is from newly defined Datamart Export DataSources:··9AGT15DP_PLAD9AGT15DP_PLAWThese planning areas have been fully configured and no changes

19、are anticipated.Data for the previous two years is required to support the reporting. This means that data from legacy systems will be loaded into the BW system. This will have to be assessed on a market-by-market basis during implementation preparation.2.2.2BW 系统信息New DataSources will be defined to

20、 enable data extraction. These new objects will reflect the changes to Demand Planning characteristics and key figures. There are no additional master data requirements. Existing InfoProviders will be used to store the data and the new queries will be defined on existing MultiProviders (based on the

21、 existing basic InfoCubes)Exact data volumes are not know at this stage but are expected to be extremely high. Extraction and report performance optimization will be critical.2.2.3版本信息Performance problems were encountered with this report in GLOBE Template v1.0. With this in mind a number of key cha

22、nges have been introduced in the area of Demand Planning & Demand Planning Reporting in BW:···Reduced number of planning characteristics ABAP coding moved to start routinesABAP coding reducedPage 9 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott Z

23、huBW 报表设计说明书·ABAP coding in the Demand Planning extracts to remove records with all zero key figure valuesAll Key figures stored and reported in Planning Unit of Measure (PUM). This is the unit coming from APO and therefore no transformations are necessary Only two extra key figures (Adjusted B

24、ase Forecast and Final Consensus Demand Plan) also stored in 0BASE_UOM to support reporting for other business areas··2.2.4权限2.2.5分布式架构的影响The impacts on Demand and Supply Planning (DSP) Reporting in BW as a whole are best considered in conjunction with the high level split architecture dia

25、gram.This diagram illustrates that the APO system itself is split into a system for the Demand Planning (DP) application at the commercial cluster level, and a number of systems for the Supply Network Planning (SNP) and Production Planning and Detailed Scheduling (PP/DS) applications at the supply c

26、luster level.This clearly has an impact on BW reporting as there is no longer a single source system for DSP data as a whole. Transactional data must be sourced from theappropriate cluster., some master data is extracted from APO systems intoPage 10 of 26Created: 16.02.20058Printed: 07.03.2021 12:20

27、报表设计说明书样例rddv1抄表计划Author: Scott Zhu权限对象Included in ReportDistribution ChannelYesSales OrganizationYesBW 报表设计说明书Reporting BW e.g. APO_RESNAM_ATTR is extracted from the supply cluster. This means that the key of this object may not be unique in all source systems. In order to address this issues the o

28、bject is compounded with logical system ID whilst it is being loaded into Reporting BW. This compounding is a fundamental concept in many of the business areas for GLOBE Template v1.5 in the split architecture environment (where BW Reporting master data is being sourced from clusters below the Zone

29、level)Process chains have been built to manage the complex load schedule and dependancies in the split architecture environment.A Visio document has been produced detailing the entire data flows in the DSP Reporting area. This shows all source systems and details the architecture that supports the e

30、nd-user reporting.GCC/Business Information Warehouse/Local Reporting/Template v1.5/RDD/DSP/DSPorgnl.vsdPage 11 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuBW 报表设计说明书2.3 业务分析维度2.3.1固定过滤器Page 12 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表

31、计划Author: Scott ZhuFilterTechnical NameValueDisplay AsSuppress Results RowsNormalize ToSort OrderHierarchy NameHierarchy PropertiesMonth NumberYGTCALMTJanuary- December (inclusive)NAAlwaysNANANANABW 报表设计说明书2.3.2变量过滤器2.3.2.1 变量条件特性(执行报表时可供选择的变量条件)Page 13 of 26Created: 16.02.20058Printed: 07.03.2021 1

32、2:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuFilterTechnical NameVariable Description / Tech NameSelection TypeSelection OptionsDefault ValueVariable TypeProcessing TypeCan be Changed in NavigationDistribution Channel0DISCHANDistribution ChannelSelection OptionOptionalNACharacteristic ValueUser Entry / De

33、fault ValueNo tickSales OrganisationYSALESORSales OrganisationSelection OptionOptionalNACharacteristic ValueUser Entry / Default ValueNo tickCustomer Level 4YCUSTL4SCustomer Level 4Selection OptionOptionalNACharacteristic ValueUser Entry / Default ValueNo tickAPOLocationYAPOLOCAPOLocationSelection O

34、ptionOptionalNACharacteristic ValueUser Entry / Default ValueNo tickMaterial Group 1YC_MATGMaterial Group 1Selection OptionOptionalNACharacteristic ValueUser Entry / Default ValueNo tickAPO ProductYAPOMATSAPO ProductSelection OptionOptionalNACharacteristic ValueUser Entry / Default ValueNo tickCalen

35、dar YearYCALYR4Calendar YearIntervalOptionalNACharacteristic ValueUser Entry / DefaultNo tickBW 报表设计说明书Page 14 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuFilterTechnical NameVariable Description / Tech NameSelection TypeSelection OptionsDefault ValueVariable

36、 TypeProcessing TypeCan be Changed in NavigationValueMonth NumberYGTCALMTMonth NumberIntervalOptionalNACharacteristic ValueUser Entry / Default ValueNo tickWeek NumberYGTCALWKWeek NumberIntervalOptionalNACharacteristic ValueUser Entry / Default ValueNo tickBW 报表设计说明书2.3.2.2变量特性的显示属性Page 15 of 26Crea

37、ted: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuFilterValueDisplay AsSuppress Results RowsNormaliz e ToSort OrderHierarchy NameHierarchy PropertiesDistribution ChannelKey and NameNeverNoNANANASales OrganisationKey and NameNeverNoNANANACustomer Level 4NameNeverNoNANANAAPOL

38、ocationNameNeverNoNANANAMaterial Group 1Key and NameNeverNoNANANAAPO ProductNameNeverNoNANANACalendar YearKeyAlwaysNoNANANAMonth NumberNameAlwaysNoNANANAWeek NumberKeyNeverNoNANANADay NumberKeyNeverNoNANANABW 报表设计说明书2.3.3自由特性Page 17 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计

39、划Author: Scott ZhuFree CharacteristicBW Technical NameDisplay AsSuppress Results RowsNormalize ToSort OrderHierarchy Technical NameHierarchy PropertiesDistribution channel0DISTR_CHANKey & NameNeverNANANANASales Organization0SALESORGKey & NameNeverNANANANACustomer Level 4YCUSTL4NameNeverNANAN

40、ANAAPO Location0APO_LOCNONameNeverNANANANAMaterial Group 10MATL_GRP_1Key & NameNeverNANANANAAPO Product0APO_PRODNameNeverNANANANABW 报表设计说明书2.3.4关键指标Page 19 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuKey Figure NameBW Technical NameHighlightingHideSelecti

41、on of ConstantsScaling FactorNo. of DecimalsReverse+/ SignsCalculationsCurrency TranslationStat (base) ForecastYSBFPUMNoNoNANAFrom KFNANANAReturned GoodsYRGPUMNoNoNANAFrom KFNANANAOrder QuantityYOQTYPUMNoNoNANAFrom KFNANANAOperational PlanYOPLPUMNoNoNANAFrom KFNANANAFinal Consensus DPYFCDPPUMNoNoNAN

42、AFrom KFNANANAEvents AdjustmentYEAPUMNoNoNANAFrom KFNANANAEvent QuantityYEVNTPUMNoNoNANAFrom KFNANANADispatchesYDISPUMNoNoNANAFrom KFNANANAContract QuantityYCQPUMNoNoNANAFrom KFNANANACleaned Base HistoryYCBHPUMNoNoNANAFrom KFNANANACalc. Clean Base HisYCCBHPUMNoNoNANAFrom KFNANANABaseline ImpactorsYB

43、IPUMNoNoNANAFrom KFNANANAAdj. Clean Base HistYACBHPUMNoNoNANAFrom KFNANANAAdj. Base ForecastYABFPUMNoNoNANAFrom KFNANANABW 报表设计说明书2.3.5计算指标No calculated key figures are defined in this report.2.3.6其他要求（层级/条件/例外/单元格定义）There are no exceptions or conditions defined in this report. Each user as required

44、 can define these individually.The column layout is set to Display as a Hierarchy expanded to Month Number. This enables the user to see a more detailed level of time granularity without having to drill down entirely. There is of course the flexibility to display without hierarchy and use the standa

45、rd drilldown functionality as required.Page 21 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuCalculated Key Figure NameBW Technical NameHighlightingHideNo. of DecimalsReverse +/ SignsFormulaBW 报表设计说明书3技术设计3.1 前端配置3.1.1变量输入屏幕Page 22 of 26Created: 16.02.20058Prin

46、ted: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuBW 报表设计说明书3.1.2最终报表展现样式Fig 1. Initial view of the report displaying all 14 key figures for 2001, 2002 & 2003 (2003 out of screen) on a Monthly level of time granularityFig 2. Analysis of the Orders Quantity key figure (see Navigation Block)Page 23 of 26Created: 16.02.20058Printed: 07.03.2021 12:20报表设计说明书样例rddv1抄表计划Author: Scott ZhuBW 报表设计说明书Fig 3. Chart representation of the Results Table dataFig 4. Orders v Dispatches with week analysis in JanuaryPage 24 of 26Created: 16.0