Search Results gr_field_name_properties_pub




Overview
Explore in AI Chat

Overview

The APPS.GR_FIELD_NAME_PROPERTIES_PUB package is a public PL/SQL API within the Oracle E-Business Suite product family designated by the product code GR (the "Process Manufacturing" / "Oracle Quality" regulatory and labeling family, often associated with Oracle's labeling and ingredient/regulatory content infrastructure). Its declared purpose is to create, delete, and validate field name properties — the metadata definitions that describe the labels, values, display ordering, and characteristics of property fields within the GR properties framework.

The package header is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the definer. This is significant because callers must therefore possess the appropriate grants on the underlying GR tables and dependent FND objects to succeed. The header file signature ($Header: GRPIFNPS.pls 120.2 2010/11/19) indicates the package was last revised in November 2010, and the noship tag shows that the specification is intentionally excluded from the standard shipped file set and treated as an internal interface component. The report annotations classify the API as active, public, compatibility level S (standard), and assign it the business-entity category GR_PROPERTIES. Its display name is "GR Field Name Properties Package." The package defines a single public procedure, FIELD_NAME_PROPERTIES, and no functions.

Key Procedures and Functions

  • FIELD_NAME_PROPERTIES — The sole documented procedure. It is the interface used to perform the create, delete, and validate operations on field name properties. It follows the standard Oracle EBS API convention of accepting p_api_version, p_init_msg_list, and p_commit control parameters, and of returning x_return_status, x_msg_count, and x_msg_data for standardized error handling. The p_action parameter selects the governing operation (create, delete, or validate), while p_object and p_property_id identify the target property. Parameters such as p_property_type_indicator, p_length, p_precision, p_range_min, and p_range_max describe the field's data characteristics, and the language parameters (p_language, p_source_language, p_description) support the multilingual translation of property labels. The p_label_prop_values_tab parameter accepts a PL/SQL associative array of label property value records, whose record type (gr_label_prop_values_rec_type) exposes display_order, value, and value_description columns. This table-driven argument allows a single call to supply an entire ordered set of permitted values for a property.

Tables Accessed

The package operates against the following documented tables (referenced through APPS synonyms):

  • GR_PROPERTIES_B — the base (non-translatable) properties table, holding the core definition of each field-name property including its type indicator, length, precision, range, and identifying keys.
  • GR_PROPERTIES_TL — the translation table for property definitions, storing language-specific descriptions and label text keyed by p_language.
  • GR_PROPERTY_VALUES_TL — the translation table for the permitted property values supplied through p_label_prop_values_tab, storing the value, its description, and display order per language.
  • FND_LANGUAGES — the Oracle Foundation language repository, used to validate the installed and source language codes passed into the procedure.
  • PLITBLM — a PL/SQL interleaved/logging table used by the API framework, typically for message capture and runtime bookkeeping during API validation and processing.

Usage Notes

Because this is a PUB-classified API, it is the intended public entry point for external and internal callers that need to manipulate GR field-name property definitions. It is typically invoked from Oracle Forms–based setup or configuration screens that maintain the property catalog, from concurrent programs that bulk-load or migrate property definitions, and from custom PL/SQL integration code that seeds labeling or regulatory metadata during implementation. As an AUTHID CURRENT_USER package, custom callers must be granted the necessary privileges on the GR and FND objects and must supply a valid p_api_version consistent with the version of the API they were developed against. The ETRM metadata records no packages that reference this API, so it is an upstream utility whose consumers are external callers rather than peer GR packages.