Results for “okc_report_prm_b”

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

Overview

OKC_REPORT_PRM_B is a core Oracle E-Business Suite table residing in the OKC schema, which underpins the Contracts Core module. As documented in the ETRM metadata, the table stores SQL-XML Parameters and is used specifically for Contract Printing. In practice, it holds the structured parameter definitions that drive the SQL-XML-based reporting and printing framework for contracts, allowing the application to render contract documents dynamically by binding query parameters to a SQL-XML template.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure identifies this object as standalone. This means that, based on documented FK relationships, it does not participate in a classic hub-link-satellite hierarchy and can be treated as an independent parameter reference table rather than a dependent satellite or link.

Key Information Stored

The table defines 14 documented columns. The most significant include:

• ID – The surrogate primary key, enforced by the constraint OKC_REPORT_PRM_B_PK and reinforced by the unique index OKC_REPORT_PRM_B_U0. It uniquely identifies each parameter row.
• SQL_ID – Identifies the parent SQL-XML definition to which the parameter belongs. It is a business-key candidate, appearing in unique indexes U1 and U2.
• SEQUENCE_NUM – Controls the ordering of parameters within a given SQL_ID. Combined with SQL_ID in unique index OKC_REPORT_PRM_B_U1, it establishes ordering uniqueness.
• CODE – The parameter code. Together with SQL_ID in unique index OKC_REPORT_PRM_B_U2, it forms a business-key candidate ensuring one code per SQL definition.
• TYPE – The data type of the parameter (for example, string, number, or date), governing how the value is interpreted at print time.
• REQUIRED_YN – A flag indicating whether the parameter must be supplied before the contract print process can execute.
• LOV_QUERY – The SQL query backing the List of Values presented to the user when entering a parameter value.
• OBJECT_VERSION_NUMBER – Supports optimistic locking for concurrent updates.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, providing multi-tenant / operating-unit data isolation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard who-columns capturing audit and identity information.

Common Use Cases and Queries

Typical scenarios include reviewing the parameters defined for a contract print template, validating that required parameters are configured, and joining parameter metadata to the parent SQL definition. A representative query retrieves all parameters for a given SQL definition in print order:

SELECT code, type, required_yn, sequence_num FROM okc_report_prm_b WHERE sql_id = :p_sql_id ORDER BY sequence_num;

Reporting use cases often join the parameter rows to the driving SQL-XML record via SQL_ID, and filter by SECURITY_GROUP_ID to respect data access boundaries. Because U2 enforces uniqueness on (SQL_ID, CODE), lookups by code within a SQL definition are deterministic.

Related Objects

• FND_SECURITY_GROUPS – Referenced by OKC_REPORT_PRM_B.SECURITY_GROUP_ID, enforcing security-group isolation.
• OKC_REPORT_PARMS / SQL-XML definition tables – Typically referenced by SQL_ID as the parent definition.
• OKC_REPORT_PRM_B_PK, OKC_REPORT_PRM_B_U0, OKC_REPORT_PRM_B_U1, OKC_REPORT_PRM_B_U2 – Primary key and unique indexes governing integrity.

These relationships make OKC_REPORT_PRM_B the parameterization layer for the OKC contract printing and SQL-XML reporting framework in both 12.1.1 and 12.2.2.