Results for “auto_charge_type”

4 results




Overview
Explore in AI Chat

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

Overview

APPS.CST_PRJMFG_COST_COLLECTOR is a Cost Management package body responsible for collecting, validating, and grouping cost transactions originating in Oracle Project Manufacturing (Project MFG) environments. It functions as the transaction-processing layer that translates inventory, work-in-process, and requisition-driven material movements into the cost records maintained by the Cost Management (CST) subsystem. The package sits at the intersection of Project Manufacturing, Inventory, Bills of Material, and Work in Process modules, ensuring that material and resource transactions associated with project and task references are properly costed, assigned to cost groups, and posted against the correct accounting periods.

The package name reflects its mandate: it collects project manufacturing costs. Its internal procedures such as pm_process_txn_mmt and pm_check_error_mmt support Project MFG transaction processing for material movements, while the publicly documented entry points orchestrate cost collection across transaction types. The header version stamp (CSTPPCCB.pls 120.32.12020000.6) indicates a file maintained through the 12.1.x and 12.2.x release cycles, with bug-fix identifiers embedded in the source (for example, bug 3495967) confirming ongoing patching.

Key Procedures and Functions

  • PM_MARK_NON_PROJECT_WORLD_TXNS — Identifies and flags transactions that are not tied to Project Manufacturing, distinguishing them from project-related transactions so that the remainder of the collection logic can focus on valid project cost transactions.
  • PM_CC_WORKER_MMT — The worker procedure that processes Material Transactions (MMT). It serves as the primary engine for collecting cost information from material movement records and preparing them for cost grouping.
  • PM_CC_WORKER_WT — The worker procedure for Work-in-Process Transactions (WT), handling the cost collection path for WIP-related movements rather than inventory material transactions.
  • ASSIGN_GROUPS_TO_MMT_TXNS — Assigns cost groups to material transactions, enabling the cost roll-up and accounting processes to aggregate related transactions consistently.
  • ASSIGN_GROUPS_TO_WT_TXNS — Performs the equivalent cost-group assignment for WIP transactions.
  • PM_GET_MTA_ACCTS — Resolves the Material Transaction Accounts (MTA) associated with a given transaction, determining the accounting flexfield combination used for cost distribution.
  • GET_GROUP_SIZE — Returns the size of a cost group, supporting batching and performance management when the collection logic processes transactions in groups.

Tables Accessed

The package reads and writes several core EBS tables through APPS synonyms. MTL_MATERIAL_TRANSACTIONS and MTL_MATERIAL_TRANSACTIONS_S provide the material transaction and sub-inventory detail that drives MMT processing. MTL_PARAMETERS and MTL_SECONDARY_INVENTORIES supply organization-level costing and sub-inventory attributes. Cost detail is sourced from CST_ITEM_COST_DETAILS, CST_QUANTITY_LAYERS, MTL_ACTUAL_COST_SUBELEMENT, and MTL_CST_ACTUAL_COST_DETAILS. Expense type mapping uses CST_COST_ELEM_EXP_TYPES. Resource and department data come from BOM_RESOURCES and BOM_DEPARTMENTS. Organization and currency information is retrieved from HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, HR_ORGANIZATION_INFORMATION, and GL_DAILY_CONVERSION_TYPES.

Usage Notes

CST_PRJMFG_COST_COLLECTOR is typically invoked indirectly through the Cost Management transaction costing and cost collection concurrent programs rather than being called directly by end users. Project Manufacturing cost collection, inventory cost processing, and period-close activities trigger its procedures. Because the package is classified as API OTHER, custom integrations should exercise caution and prefer supported public entry points. It is referenced by no other packages in the documented metadata, meaning it functions as a terminal worker rather than a shared library, and it should be considered internal to Cost Management even though it is installed under the APPS schema.