2.0 Business Process

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.

Sales follow-up report in the global sales folder of BW includes two following workbooks. 

In terms of content, the two reports share similarities. The first report is tailored for soda ash, with modifications made to exclude certain customers. Additionally, it narrows the reporting time window to the current year (12 months). In contrast, the second report offers users the flexibility to define their preferred time window.

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.

Indexes

PUQUnit prompt quantity. It is the unit quantity choosen when the report is refreshed. Can be: KG, VKG, TO...

CPPrompt Currency. It is the currency choosen when the report is refreshed. Can be USD, EUR, BRL...

COOrder Currency. It is the currency which the sales order was placed.

CRReference Currency. It is the currency of the legal company responsible for the sales.

Key figures for Sales Follow-up

Extrapol KeyFigures are calculated using working days of the Plant
Billed KeyFigures are excluding the following Billing Document Types:

Document types
F2SR	Invoice for Services
G2CC	Commission Credit
G2CS	Cancelat. G2CC
G2SS	Cancelat. G2VS
G2VS	Credit Mem Serv.
L2CC	Commission Debit
L2CS	Cancelat. L2CC
L2SS	Cancelat. L2VS
L2VS	Debit Memo Serv
ZL2A	Downpayment
ZL2S	Cancelat. ZL2A
IV	Intercompany Billing

Open Order: Total on quantity for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the Month M. Open Order confirmed: Total on quantity for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the Month M. It shows how much from the Open Orders Qty M, have a confirmed quantity after ATP analysis.

Shipped Not Billed: Total on quantity for sales orders have been issued (with Actual GI Date) on the month M, but not yet Invoiced

Total Order: Open Order + Shipped not Billed Total Order Confirmed: Open Order conf + Shipped not Billed Shipped: Total on quantity for sales orders have been issued on the month M based on the Actual GI date Ordered (GI* date): Total on quantity ordered for month M based on *GI stands for Good Issue. The Goods Issue date is the date on which the goods physically leave the warehouse or stock and are issued for delivery or consumption. If qty is not confirmed (zero) => Last Requested GI date; If qty is confirmed => Last Confirmed GI date; If qty is Shipped (with "completed" status) => Actual GI date. Blocked and Cancelled orders are excluded.

Billed: Total on quantity invoiced on the Month M

Final Forecast: Total on quantity forecast to be shipped. Final Forecast is the forecast validated after the Demand Review (=Unconstrained Forecast). Business rule: - Past snapshots (M<1): frozen forecasts (snapshots taken on 6th of each month) - Current month (M) until 6th of the month: Final Forecast from Dynasys (updated 4x/day) - Current month (M) after 6th of the month: Frozen Forecasts (snapshots taken on 6th of each month) - Future forecast (M>1): Final Forecast from Dynasys (updated 4x/day) Constrained Forecast: Demand reviewed by the S&OP

Budget: Total on quantity budget to be shipped in current year (user can expand the view to detailed months) as maintained in Dynasys under Budget Review Customer Forecast: Forecast provided directly from the customer and maintained in Dynasys BFR03/BFR06/BFR09: Total on quantity to be shipped in current year according to each BFR version as maintained in Dynasys under Budget Review Demand Orderbook: Coming from Dynasys (not SAP), corresponds to the Order Book as requested by the Customer in the future. Sales Team Forecast: forecast entered by Sales Team in Dynasys (before forecast review) Demand Review Forecast: Forecast entered by the Demand Planner during the Demand review exercise. Once it's validated (during/after the Demand review meeting), it becomes the "Final Forecast". CSR Forecast: forecast entered by Customer Service team in Dynasys (before forecast review) Statistical Forecast: this is the Forecast generated by the statistical engine in DynaSys taking into account the History. By default, the system chooses the best model fit, but user can manually choose the desired model. ST Net Sales: Sales team Forecast x Sales Price

Sales Team Forecast ETD: Offset to the Sales Team Forecast (ETA). The Offset can be 0 months (ETA = ETD), 1 month or 2 months (values higher than 2 are unusual but can happen).

Sales Price FF: Price calculated in BW based on Final Forecast Net Sales / Final Forecast

Constrained demand Net Sales: Demand reviewed by the S&OP x Sales Price

Y Final Forecast Net Sales: Final Forecast x Sales Price

Netback Sales: Final forecast in quantity valuated with the Netback price Last Leg: Transport cost between the Plant/warehouse and the customer Term Thru: Warehouse costs (R339 and R340)

Billing NETV: Total on value invoiced in the current year

Order line NETV: Total on value ordered in the current year based on the Last Requested GI date

4.2 Process Detail 

4.2.1.  Report/Process Definition 

This report is based on:

• Historical Sales Orders from Global Sales (Cumulative Order Quantity in Sales Unit)
• Historical Deliveries from Global Sales (Actual quantity delivered in Sales Units)
• Historical Invoices from Global Sales (Billing Quantity in Sales Units)
• Current Order Book
• Demand Review from DynaSys

WBP Data refresh
 - Global Sales data are daily refreshed 
 - DynaSys data is refreshed 4 times a day (10am, 2pm, 6pm, 11pm) 

Prompt Particularity:
    Company Code: DynaSys forecasts are not defined at Company Code level. Please add value 'DYN'  to see DynaSys forecasts
    Sales Office: DynaSys forecasts are not defined at Sales Office level. Please add value 'DYN'  to see DynaSys forecasts

Temporal Aspect:

It is crucial to highlight that the importance of the month specified in user prompts varies depending on the measure included in the report. For instance, when looking at  the "Deliveries" measure, the month of November in the prompt corresponds to deliveries issued in that specific month. When focusing on the "Invoices" measure, the reference to the month of November is specific to sales orders invoiced during that period. 

• Sales Orders: Last Request Goods Issue date (C_LSTRQGI)
• Deliveries: Actual Goods Issue date (0ACT_GI_DTE)
• Invoices: Date of Invoice (0BILL_DATE)

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

 - Global Sales data are daily refreshed 
 - DynaSys data is refreshed 4 times a day (10am, 2pm, 6pm, 11pm

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.

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