Search Results check_access

Overview

The APPS.ENG_VALIDATE_CHANGE_LINE package is a validation utility within the Oracle E-Business Suite Engineering (ENG) module. It provides the server-side business rules that verify the integrity of Engineering Change Order (ECO) change line records before they are inserted, updated, or deleted in the database. Change lines represent the individual item or component modifications attached to an engineering change order, and because such records drive downstream manufacturing, inventory, and BOM behavior, Oracle enforces a layered set of checks — existence, required attributes, conditional requirements, entity integrity, and access privileges — prior to persistence.

The package is classified as an OTHER API in the ETRM 12.2.2 repository and is owned by the APPS schema, meaning it executes with invoker's rights (AUTHID CURRENT_USER). It does not expose a public procedural API to end users; instead it is a private validation layer consumed by the Engineering ECO public APIs and forms. The header comment identifies it as ENGLCHLS.pls, with the last recorded revision dated 2003, indicating the validation logic has been stable across 11i and the 12.1.1 / 12.2.2 releases.

Key Procedures and Functions

The documented metadata lists eight procedures. Each conforms to the standard Oracle error-handling contract, returning an x_return_status value and populating an x_mesg_token_tbl of message tokens via Error_Handler.Mesg_Token_Tbl_Type.

• Check_Existence — Confirms that the referenced change line exists on the database and returns the previously stored (old) change line and unexposed attribute records so callers can compare old versus new values.
• Check_Required — Verifies that all mandatory (NOT NULL) attributes on the change line record have been supplied.
• Check_Attributes — Performs datatype, domain, and cross-attribute validation on the change line and its unexposed record, comparing against the old image to identify what has changed.
• Check_Conditionally_Required — Enforces attributes that are mandatory only when other attributes satisfy specific conditions (for example, when a change type or implementation flag is set).
• Check_Entity — Validates that related entities referenced by the change line (such as the engineering change order header) are internally consistent.
• Check_Entity_Delete — Applies the delete-time referential and business rules, ensuring the change line is not still referenced or protected from removal.
• Check_Access — The routine matching the user search term "check_access". It validates that the current user has the requisite privileges to perform the requested operation on the change line.

Tables Accessed

Only three database objects are referenced through APPS synonyms. ENG_CHANGE_LINES is the primary base table read during existence and attribute checks. MTL_SYSTEM_ITEMS supplies the item master definition used to validate the item referenced by a change line (item number, revision, organization control, and status). DUAL is used for scalar checks and constants. No writes are documented; the package is strictly a read-only validator.

Usage Notes

ENG_VALIDATE_CHANGE_LINE is typically invoked indirectly. The Engineering ECO forms and the ENG_ECO_PUB public APIs call these procedures immediately before DML to guarantee that invalid change lines never reach the tables. It is referenced by one other package in the ETRM repository, confirming its role as a subordinate validation component rather than a standalone entry point. Customizations should not call this package directly; the supported extension point is the public ECO API. Because it is AUTHID CURRENT_USER, any direct call executes with the caller's privileges and is subject to the same function-security and MOAC considerations as any APPS invoker-rights code.