Results for “po_system_parameters_all”

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

Overview

PO_SYSTEM_PARAMETERS_ALL is the Purchasing options table in the Oracle E-Business Suite Purchasing (PO) module, owned by the PO schema. It stores the configuration and operational defaults that govern how purchasing documents — requisitions, RFQs, quotations, purchase orders, and releases — are created, numbered, approved, received, taxed, and closed for a given operating unit. Because it is an "_ALL" table, it is partitioned by operating unit, with one row per ORG_ID, exposing the set of control parameters that the Purchasing application reads at runtime.

Under the heuristic Data Vault classification derived from its foreign-key structure, PO_SYSTEM_PARAMETERS_ALL is best modeled as a link table: it resolves relationships between an operating unit and multiple reference entities (chart of accounts combinations, conversion rate types, line types, and order types) rather than functioning as a pure hub of a single business key. Its primary key is PO_SYSTEM_PARAMETERS_PK, defined on (LAST_UPDATE_DATE, ORG_ID), and a unique business-key candidate is documented as PO_SYSTEM_PARAMETERS_U1 on ORG_ID. The ETRM 12.2.2 physical schema documents 133 columns.

Key Information Stored

The surrogate primary key PO_SYSTEM_PARAMETERS_PK combines LAST_UPDATE_DATE and ORG_ID; the unique index PO_SYSTEM_PARAMETERS_U1 on ORG_ID establishes the operating unit as the effective business key, one options row per organization. Among the 133 documented columns, the most operationally significant include:

• ORG_ID — the operating unit that owns the parameter row; the primary business-key candidate.
• ACCRUED_CODE_COMPINATION_ID — accrual account (references GL_CODE_COMBINATIONS).
• DEFAULT_RATE_TYPE — default currency conversion rate type (references GL_DAILY_CONVERSION_TYPES).
• LINE_TYPE_ID — default purchasing line type (references PO_LINE_TYPES_B).
• ORDER_TYPE_ID — default order type (references SO_ORDER_TYPES_115_ALL).
• PRICE_CHANGE_ALLOWANCE, ENFORCE_PRICE_CHANGE_ALLOWANCE, PRICE_CHANGE_AMOUNT — thresholds governing price-change tolerances.
• INSPECTION_REQUIRED_FLAG, RECEIVING_FLAG, ACCEPTANCE_REQUIRED_FLAG — receipt and inspection controls.
• ENFORCE_BUYER_AUTHORITY_FLAG, ENFORCE_BUYER_NAME_FLAG, ENFORCE_VENDOR_HOLD_FLAG — buyer and vendor enforcement rules.
• USER_DEFINED_PO_NUM_CODE, MANUAL_PO_NUM_TYPE, and the parallel REQ/RFQ/QUOTE numbering columns — document numbering schemes.
• TAX_FROM_* and TAX_HIER_* columns — tax determination sources and hierarchy.
• INVOICE_CLOSE_CODE, RECEIVE_CLOSE_CODE, and tolerance columns — close and tolerance behavior.
• MIN_RELEASE_AMOUNT, DEFAULT_DISTRIBUTIONS, AUTO_OFFSET_METHOD — blanket release and accounting defaults.
• GLOBAL_ATTRIBUTE_CATEGORY plus GLOBAL_ATTRIBUTE1–20 — descriptive flexfield storage.

Common Use Cases and Queries

PO_SYSTEM_PARAMETERS_ALL is queried whenever purchasing behavior must be explained or audited. A typical retrieval pattern isolates one operating unit:

• SELECT * FROM po.po_system_parameters_all WHERE org_id = :org_id;
• Joining to reference tables to resolve defaults, e.g. joining LINE_TYPE_ID to PO_LINE_TYPES_B or ACCRUED_CODE_COMBINATION_ID to GL_CODE_COMBINATIONS.
• Reporting on receiving and inspection configuration (RECEIVING_FLAG, INSPECTION_REQUIRED_FLAG) across operating units.
• Auditing document numbering schemes via USER_DEFINED_PO_NUM_CODE and MANUAL_PO_NUM_TYPE.
• Reviewing tax-determination setup through the TAX_FROM_* and TAX_HIER_* flags.

Because ORG_ID is the business key, cross-operating-unit comparisons are straightforward, and the LAST_UPDATE_DATE component of the primary key supports change tracking.

Related Objects

Documented foreign keys and dependencies of PO_SYSTEM_PARAMETERS_ALL include:

• GL_CODE_COMBINATIONS — via ACCRUED_CODE_COMBINATION_ID.
• GL_DAILY_CONVERSION_TYPES — via DEFAULT_RATE_TYPE.
• PO_LINE_TYPES_B — via LINE_TYPE_ID.
• SO_ORDER_TYPES_115_ALL — via ORDER_TYPE_ID.
• PO_SYSTEM_PARAMETERS_PK — the primary key constraint defined over (LAST_UPDATE_DATE, ORG_ID).

Downstream, the Purchasing forms and concurrent programs that create requisitions, RFQs, quotations, and purchase orders read these parameters at runtime, making this table a central dependency for document defaulting, validation, and numbering throughout the PO module.