Search Results cse_proj_item_in_srv_pkg




Overview
Explore in AI Chat

Overview

APPS.CSE_PROJ_ITEM_IN_SRV_PKG is a public PL/SQL package in Oracle E-Business Suite (12.1.1 and 12.2.2) that supports the Service (CSE) module's integration of project-related item and inventory transactions with Oracle Projects. Its central role is to receive service item attribute data originating from the field service or inventory workflow and route it into Oracle Projects as expenditure and cost distribution records. The package's documented procedure, INTERFACE_NL_TO_PA, exposes the "interface NL to PA" operation that application code or concurrent processing can invoke to move service transaction data into the Projects application schema.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than as the owner (APPS). This is significant for security and for grant management when custom code invokes the API. The header comment indicates the source file is CSEITSVS.pls and is maintained by Oracle development. A single packaged procedure, INTERFACE_NL_TO_PA, is documented, and the package is referenced by one other package, indicating a degree of internal reuse in the CSE stack.

Key Procedures and Functions

Only one procedure name is documented: INTERFACE_NL_TO_PA. It is provided as two overloaded signatures, distinguished by the type of the primary input parameter. Both overloads accept the service-to-Projects attribute data, an optional concurrent request identifier, and two output parameters reporting return status and an error message.

  • Scalar-record overload — accepts a single instance of the attribute record type (Proj_Itm_Insv_PA_ATTR_REC_TYPE) defined in CSE_DATASTRUCTURES_PUB, making it suitable for processing one service item/PA-attribute combination per call.
  • Table (collection) overload — accepts an attribute table type (Proj_Itm_Insv_PA_ATTR_TBL_TYPE), enabling bulk processing of many service-to-Projects attribute rows in a single invocation.
  • Common parameters — both overloads accept an optional concurrent request ID (p_conc_request_id, default NULL) and return x_return_status and x_error_message to communicate success or failure and diagnostic text.

The specific parameter lists must not be assumed beyond this structure; the public contract is limited to the two overloads described above.

Tables Accessed

The documented table references span the Service, Projects, and common modules. Projects-side tables include PA_TRANSACTION_INTERFACE_ALL, PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS_ALL, PA_COST_DISTRIBUTION_LINES_ALL, PA_PROJECTS_ALL, and PA_TASKS; these support staging, validation, and creation of project expenditures and distributions. Service and inventory infrastructure tables include CSI_PA_INTERFACE_S, CSI_TRANSACTIONS, CSI_A_LOCATIONS, HZ_LOCATIONS, and MTL_SYSTEM_ITEMS_KFV, providing source transaction, item, and location data. PLITBLM is an internal Oracle EBS table used in PL/SQL table processing contexts. Together these indicate the procedure reads service transaction and item/location details, then writes or stages corresponding Projects expenditure records.

Usage Notes

The procedure is typically invoked from Service module workflows, concurrent programs, or custom PL/SQL that needs to push field service item transactions into Oracle Projects. Because the package uses AUTHID CURRENT_USER, callers must hold appropriate privileges on the underlying tables and on the CSE_DATASTRUCTURES_PUB types. The optional p_conc_request_id allows callers running under a concurrent manager to associate processing with a request for logging and diagnostics. Callers should always inspect x_return_status and x_error_message; a failure return indicates the interface did not complete for the supplied record or set. The bulk table overload is preferable when processing multiple items to reduce context-switching overhead. Because the documented API surface is minimal, developers should confirm current behavior against the Oracle ETRM for the specific point release before relying on the package in custom integrations.