Results for “amv_mychannel_grp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.AMV_MYCHANNEL_GRP package is a member of the Oracle E-Business Suite CRM "Channels" foundation, delivered under the Applications Technology / Interaction Center product family. It is classified in ETRM as an API package of type GRP (a "group" or public API package), meaning it is intended to be called from external program units rather than being restricted to internal use. Its documented purpose is to retrieve the set of channels assigned to a specific user, so that applications can present each user with a personalized view of the channels they are authorized to work with. The package was created on 29-JAN-2000 and its header carries the 120.1 version stamp dated 22-JUN-2005, which is the form in which it is shipped in both EBS 12.1.1 and 12.2.2. In 12.2.2 the file continues to reside under the $AMV_TOP admin directory and is compiled into the APPS schema. The user search term "vivo 5 canal" appears to be an informal or localized reference (Portuguese/Spanish for "live channel") to this channel-assignment lookup functionality; the object itself is language-independent and its behavior does not change with the NLS configuration.

Key Procedures and Functions

• GET_MYCHANNELS — The primary public procedure. According to the package header comments it is documented as a Private-type API whose function is to "get all the channels for a given user (p_user_id)". It accepts a user identifier and returns a collection of channel records. The signature includes the standard FND_API error-handling triplet (x_return_status, x_msg_count, x_msg_data) alongside p_api_version, p_init_msg_list, p_validation_level and p_check_login_user. The channel rows are returned through the OUT parameter x_mychannel_array, typed as AMV_MYCHANNEL_PVT.AMV_MY_CHANNEL_VARRAY_TYPE, a PL/SQL varray defined in the companion private package. Because the array is returned by reference via NOCOPY, callers should consume it immediately after the call.
• GET_ITEMSPERUSER — The second documented procedure. ETRM records it as part of the same package but does not include its comment block in the excerpt. By naming convention and its position alongside GET_MYCHANNELS, it retrieves the items (or channel-item assignments) associated with a given user, complementing the channel list obtained from GET_MYCHANNELS.

Only these two program units are documented for the package; no other procedures or functions are exposed in the ETRM metadata.

Tables Accessed

The ETRM metadata for this package lists no tables referenced through APPS synonyms. The package header itself contains no SQL in the excerpted lines, and the table access is therefore delegated to the underlying AMV_MYCHANNEL_PVT package or to the AMV base tables that store channel and user-channel assignment data. From a functional standpoint, GET_MYCHANNELS must resolve the intersection of the user identified by p_user_id with the channels defined for the operating unit, and GET_ITEMSPERUSER must resolve the corresponding item-level assignments. Because no synonyms are documented, integrators should not assume a stable public table interface and should exercise the package only through its documented API entry points.

Usage Notes

The package is a GRP-class API and is referenced by two other packages in the EBS codebase, indicating it is consumed internally by higher-level channel or interaction-center logic as well as being available for customer extensions. Typical invocation patterns include custom concurrent programs that extract per-user channel lists, personalization logic in CRM self-service or Interaction Center forms, and custom PL/SQL that needs a channel array for a specific FND user. Callers should honor the standard API conventions: pass a valid p_api_version, initialize the message list with p_init_msg_list => FND_API.G_TRUE when the caller's own API context is not already initialized, and inspect x_return_status before using the returned array. Because the package dates from the earliest releases of the 11i/12 channel model, it remains backward compatible across 12.1.1 and 12.2.2 without known signature changes.