| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Provide an overview of the app (e.g Domain, key processes, purpose of the app, etc) |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Describe the key User profiles that exist for the application. General role/Viewer role: Approver role: |
The quotation report is part of the BW global sales folder, playing a crucial role in enabling a comprehensive analysis of quotations generated in SAP for the AERO business line of Composite Material. The analysis covers material, customer, and pricing perspectives. The report report also monitors the status of each quote, indicating whether an order has been initiated in connection with the respective quotation. This functionality provides valuable insights into the entire quotation process within the AERO business line. |
| Info | ||
|---|---|---|
| ||
Target Users:As examples: Controllers / Accountants Composite material (aero business line) sales team |
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | dd21.mm12.yyyy2023 | Azadeh Nasiri<Insert name> | Initial draft |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
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.
| Workbooks | Technical name |
|---|---|
| Quote report | BW_WBK_CPSDAE01_SD001 |
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.
Key Figures
Key figure | Comments |
Quote quantity (PUQ) | Quantity from sales document item |
Net value item (USD) | Amount based on the USD in the daily tax rate of creation document |
NET Price (CP) | Amount per quantity |
Net Value item (CP) | Amount based on the currency prompt tax rate of creation document |
Unit Price (CP) | Amount from condition price (PR00 or ZPRE) divided by the quantity item. |
Lead Time (days) | Replenishment time from material/plant master data |
4.2 Process Detail
Scope:
- No filters applied;
- Optional Date ranges: valid from, valid to, quotation creation date
“Overall status” (at Header Level) will show whether or not an order has been created with reference to the quote line:
- Completely processed: Quote has been fully referenced
- Partially processed: Quote has been partially referenced
- Not yet processed: Quote is still not been referenced
4.2 Process Detail
4.2.1. Report/Process Definition
Available filesAccount group | Material | Program | Sales Organization |
BFC GBU | Material/Plant | Quote Creation month/year | Ship to |
BFC Group of Activities | MRP Planner | Quote document | Sold to |
Company Code | Non Spec Required | Quote line | Spec long description |
CSR | Order Line creation date | Quoted Lead time | Sub Activity |
Customer Quote ref | Overall Status (quote document) | Reason for rejection of quotations | Valid from |
Division | Overall Status (quote line) | Reference document | Valid to |
Document date | Plant | Sales account manager | |
DPAS | Price Group | Sales Office | |
| Domain | <insert name> | ||
|---|---|---|---|
| Application | >insert name> | ||
| Provider | <insert name> | Existing Documentation | <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
Please populate the relevant section and delete those that are not applicable.
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. Data in BW will be refreshed daily containing information from D-1 (CET time)