Search Results get_rs_cust_sequence

Overview

CSP_PICK_UTILS is a VALID PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM API classification "OTHER." It belongs to the CSP (Spares Management, part of the Enterprise Asset Management / Service family) module and provides the underlying utility layer for pick-list processing and material movement within spare-parts and depot-repair flows. The package exposes 35 documented procedures and functions that cover the lifecycle of a pick — creation, confirmation, and persistence — alongside supporting logic for safety-stock calculation, min/max replenishment, service-level and factor derivation, and global organization context resolution.

In Oracle EBS 12.1.1 and 12.2.2, CSP_PICK_UTILS serves as a shared utility that other CSP packages and views call to build and manipulate pick-list and move-order data. Its dependency footprint is broad: it references FND_API and FND_PROFILE for error handling and profile-option retrieval, and the SYS.STANDARD package for base PL/SQL types. Within the CSP schema it is referenced by more than twenty objects, including CSP_AUTO_ASLMSL_PVT, CSP_SCH_INT_PVT, CSP_SHIP_TO_ADDRESS_PVT, and numerous views such as CSP_REQUIRED_PARTS_V, CSP_PACK_LIST_NAV, CSP_PLANNING_HEADERS_V, and CSP_REQ_LINE_DETAILS_V, confirming its role as a foundational, widely consumed utility.

Key Procedures and Functions

The documented callable units fall into several functional groups:

• Organization context: CSP_ASSIGN_GLOBAL_ORG_ID and CSP_GLOBAL_ORG_ID manage the global organization identifier used across the package's operations. CSP_PRODUCT_ORGANIZATION resolves the product organization context.
• Pick lifecycle: CREATE_PICK, CONFIRM_PICK, and SAVE_PICK form the core sequence for generating a pick, confirming it, and persisting the resulting records.
• Transaction and savepoint control: ISSUE_SAVEPOINT, ISSUE_ROLLBACK, and ISSUE_COMMIT encapsulate the transactional boundaries used while issuing material. UPDATE_MISC_MMTT manipulates the miscellaneous material transaction temporary structure.
• Min/max and safety-stock logic: CALCULATE_MIN_MAX, GET_MIN_QUANTITY, GET_MAX_QUANTITY, GET_SAFETY_FACTOR, GET_SAFETY_STOCK, GET_SERVICE_LEVEL, GET_EDQ_FACTOR, GET_ASL_FLAG, and GET_SAFETY_STOCK_FLAG provide the calculation and retrieval routines for replenishment parameters and approved-source-list flags.
• Customer sequencing: GET_RS_CUST_SEQUENCE returns the customer relationship sequence used to order pick-ticket or return-to-stock processing.

Tables Accessed

Through APPS synonyms, the package touches the following documented tables:

• CSP_MOVEORDER_HEADERS and CSP_MOVEORDER_LINES: move-order header and line records created or updated during pick processing.
• CSP_PICKLIST_HEADERS, CSP_PICKLIST_HEADERS_S1, CSP_PICKLIST_LINES, and CSP_PICKLIST_LINES_S1: pick-list header/line data and their sequences, central to CREATE_PICK, CONFIRM_PICK, and SAVE_PICK.
• CSP_RS_CUST_RELATIONS_S1: customer relationship sequence data supporting GET_RS_CUST_SEQUENCE.
• CSP_SAFETY_FACTORS: safety-factor values used by the safety-stock calculation routines.
• FND_LOOKUP_VALUES: lookup codes resolving configurable behavior and validation.
• JTF_TASK_ASSIGNMENTS: task assignment data associated with pick or service activity.
• MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_S, and MTL_MATERIAL_TRANSACTIONS_TEMP: inventory transaction records and the temporary staging structure used during issue processing and UPDATE_MISC_MMTT.
• MTL_PARAMETERS: organization-level inventory parameters supplying defaults.
• MTL_SERIAL_NUMBERS_TEMP: temporary serial-number data captured during material movement.

Usage Notes

CSP_PICK_UTILS is not intended as an end-user interface. It is invoked programmatically by other CSP packages (such as CSP_AUTO_ASLMSL_PVT, CSP_SCH_INT_PVT, and CSP_SHIP_TO_ADDRESS_PVT) and is exposed indirectly through the CSP views that reference it. Because it is referenced by 23 other packages and numerous views, changes to its logic can ripple across spares-management pick, planning, and required-parts screens. Custom code invoking these procedures should respect the package's savepoint, rollback, and commit conventions (ISSUE_SAVEPOINT, ISSUE_ROLLBACK, ISSUE_COMMIT) rather than managing transactions independently, and should supply the correct global organization context via CSP_ASSIGN_GLOBAL_ORG_ID. The package observes FND_API error-handling and FND_PROFILE profile-option conventions, so callers should follow standard EBS API exception-handling patterns. The metadata documents parameter signatures only partially; callers should obtain exact signatures from the EBS 12.1.1/12.2.2 database package specification before use.