aaes bp315 dp baseline 07 06 2010

Accenture Advanced Enterprise Services

AAES_BP315 DP Baseline<Sub Process Number>

DP Baseline<Sub Process Number>

Version: Prepared By: Reviewed By:

Copyright © 2008 Accenture All Rights Reserved of 17



Copyright © 2008 Accenture. All Rights Reserved. Neither this document not any part thereof may be copied or reproduced in any form or by any means, or translated into another language without the prior consent of Accenture. The information contained in this document is subject to

change and supplement without prior notice. All rights reserved




Usage guidelines and Specific Instructions:

• Document Flow- The flow of the document is generic. Specific changes to the flow will be required to be done by the client team to suit the client context.

• Document Content- The content explains the process and Sub Process in a generic manner. Specific changes are required to be made to meet client requirement.

• Section 1- Industry segment specific information to be added to the High level description as required by the respective client engagements.

• Section 3.2/3.3- The Inbound and Outbound Communication needs to be specifically documented for the client specific situation.

• Section 4 – The Regulatory Compliance(s) needs to be updated based on the geography where the solution is being implemented.

• Section 7- The AAES solution needs to be used as base for completion of these sections during the client engagement. It should be noted that the AAES is continuously developed and hence these documents will undergo change. Hence please touch base with your respective AAES Point of Contact for latest information.

• Section 8 – Generic Integration Touch points have been highlighted. Implementation specific integration touch points need to be documented.




Document Information

Document Review & Sign-off

SignatoriesRole Name Signature Date

ReviewersRole Name Comments Received Date


Deliverable Name Business Sub Process – DP Baseline Author AAES Development TeamOwner AccentureTeamStatus In processVersion 0.1



Revision History

Version No. Date Author Revision Description

Other Related Documents

<Please insert links to related Documents (issues, data entities, etc.).>

Related Document Comment




TABLE OF CONTENTS

1. Business Process Overview...................................................................................................................... 71.1 Overview of the Business Process................................................................................................71.2 Key Value Drivers for the Business Process...............................................................................71.3 Leading Practice Inputs.................................................................................................................. 7

2. Business Sub-Process Description..................................................................................................83. Sub-Process Activities.......................................................................................................................... 9

3.1 Activity List....................................................................................................................................... 93.2 Inbound Communication..............................................................................................................103.3 Outbound Communication...........................................................................................................103.4 Test Conditions.............................................................................................................................. 11

4. Governance / Regulatory Controls (SOX or other legal requirements)..........................115. Sub Process Scenarios....................................................................................................................... 11

5.1 Business Model Lead.................................................................................................................... 115.2 Geography Lead............................................................................................................................ 115.3 Legal Entity Lead........................................................................................................................... 11

6. Role Definition & Organisational Impact....................................................................................126.1 Role/Skill Class Inventory.............................................................................................................126.2 Role Summary................................................................................................................................ 126.3 Organisational Impact.................................................................................................................. 12

7 Process Fitness & Gap Analysis.......................................................................................................137.1 Process Fitness.............................................................................................................................. 137.2 Gap Analysis................................................................................................................................... 14

8 Integration Issues................................................................................................................................. 148.1 Integration Issues.......................................................................................................................... 148.2 Other Issues................................................................................................................................... 14




1. Business Process Overview1.1 Overview of the Business Process

Demand planning process is part of Global Process Definition for planning. Demand Planning is the starting point in the planning process. It deals with the processes connected with identification, analysis and forecasting of requirements. The objective of this process is being able to meet the customer requirements with the right material at the right time, in the right place, in the right quantity with the right quality. Planning is the process of generating, collecting and aggregating data to create the most accurate forecast of customer demand, based upon a product’s historical sales pattern and future market intelligence.

Supply Chain Planning involves the development of a forecast plan, evaluating its feasibility, splitting it into production and distribution channels, and then releasing it for manufacturing. Demand Planning involves creation of the forecast plan, followed by its release for capacity sizing and driving future sales projections. The forecast plan is based on reaching a consensus forecast. This is a result of considering sales history, planned promotions, product lifecycles, and current market intelligence.

The DP Baseline sub-process describes the one time setup of the technical structure that will support Demand Planning in the future. This includes setting up the source systems and file transfer processes so data can flow from the Business Warehouse (BI) to APO and Demand Planning can occur. The final forecast is one of the critical inputs to the overall S&OP process and drives downstream planning. The resulting final consensus forecast can be accessed in multiple dimensions and at multiple hierarchical levels.

This process will be used across all regions of O-I.

1.2 Key Value Drivers for the Business Process

The key value drivers for this business process include:

Having information available in SAP APO as an input for Demand Planning. Maintain consistent and current data by having the proper linkages between ECC, BI

and APO. Accurately importing historical data to generate statistical forecast

1.3 Leading Practice Inputs

Key Practices The BW InfoCube containing historical data should be based on logical key

