Search Results validate_and_write

Overview

CSD_TO_FORM_REPAIR_JOB_XREF is an Oracle EBS Application Object Library (AOL) PL/SQL package owned by the APPS schema. Its documented purpose is to accept all parameters passed from the Oracle Forms interface and construct those parameters into a single record suitable for calling the private API within the CSP_MOVEORDER_HEADERS_PVT package. In effect, the package functions as a forms-to-API adapter layer: the Oracle Forms block for the Repair Job Cross Reference entity supplies field values individually, and CSD_TO_FORM_REPAIR_JOB_XREF packages them into the structured arguments required by the underlying move-order header private API.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL and PL/SQL statements execute with the privileges of the invoking user rather than the definer, a standard construct for this class of EBS adapter packages. The header comment records a creation date of 17 November 1999 by Vernon Lou, with subsequent revisions by TRAVI in December 2001 (adding INVENTORY_ITEM_ID and ITEM_REVISION) and January 2002 (adding OBJECT_VERSION_NUMBER). A further revision dated 20 August 2003 by Shiv Ragunathan introduced the 11.5.10 changes that added p_source_type_code, p_source_id1, p_ro_service_code_id and p_job_name to the Validate_And_Write procedure. These same objects remain present in both the 12.1.1 and 12.2.2 releases, where the package is retained largely unchanged as part of the Depot Repair / repair job cross-reference infrastructure.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package: VALIDATE_AND_WRITE. No other procedures or functions are documented as part of the public interface.

• VALIDATE_AND_WRITE — The sole documented entry point. It validates the attribute values supplied from the form, sets up the API message list, and writes the repair job cross-reference record through the CSP_MOVEORDER_HEADERS_PVT private API. It supports an API version number, an initialization flag for the message list, a commit flag, and a validation level, consistent with the standard EBS API calling convention. Its p_action_code parameter drives the DML mode, where 0 indicates insert, 1 indicates update and 2 indicates delete. The procedure participates in the EBS optimistic locking scheme through the OBJECT_VERSION_NUMBER parameter. On insert, the repair job cross-reference identifier is returned to the caller through the IN OUT NOCOPY parameter px_REPAIR_JOB_XREF_ID.

Tables Accessed

The ETRM metadata for this object does not enumerate specific tables through the APPS synonym layer. Based on its documented purpose, the package operates on the Repair Job Cross Reference entity and routes its write operations through the CSP_MOVEORDER_HEADERS_PVT package, which owns the actual table-level DML. The parameter signature confirms the entity attributes maintained: REPAIR_JOB_XREF_ID, REPAIR_LINE_ID, WIP_ENTITY_ID, GROUP_ID, ORGANIZATION_ID, QUANTITY, INVENTORY_ITEM_ID, ITEM_REVISION, SOURCE_TYPE_CODE, SOURCE_ID1, RO_SERVICE_CODE_ID and JOB_NAME, together with the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the ATTRIBUTE_CATEGORY / ATTRIBUTE1 through ATTRIBUTE10 descriptive flexfield columns.

Usage Notes

CSD_TO_FORM_REPAIR_JOB_XREF is invoked from the Oracle Forms layer, typically as the button or save handler that submits repair job cross-reference changes. The caller supplies the audit and API control parameters explicitly and passes the action code to select insert, update or delete behavior. Because the object is referenced by four other packages, it also serves as a programmatic entry point for concurrent programs and custom extensions that need to create or maintain repair job cross reference records without going through the form. Developers integrating with this object should preserve the documented calling convention, honor the commit and validation level flags, and treat the private CSP_MOVEORDER_HEADERS_PVT APIs as internal implementation details rather than supported entry points.