Search Results build_preview_cpnt_references
Overview
IBC_UTILITIES_PVT is a private PL/SQL package in the APPS schema that provides the low-level utility layer for Oracle EBS Content Manager (iStore/iMarketing content repository, module prefix IBC). It is not intended to be called directly by external code; the public IBC API packages delegate to it. The package supplies reusable primitives for encoding and decoding binary content, resolving content item and directory names, constructing XML attribute bundles and open/close tags that describe content items and their renditions, assembling references between compound items and their children, and standardising exception handling and return-status reporting across the IBC stack.
Key Procedures and Functions
The 34 documented routines fall into several functional groups.
- Encoding and retrieval: GETENCODING and IBC_DECODE handle character-set or blob encoding conversions required when content is written to or read from the file store.
- Naming and directory resolution: GET_CITEM_NAME, GET_DIRECTORY_NAME, GETRESOURCENAME and GET_DIRECTORY_NODE_ID resolve human-readable item names, physical directory paths, resource identifiers and directory node surrogate keys.
- Metadata retrieval: GETCITEMKEYWORDS returns keyword associations, while GET_LANGUAGE_DESCRIPTION translates language codes into display descriptions.
- XML construction: BUILD_CITEM_OPEN_TAG, BUILD_CITEM_OPEN_TAGS, BUILD_CLOSE_TAG, BUILD_COMPOUND_ITEM_OPEN_TAG and BUILD_PREVIEW_CPNT_OPEN_TAG emit the XML fragments that describe content items, renditions and preview components. BUILD_ATTRIBUTE_BUNDLE and the related reference builders (BUILD_COMPOUND_ITEM_REFERENCES, BUILD_PREVIEW_CPNT_REFERENCES) assemble the complete attribute metadata set and the parent/child reference lists for compound items.
- Error handling and messaging: GET_MESSAGES, HANDLE_EXCEPTIONS and HANDLE_RET_STATUS implement the shared error-queue and status-code conventions used throughout the IBC private packages, distinguishing _PVT, _INT and _PUB layer errors.
- Attachment persistence: INSERT_ATTACHMENT writes content item attachments.
The package declares many global constants that define the XML vocabulary used by the builders, including attribute names such as id, version, ircode, ref, url, available, expiration, file, mimeType, defaultMimeType, renditionName and encrypt, together with URL parameter names (fileId, cItemId, cItemVerId, label, language). It also defines rendition and audit-action constants (COPY, CREATE, UPDATE, ARCHIVE, REMOVE, MOVE).
Tables Accessed
The package reads and writes the core Content Manager repository through APPS synonyms. IBC_CONTENT_ITEMS, IBC_CITEM_VERSIONS_B and IBC_CITEM_VERSIONS_TL hold content item headers, versions and translated attributes. IBC_ATTRIBUTE_BUNDLES and IBC_ATTRIBUTE_BUNDLES_S1 store the assembled attribute bundles produced by BUILD_ATTRIBUTE_BUNDLE. IBC_RENDITIONS and IBC_COMPOUND_RELATIONS hold rendition definitions and compound item relationships, while IBC_CITEM_KEYWORDS supports keyword retrieval. IBC_DIRECTORY_NODES_B and IBC_DIRECTORY_NODE_RELS underpin directory navigation. FND_LOBS and FND_LOBS_S store binary attachment content; FND_LOOKUP_VALUES resolves rendition lookup values such as IBC_RENDITIONS; FND_NEW_MESSAGES supplies message text; and JTF_RS_GROUPS_DENORM is consulted for resource group information.
Usage Notes
Because the package carries the _PVT suffix it is internal to the IBC product. It is invoked from the public IBC API packages, from Content Manager forms and from concurrent programs that upload, publish or migrate content items; the metadata records it as referenced by 19 other packages. Custom code should call the supported public IBC APIs rather than IBC_UTILITIES_PVT directly, since its signatures may change between 12.1.1 and 12.2.2. Recompiling the package requires the APPS schema and invalidates dependent packages.