Search Results c_fnd_lookup

Overview

The APPS.CUG_SR_ATTRIBUTE_INTF package body is a custom Oracle EBS component that supports the generation and maintenance of Service Request (SR) attribute templates used by Oracle TeleService and the Customer Support / Depot Repair modules. Its principal business function is to translate the configuration of Service Request type attributes — defined in the CUG lookup and mapping tables — into template records that the Service Request user interface can present to agents. It therefore bridges the gap between the attribute definition stored in lookup values (FND_LOOKUP_VALUES where lookup_type = 'CUG_SR_TYPE_ATTRIBUTES') and the runtime template structures held in the CS schema.

In typical 12.1.1 and 12.2.2 deployments, this package is executed as a scheduled concurrent program so that newly added or modified Service Request attributes are reflected in the template without manual form maintenance. The presence of an errbuf/retcode signature on the main procedure confirms that it is designed to run as a concurrent program, reporting success or failure through the standard EBS concurrent manager output parameters.

Key Procedures and Functions

• CREATE_ATTR_TEMPLATE — Creates the attribute template records for Service Request types. It accepts a start date parameter used to limit processing to attributes and lookup values that have changed since a given point in time. Internally it opens a cursor over CUG_SR_TYPE_ATTR_MAPS_VL, CS_INCIDENT_TYPES_VL, and FND_LOOKUP_VALUES to identify SR type attributes whose mapping record or associated lookup value has been updated on or after the supplied start date. A secondary cursor retrieves attribute list name information from FND_LOOKUP_VALUES, and a third cursor checks whether a template already exists in the CS schema before deciding whether to insert or skip. This date-driven, idempotent design allows the procedure to be rerun safely as an incremental refresh.
• UPDATE_ATTR_LISTNAME — Updates the attribute list name associated with existing Service Request attribute templates. Whereas CREATE_ATTR_TEMPLATE handles new or changed attribute definitions, this procedure reconciles the list-name assignment on templates already present in the CS tables, ensuring that template metadata remains consistent with the current lookup configuration.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. FND_LOOKUP_VALUES and FND_LOOKUP_TYPES supply the attribute definitions and their descriptions, keyed on the CUG_SR_TYPE_ATTRIBUTES lookup type and filtered by USERENV('LANG') so that only the session language's rows are processed. CS_TP_TEMPLATE_LINKS and CS_TP_TEMPLATES_VL are queried to determine whether a template already exists and to obtain its identifier. CS_TP_FREETEXTS, CS_TP_LOOKUPS, and CS_TP_TEMPLATE_QUESTIONS hold the template content that is created or amended, representing free-text fields, list-of-values attributes, and template question definitions respectively. DUAL is used for lightweight single-row operations such as existence checks or sequence lookups.

Usage Notes

The package is documented as referenced by no other packages, indicating that it is invoked directly rather than through a public API layer. It is most commonly scheduled as a concurrent program, using the p_date parameter to control the incremental window, and is re-executed after changes to Service Request attribute lookups or type-to-attribute mappings. Because it operates on CS template data, it should be run during low-activity periods to avoid contention with agents editing templates. Developers extending SR attribute behavior should treat this package as the integration point between the CUG lookup configuration and the CS template repository, and should preserve the language-filtered lookup logic when customizing. The c_fnd_lookup search term relates directly to the two FND_LOOKUP_VALUES cursors embedded in CREATE_ATTR_TEMPLATE.