Results for “validate_incident_address”

24 results




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

Overview

APPS.CUG_VALIDATE_ADDRESS_PVT is a private PL/SQL package deployed in the Oracle E-Business Suite Applications (APPS) schema. The _PVT suffix indicates that this is an internal, private implementation package; it is not intended to be called directly by external or customer-written code. Its public-facing counterpart, CUG_VALIDATE_ADDRESS_PUB, exposes the supported API surface, while the PVT package encapsulates the actual validation logic and is invoked by the public layer (and by one additional package, per the documented dependency).

The package operates in the Service / Telecommunications industry vertical context, evidenced by the CUG prefix and the incident-address terminology. Its business purpose is to validate address information and incident-type data associated with customer incidents — records that capture dispatch, service request, or location details. The package supports the Oracle EBS address verification workflow by checking that incident addresses and incident types conform to expected rules before persistence. The AUTHID CURRENT_USER declaration means the package executes with the privileges of the calling user rather than the defining user, which is relevant for security and synonym resolution. The header comments indicate the source was generated from a SQL Navigator template in 2006 and carries a "noship" designation, meaning it is not shipped as a standalone patchable object but is delivered as part of the broader product family.

Key Procedures and Functions

  • VALIDATE_INCIDENT_ADDRESS — Validates the address data associated with an incident. It accepts the standard Oracle EBS API parameter conventions (API version, message list initialization, commit flag, incident type identifier, an incident address record passed IN OUT NOCOPY, and output parameters for message count, message data, and return status, plus a validation level). The procedure inspects and enforces address-level rules and reports outcome through the standard FND_API return-status mechanism.
  • VALIDATE_INCIDENT_TYPE — Validates the incident type in relation to the supplied incident address record. It shares the same parameter profile as VALIDATE_INCIDENT_ADDRESS, including the incident type ID, the IN OUT NOCOPY incident address table, and the standard output and validation-level parameters. This procedure ensures the incident type is consistent with the address data being processed.

Both procedures follow the standard EBS API signature pattern, using FND_API.G_FALSE defaults and FND_API.G_VALID_LEVEL_FULL as the default validation level, which confirms conformance to Oracle's public API design standards.

Tables Accessed

The documented table reference is PLITBLM, accessed through an APPS synonym. PLITBLM is the Oracle EBS table that stores temporary or staging validation messages and address validation results — commonly used in address verification scenarios to hold intermediate message text and error rows during a validation session. The package reads and writes this table to record validation findings, which are subsequently retrieved by callers via the standard message-handling API (FND_MSG_PUB). No other base tables are documented as directly referenced by this package.

Usage Notes

Because this is a private (_PVT) package, it should not be invoked directly from forms, concurrent programs, or custom code. Instead, callers interact with the public API layer (CUG_VALIDATE_ADDRESS_PUB), which in turn delegates to the private procedures. In the context of the user's search term "avs address verification services private limited," the package relates to address verification (AVS) functionality within EBS, but the "Private" naming reflects the PL/SQL access modifier, not a specific vendor entity. Typical invocation paths include:

  • Oracle Forms or OAF pages in the service/telecom incident entry flow, which call the public wrapper during record validation.
  • Concurrent programs or batch processes that validate batches of incident addresses.
  • Other PL/SQL packages — one additional package is documented as referencing this one.

When customizing, always target the public package and treat CUG_VALIDATE_ADDRESS_PVT as subject to change without notice, consistent with its private classification and "noship" header designation.