Search Results validate_incident_id

Overview

APPS.CSD_ESTIMATE_UTILS_PVT is a private PL/SQL utility package within the Oracle E-Business Suite Depot Repair module. Its header declares AUTHID CURRENT_USER and it is classified as a PVT (private) API, meaning it is not intended for direct invocation by external consumers but is instead called by other packages, forms, or public APIs within the CSD schema hierarchy. The package encapsulates the core validation and defaulting logic used when creating, updating, and validating repair estimates against the repair lines to which they belong.

Repair estimates in Depot Repair represent the quoted cost and scope of work for a given repair order. Because an estimate touches many dependent entities — items, revisions, serial numbers, price lists, orders, billing types, and cost records — the validation logic is centralized here so that every caller applies identical rules. The package header carries a version marker of 120.6 dated 2012/05/09, indicating a mature object with maintenance history traceable back to its initial creation in June 2005.

Key Procedures and Functions

The package exposes roughly twenty-three documented procedures and functions. Those relevant to the user's search term, validate_revision, sit alongside a family of sibling validators that follow a consistent naming convention and return BOOLEAN to signal pass or fail:

• VALIDATE_REVISION — Confirms that a supplied item revision is valid for the associated inventory item, typically by checking against MTL_ITEM_REVISIONS.
• VALIDATE_ESTIMATE_ID — Validates that an estimate is legitimate in the context of a specific repair line.
• VALIDATE_EST_STATUS — Validates an estimate status code against the permitted values defined for estimates.
• VALIDATE_REASON — Validates an estimate rejection reason code in combination with an estimate status.
• VALIDATE_UOM_CODE and VALIDATE_LEAD_TIME_UOM — Validate units of measure for the item and for lead-time expressions respectively.
• VALIDATE_PRICE_LIST — Confirms that a referenced price list is valid and usable for the estimate.
• VALIDATE_ORDER — Validates the sales order header associated with the estimate.
• VALIDATE_ITEM_INSTANCE, VALIDATE_SERIAL_NUMBER, VALIDATE_REP_LINE_ID, VALIDATE_INCIDENT_ID — Validate the item instance, serial number, repair line, and incident references.
• VALIDATE_BILLING_TYPE — Validates the billing type against the transaction billing types.
• VALIDATE_EST_HDR_REC, VALIDATE_DEFAULTED_EST_HDR, VALIDATE_EST_LINE_REC — Validate header and line record structures used during estimate creation and defaulting.
• GET_PRICING_REC, DEFAULT_EST_HDR_REC, DEFAULT_EST_LINE_REC, COPY_TO_EST_HDR_REC — Support defaulting and copying of estimate header and line data.

Parameter lists are intentionally omitted here; callers should reference the package specification directly, as no parameters are altered by this summary.

Tables Accessed

The package reads and writes a wide set of APPS synonyms spanning Depot Repair, Inventory, Costing, and Order Management:

• CSD_REPAIRS, CSD_REPAIR_ESTIMATE, CSD_REPAIR_TYPES_B — core Depot Repair and estimate records.
• CSI_ITEM_INSTANCES, MTL_SERIAL_NUMBERS — item instance and serial number validation.
• MTL_ITEM_REVISIONS, MTL_SYSTEM_ITEMS_B — revision and item validation, directly supporting VALIDATE_REVISION.
• CST_COST_TYPES, CST_ITEM_COSTS — costing references for estimate pricing.
• CS_INCIDENTS_ALL_B, CS_INCIDENT_STATUSES_B, CS_TRANSACTION_TYPES, CS_TXN_BILLING_TYPES — incident, transaction type, and billing type validation.
• FND_LOOKUP_VALUES — lookup validation for statuses and reasons.
• OE_ORDER_HEADERS_ALL — sales order header validation.

Usage Notes

Because CSD_ESTIMATE_UTILS_PVT is a private package, it is invoked indirectly — typically from the Depot Repair estimate form, from public CSD APIs, or from concurrent programs that build or validate estimates. The package is referenced by at least one other package. Custom developers should avoid direct calls; instead, use the supported public API that internally delegates to these validators. When troubleshooting estimate creation errors, enabling PL/SQL tracing on this package is the fastest way to identify which validation rejected a given record.