Search Results po_autosource_rules_n1

Overview

PO.PO_AUTOSOURCE_RULES is a table in the Oracle E-Business Suite Procurement (PO) schema. It was originally designed to store sourcing rules that automatically determined the recommended source — a supplier, a blanket purchase agreement, or an internal requisition source — for a given inventory item during the requisitioning and purchasing lifecycle. In Oracle EBS 12.1.1 and 12.2.2 this object is legacy: the ETRM metadata explicitly states that the table is no longer used, and it resides in the APPS_TS_ARCHIVE tablespace, confirming its inactive, archival status. It is not populated by the current sourcing engine, which instead relies on sourcing rules maintained through Oracle Sourcing, Approved Supplier Lists, and sourcing rule windows that do not depend on this table.

From a Data Vault modeling perspective, the metadata classifies PO_AUTOSOURCE_RULES as hub-leaning. This is a heuristic suggestion: AUTOSOURCE_RULE_ID behaves as a durable business key (hub), while the descriptive and effective-dating columns (name, item, start and end dates, WHO columns, and the descriptive flexfield attributes) would typically be modeled as a satellite on that hub. No link class is indicated, since the table holds a single-entity rule record rather than an association.

Key Information Stored

The table contains 31 documented columns. The most significant are:

• AUTOSOURCE_RULE_ID — the numeric surrogate primary key, enforced by the unique index PO_AUTOSOURCE_RULES_U1 and by the PO_AUTOSOURCE_RULES_PK constraint. It is the column most relevant to the user's search term.
• AUTOSOURCE_RULE_NAME — a user-assigned VARCHAR2(50) label identifying the rule.
• ITEM_ID — the inventory item to which the rule applies; indexed through PO_AUTOSOURCE_RULES_N1 (nonunique).
• START_DATE and END_DATE — the effective and expiration dates bounding the rule's validity; both participate in PO_AUTOSOURCE_RULES_N1.
• ORG_ID — the operating unit, enabling multi-org security filtering.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments.

No alternate unique business key is documented beyond AUTOSOURCE_RULE_ID; the uniqueness of PO_AUTOSOURCE_RULES_U1 makes the surrogate identifier the sole documented candidate key.

Common Use Cases and Queries

Because the table is unused in current releases, its principal real-world applications are historical data retrieval, archive reconciliation, and migration verification. A typical query resolves the item behind a rule:

• Listing all rules for an item: SELECT autosource_rule_id, autosource_rule_name, start_date, end_date FROM po.po_autosource_rules WHERE item_id = :p_item_id ORDER BY start_date;
• Filtering by operating unit and effective window: ... WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));
• Audit trailing: selecting LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE to trace legacy rule maintenance history.
• Confirming archive row counts before a data purge or during an upgrade from 12.1.1 to 12.2.2.

Related Objects

Two child tables carry a foreign key on AUTOSOURCE_RULE_ID and should be joined whenever legacy rule context is required:

• PO.PO_AUTOSOURCE_DOCUMENTS_ALL — joins on PO_AUTOSOURCE_DOCUMENTS_ALL.AUTOSOURCE_RULE_ID = PO_AUTOSOURCE_RULES.AUTOSOURCE_RULE_ID, recording the documents associated with a rule.
• PO.PO_AUTOSOURCE_VENDORS — joins on PO_AUTOSOURCE_VENDORS.AUTOSOURCE_RULE_ID = PO_AUTOSOURCE_RULES.AUTOSOURCE_RULE_ID, capturing the supplier sources attached to a rule.
• PO_AUTOSOURCE_RULES_U1 — the unique index supporting identifier lookups.
• PO_AUTOSOURCE_RULES_N1 — the nonunique index on ITEM_ID, START_DATE, and END_DATE.
• FND_USER — referenced indirectly through CREATED_BY and LAST_UPDATED_BY for user identification.

Treat PO_AUTOSOURCE_RULES as a read-only archival object; no supported APIs or active sourcing logic depend on it in 12.1.1 or 12.2.2.