General presentation

Objective of the application

This report in BW Shows combined attributes of Material class attributes (Class-- Z_CM_MAT) and Material master attributes from WP1

There are two transactions in WP1  that can be used for Material master key information

MM03: Material Master attributes

CLO2: Material class attributes 

Usage information

History

https://drive.google.com/drive/folders/1uhzOszJxrDsikG4l0-tCNRZWdKd2Aenc

Roles & Access

Roles and access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Authorization objects

List of autorisation objects mandatory for the application.

Dataflow overview

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Data source level changes

1. Added the class characteristics with class type- Z_CM_MAT  to  1CL_OMAT001 Data source in WP1

2. Enhanced the Basic data text field to  Data source -0MATERIAL_ATTR in WP1

3.  Create the below Text Data flow for Material class characteristics  in WP1.

1CL_AZ_C008
1CL_AZ_C009
1CL_AZ_C010
1CL_AZ_C011
1CL_AZ_C012
1CL_AZ_C013
1CL_AZ_C014
1CL_AZ_C015
1CL_AZ_C016
1CL_AZ_C018
1CL_AZ_C019
1CL_AZ_C020
1CL_AZ_C021
1CL_AZ_C022
1CL_AZ_C023
1CL_AZ_C024
1CL_AZ_C026

BW Changes 

We have created new report based on three Master data objects : C_MATNR2 + C_MATNR3 and C_MATCLS

Reason to create C_MATNR3 is,  not possible to add additional attributes to existing Master data  C_MATNR2

Composite provider designed based on CPMATCLS,

We have combined C_MATNR2 and C_MATNR3 using inner join and C_MATCLS as outer join to this Join.

Dependencies with other applications

Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...

Data loadings

Info providers and objects loaded

Detail of process chain, list + link between or special event done for the loading

Loading frequency

Detail of frequency : monthly; weekly or else

Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Queries End User Documentation

Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.

Main queries

List the most important and complex queries only with a link to the documentation

Main functionalities

Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts

Broadcast

Indicate if there are broadcasts and give some details on the broadcast settings.

Maintenance

Known bugs

Give the list and explanation on the known, not-solved, bugs.

Recurring procedure

List recurring procedures

Planned Evolution

Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016