Results for “ghg_emission_rates_pkg”

34 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GHG_EMISSION_RATES_PKG is the core PL/SQL package within the Oracle E-Business Suite Environmental Tracking and Reporting Manager (ETRM) module responsible for managing greenhouse gas (GHG) emission rate definitions and applying those rates during emission calculation. In EBS 12.1.1 and 12.2.2, ETRM is the application layer that allows organizations to quantify, monitor, and report greenhouse gas emissions associated with suppliers, items, facilities, assets, and ledger transactions. This package, owned by APPS and declared AUTHID CURRENT_USER, serves as the computational engine that resolves which emission factor applies to a given transaction or event, validates the availability of rates, locks rate periods from further modification, and creates the corresponding ledger entries that represent quantified emissions.

The package addresses the central ETRM problem of rate resolution: for any combination of emission source, scope, location, date, supplier, supplier site, item, asset, and facility, the package determines whether a valid rate exists and, if so, returns the appropriate factor. It also supports factor date boundary determination and rate ID generation, making it a foundational utility invoked throughout the emission accounting lifecycle.

Key Procedures and Functions

The package exposes ten documented procedures and functions:

  • RATE_IN_USE — Determines whether a specified rate is currently referenced or active, supporting integrity checks before rate maintenance.
  • GENERATE_RATE_ID — Produces a unique identifier for a new emission rate record.
  • GET_MAX_FACTOR_DATE — Returns the latest factor effective date for a given combination of source, account, scope, location, transport type, supplier, item, and facility, enabling effective-date windowing.
  • LOCK_DATE — Evaluates whether a given date is locked for a specified source and dimensional combination, preventing retroactive rate changes.
  • CALCULATE_EMISSIONS — Drives the emission calculation for a given emission record, applying resolved factors and quantities.
  • ARE_THERE_ANY_RATES — Boolean check confirming whether any rates exist for the supplied source, scope, location, date range, and dimensional keys.
  • GET_FACTOR — Returns the numeric emission factor applicable to a specific source, scope, location, date, and dimensional key set.
  • CREATE_LEDGER_ENTRY — Persists a ledger entry capturing the factor, quantity, emission date, unit of measure class, and organization.
  • ARE_THERE_ANY_RATES_LOCATION — Variant of the rates-existence check that additionally considers a user-specified location.
  • GET_FACTOR_USER_LOCATION — Factor retrieval variant that resolves against a user-designated location.

Tables Accessed

The package interacts with the principal ETRM transactional and setup tables through APPS synonyms. GHG_SOURCES and GHG_SOURCE_COMBINATIONS_ALL/S provide source definitions and their accounting combinations. GHG_FACTORS_ALL stores the emission factors themselves. GHG_TRANSACTIONS_ALL and GHG_TRANSACTION_DETAILS_ALL hold emission transactions and their line-level detail, while GHG_TXN_DETAILS_HISTORY_ALL preserves historical detail. GHG_EMISSION_FORMULAS supplies formula definitions used during calculation. GHG_ASSETS, GHG_ORGANIZATIONS, and DUAL support asset-, organization-, and scalar-level operations.

Usage Notes

GHG_EMISSION_RATES_PKG is typically invoked from ETRM concurrent programs that calculate emissions, from ETRM setup and maintenance forms managing factors, and from custom extensions that require programmatic factor resolution. It is referenced by three other packages within the application, indicating that it functions as a shared service rather than an isolated module. Because rate resolution depends on effective dating and dimensional specificity, callers should supply complete key sets to GET_FACTOR and ARE_THERE_ANY_RATES to avoid ambiguous matches. Rate changes should be coordinated with LOCK_DATE to preserve auditability of previously calculated emissions.