Search Results create_cp_image

Overview

AMS_CPAGEUTILITY_PVT is a private PL/SQL package in the APPS schema that supports the Oracle Marketing (AMS) "Content Page" and campaign content authoring infrastructure. In Oracle EBS 12.1.1 and 12.2.2 it provides the internal utility API layer used to build and manipulate rich content items, questions sections, table-of-contents sections, submit sections, display templates, and associated images that make up campaign content pages and landing pages. The package is classified as PVT, indicating it is an internal implementation package rather than a public, supported API; it is consumed by the AMS content page UI and by sibling AMS packages rather than exposed for direct customer invocation.

Functionally, it encapsulates the reuse logic for creating content items (CITEMs) that are delivered, approved, or updated as part of a content page lifecycle. It centralizes the handling of BLOB rich content, image management through FND_LOBS and IBC stylesheets/associations, and the generation of dynamic SQL for select lists driven by list source definitions. This separation allows the public-facing AMS content page components to remain thin while the private utility package performs the underlying DML and content assembly.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions, grouped by purpose:

• Content item lifecycle: CREATE_CITEM_FOR_DELV, APPROVE_CITEM_FOR_DELV, and UPDATE_CITEM_FOR_DELV create, approve, and update content items destined for delivery within a content page.
• Rich content and sections: MANAGE_RICH_CONTENT, MANAGE_TOC_SECTION, UPDATE_QUESTIONS_SECTION, CREATE_BASIC_QUESTIONS_ITEM, CREATE_SUBMIT_SECTION, and UPDATE_SUBMIT_SECTION build and maintain the individual building blocks of a content page.
• Data retrieval: GET_RICH_CONTENT_DATA, GET_CONTENT_ITEM_DATA, and GET_CONTENT_ITEM_ATTRS return rich content payloads, content item records, and item attribute values for rendering or further processing.
• Image handling: CREATE_CP_IMAGE and UPDATE_CP_IMAGE manage content page images, including their LOB storage.
• Templates and generic update: CREATE_DISPLAY_TEMPLATE creates a display template, and UPDATE_CONTENT_ITEM performs a generic content item update.
• SQL and LOB utilities: GENERATE_SELECT_SQL builds dynamic select statements from list source metadata, and ERASE_BLOB clears BLOB content.

All procedures are internal helpers; parameter signatures are not part of the supported public interface and should not be relied upon by custom code.

Tables Accessed

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

• AMS_CPAG_QUESTIONS_B — question definitions for the questions section of a content page.
• AMS_LIST_SRC_FIELDS, AMS_LIST_SRC_TYPES, AMS_LIST_SRC_TYPE_USAGES, and AMS_LIST_SRC_TYPE_USAGES_S — list source metadata used by GENERATE_SELECT_SQL to build dynamic selection SQL.
• IBC_CITEM_VERSIONS_B and IBC_CITEM_VERSIONS_TL — base and translated content item version records.
• IBC_ASSOCIATIONS — relationships between content items and other objects.
• IBC_STYLESHEETS — stylesheet definitions applied to content pages.
• FND_LOBS — storage of rich content and image BLOB data.
• DUAL and PLITBLM — utility access for scalar and bulk operations.
• DBMS_LOB — Oracle-supplied LOB manipulation calls used for BLOB read/write and erase operations.

Usage Notes

AMS_CPAGEUTILITY_PVT is invoked indirectly when users author or manage content pages in the Oracle Marketing user interface, and by related AMS/IBC rendering components that need to assemble question, table-of-contents, submit, or rich content sections. It is not intended for direct invocation from customer extensions, and the ETRM metadata records no other packages that reference it, confirming its position as a leaf-level implementation utility. Custom code should use the supported public AMS content APIs instead. Because the package relies on FND_API, IBC_UTILITIES_PUB, and JTF collection types (JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_300, JTF_VARCHAR2_TABLE_4000), its behavior is consistent across both 12.1.1 and 12.2.2 where these dependencies are present and valid.