Search Results p_file_name

Overview

APPS.IBC_RENDITIONS_PKG is an Oracle E-Business Suite PL/SQL package that manages the IBC_RENDITIONS entity, which stores rendition records associated with content items in the Oracle iMarketing/IBC content management schema. A rendition in this context represents a specific presentational form of a content item — for example, a generated file or published asset linked to a content item version. The package encapsulates the standard EBS table-handling API pattern, providing atomic insert, update, delete, and locking operations against IBC_RENDITIONS, together with seed data loading procedures used during installation and patching. The package is owned by APPS and is classified as an OTHER API, indicating it is a programmatic interface rather than a user-facing form API.

Key Procedures and Functions

• INSERT_ROW — Creates a new rendition record. It generates the primary key from the IBC_RENDITIONS_S1 sequence when the caller does not supply a RENDITION_ID, and it applies defaulting for object version number, audit columns, and the MIME type. The P_FILE_NAME parameter carried by this procedure is the attribute most commonly referenced by callers searching on file name values.
• LOCK_ROW — Obtains a row-level lock on a rendition record to support optimistic concurrency control before an update or delete.
• UPDATE_ROW — Modifies an existing rendition record. The modification history shows that G_MISS defaulting was removed from UPDATE_ROW in 2002, so callers must pass explicit values for columns they intend to change.
• DELETE_ROW — Removes a rendition record, typically by primary key after a successful lock.
• LOAD_ROW — Loads a single rendition row during installation or patching, mapping seed data into the base table.
• LOAD_SEED_ROW — Introduced in the 2005 revision (bug 4411674) to conform to R12 Lightweight Component Technology seed data standards, working alongside modified LOAD_ROW and TRANSLATE_ROW logic.

Tables Accessed

• IBC_RENDITIONS — The base table holding rendition rows, including FILE_ID, FILE_NAME, MIME_TYPE, RENDITION_ID, and CITEM_VERSION_ID. This is the primary insert, update, delete, and lock target.
• IBC_RENDITIONS_S1 — The sequence supplying RENDITION_ID primary key values when one is not provided by the caller.
• IBC_CITEM_VERSIONS_TL — The translated content item version table, referenced to maintain the linkage between a rendition and its parent content item version.
• DUAL — Used to fetch the next sequence value during key generation.

Usage Notes

The package is typically invoked from Oracle Forms, from concurrent programs that generate or publish content renditions, and from custom PL/SQL code that needs to create or maintain rendition records. It is referenced by two other packages in the EBS schema, indicating that it serves as a lower-level dependency for higher-level content management logic. Because UPDATE_ROW no longer applies G_MISS defaulting, callers should pass fully populated values for any column they intend to modify. The LOAD_ROW and LOAD_SEED_ROW procedures are reserved for seed data installation and patch application and should not be used in normal runtime processing. When tracing a rendition by file name, the P_FILE_NAME parameter of INSERT_ROW and the corresponding FILE_NAME column of IBC_RENDITIONS are the relevant entry points.