Search Results one_repair

Overview

The APPS.CSD_RO_BULLETINS_PVT package is a private (PVT) PL/SQL API that belongs to the Oracle E-Business Suite Depot Repair / Service functionality, specifically the Component Service Data (CSD) schema. It governs the relationship between bulletin records and Repair Orders (RO). A bulletin is a service communication issued by a manufacturer or supplier — for example a safety notice or mandatory part-replacement instruction — that must be applied to specific repair lines. This package encapsulates the business logic used to create, update, delete, and lock the association between repairs and bulletins, including the linking of bulletins to repair orders and service codes.

The package was authored in January 2008 (signature csdvrobs.pls 120.2.12010000.2) and is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user. It defines a public constant API version G_L_API_VERSION_NUMBER := 1.0, along with supporting constants that identify source type 'RULE', frequency codes ONE_REPAIR and ONE_INSTANCE, and a default fetch size of 30 records per call. It also declares the PL/SQL collection type CSD_RO_SC_IDS_TBL_TYPE (a table of numbers indexed by binary integer) and the record type RO_BULLETIN_REC_TYPE, which mirrors the columns of the underlying CSD_RO_BULLETINS entity with FND_API.G_MISS defaulting for the standard API convention.

Key Procedures and Functions

• CREATE_RO_BULLETIN — Creates a new repair-order bulletin link record, establishing the association between a repair line and a bulletin.
• UPDATE_RO_BULLETIN — Modifies an existing repair-order bulletin association, such as updating view status or source information.
• DELETE_RO_BULLETIN — Removes an existing repair-order bulletin link.
• LOCK_RO_BULLETIN — Obtains a locking handle on a bulletin link record to support concurrency control during update or delete operations.
• LINK_BULLETINS_TO_RO — Associates one or more bulletins with a repair order, applying the applicable bulletins in bulk.
• CREATE_NEW_RO_BULLETIN_LINK — Constructs and persists a new link between a repair order and a bulletin.
• GET_CSD_REPAIRS_OBJ_VER_NUM — Retrieves the object version number for a CSD repair record, used for optimistic locking checks.
• LINK_BULLETINS_TO_REPAIRS_CP — A concurrent-program oriented wrapper that links bulletins to repair lines in a set-based batch process.
• LINK_BULLETIN_FOR_RULE — Links a bulletin to a repair based on a defined rule. This is the routine users reach when searching for "link_bulletin_for_rule" and is the primary entry point for rule-driven bulletin application.
• APPLY_BULLETIN_SCS_TO_RO — Applies the service codes (CSD_BULLETIN_SCS) attached to a bulletin onto a repair order, propagating the repair actions dictated by the bulletin.

Tables Accessed

• CSD_RO_BULLETINS — The central intersection table holding repair-order-to-bulletin links; primary read/write target.
• CSD_BULLETINS_B — The bulletin base table, source of bulletin definitions and identifiers.
• CSD_BULLETIN_SCS — Bulletin service codes defining the repair actions associated with each bulletin.
• CSD_REPAIRS — Repair line records to which bulletins are linked.
• CSD_RO_SERVICE_CODES — Service codes recorded against a repair order; populated when bulletins are applied.
• CSD_RULES_B — Rule definitions used by LINK_BULLETIN_FOR_RULE to determine which bulletins apply.
• CSD_WF_ITEM_KEY_S — Workflow item key sequence, supporting workflow integration.
• DUAL and PLITBLM — Utility references (PLITBLM is the standard PL/SQL indexed-table helper).

Usage Notes

Because this package is classified PVT (private), it is not intended as a public integration API. It is referenced directly by seven other packages within the CSD schema, which orchestrate repair-order bulletin processing. Typical invocation paths include Depot Repair forms that maintain repair orders and their applicable bulletins, concurrent programs that link bulletins across repair populations using LINK_BULLETINS_TO_REPAIRS_CP, and rule-driven flows that automatically apply bulletins where a matching condition exists. All calls must respect standard EBS API conventions: callers should supply FND_API.G_MISS for unspecified fields, pass the correct G_L_API_VERSION_NUMBER, and check the returned x_return_status/message stack. Optimistic locking is enforced through object version numbers, with LOCK_RO_BULLETIN and GET_CSD_REPAIRS_OBJ_VER_NUM supporting concurrency safety. Custom code should generally call the public wrapper packages rather than this private API directly.