Search Results ibc_attribute_bundles_s1

Overview

IBC_UTILITIES_PVT is a private PL/SQL package body in the APPS schema that provides shared utility services for the Oracle E-Business Suite Content Manager / iSetup content repository, part of the ETRM (Electronic Technical Reference Manual) technology stack. In Oracle EBS 12.1.1 and 12.2.2, this package acts as the internal workhorse supporting its public counterpart, IBC_UTILITIES_PUB. Because it is classified as a PVT package, it is not intended for direct invocation by external consumers; instead, it supplies reusable routines for encoding, name resolution, markup construction, attribute bundling, and error handling that the rest of the IBC content item and directory framework depends upon.

The package encapsulates low-level operations that would otherwise be duplicated across the IBC schema, centralizing logic for translating database identifiers into human-readable labels, generating content item tags and references, and normalizing exceptions into the standard FND_MSG_PUB message stack.

Key Procedures and Functions

The documented 34 procedures and functions fall into several functional groups:

• Encoding and decoding: GETENCODING and IBC_DECODE convert content between stored and transport-safe representations, typically using UTL_RAW and DBMS_LOB facilities.
• Name resolution: GET_CITEM_NAME, GET_DIRECTORY_NAME, GETRESOURCENAME, GET_DIRECTORY_NODE_ID, GET_LANGUAGE_DESCRIPTION, and GETCITEMKEYWORDS resolve identifiers into display names, node identifiers, language descriptions, and keyword lists sourced from the IBC and JTF tables.
• Markup and tag construction: BUILD_CITEM_OPEN_TAG, BUILD_CITEM_OPEN_TAGS, BUILD_CLOSE_TAG, BUILD_COMPOUND_ITEM_OPEN_TAG, BUILD_PREVIEW_CPNT_OPEN_TAG, BUILD_COMPOUND_ITEM_REFERENCES, and BUILD_PREVIEW_CPNT_REFERENCES assemble the structural tags and cross-references that bind content items, compound items, and preview components into rendered output.
• Attribute handling: BUILD_ATTRIBUTE_BUNDLE assembles attribute bundles from IBC_ATTRIBUTE_BUNDLES into a consumable form.
• Error and message handling: GET_MESSAGES, HANDLE_EXCEPTIONS, and HANDLE_RET_STATUS interact with FND_MSG_PUB and FND_MESSAGE to standardize error reporting and return status across IBC APIs.
• Attachment processing: INSERT_ATTACHMENT persists binary content into FND_LOBS.

Tables Accessed

Through APPS synonyms the package reads and writes core content repository tables. IBC_CONTENT_ITEMS, IBC_CITEM_VERSIONS_B, IBC_CITEM_VERSIONS_TL, and IBC_CITEM_KEYWORDS supply item identity, versioned metadata, translations, and keywords. IBC_DIRECTORY_NODES_B and IBC_DIRECTORY_NODE_RELS provide directory structure and hierarchy. IBC_ATTRIBUTE_BUNDLES and IBC_ATTRIBUTE_BUNDLES_S1 store attribute definitions. IBC_COMPOUND_RELATIONS links compound items, while IBC_RENDITIONS and IBC_RENDITIONS_PKG govern rendered formats. FND_LOBS and FND_LOBS_S persist attachments. JTF_RS_GROUPS_DENORM and related JTF resource tables support responsibility-based resource resolution. FND_LOOKUP_VALUES, FND_NEW_MESSAGES, FND_PROFILE, and FND_GLOBAL supply reference data, messaging, profile options, and session context.

Usage Notes

IBC_UTILITIES_PVT is invoked internally by IBC_UTILITIES_PUB and is referenced by 19 other packages within the IBC schema. It is not referenced by any database object outside this dependency chain. Typical invocation occurs from Oracle Forms and OAF pages in the Content Manager, from concurrent programs that build or rebuild content item structures, and from custom extensions that legitimately call the public IBC_UTILITIES_PUB wrapper. Direct calls to IBC_UTILITIES_PVT are not supported and should be avoided, as the package signature is subject to change across patch levels in both 12.1.1 and 12.2.2. Developers should route all content item, directory, attachment, and rendering utility requests through the public API layer.