Search Results get_contract_resolve_by_date

Overview

CSD_REPAIRS_UTIL is a utility package in the APPS schema that provides the shared, low-level services underpinning the Oracle E-Business Suite Depot Repair module. It is classified as a UTIL package, meaning it is not an externally exposed business API but rather an internal helper layer consumed by the public and private repair APIs, concurrent programs, and forms. The package consolidates cross-cutting logic required throughout the repair lifecycle — receipt and return of defective items, repair order status transitions, entitlement and warranty evaluation, requisition creation, and item-instance ownership changes — so that the higher-level repair packages do not duplicate that logic.

The package sits within the CSD (Depot Repair) product family and is tightly coupled to the Service (CSI/CS) and Order Management/Service Fulfillment components. Its dependencies establish the module boundaries: it references CSD_REPAIRS_PUB, FND_API (for the standard Oracle API error-handling framework), OKS_ENTITLEMENTS_PUB (service contracts and entitlement verification), and the SYS.STANDARD library. The package has been validated as VALID against both Oracle EBS 12.1.1 and 12.2.2, and ETRM 12.2.2 documents 21 procedures and functions within it.

Key Procedures and Functions

The documented entry points divide into several functional groupings:

• Validation and security: IS_DESCFLEX_VALID, CHECK_REQD_PARAM, CHECK_WEBSRVC_SECURITY, and CHECK_TASK_N_WIPJOB provide input validation, mandatory-parameter enforcement, web-service authorization checks, and verification of task-to-WIP job relationships.
• Record and status conversion: CONVERT_TO_REPLN_REC_TYPE, CONVERT_TO_DEF_REC_TYPE, and CONVERT_STATUS_VAL_TO_ID translate values between the replacement record structures, default record structures, and internal status identifiers used across the repair APIs.
• Entitlement and warranty: GET_ENTITLEMENTS and CREATE_REPAIR_WARRANTY retrieve service entitlement information and establish warranty coverage for a repair order.
• Item and ownership handling: CHANGE_ITEM_IB_OWNER reassigns installed-base ownership, while CREATE_INST_PARTY_RELATION creates party relationships associated with an item instance.
• Repair order defaults and updates: DEFAULT_RO_ATTRS_FROM_RULE applies repair-order attribute defaults derived from business rules, and AUTO_UPDATE_RO_STATUS performs automated repair-order status progression.
• Procurement and contracts: CREATE_REQUISITION and CREATE_REQUISITION_CP create purchase requisitions for repair-related material (and a concurrent-program variant), while GET_CONTRACT_RESOLVE_BY_DATE resolves the applicable contract based on a given date.
• Descriptive and profile data: GET_KB_ELEMENT_DESCRIPTION and GET_USER_PROFILE_OPTION_NAME look up knowledge-base element descriptions and translated profile option names, while CREATE_CSD_INDEX builds supporting indexes used by the repair schema.

Tables Accessed

The package reads and writes a broad set of tables through APPS synonyms. CSD_REPAIRS, CSD_PRODUCT_TRANSACTIONS, CSD_PRODUCT_TRANSACTIONS_S1, CSD_REPAIR_JOB_XREF, CSD_WIP_TRANSACTION_DETAILS, and CSD_FLOW_STATUSES_B represent the core repair order, transaction, WIP, and workflow-status data. CSI_ITEM_INSTANCES, CSI_I_PARTIES, CSI_IP_ACCOUNTS, and HZ_PARTIES supply installed-base instance, party, and account context. BOM_DEPARTMENTS provides department references for WIP activity, while CS_ESTIMATE_DETAILS supports repair estimating. FND_USER, FND_PROFILE_OPTIONS_TL, and HR_ORGANIZATION_INFORMATION supply user, profile option translation, and organization information.

Usage Notes

CSD_REPAIRS_UTIL is not intended for direct invocation by external integrations. It is referenced by thirteen other packages, including CSD_REPAIRS_GRP, CSD_REPAIRS_PVT, CSD_BULK_RECEIVE_UTIL, CSD_REPAIR_ESTIMATE_PVT, CSD_REPAIR_GROUPS_PVT, CSD_SPLIT_PKG, CSD_UPDATE_PROGRAMS_PVT, and MRP_CL_REFRESH_SNAPSHOT, and it references itself for internal reuse. Typical invocation occurs from Depot Repair forms, concurrent programs, and the public repair APIs that wrap it. Customizations should call the public APIs (such as CSD_REPAIRS_PUB) rather than this utility package, since its signatures are not guaranteed stable across releases.