Search Results bom_explosion_temp_s




Overview
Explore in AI Chat

Overview

APPS.CTO_TRANSFER_PRICE_PK is a configuration-to-order (CTO) pricing utility package body in Oracle E-Business Suite. Its business purpose is to determine and transfer the correct unit price from a configured parent item down to the components and sub-assemblies that originate from a configuration, so that the pricing of an assembled, make-to-order deliverable reflects the transfer price defined for the configuration rather than standalone component list prices.

In CTO and Assemble-to-Order (ATO) flows the sales order line references a model or option class, and the actual shipped or built item is derived through a bill of material explosion. Because the components are generated at order entry time, standard price list logic may not resolve them correctly. This package bridges that gap by reading the exploded configuration structure, resolving item attributes, and transferring the appropriate price onto the configuration's related order lines. It sits within the broader CTO utility family alongside CTO_UTILITY_PK and CTO_WIP_WORKFLOW_API_PK.

Key Procedures and Functions

The documented PL/SQL interface exposes four procedures and functions:

  • GET_CONFIG_DETAILS — The primary driver routine. It gathers the details of a given configuration, orchestrating the calls that resolve the configuration structure and initiate the price transfer logic.
  • GET_CONFIG_DETAILS_BCOL — Retrieves configuration details using the BOM CTO Order Lines path, reading the staged configuration order line records that represent the configuration at order entry time.
  • GET_CONFIG_DETAILS_BOM — Retrieves configuration details by performing a bill of material explosion, deriving the component hierarchy from BOM structures rather than from pre-staged order lines.
  • CTO_TRANSFER_PRICE — The transfer routine that applies and moves the resolved price onto the target configuration order lines.

Parameter lists are not reproduced here; the interface follows standard FND_API conventions for message and return-status handling.

Tables Accessed

Per the ETRM metadata, the package reads and writes the following objects (through APPS synonyms):

  • BOM_CTO_ORDER_LINES — Staged CTO order line data that links a sales order configuration to its exploded BOM structure; the source for the BCOL retrieval path.
  • BOM_EXPLOSION_TEMP and BOM_EXPLOSION_TEMP_S — The BOM explosion temporary structures. BOM_EXPLOSION_TEMP_S is the serialization or summary companion table, and is the specific object associated with the search term bom_explosion_temp_s. These hold the exploded component hierarchy used by GET_CONFIG_DETAILS_BOM.
  • MTL_SYSTEM_ITEMS — Supplies item master attributes for the exploded components.
  • OE_ORDER_LINES_ALL — The order line table where transferred prices are ultimately reflected and read from for pricing context.
  • DUAL — Used for scalar evaluations and FND_API calls.

Additional dependencies documented in the broader metadata include BOM_BILL_OF_MATERIALS, BOM_INVENTORY_COMPONENTS, and OE_SYS_PARAMETERS, used to resolve BOM structure, component relationships, and system-level CTO profile behavior.

Usage Notes

CTO_TRANSFER_PRICE_PK is an internal engine package rather than a user-invocable API. It is not referenced by any database object, confirming that it acts as a dependent utility called by other packages and by the CTO order-processing flow. Typical invocation occurs during sales order entry when a configured item is booked, from the pricing and configuration validation path, and from concurrent or workflow processes handling CTO order lines.

It is commonly triggered indirectly through Oracle Order Management and Oracle Configurator flows, or via workflow activities managed by CTO_WIP_WORKFLOW_API_PK. Custom code should not call these procedures directly unless the FND_API message stack and CTO context are correctly initialized, as the routines depend on CTO_MSG_PUB, FND_MSG_PUB, FND_PROFILE, INV_TRANSACTION_FLOW_PUB, and OE_DEBUG_PUB for messaging, profile resolution, and diagnostics. Debugging behavior is governed by the relevant OE/CTO debug profiles.