SAP HANA Functional Design:
MCHI BOM Creation / Changes
GFCF Control
MTD Production BOMs Creation of and changes to production Bill of Material's (BOM) are reviewed
C1.2 (Approval of and approved by an independent authorised user prior to processing.
Creation/Changes)
MTD SAP BOMs Creation of and changes to SAP generated Bill of Material's (BOM's) are
C1.3 approved by an independent authorised user prior to processing. Processing
is prevented unless all mandatory fields are complete and validations
satisfied.
Page 1 of 10
Document Control
Document Preparation
Versi
Date Name Role Comments
on
30-11-2020 1.1 Ashish Pathania IT Functional Report Logic Update ,HANA model
Update
Document Review
Vers
Date Name Role Comments
ion
02-02-2021 1.1 Manish Taparia A.M SIGNED OFF
Document Approval
Date Version Name Role Comments
06-02-2021 1.1 Shradha Acharya SR.MANAGER IT
Page 2 of 10
Table of Contents
DOCUMENT CONTROL.................................................................................................................................... 2
1 OVERVIEW AND SCOPE.......................................................................................................................... 5
1.1 FUNCTIONAL DESCRIPTION AND SCOPE.................................................................................................. 5
1.1.1. REQUIREMENTS:............................................................................................................................... 5
1.2 DEPENDENCIES / CONSTRAINTS............................................................................................................. 5
1.3 ASSUMPTIONS....................................................................................................................................... 5
1.4 EXTENSION USAGE............................................................................................................................... 5
2 DETAILED FUNCTIONALITY.................................................................................................................... 6
2.1 FUNCTIONAL SPECIFICATION.................................................................................................................. 6
2.1.1 BOM Creation / Changes................................................................................................................ 6
2.2 PROCESS FLOW DIAGRAM..................................................................................................................... 6
2.3 DATA MODEL........................................................................................................................................ 7
2.4 A4O AND TABLEAU DASHBOARD............................................................................................................ 7
2.5 GEOGRAPHY HIERARCHY DATA UPLOAD................................................................................................ 7
2.6 DIMENSIONS AND KEY FIGURES FOR TREND DETAILS.............................................................................8
2.7 DATA DICTIONARY................................................................................................................................. 8
2.7.1 BOM Creation / Changes / Deletion................................................................................................8
2.8 MASTER TABLES................................................................................................................................... 9
2.9 INPUT AND OUTPUT............................................................................................................................... 9
2.10 REPORTING.......................................................................................................................................... 9
2.11 INITIAL DATA SET-UP / CONVERSION REQUIREMENTS.............................................................................9
2.12 NETWORK INTEGRATION...................................................................................................................... 10
2.13 EXISTING SAMPLE PROGRAMS............................................................................................................. 10
2.14 SECURITY AND AUTHORISATION........................................................................................................... 10
2.14.1 Segregated Access Requirements for Users into Single Roles................................................10
2.14.2 Risk Assessment and Considerations for the Access Required...............................................10
2.14.3 Users, Teams, Jobs where access is required.........................................................................10
2.14.4 Objects to be authority-checked............................................................................................... 10
2.14.5 Authorization Design:................................................................................................................ 10
2.9.6 Security and Authorization for the Vendor AM Team................................................................10
2.15 PROCESSING AND OPERATIONAL CONSIDERATIONS..............................................................................10
2.15.1 Performance............................................................................................................................. 10
2.15.2 Batch Requirements................................................................................................................. 10
2.15.3 Data Maintenance Requirements............................................................................................. 10
2.15.4 Re-Use Details.......................................................................................................................... 10
2.15.5 Error Handling........................................................................................................................... 10
2.15.6 Log Output................................................................................................................................ 10
2.15.7 Purge and Archive Considerations........................................................................................... 11
2.16 DESIGN ALTERNATIVES....................................................................................................................... 11
2.17 KEY TEST CONDITIONS AND CONSIDERATIONS.....................................................................................11
OPEN POINTS................................................................................................................................................. 11
Page 3 of 10
1 Overview and Scope
1.1 Functional Description and Scope
Business requirement is:
a. To identify list of all Bills of Materials created during the calendar month
b. To identify list of all Bills of Materials changed during the calendar month
c. To identify list of all Bills of Materials deleted during the calendar month
1.1.1. Requirements:
These reports will benefit significantly from HANA acceleration and enable business teams to
perform to a higher standard. The proposed user interface is Analysis for Office (A4O) and Tableau
as this provides a flexible user interface, giving the power to business users to obtain and interpret
the data as required without further development.
Report Logic :
1. Select all the entries for Object class STUE and STUE_V from the Start of the Reporting Date’s Month
till the keyed in date in CDHDR
2. Pass Object Number and Doc No to CDPOS and select fields from CDPOS
3. Pass BOM Category and BOM Number to Table STKO and select field WRKAN(Created in Plant).
Only matching entries between user Input and this field needs to be shown in the report.
4. Pass BOM Number and Plant to table MAST and select Material # (MATNR)
5. Pass MATNR to MARA and select Material Description and Material Type
1.2 Dependencies / Constraints
N/A
1.3 Assumptions
Data loaded into HANA through ECC tables will be used for reporting.
1.4 Extension Usage
N/A.
Page 4 of 10
2 Detailed Functionality
2.1 Functional Specification
Business should be able to run the report at Cluster, Country level , Plant level in A4O. The tableau
tool should open to show a dashboard showing count of all BOM Creations , Changes and
deletions. Users should be able to drilldown to line item level details for each item in dashboard.
2.1.1 BOM Creation / Changes
Data for this is extracted from Table CDHDR and CDPOS. From CDPOS, select data for below
indicator.
Change Indicator – I, J – Creation
Change Indicator – U – Change
Change Indicator – E,D – Change
General Observations
On Tableau, Along with the past 6 Months trend, Real time trend will be displayed in an
independent Chart so that ageing summary is not impacted.
Month end figures will be locked between WD1. Offline Tableu templates will be uploaded
for previous months on one view.
2.2 Process Flow Diagram
Data Extraction:
ECC Transactional Data SLT SAP A4O
CORDILLE Master Data REPLICATION
HANA Tableau
RA SERVER
ECC Transactional Data SLT
SAP A4O
REPLICATION
SIRIUS Master Data SERVER HANA Tableau
ECC Transactional Data SLT
A4O
REPLICATION SAP
FUSION Master Data Tableau
SERVER HANA
Transactional Data SAP A4O
ECC SLT
U2K2 Master Data REPLICATION HANA Tableau
SERVER
Below data will be replicated through SLT (real-time):
ECC Master and Transactional Data
Page 5 of 10
Solution Approach
2.3 Data Model
2.4 A4O and Tableau Dashboard
The interface should open to a dashboard which is excel like tool, displaying report as a
tabular line item data.First login should report at a landscape level. User should then have
the option to save default parameters when opening the dashboard.
User will get a input prompt to execute report at
1. Cluster
2. Country
3. Plant
2.5 Geography Hierarchy Data Upload
Changes to Geography Hierarchy will be done by the Basis team through a service request.
This will be done by HANA team with incident assigned to HANA model group.
A customized table for Customer types, document types will be created in HANA
There will be option for incremental uploads or incremental deletes
The following fields to be included in the report
Field Field Description DataType Width Validation
Market
Market Cluster CHAR 25
Cluster
MCO MCO CHAR 30
Country Country CHAR 20
Plant Plant CHAR 4
Page 6 of 10
2.6 Dimensions and Key Figures for Trend Details
2.7 Data Dictionary
The data dictionary is the catalogue that includes the data elements needed for reporting. The
tables below outline all of the data elements which will be included in each of these domains.
Selection Criteria
User can run the dashboard with standard filters provided by A4O and can apply to all views or the
current view .
2.7.1 BOM Creation / Changes / Deletion
Promp Outpu
Field Description Table Field t t Comments
Instance
Reporting Date Yes Yes Input
Market Cluster Yes Yes Master File
Country Yes Yes Master File
ETS / Non ETS Yes Master File
Refer to the Master file. Per
ID Calc Yes Tabe and Field Name.
Company Code Yes Yes Master File
Company Code
Desc Yes Master File
Plant Yes Yes Master File
Plant Desc Yes Master File
If CDPOS - Change
Indicator is
I or J – Set it to “Creation”,
U – Change
Change Type Calc Yes E or D - Delete
CDHD CHANGEN
Change Number R R Yes
CDHD
Changed On R UDATE Yes
CDHD
Changed at R UTIME Yes
CDPO
Change Indicator S CHNGIND Yes
8 Characters from 5th in
CDPOS-
BOM Number Calc Yes TABKEY(Mid(x,5,8))
CDPO USERNAM
User ID S E Yes
Page 7 of 10
Refer to the Master file. Per
User name. if Username is
not present in the file, make
User Type Calc Yes it “Non System user”
CDPO
Table Name S TABNAME Yes
CDPO
Table Key S TABKEY Yes
CDPO
Field Name S FNAME Yes
Field Name
Description Calc Yes Use Master file.
CDPO
Old Value S UNIT_OLD Yes
CDPO
New Value S UNIT_NEW Yes
4th Character in CDPOS-
BOM Category Calc Yes TABKEY(Mid(x,4,1))
BOM Category
Desc Calc Yes Master File. Refer Sec 2.8
Refer Master file. Per User
Function Calc Yes Name
Refer to the Master file. Per
Sub Function Calc Yes Table and Field Name.
Material MAST MATNR Yes
Material Desc MAKT MAKTX Yes For SPRAS = EN
Material Type MARA MTART Yes
Material Type Desc T134T MTBEZ Yes
BOM Usage MAST STLAN Yes
BOM Usage Desc Calc Yes Master File. Refer Sec 2.8
Refer Master File. Per table
Change Group Calc Yes and field name.
2.8 Master Tables
BOM Category BOM Usage Field Name BOM BOM Changes-User BOM
Desc.xlsx Desc.xlsx Desc.xlsx Changes-ID,Mand Fld.xlsx
Type.xlsx Changes-Fun,Sub Fn.xlsx
2.9 Input and Output
INPUT OUTPUT BOM
CREATION CHANGE REPORT.xlsx
Page 8 of 10
2.10 Reporting
As discussed in section 2.1.
2.11 Initial Data Set-Up / Conversion Requirements
SLT replication that is currently available for all landacapes and new replication that needs to be
setup is mentoioned in the attached file
2.12 Network Integration
N/A.
2.13 Existing Sample Programs
N/A
2.14 Security and Authorisation
N/A
2.14.1 Segregated Access Requirements for Users into Single Roles
N/A
2.14.2 Risk Assessment and Considerations for the Access Required
N/A
2.14.3 Users, Teams, Jobs where access is required
N/A
2.14.4 Objects to be authority-checked.
N/A
2.14.5 Authorization Design:
N/A
2.9.6 Security and Authorization for the Vendor AM Team
N/A
2.15 Processing and Operational Considerations
2.15.1 Performance
N/A
2.15.2 Batch Requirements
N/A
Page 9 of 10
2.15.3 Data Maintenance Requirements
N/A
2.15.4 Re-Use Details
N/A
2.15.5 Error Handling
N/A
2.15.6 Log Output
N/A
2.15.7 Purge and Archive Considerations
N/A
2.16 Design Alternatives
N/A
2.17 Key Test Conditions and Considerations
Below are the key test conditions. Detailed test conditions will be created as part of unit and product testing.
No. Description Expected Result
1 A4O A4O should successfully run and bring output
Run the report by Cluster / Country/ Co
Code and plant
2 Enter different date inputs The report values should be refreshed with new
values.
3 Check the A4O output values in the with Values must match with ECC
ECC
Open points
Page 10 of 10
