| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
The GBU Fixed Costs applciation is part of Finance domain and we use mainly the SAP data from CO (Controlling) module to get data for the fixed costs and GBU level. The application GBU Fixed Costs is used to follow Solvay’s fixed costs mainly:
|
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
For this Application the access is provided based on the BW menu "FC - GBU Fixed Costs" and it's done via Service one. Fill the form In SAP system select the "WBP - BW Business Warehouse" In WBP - BW Business Warehouse : Select the Business Role select the "FC - GBU Fixed Costs" Describe the key User profiles that exist for the application. General role/Viewer role: Approver role: |
| Info | ||
|---|---|---|
| ||
Target Users: As examples: Controllers / Accountants GBU and Site Controllers and Plant Management |
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | dd29.mm09.yyyy2023 | Inês Vilares<Insert name> | Initial draft |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
2.0 Business Process
To understand the business process it's important to know the basic concept for the SAP CO module and how it's applicable in Solvay organization.
The SAP CO module in the SAP ERP (Enterprise Resource Planning) system focus on financial controlling and management accounting functions within an organization. SAP CO is designed to provide tools and capabilities to effectively manage and control costs, perform internal and external accounting, and support decision-making processes related to financial aspects of the business. SAP CO is tightly integrated with other SAP modules, such as SAP FI (Financial Accounting) and SAP MM (Materials Management), providing a cohesive and comprehensive solution for managing financial data, controlling costs, and supporting financial decision-making throughout the organization.
CO Structure in Solvay:
PF1 Structure
| Code | Description | |
|---|---|---|
| Operating concern | FO01 | Slv ERP Operating concer |
| Controlling area | CHEF | ERP SOLVAY |
WP1 Structure
| Code | Description | |
|---|---|---|
| Operating concern | Z001 | Solvay Engin.Plasti.Polan |
| Z006 | Rhodia Europe | |
| Z013 | Rhodia Europe | |
| Z025 | Rhodia Latin America | |
| Z026 | Rhodia Asia Pacific | |
| Z028 | Solvay North America | |
| Controlling area | = Operating concern | |
- PF1 & WP1 cost centers are included as long as there are included in the hierarchy ZCBS.
-
- For the cost elements in both systems they are included in the new hierarchy ZSOLV (old ZRCS-FC hierarchy). See more information about the change of the group in the Process Detail section for the hierarchy.
| Info | ||
|---|---|---|
| ||
In the systems we can see the hierarchy using the SAP transaction KSH3 - Display cost center hierarchy to see the hierarchy respective to the cost center organization. In the systems we can see the hierarchy using the SAP transaction KAH3 - Display cost element group to see the hierarchy respective to the cost element organization. In the Process detail section we show in more detail the hierarchy and restrictions for this scope. |
The fixed costs report is available by GBU.
In WP1, the GBU comes from the Profit Center of the cost center while in PF1 it comes from the Business Area of the cost center
GBU determination in WP1
The determination of the GBU in WP1 is done with the Profit Center Standard hierarchy
Example
1. The profit center of the cost center 6062-6227 is 6062-I1184
2. The profit center belongs to the GBU Soda Ash
3. In the fixed costs report, the cost center 6062-6227 is allocated to the GBU Soda Ash
GBU determination in PF1
The determination of the GBU for PF1 cost centers is done with the Business Area
Determination of the plant
The report is available by production site or headquarter. It comes from the Profit Center department
Report at origin - indirect production cost center
Report at destination - indirect production cost center
For the GBU fixed costs we use the SAP information from the controlling part to analyze the fixed costs at GBU level. For this it's important to understand the structure behind and how the business see the costs and be able to analyze the information to perform their activities during and end of month.
Model behind for PF1 and WP1:
Curently we have the WBS, cost centers and orders objects with values coming from the purchase orders and accounting entries. Each object is linked to a cost center which we call it "Responsible Cost Center" and this cost center is linked to a GBU.
We have the primary postings and during the closing process we have the settlements cycles (which will allocate the costs to a final cost center) and the final cost centers has the correspondent cost element for COPA line items to be present in the P&L report for PF1 and WP1 using the respective value field.
Reporting fixed costs challenges : reconciliation SAP/BFC:
In the controlling side we have primary posting in the CO objects for the fixed costs and during the closing we have the settlement cycles to transfer/allocate the costs to a final CO object and to be in the respective lines in P&L.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.For this application find below all the workbooks available:
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| FC - Cost center master data (Core Query) | This report is used to display the master data of all cost centers in WP1 & PF1 including the ZCBS hierarchy, the GBU and the plant code. | Mandatory: N.A Optional:
| BW_WBK_FC_0003 | BW_QRY_C_COSTCTR_0001 |
| FC - End month - P&L reconciliation COPA (Core Query) | In this report the users can check the costs in the cost center and the respective cost element and the same amount allocated in P&L destination (COPA). The ZSOLV Group 4 as the default values - different from:
The field Function has default options - different from:
The field Variable Cost has the default option to be excluded: X | Mandatory:
Optional:
| BW_WBK_FC_0001 | BW_QRY_MPR_FC003_0003 |
| FC - End month - P&L select - Monthly P&L Impact (Core Query) | This report shows the amounts allocated to the fixed costs in P&L but it's recommended to be used when the users wants to analyze the amounts allocated to different GBU's or Group of Activities. You can see more details in the section "Process Detail → Workbook Details" . The field BFC Account has default options selected:
The ZSOLV Group 4 as the default values - different from:
The field Function has default options - different from:
The field Variable Cost has the default option to be excluded: X | Mandatory:
Optional:
| BW_WBK_FC_0007 | BW_QRY_MPR_FC003_0009 |
| FC - End month - P&L select - P&L Impact (Core Query) | This report shows the amounts allocated to the responsible cost center for fixed costs in P&L regarding the actual destination and the GBU's involved. You can see more details and examples in the section "Process Detail → Workbook Details" . The field BFC Account has default options selected:
The ZSOLV Group 4 as the default values - different from:
The field Function has default options - different from:
The field Variable Cost has the default option to be excluded: X | Mandatory:
Optional:
| BW_WBK_FC_0006 | BW_QRY_MPR_FC003_0008 |
| FC - CO Orders master data (Core Query) | This report shows the master data for CO orders with settlement details. | Mandatory:
Optional:
| BW_FC_WBK_0008 | BW_QRY_CPCOCC01_0001 |
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| GBU | Refer to the Global Business Unit and it's a concept used in our officil reporting tool. To know how we get the GBU for PF1 and WP1 systems this is detail in the Process Definition section. |
|---|---|
| Cost Center | A cost center is a specific organizational unit within a company that is responsible for incurring costs. It represents a location, department, or function where expenses are generated. Cost centers are used for tracking and controlling costs, allocating expenses, and monitoring budget compliance. |
| Responsible Cost Center | A responsible cost center is a subcategory of a cost center that is responsible for specific cost incurrences within the main cost center. It allows for more detailed tracking and allocation of costs within a broader cost center. Responsible cost centers help organizations drill down into expenses for greater accuracy in cost analysis and control. Responsible Cost center is : |
| Cost element | It's a categorization used to track and classify expenses incurred by an organization. It represents a specific type of cost, such as wages, materials, rent, or utilities, and serves as a fundamental building block for cost accounting and reporting. Cost elements are essential for allocating and analyzing costs within the SAP CO module. It's the P&L account used to post the amounts in SAP CO document. |
| Plant | Refers to a specific physical location or facility within a company's organizational structure. |
| Cost Center Hierarchy | Refers to a structured arrangement or organization of cost centers within a company. It establishes a hierarchical relationship among cost centers, typically based on their functions, responsibilities, or reporting structures. This hierarchy helps in organizing and managing cost centers efficiently for accounting, budgeting, and reporting purposes, allowing for better control and analysis of costs across the organization. |
4.2 Process Detail
4.2.1. Report/Process Definition
| Domain | <insert name>Finance |
|---|---|
| Application | >insert name>BW reports under FC - GBU Fixed Costs folder |
| 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.
4.2.2. KPI's/Calculations/Indicators
Indicators available:
- XXXX
- XXXX
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
| MPR_FC003 |
| Info | ||
|---|---|---|
| ||
In this section we will approach: |
| Info | ||
|---|---|---|
| ||
The GBU Fixed Costs it's based in an existent model, since many years ago exist a controlling model to be more accurate for the GBU needs. We take the model already developed and it was enhanced to follow the fixed costs specially in the cost center at GBU level. We have the PF1 and WP1 systems and we are using the main CO objects cost centers, WBS and orders and with this information extracted the data is splitted in two BW tools one side the GBU fixed costs and the other solution is CBS for the functions (This scope is explained in the "Corporate Business Services application"). For both applications we use the same data base and the same cubes but the multiproviders are different also because of the authorization part. The GBU Fixed Cost application are using COPA data's for reconciliation purpose |
SAP BW High Level View Anchor SAP BW High Level View SAP BW High Level View
| SAP BW High Level View | |
| SAP BW High Level View |
To see the data from the source systems see below how the information is organized in the BW perspective:
Hierarchy Anchor Hierarchy Hierarchy
| Hierarchy | |
| Hierarchy |
All cost centers for this scope are stored in a unique hierarchy ZCBS.
- The cost centers for the GBU fixed costs are identified by an unique sub-folder in ZCBS hierarchy : ENTRP (some others filters are done and they are identified in the section below Restrictions). See more details for the structure for cost centers hierarchy ZCBS in the GBU cost center section.
- The cost elements for the fixed costs are identified by specific folder (ZSOLV) and sub folder. Refer to ZSOLV Cost Element Group ZSOLV
| Note |
|---|
In the Cost Element Hierarchy from 01 Jan 2022 the Cost Element Group ZRCS-FC it was replaced by the Cost Element Group ZSOLV. In the reports we have information for the ZSOLV group and the reports working for the filters and key figures with the new group (ZSOLV). |
Restrictions Anchor Restrictions Restrictions
| Restrictions | |
| Restrictions |
To determine GBU Fixed Costs perimeters, there is restrictions on:
- Cost center
- Cost element
- Miscellaneous filters
Restriction on cost center
As already mentioned for GBU Fixed Cost we only analyse ENTRP (1 Organisation attribute = ENTRP of the Responsible Cost center ). By default we must excluded some “2 Function” attributes values in the reports. The users can delete these default filters.
Cost center hierarchy ZCBS : restrictions
Restriction on cost element:
In the cost element BW object the cost element hierarchy was denormalized (levels of the hierarchy are translated as attributes of cost element).
By default we must excluded some “ZSOLV Group 4 “ attributes values in the reports. The users can delete these default filters.
Cost element hierarchy ZSOLV Group 4 : restrictions: The below Groups are excluded from the report by default
Miscellaneous filters:
Order Type : we exluded (investment) :
- ZPM4
- ZPM6
Project Type we exluded (investment) :
- II
- FD
Value type
- 10- Real
- 20-plan
Currency type
- 10 company code currency
Special Case: mixed cost center Anchor Special Case: mixed cost center Special Case: mixed cost center
| Special Case: mixed cost center | |
| Special Case: mixed cost center |
Because some cost centers are not 100% fixed (or variable), we identify them by an attribute mixed cost center = X
For this cost center we must check if the cost element is variable or not using XCS-ALL hierarchy (to exclude them)
We need a characteristic to identificate these cost element (with an X as attribute )
How to identificate “Mixed Cost center “?
All cost center ENTRP with level 4 node finishing by Y in ZCBS Hierarchy
How to identificate “variable cost” element?
use XCS-ALL hierarchy
The variable cost elements are all cost element attached to a node starting with "XCS-V" ou "XCS-S" (or attached to sub node under XCS-VCAL et XCS- SELL).
Plant vs Responsible Plant Anchor Plant vs Responsible Plant Plant vs Responsible Plant
| Plant vs Responsible Plant | |
| Plant vs Responsible Plant |
- Plant is the physical plant
- Responsible plant is financially responsible of the cost center
- Responsible plant is an authorization object
- In SAP (WP1/PF1) responsible plant is in the field department of the profit center of the cost center
The report is available by production site or headquarter. It comes from the Profit Center department.
Workbook Details Anchor Workbook Details Workbook Details
| Workbook Details | |
| Workbook Details |
FC - Cost center master data (Core Query)
| Info | ||
|---|---|---|
| ||
The workbook BW_WBK_FC_0003 FC - Cost center master data is used to display the master data of all cost centers in WP1 & PF1 including the ZCBS hierarchy, the GBU and the plant code. It is used to control the consistency of the cost centers master data and ensure the FC - Create a fixed costs report is working well. |
When you open the workbook for the 1st time, the following columns are displayed:
- Source System
- 0 Hierarchy
- 1 Organisation
- 2 Function
- 3 Sub-funct Grouping
- 4 Sub-function
- CO area
- BFC GBU
- Cost Center
- Company code
- CCtr Category
- Business area
- Profit Center
- Obsolete object
| Tip |
|---|
By default the report is filtered on the ZCBS group = ENTRP but the filter can be removed to display all cost centers. |
| Tip |
|---|
It is recommended to filter on active cost centers with "Obsolete object" = 0 |
For each cost center there is:
- the cost center master data coming from KS03 - Display cost center:
- Code & description
- Company code
- Profit center
- Business area (only in PF1)
- Person responsible and its position (from SRM7 financial matrix)
- Obsolete object = 0 when the cost center is active or 1 when it is closed and can not be used
- the 5 levels of the ZCBS hierarchy
- Other information:
- BFC GBU is coming from the profit center for cost centers created in WP1 and from the business area for cost centers in PF1
- Person Resp. is the name of the person responsible assigned to the Position (in SRM7)
- Plant is the department of the profit center
FC - End month - P&L reconciliation COPA (Core Query)
Overview of the fixed costs workbook
When you open the workbook for the 1st time, you have the following columns displayed:
- GBU
- Function determined with the ZCBS hierarchy
- Cost centers
- Plant
- Cost elements Group ZRCS-FC
- Actual - Destination (Conv) = primary & secondary cost elements. (you can click
to see the detail). => conversion is done with the currency entered in the prompt - P&L Destination (Conv). Costs in COPA after cost centers settlement in the corresponding value field. (based on ZCBS hierarchy correspondance)
- Actual Destination (Local) = same as (6) in local currency
- P&L Destination (Local) = same as (7) in local currency
FC - End month - P&L select - P&L Impact (Core Query) and FC - End month - P&L select - Monthly P&L Impact (Core Query)
The workbook that is recommended to use when working on fixed costs analysis is FC-End month - P&L reconciliation COPA (Core Query). However when working with cost centers shared with other GBUs, the workbook "FC-End month - P&L select - P&L Impact" can be more relevant.
In this page, you will see based on an example the difference between the standard workbook FC-End month - P&L reconciliation COPA (Core Query) and the workbook "FC-End month - P&L select - P&L Impact" and in which cases it is recommended to use the workbook "FC-End month - P&L select - P&L Impact".
Then there is the procedure to access the workbook "FC-End month - P&L select - P&L Impact" with a description of the prompt and main measures available in the workbook.
What is the difference between the standard workbook "Reconciliation COPA" and the workbook "P&L Impact"
Let's take an example to explain the difference between both workbooks:
Example
The cost center 7418-6007 is used to record the administrative costs of the legal entity 7418.
In January 100 kUSD were posted on the cost center 7418-6007 with the detail below:
| Labour | 60 kUSD |
|---|---|
| T&E | 10 kUSD |
| Other | 30 kUSD |
Standard case: One cost center = One GBU
The owner of cost center 7418-6007 is the GBU CS - Novecare as its profit center 7418-I0449 belongs to the GBU CS - Novecare (see: Profit center )
In the standard BW fixed costs report (FC-End month - P&L reconciliation COPA (Core Query)) , all costs posted on the cost center 7418-6007 are reported in the GBU Novecare. It corresponds to what is expected if the cost center is fully allocated to the GBU Novecare.
| Info | ||
|---|---|---|
| ||
When cost centers are fully allocated to a single GBU which is the most common case, it is recommended to use the workbook FC-End month - P&L reconciliation COPA (Core Query). |
Special case: One cost center = More than one GBU
However in some cases a cost center can be shared with other GBUs. For instance the cost center 7418-6007 can be shared with other GBUs and allocated to the P&L to several GBUs as detailed in the diagram :
The GBU CS - Novecare doesn't want to report 100 % of costs posted in the cost center 7418-6007 but only 21 % of the costs allocated to the GBU with the same level of details (Labour / Purchases / T&E). In this case, the workbook FC-End month - P&L select - P&L Impact can be used.
| Info |
|---|
When cost centers are shared with other GBUs, it is possible to use the workbook BW_WBK_FC_0006 FC-End month - P&L select - P&L Impact (Core Query) or BW_WBK_FC_0007 FC-End month - P&L select - Monthly P&L Impact (Core Query) to report the part of the cost center allocated to each GBU. |
Access the workbook: FC-End month - P&L select - P&L Impact
Select the workbook you want to use:
- BW_WBK_FC_0006 FC-End month - P&L select - P&L Impact (Core Query)
- or BW_WBK_FC_0007 FC-End month - P&L select - Monthly P&L Impact (Core Query)
| Info |
|---|
What is the difference between the 2 workbooks ? The difference is the exchange rate used, the rest is the same. When there is "Monthly" in the description of the workbook it means the exchange rate conversion is done as it is done in BFC. (see: P&L - Exchange rates) |
- Enter the Fiscal Year/Period: in the example 001.2019
- Enter the BFC GBU code: in the example CS for Novecare
- It is possible to enter 5 group of activities (detailed in the section Allocation by group of activities )
- By default there is the list of BFC accounts used for SG&A
| Info |
|---|
Can we remove the filter on BFC accounts without risk ? The allocation of costs by GBU can only work when a cost center is directly allocated to the P&L. It can not work when the cost center is allocated to another cost center (ex: indirect production cost centers that are always allocated first to a direct production cost center). The aim of the filter by default is to exclude cost centers not directly allocated to the P&L. It can be removed but with a risk of seeing dummy results. |
The report is displayed with:
- BFC Global Business Unit: GBU coming from the master data of the cost center
- Actual - Destination: Total costs posted in the cost center
- P&L Paid by CS: The part of the cost center allocated to the GBU selected in the prompt
Allocation by group of activities
In some cases the allocation of cost center is done at the group of activities level. In this case it is possible to select the group of activities you want to detail in the prompt.
For instance 6% of the cost center 7418-6007 is allocated to the group of activities TSDPH and 11% to the group of activities TSADT.
- Enter the P&L GBU: TS for Technology Solutions
- Enter the group of activities 1: TSDPH
- Enter the group of activities 2: TSADT
The report is displayed with:
- P&L Paid by TS: The part of the cost center allocated to the GBU selected in the prompt (=TS)
- P&L Paid by BU 1: The part of the cost center allocated the group of activities 1 (=TSDPH)
- P&L Paid by BU 2: The part of the cost center allocated the group of activities 2 (=TSADT)
Other Measures
In the workbook, a long list of Measures are available. However most of them are useless for the reporting but they can be used to understand the detail of the calculation done by BW.
For instance, you can display the measure "P&L allocation - Total" to control the calculation done by BW.
In the example:
- The measure "P&L allocation - Total" (2) is the total of costs posted on the cost center reported on each raw.
- The measure "P&L allocation - Total GBU TS" (3) is the part of the cost center that was allocated to the P&L. It comes from the P&L in COPA.
- The part allocated the the GBU (3) divided by the total of the cost center (2) gives a ratio (5) that is used to calculate the measure "P&L Paid by TS (4)
Obviously it is not necessary to display the measure (3) & (4) in the final reporting but can be used to understand how the allocation to a GBU is done.
FC - CO Orders master data (Core Query)
| Info |
|---|
The query BW_QRY_CPCOCC01_0001 FC - CO Orders master data (Core Query) is used to display the master data of all CO orders in WP1 & PF1. The query combines the orders master data with the Settlement details, to maintain the clean-up of the Finance Master data (CO Orders). In order to maintain the regular clean-up of the CO Orders by Authorization Scope, we have created this query to ease the quarterly clean-up procedure. Restrictions for the query output (Applied in the backend): CO AREA: PF1 = CHEF WP1 = Z006 , Z013 , Z025, Z026 and Z028 ORDER TYPE: PF1 = Y* (Y000 to YZZZ) WP1 = ZORD , Y991 , Y998 and Y999 STATUS: Orders with Status "CLSD" (Closed) , "LKD"(Locked) or "DLT" (Marked for Deletion) will be excluded in the report output. For more detailed information, you can check the functional specification documentation. |
5.0 Non-functional Descriptions
5.1 Usability
as per standard.
5.2 Regulatory Compliance
as per standard.
5.3 Security
as per standard.
5.4 Performance
as per standard.
5.5 Reliability
as per standard.
5.6 Scalability
as per standard.
5.7 Compatibility
as per standard.
5.8 Availability
as per standard.
5.9 Refresh of the Data
The loads for the GBU Fixed Costs application is the following:
Closing Time:
Outside of Closing: it's one time on a daily basis.
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.