Search Results new_components_present




Overview
Explore in AI Chat

Overview

AMW_COMPONENTS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Advanced Product Catalog / assessment component framework and is classified under the ETRM API taxonomy as an OTHER package. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the package owner, which is typical of utility and validation packages that are invoked from a variety of application contexts.

The package provides the programmatic plumbing for determining whether a given assessment object carries a particular component, and for processing the set of components associated with that object. In EBS terms, "components" are the configurable sub-elements attached to an assessment or catalog object; the package answers the question "does this object contain this component?" and then drives the validation and persistence logic when those components are processed. It is a server-side building block rather than a user-facing API.

Key Procedures and Functions

The package exposes three documented callable units, two functions and one procedure.

  • COMPONENTS_PRESENT — A function that determines whether a specified component is present for a given object. It accepts an object identifier, an object type, and a component code, and returns a VARCHAR2 result. It is the original presence-check routine.
  • NEW_COMPONENTS_PRESENT — A function with the same conceptual purpose as COMPONENTS_PRESENT but intended as the revised implementation. It likewise takes an object ID, object type, and component code and returns a VARCHAR2. The coexistence of both functions reflects an in-place upgrade of the presence-check logic while preserving backward compatibility for existing callers.
  • PROCESS_COMPONENTS — The principal procedure of the package. Its signature follows the standard EBS API conventions: it accepts an initialization message list flag, a commit flag, and a validate-only flag, all defaulting to FND_API.G_FALSE. It also takes a select flag, an object ID, an object type, a component code, an optional other component value, and the standard OUT parameters for return status, message count, and message data (x_return_status, x_msg_count, x_msg_data). The header comments record that the earlier assessment_id parameter was obsoleted in November 2003 and replaced by the combination of object_id and object_type, which is why those parameters are present in the current signature.

Tables Accessed

The package operates against two documented application tables, referenced through APPS synonyms, plus the DUAL dummy table.

  • AMW_ASSESSMENT_COMPONENTS — The base table holding component records attached to assessment objects. This is the table the presence checks query and that PROCESS_COMPONENTS reads and writes.
  • AMW_ASSESSMENT_COMPONENTS_S — The corresponding intersection/child table within the assessment components schema, used to hold related component rows such as the other-component value passed into PROCESS_COMPONENTS.
  • DUAL — Used for scalar evaluation, consistent with the function-based presence checks that return a single VARCHAR2 value.

Usage Notes

AMW_COMPONENTS_PKG is not registered as a public API in the documented metadata and is not referenced by any other package in the ETRM repository, indicating that it is called directly rather than through a documented dependency chain. Typical invocations are as follows.

  • Form-level calls: Oracle Forms blocks on the assessment/component maintenance screens call the presence-check functions to enable or disable component controls and to validate user selections before saving.
  • Validation before persistence: PROCESS_COMPONENTS is invoked with p_validate_only set to FND_API.G_TRUE to check component data without committing, and subsequently with p_commit set to FND_API.G_TRUE when the caller is ready to persist.
  • Custom code and concurrent processing: Because the package is AUTHID CURRENT_USER and not wrapped in a documented public API, integrators use it from custom PL/SQL to interrogate and update assessment components. Callers must initialize the message stack with FND_MSG_PUB.INITIALIZE and inspect x_return_status, x_msg_count, and x_msg_data to detect failures.
  • Version compatibility: The package is present in both 12.1.1 and 12.2.2 with the same signature; the obsoleted assessment_id parameter must not be used, and object_id/object_type should be supplied instead.