Search Results amw_constraint_rev_s

Overview

AMW_LOAD_CONSTRAINT_DATA is an Oracle Applications (APPS) PL/SQL package body that belongs to the Oracle Enterprise Asset Management / Complex Maintenance Repair and Overhaul (CMRO) product family, where the AMW prefix designates objects used by the constraint management framework. Its business function is to load, validate, and persist constraint definitions and their associated entries from staging interface tables into the production constraint repository. In a maintenance and MRO context, constraints represent rules that restrict or govern which work types, resources, operations, or organizational combinations are permissible. This package acts as the loader/conversion routine that consumes rows loaded into the constraint interface tables and materializes the corresponding constraint definitions in the base tables.

The package is classified as OTHER rather than a public or private API, indicating it is primarily an internal implementation utility invoked by the constraint administration process rather than a supported integration interface. It is documented as VALID in the APPS schema for Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

Two documented procedures constitute the public surface of this package body:

• CREATE_CONSTRAINTS — The primary loader procedure. It reads staged constraint records from the interface tables, performs validation, and creates the corresponding constraint definitions in the base constraint tables (header and translation tables), along with their entries and revisions. Its dependency list, which includes AMW_CONSTRAINTS_B, AMW_CONSTRAINTS_TL, AMW_CONSTRAINTS_VL, AMW_CONSTRAINT_ENTRIES, AMW_CONSTRAINT_REV_S, and AMW_CONSTRAINT_WAIVERS, confirms that creation spans multiple related entities.
• UPDATE_INTERFACE_WITH_ERROR — A supporting routine that writes error information back to the interface staging table when a constraint row fails validation or creation. This enables the concurrent program or caller to report which rows could not be loaded, supporting user-driven correction and reprocessing.

No parameter lists are documented in the supplied metadata; the above describes purpose only.

Tables Accessed

The package reads from and writes to the following documented tables (via APPS synonyms):

• AMW_CONSTRAINT_INTERFACE — the staging table consumed by the loader; also updated by UPDATE_INTERFACE_WITH_ERROR.
• AMW_CONSTRAINTS_B, AMW_CONSTRAINTS_TL, AMW_CONSTRAINTS_VL — base, translation, and view-layer constraint definition tables populated during creation.
• AMW_CONSTRAINT_ENTRIES — constraint entry/detail records associated with each constraint header.
• AMW_CONSTRAINT_REV_S — the constraint revision table, referenced to maintain revision history; this object corresponds directly to the user's search term "amw_constraint_rev_s".
• AMW_CONSTRAINT_WAIVERS — waiver records linked to constraints.
• AMW_VIOLATIONS and AMW_AP_INTERFACE — violation and application interface data used during validation/loading.
• AMW_WORK_TYPES_B — work type definitions that constraints reference.
• FND_* tables (FND_CONCURRENT_PROGRAMS, FND_RESPONSIBILITY, FND_RESP_FUNCTIONS, FND_FORM_FUNCTIONS, FND_COMPILED_MENU_FUNCTIONS, FND_OBJECTS) — used for menu/function/responsibility lookups when constraints govern navigation or function access.

FND_API, FND_FILE, FND_MESSAGE, FND_GLOBAL, FND_PROFILE, and AMW_UTILITY_PVT provide the standard API, logging, message, session, and utility infrastructure.

Usage Notes

AMW_LOAD_CONSTRAINT_DATA is typically invoked from a concurrent program or an administrative process that batch-loads constraint data from the interface table into the live constraint repository. It is not referenced by any database object, and it is referenced by one other package, confirming it sits near the top of the internal call hierarchy rather than being a reusable building block. Because FND_CONCURRENT_PROGRAMS and FND_FILE appear in its dependencies, output is written to the concurrent manager log/report, and FND_MESSAGE supplies user-facing feedback. Customizations should not call this package directly; instead, populate the AMW_CONSTRAINT_INTERFACE table and submit the standard concurrent request, or use AMW_CONSTRAINTS_PKG for supported constraint operations. When diagnosing load failures, inspect the error columns written by UPDATE_INTERFACE_WITH_ERROR and verify that revision records referenced through AMW_CONSTRAINT_REV_S are consistent with the incoming interface rows.