Transportation in supply chain refers to the movement of products from one location to another, which begins at the start of the supply chain as materials make their way to the warehouse and continues all the way to the end user with the customer's order delivered at the doorstep.
Transport Integrated & Enhanced Reporting Solution also known as 'Tiers' is the new common reporting solution dedicated to Transportation at Solvay group for both Legacy processes and SAP ERP Systems (PF1 and RCS), offering consolidated view capabilities at Group level.
Transportation plays a central role in seamless supply chain operations, moving inbound materials from supply sites to manufacturing facilities, repositioning inventory among different plants and distribution centers, and delivering finished products to customers.
Key Users:
The key users for this existing application are:
Supply Chain Operational, Supply Chain Managers, Supply Chain Excellence, LogisticsCustomer, Managers
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 18.10.2023 | Karen Oppong | Initial draft |
| Data Product Type |
|
| Technologies |
|
Data Sources Note: list of all applications and various environment |
|
2.0 Business Process
This section captures provides more information about the background of the application, the benefits and the business process that the application supports .Introduction
The Transportation Costs analysis was developed in 2007 to attend the Rhodia users of Logistic processes. The solution had usage several DSO’s and just one cube with many detailed information. The number of tickets about inconsistency of data and bad performance some of triggers to develop a new application, in this case much more robust and covering also the Solvay data and its users.
The TIERS project was started in the begin of 2015, using a remodelling by layers Layered Scalable Architecture (LSA), in our case: propagation, business, reporting and virtual layers. The current transportation datasources from Rhodia were reused with low change and all datasources from Solvay were activated with low enhancements. Some additional master data were created to avoid duplication of data in different providers, like shipment document, shipment cost item and delivery item.
The development of project was request by the logistic areas and Jean Baptiste concentrated all the requests and generated the functional specification.
The project was started in April/2015 and it was deployed in December/2015 with all users trained.
Objective of the application
The objectives of this application is as follows:
- To create One unique, common and consolidated reporting space and solution.
- for the Solvay group
- Rationalization of the “live” solutions and reduction of evolutions requested
- To have a solution which is maintainable and sustainable.
- To streamline and Enable productivity actions on Shipment costs
- Drillable solution - allowing possibility to detect & analyse problems by showing the link from aggregated figures down to document in SAP.
- Few “core” queries/workbooks design for application (=> Use BW analysis functionalities and not just as extractor).
Benefits
The benefits of creating this solution
- Revamped reporting BW solution based on RCS (WBP-TR002) but built on old historical architecture (no project on this application for years) - mainly designed for cost reporting.
- Only aggregated monthly data available on PF1.
- Specific solution (cross legacies) built for CO2 footprint with activation of some standard extractors on PQ1.
- More than 250 existing queries in SAP => almost impossible to maintain on an efficient way, most of then not or almost not documented.
- Some previous experiences of common transversal reporting tools : WISE (working cap.) and SPRINT (Purchasing and Procurement).
- “Drillable” solution - allowing possibility to detect & analyse problems by showing the link from aggregated figures down to document in SAP.
- Few “core” queries/workbooks design for application (=> Use BW analysis functionalities and not just as extractor)
Business Processes
The key associated business processes
logistics business processes
Air,
Road,
Sea and
Rail.
The TIERS project consists in implementing a simplified global reporting solution for transport process, from planning to invoice to meet the requirements from GBUs users, SBS users and transport buyers, including processes from both companies (Solvay & Rhodia).
This solution will provide:
- automatic & consolidated BW reports on shipment costs
- based on data coming from the ERPs from both legacies (Solvay – PF1, Rhodia – RCS)
- enabling to drill-down to the ECC object at the origin of the detailed figures
- updated on daily basis
3.0 Application Feature Overview
This section contains Information about the existing Workbooks and the respective BW queries.
The application loads data of the transportation shipments, deliveries and shipment costs from ECC (Solvay and Rhodia) into BW.
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| CO2 Emissions | Tool for CO2 footprint reporting | Mandatory: None Optional:
| BW_QRY_MVSDTR01_0013 | |
Shipment events | This is used for haulier evaluation Advanced functionalities on process performances (lead-times not available through shipment standard events) Technical analysis on connectivity tools: nb of shipment with slot booking performed, date we received vessel departure information… | Mandatory: None Optional:
| BW_QRY_MVSDTR002_0001 | |
Shipment status and events | Aggregated indicators on other key figures than costs: number of shipments, number of deliveries, average lead-time, average transit time… | Mandatory: | BW_QRY_MVSDTR01_0012 | |
Shipment costs vs invoices | Also Knows as Accrual cost vs invoiced value Query for analyses at shipment level that are not relevant at delivery item level. Comparison between accrual and invoiced value. | Mandatory:
| BW_QRY_MVSDTR01_0011 | |
Shipment costs detailed analysis | Provide detailed information, allowing benchmarks, identification of productivity levers : detailed transportation costs (accruals) by material, customer, nature of costs, haulier | Mandatory:
| BW_QRY_MVSDTR01_0010 |
Accessing the Queries
To access the queries follow the below steps
Go to BW Analysis > WBP > Role DP -
4.0 Functional Specification
This section approaches the concepts/definitions used in all the reports and required to understand the data from the reports.
4.1 General Data/Calculations
The data required to build the various reports1 - Shipment cost details analysis
- Propose a detailed analysis of shipment cost accruals, detailled by materials. Make shipment costs accruals understandable.
- Allows benchmarking between materials, between customers.
- Gives some possibilities of drill down to get details on a macro figure.
- Public: sites log managers / GBU log process teams, base for Qlikview reportings
2 - Shipment cost vs invoice analysis
- Propose advanced cost analysis functionalities including invoice / accrual comparision and other ratios that can't be available at material level.
- Detect / evaluate unbilled payables.
- Audit tarif calculation
- Public: finance / controlling, sites & GBU logistics managers, data log and support teams
3 - Shipment status and events
- Technical Name: BW_QRY_MVSDTR01_0012
- Propose tracking of events on shipments. without cost considerations.
- Propose a reporting on volumetry : number of files (delivery or shipment) per flow, average value on some indicators...
- Load plan of shipping points
- Public: LOG data and support teams, GBUs sites log managers and sites operations supervisors, Transport managers
4 - CO² Emissions
- Technical Name: BW_QRY_MVSDTR01_0013
- The propose is to show the calculations about quantity of carbonic gas that is released in atmosphere considering all the shipments by zone
- Public: users that manage the environment effects and reports to governments
5 - Shipment Events
- Technical Name : BW_QRY_MVSDTR02_0001
- The propose is to show the events (problems) involving the hauliers that happened during the logistic process
Public: GBUs sites log managers and sites operations supervisors, transport managers
Perimeter
Currently the WBP Tiers Application contains data coming from the PF1 and WP1 ERP server.
Access
- Access to the Tiers Application has to be requested (See Getting an account).
- Access is managed at company level, which you will need to precise when requesting the access :
4.2 Process Detail
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.1. Report/Process Definition
| Domain | Supply Chain |
|---|---|
| Application | SAP BW |
| Provider | MVSDTR01 MVSDTR02 |
| Existing Documentation | <insert link> |
Reporting Requirements by user profile:
Targeted users have been grouped in 3 user profiles depending on the reporting activities they will handle.
Cost analysis needs :
- Detailed mapping of calculated costs (accruals)
- By haulier
- By site / plant
- By ship_to (customers)
- By shipment or shipment attribute like shipment departure point / destination point / mode / type)
- By delivery or delivery attribute like shipping condition, shipping point...
- Accrual versus invoiced value
- By shipment or shipment attributes.
- By haulier
- Time analyses
- By month of shipment completion (planned / actual)
- By shipment cost posting date
- Detailed accrual analysis by nature of cost
- Accrual net value by shipment cost item category
- Valuated condition by cost condition
- Ratio calculation
- Value per ton
- Value per KM
- Value per To/KM
- Value per container
- Value per shipment
Operation reporting needs:
- Volumetry (number of shipment & number of deliveries)
- Per GBU/plant
- Per Shipment Departure point/Shipment Destination point
- Per date (Year / Year-Month)
- Average payload per shipment
- Volumetry (number of containers)
- Per GBU/plant
- Per Shipment Departure point/Shipment Destination point
- Per date (Year / Year-Month)
- Average payload per container
- Haulier evaluation
- % OTS shipment (planned completion = actual completion)
- % OTD shipments (planned shipment end = actual shipment end)
- Number of event / Type of event / Number of shipment
- Leadtime analyses
- % of shipments with calculable transit time
- % of shipments with calculable queue time
- % of shipments with calculable “on site time”
- Average Actual transit time (shipment end - shipment completion)
- Average “queue time” (loading start - check in)
- Average “on-site” time (completion - check in)
- Average booking leadtime (shipment start - planification date)
C02 Footprint :
- Tons and Distances by mode
- CO2 emission (by mode, by GBU…)
4.2.2. Calculations
- C02 Footprint:
For CO2 Footprint calculations
The key figures required for calculating the Shipment costs detailed analysis query
are as follows
Net Value
To calculate the Net Value,
- Stored at shipment stage X cost item X delivery item level
- Net/Gross Weight
- Accrual costs vs invoice analysis:
- Shipment events:
- Shipment status and events:
Data Flows
Reporting
Calculated & Restricted key figures
| Name | Description | Formula |
| BW_CKF_MVSDTR01_0001 | No of Containers | |
| BW_CKF_MVSDTR01_0002 | Distance (SUM ship) | |
| BW_CKF_MVSDTR01_0003 | Gross W. dels. (SUM del item) | |
| BW_CKF_MVSDTR01_0004 | Net W, dels. (SUM del item) | |
| BW_CKF_MVSDTR01_0005 | Gross W, dels. (SUM delivery) | |
| BW_CKF_MVSDTR01_0006 | Net W, dels. (SUM delivery) | |
| BW_CKF_MVSDTR01_0007 | Gross W, dels. (SUM ship) | |
| BW_CKF_MVSDTR01_0008 | Net W, dels. (SUM ship) | |
| BW_CKF_MVSDTR01_0010 | No of handling units (MAX delitem) | |
| BW_CKF_MVSDTR01_0011 | No of handling units | |
| BW_CKF_MVSDTR01_0014 | Detailed Shpt. condition value | |
| BW_CKF_MVSDTR01_0015 | Invoiced Value | |
| BW_CKF_MVSDTR01_0016 | Accrual, Net value shipment | |
| BW_CKF_MVSDTR01_0017 | # Ship Relevant for SADH below 30 min | |
| BW_CKF_MVSDTR01_0018 | # Ship Relevant for SADH | |
| BW_CKF_MVSDTR01_0020 | Distance (SUM stage) | |
| BW_CKF_MVSDTR01_0021 | No of Shipments | |
| BW_CKF_MVSDTR01_0023 | No of handling units (MAX stage) | |
| BW_CKF_MVSDTR01_0024 | No of Stages (by detail) | |
| BW_CKF_MVSDTR01_0025 | No of Stages (by Stage) | |
| BW_CKF_MVSDTR01_0026 | No of Stages | |
| BW_CKF_MVSDTR01_0027 | No of Delivery Items | |
| BW_CKF_MVSDTR01_0028 | No of Deliveries | |
| BW_CKF_MVSDTR01_0032 | CO² Emission Factor | |
| BW_CKF_MVSDTR01_0040 | #Ship Relevant for Loading duration | |
| BW_CKF_MVSDTR01_0041 | #Ship Relevant for Queue time | |
| BW_CKF_MVSDTR01_0042 | #Ship Relevant for On Site duration | |
| BW_CKF_MVSDTR01_0045 | Number of HOTS | |
| BW_CKF_MVSDTR01_0046 | #Ship Relevant for booking leadtime | |
| BW_CKF_MVSDTR01_0052 | Net W. dels in VKG (SUM del item) | |
| BW_CKF_MVSDTR01_0053 | Net W. dels in VKG (SUM delivery) | |
| BW_CKF_MVSDTR01_0054 | Net W. dels in VKG (SUM ship) | |
| BW_CKF_MVSDTR01_0055 | Net W. dels in VTN (SUM del item) | |
| BW_CKF_MVSDTR01_0056 | Net W. dels in VTN (SUM delivery) | |
| BW_CKF_MVSDTR01_0057 | Net W. dels in VTN (SUM ship) | |
| BW_CKF_MVSDTR01_0070 | Gross W. dels. (MAX stage) | |
| BW_CKF_MVSDTR01_0071 | Net W. dels. (MAX stage) | |
| BW_CKF_MVSDTR01_0072 | Net W. dels in VKG (MAX stage) | |
| BW_CKF_MVSDTR01_0073 | Net W. dels in VTN (MAX stage) | |
| BW_CKF_MVSDTR01_0081 | Distance (max delivery) | |
| BW_CKF_MVSDTR01_0082 | Distance (max delitem) | |
| BW_CKF_MVSDTR01_0090 | Loading Duration (Days) | |
| BW_CKF_MVSDTR01_0091 | Transit time (Days) | |
| BW_CKF_MVSDTR01_0092 | Booking leadtime (Days) | |
| BW_CKF_MVSDTR01_0093 | HOTD delay (in days) | |
| BW_CKF_MVSDTR01_0094 | HOTS delay (in days) | |
| BW_CKF_MVSDTR01_0095 | On site duration (Days) | |
| BW_CKF_MVSDTR01_0096 | Queue time at plant (Days) | |
| BW_CKF_MVSDTR01_0097 | Planned Transp Time (Days) | |
| BW_CKF_MVSDTR01_0098 | SADH in min (by ship) | |
| BW_RKF_MVSDTR01_0001 | Number of Legs | |
| BW_RKF_MVSDTR01_0002 | Extra-costs accrual CP |
5.0 Non-functional Descriptions
Please populate the relevant section and delete those that are not applicable.
5.8 Availability
5.9 Refresh of the Data
The data is updated daily around ~5 am Paris Time using delta process via process chain schedule.







