Results for “check_termination_for_cwk”

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

Overview

PATC is a PL/SQL package owned by APPS within the Oracle E-Business Suite Projects (PA) module. Its principal purpose is to enforce Project Transaction Controls — the business rules that govern which expenditures may be charged to which projects, tasks, and organizational combinations. The package header comments reference the "Using Transaction Controls" essay in the Release 10 OPA Reference Manual, indicating that the design lineage of the package predates the current 12.1.1 and 12.2.2 code lines; the shipped header identifier (PAXTTXCS.pls 120.2.12000000.4, dated 2007) reflects a long-stable interface that has been carried forward through subsequent releases.

Functionally, PATC occupies the validation layer of Oracle Projects transaction processing. When a candidate expenditure, labor charge, or invoice distribution is submitted against a project, PATC determines whether that item is permissible under the project's or task's configured transaction controls and, where applicable, whether it qualifies as billable. The package also exposes termination-checking logic tied to employee periods of service and placement, which supports the rules that prevent charges from being applied against individuals who are no longer eligible to charge time or costs to a given project.

Key Procedures and Functions

The documented interface exposes four procedures and functions. Parameter signatures are not reproduced here; the descriptions below reflect the intended purpose of each entry point.

• SET_BILLABLE_FLAG — Sets or derives the billable flag associated with a transaction under evaluation, allowing the transaction control pathway to record whether a validated item should be treated as billable for subsequent costing and revenue processing.
• GET_STATUS — Returns the status or disposition of a transaction relative to the applicable controls, providing callers with the outcome of validation without requiring them to re-derive the precedence logic themselves.
• CHECK_TERMINATION — Evaluates whether an employee has terminated, using the person, placement, and service period data accessible to the package, so that charges attributable to that person can be assessed against project and task control rules.
• CHECK_TERMINATION_FOR_CWK — A variant of the termination check oriented specifically toward chargeable work / cost-eligible assignments, supporting the validation of persons whose assignment status would otherwise permit or block a charge.

The package header further documents the internal processing flow: a transaction first passes basic validation (project not closed, task chargeable, transaction date within project and task start/end dates). It is then evaluated against task-level controls, which always override project-level controls. If no applicable task-level control is found, the "limit to transaction controls" flag determines whether the item is rejected outright or passed down to project-level controls. Where multiple controls apply, precedence is resolved in the following order: Person–Expenditure Category–Expenditure Type–[Non-Labor Resource]; Person–Expenditure Category; Expenditure Category–Expenditure Type–[Non-Labor Resource]; and finally Expenditure Category.

Tables Accessed

PATC reads and writes across the Projects and HR schema families through APPS synonyms. Project and task definition data is drawn from PA_PROJECTS_ALL, PA_TASKS, PA_PROJECT_TYPES_ALL, PA_PROJECT_ASSIGNMENTS, and PA_ALTERNATE_TASKS. Transaction control definitions come from PA_TRANSACTION_CONTROLS, while expenditure classification draws on PA_EXPENDITURE_TYPES, PA_EXPEND_TYP_SYS_LINKS, PA_EXPENDITURE_ITEMS_ALL, and PA_WORK_TYPES_TL. Employee eligibility and termination data is sourced from PER_ALL_PEOPLE_F, PER_PERSON_TYPES, PER_PERIODS_OF_PLACEMENT, and PER_PERIODS_OF_SERVICE. AP_INVOICES_ALL is referenced to support invoice-related charge validation.

Usage Notes

PATC is an internal infrastructure package rather than a public API. It is referenced by nine other packages in the Projects schema, and it is typically invoked indirectly — from Oracle Projects forms during expenditure entry and adjustment, from concurrent programs performing transaction validation and interface processing, and from custom extensions that must reproduce native transaction control behavior. Because the package header notes that transactions are evaluated only against the highest-precedence applicable control, custom code that bypasses PATC risks producing results inconsistent with standard Projects validation.