2.0 Business Process

Capture the business process that the application supports . This can be describe through a process diagram or a business capability modelNot applicable

3.0 Application Feature Overview

Information about the existent Workbooks and the respective BW queries.

---

Workbooks	Technical names
Data Admin - Customer Corporate Group	BW_WBK_SD_CPSDSO54_0001
Data Admin - Customer Group	BW_WBK_SD_ADM_0002
Data Admin - Customer Master Data	BW_WBK_SD_MVSDAD02_0005
Data Admin - End Use	BW_WBK_SD_ADM_0001
Data Admin - Material Master Data	BW_WBK_SD_MVSDAD02_0006
Data Admin - Material not Converted	BW_WBK_SD_MVSDSO44_SD0009
Data Admin - Ship-to KA	BW_WBK_SD_MVSDSO44_SD0002_ADMIN

ReportsDefinitionPromptsBW Workbook QueryQuery Technical Name

4.0 Functional Specification

4.1 General Data/Calculations 

This section will approach the concepts/definitions that will be used in all the reports and required to understand the data from the reports.

Could be specific fields, closing activities, additional information to work and understand the reports.

4.2 Process Detail 

4.2.1.  Report/Process Definition 

<insert link>

This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.

GBR* Data Mapping control

This report provides data to control the mapping done for 2 axis recorded in GBR(*) and was developed to help the data mapping for the CRM Analytics tool (depending of the GBU’s decision to use it or not). The axis are:

• CORPORATE END USE

• GBU Customer Group (Group, Sub-Group, Account Type, Customer Classification)

Both are available in the BW WBP reports and in the CRM Analytics.

For the Billing date we suggest to use always 1 year period.

Tabs in the report:

Image Added

For the END USE mapping always use the Corporate end use TO LINK, to identify easily the customers and products to update in Quikload (GBR).

 (*)GBR - It is a global data repository for the data mapping done in the Quikload Tool

Data Admin - Customer

This workbook works directly with Customer's Master-Data, whether or not the customer has sales.
It is possible to control the GBR(*) customer Corporate group, even if the customer still has no sales in SAP. This report works directly with master data and for that reason the GBU can't be used in prompts (GBU defined only when the customer has sales).

Data Admin - Customer Group
This report retrieves all customers' groups (Corporate and GBU), for customers with sales in SAP. It is possible to be refreshed by GBU.

Data Admin - End Use
This report provides data to control the mapping done for 2 axis recorded in GBR(*) and was developed to help the data mapping for the CRM Analytics tool (depending of the GBU’s decision to use it or not).
The axis are:

• CORPORATE END USE
• GBU Customer Group (Group, Sub-Group, Account Type, Customer Classification)

Tabs in the report:

• END USE and SALES
• END USE link
• END USE axis
• Application
• Market
• Segment

For the Billing date we suggest to use always 1 year period.
For the END USE mapping always use the Corporate end use TO LINK, to identify easily the customers and products to update in Quikload (GBR).

Data Admin - Material not converted

It’s not possible to convert sales unit into prompted quantity unit (PUQ) when that conversion don't exist in SAP.
After choosing the PUQ the report retrieves all materials that are not converted in that unit.

Tip! To convert most quantities in Tonnes or Kilograms, you can use “VTN” (for tonnes) or “VKG” (for kilogram) in the “Prompt Unit Quantity”

5.0 Non-functional Descriptions 

5.1 Usability

5.2 Regulatory Compliance

5.3 Security

5.4 Performance

5.5 Reliability

5.6 Scalability

5.7 Compatibility

5.8 Availability

5.9 Refresh of the Data

Data loaded in GBR at day D it will be updated in BW at D+1.

5.0 Non-functional Descriptions 

5.1 Usability

Usability is about the ease with which a User can learn to start using the solution and the ease with which they can use the system.  In addition to ease of learning and ease of use, usability also includes areas such as ease of recall, error avoidance and handling, accessibility among others e.g., 99% of metadata entry Users who have use the Maintenance Dashboard should be able to change filters, extract etc., when required.  Maintenance data will be centrally stored in the Google Cloud platform, which will be available to other applications e.g., and Dashboards if needed.

5.2 Regulatory Compliance

Software systems must comply with legal and regulatory e.g., GDPR requirements, this can change depending on country, organisation industry and / or region.  The software systems must be secure from unauthorized access.  The Maintenance Dashboard will comply with Solvay’s regulations and compliance e.g., access only granted to authorized Users.

5.3 Security

Security refers to essential aspects that assure a solution and its components will be protected against unauthorized access or malware attacks.  Important considerations related to security aspects of a system are User authentication, User authorization or User access privileges, data theft, malware attacks, data encryption, and maintaining audit trails, e.g., only Users with administrator access shall be able to create new accounts and assign data access privileges to the new accounts e.g.,

• All data will be encrypted in the dashboard
• Only authorised Users / Administrative Users will be able to access data.
• Maintenance data will be split between either SCO or ECO, and Users will only have authority to one Entity data.

5.4 Performance

Performance defines how fast a software system or a particular section of it responds to certain User actions under a certain workload.  In most cases, this metric explains how long a User must wait before the target operation happens e.g., the page renders, a transaction is processed, etc., given the overall number of Users now.  Performance requirements may describe background processes invisible to Users, e.g., backup and speed of data transfers. 

5.5 Reliability

Reliability is the ability of a solution or its component to perform its required functions without failure under predefined conditions for a specified time / period.  Reliability can possibly be specified in terms of average time system runs before failure occurs, percentage of operations completed successfully within a time / period, maximum acceptable failure probability, or number of failures within a period.  Reliability aspects are in reference to (but not limited to) evaluation of the system to be considered as reliable, classification of reliability defining failures vs. regular failures, and the impact of failure on business operations.  The Maintenance Dashboard will display data from the previous refresh of data.   

5.6 Scalability

Scalability refers to the degree to which a solution can evolve to handle increased amounts of work.  The increased amount of work could be in terms of the user base, transactions, data, network traffic, or other factors e.g., the system should be able to handle an additional load of a maximum of 5,000 Users every month for the next 6 months without any noticeable performance impacts.  

5.7 Compatibility

Interoperability is the degree to which the solution is compatible with other components.  It is a measure of how effectively the system interoperates with other software systems and how easily it integrates with external hardware devices.

Interoperability aspects to be discussed during elicitation are in reference to (but not limited to) software systems to be interfaced with along with data / messages to be exchanged and any standard data formats, hardware components to be integrated with, and any standard communication protocols to be followed e.g., Order Management system will push the order file into a secured file transfer protocol server from where it will be loaded into the system through a daily job.  To guarantee between Google Cloud platform and SAP BW Queries e.g., BW_QRY_MVPMOR01_0002, Solvay has introduced a new tool called Xtract (Xtract).

5.8 Availability

Availability is the degree to which the solution is operable and accessible when required. It is a measure of time during which the system is fully operational e.g., available for use and sometimes included as a Service Level Agreement (SLA) considering its criticality to the business, e.g., the system shall be at least 99% available on weekdays between 09:00 to 18:30 Central European Time (CET).

5.9 Refresh of the Data

Frequency, data, and time of the data refresh in the data product.