Search Results csptrreq_fm_order

Overview

CSP_PARTS_REQUIREMENT is the Oracle E-Business Suite package responsible for creating, updating, and cancelling parts requirements for spares within the Depot Repair and field service flow. Defined with AUTHID CURRENT_USER in the APPS schema, the package acts as the programmatic backbone that converts a service-driven demand signal into a formal internal requisition and, where appropriate, a replenishment order. Its header comments state the purpose plainly: to create, update, and cancel parts requirements for spares.

The package belongs to the CSP (spares) module family and ties a service incident or repair order to a supply chain requisition. It bridges service-side entities such as incidents, tasks, and resources to inventory and purchasing structures including requisition headers, requisition lines, destination subinventories, and ship-to locations. In release 12.1.1 and 12.2.2 the package retains the same public contract, with a documented API classification of OTHER and no fewer than fourteen callable procedures and functions. It is referenced by seventeen other packages, indicating that it functions as a shared dependency rather than a standalone utility.

Key Procedures and Functions

The documented entry points cover the full lifecycle of a spare-parts requirement:

• PROCESS_REQUIREMENT — the principal driver that accepts requirement data and orchestrates creation, update, or cancellation of the parts requirement.
• CSPTRREQ_FM_ORDER and CSPTRREQ_ORDER_RES — order-facing routines that support the flow of a requirement into an order and its associated resource context.
• CREATE_ORDER — generates the internal order or requisition document resulting from an approved requirement.
• CHECK_AVAILABILITY — validates whether the requested spare is available before the requirement is committed.
• GET_SOURCE_ORGANIZATION — resolves the supplying organization from which the spare should be sourced.
• SAVE_RQMT_LINE and DELETE_RQMT_LINE — persist or remove individual requirement line records.
• DELETE_RQMT_HEADER — removes the parent requirement header and its dependent data.
• TASK_ASSIGNMENT_PRE_INSERT, TASK_ASSIGNMENT_POST_INSERT, TASK_ASSIGNMENT_PRE_UPDATE, TASK_ASSIGNMENT_POST_UPDATE, and TASK_ASSIGNMENT_PRE_DELETE — table-handler style hooks that enforce validation and side effects around task assignment DML.
• GET_RESOURCE_SHIFT_END — retrieves the end of a resource shift, typically used to derive default need-by dates.

Tables Accessed

The package reads and writes the core requirement tables CSP_REQUIREMENT_HEADERS, CSP_REQUIREMENT_LINES, CSP_REQ_LINE_DETAILS, and its sequence table CSP_REQ_LINE_DETAILS_S1. Sourcing and location logic draws on CSP_INV_LOC_ASSIGNMENTS. Customer and site information for ship-to resolution comes from HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, and HZ_LOCATIONS, with responsibility links in CSP_RS_CUST_RELATIONS. Service context is supplied by CS_INCIDENTS_ALL_B and JTF_RS_RESOURCE_EXTNS, while HR_ALL_ORGANIZATION_UNITS supports organization validation.

Usage Notes

CSP_PARTS_REQUIREMENT is typically invoked from Depot Repair and spares forms, from concurrent programs that batch-process requirements, and from custom extensions that need to raise or cancel spare-parts demand programmatically. The ship_complete search term reflects a common operational concern: ensuring a requirement ships in full rather than partially, which depends on the availability check and sourcing routines above. Callers should supply the Header_Rec_Type and Line_Rec_Type structures, populate mandatory destination and item attributes, and expect the package to derive need-by dates from resource shift data where not explicitly provided.