Results for “amount_limit”

50+ results




Overview
Explore in AI Chat

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

Overview

PO_CONTROL_RULES_EFC is an archive table in the PO (Purchasing) schema of Oracle E-Business Suite, documented in ETRM metadata for releases 12.1.1 and 12.2.2. Its description identifies it as an "archive for euro functional currency project," indicating that the table was created as a historical holding area during the Euro functional currency conversion initiative rather than as an active transactional object in the purchasing control-rule model. The table is a structural clone of the live PO_CONTROL_RULES configuration under PO_CONTROL_GROUPS_ALL, preserving the same five documented columns so that pre-conversion control-rule rows could be retained after migration.

Because the object is described as an archive, it is not expected to participate in the day-to-day Purchasing transaction flow. It carries no validation beyond the table definition (Status: VALID) and is not exposed through standard purchasing UI. The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning it is not currently modeled as a hub, link, or satellite. As a modeling suggestion, this reflects its archive nature; if retrofitted into a Data Vault, CONTROL_RULE_ID would serve as a hub-like key for the control rule, with the amount-limit and group/book relationships best treated as satellite attributes.

Key Information Stored

The documented physical schema contains five columns in the PO schema. The most significant are:

  • CONTROL_RULE_ID — the surrogate primary key that uniquely identifies each archived control-rule record.
  • CONTROL_GROUP_ID — foreign key to PO_CONTROL_GROUPS_ALL; ties the rule to the purchasing control group it belonged to before conversion.
  • AMOUNT_LIMIT — the monetary threshold defined for the control rule, stored against the set of books in force at archive time.
  • SET_OF_BOOKS_ID — identifies the accounting set of books affected by the Euro functional currency project, preserving the currency context of the archived row.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; records the security group assignment applied to the rule.

The surrogate key is CONTROL_RULE_ID. No unique indexes are documented in the supplied metadata, so no secondary business-key candidate is asserted beyond the primary identifier.

Common Use Cases and Queries

Typical use is historical and audit-oriented: comparing control rules before and after the Euro functional currency conversion, verifying that amount limits and group assignments were migrated correctly, and reconstructing purchasing control behavior for a given set of books at a point in time. A representative reconciliation query joins the archive to the live table on the rule identifier:

  • SELECT a.control_rule_id, a.amount_limit, a.control_group_id, a.set_of_books_id FROM po.po_control_rules_efc a WHERE a.set_of_books_id = :sob_id;
  • Group-level reporting: join CONTROL_GROUP_ID to PO_CONTROL_GROUPS_ALL to summarize archived limits per group.
  • Security review: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to confirm which security grouping governed each archived rule.

These queries are read-only by convention; production DML against an archive table should be avoided.

Related Objects

  • PO_CONTROL_GROUPS_ALL — joined via CONTROL_GROUP_ID; the parent definition of purchasing control groups.
  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; governs row-level security grouping.
  • PO_CONTROL_RULES — the live control-rule table from which archived rows were sourced (keyed by CONTROL_RULE_ID).
  • PO_CONTROL_RULES_ALL — the multilingual/live counterpart typically queried alongside for before/after comparisons.
  • FND_SET_OF_BOOKS / GL_SETS_OF_BOOKS — joined via SET_OF_BOOKS_ID to resolve book context.
  • PO_CONTROL_RULE_GROUPS — relates control rules to their groups within the live model.