Results for “user_value”

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

Overview

PSP_AUTO_PARAMS is a transaction and configuration table in the PSP (Labor Distribution) product of Oracle E-Business Suite, present in release 12.1.1 and 12.2.2. It stores one record for each parameter associated with each natural account or expenditure type record used by the auto-population module of Labor Distribution. In practical terms, this table defines the rule parameters that drive how labor distribution entries are automatically generated, making it a central configuration artifact for organizations that automate the redistribution of labor costs across accounts, projects, and expenditure types.

The table resides in the PSP schema and is classified as VALID in the ETRM repository. Its documented primary key is a composite surrogate key, ACCT_PARAM_PK, defined over ACCT_ID and PARAM_LINE_NUM. A unique index, PSP_AUTO_PARAMS_U1, also spans the same column pair, confirming ACCT_ID and PARAM_LINE_NUM as the business-key candidate that guarantees one parameter line per account record. Under a heuristic Data Vault classification mined from the foreign-key structure, PSP_AUTO_PARAMS is modeled as a link, connecting account definitions in PSP_AUTO_ACCTS to lookup values in PSP_AUTO_LOOKUPS.

Key Information Stored

The documented physical schema contains 10 columns. The most significant are:

• ACCT_ID — Foreign key to PSP_AUTO_ACCTS, identifying the natural account or expenditure type auto-population record to which the parameter belongs. Part of both the primary key and the unique business key.
• PARAM_LINE_NUM — Sequence number distinguishing each parameter line within a given ACCT_ID. Together with ACCT_ID, it forms the composite primary key ACCT_PARAM_PK and the unique index PSP_AUTO_PARAMS_U1.
• LOOKUP_ID — Foreign key to PSP_AUTO_LOOKUPS, resolving the parameter to its defined lookup value; this drives which operand or value the auto-population logic applies.
• OPERAND — The operator or comparison token applied when evaluating the parameter.
• USER_VALUE — The user-supplied value or threshold matched against the operand during auto-population processing.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard Oracle EBS who-column auditability for change tracking.

The surrogate key is ACCT_PARAM_PK (ACCT_ID, PARAM_LINE_NUM); the same columns constitute the documented business-key candidate. No additional descriptive columns are documented beyond the 10 listed.

Common Use Cases and Queries

Typical uses include auditing auto-population rules, troubleshooting why a labor distribution entry was generated (or not), and reporting on configured parameters by account. A representative query joins the parameter table to its parent account record:

• SELECT p.ACCT_ID, p.PARAM_LINE_NUM, p.LOOKUP_ID, p.OPERAND, p.USER_VALUE FROM PSP.PSP_AUTO_PARAMS p WHERE p.ACCT_ID = :acct_id ORDER BY p.PARAM_LINE_NUM;
• Resolving parameter semantics: SELECT p.ACCT_ID, l.LOOKUP_CODE, p.OPERAND, p.USER_VALUE FROM PSP.PSP_AUTO_PARAMS p, PSP.PSP_AUTO_LOOKUPS l WHERE p.LOOKUP_ID = l.LOOKUP_ID;
• Change-audit reporting using LAST_UPDATE_DATE and LAST_UPDATED_BY for SOX or internal control reviews.

These patterns support reconciliation of auto-population output against the configured parameters, and help validate that every account has at least one active parameter line.

Related Objects

The following objects are the most significant dependencies, based on documented foreign-key and key relationships:

• PSP_AUTO_ACCTS — Parent of ACCT_ID; holds the account or expenditure type record that owns each parameter set.
• PSP_AUTO_LOOKUPS — Parent of LOOKUP_ID; defines valid lookup values referenced by parameters.
• PSP_AUTO_PARAMS_PK1 and PSP_AUTO_PARAMS_U1 — The primary-key constraint and unique index enforcing uniqueness on ACCT_ID and PARAM_LINE_NUM.
• PSP_AUTO_PARAMS (base table) — Referenced by Labor Distribution auto-population processing logic and concurrent programs that read parameter definitions.

Because the metadata lists only two outbound foreign keys, additional dependents are primarily application logic rather than schema-level constraints. Queries should therefore always filter on ACCT_ID to exploit the PSP_AUTO_PARAMS_U1 index and avoid unnecessary full scans on large parameter sets.