Search Results validate_fieldserviceobjects

Overview

CSF_MAINTAIN_GRP is a maintenance-group PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Field Service (CSF) product family and provides the programmatic interface used to maintain Field Service object data throughout its lifecycle. Specifically, the package exposes the validation and purge logic required to keep the Field Service scheduling and debriefing data model free of obsolete or inconsistent records.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the calling user rather than the definer. The source header (csfpurgs.pls, version 120.0, dated 2005/06/23) indicates the package originated as part of the Field Service purge infrastructure. Its API classification is GRP (group), reflecting that both entry points are PL/SQL procedures following the standard Oracle EBS API conventions: an API version parameter, initialization and commit flags, a processing set identifier, an object type discriminator, and the standard return status, message count, and message data OUT parameters.

Key Procedures and Functions

The package documents two procedures. No functions are exposed.

• Validate_FieldServiceObjects — Validates Field Service objects identified by a processing set and object type. The procedure accepts the standard API version, message-list initialization flag, and commit flag, together with a processing set ID and object type, and returns the standard X_RETURN_STATUS, X_MSG_COUNT, and X_MSG_DATA outputs. Validation likely confirms that candidate objects are eligible for subsequent maintenance operations, such as purging, before those operations are executed.
• Purge_FieldServiceObjects — Removes or retires the Field Service objects associated with the supplied processing set and object type. It shares the identical signature pattern as the validation procedure, including the API version, initialization and commit flags, processing set identifier, object type, and the three standard OUT parameters. The commit flag governs whether the purge is committed immediately or left to the caller's transaction.

Both procedures use the standard FND_API.G_FALSE defaults for the initialization and commit flags, enabling callers to compose multiple API calls within a single logical transaction when required.

Tables Accessed

The package references the following tables through APPS synonyms:

• Scheduling and planning data: CSF_R_SCHED_REQUESTS, CSF_R_PLAN_OPTIONS, CSF_R_PLAN_OPTION_TASKS, CSF_R_REQUEST_TASKS, CSF_R_RESOURCE_RESULTS, CSP_REQUIREMENT_HEADERS, and CAC_SR_OBJECT_CAPACITY.
• Debrief data: CSF_DEBRIEF_HEADERS and CSF_DEBRIEF_LINES.
• Skills and availability: CSF_REQUIRED_SKILLS_B, CSF_ACCESS_HOURS_B, and CSF_ACCESS_HOURS_TL.
• Messages and spares: CSF_R_MESSAGES, CSF_R_MESSAGE_TOKENS, and CSF_R_SPARES_OPTIONS.

These tables constitute the principal entities subject to validation and purge, covering scheduled requests, resource results, debrief records, skills, access hours, and related messaging infrastructure.

Usage Notes

CSF_MAINTAIN_GRP is typically invoked from Field Service purge and maintenance concurrent programs, which supply a processing set identifier and object type and then call the validation procedure before the purge procedure. Because the API follows FND_API conventions, custom code can call either procedure directly, checking X_RETURN_STATUS for FND_API.G_RET_STS_SUCCESS or error, and inspecting X_MSG_DATA when the message count is greater than zero. The package is referenced by one other package in the ETRM metadata, indicating that it also serves as a building block for higher-level Field Service maintenance routines. Callers should respect the commit flag semantics to preserve transactional integrity when chaining multiple maintenance operations.