Results for “edr_constants_grp”

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

Overview

EDR_CONSTANTS_GRP is a specification-only PL/SQL package in the APPS schema that defines the global constant values used throughout the Oracle E-Business Suite Electronic Records and Electronic Signatures (ERES) framework, sometimes referenced generically as the electronic records (EDR) subsystem. It is classified as a GRP (group/constants) object in the ETRM repository, meaning it exposes no executable business logic. Instead, it is a central catalogue of literal strings — status codes, payload parameter names, and workflow attribute names — that the ERES processing engine, its cookbook implementation, and dependent application modules all reference by name rather than by hard-coded value.

The package carries a version header consistent with Oracle Applications development conventions ($Header: EDRGCONS.pls 120.3.12000000.1 2007/01/18), indicating it is part of the 11i lineage that was carried forward into Release 12.1.1 and 12.2.2. The comment block explicitly warns that all code using these constants, together with the ERES cookbook, must be changed if any values are modified, confirming the package is treated as a stable interface contract rather than an implementation detail.

Key Procedures and Functions

The documented metadata identifies no procedures or functions in this package. This is consistent with a GRP-classified specification whose sole content is constant declarations. Because the object publishes no callable API, no parameter lists exist to describe, and any reference to it consists of reading a declared constant. The constants fall into three documented groups:

• Status codes — returned to calling code by the ERES framework to indicate processing outcome: g_error_status ('ERROR'), g_pending_status ('PENDING'), g_no_action_status ('NOACTION'), g_complete_status ('COMPLETE'), and g_indetermined_status ('INDETERMINED').
• Mandatory payload parameter names — required to be present in the payload when an ERES event is raised, including g_deferred_param ('DEFERRED'), g_postop_param ('POST_OPERATION_API'), g_user_label_param ('PSIG_USER_KEY_LABEL'), g_user_value_param ('PSIG_USER_KEY_VALUE'), g_audit_param ('PSIG_TRANSACTION_AUDIT_ID'), g_source_param ('#WF_SOURCE_APPLICATION_TYPE'), and g_requester_param ('#WF_SIGN_REQUESTER').
• Implicitly added and inter-event parameters — attributes injected by the ERES code itself, such as g_wf_pageflow_itemtype_attr, g_wf_pageflow_itemkey_attr, g_erecord_id_attr, and g_parent_event_name, the last of which is required when an event participates in a parent/child relationship.

Tables Accessed

ETRM lists no tables referenced through APPS synonyms for this package, which is expected: a constants specification performs no SQL and holds no cursor. All values are compile-time literals resolved in the PL/SQL engine's package state, so the package neither queries nor writes any application table such as FND_* or WF_* objects. Downstream consumers, notably packages that read ERES transaction audit identifiers or write electronic signature records, perform the actual DML against their own tables; EDR_CONSTANTS_GRP simply supplies the parameter keys those packages use to locate values in the event payload.

Usage Notes

EDR_CONSTANTS_GRP is invoked indirectly. The ETRM repository records that it is referenced by eleven other packages, reflecting the ERES framework modules that compare status results, construct event payloads, and populate workflow attributes. Typical invocation paths include ERES-enabled Oracle Forms, where electronic signature and record retention behaviour is triggered during transaction entry, and concurrent or workflow-driven processing where an ERES event is raised programmatically. Because the values are constants and not functions, calls appear as simple qualified references such as EDR_CONSTANTS_GRP.g_complete_status or EDR_CONSTANTS_GRP.g_audit_param within comparison and assignment statements.

Custom code extending the ERES framework, particularly Oracle E-Records or Oracle Quality signature implementations built on the ERES cookbook, should reference these constants rather than duplicating literal strings. This ensures that payload parameter names remain consistent with the framework and that status comparisons continue to match after patching. The absence of any search match for specialized utility or address-related terminology in the underlying source confirms that this package has no geographical, address-validation, or utility-industry responsibility; it is strictly an internal constants container for the electronic records and signatures subsystem. Because it declares no procedures, it cannot be executed and, being a specification-only object, requires no package body.