Results for “get_density_value”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMD_SPREAD_FETCH_PKG is a Process Manufacturing (OPM) PL/SQL package owned by the APPS schema and declared with AUTHID CURRENT_USER. It belongs to the Oracle E-Business Suite Enterprise Technical Reference Model (ETRM) and is classified as an "OTHER" API rather than a formal public interface. Its business purpose is to retrieve, assemble, and persist the detailed line and value data that underlies the OPM "spreadsheet" and technical data entry experience — the load and save engine behind formula, batch, and recipe spreadsheets.

The user search term "sprinkload application" is a likely misspelling of "spreadsheet load," which maps directly to this package's role: the procedures whose names begin with LOAD_ and SAVE_ populate and commit spreadsheet-style detail rows. In practice the package bridges the front-end folding spreadsheet (FND_FOLDERS / FND_FOLDER_COLUMNS) with the underlying formula management tables (FM_FORM_MST, FM_MATL_DTL) and the technical data staging tables used during entry.

Key Procedures and Functions

The package exposes twenty documented procedures and functions. They fall into a consistent pattern of master-level load, line-level load, value-level load, and persistence:

• LOAD_DETAILS — top-level loader that accepts entity, spread, batch, formula, and specification identifiers along with an organization and inventory-update indicator; it drives the detail fetch for a spreadsheet.
• LOAD_SPREAD_DETAILS, LOAD_BATCH_DETAILS, LOAD_FORMULA_DETAILS — context-specific loaders that populate detail rows for a spread, a batch, or a formula respectively.
• LOAD_TECH_PARAMS — loads technical parameter data for an entity, spread, or batch within a named folder; its organization parameter was changed from an organization code to an organization ID during NPD conversion.
• ADD_NEW_LINE — inserts a new spreadsheet line for a given item and line type, returning the generated line, parent line, and move-order line identifiers through OUT NOCOPY parameters.
• LOAD_SPREAD_VALUES, LOAD_BATCH_VALUES, LOAD_FORMULA_VALUES — populate the value columns beneath a loaded parent line.
• SAVE_SPREADSHEET — commits the assembled spreadsheet content back to the database.
• GET_DENSITY_VALUE, GET_LOT_DENSITY, UPDATE_LINE_MASS_VOL_QTY, UPDATE_MASS_VOL_QTY — density and mass/volume conversion utilities used to reconcile quantity representations on spreadsheet lines.
• LOAD_QUALITY_DATA — retrieves quality-related data associated with the entity being spread.
• LOAD_LCF_DETAILS, LOAD_LCF_VALUES, LOAD_DERIVED_COST — load lowest-cost-formula details and values and derived cost information.
• UPDATE_FORMULA_DETAILS, UPDATE_FORMULA_VALUES — apply the persisted changes to formula detail and value records.

Tables Accessed

Access is performed through APPS synonyms. Formula master and material detail data are read from FM_FORM_MST and FM_MATL_DTL. Recipe definition and validity are drawn from GMD_RECIPES and GMD_RECIPE_VALIDITY_RULES. Technical data is staged and stored in GMD_TECHNICAL_DATA_GTMP and GMD_TECHNICAL_DATA_HDR, with parameters held in GMD_TECHNICAL_PARAMETER_GTMP. Lowest-cost-formula detail uses GMD_LCF_DETAILS_GTMP, and material detail staging uses GMD_MATERIAL_DETAILS_GTMP. Surrogate keys are generated from GEM5_FORMULALINE_ID_S, GEM5_SPRD_ID_S, and GEM5_SPRD_LINE_ID_S. The folding-spreadsheet framework is accessed via FND_FOLDERS and FND_FOLDER_COLUMNS, and FND_DUAL is used for singleton selects. The "_GTMP" suffix identifies global temporary staging tables, confirming the package's load-then-save cycle.

Usage Notes

GMD_SPREAD_FETCH_PKG is invoked indirectly rather than called directly by end users. It is referenced by one other package, indicating layered internal use within Process Manufacturing. Typical invocation occurs from OPM formula, recipe, and batch maintenance forms when a user opens or saves a spreadsheet-style detail window, and from internal code that populates the technical data folders. Because the package is classified OTHER and is not a documented public API, customizations should not call it directly; the supported extension points are the underlying base tables. The 120.6.12020000.2 header version applies to both 12.1.1 and 12.2.2, as the file is shared across those releases. All procedures operate in the context of the APPS schema, and the AUTHID CURRENT_USER declaration means privilege resolution follows the invoking schema, a consideration when troubleshooting permission errors from custom callers.