| The purpose of the application is to provide Solvay users a set of reports to follow-up Packaging costs.SCREEN is 2 Log & Pack Dashboards providing Cost transparency & key performances analysis.One Single Source of Truth for Procurement, Package Owners, Supply Chain and Finance, but also for Business as well in GBU and at Excellence Center ⇒ Costs reconciled with P&LProviding Cost transparency making links between flows from Plants to Customers, Vendors & Packages including Volumes Sold, delivered and handling units,....Providing understanding of action impacts from various programs (E2E program, & all GBU projects) Leading to a standard way to assess performancesSupporting the identification of process issues and quality of data |
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 | 13.11.2023 | Karen Oppong | Initial draft |
|
Capture the business process that the application supports . This can be describe through a process diagram or a business capability model
Information about the existent Workbooks and the respective BW queries.
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| SCREEN - Pack. Inventory analysis (Core Workbook) | The aim of Inventory query is to provide users with an helicopter view in qty/value of Packaging stocks in WP1 and PF1
| BW_WBK_SCRE_0001 | ||
| SCREEN - Pack. Manuf. Consumption analysis (Core Workbook) | The aim of this query is to provide users with a transversal view of Packaging material consumption in production process in WP1 and PF1 | BW_WBK_SCRE_0003 | ||
| SCREEN - Pack. Purchasing analysis (Core Workbook) | The aim of Purchasing query is to provide users with a transversal view in qty/value of Packaging Materials purchasing in WP1 and PF1at following steps:
| BW_WBK_SCRE_0002 |
SCREEN - Pack. Inventory analysis (Core Workbook)
It is based on stock postings of Packaging materials
Packaging entries are filtered according to material Valuation classes and related Stock accounts: WP1 Z110 (GL Account 31000300) and PF1 Z051 (2110110000) + WP1 adjustment account 31000309
SCREEN - Pack. Manuf. Consumption analysis (Core Workbook)
It includes:
Actual production quantities and costs (total + variable) of products including “direct” packaging consumption, in order to measure weight of packaging vs production metrics. “Direct” means that if finished B has semi finished A in its BoM, and if A has packaging component P in its BoM, only A is reported as product in Screen report (and not B) => multi level consumption is not supported.
SCREEN - Pack. Purchasing analysis (Core Workbook)
It mainly includes Purchase orders data (with Creation date greater than 01.2018)
PO items w/o a Material (i.e. only assigned to a Material Group) are excluded from the report
It also includes FIGL data:
=> Same filter based on Material Val. Class in KOS/KBS FI items (see accounts WP1 40100380 / PF1 2320000000)
=> Same filter based on Material Val. Class in PRD/AKO FI items (see accounts WP1 98151982 / PF1 6091311100)
Access the workbook
Step One

=> Go to Analysis for Office in excel
=> Click "Open Workbook"
Run the workbook

It is mandatory to enter:
It is also possible to enter:
Click "OK"
The report is displayed with :

