Search Results pv_allowed_statuses

Overview

The PV_ALLOWED_STATUSES table is a data object within the Oracle E-Business Suite (EBS) Partner Management (PV) module. Its primary function was to define and enforce valid status transitions for partner-related entities, such as partner profiles or opportunities, by storing permissible "from" and "to" status pairs. This mechanism was crucial for maintaining data integrity and ensuring business process compliance within the partner lifecycle. However, based on the provided ETRM documentation, this table was officially marked for obsolescence starting with release 11.5.6. In the context of EBS 12.1.1 and 12.2.2, this table is considered a legacy object retained for potential data reference or upgrade compatibility but is no longer actively maintained or extended by new application functionality.

Key Information Stored

The table's structure centers on defining a single allowed status transition. The key columns, as indicated by the foreign key relationships, are FROM_STATUS_CODE and TO_STATUS_CODE. These columns store the status codes that represent the beginning and end states of a permissible transition. The primary identifier for each rule is the ALLOWED_STATUS_ID. The table's purpose is declarative; each record explicitly states that an entity can move from the status in FROM_STATUS_CODE to the status in TO_STATUS_CODE. The actual status meanings (e.g., "Active," "Inactive," "Pending") are stored in the referenced AS_STATUSES_B table.

Common Use Cases and Queries

In active implementations prior to its obsolescence, this table was queried to validate user-initiated status changes or to populate list of values for a status change field. A typical validation query would check if a proposed new status was allowed. For reporting or administrative purposes, queries would often join with AS_STATUSES_B to translate codes into meaningful names.

• Sample Validation Query: SELECT COUNT(*) FROM pv_allowed_statuses WHERE from_status_code = :current_status AND to_status_code = :proposed_status;
• Sample Query to List Allowed Transitions: SELECT from_status.meaning AS "From Status", to_status.meaning AS "To Status" FROM pv_allowed_statuses alw JOIN as_statuses_b from_status ON alw.from_status_code = from_status.status_code JOIN as_statuses_b to_status ON alw.to_status_code = to_status.status_code;

In releases 12.1.1 and 12.2.2, direct operational use is deprecated. Queries would primarily be for diagnostic or data migration analysis.

Related Objects

The table's relationships are explicitly defined by its foreign keys, both pointing to the core statuses table.

• Primary Key: PV_ALLOWED_STATUSES_PK on column ALLOWED_STATUS_ID.
• Foreign Key to AS_STATUSES_B: The column FROM_STATUS_CODE references AS_STATUSES_B.STATUS_CODE. This links the "starting" status of the transition rule.
• Foreign Key to AS_STATUSES_B: The column TO_STATUS_CODE references AS_STATUSES_B.STATUS_CODE. This links the "ending" status of the transition rule.

The dual foreign key relationship to the same table (AS_STATUSES_B) underscores the table's role as a bridge defining permissible paths between two status points. No other tables are documented as having foreign keys referencing PV_ALLOWED_STATUSES, consistent with its obsoleted status.