Search Results get_source_document_id

Overview

CTO_UTILITY_PK is a shared utility package in the APPS schema of Oracle E-Business Suite, belonging to the Configure-To-Order (CTO) application family. In both Release 12.1.1 and 12.2.2, it functions as the low-level helper library that supports the broader CTO configuration, sourcing, and order-line processing infrastructure. Rather than exposing a user-facing business flow of its own, CTO_UTILITY_PK centralizes recurring operations—sourcing organization resolution, order-line maintenance, unit-of-measure conversion, attachment generation, reservation validation, and configuration item checks—so that other CTO packages can invoke them consistently. Its status is documented as VALID, and the ETRM metadata classifies it as an API of type OTHER.

The package is highly central to the CTO module: it is referenced by 24 other packages, including CTO_ATP_INTERFACE_PK, CTO_AUTO_PROCURE_PK, CTO_BOM_RTG_PK, CTO_CONFIG_BOM_PK, CTO_ITEM_PK, CTO_WIP_WORKFLOW_API_PK, and CZ_BOM_CONFIG_EXPLOSIONS_PKG, and it also calls itself recursively. This dependency footprint confirms its role as a foundational utility layer for configured-item processing.

Key Procedures and Functions

The documented package interface exposes 38 procedures and functions. The principal categories are:

• Sourcing organization management — POPULATE_SRC_ORGS, UPDATE_SRC_ORGS, CREATE_SOURCING_RULES, QUERY_SOURCING_ORG, GET_MODEL_SOURCING_ORG, and POPULATE_BCOL support the definition, population, and querying of sourcing rules and source organizations for configured models and order lines.
• Order-line processing — UPDATE_ORDER_LINES and POPULATE_BCOL maintain the BOM_CTO_ORDER_LINES records that track configured order lines.
• Item and organization queries — GET_ALL_ITEM_ORGS returns the organizations in which an item is defined; CHECK_CONFIG_ITEM and ISMODELMLMO validate configuration and model status.
• Reservation validation — CHECK_RSV_QUANTITY and CHK_ALL_RSV_DETAILS validate reservation quantities and details before supply or demand actions proceed.
• Supply and procurement checks — CHECK_CTO_CAN_CREATE_SUPPLY determines whether a configured item can generate supply; GET_SOURCE_DOCUMENT_ID and GET_MODEL_SOURCING_ORG resolve source documents and organizations.
• Conversions and value handling — CONVERT_UOM performs unit-of-measure conversion; CONCAT_VALUES and COPY_COST handle string concatenation and cost copying.
• Attachments and BOM text — CREATE_ATTACHMENT and GENERATE_BOM_ATTACH_TEXT build document attachments and BOM attachment text.
• BOM and cost generation — CREATE_ISP_BOM constructs ISP-related BOM structures.

Tables Accessed

Access is performed through APPS synonyms. Core tables include BOM_CTO_ORDER_LINES (configured order-line data), BOM_CTO_ORDER_LINES_GT (the global temporary staging table for order lines), BOM_CTO_SRC_ORGS (sourcing organizations), MTL_SYSTEM_ITEMS (item master), FND_USER (user identity), and FINANCIALS_SYSTEM_PARAMS_ALL (financial system parameters). BOM_EXPLOSION_TEMP and BOM_EXPLOSION_TEMP_S are used for BOM explosion staging, and BOM_OPERATIONAL_ROUTINGS supports routing access. Cost-related data is read from CST_ITEM_COSTS and CST_ITEM_COST_DETAILS. Attachment and document text handling uses FND_ATTACHED_DOCUMENTS, FND_ATTACHED_DOCUMENTS_S, FND_DOCUMENTS_LONG_TEXT, FND_DOCUMENTS_TL, and FND_LANGUAGES.

Usage Notes

CTO_UTILITY_PK is not normally invoked directly by end users. It is called programmatically by the CTO package suite during configured order processing, AutoCreate, configuration BOM/routing generation, ATP checks, and WIP workflow integration. Because it is a dependency of 24 packages, changes to its interface can cascade across the CTO module. Custom code should reference the documented procedures only as declared, and any extensions should treat this package as an internal utility layer rather than a stable public API.