Search Results cug_sr_attribute_intf




Overview
Explore in AI Chat

Overview

The APPS.CUG_SR_ATTRIBUTE_INTF package is an Oracle E-Business Suite PL/SQL interface package that supports the Oracle TeleService / Customer Support attribute template framework. It is classified in ETRM as OTHER (the API classification attached to the documented version, 12.2.2), indicating that it is not a formally published public API with a guaranteed interface contract, but rather an internal utility package used to populate and maintain the seeded attribute template and lookup data that drive service request (SR) attribute collection. The package declares AUTHID CURRENT_USER, so its SQL executes with the privileges of the invoking schema rather than the definer; the source header identifies the file as CUGATTPS.pls version 115.3 (dated 2002/12/04), which reflects its long-standing role within the Customer Support (CUG) product family. The package exposes both a data-creation routine and a rename routine, implying that its primary business purpose is administrative: establishing the seeded setup rows that define which attributes are presented on service request templates, and subsequently correcting or refreshing the display names associated with those attributes.

Key Procedures and Functions

  • CREATE_ATTR_TEMPLATE — The first documented procedure. It is the template-creation entry point, responsible for generating or seeding the attribute template records used by the service request attribute framework. It returns standard concurrent-program style output parameters (an error buffer and a return code), and accepts a date input that scopes the operation, typically used to control which template or attribute generation is created. As this procedure is invoked with the standard errbuf/retcode signature, it is designed to be run as a concurrent program.
  • UPDATE_ATTR_LISTNAME — The second documented procedure and the object of the user's search. It returns the same errbuf/retcode concurrent output parameters and takes a lookup type input, which identifies the lookup category whose attribute list name values are to be updated. This procedure is used to synchronize or rename attribute list name entries so that the attribute presented to the user matches the current lookup definition.

In addition to these procedures, the package body declares local constants used in the standard Oracle EBS API error-handling pattern (l_api_version, l_init_msg_list_true/false, l_init_commit_true/false), along with message-handling variables (x_msg_count, x_msg_data, x_return_status). This confirms that the package follows the conventional FND_API message stack model even though its public entry points use the concurrent-program convention.

Tables Accessed

The documented tables referenced via APPS synonyms are CS_TP_FREETEXTS, CS_TP_LOOKUPS, CS_TP_TEMPLATE_LINKS, CS_TP_TEMPLATE_QUESTIONS, FND_LOOKUP_TYPES, FND_LOOKUP_VALUES, and DUAL. The CS_TP_* family forms the Customer Support template definition schema: CS_TP_TEMPLATE_LINKS and CS_TP_TEMPLATE_QUESTIONS define the structure and prompts of a template, CS_TP_LOOKUPS associates lookup values with template attributes, and CS_TP_FREETEXTS stores the free-text attribute storage. The FND_LOOKUP_TYPES and FND_LOOKUP_VALUES tables are the standard Oracle Application Object Library lookup tables; the package reads them to identify and rename attribute list names, which is why UPDATE_ATTR_LISTNAME takes a lookup type as its driving parameter. DUAL is used for singleton queries such as version or existence checks. Because the package is not referenced by any other package, it is a leaf-level utility rather than a shared dependency.

Usage Notes

Both documented procedures carry the (errbuf OUT, retcode OUT) signature characteristic of Oracle EBS concurrent programs, so the package is most commonly invoked through a concurrent program registration in the Customer Support responsibility, either manually by an administrator during initial setup or scheduled for periodic maintenance. CREATE_ATTR_TEMPLATE is expected during template provisioning for a service request attribute framework. UPDATE_ATTR_LISTNAME is expected during maintenance windows when lookup values have been redefined and the corresponding attribute list names must be brought back into synchronization.

Because this package is classified as OTHER and has no declared dependents, it should be treated as an internal utility. Custom code should avoid calling it directly and should prefer supported APIs. Any direct invocation should be reserved for controlled setup or data repair scenarios in 12.1.1 and 12.2.2 environments, with the understanding that the signature may change without the compatibility guarantees that apply to public APIs. Always run such changes in a test instance first and confirm that FND_LOOKUP_VALUES and the CS_TP_* template tables reflect the intended state afterward.