Search Results ledger_customer_is_pop_flag

Overview

The APPS.FEM_REFRESH_UTIL_PKG package body is a utility component within the Oracle Enterprise Business Suite (EBS) Enterprise Performance Foundation (now Enterprise Resource Planning Integrator / ETRM) schema. Its documented purpose is to support the Refresh engine when it returns the FEM (Financial Enterprise Management) database to its install state. Specifically, the package contains procedures that delete obsolete seeded data which would otherwise be reintroduced by the refresh process through the Layer Distribution Tool (LDT) files.

The package is classified as an OTHER API type in the ETRM 12.1.1 metadata, indicating it is not a public application programming interface intended for customer consumption. It is an internal maintenance utility owned by APPS. The header comment notes that the LDT files for backports are targeted — the main LDT file retains obsolete rows — making a dedicated deletion utility necessary to prevent stale seed data from being re-populated during refresh operations.

Key Procedures and Functions

Only one procedure is documented in the ETRM metadata for this package body:

• DEL_OBSOLETE_SEED_DATA — Accepts an x_status OUT parameter and executes a series of delete statements that remove obsolete seeded data from the database. The procedure was originally created to support Bug 5002331 (removing a reference to DIM_PROPERTIES in delete statements for FEM_ADMIN_DIMESTUP_TASKS) and later extended under Bug 5237422 to add deletes for attributes that were previously made optional. Within this procedure, a cursor (c_ldgattr) is declared that selects attribute_id from FEM_DIM_ATTRIBUTES_B filtered by dimension_id and by specific attribute_varchar_label values such as LEDGER_CHANNEL_IS_POP_FLAG, LEDGER_CUSTOMER_IS_POP_FLAG, LEDGER_ENTITY_IS_POP_FLAG, and LEDGER_FIN_ELEM_IS_....

No public functions are documented. The procedure is the sole entry point exposed by this package body.

Tables Accessed

The ETRM metadata lists fifteen tables referenced via APPS synonyms. These fall into several functional groups:

• Dimension attribute tables: FEM_DIM_ATTRIBUTES_B, FEM_DIM_ATTRIBUTES_TL, FEM_DIM_ATTRIBUTES_PRIV, FEM_DIM_ATTR_GRPS, FEM_DIM_ATTR_VERSIONS_B, and FEM_DIM_ATTR_VERSIONS_TL. These hold the attribute definitions, translations, privilege assignments, groupings, and version history. The cursor demonstrated in the source explicitly queries FEM_DIM_ATTRIBUTES_B to locate obsolete ledger attribute flags.
• Dimension and entity metadata: FEM_DIMENSIONS_B, FEM_ENTITY_TYPES_B, and FEM_ENTITY_TYPES_TL.
• Data type and calendar metadata: FEM_DATA_TYPES_B, FEM_DATA_TYPES_TL, FEM_DATA_TYPES_ATTR, FEM_CALENDARS_ATTR, and FEM_DSNP_LEDGERS_ATTR.
• Administrative task table: FEM_ADMIN_DIMSETUP_TASKS, which stores dimension setup tasks and is targeted by delete statements per Bug 5002331.

The tables are accessed primarily for delete operations, with the cursor performing a read against FEM_DIM_ATTRIBUTES_B to drive the attribute deletions.

Usage Notes

This package is invoked by the Refresh engine rather than directly by end users or standard concurrent programs. Its procedures are called when the refresh process returns the FEM database to its install state, ensuring that obsolete seeded rows do not persist after refresh. Because the main LDT files for backports still contain obsolete rows, the deletion logic in DEL_OBSOLETE_SEED_DATA is required to clean them out after LDT repopulation.

The metadata reports that the package is referenced by zero other packages, confirming it is a terminal utility called only from the refresh framework. It is not exposed through Oracle Forms or standard concurrent program interfaces. The x_status OUT parameter suggests the caller inspects the result to determine success or failure of the deletion sequence. Custom code should not invoke this package directly, as its behavior is tied to specific patch and backport levels and may change across EBS releases. The presence of FEM_DIM_ATTRIBUTES_B in the cursor reflects the package's role in managing optional versus required dimension attribute states across upgrades.