Search Results tbl_type

Overview

CST_PERIODIC_ABSORPTION_PROC is an Oracle E-Business Suite cost management package owned by the APPS schema. It implements the periodic absorption processing logic used by Oracle Cost Management to transfer costs across inventory organizations and to execute periodic cost updates. Although its source file (CSTRITPS.pls) originated as the Inter Organization Transfer concurrent program, the package body was renamed to CST_PERIODIC_ABSORPTION_PROC during R12 development to reflect its broader role in periodic costing.

The package supports the rollup and absorption of costs at period close, including inter-organization transfers, WIP completion transactions, and periodic cost updates. It is central to the flow that reconciles cost group balances and posts value changes resulting from material movements between cost groups and organizations. The tbl_type element users commonly search for refers to PL/SQL collection types declared within the package specification and body for passing sets of rows between procedures.

Key Procedures and Functions

• GET_EXP_FLAG — Determines and returns an explosion or processing flag used to control how items are expanded during periodic absorption. It gates rollup behavior, notably the "Rollup for all items by BOM level" option introduced in the 2004 design change for WIP completion items.
• TRANSFER_CP_MANAGER — Manages the inter-organization transfer concurrent program logic. It orchestrates transfer processing across legal entities, incorporating the LE time zone fix (Bug#4351270) via the p_le_process_upto_date parameter so that transactions are bounded by the correct legal-entity cutoff date.
• PERIODIC_COST_UPDATE_BY_LEVEL — Executes periodic cost update organized by BOM level. This corresponds to the documented change that "Value Change has to be processed after all the cost owned txns," in particular after inter-org receipts, so that cost adjustments are applied in the correct sequence relative to the primary quantity populated on MTL_MATERIAL_TRANSACTIONS (Bug 7342514).

Supporting internal logic includes functions such as Get_Transfer_Price_Option, Calc_Pmac_Update_Cppb_First (a cost-group-specific variant of Calc_Pmac_Update_Cppb), and Check_Interorg_Item_Level, which enforce the item-level validation rules introduced for inter-org processing.

Tables Accessed

Through APPS synonyms the package reads and writes a mix of transaction, costing setup, and period-control tables.

• MTL_MATERIAL_TRANSACTIONS — source transaction rows consumed and updated during periodic processing, including cost adjustments and value changes.
• CST_COST_GROUPS, CST_COST_GROUP_ASSIGNMENTS, CST_COST_TYPES, CST_LE_COST_TYPES — provide the cost group structure and cost type definitions that determine how costs are absorbed and rolled up.
• CST_PAC_EXPLOSION_TEMP, CST_PAC_INTORG_ITMS_TEMP, CST_PAC_ITMS_ABSL_CODES, CST_PAC_LOW_LEVEL_CODES — temporary and low-level-code tables used to sequence items by BOM level and track absorption codes during processing.
• CST_PAC_PERIODS, CST_PAC_PERIOD_BALANCES, CST_PAC_PROCESS_PHASES — maintain period state, balance snapshots, and phase control that govern the periodic cost update cycle.
• FND_CONCURRENT_REQUESTS — records the concurrent program request associated with the run.
• HR_ORGANIZATION_INFORMATION, MTL_INTERCOMPANY_PARAMETERS — supply organization and intercompany parameters used for inter-org transfer pricing and legal-entity cutoff handling.

Usage Notes

CST_PERIODIC_ABSORPTION_PROC is invoked primarily by Oracle Cost Management concurrent programs, including Periodic Cost Update and Inter-Organization Transfer, rather than directly from forms. It is also referenced by three other packages, which call its procedures to reuse the periodic absorption and transfer logic. Custom code should call the documented procedures only through their public specification, observing the API-standard return conventions (x_return_status of Success or Error, and x_error_message) established in the 2003 revision. Because it enforces BOM-level sequencing and legal-entity time zone rules, it must be scheduled within the standard period-close sequence and should not be run ahead of dependent transaction processing.