Results for “retrieve_fpo_data”

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

Overview

The APPS.GME_CONVERT_FPO_PVT package body is a private (PVT-classified) PL/SQL API within the Oracle E-Business Suite Process Manufacturing (OPM/GME) module. Its core business function is to convert a firm planned order (FPO) — a scheduling construct used in process manufacturing planning — into an actual production batch record in GME_BATCH_HEADER. The package supports the "convert firm planned order to batch" workflow, allowing planners to transform forecasted or planned production into executable batch documents. It derives batch headers, validates production parameters, calculates lead times, and generates pre-batch header records before committing the conversion to the database. The module header comment references GME_API_CONVERT_FPO, confirming this package is the private implementation backing a public conversion API surface.

Key Procedures and Functions

The package exposes seven documented procedures and functions, all named with the private API convention:

• VALIDATION — Evaluates the incoming planned batch parameters (batch size, unit of measure, number of batches, validity rule, lead time, batch offset, offset type, and planned start/complete dates) and returns a populated pregen_fpo_row along with a return status. It raises defined exceptions such as no_null_dates, no_populate_both_dates, invalid_batch_status, plan_qty_zero_err, invalid_item_item_um, no_batches, neg_validity_rule_id, leadtime_err, batch_offset_err, and offset_type_err. Per Bug 3607420, it permits planned dates in the past, applying a forward scheduling method when only a start date is supplied.
• RETRIEVE_FPO_DATA — Fetches the firm planned order source data to be converted.
• CALCULATE_LEADTIME — Computes the lead time used to schedule the resulting batch.
• GENERATE_PRE_BATCH_HEADER_RECS — This is the procedure referenced by the user's search term. It builds the pre-batch header records that are staged before the actual batch header is created, forming the bridge between the FPO and the production batch.
• CONVERT_FPO_TO_BATCH — Performs the physical conversion, writing the batch header and associated records.
• CONVERT_FPO_MAIN — The orchestrating entry point that sequences validation, data retrieval, lead-time calculation, and conversion.
• UPDATE_ORIGINAL_FPO — Updates the originating firm planned order to reflect its converted status.

Tables Accessed

The package reads and writes several core OPM and inventory tables through APPS synonyms:

• GME_BATCH_HEADER — The primary target; batch header records are generated, validated, and inserted or updated.
• GMD_RECIPE_VALIDITY_RULES — Used to validate the recipe and validity rule identifier supplied during conversion.
• GME_MATERIAL_DETAILS — Material line details associated with the converted batch.
• GME_INVENTORY_TXNS_GTMP / GME_RESOURCE_TXNS_GTMP — Global temporary tables staging inventory and resource transactions generated during conversion.
• MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_KFV — Item master validation, including key flexfield views for item identification and UOM checks.
• PLITBLM — The PL/SQL integer table type used for list/multi-value handling within the API.

Usage Notes

As a PVT-classified package, GME_CONVERT_FPO_PVT is not intended for direct invocation by external or customer code. It is referenced by one other package, which serves as the public-facing API layer. Typical invocation paths include process manufacturing planning forms and concurrent programs that convert firm planned orders into batches, particularly from the production scheduling and FPO conversion windows. GENERATE_PRE_BATCH_HEADER_RECS is called internally as part of the main conversion sequence rather than exposed independently. On EBS 12.1.1 and 12.2.2, the package relies on AFLOG_LEVEL for debug logging via GME_DEBUG.PUT_LINE. Customizations should extend the public API rather than this private body, since Oracle retains the right to modify private signatures between releases.