2.0 Business Process

The base is the same for the Profit and Loss application in the functional documentation. We can see in that documentation the logic for the P&L.

For this application this was built in 2018 and the need was to provide a dedicated report only for GBU SD .This report is a separate report from the P&L  reports.

This new report:

• is based for main Part on P&L datas; 
• will construct Soda Ash business axis that are not existing in ERp or in actual BI reports;
  • SD BU;
  • Origin.
•  retreat some functional flow :
  • redetermination of internal or external amounts
  • reallocation of transport cost between SD BU for specific flow
• recalculate some lines of the P&L (internal sales and COGS ) for specifics flows

On a monthly basis the business needs to analyzed the logistic costs and to verify the origin information to be able to see in more detail the flows associated to Soda Ash and the impact of the values in the P&L.

The Origin/Sourcing field will provide details on where the Soda Ash is produced (for example, it can be in Europe or North America), distinguishing whether the material is synthetic or natural.

The Scope field categorizes whether it is internal or external and further checks are conducted for these flows (for example, if it is Europe to Europe or Europe intra BICAR).Capture the business process that the application supports . This can be describe through a process diagram or a business capability model

3.0 Application Feature Overview

Information about the existent Workbooks and the respective BW queries.For this scope we only have one query:

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 reportsThe base is the same for the Profit and Loss application in the functional documentation. We can see in that documentation the logic for the P&L.

4.2 Process Detail 

4.2.1.  Report/Process Definition 

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

4.2.2. KPI's/Calculations/Indicators 

Indicators available: 

• XXXX
• XXXX

Indicatores/KPI's

Definition

Calculation/Extraction of data

Can be a field, a program, something that was created or the report

What are we looking for ? Why has this KPI been created/developed? What is the goal of monitoring this data ? 

SAP BW High Level View 

To see the data from the source systems see below how the information is organized in the BW perspective: 

Image Added

General Requirements: 

Assuming that BW is the selected tool it is recommended creating a separate model/cube in BW although fed by the existing BW P&L one. 

Reasons:

• The  calculations are done at an aggregated level and cannot be made for a detailed level
• The BFC R1000 / R15400 headings cancellation (aggregated level) involve complex cross data checks.
• The request is complex and it involves some performance risks.
• The new axis of  BU SD is too complex to build in the existing P&L impacting the whole model volumetry → side effects in other GBUs

Macro process 

Image Added

We have the specifications for each step in the functional specification done in 2018.  

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.as per standard.

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 Usersas per standard.

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.,

as per standard.

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. as per standard.

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.   as per standard.

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.  as per standard.

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).as per standard.

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)as per standard.

5.9 Refresh of the Data

Frequency, data, and time of the data refresh in the data product. The load for this report it's for working days around 3 a.m.