Search Results validate_line_id

Overview

CSC_PLAN_LINES_PVT is a private PL/SQL package in the Oracle EBS Applications (APPS) schema that provides the transactional backbone for managing rows in the CSC_PLAN_LINES table. As the name indicates, its focus is the individual line records that belong to a service or field-service plan, rather than the plan header itself. The package encapsulates insert, update, and delete operations, and it is the single point through which the EBS infrastructure enforces item-level validations when the plan's validation level is set to 100 (FULL), as documented in the package header comment block.

The package header identifies it as a private package (PVT), consistent with the ETRM classification. Its file name is cscvplnb.pls, and the embedded header history shows an initial creation in 1999 during the Customer Care / Service planning development cycle, followed by several code-freeze revisions, NOCOPY changes in November 2002, and the addition of FND_API default removal plus a WHENEVER OSERROR EXIT FAILURE ROLLBACK directive in late November 2002. These changes reflect the standard EBS pattern of aligning private APIs with the public FND_API framework while maintaining strict error handling.

Key Procedures and Functions

The ETRM metadata documents ten procedures, which fall into two groups: the DML drivers and the validation helpers.

• CREATE_PLAN_LINES — Inserts one or more plan line records into CSC_PLAN_LINES, applying defaulting and validation before the insert is committed.
• UPDATE_PLAN_LINES — Modifies existing plan line records, including version and attribute columns, while preserving audit columns.
• DELETE_PLAN_LINES — Removes plan line records that are no longer required.
• VALIDATE_LINE_ID — Confirms that the supplied line identifier exists and is valid for the operation being performed; this is the procedure most directly associated with the "validate_line_id" search.
• VALIDATE_PLAN_ID — Confirms the parent plan identifier is valid and active.
• VALIDATE_CONDITION_ID — Validates the condition identifier that links the line to its pricing or contract condition.
• VALIDATE_OBJECT_VERSION_NUMBER — Performs optimistic locking validation, checking that the caller's object version matches the stored value.
• VALIDATE_CSC_PLAN_LINES — Performs the full row-level validation for CSC_PLAN_LINES, including item-level checks when validation level is FULL.

The package also declares G_PKG_NAME and G_FILE_NAME constants used for FND_MSG_PUB error messaging, and includes an internal convert_columns_to_rec_type helper that maps individual column values into the record type used by the private API.

Tables Accessed

Three objects are referenced through APPS synonyms. CSC_PLAN_LINES is the primary table written and read by the DML procedures. CSC_PLAN_HEADERS_B is accessed to validate the parent plan and to determine the applicable validation level. OKC_CONDITION_HEADERS_B supplies the condition header information used by VALIDATE_CONDITION_ID, tying plan lines to the OKC contract terms and conditions model.

Usage Notes

As a private package, CSC_PLAN_LINES_PVT is not intended to be called directly by customers or by external integrations. It is invoked by the public service planning APIs and by the associated EBS forms, typically from the Service / Customer Care module, and is referenced by at least one other package in the APPS schema. Developers extending plan line behavior should call the public wrapper rather than this private package, and any customization should preserve the documented validation sequence (plan, condition, line, and object version) to avoid corrupting CSC_PLAN_LINES rows or bypassing FULL level item validation.