Search Results save_delete_lgl_ctnt

Overview

IBE_LOGICALCONTENT_GRP_W is a wrapper package in the Oracle E-Business Suite iStore (IBE) module, owned by the APPS schema and classified as an "OTHER" API under the ETRM repository. Its narrow purpose is to expose a thin, table-structured interface over the logical content grouping model used by iStore merchandising and content publishing. Logical content grouping allows administrators to organize store content — such as sections, folders, and published media — into hierarchical or associative structures that drive catalog navigation and storefront rendering.

The package carries the AUTHID CURRENT_USER directive, meaning it executes with the privileges of the invoking session rather than the definer. This is characteristic of wrapper interfaces generated to be called from the middle tier or from PL/SQL clients operating under an APPS login. The header comment dates the source to 2002, indicating the package has remained stable and largely untouched across the 11i through 12.1.1 and 12.2.2 release lines. Its API classification as "OTHER" reflects that it is not part of a formally published public API set, though the internal naming and the Rosetta-style bulk copy convention suggest it was generated by Oracle's interface generation tooling.

Key Procedures and Functions

The package exposes three documented procedures:

• ROSETTA_TABLE_COPY_IN_P3 — A bulk marshalling routine that converts the flat, parallel PL/SQL table structures passed by the caller into the strongly typed ibe_logicalcontent_grp.obj_lgl_ctnt_tbl_type record collection used internally by the logical content group layer. This is the inbound half of the Rosetta conversion pattern.
• ROSETTA_TABLE_COPY_OUT_P3 — The inverse operation, converting the typed logical content table back into parallel JTF_VARCHAR2_TABLE_100 and JTF_NUMBER_TABLE collections for return to the caller.
• SAVE_DELETE_LGL_CTNT — The principal business procedure. As its name indicates, it performs the save and delete operations on logical content group records. It follows the standard EBS API convention with a version parameter, an initialization flag, a commit flag, and the standard x_return_status, x_msg_count, and x_msg_data out parameters. The remaining parameters carry the object type code and the nested table payload that describes the rows to be inserted, updated, or removed.

Tables Accessed

Per the documented metadata, the only table referenced through APPS synonyms is PLITBLM. This is a generic EBS multi-purpose table commonly used as a persistent store for PL/SQL table payloads passed between layers. In this context, it functions as the staging and persistence medium through which the logical content group rows identified by SAVE_DELETE_LGL_CTNT are recorded before or during processing. The package does not directly reference the base logical content tables in the documented metadata, which reinforces its role as a wrapper rather than the owner of the underlying business logic.

Usage Notes

IBE_LOGICALCONTENT_GRP_W is invoked programmatically rather than directly by end users. Typical callers include iStore administrative forms and concurrent programs that manage store content hierarchy, as well as custom extensions that need to bulk-maintain logical content groupings. Because the metadata records zero packages referencing it, dependencies are consumed by form-level or external code rather than by other PL/SQL packages.

The search term "save_delete_lgl_ctnt" corresponds exactly to the package's main procedure, confirming that the object surfaced in response to a request for that entry point. Developers integrating with this package should invoke SAVE_DELETE_LGL_CTNT using the standard EBS API error-handling pattern: check x_return_status, iterate x_msg_count, and retrieve messages via x_msg_data or the FND message stack. Because the package is flagged AUTHID CURRENT_USER and classified as OTHER, it should be treated as a semi-private interface — functional but not guaranteed for external support, and subject to the caveat that the Rosetta copy procedures are low-level helpers intended for internal use rather than direct customer invocation.