The functionality of Waste Management aims to use SAP system for optimizing the control of all relevant legal documents of waste management process, ensuring integrity, accessibility and traceability of all data and costs related to the process, and compliance with legal requirements.
The SAP module is installed and used on Solvay/RCS legacy systems.
The SVT reporting is now based on a BW solution.
Around 2 users, In Latin America first. It be implemented in other countries in the future.
For Paulinia operations SAP Environment is WP1
Today, in Paulinia we have one main user that is the Waste Administrator Management and one or two representatives per production unity. Also, not specifically, there are people that deals with transport and expedition , the purchase people and the cost control people.
| Role Code | Role Description | Explanation |
|---|---|---|
| ZR_RCS_CA_M5X | EHS - Waste Management | Menu access to transaction RRMX (bex analysis) |
| ZBI_RCS_EHS_A06 | EHS - Waste Management | Access to InfoArea WASTE |
| Authorization object | Explanation |
|---|---|
| C_PLANT | Restriction for plants in analysis |
| C_CNTRY | Restriction for country in analysis |
Reporting documentation drive folder:
Exemple of dataflow overview :
Template Application name DataFlow
The goal of Entries Control Report is to provide a report that facilitates the control of waste generation by period and its posterior management at Paulinia site.
In order to control the generation of each waste by several generating areas of Paulinia and the subsequent steps to final disposition from the supplier, it is necessary to list all Entry Documents created in the period that were not deleted, and them to have the trace of each relevant document created during the process.
Waste Management processes are transversal processes that involves EHS (DG and Product Safety), RtR, PtP and OTC.
There are 2 main transactions in Waste process:
- Edit Entry Documents - WAE0X – that creates Entry Documents, wastes, stock entries and purchase Orders,
- Edit Disposal Documents – WAM0X – that manages the details of waste expedition and posterior disposal
Both types of documents – entry and disposal – have different types of status that are linked to their current process step.
There is a governmental license –CADRI- that controls the amount of waste that can be disposed by type of waste and by disposer in a defined period. Also for each waste there are 2 codes that must be informed CETESB and IBAMA CODES.
Also, there are 2 types of classification, one related to waste and its transport, that is the normal DG country classification. And the other is a country Waste Code related to its waste nature.
Summarizing the process at Brazil:
1- The generator representative creates an amount of waste in the system. The number of units is exact but the weight is estimated. The waste will be weighed only at the time that it is being issued, therefore the quantity in Kg is estimated until the expedition time.
2- The Waste Administrator release the Entry Document and define where the waste will be stored, transferring the quantity to the defined warehouse.
3- Waste Administrator defined the disposer and the transporter and creates the Disposal Document and the purchase request that is based in a preexistent contract. There is an automatic check regarding governmental license- CADRI- if there is no allowed volume, the process is blocked.
4- In the purchase request the Waste Adm informs the date expected to issue the waste. Back office team will create the purchase order. The purchase process is a subcontracting process. Therefore there is a mirror virtual material (ZDIE) linked to each waste material (ZUNB). The waste material appears in the purchase order as a component.
5- The logistic team creates the delivery by transaction ME2O, based in the purchase order. After the delivery creation, logistics team creates the shipment order and the expedition programing. If it is the case, all the usual process regarding DG goods expedition is followed.
6- In right date, the picking is done, the truck is loaded, the waste is weighed, NFe is created and the expedition is done. The waste delivered appears as in the supplier storage control.
7- NFe copy is sent to Waste Adm that input the data updating the Disposal Document. Also, the right weight value in KG is fixed by MIGO transaction in the stock.
8- After the effective disposal, the supplier (disposer) sends a destruction certificate and the related invoice to Waste Adm. The weight informed by the supplier can be different of the registered in the expedition.
9- The Waste Adm updates data in Disposal document and changes its status. People of invoice centralized reception receives automatically information to perform MIRO and MIGO, and also closes the purchase requisition.
10- The process is finished.
There is no dependencies of other applications, just the commun use of master data, like: material, specification.
Process Chain name: PC_EHS_WASTE
DataFlow:
Waste Management Waste CADRI
DSO DPEHSW01 - Waste movement
Daily full.
This is a daily load running in 1 minute with 2000 records loaded.
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | 1 min |
| ~ Average nb of rows loaded per load | 2000 |
| ~ Total nb of rows loaded (if full) | 2000 |
| ~ Average Runtime for 10k lines | 1 min |
Around 2000 records per year per plant.
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016