Configuring Customizing Activities

This configuration activity allows administrators to assign specific environment management activities to designated responsibility roles, such as Environmental Manager and Environmental Technician. These roles define what actions a user can perform, such as scheduling tasks, collecting compliance data, or managing regulatory scenarios. The goal is to distribute responsibilities in line with organizational structures and regulatory roles while ensuring compliance accountability.

Used to tailor user responsibilities to their operational or regulatory scope.

For example, you might assign the Environmental Technician role to users responsible for on-site data collection, while Environmental Manager roles could be designated for regional leads responsible for scenario oversight.

Once defined, the role-activity mappings are reflected in the system’s UI and used in filtering, task assignment, and analytics. The UI components even use the configured roles in section headers and labels, which means changes to standard role names require corresponding updates in Online Text Repository (OTR) entries to maintain UI clarity.

• Maintain at least one role with the responsibility to manage compliance scenarios. This is essential for enabling the compliance task lifecycle.
• Stick with standard delivery roles if possible to avoid complications with translations and text elements in the UI.
• If custom role names are used, update the following OTR text keys:
  • EHENV_UI_SCENARIO_SETUP/ENV_MNGR_RESP_FOR_LOC
  • EHENV_UI_MDEF_SETUP/ENV_TECH_RESP_FOR_LOC
• Test role behavior in SAP Fiori apps such as Manage Compliance Scenarios and My Data Collection to validate permissions and usability.

This configuration activity allows administrators to whitelist ABAP function modules for use in user-defined calculation expressions within compliance scenarios. It enables complex, custom logic (such as conditionals, formula-based results, or dynamic thresholds) beyond what standard calculation methods support. This is especially useful in environmental reporting, where specific regulatory formulas or conditional limits must be modeled.

Used when your compliance or emission calculations require business-specific logic.

For example, if different regulatory limits apply based on region or equipment type, a custom ABAP function like EHFND_IF_GREATER_THAN could dynamically determine the correct value set.

Allowed functions must follow a specific input structure: one function name and up to five input parameters, each being a single variable (fixed value, sampled data, or previously calculated value).

These functions return a variable structure and are invoked using the keyword FUNC.

If the function is not in the allowed list, it cannot be used in expressions, and disabling it later may break active calculations.

• Define and thoroughly test any custom ABAP functions in development before enabling them in production.
• Only enable functions with clear documentation and ownership, as incorrect usage can disrupt reporting and legal submissions.
• Avoid using overly complex or undocumented logic, as future audits or consultants may struggle to interpret the configuration.
• Ensure that inputs are well-labeled in scenarios (e.g., CHECK_VALUE, LIMIT_VALUE) for traceability and transparency.
• Reassess allowed functions regularly to maintain system stability and compliance validity.

This configuration activity allows you to create and manage the types of permits relevant to your organization’s EHS operations. Permit types may be based on external legal requirements or internal control needs, and they help classify and structure permits managed within compliance scenarios.

Used to define categories such as Air Quality Permit, Hazardous Waste Transport License, or Chemical Storage Authorization.

This categorization helps EHS professionals and auditors to understand the scope of the permit, filter by type, and ensure that each compliance requirement has the appropriate permit type assigned.

Permit types appear as selectable options when creating permits or compliance requirements in the system. Each entry is uniquely identified and used throughout the compliance management process, including reporting, task creation, and audit tracking.

• Collaborate with legal and compliance teams to identify all required permit types and match them with regulatory frameworks.
• Ensure naming consistency across regions or sites to enable enterprise-wide reporting and filtering.
• Delete unused permit types only after verifying they are not referenced in active requirements or tasks.
• Document any internal-only permit types so their use is clear during audits or system rollouts.

This configuration activity links specific permit types to relevant compliance domains (e.g., Environmental, Safety, Chemical). It ensures that users only see appropriate permit types based on the regulatory or business context, which helps reduce errors and simplifies permit creation.

If your organization separates EHS responsibilities by domain, this configuration ensures, for example, that a user working in the Environmental domain does not accidentally assign a Chemical Storage permit, which belongs to the Chemical domain.

Once assigned, permit types are filtered by domain when users create or manage permits. This restriction improves user experience and prevents mismatches that could result in non-compliance or audit findings.

• Define your compliance domains first, then match each permit type to the correct domain using business logic or legal mandates.
• Use consistent naming and documentation across both domains and permit types for transparency.
• Regularly review assignments to accommodate regulatory changes or internal restructuring.
• Remove outdated assignments only after confirming they are not used in ongoing scenarios or permits.

This configuration activity defines the classifier categories available for grouping locations in SAP EHS Management, environment management. Classifiers provide a structured way to sort, filter, and report on locations based on shared characteristics.

Create classifier types, such as Facility Type, Environmental Risk Level, or Compliance Zone, and assign them to different locations to support grouping, filtering, and regulatory reporting.

Once defined, classifier types become selectable attributes within location records. These classifiers are then available for filtering in compliance tasks, analytics, and emissions reporting, enabling fine-grained process control.

• Define classifier types based on regulatory requirements, internal audits, or reporting needs.
• Avoid overly granular types, unless required, as they can increase data maintenance complexity.
• Ensure classifier names are intuitive and standardized across business units.
• Use classifiers strategically to drive dashboard filters and location-based analytics.

This configuration activity defines how emission values are determined (e.g., measured, calculated, estimated). This distinction is essential for regulatory reporting, audit trails, and internal emissions assurance.

When preparing an emissions declaration, users must select the determination method for each value. Regulatory bodies may require that some pollutants be measured directly, while others can be estimated using validated models.

Determination types are presented in a drop-down list in the My Emissions Declarations app.

The selection impacts downstream processes, such as validations, reporting formats, or audit flags.

• Use standard determination types (M = Measurement, C = Calculation, E = Estimation) where possible to align with industry norms.
• Define additional types only if required by specific regulatory bodies or internal processes.
• Train users to select the appropriate determination method based on data availability and accuracy.
• Maintain a cross-reference table between emission factors and determination types for consistency and documentation.