Results for “get_itemsperuser”

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

Overview

AMV_MYCHANNEL_GRP_W is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API — that is, a package that does not conform to the standard PL/SQL API generation templates used by the Oracle Application Object Library, but instead exposes a custom, hand-maintained interface. Its file header (amvwmcgs.pls 120.2, dated 30-JUN-2005) indicates it belongs to the AMV module, which governs the Oracle Marketing "My Channels" and personalization components used within the eBusiness Suite's interaction and channel-management framework.

At a functional level, the package provides server-side routines for retrieving the set of marketing or interaction channels associated with a given user, and for returning per-user item counts that feed dashboard-style summaries. This supports the self-service "My Channels" region that a logged-in user sees, where channels, counts, and related attributes are populated dynamically based on user identity.

Key Procedures and Functions

• GET_MYCHANNELS — Returns the collection of channels associated with the requesting user. It accepts the caller's identity and login-check parameters (including p_api_version, p_init_msg_list, and p_check_login_user) and returns the channel data through a series of indexed out-parameter tables (the p8_a0 through p8_a11 columns), which conform to the JTF_NUMBER_TABLE and JTF_VARCHAR2_TABLE collection types. The procedure follows the standard JTF API messaging convention, returning x_return_status, x_msg_count, and x_msg_data so callers can detect and report errors.
• GET_ITEMSPERUSER — Returns item counts and related per-user figures. It exposes three scalar numeric out-parameters (p9_a0–p9_a2) together with three collection out-parameters (p10_a0–p10_a2) of JTF_NUMBER_TABLE and JTF_VARCHAR2_TABLE_300 types. As with its companion, it uses the standard JTF return-status and message-count/message-data outputs. Default values on some scalar parameters (including fnd_api.g_miss_char) allow callers to omit optional inputs.

Tables Accessed

The ETRM metadata for this package does not document any tables referenced through APPS synonyms, and no underlying base tables are listed. Because the package is an "OTHER" API, its dictionary-level table dependencies are not exposed in the same manner as a generated TCA or JTF API. Functionally, such routines read from the marketing/interaction channel definition tables and user/channel association tables — the entities that determine which channels a given user can see and which items belong to each channel. However, in the absence of documented table references, the specific DDL dependencies must be verified directly against the package body source rather than asserted here.

Usage Notes

• Designed for invocation from Oracle Application Framework or OAF-based "My Channels" pages, where a user's personalized channel list and item totals are rendered as part of the marketing or interaction dashboard region.
• May be called from concurrent programs or from custom PL/SQL that needs to enumerate a user's channels without querying the base tables directly, taking advantage of the JTF collection-based interface.
• Callers must follow the JTF API convention: pass p_api_version, optionally request message list initialization with p_init_msg_list, and inspect x_return_status before consuming the out-parameter collections.
• The package is not referenced by any other documented package in the ETRM repository, so it sits at the leaf of the dependency chain and is intended for direct external use.