characteristics. (i.e. Sales Org, customer( sold to party), SKU, ship to #, category). To ensure no data is missing in our planning modules, source systems should be

setup to ensure proper data linkages exist between ECC, SAP BI and APO.




ECC stores Master data used for Demand Planning. (Customers, Material Numbers Ship to Party, category etc..)

2. Business Sub-Process DescriptionThe Demand Planning Baseline sub-process creates the technical structure in order to support O-I Supply Chain Planning (SCP) processes in the DP area. This means, setting up the necessary structure to upload and store information in SAP APO. Having this setup correctly and effectively is essential in order to start the planning process.

The main point of building a technical structure is to allow the planner to upload historical information to SAP APO, store it, and manage it within the demand planning module. Setting up these elements will enable activities that need to be carried out in the future planning process.

Shipment history will be based on actual delivered quantities and will be imported at the SKU level, these will be aggregated to the SKU group level in order to generate a SKU group level statistical forecast.

1. Historical data will be brought at SKU level2. SKU level data will be aggregated to SKU group.3. We forecast at SKU group Level.4. SKU group forecast dis-agreegated into SKU based on proportional factors.( Mid to

Long term)5. We release forecast to SNP at SKU level

Key characteristics to be included to build the InfoCubes:

Customer Bill to Name (customer name ( sold to party) Ship to party (Primary demand location)

Product SKU SKU-group Category (beer, food, wine, etc…)

Plant

Time Monthly buckets

Key Figures:

Order Quantity/Actual delivered quantity (includes actual shipments minus returns) Historical adjustments (corrected outliers/incorrect shipments or 0’s) Statistical Forecast Adjusted/Override Statistical forecast Market intelligence Finance department ???? Consensus/Collaborative forecast




Previous period forecast Expost forecast Promotions

Note that activities mentioned in this document are technical activities carried out by the DP Maintainer only once. It is important to understand this structure in order to have a clear picture of how SAP APO stores and manages information.

The following activities occur in the DP Baseline sub-process:

Initiate setup of datamart structure

Once the DP Setup sub-process is finished, the next step is initiating the setup of the datamart structure so data can flow to APO.

Setup source systems

All systems that provide BI with data are described as source systems (ECC). Source systems should be created to upload data into InfoCubes. Typically, legacy systems load their data into BI, and APO loads it from BI.

Assumption: Initially, historical data will be extracted from the legacy systems (mainframe) based on actual delivered quantities and uploaded into infocubes APO.

In the future, ECC (SAP) will be the source system.

Setup upload process

To create all of the necessary elements in the demand planning baseline, it is essential to use the Data Warehousing Workbench. The Data Warehousing Workbench is the tool with which you load data into the InfoCubes from a source system. The process for uploading data to the InfoCube is more or less the same irrespective of the type of source system. Setting up the upload process involves creating an InfoArea, InfoCube, Source system, Application Component, and Info Package.

Master data

SKU SKUGroup

Setup InfoCubes

An InfoCube is a set of relational tables arranged according to the star schema (multi-dimensional): A large fact table in the middle surrounded by several dimension tables. InfoCubes are filled with data from one or more InfoSources or other InfoProviders. They are available as InfoProviders for analysis and reporting purposes. InfoCubes will include data dimensions, characters, and key figures.




Key Decision Demand planning data model must be defined and data conversion rules must be

defined. Position Papers for Demand Planning Data Model and Demand Planning Data Re-Alignment have been written and approved for implementation with Demand Planning. BW team will work on bringing data and creation InfoCubes.

Backup cubeHistorical reporting

Remote cubeLive reporting

Setup file transfer process

BI supports the transfer of data from flat files, files in ASCII format (American Standard Code for Information Interchange) or CSV format (Comma Separated Value). Each file to be uploaded should have an associated InfoSource, InfoPack, and file name.

Setup data exchange between InfoCubes and planning areas

Permanent data is stored in InfoCubes. In general, this is either historical actual data or forecasts that you want to keep for future comparison. Current data for planning is kept in LiveCache in planning areas. Demand planning itself is conducted in LiveCache. Data needs to be transferred between the two, for instance to use historical data as the basis for forecasting.

3. Sub-Process Activities3.1 Activity List

Name Description Transaction Code, if relevant

Roles involved

SOX Control / Other controls to be put Initiate setup of

datamart structure

The DP Maintainer will kick off the setup of the datamart structure.

/n/RSA1 DP Maintainer

Setup source systems

BI Master DataHistorical data

Determine which source systems will supply data to BI. There will be two source systems,

ECC/BI after Go liveFlatfile for data collected from Mainframe.





Setup upload process

Setup data warehousing workbench to setup rules (timing) for loading data from the source system to the InfoCubes.


Setup InfoCubes

Setup fact and relational tables for InfoCubes in a logical format (i.e. sales Organization, Customer, Ship to party, category, SKU/SKU group for key figure Delivered QTY).


Setup file transfer process

Setup format of flat files and data conversion rules for data upload.


Setup data exchange between InfoCubes and planning areas

Setup transfer process to load data into live cache from history cube.

/n/SAPAPO/TSCUBE DP Maintainer

Setup Infoobjects, Infoarea, Infocubes, Application component, Catalog. Setup Infopackage/DTP for data loadsSetup transformations rules for data loadsPlanning object structurePlanning areaPlanning books and data viewsForecast profilesMacrosBackground activities and jobsTime bucket profilesStorage bucket profilesLife cycle planningPromotions planningAlerts ( Forecast Errors – Standards)

3.2 Inbound Communication

Activity Type (email, form, handoff, etc.)

Automatic / Manual

Source Description

DP Setup Handoff Manual APO DP module, including




9.14.01 (one time) key figures and planning book structures setup.

3.3 Outbound Communication

Activity Type (email, form, handoff, etc.)

Automatic/Manual

Destination Description

Datamart Structure set up Completed

3.4 Test Conditions

<<Captures specific Test conditions for this sub process for the any specific client requirements. Generic test conditions for this sub process will be within the AAES test scripts >>

Number Test Condition – Action Expected Result

4. Governance / Regulatory Controls (SOX or other legal requirements)<<Describe any Control elements necessary for the Sub Process. This section can be leveraged from the SOX compliance documents >>

Control Comments

<<Instructions: Control: The control name and number Comment: Include additional information as necessary>>




5. Sub Process Scenarios<<A Sub Process scenario is a variation of the specific sub process led by a business / geography or could be required to cater to certain legal regulations. Identify known process scenarios here. These scenarios will be captured as part of the Integrated Test Plan. It is the prerogative of the individual engagements to develop specific Blueprint and/or Realization deliverables for these scenarios. Further additions / details may get added on as we move towards localisation >>

5.1 Business Model Lead

5.2 Geography Lead

5.3 Legal Entity Lead

6. Role Definition & Organisational Impact6.1 Role/Skill Class Inventory<<Update the “Skills and Knowledge” needs for the roles supporting the Sub Process change management impact. The Standard AAES roles are used as the basis for this section. It is the prerogative of the specific engagements to adopt or change these roles as fit. >>

<<Refer the Roles and T codes sheet provided in section 3>>

Role Skills Knowledge

6.2 Role Summary<<This will serve as an input into the role definition document role definition>>

Role List of Steps SAP Transaction

6.3 Organisational Impact




People Impact

Reference #

Impact Description Impact(H/M/L)

Impact Type Impacted Roles

APO technical knowledge of the data structure is needed for ongoing support.

Low Knowledge / Skill DP Maintainer

Instructions: Magnitude of Change / Impact <H,M,L> Impact Type to be chosen from- Business Process, Knowledge / Skill, Role, Team/Org

Structure, Culture, Technology, Forms/ Policy/ Procedures, Communications>>

7 Process Fitness & Gap Analysis7.1 Process Fitness

<<This section will capture the sub process specific requirements and the process fitness compared to the AAES solution>

Req. Types are Application, Technical Architecture, Training and Performance Support, Service Introduction, DeployProcess Fitment Categories:

Cat A -> Can be met by Config already available in ECC + jump start layer. Tables may need to be updated & validated

Cat B -> Can be met by additional Config / config changes itself (Exists in SAP Industry Solution/SAP BP Solution). Verify through prototype.

Cat C -> A Gap. Requires some Config & Development, but Accenture Building Block exists (Typically Interface / Workflow / Enhancement).

Cat D -> A Gap. Requires some Config & Development, but NO Building Block exists

Req ID Title Description Requirement Type

DP Setup DP Setup must occur before datamart structure can be setup.

Application

Legacy Data Format All legacy shipment history data will need to be in flat file format to be uploaded into the InfoCubes.

Application

Data Conversion All legacy shipment history data in flat files must be in the correct data structure for conversion.

Application

Planning Area Structure

InfoCubes setup must be done before planning areas can be structured.

Application

Demand Planning Data Model

Demand Planning Data Model must be defined before InfoCubes can be built.

Application




Master Data Verification

Master data transferred from ECC to BI is verified.

Application

Data Transfer Volume

Volume of file transfer data loaded from BI to APO is verified.

Application

DP Set Up Capability to insure sales history key figure values are consistent across the landscape (ECC, BI, DP)

Application

Demand Planning BI Create backup cube and daily process for Demand Planning BI reporting and backup usage

Application

BI backup cube for DP planning area

Create backup cube and daily process for Demand Planning area BI reporting and backup usage

Application

7.2 Gap Analysis

Country/ Region/ Business Impacted

Gap Description Legal Req.(Y/N)

Impact (L/M/H)

Solution Type RICEFW No.

All All legacy shipment history data in flat files must be in the correct data structure for conversion. A Data Conversion template needs to be developed to support this task.

N M Conversion

All Capability to insure sales history key figure values are consistent across the landscape (ECC, BI, DP)

N H Extension

All Create backup cube and daily process for Demand Planning area BI reporting and backup usage

N H Extension

Need the ability to SKU to SKU Group for history

Extension

8 Integration Issues8.1 Integration Issues

Reference #

Issue Description Impact Status Resolution




8.2 Other Issues

Reference #

Issue Description Impact Status Resolution
