Results for “ghg_transaction_batches_pkg”

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

Overview

The APPS.GHG_TRANSACTION_BATCHES_PKG package body provides the core data access and business logic layer for the Greenhouse Gas (GHG) Transaction Batches entity within Oracle E-Business Suite. It is part of the ETRM (Environmental, Transportation, and Regulatory Management) product family, which supports environmental compliance and emissions accounting. The package encapsulates the DML operations and lifecycle management of emission transaction batches, allowing callers to create, maintain, copy, and reverse batches of GHG transactions without directly manipulating the underlying base tables. Its API classification is OTHER, indicating it is not a public, extension-oriented API but rather an internal package intended for use within the application stack.

The package operates in both Oracle EBS 12.1.1 and 12.2.2, and its compiled status is VALID in the APPS schema.

Key Procedures and Functions

The package exposes six documented procedures that implement the standard row-level operations and batch-level actions:

• INSERT_ROW — Creates a new GHG transaction batch record in the GHG_TRANSACTION_BATCHES_ALL table. This is the primary entry point for establishing a new batch header.
• UPDATE_ROW — Modifies attributes of an existing transaction batch. Used to adjust batch metadata after creation.
• DELETE_ROW — Removes a transaction batch record. Typically applied to batches that are no longer required and have not been committed to downstream processing.
• LOCK_ROW — Acquires a row-level lock on the target batch to guarantee serialized access during concurrent modification. This supports the standard EBS concurrency pattern in multi-user environments.
• COPY_BATCH — Duplicates an existing batch, replicating batch details and associated transaction lines to accelerate the creation of similar emission batches.
• REVERSE_BATCH — Reverses a previously posted batch, generating the offsetting accounting/emission entries required to void the original batch while preserving audit history.

Each procedure is tightly coupled with the standard error-handling infrastructure, raising messages via APP_EXCEPTION and FND_MESSAGE.

Tables Accessed

The package reads and writes the following documented tables (accessed via APPS synonyms):

• GHG_TRANSACTION_BATCHES_ALL — The primary batch header table; targeted by INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW.
• GHG_TRANSACTIONS_ALL — Stores individual emission transactions; read and written during COPY_BATCH and REVERSE_BATCH to replicate or offset transaction lines.
• GHG_TRANSACTIONS_S — The sequence/primary key source table for GHG transaction identifiers. The user search term "ghg_transactions_s" relates directly to this object.
• GHG_TRANSACTION_DETAILS_ALL — Holds detailed line-level attributes; consumed during COPY_BATCH and REVERSE_BATCH.

The package also depends on GHG_EMISSION_RATES_PKG, GHG_TRANSACTIONS_V, and standard PL/SQL STANDARD package utilities.

Usage Notes

The package is not referenced by any other database object, and it is intended for invocation by EBS Forms (typically the GHG Transaction Batches form), concurrent programs, or focused custom code. Operators normally interact with the batch screens rather than calling the package directly. Developers who invoke these procedures directly must honor the established transaction boundaries, supply the appropriate batch identifiers, and rely on APP_EXCEPTION for error propagation. Because the package is classified as OTHER rather than a public API, customizations should avoid unnecessary direct coupling; where integration is required, the procedures should be called within a single logical transaction consistent with the calling form or concurrent program. Dependencies on GHG_EMISSION_RATES_PKG ensure emission rate calculations are applied during batch operations.