Search Results validate_before_delete

Overview

GMD_CUSTOMER_TESTS_GRP is a public PL/SQL package owned by APPS in the Oracle E-Business Suite, classified as a Group (GRP) API within the Process Manufacturing (GMD) product family. It encapsulates the server-side validation logic governing the relationship between customer records and quality control tests in Oracle Quality and Process Manufacturing. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges and schema context of the invoking session rather than the definer's. This design is typical of Oracle EBS group APIs, which are intended to be called by forms, concurrent programs, and other packages that already run within the APPS schema context.

Functionally, the package provides the validation entry points used before a customer-test association is created or removed. It ensures that a given quality test may be legitimately tied to a given customer account and that the association does not violate existing data integrity or business rules before the transaction is committed.

Key Procedures and Functions

The package exposes three documented program units:

• VALIDATE_BEFORE_INSERT — A procedure invoked prior to inserting a row into the customer-tests relationship. It accepts an initialization flag for the message list, a record of type GMD_CUSTOMER_TESTS%ROWTYPE containing the proposed row, and returns a status indicator plus message data. Its purpose is to confirm that the proposed customer-test assignment is valid before the insert proceeds.
• VALIDATE_BEFORE_DELETE — A procedure invoked prior to removing a customer-test association. It accepts the initialization flag and identifiers for the test and the customer, returning a status and message data. This is the routine associated with the user's search term "validate_before_delete" and is the gatekeeper that determines whether a given test-customer link may safely be deleted.
• CHECK_EXISTS — A boolean function that takes a test identifier and a customer identifier and reports whether an association already exists between them. It is used to detect duplicate or pre-existing relationships during validation.

All three units follow the standard EBS API convention of returning x_return_status and x_message_data, allowing callers to interrogate the outcome and surface user-facing errors.

Tables Accessed

The package operates against several tables, accessed through APPS synonyms:

• GMD_CUSTOMER_TESTS — The primary table holding customer-to-test associations; it is the target of insert and delete validation.
• GMD_QC_TESTS — The quality control test definitions referenced when validating a test identifier.
• HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_SITES_ALL, and HZ_PARTIES — The Trading Community Architecture (TCA) tables used to resolve and validate the customer account and party context.
• GL_PLCY_MST — The accounting policy master, referenced for policy-level validation.

Usage Notes

GMD_CUSTOMER_TESTS_GRP is typically invoked from the Oracle Quality/Process Manufacturing forms that maintain customer test assignments, and from custom code or other PL/SQL packages that insert or delete customer-test rows programmatically. As a group API, it is not intended for direct end-user execution; it supplies validation services to calling transactions. The package is referenced by at least one other package in the EBS schema, confirming its role as a shared validation utility. Callers should supply the initialization flag, pass the relevant record or identifiers, and inspect x_return_status before proceeding with their DML. Customizations should respect the AUTHID CURRENT_USER semantics and apply the same validation routines rather than bypassing them.