Search Results ams_status_pvt




Overview
Explore in AI Chat

Overview

APPS.AMS_STATUS_PVT is a private PL/SQL package within the Oracle E-Business Suite Marketing (AMS) module. It is classified as a Private API (PVT), meaning it is intended strictly for internal consumption by other Oracle EBS components rather than as a public integration surface for customer extensions. The package's stated purpose is to resolve the next valid statuses available for Marketing Activities and to validate proposed status transitions. It centralizes the business logic that governs how marketing activities, promotions, and related entities move through their lifecycle states, ensuring that status changes conform to the configured workflow rules.

The package exposes two PL/SQL collection types, next_status_rec_type and next_status_tbl_type, which together form the data structure returned when the package computes the set of permissible next statuses for a given activity. Each record carries the user status identifier, system status code, system status type, a default indicator, and the user-facing status name. The package was created in June 1999 and last modified in November 2002, as recorded in its header history.

Key Procedures and Functions

  • GET_STATUS_LOOKUP_TYPE — Given an ARC (Application Resource Catalog) qualifier for an area, such as 'PROM' for promotions, this function returns the corresponding lookup type name, for example 'AMS_PROMOTION_STATUS'. If no matching lookup type exists, the function returns null.
  • GET_LOOKUP_MEANING — Resolves the display meaning for a status by accepting a lookup type and lookup code and returning the human-readable description associated with that code.
  • IS_APPROVAL_NEEDED — Determines whether a proposed status transition requires an approval step, based on the configured approval rules for the activity's area.
  • GET_NEXT_STATUSES — Returns the collection of valid next statuses for an activity, populating the next_status_tbl_type table with records that include the default status flag and both system and user-facing status identifiers.
  • VALIDATE_STATUS_CHANGE — The procedure most relevant to the search term "validate_status_change." It verifies that a requested status transition is legal under the configured status order and approval rules, typically raising an error or returning a failure indicator when the change is not permitted.

Tables Accessed

  • AMS_APPROVAL_RULES — Stores the rules that determine whether a status change must pass through an approval workflow. IS_APPROVAL_NEEDED and VALIDATE_STATUS_CHANGE consult this table to decide if approval is mandatory.
  • AMS_STATUS_ORDER_RULES — Defines the permitted ordering and sequencing of statuses. GET_NEXT_STATUSES and VALIDATE_STATUS_CHANGE rely on this table to enumerate legal successor statuses and to reject illegal transitions.
  • PLITBLM — The Oracle Applications lookup meanings table. GET_LOOKUP_MEANING and GET_STATUS_LOOKUP_TYPE reference it to translate lookup codes into display text.

Usage Notes

As a private API, AMS_STATUS_PVT is invoked internally by the Marketing application's forms, concurrent programs, and other server-side PL/SQL units whenever a marketing activity's status is displayed, changed, or validated. The metadata indicates the package is referenced by zero other packages in the documented set, which is consistent with its role as a leaf-level utility invoked directly rather than through a wrapper API. Custom or extension code should not call this package directly, because Oracle does not guarantee its signature or behavior across releases. Instead, developers requiring status validation should use the corresponding public APIs or declarative validation mechanisms. Changes to the underlying rule tables directly affect the behavior of VALIDATE_STATUS_CHANGE, so administrators must maintain AMS_APPROVAL_RULES and AMS_STATUS_ORDER_RULES carefully to preserve correct lifecycle enforcement.