Search Results perform_res_txn




Overview
Explore in AI Chat

Overview

APPS.EAM_OTL_TIMECARD_PUB is a public PL/SQL package in Oracle E-Business Suite that supports the integration between Oracle Enterprise Asset Management (EAM) and Oracle Time and Labor (OTL). Its principal business purpose is to bridge shop-floor maintenance transactions recorded against assets and work orders with the time and labor infrastructure, allowing timecard and resource transaction data to be retrieved, validated, and processed consistently. The package exposes a public API surface (classified as PUB in ETRM 12.2.2) intended for use by Oracle applications and by customer extensions that need to drive the EAM timecard retrieval and validation cycle. It operates on the APPS schema and is delivered with header version EAMOTLTS.pls 120.0, first shipped in the 11i/12.0 lineage and carried forward into 12.1.1 and 12.2.2.

Key Procedures and Functions

  • GET_ATTRIBUTE_ID — Resolves the time attribute group and related identifiers from a user type definition and building block id, returning work order, operation, resource, charge department, asset group, owning department, and asset number values. It is the entry point for mapping a time building block to EAM shop-floor context.
  • PERFORM_RES_TXN — Performs a resource transaction for a given WIP entity, operation sequence, resource instance, department, and quantity at a specified start time, effectively posting shop-floor resource usage to the manufacturing/EAM transaction stream.
  • WHERE_CLAUSE — Builds a dynamic SQL predicate from the supplied filter attributes (asset group, asset number, owning and charge department, resource, work order, operation, organization, and person) and returns it for use in retrieval queries.
  • RETRIEVE_PROCESS — The main concurrent-program entry point. It accepts start and end dates, organization and asset/resource filters, department and transaction code parameters, and returns the standard errbuf/retcode pair used by concurrent managers.
  • GET_PERSON_ID — Returns the current person identifier, typically derived from the FND_USER session context.
  • VALIDATE_WORK_DAY — Validates whether a supplied date is a valid work day for the given organization by returning a status value, using calendar data.
  • GET_RETRIEVAL_FUNCTION — Returns the name of the retrieval function used by the timecard retrieval flow.
  • VALIDATE_PROCESS — Performs validation of the timecard retrieval/processing results, applying the business rules that determine whether retrieved time can be accepted. This is the object associated with the search term validate_process.
  • EAM_VALIDATE_TIMECARD — Validates an individual EAM timecard record against EAM rules before it is committed.
  • ADD_ERROR_TO_TABLE — Records validation or processing errors into the message/error table so they are surfaced to the user or concurrent log.

Tables Accessed

The package reads and writes through APPS synonyms. HXC_TIME_BUILDING_BLOCKS supplies the timecard building block records being processed, while FND_NEW_MESSAGES and FND_USER support error messaging and user/person resolution. Calendar validation uses BOM_CALENDARS, BOM_CALENDAR_EXCEPTIONS, BOM_WORKDAY_PATTERNS, and ORG_ACCT_PERIODS to determine valid working days and open periods. Resource and department context is drawn from BOM_DEPARTMENTS, BOM_DEPARTMENT_RESOURCES, BOM_DEPT_RES_INSTANCES, BOM_RESOURCES, and BOM_RESOURCE_EMPLOYEES. Asset instance data comes from CSI_ITEM_INSTANCES, costing context from CST_ACTIVITIES, and organization parameters from MTL_PARAMETERS.

Usage Notes

EAM_OTL_TIMECARD_PUB is most commonly invoked from the EAM Timecard Retrieval concurrent program (via RETRIEVE_PROCESS and VALIDATE_PROCESS), from OTL timecard entry screens that need to translate time building blocks into EAM work order and resource context, and from custom extensions that post resource transactions through PERFORM_RES_TXN. ETRM records zero referencing packages, so it is a top-level entry point rather than an internal helper. Because it is classified PUB, callers may rely on its signatures across 12.1.1 and 12.2.2, but should always honor the errbuf/retcode contract and inspect the error table populated by ADD_ERROR_TO_TABLE before assuming successful validation.