Search Results po_asl_statuses




Overview
Explore in AI Chat

Overview

PO_ASL_STATUSES is a Purchasing (PO) module reference table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the master list of status values applicable to Approved Supplier List (ASL) entries. An ASL record defines a supplier, supplier site, and item combination that has been approved for procurement, and each such entry is governed by a status that determines whether purchasing activity against it is permitted. PO_ASL_STATUSES provides the controlled vocabulary for those statuses, together with flags and descriptive text that drive application behavior.

The table resides in the PO schema and is owned by Oracle Purchasing. Its primary key is PO_ASL_STATUSES_PK, defined on STATUS_ID. The documented physical schema contains 31 columns, and the metadata identifies a unique index, PO_ASL_STATUSES_U1, on the composite of STATUS_ID and ZD_EDITION_NAME. This composite key is characteristic of the Oracle Online Patching / editioning infrastructure introduced in 12.2, where the ZD_EDITION_NAME column supports edition-based redefinition during online patching cycles. Based on the foreign-key relationship data, the heuristic Data Vault classification for this object is standalone — it is not modeled as a hub, link, or satellite because the mined FK structure shows no inbound or outbound dependencies. It is best treated as a reference or lookup table rather than a transactional entity.

Key Information Stored

Although the table includes 31 documented columns, the meaningful business content is concentrated in a small number of attributes:

  • STATUS_ID — the surrogate primary key. It uniquely identifies each ASL status row and is the value referenced by ASL transactional tables.
  • STATUS — the short status code or name presented to users and used in queries and validation logic.
  • STATUS_DESCRIPTION — the descriptive, user-facing text explaining the status.
  • ASL_DEFAULT_FLAG — indicates whether the status is the default applied to newly created ASL entries. This flag influences defaulting behavior during ASL maintenance.
  • INACTIVE_DATE — the date on which the status becomes (or became) inactive; a null value generally indicates an active status.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard Oracle WHO columns capturing audit and user information.
  • LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and session audit columns populated when the row is maintained by an Oracle EBS concurrent request.
  • ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard Oracle EBS extensibility (DDF) flexfield columns, available for customer-defined descriptive attributes.
  • ZD_EDITION_NAME — the editioning column that participates with STATUS_ID in the unique index PO_ASL_STATUSES_U1, supporting online patching in EBS 12.2.

In practice, STATUS_ID is the join key, STATUS and STATUS_DESCRIPTION are the display attributes, and ASL_DEFAULT_FLAG and INACTIVE_DATE are the control attributes that determine behavior. The audit and flexfield columns are present for standards compliance but are not typically queried.

Common Use Cases and Queries

The table is most often queried as a lookup to resolve status meaning for ASL records and to drive validation, reporting, and reconciliation. Typical scenarios include reviewing which statuses are active and which is the default, identifying ASL entries assigned to a particular status, and filtering inactive statuses from operational reports.

A simple lookup query that retrieves the current active statuses might be written as:

SELECT status_id, status, status_description, asl_default_flag, inactive_date
FROM po.po_asl_statuses
WHERE inactive_date IS NULL
ORDER BY status;

To join ASL transactional data to the status definition, a query pattern such as the following is used (the exact ASL table name depends on the release):

SELECT a.asl_id, a.status_id, s.status, s.status_description
FROM po.po_asl_headers a, po.po_asl_statuses s
WHERE a.status_id = s.status_id;

Reporting use cases include ASL status distribution summaries, auditing status changes over time via the WHO columns, and confirming configuration of the default status before go-live or during data migration validation.

Related Objects

The metadata describes PO_ASL_STATUSES as standalone with no mined foreign-key dependencies, so related objects are identified by functional association rather than documented FK links. The most significant are:

  • PO_ASL_HEADERS — the ASL header table that references the status through STATUS_ID.
  • PO_ASL_ATTRIBUTES — ASL attribute rows associated with ASL header records.
  • PO_ASL_DOCUMENTS — documents attached to ASL entries, which follow the parent ASL status.
  • PO_ASL_ITEMS / ASL item-level tables — item-level ASL definitions whose validity depends on the parent status.
  • PO_APPROVED_SUPPLIER_LIST view — the reporting view exposing ASL data joined to status descriptions.
  • PO_ASL_STATUSES_PK — the primary key constraint on STATUS_ID, referenced when validating status values.
  • PO_ASL_STATUSES_U1 — the unique index on STATUS_ID and ZD_EDITION_NAME supporting 12.2 editioning.

Together these objects form the ASL subsystem, with PO_ASL_STATUSES acting as the central controlled-value reference for status assignment throughout the approved supplier list.