DataFlow

Overview

Reporting documentation drive folder:

Functional Specification for Waste Management

1. WASTE MANGT. - ENTRIES CONTROL BW 

Mapping for Waste Management

Functional Specification for Waste Management

WASTE MANGT. – BW CADRI REPORT

Mapping for Waste CADRI

Exemple of dataflow overview :

Template Application name DataFlow

General presentation

Objective of the application

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.

Usage information

Around 2 users, In Latin America first. It be implemented in other countries in the future.

History

In 2016 it was implementyed as a pilot solution for Paulinia site, however this solution can be rolled out easily to any other Brazilian site, and even to any other Region.

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.

Technical Rules on Workbench

BW EHS Waste Management and CADRI

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.       

Dependencies with other applications

There is no dependencies of other applications, just the commun use of master data, like: material, specification.

Data loadings

Info providers and objects loaded

Process Chain name: PC_EHS_WASTE_FLOW

Image Added

Remark: PC_EHS_WASTE was the original metachain, but has been replaced by chain PC_EHS_WASTE_FLOW, in order to be aligned with all BW systems

DataFlow:

Waste Management                             Waste CADRI

Image Added                   Image Added    

DSO DPEHSW01 - Waste movement

Image AddedImage Added

DSO DPEHSW02 - Waste CADRI

Image Added

Datasources:

DTS_EHS_WASTE - EHS Waste Movement

Image Added

Based on Function Module Z_WBW_DTS_EHS_WASTE

This function module is an left outer join selection of tables below:

SELECT ehswat_entam~matnr " Waste Material
ehswat000~partner " Waste management business partner */
ehswat_entam~crdat " Created On */
ehswat_entam~entamno " Entry document for Disposal Processing */
ehswat_entam~anzgeb " Number of Containers */
ehswat_entam~eaintam " Quantity */
ehswat_entam~eaextam " Outgoing quantity */
ehswat_entam~objnr " Object number
ehswat_entam~recnbpgen
ehswat_entam~recn
ehswat_entam~recnroot
ehswat_enacc~kokrs " CO AREA
ehswat_enacc~kostl " Cost Center */
ehswat_bpdefinit~objnum " Master Data Object Key */
ehswat_enfod~easucc " Follow~On Document */
ehswat_enfod~easucccat " Follow~On Document */
ehswat_enprt~eabpcount " Counter

ehswat_enfod~easucc AS banfn
ehswat_entam~matnr AS wrkst
ehswat_entam~matnr AS subid
ehswat_entam~matnr AS ident
ehswat_entam~anzgebeinh
ehswat_entam~eaintamu " Unit
ehswat_entam~eaextamu " Unit

FROM ehswat_entam " Disposal Processing (Quantity Entry/Planning)
LEFT OUTER JOIN ehswat_enprt " Disposal Processing: Partner for Entry Document
ON ehswat_enprt~recnroot = ehswat_entam~recn
AND ehswat_enprt~delflg = ' '
LEFT OUTER JOIN ehswat_enacc " Disposal Processing: Account Assignments for Entry
ON ehswat_enacc~recnroot = ehswat_entam~recn
AND ehswat_enacc~delflg = ' '
LEFT OUTER JOIN ehswat_enfod " Disposal Processing: Follow~On Document Table
ON ehswat_enfod~eapred = ehswat_entam~entamno " Entry Document
AND ehswat_enfod~easucccat EQ 'SAP009' " Document Category
AND ehswat_enfod~delflg = ' '
LEFT OUTER JOIN ehswat001
ON ehswat001~recn = ehswat_entam~recnbpgen
AND ehswat001~delflg = ' '
INNER JOIN ehswat100
ON ehswat100~recn = ehswat001~recn
* ON ehswat100~recn = ehswat_entam~recnbpgen
AND ehswat100~delflg = ' '
INNER JOIN ehswat000 " Master Table for the Waste Management
ON ehswat000~recn = ehswat100~recnroot

LEFT OUTER JOIN ehswat_bpdefinit " MD: Partner Reference to Master Data Objects

ON ehswat_bpdefinit~recnroot = ehswat100~recn
AND ehswat_bpdefinit~delflg = ' '

And individual selections in tables below:

