Search Results clean_invalid_data

Overview

APPS.JMF_SHIKYU_UTIL is a utility package body in the Oracle E-Business Suite ETRM (Enterprise Territory and Resource Management / Charge-Based SHIKYU) module. Its source file, JMFUSHKB.pls, was created in April 2005 and last revised in October 2007 (version 120.17). The package encapsulates the shared PL/SQL logic required by the Charge Based SHIKYU project, which supports subcontracting and replenishment costing, allocation, and shipment processing within Oracle Manufacturing and Order Management. Because it is classified as a UTIL package in the documented metadata, it is not an end-user facing API; it provides reusable helper routines that other packages and concurrent programs call to retrieve quantities, unit-of-measure attributes, allocation dates, component prices, and account information. The package is referenced by eight other packages, confirming its role as a foundational dependency. The clean_invalid_data procedure, added 30-AUG-2006, is one of twenty-six documented procedures and functions in this package body.

Key Procedures and Functions

The package exposes twenty-six documented routines covering UOM handling, quantity retrieval, allocation, pricing, and date conversion.

• CLEAN_INVALID_DATA — Added in August 2006, this procedure purges or repairs invalid data encountered by the SHIKYU charge-based process. It is the routine most associated with the user's search term.
• GET_PRIMARY_UOM, GET_PRIMARY_UOM_CODE, GET_UOM_CODE, GET_UOM_CONVERSION_RATE — Return the primary unit of measure, its code, a specified item's UOM code, and conversion rates between units of measure.
• GET_PRIMARY_QUANTITY — Derives the primary quantity for a given item or transaction.
• GET_USED_QUANTITY, GET_REPLENISH_SO_RETURNED_QTY, GET_REPLENISH_SO_RECEIVED_QTY — Report consumed quantities and replenishment sales-order return and receipt quantities. GET_REPLENISH_SO_RETURNED_QTY was modified 26-JUN-2006.
• GET_FINAL_SHIP_DATE, GET_ALLOCATION_DATE — Return shipping and allocation dates. GET_ALLOCATION_DATE was modified 15-FEB-2005 to return the scheduled_start_date of the WIP job if work has not started, otherwise the scheduled_completion_date.
• GET_SUBCONTRACT_ORDER_ORG_IDS, GET_SUBCONTRACT_ALLOCATED_QTY — Provide subcontracting order organization identifiers and allocated quantities. GET_SUBCONTRACT_ALLOCATED_QTY returns zero when no allocations exist for the specified order.
• GET_SHIKYU_ATTRIBUTES, GET_SHIKYU_COMPONENT_PRICE, GET_SHIKYU_OFFSET_ACCOUNT — Retrieve SHIKYU attributes, component prices, and offset accounting information. GET_SHIKYU_COMPONENT_PRICE had its signature and query corrected in September 2005.
• GET_REPLEN_PO_ALLOCATED_QTY, GET_REPLEN_PO_ORDERED_QTY, GET_REPLEN_SO_ALLOCATED_QTY, GET_REPLENISHMENT_SO_PRICE — Return replenishment PO and SO allocated and ordered quantities, plus replenishment sales-order pricing.
• TO_XSD_DATE_STRING — Added 08-SEP-2006 and later enhanced to accept an optional timezone-offset parameter, converting dates to XSD format for correct rendering in XML Publisher reports.
• DEBUG_OUTPUT — Added 03-OCT-2005 for diagnostic output.

Tables Accessed

The package reads and writes through APPS synonyms. The SHIKYU-specific tables — JMF_SHIKYU_ALLOCATIONS, JMF_SHIKYU_COMPONENTS, JMF_SHIKYU_REPLENISHMENTS, and JMF_SUBCONTRACT_ORDERS — hold allocation records, component definitions, replenishment data, and subcontract orders respectively; these are the primary tables used by the retrieval and cleanup routines. MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_B supply item attributes, while MTL_UNITS_OF_MEASURE, MTL_INTERORG_PARAMETERS, and MTL_INTERORG_SHIP_METHODS support UOM conversion and inter-org shipping logic. OE_ORDER_LINES_ALL, PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL provide order and purchasing data used by the replenishment quantity and price functions. RCV_TRANSACTIONS supplies receiving transaction data. FND_CONCURRENT_REQUESTS is referenced for concurrent request context, consistent with the June 2006 change making worker request options visible.

Usage Notes

JMF_SHIKYU_UTIL is invoked indirectly by the eight dependent packages rather than by end users. It runs within the context of concurrent programs, Oracle Forms-based SHIKYU maintenance screens, and XML Publisher reports — the latter through TO_XSD_DATE_STRING. The CLEAN_INVALID_DATA procedure would typically be executed as part of a corrective or housekeeping concurrent request when allocation, component, or replenishment data is found to be inconsistent. Because the last source revision is dated 2007, the package remains compatible with the EBS 12.1.1 and 12.2.2 file systems, though it is a legacy component of the charge-based SHIKYU feature set.