Search Results get_updatechannelstatus

Overview

AMV_UTILITY_PVT2 is a private utility package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the Oracle Marketing (AMS/AMV) channel management infrastructure, providing low-level validation and status-retrieval services that support the higher-level channel and category APIs in the AMV family. The package is classified under the ETRM "OTHER" API classification, indicating it is intended for internal consumption rather than as a published, customer-facing API.

The body declares a package-level constant, G_VALID_LEVEL_LOGIN, initialized to FND_API.G_VALID_LEVEL_FULL. This constant governs the validation strictness applied to any callers that reference it, and its presence reflects the package's role as a controlled gateway for validating channel- and user-related identifiers before downstream processing proceeds. The header comment identifies the original author (SLKRISHN) and a creation date of 30-AUG-1999, with the shipped version dated 02-FEB-2000, confirming the object as legacy code carried forward through successive EBS releases.

Key Procedures and Functions

The ETRM metadata documents seven program units within this package body. The first three are boolean-returning validation functions:

• IS_CATEGORYIDVALID — Determines whether a supplied category identifier corresponds to a legitimate record. It is a private function used internally to guard category-processing logic.
• IS_USERIDVALID — Determines whether a supplied user (resource) identifier is valid.
• IS_MYCHANNELIDVALID — Determines whether a supplied channel identifier owned by the current user is valid.

The remaining four functions retrieve status information:

• GET_DELETECHANNELSTATUS — Returns the status associated with a channel-deletion operation.
• GET_UPDATECHANNELSTATUS — Returns the status associated with a channel-update operation.
• GET_DELETECATEGORYSTATUS — Returns the status associated with a category-deletion operation.
• GET_UPDATECATEGORYSTATUS — Returns the status associated with a category-update operation.

The documented source excerpt confirms that IS_CATEGORYIDVALID is declared as Private within the body. In keeping with PL/SQL package conventions, the remaining routines are likewise expected to be private helpers exposed only to sibling programs within the AMV channel-management code path. No parameter signatures are published in the metadata; consumers should not assume calling conventions beyond those documented for the parent AMV APIs.

Tables Accessed

The package reads from and writes to the following tables through APPS synonyms:

• AMV_C_CATEGORIES_B — The base table for channel categories. The validation functions query this table to confirm that a category identifier resolves to an existing record. The source excerpt shows exactly this pattern in IS_CATEGORYIDVALID, which counts rows in AMV_C_CATEGORIES_B filtered on CHANNEL_CATEGORY_ID.
• AMV_U_ACCESS — Stores user access definitions within the channel hierarchy. It supports the user-validity and status functions that must respect access privileges.
• AMV_U_MY_CHANNELS — Holds the set of channels associated with a given user. It backs IS_MYCHANNELIDVALID, ensuring the caller references only channels the user owns or can see.
• JTF_RS_RESOURCE_EXTNS — The resource extensions table from the JTF (CRM Foundation) schema. It supplies the resource-level data needed to resolve user identifiers to valid sales or service resources.

Usage Notes

AMV_UTILITY_PVT2 is an internal utility layer. It is not referenced by any other documented package in the ETRM metadata, which indicates it is invoked directly from Oracle Marketing forms, concurrent programs, or other AMV packages that require pre-flight validation before committing channel or category changes. Typical invocation occurs when a user maintains marketing channels or categories, where the parent logic first calls the IS_*VALID functions to reject invalid identifiers and then calls the GET_*STATUS functions to interpret the outcome of delete or update operations.

Because the package is classified as private and its program units are private, customizations should not call AMV_UTILITY_PVT2 directly. Developers extending channel management should instead rely on the documented public AMV APIs and treat this body as implementation detail. Any direct dependency risks breakage across patching, given the object's age and its lack of a published interface.