SELECT jest~objnr
tj30t~txt30
INTO TABLE t_jest
FROM jest " Individual Object Status */
INNER JOIN tj30t " Texts for User Status */
ON tj30t~estat = jest~stat
FOR ALL ENTRIES IN t_collect_objnr
WHERE jest~objnr = t_collect_objnr-objnr
AND jest~inact NE 'X'
AND tj30t~spras = 'P' 
AND tj30t~stsma = 'ZEHS_WMM' . 

SELECT matnr
wrkst
INTO TABLE t_mara
FROM mara
FOR ALL ENTRIES IN t_collect_matnr
WHERE matnr = t_collect_matnr-matnr.

SELECT estrh~subid
estri~ident
INTO CORRESPONDING FIELDS OF TABLE t_estrh
FROM estrh
INNER JOIN estri
ON estrh~recn = estri~recnroot
FOR ALL ENTRIES IN t_collect_subid
WHERE estrh~subid = t_collect_subid-subid
AND estri~delflg NE 'X'
AND estrh~delflg NE 'X'.

SELECT recn recnroot wadescrpofg
INTO TABLE t_ehswat001_descr
FROM ehswat001_descr
FOR ALL ENTRIES IN t_data_aux
WHERE recnroot = t_data_aux-recnbpgen
AND langu = 'P'.

SELECT mnino
mnstatus
zzo_delivery
zzo_item
zzp_order
zzp_item
zz_emission
zz_quantity
zz_uom
zzinv_number
zz_manifest_doc
zz_vend_inv_doc
ehswat_approval~appno
ehswat_approval~apvalto
INTO TABLE t_ehswat_mn
FROM ehswat_mn
LEFT OUTER JOIN ehswat_approval " MD: Waste Approval
ON ehswat_approval~recn = ehswat_mn~mnapno
AND ehswat_approval~delflg = ' '
FOR ALL ENTRIES IN t_ehswat_enfod
WHERE mnino = t_ehswat_enfod-mnino
AND ehswat_mn~delflg NE 'X'.

SELECT lips~vbeln
lips~posnr
lips~werks " Plant */
lips~pstyv " Sales document item category
lips~erdat
INTO TABLE t_lips
FROM lips
FOR ALL ENTRIES IN t_collect_delivery
WHERE vbeln = t_collect_delivery-delivery.

SELECT eban~ekorg " Plant */
eban~ekgrp " Sales document item category
eban~banfn
eban~bsart
eban~bstyp
eban~ebeln
eban~ebelp
eban~flief
eban~werks
INTO TABLE t_eban
FROM eban
FOR ALL ENTRIES IN t_ehswat_enfod
WHERE banfn = t_ehswat_enfod-banfn.

DTS_EHS_WASTE_CADRI - EHS Waste Movement

This datasource is based on view ZBWEHS_WAS_CADRI

Image Added

View: ZBWEHS_WAS_CADRI - EHS Waste Cadri

Image Added

Image Added

Image Added

Reporting

BW_QRY_MVEHSW01_0001 - EHS Waste Movement (core query)

This query is used to analyze the data stored in WASTE movement

Filters

Image Added

Rows

Image Added

Columns
Image Added
Navigational Attributes
Image Added
Lay-Out
Image Added
Image Added

BW_QRY_MVEHSW02_0001 - EHS Waste CADRI (core query)

This query is used to analyze the data stored in CADRI repository

Filters

Image Added

Rows

Image Added

Columns

Image Added

Navigational Attributes

Image Added

Lay-Out

Image Added

2.0 DataFlow

2.1 Overview

Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

Exemple of dataflow overview :

Template Application name DataFlow

2.2 Technical Rules on Workbench

Explanation for the process on the technical side. Can be specific cases or general rules depending on the scope.

Dependencies with other applications

We should have the information where the application is sending or receiving information (e.g. APD open hub) 

Data Loading

Info Providers and objects loaded 

Detail of process chain, list + link between or special event done for the loading

Data Quality Control

Operational Documentation

Procedures

<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>

Scheduling

<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>

Monitoring

<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>

Error Handling

<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>

Known Bugs

<List the existing bugs, its criticity, workarounds and resolution plan.>

Roadmap

<List past & future evolutions for the application (including links to MED/FSD/TSD)>