Run the workbook
It is mandatory to enter:
It is also possible to enter:
Click "OK"
The report is displayed with :
Run the workbook
It is mandatory to enter:
It is also possible to enter:
Click "OK"
The report is displayed with :
Run the workbook
It is mandatory to enter:
It is also possible to enter:
Click "OK"
The report is displayed with :
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
SCREEN - Pack. Inventory analysis (Core Workbook)Quantity key figures
Opening Stock Qty (w/o. Consign.): in material base UoM, according to selected period in prompt (Ex. 01.2021 ⇢ 01.01.2021)
Purchasing Var. Qty: in material base UoM, according to selected period in prompt (Ex. 01.2021 ⇢ 01.01.2021 to 31.01.2021)
Packaging postings assigned to a PO (and not assigned to a Process order/Cost collector), mainly allocated to movement type 101/102 (GR goods receipt/Reversal)
Manuf. Consumpt. Var. Qty: in material base UoM, according to selected period in prompt
Packaging postings assigned to a Process order/Cost collector, also allocated to movement type 261/262 (GI for order/Reversal)
Others Var. Qty: all other GR/GI which are not Purchasing nor Manuf. consumption
Ending Stock Qty (w/o Consign.): in material base UoM, according to selected period in prompt (Ex. 01.2021 ⇢ 31.01.2021)
Consignment quantities are displayed separately
Var. Qty check (6) = Closing stock (5) - Opening stock (1) - Purchasing (2) - Consumption (3) - Others (4) = 0
Opening Stock: in Local (company) /Target currency, according to selected period in prompt (Ex. 01.2021 ⇢ 01.01.2021)
Purchasing Var: in Local (company) /Target currency, according to selected period in prompt (Ex. 01.2021 ⇢ 01.01.2021 to 31.01.2021)
Packaging postings assigned to a PO (and not assigned to a Process order/Cost collector), mainly relative to movement type 101/102 (GR goods receipt/Reversal)
Manuf. Consumpt. Var.: in Local (company) /Target , according to selected period in prompt
Packaging postings assigned to a Process order/Cost collector, also related to movement type 261/262 (GI for order/Reversal)
Others Var.: all other GR/GI which are not Purchasing nor Manuf. consumption
Ending Stock Loc./Target Curr.: in Local (company) /Target currency, according to selected period in prompt (Ex. 01.2021 ⇢ 31.01.2021)
Variation value check (6) = Closing stock (5) - Opening stock (1) - Purchasing (2) - Consumption (3) - Others (4) = 0
SCREEN - Pack. Manuf. Consumption analysis (Core Workbook)
It includes:
Actual production quantities and costs (total + variable) of products including “direct” packaging consumption, in order to measure weight of packaging vs production metrics. “Direct” means that if finished B has semi finished A in its BoM, and if A has packaging component P in its BoM, only A is reported as product in Screen report (and not B) => multi level consumption is not supported.

It mainly includes IMEP - Integrated Manufacturing & Energy Performance data
Related products are all the ones for which packaging is consumed in the same Plant / Period (IMEP - Index 1 = 1)
It also includes P&L data (sales):
For all selected products (see above), some related sales infos (including Sold quantity, Net sales and Variable Costs of Sales) are pulled from COPA at Company code / Period level. That means that for ex in Period 01.2021, if Material 10363 is produced in Plant 7851, the whole sales of 10363 in Company 8090 are taken into account, and not only sales from Plant 7851
It is assumed that, most of the time, production and sales do not occur during the same period; for this reason, comparisons should be done for several rolling periods in order to minimize this time effect
Prod. Actual qty: actual production qty issued from Production/Process orders (IMEP index 1 = 1)
QUR *100: Pack. Actual qty / Prod. Actual qty * 100
Actual number of packaging units needed to produce 1 unit of finished product
by product sold (=Material (Prod.)
Packaging costs / sales
SCREEN - Pack. Purchasing analysis (Core Workbook)
Agreement Unit price (in local & target currency)
Not all Purchase orders are created with reference to an Agreement/InfoRecord
Ordered
GR qty: Quantity received in PO UoM & in Material base UoM
GR value: Value of goods received in PO Currency & in Local (Company code) currency or any Target currency if entered in prompt
GR unit price: GR value in Local curr. / GR qty in PO UoM & GR value in Local/Target curr. / GR qty in PO UoM
GR Price diff.: difference between GR value and standard value of stock entry, in PO & Local or Target curr., when posted in GR doc.
Standard value = GR qty * Material standard price
There are specific indicators to follow-up consignment:
GR Unit Price & Price diff. columns/ratios are the same for both standard and consignment GR
Standard value = IR qty * Material standard price
As for goods receipt, there are specific indicators to follow-up consignment invoices:
As Consignment invoices are auto invoices (MRKO tr.), no IR Price diff. should occur
IR Unit Price & Price diff. columns/ratios are the same for both standard and consignment IR
| 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.
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).
Data update
SCREEN - Pack. Purchasing analysis (Core Workbook)
=> Sources are the same than the ones used in SPRINT - Solvay Purchasing Reporting INTelligence