Results for “edr_psig_security”

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

Overview

EDR_PSIG_SECURITY is the E-Record security rule table within the Oracle E-Business Suite EDR (E-Records) product family. It defines the security rules that govern which users or responsibilities may access specific electronic records stored in the EBS repository. In practice, this table acts as the security anchor for a broad range of financial instruments and documents across the EBS Trading and Treasury modules, since many security-bearing entities within the XTR (Trading/Treasury) schema reference it through a SECURITY_ID foreign key.

According to the ETRM documentation metadata, this object is not implemented in this database, meaning it is documented as part of the product data model but may not be physically present or populated in every deployment. Its primary key, EDR_PSIG_SECURITY_P, is defined on the single column SECURITY_ID. The heuristic Data Vault classification mined from the foreign key structure is standalone, suggesting from a modeling perspective that it functions as a hub-like reference entity with no defined parent dependencies within the mined relationship set — although note that several downstream tables point into it, and it may be best modeled as a hub where SECURITY_ID is the business key.

Key Information Stored

The documented metadata exposes a narrow but strategically important column set. The principal columns are:

• SECURITY_ID — The single-column primary key (EDR_PSIG_SECURITY_P) and the join column referenced by every dependent table. This is both the surrogate identifier and the business-key candidate for the security rule record.

Beyond the primary key, the ETRM excerpt does not enumerate additional columns. Based on the table's stated purpose as an "E-Record security rule table," the remaining attributes would typically capture the rule scope, the associated user or responsibility, the access privilege granted or denied, and any effective-date or enablement flags that determine when the rule applies. Because the table is documented as not implemented, administrators should verify the actual column set in their specific environment before building queries against non-key attributes.

Common Use Cases and Queries

The most frequent requirement involving EDR_PSIG_SECURITY is resolving the security rule associated with a given instrument, deal, or document. A representative lookup joins a dependent table back to the security rule table on SECURITY_ID:

SELECT d.deal_id, d.security_id, s.security_id
FROM   xtr_deals d, edr_psig_security s
WHERE  d.security_id = s.security_id;

Reporting scenarios include auditing which treasury instruments carry an explicit security rule, validating that every active deal resolves to a defined security record, and inventorying the security rules attached to stock issues, bond issues, and deals for SOX or access-control reviews. Because the table is a shared reference for the XTR_A (audit) shadow tables as well, reconciliation queries between XTR_DEALS and XTR_A_DEALS via SECURITY_ID are common during financial-instrument data audits.

Related Objects

EDR_PSIG_SECURITY is referenced through the SECURITY_ID column by a significant set of dependent tables, confirming its role as a shared security reference:

• XTR_R_DEALS — SECURITY_ID → EDR_PSIG_SECURITY
• XTR_DEALS — SECURITY_ID → EDR_PSIG_SECURITY (primary trading deal repository)
• XTR_STOCK_ISSUES — SECURITY_ID → EDR_PSIG_SECURITY
• XTR_BOND_ISSUES — SECURITY_ID → EDR_PSIG_SECURITY
• XTR_A_BOND_ISSUES — SECURITY_ID → EDR_PSIG_SECURITY
• XTR_A_DEALS — SECURITY_ID → EDR_PSIG_SECURITY (audit shadow of XTR_DEALS)
• XTR_DEALS_INTERFACE — SECURITY_ID → EDR_PSIG_SECURITY (inbound interface staging)
• FND_DOCUMENTS — SECURITY_ID → EDR_PSIG_SECURITY (Oracle Foundation document attachments)

These relationships confirm that EDR_PSIG_SECURITY sits at the center of instrument-level access control, mediating how deals, stock issues, bond issues, and attached documents inherit their security rules across the EBS Trading community. Any query or extension that filters records by security rule should join through SECURITY_ID to reach the rule definition in this table.