Search Results is_create_enabled




Overview
Explore in AI Chat

Overview

AMW_FINDINGS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM documentation as an "OTHER" API. It is part of the Oracle Engineering (formerly Advanced Product Catalog / Engineering Change Management) module, and its name reflects its role in managing "findings" — discrete issue or nonconformance records raised against engineering objects during the change management lifecycle.

The package encapsulates the business rules that determine whether a new finding may be created for a given change category and organization, and how many findings remain open within a specified hierarchy of related entities. It is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer, allowing it to respect the caller's security context when invoked from forms, concurrent programs, or other PL/SQL APIs. The header comment (amwfinds.pls, version 115.3) indicates the package has been stable since 2004, consistent with a long-standing internal utility used by the engineering change infrastructure rather than a customer-facing public API.

Key Procedures and Functions

ETRM documents two callable program units within this package:

  • CALCULATE_OPEN_FINDINGS — A function that returns a numeric count of open findings. It accepts a findings category, a "self" entity name and primary key value, and up to four levels of parent entity name and primary key pairs (parent1 through parent4). This hierarchical parameter structure allows the caller to walk upward through a multi-level relationship chain — for example, a change line to a change header, or a component to an assembly — and aggregate the open findings that apply at any level. The returned number is typically used to drive validation, workflow routing, or UI indicators.
  • IS_CREATE_ENABLED — A function returning a numeric flag that indicates whether creation of a finding is permitted for a given change category, organization, and process identifier. This serves as a gating check so that callers do not attempt to insert findings when configuration or process state prohibits it.

The metadata does not document additional procedures; no parameter lists beyond those shown should be assumed.

Tables Accessed

The package accesses two base tables through APPS synonyms:

  • ENG_ENGINEERING_CHANGES — The engineering change header table. It supplies the change category and organizational context used by IS_CREATE_ENABLED, and anchors the hierarchy traversed by CALCULATE_OPEN_FINDINGS.
  • ENG_CHANGE_SUBJECTS — The table linking engineering changes to the objects (subjects) they affect. This provides the child-level records against which findings are associated, enabling the function to count open findings at the self level and roll them up through the parent chain.

Usage Notes

AMW_FINDINGS_PKG is an internal utility rather than a documented public interface. ETRM records that it is referenced by seven other packages, indicating it is called programmatically by higher-level engineering change APIs and validation routines rather than invoked directly by end users. Runs on Oracle EBS 12.1.1 and 12.2.2 follow the same behavior; the package source is unchanged between these releases as evidenced by the stable 115.3 version.

Typical invocation patterns include Oracle Forms triggers on the engineering change or findings blocks (to enable or disable the Create action via IS_CREATE_ENABLED), and internal validation logic that calls CALCULATE_OPEN_FINDINGS before permitting change status transitions or closure. Because it is AUTHID CURRENT_USER, custom code calling it must ensure the invoking schema has appropriate grants on the underlying ENG tables. Customizations should treat this package as internal and avoid direct dependency where a supported public API exists.