Results for “create_phantom”

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

Overview

The APPS.GME_PHANTOM_PVT package body implements the Phantom Batch API for Oracle Process Manufacturing (OPM) within Oracle E-Business Suite. Its role is to create and resolve phantom batches, which are transient parent batches generated automatically to satisfy the demand of a material detail line in a production batch. A phantom batch supplies intermediate or co-product material required by the main batch without the user manually defining a separate production order. The package is classified as a private (PVT) API in the ETRM registry for 12.2.2 (and is present in 12.1.1), owned by APPS.

As documented in the source header (GMEVPHBB.pls, version 120.7.12020000.2, dated 2012/10/15), the file was authored by Thomas Daniel of OPM Development, with maintenance changes recorded by G. Muratore for Bug 8490219 (June 2009) and Bug 14681911 (October 2012). The header describes the file as containing the Phantom Batch APIs for GME, with each procedure sharing a common set of parameters to which API-specific parameters are appended. A package-level constant g_pkg_name and a debug flag sourced from the profile option AFLOG_LEVEL support diagnostics.

Key Procedures and Functions

• CREATE_PHANTOM — Creates the phantom batch for a given material detail line. Per the documented parameter description, it accepts a material detail row to identify the detail line (p_material_detail), returns the resulting out row (x_material_detail), takes a validity rule id for creating the phantom batch (p_validity_rule_id), and a flag to ignore shortages during batch auto allocation (p_ignore_shortages). It returns an outcome status (x_return_status) with values indicating Success (S), Error (E), Warning (W), or Unexpected error (U). Two documented bug fixes affect this procedure: Bug 8490219 removed the need to timestamp the batch header record when updating the parentline_id (since the record was just created), and Bug 14681911 mandated refreshing variable data before the next update so the timestamp remains accurate.
• IS_PHANTOM — A predicate that determines whether a specified batch or line is a phantom batch, allowing callers to branch their logic accordingly.
• FETCH_STEP_PHANTOMS — Retrieves phantom batches associated with batch steps, enabling step-level resolution of phantom demand.
• FETCH_LINE_PHANTOMS — Retrieves phantom batches associated with batch lines, supporting line-level identification of generated phantoms.

Tables Accessed

• GME_BATCH_HEADER — The parent batch header; phantom batches are inserted and updated here, including parentline_id linkage.
• GME_MATERIAL_DETAILS — The material detail rows that drive phantom creation; the procedure reads the source detail line and returns the phantom-related out row.
• GME_BATCH_STEPS — Batch step definitions, used when fetching step-level phantoms.
• GME_BATCH_STEP_ITEMS — Step item requirements, consulted for step phantom resolution.
• PLITBLM — OPM's standard PL/SQL index-by table type, used for bulk parameter passing within the API.

All access is via APPS synonyms, so no direct schema qualification outside the APPS layer is required.

Usage Notes

The package is typically invoked indirectly: OPM batch creation and material detail maintenance forms, the batch auto-allocation process, and concurrent programs call the private phantom API rather than end users invoking it directly. It is referenced by six other packages in the ETRM registry, indicating it is a shared internal service. Custom code should not call this private package directly; the public API wrapper should be used instead. The AFLOG_LEVEL profile option governs debug output. Because phantom creation is tied to shortage handling (p_ignore_shortages), behavior at batch release and allocation time is sensitive to inventory availability. Note that the search term supplied by the user ("Rab Phantom Jacket Men's") is unrelated to this object; it appears to be a retail product query that does not correspond to any documented ETRM entity.