Search Results cse_cost_collector




Overview
Explore in AI Chat

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

Overview

APPS.CSE_COST_COLLECTOR is a cost collection and expenditure interface package within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 Enterprise Asset Management and Projects costing stack. Its primary business function is to collect manufacturing, inventory, and capitalized transaction costs originating in Oracle Inventory, Work in Process, or Oracle Projects, and to feed them into Oracle Projects as expenditure items and cost distribution lines. In this capacity it acts as the bridge between supply-chain transactional data and the Projects subledger, ensuring that material, resource, and burden costs are recognized against the correct project, task, and expenditure organization.

The package also exposes a reversal capability (reverse_expenditures) that lets callers unwind previously collected and distributed expenditure amounts, correlating them back to the originating transactions and accounting periods. Published under the APPS schema and flagged as OTHER in ETRM for 12.2.2, this package is a low-level integration component rather than an end-user feature.

Key Procedures and Functions

  • EIB_COST_COLLECTOR_STUB — The main cost-collection entry point. It receives a comprehensive set of transactional parameters describing the source event: transaction and organization identifiers, transaction action and source type, project and task identifiers (including transfer and source project/task variants), transaction date and primary quantity, cost group and transfer cost group, inventory item, primary cost method, accounting period, expenditure organization, and distribution account. It further accepts costing literals for Inventory, Business Unit, and WIP system links, expenditure type inputs, denom currency code, and debit/credit code combinations together with raw and burdened cost, cost element, and subledger identifiers. The procedure returns hook usage and standard error outputs (error number, code, and message). As its "stub" name suggests, it is designed to be invoked by originating modules or an EIB integration layer to convey a single cost event.
  • REVERSE_EXPENDITURES — A reversal routine that processes expenditure reversals tied to the collected cost records. The naming aligns with the user search term reverse_expenditures. Because the documented signature carries no parameters, it is typically invoked as part of a batch or concurrent reversal flow rather than as a finely targeted call, and driver logic selects the expenditures to reverse based on system state.

Tables Accessed

Usage Notes

CSE_COST_COLLECTOR is not invoked directly from a standard form; it is a back-end API. It is most commonly triggered by cost-collection concurrent programs, by the Enterprise Installation / capitalized-cost integration flows, or by custom PL/SQL that must inject or reverse project expenditures. Because only one other package references it, extension developers invoking it directly should mirror the parameter contract exactly and honor the returned error outputs, then commit appropriately. When reversing, callers should confirm period status in ORG_ACCT_PERIODS to avoid posting into closed accounting periods.