Results for “to_status_code”

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

Overview

The PV_ALLOWED_STATUSES table is a Partner Management (PV) module data object in the Oracle E-Business Suite database. It defines the permissible transitions between partner status codes within the partner lifecycle, functioning as a control table that governs which status-to-status movements are valid for a given status category and status type. The object is owned by the PV schema and remains marked VALID in the data dictionary for both 12.1.1 and 12.2.2, though the ETRM documentation explicitly notes that the table is being obsoleted as of release 11.5.6. Its continued presence reflects the requirement to support upgrade paths and legacy partner data rather than active functional use in current releases.

From a modeling perspective, the mined Data Vault classification for this object is link. This is a heuristic suggestion: the table primarily resolves relationships between status definitions held in AS_STATUSES_B, recording which from-status may transition into which to-status, and it carries an edition-qualified uniqueness constraint consistent with a link structure scoped by ZD_EDITION_NAME.

Key Information Stored

The table contains 21 documented columns spanning identifier, audit, configuration, and notification attributes. The most significant are:

• ALLOWED_STATUS_ID — the surrogate primary key, enforced by the unique index PV_ALLOWED_STATUSES_PK. It is the single-column identifier referenced by dependent objects.
• FROM_STATUS_CODE and TO_STATUS_CODE — the two foreign key columns that reference AS_STATUSES_B, together defining the directed transition permitted by each row. These form the substantive business content of the table.
• STATUS_CATEGORY and STATUS_TYPE — classification attributes that scope the transition to a partner status category and type.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, restricting visibility of the transition rule to an operating unit or security group context.
• ENABLED_FLAG and LOV_FLAG — control whether the transition is active and whether the to-status appears in a list of values presented to users.
• TIMEOUT_NOTIFY_FLAG and DURATION_VIEW_TYPE_CODE — govern elapsed-time notification behavior associated with a status.
• NOTIFY_PT_FLAG, NOTIFY_CM_FLAG, NOTIFY_LAM_FLAG, NOTIFY_SUPPORT_REP_FLAG — notification routing flags for partner team, channel manager, local area manager, and support representative recipients.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard EBS audit and optimistic locking columns.
• ZD_EDITION_NAME — the edition qualifier appearing in the unique index PV_ALLOWED_STATUSES_U1 (ALLOWED_STATUS_ID, ZD_EDITION_NAME), supporting Edition-Based Redefinition.

The surrogate key is ALLOWED_STATUS_ID; the business-key candidate documented through the unique index combines ALLOWED_STATUS_ID with ZD_EDITION_NAME.

Common Use Cases and Queries

Because the table is obsolete, its principal modern uses are upgrade validation, data migration auditing, and investigation of legacy partner status behavior. A typical query retrieves the valid outgoing transitions for a given partner status:

• Select FROM_STATUS_CODE and TO_STATUS_CODE filtered by STATUS_CATEGORY and STATUS_TYPE with ENABLED_FLAG = 'Y'.
• Join both status columns to AS_STATUSES_B to resolve human-readable status names for each endpoint of the transition.
• Filter by SECURITY_GROUP_ID to reproduce the status options available to a specific operating unit.
• Query by TO_STATUS_CODE to identify all predecessor statuses permitted to reach a target status.
• Use TIMEOUT_NOTIFY_FLAG and the NOTIFY_* flags together to reconstruct which transition rules drove historical notification behavior.

Because ZD_EDITION_NAME participates in the unique index, any query used for upgrade reconciliation should constrain or group by edition name to avoid double counting across editions.

Related Objects

The following objects are directly related through the documented constraints:

• AS_STATUSES_B — referenced twice, by TO_STATUS_CODE and FROM_STATUS_CODE; the definitive source of status code definitions.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, providing the security group context for each rule.
• PV_ALLOWED_STATUSES_PK — the primary key index on ALLOWED_STATUS_ID.
• PV_ALLOWED_STATUSES_U1 — the unique index on ALLOWED_STATUS_ID and ZD_EDITION_NAME.

Additional PV partner management tables that consume partner status configuration, along with the partner status application programming interfaces, may reference or depend upon these definitions, but AS_STATUSES_B and FND_SECURITY_GROUPS represent the confirmed dependencies derived from the documented foreign key structure.