2.0 Business Process

Capture The report support the business process that the application supports . This can be describe through a process diagram or a business capability modelof shipping the products from the plants. 

3.0 Application Feature Overview

Information about the existent Workbooks and the respective BW queries.

---

Ship pad (aero) report in the global sales folder of BW is providing the visibility on pending orders and all their corresponding information from different domains (Order Management, Production Planning, Quality Management, Logistics Execution).

The scope of the report:  Open Sales Orders and Purchase Orders (Stock transfer) information.

Excluded from the report: Rejected order lines, order lines with remaining quantity to be delivered below tolerance, and all schedule lines without "Actual GI date" from Delivery (shipped).

Report	Technical name
Open Orders report - External	BW_WBK_CPSDAE03_0002
Open Orders report - Internal	BW_WBK_CPSDAE03_0003
Order Book: To be Invoiced + Aero Program & Market	BW_WBK_CPSDA041_SD011
Ship Pad report	BW_WBK_CPSDAE03_0001

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.

The report is on top of SAP data with calculations on top. Data in BW will be refreshed daily containing information from D-1 (CET time)

Key Figures: 

Note: In addition to displaying original document Currency and Unit of Measure, you can select a target Currency and Unit of Measure in before execution (conversion)

• Partial Deliveries “Qty Ordered” <> “To Be Issued QTY”

Image Added

• Multiple deliveries

Image Added

• Qty Allocated: based on the existence of a batch in the delivery (batch also available)

Image Added

Available Fields:  

Passed Spec statuses:

Not assigned: order line has no Spec ID

Image Added

No batch allocated: no batch allocated in delivery

Image Added

Not all specs passed: one/multiple specs from order line not passed

Image Added

All specs passed: all required specs were passed

Image Added

• WO fields: multiple WO -> order qty and amount repeated

Image Added

• Specs: Short name concatenated by default, also available by Spec ID

Image Added

4.2 Process Detail 

4.2.1.  Report/Process Definition

Open order reports 

 It includes three reports:  Open Orders report - External, Open Orders report - Internal, and  Ship Pad report. The last one contains exact similar information by  combing the first two but different layout.

Scope of the report: Open Sales Orders information (PO excluded);

Excluded from the report: Rejected order lines, order lines with remaining quantity to be delivered below tolerance, and all schedule lines without "Actual GI date" from Delivery (shipped).

Order Book: To be Invoiced + Aero Program & Market

This report is an enhanced version of the standard “Order Book - To be Invoiced” query. Where  the concepts of Aero Program (ex: Boeing 777, 767, etc) and Aero Market (ex: Military, Civilian) are added. This “assignment” is quite dynamic and it is also split by %. Meaning that a sale of a specific material can be 60% for one Aero Program and 40% for another. The report does those calculations in the order book according to these assignments. 

Key data for Program/Market selection is Period calendar month / Distribution Channel / Material / Ship-to / Main spec (Aero specification ID)

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