Search Results ibc_stylesheets_pkg




Overview
Explore in AI Chat

Overview

APPS.IBC_STYLESHEETS_PKG is a PL/SQL table handler package responsible for managing the IBC_STYLESHEETS table in Oracle E-Business Suite. The IBC_STYLESHEETS table stores stylesheet associations that bind content types to content items, including a flag indicating whether a given stylesheet is the default for its associated content item. This table underpins the delivery and rendering of styled content in the iSetup and content management areas of EBS, where web content, iHelp files, or other structured content must be presented with an associated XSL or CSS stylesheet.

As a table handler, the package encapsulates the standard EBS Data Manipulation Language (DML) and locking logic for the table, offering callers a consistent, controlled API rather than allowing direct inserts, updates, or deletes. The package header comment identifies it as the "Table Handler for Ibc_Stylesheets table." It also supplies seed data loading and translation capabilities required for the R12 Localization Content Tooling (LCT) standards. The modification history notes that the package was created on 01/06/2002 by Sri Rangarajan; that the G_MISS defaulting on UPDATE_ROW was removed in November 2002; that initialization was removed for the GSCC mandate in June 2005; and that LOAD_ROW and TRANSLATE_ROW were modified and LOAD_SEED_ROW created for R12 LCT standards under bug 4411674 in July 2005.

Key Procedures and Functions

  • INSERT_ROW — Inserts a new row into IBC_STYLESHEETS. It returns the rowid of the newly created record via an OUT parameter and accepts the content type code, content item identifier, object version number, default stylesheet flag, and the standard audit columns (creation date, created by, last update date, last updated by, and last update login).
  • LOCK_ROW — Acquires a row-level lock on an existing IBC_STYLESHEETS record, keyed by content type code, content item identifier, and object version number. It is used to enforce optimistic concurrency control before an update or delete.
  • UPDATE_ROW — Updates the default stylesheet flag, audit columns, and object version number for an existing row identified by content item identifier and content type code.
  • DELETE_ROW — Deletes a row from IBC_STYLESHEETS, identified by content type code and content item identifier.
  • LOAD_ROW — Loads (inserts or updates) a row according to an upload mode, typically used to migrate or refresh data. It accepts the upload mode, content item identifier, content type code, default stylesheet flag, owner, and last update date as a string.
  • LOAD_SEED_ROW — A seed-data variant of LOAD_ROW created for R12 LCT standards. It loads seed/translatable data, accepting the upload mode, content item identifier, and content type code together with the remaining row attributes, and is designed for localized seed data installation and upgrade.

Tables Accessed

The package operates exclusively on the IBC_STYLESHEETS table, referenced through its APPS synonym. All six procedures read from or write to this table: INSERT_ROW, LOAD_ROW, and LOAD_SEED_ROW insert or merge records; UPDATE_ROW modifies existing records; DELETE_ROW removes records; and LOCK_ROW selects the row with a locking clause to serialize concurrent access. The table stores the mapping between content types and content items together with the default stylesheet designation and standard WHO audit columns.

Usage Notes

Because the package is classified as a table handler API, it is typically invoked by EBS forms or underlying entities rather than by end users directly. The presence of LOAD_ROW and LOAD_SEED_ROW indicates use by concurrent programs and AD utilities that install, upgrade, or localize seed data — particularly the LCT seed data loaders introduced in R12. In Oracle EBS 12.1.1 and 12.2.2, LOAD_SEED_ROW is the procedure most relevant to seed-data loading operations, and callers searching for load_seed_row should note its dependence on the upload mode parameter to determine whether the row is inserted or updated. The package is referenced by no other documented packages, so custom code integrating with IBC_STYLESHEETS should call this API directly rather than issuing DML against the table. The removal of G_MISS defaulting on UPDATE_ROW and the removal of initialization for the GSCC mandate are behavioral details that customizations should respect when invocating the update path.