Search Results insert_incr_actual_rsrc_txnp

Overview

GME_RESOURCE_ENGINE_PVT is the private implementation layer of the Oracle Process Manufacturing (OPM) Resource Transaction Processor in Oracle E-Business Suite. It is owned by APPS and classified as a private (PVT) API, meaning it is not intended for direct invocation by external or customer-developed code. Its purpose is to manage the lifecycle of resource transactions generated during batch manufacturing execution — creating, updating, deleting, building, consolidating, and validating the resource consumption and usage records that feed OPM cost rollup and production reporting. The package sources in the header comment date to release 120.4 (2007), but the object remains present and documented in 12.1.1 and 12.2.2.

Resource transactions capture machine, labor, and utility usage against batch steps and activities. The engine translates temporary staging records into persistent GME_RESOURCE_TXNS rows and reconciles actual usage against planned resource requirements defined in CR_RSRC_DTL and CR_RSRC_MST.

Key Procedures and Functions

• FETCH_ALL_RESOURCES — returns every resource transaction matching a staging record into a resource transactions collection, with an option to filter for active transactions only.
• CREATE_RESOURCE_TRANS — inserts a new resource transaction from a staging record and returns the populated transaction record.
• UPDATE_RESOURCE_TRANS and DELETE_RESOURCE_TRANS — modify or remove an existing resource transaction based on the supplied staging record.
• BUILD_RESOURCE_TRAN — maps a staging (GTMP) record to the persistent GME_RESOURCE_TXNS row structure.
• CONSOLIDATE_BATCH_RESOURCES — aggregates resource transactions for a given batch.
• FETCH_ACTIVE_RESOURCES — retrieves active resource transactions, with a calling-mode parameter introduced under bug#5609683.
• RESOURCE_DTL_PROCESS — processes a batch step resource record according to an action code.
• VALIDATE_RESOURCE, CHECK_PRIMARY_RESOURCE, GET_RESOURCE_USAGE, and VALIDATE_RSRC_TXN_PARAM — perform validation, primary-resource verification, usage retrieval, and parameter checking.
• UPDATE_ACTUAL_RESOURCE_USAGE and its P-suffixed variant — post actual resource usage to cost and inventory.
• INSERT_INCR_ACTUAL_RSRC_TXN and INSERT_INCR_ACTUAL_RSRC_TXNP — insert incremental actual resource transactions. The user-searched name insert_incr_actual_rsrc_txnp corresponds to the private wrapper form of this procedure. Companion pairs include the TIMED_ACTUAL and START_CMPLT_ACTUAL variants, each with a P-suffixed counterpart.

Tables Accessed

• GME_RESOURCE_TXNS and GME_RESOURCE_TXNS_GTMP — the persistent and staging resource transaction tables, the core read/write targets.
• GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_RESOURCES — batch and step context used to derive, validate, and consolidate resource usage.
• GME_BATCH_STEP_CHARGES — step charge information relevant to resource cost postings.
• CR_RSRC_DTL and CR_RSRC_MST — resource master and detail definitions supplying planned usage and validation rules.
• GMP_RESOURCE_INSTANCES — equipment/resource instance data.
• MTL_TRANSACTION_REASONS — reason codes attached to resource movements.
• SY_UOMS_MST — unit-of-measure validation and conversion.
• DUAL and PLITBLM — utility references used within PL/SQL logic.

Usage Notes

GME_RESOURCE_ENGINE_PVT is a private layer and should not be called directly. It is referenced by eight other packages, which expose the supported public wrappers such as GME_RESOURCE_ENGINE_PUB. Indirect invocation occurs through OPM batch execution forms, the Resource Transaction and batch close/charge concurrent programs, and production reporting flows that post actual resource usage. Custom code requiring resource transaction handling must target the public engine APIs instead of this private package. Because the procedures rely on GTMP staging and collection types from GME_COMMON_PVT, callers must respect commit and locking semantics defined by the public layer.