U2K2 Programme

<IM BW> Technical Specification

<.. >

Prepared by
Date

Reviewed by
Date

Approved by
Date

< CR DESCRIPTION & NO >

File Name:91508180.doc.ms_office
Status: Draft

Page 1 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

TABLE OF CONTENTS
GENERAL INFORMATION ......................................................................................................................................................... 4
SIGN OFF ........................................................................................................................................................................................ 4
REVISION HISTORY .................................................................................................................................................................... 4
CATEGORY OF CHANGE ............................................................................................................................................................ 4
CONTACT AND PHONE NUMBER ............................................................................................................................................ 4
RICEF WORK UNIT #: ................................................................................................................................................................. 5
CHANGE REQUEST TITLE: ....................................................................................................................................................... 5
MODULE & SUB MODULE: ........................................................................................................................................................ 5
REGIONAL / COUNTRY PROJECT: .......................................................................................................................................... 5
EXPECTED DELIVERY TIMELINE: ......................................................................................................................................... 5
1

.REPORTING .......................................................................................................................................................................... 5

1A.GENERAL REQUIREMENTS ................................................................................................................................................ 5

1B. DESIGN ..................................................................................................................................................................................... 6
DETAILED DESCRIPTION OF NEW REPORT/CHANGES TO EXISTING REPORT ................................................................................... 6
PRE-PROCESSING/POST-PROCESSING DEPENDENCIES .................................................................................................................... 6
PRE-PROCESSING ........................................................................................................................................................................... 6
POST-PROCESSING ......................................................................................................................................................................... 6
REPORT LAYOUT ............................................................................................................................................................................ 6
SECURITY AND AUTHORIZATION CHECK ........................................................................................................................................ 6
TECHNICAL NAME OF THE ROLE; ( .................................................................................................................................................. 6
TEST DATA..................................................................................................................................................................................... 7
2

. DATA MODEL ...................................................................................................................................................................... 7

2A.GENERAL REQUIREMENTS ................................................................................................................................................ 7

2B. DESIGN ..................................................................................................................................................................................... 8
DETAILED DESCRIPTION OF NEW DATA MODEL/CHANGES TO EXISTING DATAMODEL .................................................................. 8
PRE-PROCESSING/POST-PROCESSING DEPENDENCIES .................................................................................................................... 8
PRE-PROCESSING ........................................................................................................................................................................... 8
POST-PROCESSING ......................................................................................................................................................................... 8
SECURITY AND AUTHORIZATION CHECK ........................................................................................................................................ 8
TEST DATA..................................................................................................................................................................................... 8
3

. INTERFACE .......................................................................................................................................................................... 8

3A.GENERAL REQUIREMENTS ................................................................................................................................................ 9

File Name:91508180.doc.ms_office
Status: Draft

Page 2 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

3B. DESIGN ................................................................................................................................................................................... 10

DETAILED DESCRIPTION OF NEW INTERFACE/CHANGES TO EXISTING INTERFACE ....................................................................... 10
PRE-PROCESSING/POST-PROCESSING DEPENDENCIES .................................................................................................................. 10
PRE-PROCESSING ......................................................................................................................................................................... 10
POST-PROCESSING ....................................................................................................................................................................... 10
SECURITY AND AUTHORIZATION CHECK ...................................................................................................................................... 10
TEST DATA................................................................................................................................................................................... 10
TS STATUS .................................................................................................................................................................................... 10

File Name:91508180.doc.ms_office
Status: Draft

Page 3 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

General Information
Document Location
Associated
Documentation

Sign Off
Team

Name

Date

Signature

CPL
RAC

Revision History
Version

CR No/
FUR No

Date

Author

Status

CR Description

Approved
Signed off

Initial Version
Daily Store Stock Tracking Report

< version 1.x: First FS of CR

version 2.x: If any FUR created to related CR
version 3.x: For another FUR
version x.1:First version of FS after CAB approval which is called DRAFT.
version x.2:Under Review
version x.3:SIGNOFF version of FS after country and RAC agreement..

Category of Change
New Report

New Data Model

Local Interface (New)

Report Enhancement
Performance Improvement

Data Model Enhancement

Local Interface (Enhancement)

Regional Interface (New)

Regional Interface (Enhancement)

Contact and Phone number

Name Surname

File Name:91508180.doc.ms_office
Status: Draft

E-mail

Phone Number

Page 4 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

RICEF Work Unit #: (Required)

[<Fun_Module>-R-###]

IM_BW - RXXX

Change Request Title: (Required)

[Title of the functional report specification.]

Daily Store Stock Tracking Report

Module & Sub module: (Required)

[Indicate the SAP Module and Sub module based on SAP Hierarchy, e.g.: FI AR, MM PUR, etc]

IM_BW - CD

Regional / Country Project:

<Regional or Country>

Country

Expected Delivery Timeline:

<dd.mm.yyyy>

[TBA]

1 .REPORTING
1a.General Requirements
Technical Name & Description of the Report: (Required)
ZIM_C001_Q001_35 - Daily Store Stock Tracking Report

Functional Description of Change:(Required)

[Describe briefly the purpose of the change]

Report will have product hierarchy and customer hierarchy linkage after the change.

Priority:
[Enter the relative priority of the report based on its necessity to run the business.
Use the following criteria:
Low - Item has little or no impact on running the business and does not support the business case or quality of the project.
Medium - Item is not required to run the business on 'day one' and indirectly supports the business case and quality of the project.
High - Item is required to run business on 'day one' and directly support the business case of the project.]

Medium
Complexity:
[Enter the following complexity:
Easy - Simple Basic, single-level report. Little aggregation or sorting. No use of external subroutines.
Medium - Multiple-level drill down/layout capability (2-3). Moderate calculation, sorting. Field translations needed. Some customization
Difficult - Use of sub screens, pop-ups, 3-6 levels of drill down/layout ,etc. Significant authorization checking. Complicated data retrieval. Some
customization.
Very Diff. - Need to dig into SAP code to manipulate data that will simulate SAP processing. Large number of drill downs or alternate views.
Multiple currencies.]

Medium

File Name:91508180.doc.ms_office
Status: Draft

Page 5 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

Design Assumptions:
[Describe the expectations external to this document that directly affect the outcome and are not discussed in detail. Areas discussed should
include: Entry criteria prior to design document, things that need to be done prior to design completion, resource support and requirements signoff.]

All data will be extracted from MRP results.

1b. Design
Detailed Description of New Report/Changes to Existing Report: (Required)
[Use this section to describe the major features of the document. Include header and trailer information, user specified parameters ( i.e. List by
customer, list by product, or list by sales region) and any specifics on summary information ( commonly placed at the end of the report such as
totals, sub-totals, etc.). If required list rank-by, sort-by, or group-by criteria.]

Field A will be added in free chars and it will be also added on selection screen as interval, mandatory, multiple
selection.

Pre-Processing/Post-Processing Dependencies:
[Enter the prerequisite steps, i.e., any customized table that the program retrieved the data from. In that case, the user must provide valid data
record in the table. Also state the post-processing steps, i.e. report is sent to a dept via spool request.]

Pre-Processing
-

Table A should be prepared before BW development.

Post-Processing
-

Workbooks should be generated.

Report Layout: (Required)

[Enter sample layout or provide a document containing the layout.]

Daily Store Stock

Tracking Report

Security and Authorization Check

[Provide the security and authorization check requirements, such as the field to check, authorization objects, field value, etc. This authorization
check should be able to control that only user with the correct authorization can execute/view the data in this report. ]

Current BW Authorization model will be used.

Technical name of the role; (if new report is created)

-

ZSD_ROLE_35

1d. Unit Testing Criteria

Screen shot of unit test selection screen should be added.

File Name:91508180.doc.ms_office
Status: Draft

Page 6 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

Test Data: (Required)

[Provide the test data that to perform the above test conditions]

Screen shot of unit test result should be added.

2 . DATA MODEL
2a.General Requirements
Type of the changed/created objects;
-

Cube
Mutiprovider
Transformations

Technical Name & Description of the Objects (Required)

-

ZIM_C001 Stock Cube

ZIM_M006 Stock Multiprovider
ZLIS_03_BFZIM_C001 transformation

Functional Description of Change:(Required)

[Describe briefly the purpose of the change]

Ability to add Product hierarchy and customer hierarchy to the reports based on info provider ZIM_C001.
Ability to prepare new reports which includes Product hierarchy and customer hierarchy

Dataload Type: (If any new datamodel is created)

[Enter the dataloading type of the report:
Manual The data loading will be executed manually upon request
Process Chain The data loading will be scheduled as a background job via PC.
Scheduled job The data load will be scheduled as a background job via infopackage.

Process Chain
SourceSystem of Data loading: (If any new datamodel is created)
[Enter the dataloading source for the new model]
ECC/PC file/interface/etc

ECC
Priority:
[Enter the relative priority of the report based on its necessity to run the business.
Use the following criteria:
Low - Item has little or no impact on running the business and does not support the business case or quality of the project.
Medium - Item is not required to run the business on 'day one' and indirectly supports the business case and quality of the project.
High - Item is required to run business on 'day one' and directly support the business case of the project.]

Medium

Complexity:
[Enter the following complexity]:
Easy - Medium - Difficult (According to RICEF Estimation)

File Name:91508180.doc.ms_office
Status: Draft

Page 7 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

Medium
Design Assumptions:
[Describe the expectations external to this document that directly affect the outcome and are not discussed in detail. Areas discussed should
include: Entry criteria prior to design document, things that need to be done prior to design completion, resource support and requirements signoff.]

All data will be extracted from MRP results.

2b. Design
Detailed Description of New Data Model/Changes to Existing Datamodel: (Required)
[Use this section to describe the major features of the document. Include header and trailer information, user specified parameters ( i.e. List by
customer, list by product, or list by sales region) and any specifics on summary information ( commonly placed at the end of the report such as
totals, sub-totals, etc.). If required list rank-by, sort-by, or group-by criteria.]

Field A will be added in cube ZIM_C001 and ZIM_M006. It will be matched in all transformations under ZIM_C001.

Pre-Processing/Post-Processing Dependencies:
[Enter the prerequisite steps, i.e., any customized table that the program retrieved the data from. In that case, the user must provide valid data
record in the table. Also state the post-processing steps, i.e. report is sent to a dept via spool request.]

Pre-Processing
-

Field A should be available in source table in ECC.

Post-Processing
-

After changing ZIM_C001, all multiproviders which include ZIM_C001 should be activated.

Security and Authorization Check

[Provide the security and authorization check requirements, such as the field to check, authorization objects, field value, etc. This authorization
check should be able to control that only user with the correct authorization can execute/view the data in this report. ]

Current BW Authorization model will be used.

2d. Unit Testing Criteria

Test Data: (Required)
[Provide the test data that to perform the above test conditions]

Screen shot of unit test result should be added.

3 . INTERFACE

File Name:91508180.doc.ms_office
Status: Draft

Page 8 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

3a.General Requirements
Type of Interface
Inbound/Outbound

Inbound
Technical Name & Description of Datasource (If Inbound)
-

ZIM_AU1 Stock Interface

Technical Name & Description of Method (If Inbound)

-

ZII_MNT_PROD_HIER_ATTR_BW_IN_A~MNT_PROD_HIER_ATTR_BW_IN_AS

Technical Name & Description of Open Hub (If outbound)

- /BIC/OHRG_PRODHR
Technical Name & Description of Open Hubs Source (If outbound)
-

ZIM_C001

Technical Name & Description of Class (If outbound)

ZCLPUSH_PH_XI
Functional Description of Change:(Required)
[Describe briefly the purpose of the change]

Extracting product hierarchy data to target DMS system

Dataload Type: (If any new datamodel is created)
[Enter the dataloading type of the report:
Online The data loading will be executed manual(online)
Process Chain The data loading will be scheduled as a background job via PC.

Process Chain
SourceSystem of Data loading: (If inbound)
[Enter the dataloading source for the new model]
DMS HUB/country local system/OPSO etc

DMS
TargetSystem of Data loading: (If outbound)
[Enter the dataloading source for the new model]
DMSHUB/country local system/OPSO etc

DMSHUB

Priority:
[Enter the relative priority of the report based on its necessity to run the business.
Use the following criteria:
Low - Item has little or no impact on running the business and does not support the business case or quality of the project.
Medium - Item is not required to run the business on 'day one' and indirectly supports the business case and quality of the project.
High - Item is required to run business on 'day one' and directly support the business case of the project.]

File Name:91508180.doc.ms_office
Status: Draft

Page 9 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

Medium
Complexity:
[Enter the following complexity]:
Easy - Medium - Difficult (According to RICEF Estimation)

Medium

3b. Design
Detailed Description of New Interface/Changes to Existing Interface: (Required)
[Use this section to describe the major features of the document. Include header and trailer information, user specified parameters ( i.e. List by
customer, list by product, or list by sales region) and any specifics on summary information ( commonly placed at the end of the report such as
totals, sub-totals, etc.). If required list rank-by, sort-by, or group-by criteria.]

Field A will be added to interface X to extract the product hierarchy data from DMS HUB to BW system.

Pre-Processing/Post-Processing Dependencies:
[Enter the prerequisite steps, i.e., any customized table that the program retrieved the data from. In that case, the user must provide valid data
record in the table. Also state the post-processing steps, i.e. report is sent to a dept via spool request.]

Pre-Processing
-

Proxy should be regenerated after PI side is completed.

Post-Processing
-

Security and Authorization Check

[Provide the security and authorization check requirements, such as the field to check, authorization objects, field value, etc. This authorization
check should be able to control that only user with the correct authorization can execute/view the data in this report. ]

Current BW Authorization model will be used.

3c. Unit Testing Criteria

Test Data: (Required)
[Provide the test data that to perform the above test conditions]

Screen shot of unit test result should be added.

TS Status
FS Status
Regional Application
Manager
(ERP / Information
Management / Customer

File Name:91508180.doc.ms_office
Status: Draft

Approved

Rejected

Deferred

Escalated

Name: Murat Kncak

Date:

Page 10 of 11
Confidential

U2K2 Programme
<IM BW> Technical Specification
<.. >

Development etc.)

Signature / Email Rejection

Comments / Reasons if rejected or escalated:

File Name:91508180.doc.ms_office
Status: Draft

Page 11 of 11
Confidential