Results for “program_application_id”

50+ results




Overview
Explore in AI Chat

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

Overview

OKC_XPRT_RULE_HDRS_ALL_V is a reporting and integration view owned by the APPS schema within the OKC – Contracts Core product of Oracle E-Business Suite. It presents the header-level definition of export (transfer) rules used by the Contracts Core module, which govern how contract data is validated, transformed, and made available for export to external systems and downstream processes. The view is a consolidation layer: it unifies the active rule header records held in the primary rules table with a companion table that stores the currently effective rule set, so that consumers of the view see a single, de-duplicated picture of every rule header that is in force.

Because the view filters and merges records rather than exposing a single physical table, it is suited to read-only access by reports, concurrent programs, interfaces, and integration queries. Application logic that must act only on currently active rules can therefore query one object instead of reconciling two tables. The user-facing attribute most commonly referenced when working with this view is PUBLISHED_FLAG, which indicates whether a given rule header has been released for operational use.

Underlying Base Objects

The view text is defined as a UNION ALL over two referenced base objects, both of which are exposed to APPS as synonyms:

Each branch projects the identical 22-column list and preserves the column order, which is a prerequisite for a valid UNION ALL. The design implies that OKC_XPRT_RULE_HDRS_ALL holds the complete historical or staged population of rule headers, while OKC_XPRT_RULE_HDRS_ALL_ACTIVE tracks the rules currently in effect. By filtering the former to ACTIVE status and combining it with the latter, the view presents all active rule headers irrespective of which physical table currently carries them. Duplicate RULE_ID values should be expected where a rule exists in both sources; consumers requiring a single row per rule must apply their own DISTINCT or aggregation logic.

Key Columns

The view exposes the full rule header attribute set across 22 columns. The most significant include:

Common Use Cases and Queries

The view is typically queried to inventory active export rules, to confirm publication status before enabling integration flows, and to drive contract export validation logic. A typical listing of published, active rules for an operating unit is shown below:

  • SELECT rule_id, rule_name, status_code, published_flag, org_id, activation_date FROM okc_xprt_rule_hdrs_all_v WHERE published_flag = 'Y' AND org_id = :p_org_id ORDER BY rule_name;
  • SELECT r.rule_id, r.rule_name, r.rule_type, r.line_level_flag FROM okc_xprt_rule_hdrs_all_v r WHERE r.status_code = 'ACTIVE' AND r.published_flag = 'Y' AND NVL(r.activation_date, SYSDATE) <= SYSDATE;
  • SELECT DISTINCT rule_id, rule_name, org_wide_flag FROM okc_xprt_rule_hdrs_all_v WHERE rule_type = :p_rule_type;

Because the UNION ALL may return the same RULE_ID from both base objects, queries that require exactly one row per rule should include DISTINCT or an explicit filter on the originating source. Performance is generally adequate for reporting workloads, though large rule populations benefit from predicates on STATUS_CODE, PUBLISHED_FLAG, and ORG_ID.