Results for “validate_incident_type”
24 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.CUG_VALIDATE_TYPE_PKG is a server-side PL/SQL package body belonging to the Oracle EBS customer relationship management and telephony integration layer, commonly associated with the Computer Telephony Integration (CTI) and Universal Gateway (CUG) modules. The package exists to perform validation of incident-related data structures prior to persistence or downstream processing. The package body carries the standard SQL Navigator header against the source file CUGVTPIB.pls (version 115.2, dated 2002/12/04), indicating that it is a long-standing seeded object that has remained stable across releases. In the context of Oracle EBS 12.1.1 and 12.2.2, it functions as a validation utility invoked before the creation or update of an incident record whose type and address context must be checked against jurisdiction rules.
The overriding business purpose is to determine whether a supplied incident type, combined with its associated incident address collection, satisfies the applicable validation and jurisdiction requirements. The package returns a standardized API return status so that calling code can branch on success, error, or unexpected conditions without parsing exception text.
Key Procedures and Functions
The documented interface exposes a single public program unit, VALIDATE_INCIDENT_TYPE. Its documented role is to accept an incident type identifier together with an incident address collection and evaluate the jurisdiction status associated with that address data. Rather than inventing a parameter list, the essential behavior may be described as follows: the procedure initializes the first entry in the incident address record, defaulting both the validation status and jurisdiction status to the success indicator 'S'. It then tests whether the jurisdiction status is null or equal to 'S'. If so, it sets the API return status to FND_API.G_RET_STS_SUCCESS. Otherwise, it marks both the validation status and jurisdiction status as 'F' (failed) and sets the API return status to FND_API.G_RET_STS_ERROR.
The procedure conforms to the Oracle Application Object Library API conventions, honoring p_api_version, p_init_msg_list, p_commit, x_msg_count, x_msg_data, x_return_status, and p_validation_level. These parameters follow the standard FND_API contract, allowing the caller to request message list initialization and to retrieve error diagnostics. No additional documented functions are exposed, and the package body contains no private helper routines beyond the single validation procedure.
Tables Accessed
Per the documented ETRM metadata, the package references one table via an APPS synonym: PLITBLM. This table is used in the validation path to support the incident type and jurisdiction lookup logic. The package writes only to its OUT and IN OUT parameters; it does not directly perform transactional DML against the incident tables shown in the procedure signature. Because the signature declares the incident address parameter as an IN OUT NOCOPY collection, the procedure mutates the caller's collection in place, adjusting the validation_status and jurisdiction_status attributes so the caller retains the evaluated result.
Usage Notes
CUG_VALIDATE_TYPE_PKG is typically invoked from form-level or server-side code that precedes incident creation or update in the CTI/Universal Gateway flow. The metadata records that it is referenced by one other package, meaning it is consumed as a subordinate validation routine rather than called directly by end users. In practice, the invoking package calls VALIDATE_INCIDENT_TYPE during pre-insert or pre-update validation triggered by an Oracle Forms block, a concurrent program, or custom PL/SQL that must confirm the incident type before committing the record.
Because the procedure follows the FND_API standard, callers should check x_return_status after invocation and inspect x_msg_count and x_msg_data when the status is not success. The jurisdiction_status and validation_status flags in the incident address collection provide an additional, record-level indication of which entries failed. In Oracle EBS 12.1.1 and 12.2.2 the package remains compatible with the online patching model used by 12.2, as it is a seeded APPS-owned body with no direct DDL. Developers extending validation logic should do so through wrapper code rather than modifying this package, since customizations to seeded package bodies are overwritten during patching and can invalidate dependent objects.