Search Results load1_control




Overview
Explore in AI Chat

Overview

AMW_CONTROL_PVT is a private PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema, classified in the ETRM repository as a Private (PVT) API. It encapsulates the core business logic for creating, maintaining, validating, and revising control records belonging to the Oracle Enterprise Asset Management / Advanced Maintenance (AMW) product family. Controls in this context represent configuration and automation definitions — the rules, locations, automation types, and approval state that govern how maintenance operations are executed and tracked.

The package is declared with AUTHID CURRENT_USER and begins with a generated header ($Header: amwvctls.pls 120.1.12000000.2, dated 2007), indicating a long-stable interface carried forward through the 12.1.1 and 12.2.2 releases. It exposes a public record type, control_rec_type, which mirrors every column of the AMW_CONTROLS base table. Because it is a PVT package, it is not intended for direct external invocation; it is called by sibling public APIs and by the AMW user interface layer. The package also defines two constants, G_TRUE and G_FALSE, mapped from FND_API, and a batching constant G_DEFAULT_NUM_REC_FETCH set to 30, which controls the default fetch size during bulk load operations.

Key Procedures and Functions

  • LOAD_CONTROL and LOAD1_CONTROL — Bulk-insertion routines that populate control records, typically driven from inbound interface or migration data. The "1" variant generally denotes a single-record or alternate loading path.
  • CREATE_CONTROL — Inserts a new control record and its associated translations and revision row.
  • UPDATE_CONTROL — Applies changes to an existing control, respecting the object_version_number for optimistic locking.
  • DELETE_CONTROL — Removes a control record and maintains referential integrity across the base, translation, and revision tables.
  • LOCK_CONTROL — Acquires a row-level lock on a control to serialize concurrent modifications.
  • VALIDATE_CONTROL — Performs entity-level validation of a control before it is committed.
  • CHECK_CONTROL_ITEMS — Verifies dependent or child items associated with a control, guarding against orphaned references.
  • VALIDATE_CONTROL_REC — Validates an in-memory control_rec_type record structure prior to persistence, enforcing required fields and domain rules.

Tables Accessed

  • AMW_CONTROLS_B — The base table holding the primary control definition, including control_type, category, automation_type, approval_status, and the DFF attribute columns.
  • AMW_CONTROLS_TL — The translation table supplying language-specific control names and descriptions.
  • AMW_CONTROLS_S — A sequence/primary-key support table used to generate unique control identifiers.
  • AMW_CONTROL_REV_S — Stores revision history, supporting the rev_num, control_rev_id, and latest_revision_flag attributes.
  • PER_JOBS — Referenced to resolve job_id and requestor context for controls linked to HR job definitions.
  • DUAL — Used for scalar assignments and sequence evaluations.

Usage Notes

AMW_CONTROL_PVT is invoked indirectly. The ETRM metadata records that it is referenced by three other packages, indicating it functions as a shared internal service consumed by higher-level public APIs and the AMW maintenance forms. Typical invocation paths include the Control setup form, concurrent programs that load control definitions from external systems, and migration scripts that bulk-import control data. Custom development should call the corresponding public AMW API rather than this private package, since the interface may change between releases. Because AMW_CONTROL_PVT uses AUTHID CURRENT_USER, callers must possess the required privileges on the underlying AMW_CONTROLS tables. During 12.1.1 to 12.2.2 upgrades, the package is recompiled against the Online Patching editioning model, but its signatures — including control_rec_type — remain compatible with the documented 120.1 revision.