Search Results update_rma_ro_line_id

Overview

CSD_SOO_PVT is a private PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that implements the Service Order Orchestration (SOO) engine within the Enterprise Asset Management / Depot Repair and Service family of modules. Its central responsibility is to synchronize the transactional state of "source" business documents—service requests, service request tasks, purchase requisitions, internal requisitions, internal sales orders, RMAs, shipments, and deliveries—into the CSD_SO_ORCHESTRATION table and its associated Depot repair structures. In other words, the package acts as the orchestration driver that reads the current state of feeder transactions, determines what has changed, and merges or refreshes the corresponding orchestration records used by downstream Depot and Service processes.

A secondary responsibility is the maintenance of cross-reference identifiers. Through its global hashtables (g_updated_ids, g_rma_ro_line_ids, g_ship_ro_line_ids, g_int_order_header_ids) and their associated UPDATE_* routines, the package records the primary keys of rows affected by MERGE/UPDATE statements so that related Depot tables can be updated in the same logical unit of work. This gives the package the character of an internal orchestration engine rather than a user-facing API.

Key Procedures and Functions

• UPDATE_COUNT and GET_UPDATED_IDS — Maintenance of g_updated_ids; UPDATE_COUNT is invoked from MERGE...UPDATE SET statements to capture orchestration_id values, and GET_UPDATED_IDS returns the accumulated collection.
• UPDATE_RMA_RO_LINE_ID, UPDATE_SHIP_RO_LINE_ID, UPDATE_INT_ORDER_HEADER_ID — Populate the respective hashtables that track repair line IDs (RMA, RMA third party, Ship, Ship third party) and internal order header IDs requiring subsequent Depot updates.
• DEBUG — Logging/diagnostic helper for the orchestration run.
• GET_DOCUMENT_STATUS — Returns the status of an orchestration document for evaluation during refresh processing.
• REFRESH_JOB — Refreshes orchestration information associated with WIP/service jobs.
• REFRESH_SR and REFRESH_SR_TASK — Refresh orchestration records derived from service requests and their tasks.
• REFRESH_PURCHASE_REQ and REFRESH_INTERNAL_REQ — Refresh purchase requisition and internal requisition sources.
• REFRESH_INT_SALES_ORDER — Refresh internal sales order sources.
• REFRESH_RMA and REFRESH_RMA_THIRD_PARTY — Refresh RMA and third-party RMA sources.
• REFRESH_SHIP and REFRESH_SHIP_THIRD_PARTY — Refresh shipment and third-party shipment sources.
• REFRESH_DELIVERY — Refresh orchestration records for delivery transactions, aligning delivery state with orchestration data.
• REFRESH — The master refresh controller that sequences the individual REFRESH_* routines.
• SOO_DRIVER_MAIN — The top-level orchestration driver invoked to execute the full synchronization cycle.

Tables Accessed

• CSD_SO_ORCHESTRATION / CSD_SO_ORCHESTRATION_S1 — The primary orchestration table and its synonym, the principal target of MERGE/UPDATE refresh operations.
• CSD_REPAIRS, CSD_REPAIR_JOB_XREF, CSD_PRODUCT_TRANSACTIONS — Depot repair and product transaction data linked to orchestration records.
• CS_INCIDENTS_ALL_B, CS_INCIDENT_STATUSES, CS_ESTIMATE_DETAILS — Service request, status, and estimate detail sources used by the SR refresh routines.
• OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL — Sales order source data for internal sales order and RMA refresh.
• PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL — Purchase requisition source data.
• WIP_DISCRETE_JOBS, WIP_ENTITIES — Work-in-process job sources for REFRESH_JOB.
• FND_LOOKUP_VALUES — Reference lookup values for status mapping.

Usage Notes

CSD_SOO_PVT is classified as a PVT (private) package, meaning its interface is intended for internal consumption by other CSD/Depot components rather than direct customer calls. The ETRM metadata indicates it is referenced by one other package, which is the expected entry point for orchestration execution. In practice, SOO_DRIVER_MAIN is invoked from that calling component, a concurrent program, or a scheduled job to run a full refresh cycle, which then delegates to the individual REFRESH_* routines. REFRESH_DELIVERY and its sibling routines are not intended to be called independently from a form; they rely on shared global state (g_updated_ids and the ro_line_ids hashtables) whose lifecycle is managed by the driver. Custom code should therefore call the documented entry-point driver or the calling package rather than the individual refresh procedures directly, since invoking a leaf routine in isolation may leave the identifier-tracking collections incomplete and cause orphaned Depot updates.