Search Results po_autosource_rules_all

Overview

PO_AUTOSOURCE_RULES_ALL is an Oracle E-Business Suite view owned by the APPS schema within the Purchasing (PO) product family. Its documented description reads simply "10SC ONLY," a designation indicating the object is scoped to a specific configuration or localization context rather than to mainstream, out-of-the-box functionality. The view surfaces sourcing rule definitions that govern how items are automatically sourced onto requisitions and purchase orders, exposing a single logical row per rule for reporting and integration purposes.

From a reporting standpoint, the view presents a convenient, security-consistent read layer over autosource rule data. The _ALL suffix in Oracle EBS naming conventions typically signals that the object exposes data across multiple operating units, subject to the organization identifier carried on each row. That characteristic makes it suitable for cross-organization inquiries, extract programs, and integration interfaces that must reconcile sourcing behavior without directly touching the underlying transactional table.

Underlying Base Objects

The view is defined over a single referenced base object: the synonym PO_AUTOSOURCE_RULES. The documentation identifies this object as a synonym rather than a physical table, meaning the view resolves to the underlying Purchasing autosource rules storage through the synonym layer. The view's SQL is a straightforward projection — it selects a defined column list directly from PO_AUTOSOURCE_RULES with no joins, unions, or aggregations.

Because the view performs no filtering or transformation, every column is passed through unchanged, and the row cardinality of the view matches that of the base object. This design means the view functions as a column-level interface rather than a data-reduction or data-enrichment mechanism. It does not expose columns that are absent from the base object, nor does it suppress any rows based on organization, date, or status.

Key Columns

The view exposes a compact set of business and administrative columns. The most significant identifiers are AUTOSOURCE_RULE_ID, the primary key that uniquely identifies each rule and is the value most frequently used in joins and lookups; AUTOSOURCE_RULE_NAME, the human-readable label; and ITEM_ID, which ties the rule to a specific inventory item. Effective-dating is handled by START_DATE and END_DATE, allowing consumers to determine whether a rule is currently active.

Organization context is captured by ORG_ID, which is central to any _ALL view since it determines the operating unit to which each rule belongs. Standard EBS audit columns are present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Concurrent program lineage is tracked through REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, enabling traceability of the process that last touched a record. A full descriptive flexfield is available through ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical uses include auditing active sourcing rules, resolving the rule name associated with a known AUTOSOURCE_RULE_ID, and extracting rule definitions for integration or reconciliation. A representative query retrieving active rules for a given organization follows:

• SELECT autosource_rule_id, autosource_rule_name, item_id, start_date, end_date FROM po_autosource_rules_all WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));
• SELECT autosource_rule_id, autosource_rule_name, item_id FROM po_autosource_rules_all WHERE autosource_rule_id = :p_rule_id;
• SELECT autosource_rule_id, last_update_date, last_updated_by FROM po_autosource_rules_all WHERE item_id = :p_item_id ORDER BY start_date DESC;

Because the view is a pass-through over its synonym, the same constraints and indexing behavior as the base object apply. Queries should therefore filter on AUTOSOURCE_RULE_ID, ITEM_ID, or ORG_ID to avoid full scans, and consumers should confirm whether the "10SC ONLY" scope affects their deployment before relying on the view in production interfaces.