| Status | |
| Owner | Stefanie Schwartz |
| Stakeholders | The persons consulted or otherwise involved in making this decision. Type @ to mention people by name |
Issue
Succinctly describe the issue or problem statement that this Decision addresses. Why is a decision required? What business or technical problem does it address?
Waste is currently managed offline at site level. The tools and processes used for different sites and countries vary. It adversely impacts data management, data integrity and reporting in relation to waste management in Syensqo.
The exception is the Paulinia site in Brazil, where a simplified SAP subcontracting process has been implemented since 2015.
Recommendation
Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.
The recommendation is for Waste Management to be harmonised at group level for SAP related processes as a foundation for additional local requirements.
Site or country specific waste related process to support local requirements will benefit from a harmonised process for improved transparency, data integrity, data management, reporting and compliance.
Background & Context
Explain the context in which the decision is being made.
Syensqo has the responsibility to manage the generation, storage, transportation and disposing of materials deemed to be waste relevant. SAP offers the following process:
- Manage waste materials in SAP.
- Waste codes are required for the creation of waste disposal documents that meet compliance requirements.
- Manage designated business partners as waste transporters or waste disposers.
- Manage waste streams, which define the relationship between a waste product, waste generator, storage location, and the points of generation.
- Manage disposal channels to define how products can be disposed. They define the relationship between a waste stream and transporters and disposers.
- Manage waste generator locations and waste transportation documents including permits.
- Manage waste reporting.
S/4 HANA 2023 Cloud, Private Edition
Waste Management in EHS for SAP S/4HANA Cloud, private edition, you can handle the management of waste generated by an organization. It is designed to help companies comply with environmental regulations and ensure proper handling, disposal, and reporting of waste materials.
The features provide functionalities to track and manage waste throughout its lifecycle, from generation to disposal. It enables organizations to record waste generation data, classify waste types, track waste storage locations, and manage waste transportation and disposal processes.
Types of Waste: Liquid, solid, products/by-products, organic, inorganic, haz/non-haz, domestic, other
Waste disposal entities: disposal permits, disposal companies, industrial cleaning companies, certificates of destruction, disposal manifests,
Waste transport: transport permits and waste carriers
Waste treatment: landfill, recycling, recovery for energy, incineration
Reporting: site, country, group reporting
SAP Road Map
- Integration of waste management and purchasing and sales processes (cloud): Integration of waste management processes with other logistics processes like supply chain management and procure to pay. Help environment managers to:
- Procure waste disposal services
- Pay invoices in a timely manner
- Manage on-site waste storage and plan timely shipment of waste
- Waste management: integration with extended warehouse management (cloud)
- Further integration into extended warehouse management, enabling the user to track the inventory of stored waste
- Obtain deeper insights into the amounts and locations of stored waste
- Management of waste cost allocation and payments (cloud): Manage allocation of costs associated with the transportation and disposal of waste
- View costs associated with the transportation and disposal of waste
- Allocate waste transportation and disposal costs to appropriate cost centers
Assumptions
Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited.
Constraints
Capture any constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.
Impacts
Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.
Business Rules
The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order".
Options considered
List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.
Option A: Local Process only - Continuation of AS IS
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Variety of local processes specific to country or site.
Largely relying on use of local applications for data collection and reporting purposes.
No harmonisation,
Low levels of transparency and data integrity.
Option B: Group Process only
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Group Process in S/4 HANA.
Maximum harmonisation supporting transparency and data integrity.
Option C: Group Process with Local Variations
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Evaluation
Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.
Option A | Option B | Option C | Option D | |
|---|---|---|---|---|
| Criterion 1 |
|
|
|
|
| Criterion 2 |
|  Con |
|
|
| Criterion 3 |  Pro | Con | Con | Pro |
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
