Search Results check_instance_data

Overview

GMP_RESOURCE_DTL_PUB is the public PL/SQL interface for the Oracle Process Manufacturing (OPM) Plant Resources API. It is owned by APPS and classified as a public API, exposing a supported entry point for creating, updating, and deleting plant resources and their associated instances within the OPM schema. The package is declared with AUTHID CURRENT_USER and carries an internal API version constant of 1, with the package name constant identifying it as GMP_RESOURCE_DTL_PUB. Its lifecycle status is active, and it is registered against the business entity GMP_PLANT_RESOURCE.

The user search term "check_instance_data" corresponds to the documented procedure CHECK_INSTANCE_DATA, which performs validation logic on resource instance data prior to insert or update operations. This validation step enforces data integrity for equipment instances such as serialized or tracked plant resources.

Key Procedures and Functions

The package exposes ten documented procedures, organized around two primary entities: plant resource detail records and resource instances.

• INSERT_RESOURCE_DTL — creates a new plant resource by inserting a row into the plant resource table, cr_rsrc_dtl.
• CHECK_DATA — validates resource detail data before insertion or update.
• INSERT_DETAIL_ROWS — inserts the associated detail-level rows that accompany a resource record.
• UPDATE_RESOURCE_DTL — modifies an existing plant resource header record.
• UPDATE_DETAIL_ROWS — updates the detail rows linked to a plant resource, optionally driven by a table of column/value pairs supplied through the update_tbl_type structure.
• DELETE_RESOURCES — removes plant resource records.
• CHECK_INSTANCE_DATA — the procedure matching the user search term; it validates resource instance data before persistence.
• INSERT_RESOURCE_INSTANCE — inserts a new resource instance using the resource_instances_rec record type, which carries fields such as RESOURCE_ID, INSTANCE_ID, VENDOR_ID, MODEL_NUMBER, SERIAL_NUMBER, tracking numbers, maintenance and calibration dates, and standard WHO columns.
• UPDATE_INSTANCES — updates existing resource instances in bulk.
• UPDATE_INSTANCE_ROW — updates a single resource instance row.

The package defines supporting types including update_table_rec_type, update_tbl_type, resource_instances_rec, and resource_instances_tbl, all indexed by BINARY_INTEGER, which allow callers to pass sets of changes efficiently.

Tables Accessed

The package operates across the core OPM resource and inventory tables accessed through APPS synonyms:

• CR_RSRC_DTL — the primary plant resource detail table written by the insert and update procedures.
• CR_RSRC_MST — the plant resource master, referenced for resource definitions.
• GMP_RESOURCE_INSTANCES and GMP_RESOURCE_INSTANCES_S — store resource instance records managed by the instance procedures.
• GMP_RESOURCE_AVAIL, GMP_RSRC_EXCP_ASNMT, and GMP_RSRC_UNAVAIL_MAN — support resource availability, exception assignment, and unavailability management.
• BOM_CALENDARS and BOM_RESOURCES_S — supply calendar and resource definition data.
• IC_ITEM_MST and MTL_UNITS_OF_MEASURE — provide item and unit-of-measure validation.
• MTL_PARAMETERS — supplies inventory organization defaults.
• PLITBLM — an OPM utility table used for error and message handling.

Usage Notes

GMP_RESOURCE_DTL_PUB is the supported programmatic path for maintaining OPM plant resources. It is typically invoked from OPM application forms, concurrent programs that create or synchronize resources, and custom extensions that require resource creation or instance tracking. The package is not referenced by any other documented package, so callers invoke it directly. Standard API conventions apply: callers pass an API version, an initialization flag for the message list, and a commit flag, then inspect the message list for errors. Because the package runs with AUTHID CURRENT_USER, privileges are resolved against the calling schema. Given the validation procedures CHECK_DATA and CHECK_INSTANCE_DATA, implementations should call these or rely on the insert and update procedures to enforce integrity before committing resource and instance records.