Search Results jtf_object_purge_param_tmp




Overview
Explore in AI Chat

Overview

CSF_MAINTAIN_GRP is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and classified under the ETRM GRP (group/maintenance) API category. It resides in the Field Service (CSF) module family and provides the server-side maintenance logic used to validate and purge Field Service transactional objects that are attached to a processing set. In release 12.1.1 and 12.2.2 the package is delivered as part of the standard Field Service patch set; the header comment identifies the source file as csfpurgb.pls, version 120.9, indicating that the package originated as a purge utility and was subsequently expanded with validation entry points.

The package addresses a recurring data-management problem: incident and debrief records accumulate in the Field Service schema, but not all of them are safe to remove. Some are linked to chargeable or mission-critical repair order (CMRO) objects, while others are still referenced by mobile or capacity processes. CSF_MAINTAIN_GRP centralises the decision logic that determines which records within a user-supplied processing set are eligible for deletion, then performs the deletion itself. Its GRP classification means it is intended for administrative, batch-style maintenance rather than for interactive online transactions.

Key Procedures and Functions

ETRM documents two public procedures for this package body: VALIDATE_FIELDSERVICEOBJECTS and PURGE_FIELDSERVICEOBJECTS.

  • VALIDATE_FIELDSERVICEOBJECTS — Evaluates the Field Service objects associated with a processing set identifier and marks those that are not candidates for purge. The documented logic first checks whether the incident IDs in the processing set have links to CMRO objects; when such links exist, the corresponding incident is flagged as ineligible. The procedure then invokes the mobile validation API to confirm whether the remaining incident IDs are eligible. As with all EBS APIs in this family, it follows the standard FND_API contract: it checks API version compatibility through FND_API.Compatible_API_Call, initialises the message list via FND_MSG_PUB.initialize, sets the return status to success at entry, and raises FND_API.G_EXC_UNEXPECTED_ERROR when the version check fails. It honours the standard initialise-message-list and commit control flags and returns status, message count and message data to the caller.
  • PURGE_FIELDSERVICEOBJECTS — Performs the physical removal of the Field Service objects whose processing set has been validated as purgeable. It is the companion operation to the validation procedure and is expected to be executed only after validation has marked the processing set appropriately.

Tables Accessed

The package reads and writes a broad set of Field Service configuration and transaction tables through APPS synonyms. Capacity and scheduling data is drawn from CAC_SR_OBJECT_CAPACITY, CSF_ACCESS_HOURS_B and CSF_ACCESS_HOURS_TL. Debrief transaction data resides in CSF_DEBRIEF_HEADERS and CSF_DEBRIEF_LINES. Resource and requirement definitions are held in CSF_REQUIRED_SKILLS_B, CSF_R_RESOURCE_RESULTS, CSF_R_SCHED_REQUESTS, CSF_R_SPARES_OPTIONS, CSF_R_REQUEST_TASKS and CSP_REQUIREMENT_HEADERS. Message and planning metadata come from CSF_R_MESSAGES, CSF_R_MESSAGE_TOKENS, CSF_R_PLAN_OPTIONS and CSF_R_PLAN_OPTION_TASKS. The presence of the TL table confirms that the purge logic must respect translated reference data, and the B table confirms that base and translation rows are handled together.

Usage Notes

CSF_MAINTAIN_GRP is invoked from Field Service concurrent programs and administrative purge routines rather than from end-user forms. Because it is referenced by one other package, custom code should call the documented procedures with a valid processing set ID, the correct object type, and the standard FND_API parameters; callers must supply a savepoint of their own if they intend to roll back independently. The processing set acts as the unit of work, so the validation result is only meaningful for the set that was passed in. When the search term jtf_object_purge_param_tmp arises in relation to this package, it reflects the surrounding purge infrastructure that stores purge parameters; CSF_MAINTAIN_GRP itself is the enforcement point that determines which Field Service objects those parameters may actually remove.