Search Results amw_public_pkg

Overview

AMW_PUBLIC_PKG is a small public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in the ETRM metadata as an OTHER API. Its declared purpose is to expose the outcome of the "opinion" (approval or disposition) recorded by a processing organization for a given process. The package header carries the standard Oracle EBS version banner (amwpbpks.pls 115.0, dated 2004/04/28) and is declared AUTHID CURRENT_USER, meaning that it executes with the privileges of the calling schema and relies on APPS-owned synonyms for all underlying object references.

The AMW_ prefix associates the package with Oracle's Application Management/Workflow-family opinion framework, in which an object type is defined in FND_OBJECTS, the possible opinions for that object type are defined in AMW_OPINION_TYPES_B, and the opinions actually recorded against specific object instances are stored in AMW_OBJECT_OPINION_TYPES. AMW_PUBLIC_PKG provides the narrow public read interface to that model: given a process and an organization, it reports what that organization decided and when.

Key Procedures and Functions

• GET_PROC_ORG_OPINION_STATUS — Returns the opinion or approval status recorded by a processing organization for a specified process, as a VARCHAR2 value. It is the primary interrogative function: callers use it to determine whether an organization, for example, approved, rejected, or is still pending on a process instance.
• GET_PROC_ORG_OPINION_DATE — Returns the date associated with the process-organization opinion as a VARCHAR2 value. This is the function most commonly invoked when auditing when a given organization reached its opinion on a process. The user search string "get_proc_org_opinion_date" corresponds directly to this documented function.

Both functions accept a process identifier, an organization identifier, and a mode argument. The mode parameter governs the resolution behavior of the lookup—for example, how a missing or ambiguous opinion row should be interpreted—but the metadata does not enumerate its permitted values, so callers should reference the package body for the accepted literals. Both functions return character data, with the date function returning a formatted date string rather than a native DATE, which is significant when the value is consumed by SQL or by a form field.

Tables Accessed

• AMW_OBJECT_OPINION_TYPES — The central fact source for both functions, holding the opinion recorded against a specific object (process) instance. It supplies the status attribute and the associated date returned by the two functions.
• AMW_OPINION_TYPES_B — The opinion-type definition table, supplying the base definition and description of each possible opinion so the stored identifier can be rendered meaningfully.
• FND_OBJECTS — The object metadata registry, used to validate and resolve the object identifier (process) supplied by the caller against the framework's registered object definitions.

The package is documented as referencing these tables through APPS synonyms, consistent with its AUTHID CURRENT_USER declaration.

Usage Notes

Because the package has no documented inbound references from other packages (referenced by 0), it is best characterized as a leaf utility invoked directly by client-side or server-side code rather than by inter-package dependencies. Typical invocation points include OAF or Forms pages that display approval outcome and date for a processing organization, concurrent programs that report on approval timeliness, and custom PL/SQL that queries APPS.AMW_PUBLIC_PKG.GET_PROC_ORG_OPINION_DATE(:process_id, :org_id, :mode) inside a SELECT statement.

Two practical cautions apply in 12.1.1 and 12.2.2. First, since both functions return VARCHAR2, callers requiring date arithmetic must convert the returned string explicitly and be tolerant of the session's date format. Second, the package is a read-only reporting interface; it should not be used to record or update opinions. When making direct SQL calls, invoke the package as APPS.AMW_PUBLIC_PKG and ensure the calling schema holds EXECUTE on the package and SELECT on the referenced objects.