Search Results get_trade_area_attributes

Overview

APPS.RRS_SITE_INFO is a PL/SQL package declared with AUTHID DEFINER that provides a read-oriented API for retrieving Site Hub information within Oracle E-Business Suite. The package accepts a Site Identification Number as its primary input parameter and returns the full complement of relative information for that Site, with the specific data set determined by the procedure that is called. Its header notation identifies it as a component of the RRS (Retail Site) schema, bearing the source control header RRSGSDTS.pls.

The package is functionally organized around six categories of Site information: basic attributes and details such as Address and Purpose; Site associations including Trade Areas, Clusters, and Hierarchy; Site attributes, which represent the User Defined Attributes (UDAs) for various entities such as Site, Location, and Trade Area; Site contacts such as Phone, Email, URL, and other contact details; attachments linked to the Site; and asset details for assets attached to the Site. In ETRM terms the package is classified as OTHER rather than as a standard public API, and it is not referenced by any other packaged object, indicating it is intended to be consumed directly by client-side logic rather than nested within other server-side code.

Key Procedures and Functions

The documented API exposes eleven procedures and functions. The central entry point for complete retrieval is GET_COMPLETE_SITE_DETAILS, which accepts a Site Number and returns the aggregate Site detail. GET_SITE_DETAILS returns the core Site details, while CALL provides a generic invocation wrapper. Category-specific routines round out the surface:

• GET_SITE_COMPLETE_ATTRIBUTES and GET_SITE_ATTRIBUTES — retrieve UDA-style attribute information, with the complete variant returning the full attribute set for a Site.
• GET_LOCATION_ATTRIBUTES — returns the attribute values defined for a Location, which the user search targeted; this aligns Location attributes with the UDA model described in the package header.
• GET_TRADE_AREA_ATTRIBUTES — returns attribute values for Trade Area entities.
• GET_SITE_ASSOCIATIONS — returns the associations of a Site, including Trade Areas, Clusters, and Hierarchy.
• GET_SITE_CONTACTS — returns contact details such as Phone, Email, and URL.
• GET_SITE_ATTACHMENTS — returns attachments and linked documents associated with the Site.
• GET_SITE_ASSETS — returns details of assets attached to the Site.

Each routine returns a PL/SQL collection populated with the relevant information. The documented collection types include RRS_SITE_HEADER_TAB (TABLE OF RRS_SITE_HEADER_REC) and RRS_SITE_ADDRESS_TAB (TABLE OF RRS_SITE_ADDRESS_REC), and the design pattern implies parallel typed collections for each category returned.

Tables Accessed

The package reads from a set of APPS synonyms. Site and location attribute data is sourced through EGO_FND_DSC_FLX_CTX_EXT and EGO_OBJ_AG_ASSOCS_B, the extensibility framework tables that store descriptive flexfield context extensions and object attribute group associations. Asset information is drawn from CSI_ITEM_INSTANCES and CSI_INSTANCE_STATUSES, the Enterprise Asset Management instance tables, with BOM_CALENDARS supplying calendar context. Attachment and document handling relies on FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS, FND_DOCUMENTS_TL, FND_DOCUMENT_CATEGORIES_TL, FND_DOCUMENT_DATATYPES, and FND_DOCUMENT_ENTITIES. Organizational and hierarchical structures are read from FND_DM_NODES, while lookups and messages are resolved through FND_LOOKUP_VALUES, FND_NEW_MESSAGES, and FND_OBJECTS.

Usage Notes

RRS_SITE_INFO is typically invoked from custom PL/SQL code, Oracle Forms, or concurrent programs that require Site Hub data to be surfaced or propagated to downstream processes. Callers pass a Site Identification Number and select the procedure matching the required information category, or call GET_COMPLETE_SITE_DETAILS to obtain the full aggregate in a single invocation. Because the package is AUTHID DEFINER and returns typed collections, consumers must declare matching collection variables and handle the out parameters defined by each routine. The absence of inbound dependencies confirms the package is a terminal API; changes to it do not cascade to other packaged objects, though its dependency on EGO and CSI base tables means its results reflect the current state of Site Hub and asset registry data at execution time.