Search Results cs_sr_preferred_lang_pub

Overview

The APPS.CS_SR_PREFERRED_LANG_PUB package is a public PL/SQL API in Oracle EBS 12.1.1 and 12.2.2 that exposes business logic for maintaining a service request's preferred language attribute. It follows the standard published API pattern used throughout Oracle's Customer Service (CS) and Depot Repair modules, delegating its actual processing to the companion private package CS_SR_PREFERRED_LANG_PVT. The "_PUB" suffix denotes that the package is intended for external invocation by forms, concurrent programs, or customer extensions, while the PVT package holds the implementation logic and record type definitions.

The package is declared with the standard API constants G_PKG_NAME (set to the string 'CS_SR_Preferred_Lang_PUB') and G_INITIALIZED (set to 'R'), which the underlying PVT package uses to signal initialization state. It defines a private record type, preferred_language_rec_type, owned by CS_SR_Preferred_Lang_PVT, which carries the preferred-language data between the caller and the API layer.

Key Procedures and Functions

ETRM documents three procedures in this package:

• INITIALIZE_REC — Initializes an IN OUT NOCOPY parameter of type CS_SR_Preferred_Lang_PVT.preferred_language_rec_type to a clean null/default state. It takes a single preferred_language_record parameter and simply forwards the call to the PVT package's same-named routine. This procedure is typically called by callers before populating a record for a Create or Update call, ensuring no stale field values are carried over.
• CREATE_PREFERRED_LANGUAGE — Creates a new preferred-language association. It uses the standard EBS API parameter convention: p_api_version, p_init_msg_list, p_commit, the output trio x_return_status/x_msg_count/x_msg_data, plus responsibility and user context parameters (p_resp_appl_id, p_resp_id, p_user_id, p_login_id) and the input record p_preferred_language_rec. The body declares a local API version constant of 1.0 and a local full API name for error reporting, copies the caller's record into a local variable, and begins a SAVE POINT (documented in the excerpt at line 58) before delegating to the PVT implementation.
• UPDATE_PREFERRED_LANGUAGE — The counterpart procedure for modifying an existing preferred-language record. It follows the same API parameter conventions as the Create procedure and is likewise implemented by delegating to CS_SR_PREFERRED_LANG_PVT.

No functions are documented; all three entries are procedures.

Tables Accessed

The ETRM metadata does not list any base tables referenced directly through APPS synonyms by CS_SR_PREFERRED_LANG_PUB. Because the public package is a thin wrapper, the actual DML against the preferred-language storage table (CS_SR_PREFERRED_LANG, or the relevant CS service-request language table) is performed inside CS_SR_PREFERRED_LANG_PVT. This layering keeps the public interface stable while the private package owns the INSERT, UPDATE, and lookup logic. Callers should therefore treat the PUB package as the supported entry point and avoid referencing the PVT package directly.

Usage Notes

CS_SR_PREFERRED_LANG_PUB is invoked when an application needs to persist or initialize a preferred language for a service request record. Typical callers include the Service Request forms in the Customer Service module, concurrent programs that bulk-update service request attributes, and custom extensions that must set a preferred language programmatically. Callers should supply p_api_version matching the declared 1.0, initialize the record via INITIALIZE_REC before setting fields, and inspect x_return_status against FND_API.G_RET_STS_SUCCESS. Because the package is documented as being referenced by zero other packages, it is unlikely to be consumed internally by other Oracle APIs; its contract is primarily for external and form-based invocation. ETRM records the last source revision at version 115.4 (2002/11/30), so the object is stable and unchanged across 12.1.1 and 12.2.2.