Search Results get_csp_acccount_id

Overview

CSP_REPAIR_PO_PVT is a private PL/SQL package in the APPS schema that belongs to the Oracle E-Business Suite depot repair and service logistics family of modules. In the Oracle EBS 12.1.1 and 12.2.2 releases, this package supports the repair order to purchasing integration, permitting a repair organization to generate purchasing documents — requisitions, purchase orders, and associated receipts — that are required to obtain parts, components, or outside repair services needed to fulfill a repair order. The package is classified as a "PVT" (private) API according to ETRM documentation, meaning its procedures are intended for internal invocation by other Oracle EBS program units rather than by external custom code. Its principal dependency is the FND_API package, which confirms that it follows the standard EBS API architecture with its conventions for message handling, error reporting, and commit control. The package is documented as being referenced by no other packages, and its only external referenced object of note is FND_API itself, underscoring its role as an internal implementation layer within the CSP (Service) schema lineage.

Key Procedures and Functions

ETRM documentation records three documented program units within this package:

• RUN_REPAIR_EXECUTION — The main driver procedure. It orchestrates the repair-related purchasing activity, coordinating the processing of repair order data against purchasing and work-in-process structures so that supply is created or adjusted in support of an active repair.
• REP_PO_SCRAP_ADJUST_TRANSACT — Handles scrap and adjustment transactions associated with repair purchase orders. This procedure addresses the return or write-off of material acquired against a repair PO and the corresponding transaction activity.
• GET_CSP_ACCCCOUNT_ID — A lookup function that resolves the applicable CSP account identifier used by the repair purchasing process, providing the account context needed for the transaction and costing logic executed by the other procedures.

Because the package is classified as a private API, parameter lists and call signatures are not published for external consumption. Consumers should not invoke these procedures directly; they are called by the repair purchasing infrastructure.

Tables Accessed

The package reads and writes across the full repair-to-procure data model. Repair order structures are represented by CSP_REPAIR_PO_HEADERS, CSP_REPAIR_PO_LINES, MTL_GENERIC_DISPOSITIONS, and MTL_SECONDARY_INVENTORIES, which hold the repair order header and line detail together with inventory disposition and subinventory information. Purchasing data is drawn from PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL, reflecting the purchase orders and schedules created or referenced for the repair. Requisition data is handled through PO_REQUISITIONS_INTERFACE_ALL, PO_REQUISITION_HEADERS_ALL, and PO_REQUISITION_LINES_ALL, supporting requisition creation and interface processing. Work-in-process integration uses WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_ENTITIES_S, and WIP_JOB_SCHEDULE_INTERFACE, reflecting the linkage between repair demand and discrete job or scheduling activity. Order management context is provided by OE_ORDER_HEADERS_ALL. Together these tables evidence a package that bridges depot repair, purchasing, inventory, and manufacturing within the EBS supply chain.

Usage Notes

CSP_REPAIR_PO_PVT is invoked internally rather than being exposed to end users directly. In typical execution, it is called from the repair order processing flow — often driven from the Depot Repair or Service Logistics forms and from concurrent programs that perform repair order execution and purchasing document creation. Its dependence on FND_API indicates that callers expect standard API error and message handling, and that the calling program is responsible for savepoint, commit, and rollback management. The presence of numerous WIP and purchasing interface tables further suggests concurrent program invocation, where repair supply is pushed into PO and WIP interface structures for downstream validation and processing. Customizations should not call this PVT package directly; supported extension points would instead use the public APIs in the same product family. When troubleshooting repair-to-PO supply issues in 12.1.1 or 12.2.2, this package and its referenced tables are relevant to diagnostics, but its private status means modification is not supported.