Provide an overview of the app (e.g Domain, key processes, purpose of the app, etc) |
Describe the key User profiles that exist for the application. General role/Viewer role: Approver role: |
Target Users: As examples: Controllers / Accountants |
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | dd.mm.yyyy | <Insert name> | Initial draft |
|
Capture the business process that the application supports . This can be describe through a process diagram or a business capability model
| Category | Detailed | Technical name | Type | |
|---|---|---|---|---|
PO→ Purchase order (transfers) | ✓ | Order Book: PO - Invoiced (Current Month) | BE_WBK_MVSDSO47_003 | Invoiced |
| ✓ | Order Book: PO - To be Issued (Open Order) | BE_WBK_MVSDSO47_002 | To be Issued | |
| × | Order Book (PO): To be Issued (Snapshot) | BE_WBK_MVSDSO47_001 | To be Issued | |
| SO→ Sales Order | ✓ | Order Book: Invoiced (Current Month) | BE_WBK_MVSDSO41_SD008 | Invoiced |
| ✓ | Order Book: To be Invoiced | BE_WBK_MVSDSO41_SD011 | To be Invoiced | |
| ✓ | Order Book: To be Invoiced (Open Order) | BE_WBK_MVSDSO41_SD006 | To be Invoiced | |
| ✓ | Order Book: To be Invoiced (Shipped not Billed) | BE_WBK_MVSDSO41_SD007 | To be Invoiced | |
| ✓ | Order Book: To be Issued | BE_WBK_MVSDSO41_SD012 | To be Issued | |
| ✓ | Order Book: To be Issued (Open Order) | BE_WBK_MVSDSO41_SD001 | To be Issued | |
| ✓ | Order Book: To be issued (Shipped Not Billed) | BE_WBK_MVSDSO41_SD002 | To be Issued | |
| × | Order Book: To be invoiced (Snapshot) | BE_WBK_MVSDSO41_SD004 | To be Invoiced | |
| × | Order Book: To be invoiced + Contribution WP1 (Snapshot) | BE_WBK_MVSDSO41_SD014 | To be Invoiced | |
| × | Order Book: To be issued (Snapshot) | BE_WBK_MVSDSO41_SD003 | To be Issued | |
| × | Order Book: To be Recognized (Snapshot) | BE_WBK_MVSDSO41_SD013 | To be Recognized | |
| SO+PO | ✓ | Order Book (SO+PO): Invoiced | BE_WBK_MVSDSO49_SD004 | Invoiced |
| ✓ | Order Book (SO+PO): To be Issued (Open Order) | BE_WBK_MVSDSO49_SD002 | To be Issued | |
| ✓ | Order Book (SO+PO): To be Issued (Shipped not Billed) | BE_WBK_MVSDSO49_SD003 | To be Issued | |
| × | Order Book (SO+PO): To be Issued (Snapshot) | BE_WBK_MVSDSO49_SD001 |
Orderbook reports provide overview on Sales Orders, Purchase Orders (transfers), Sales Order Lines, Schedule Lines, Deliveries, Invoices. BW includes 14 workbooks in the subject of orderbook. The reports includes two main categories, namely, To be Invoiced and To be Issued. The first one provides the best estimation about the incoming results expected by end of the actual month and for the months to come. It is based on the placed sales order in the SAP system, and for each of them determines the expected date to be invoiced (billing date). The second one is indicated to the supply chain team because it provides the best estimation about the deliveries to be issued by end of the actual month and for the months to come. It is based on the placed sales order in the SAP system, and for each of them determines the expected date to be issued (or the best estimation when the product will leave the plant)
Sales document used in the reports
INVOICED | |||||
B1 | Reb.Credit Memo Req. | RE | RE Returns | ZDRB | Debit Memo Req. BR |
B2 | Rebate Correctn Rqst | REA | REA Returns-AR | ZITI | Sales Order ITI BR |
B3 | PartRebSettl.Request | SB | SB Third-p.dir order | ZORB | Standard Order BR |
B4 | Reb.Req.f.Man.Accrls | SO | SO Rush Order | ZOUT | Other Outputs BR |
CR | CR Credit Memo Req. | TA | Standard Order | ZPVA | ZPVA Ord.immed.ship. |
CRV | CRV Credit Mem Value | TAF | Standard Order (FPl) | ZRCM | Sales Accnt/Order BR |
DR | DR Debit Memo Req. | TAM | Delivery Order | ZREN | Returns NFe Custo BR |
DRV | DRV Debit Memo Value | TAV | Standard Order (VMI) | ZROB | Own NFe Returns BR |
KE | KE Consignment Issue | TD | TD Standard Order | ZSAM | Sample Order BR |
KR | KR Consign. Returns | TSA | Telesales | ZTDL | ZTDL StdOrder w/o GI |
R1 | R1 Fictive Return | ZCRB | Credit Memo Req. BR |
| |
R4 | R4 Returns free ch. | ZDON | Donation Order BR |
| |
OPEN ORDERS AND SHIPPED NOT INVOICED | |||
KB | KB Consign. Fill-up | ZITI | Sales Order ITI BR |
KBCC | KBCC CC Consign.Sto. | ZORB | Standard Order BR |
SB | SB Third-p.dir order | ZOUT | Other Outputs BR |
SO | SO Rush Order | ZPVA | ZPVA Ord.immed.ship. |
TA | Standard Order | ZRCM | Sales Accnt/Order BR |
TAF | Standard Order (FPl) | ZSAM | Sample Order BR |
TAM | Delivery Order | ZTDL | ZTDL StdOrder w/o GI |
TAV | Standard Order (VMI) | ZVEX | Fut. Dely Invoice BR |
TD | TD Standard Order | ZVEY | Fut. Dely Shipmnt BR |
TSA | Telesales | ZVNO | Del N/Prod(w/o acct) |
ZDON | Donation Order BR | ZVNP | Non Product Order BR |
Indexes
| PUQ | Unit prompt quantity. It is the unit quantity choosen when the report is refreshed. Can be: KG, VKG, TO... |
| CP | Prompt Currency. It is the currency choosen when the report is refreshed. Can be USD, EUR, BRL... |
| CO | Order Currency. It is the currency which the sales order was placed. |
| CR | Reference Currency. It is the currency of the legal company responsible for the sales. |
4.2.2. KPI's/Calculations/Indicators
| ASP: Average Sales Price = Order line Net value / Order line QTY | ||
| Estimated Contribution Margin (Open Order): Turnover To be Invoiced current Month (-) Unit Costs * Quantity To be Invoiced current Month | ||
| Invoiced Gross Sales M: Gross Revenue invoiced on the month M | ||
| Open Order Cust. pick-up Net value M: Total on revenue for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M. Just for the shipping conditions = Customer Pick up. This works as an alert to show how much from the Open Orders Qty M have a risk to not be invoiced by the end of month M | ||
| Open Order Cust. pick-up QTY M: Total on quantity for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M. Just for the shipping conditions = Customer Pick up. This works as an alert to show how much from the Open Orders Qty M have a risk to not be invoiced by end of the month M | ||
| Open Order M Last 5 days Net value: Total on revenue for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE in the past 5 days | ||
| Open Order M Last 5 days QTY: Total on quantity for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE in the past 5 days | ||
| Open Order Net value M: Total on Revenue for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M | ||
| Open Order QTY M: 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 with conf. qty M: 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 | ||
| Open Order with conf. qty Net value M: Total on Revenue 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 Net Value M: Total on revenue for sales orders that have been issued (with Actual GI Date) on the month M, but not yet invoiced | ||
| Shipped not Billed QTY M: Total on quantity for sales orders that have been issued (with Actual GI Date) on the month M, but not yet invoiced | ||
| To Be Invoiced Net value < M: Total on revenue for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the past. This brings in evidence sales orders that must be changed or closed | ||
| To Be Invoiced Net value M: Total on revenue for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M. This brings in evidence sales orders that must be changed or closed | ||
| To Be Invoiced Net value M+1: Total on Revenue for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M+1 | ||
| To Be Invoiced Net value M+2: Total on revenue for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M+2 | ||
| To Be Invoiced Net value M>2: Total on Revenue for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M+3 on | ||
| To Be Invoiced QTY < M: Total on quantity for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the past. This brings in evidence sales orders that must be changed or closed | ||
| To Be Invoiced QTY M: Total on quantity for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M. This brings in evidence sales orders that must be changed or closed | ||
| To Be Invoiced QTY M+1: Total on quantity for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M+1 | ||
| To Be Invoiced QTY M+2: Total on quantity for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE on the month M+2 | ||
| To Be Invoiced QTY M>2: Total on quantity for sales orders not yet issued and not yet invoiced, with the TO BE INVOICED DATE from the month M+3 on | ||
| To be Invoiced Total Net value: Total on revenue that remains to be delivered. To calculate it, subtract the Order line quantity to what was already issued or invoiced multiplied by the order line price | ||
| To be Invoiced Total QTY: Total on quantity that remains to be delivered. To calculate it, subtract the Order line quantity to what was already issued or invoiced. | ||
| To Be Issued Net value M+1: Total on revenue for sales orders with the TO BE ISSUED date on the month M+1 | ||
| To Be Issued Net value M+2: Total on revenue for sales orders with the TO BE ISSUED date on the month M+2 | ||
| To Be Issued Net value M>2: Total on revenue for sales orders with the TO BE ISSUED date on the month M+3 on | ||
| To Be Issued QTY M+1: Total on quantity for sales orders with the TO BE ISSUED date on the month M+1 | ||
| To Be Issued QTY M+2: Total on quantity for sales orders with the TO BE ISSUED date on the month M+2 | ||
| To Be Issued QTY M>2: Total on quantity for sales orders with the TO BE ISSUED date on the month M+3 on | ||
| TOTAL ASP: Total Average Sales Price = Total Net value / Total QTY | ||
| TOTAL CONF ASP: Total Average Sales Price = TOTAL CONF Net value / TOTAL CONF QTY | ||
| TOTAL CONF Net value: Open order with conf qty Net value M + Shipped not billed Net value M + Invoiced Gross sales M | ||
| TOTAL CONF QTY: Invoiced QTY M + Shipped not billed QTY M + Open order with conf qty QTY M | ||
| TOTAL Net value: Invoiced Gross Sales M + Shipped not Billed Net Value M + OPEN ORDER Net value M |
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 ? | How is the calculation, or if it's a program what are the steps or how the data is extracted if it's by files |
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.
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.
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.,
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.
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.
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.
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).
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).
Frequency, data, and time of the data refresh in the data product.