Results for “csd_refurbish_iro_grp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.CSD_REFURBISH_IRO_GRP package is a Group (GRP) API within the Oracle E-Business Suite Depot Repair and Service (CSD) module. Its business function is to automate the creation of internal repair orders (IROs) that originate from internal sales orders and requisitions, and to resolve the relationship between customer site use records and their underlying Trading Community Architecture (TCA) party, party site, and party site use identifiers. In the telecommunications and high-technology service industries, the concept of a "refit order" (also referred to as a refurbishment or repair order) describes the work authorization that returns a customer-owned or internally owned asset to a serviceable condition. This package provides the programmatic backbone that lets depot repair operations convert an internal sales order or requisition into a formal service request and the associated repair orders, thereby supporting asset refurbishment, warranty repair, and return-to-service workflows.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer, which is consistent with standard Oracle EBS API security practice for packages invoked from forms, concurrent programs, and integration code.

Key Procedures and Functions

The package exposes two documented procedures:

• GET_PARTYSITEID — Accepts a customer site use identifier and a site use type (for example, To_Ship or To_Bill) as input and returns the corresponding party identifier, party site identifier, and party site use identifier. Standard return status, message data, and message count OUT parameters are provided for error handling. This procedure supplies the TCA addressing context required before a repair order can be raised against a customer or internal party.
• CREATE_INTERNALRO — Takes internal sales order header and requisition header identifiers as input, creates a service request, and returns the service request number along with the output internal sales order header and requisition header identifiers. If the item on the internal sales order is non-serialized, a single repair order is created beneath the service request. If the item is serialized, one repair order is created for each unit of ordered quantity. On failure, an error code and message are returned and all database transactions are rolled back, preserving transactional integrity.

Tables Accessed

The package reads and writes across several EBS schemas through APPS synonyms. Service and repair data is held in CSD_PRODUCT_TRANSACTIONS, CSD_REPAIRS, and CS_INCIDENTS_ALL_B. Customer and party information is drawn from the TCA tables HZ_PARTIES, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_LOCATIONS. Item validation relies on MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV. The order and requisition documents are sourced from OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and PO_REQUISITION_HEADERS_ALL.

Usage Notes

This package is typically invoked from Depot Repair forms, service request workflows, and custom PL/SQL integration code that bridges order management and depot repair. It is referenced by two other packages, indicating its role as a reusable building block in the refurbishment process chain. Developers implementing telecom or high-tech repair flows should call CREATE_INTERNALRO after the internal sales order or requisition has been booked, and use GET_PARTYSITEID when the correct TCA address context must be derived from a customer site use record. Standard return status parameters must be checked after each call, and callers should note that CREATE_INTERNALRO performs an all-or-nothing commit strategy, rolling back on error.