Search Results edr_psig_sign_params_b




Overview
Explore in AI Chat

Overview

The EDR_PSIG_SIGN_PARAMS_B table is an E-Records (EDR) module object within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the signature attributes associated with electronic signature configurations, functioning as a child attribute store that captures the individual parameters that define how an electronic signature is presented, validated, and applied. In the EDR product line, this table supports the Personal Identification (PSIG) signature framework by holding the discrete parameter records that accompany a signature definition.

From a Data Vault modeling perspective, the mined FK structure classifies this object heuristically as standalone, since the only documented relationship is a single reference to CZ_SIGNATURES via SIGNATURE_ID. As a modeling suggestion, this table behaves as a satellite dependent on the signature hub, with no further downstream links documented in the source metadata.

Key Information Stored

The table contains 9 documented columns. The most significant are:

  • PARAMETER_ID — the surrogate primary key, enforced by the unique index EDR_PSIG_SIGN_PARAMS_B_P. This column uniquely identifies each signature parameter record and serves as the technical identifier rather than a business key.
  • SIGNATURE_ID — a foreign key referencing CZ_SIGNATURES. This is the primary business-key relationship candidate, linking each parameter row to its parent signature definition.
  • NAME — the parameter name or attribute label, identifying what aspect of the signature is being configured.
  • VALUE — the corresponding value assigned to the named parameter, holding the actual configuration content.

The remaining documented columns are standard Oracle EBS audit and concurrency attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These support Multi-Org audit tracking and WHO-column conventions throughout the application.

Common Use Cases and Queries

Typical scenarios involve retrieving the configured attributes for a given electronic signature, auditing changes to signature parameters, and reporting on signature setup across responsibilities. A representative query joining parameters to their parent signature is:

  • SELECT p.parameter_id, p.signature_id, p.name, p.value FROM edr.edr_psig_sign_params_b p WHERE p.signature_id = :signature_id;
  • Audit reporting using WHO columns, for example filtering by last_update_date to track recent configuration changes.
  • Inventory reporting of signature parameters grouped by name to understand which attributes are commonly configured.
  • Joining to CZ_SIGNATURES to produce a consolidated view of signature definitions and their parameters.

Related Objects

The most significant related object is the parent signature definition referenced by the documented foreign key:

  • CZ_SIGNATURES — joined on EDR_PSIG_SIGN_PARAMS_B.SIGNATURE_ID = CZ_SIGNATURES.SIGNATURE_ID. As the only documented FK relationship, it is the principal object governing this table's referential integrity.
  • EDR_PSIG_SIGN_PARAMS_B_P — the primary key unique index, essential for direct parameter lookups by PARAMETER_ID.

Additional EDR and PSIG signature-related tables may reference signature definitions through the same SIGNATURE_ID lineage, but the documented ETRM metadata identifies CZ_SIGNATURES as the primary dependent object.