Results for “cug_validate_address_pvt”
26 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 body within the Oracle E-Business Suite environment, operating under the APPS schema. As indicated by the "PVT" suffix in its name, this package is classified as a private API, meaning its procedures are intended for internal consumption by the corresponding public package (CUG_VALIDATE_ADDRESS_PUB) or other closely coupled components rather than being called directly by external integrations or end-user interfaces. The package header comment indicates a header revision dated 2006, with a note that the file was generated from a SQL Navigator template; this is consistent with in-house or CUG (Customer User Group) customizations common in earlier EBS releases.
The business function of this package centers on incident address validation. In service and telephony-oriented EBS deployments, incidents capture customer-reported problems, and the address associated with an incident must be verified for consistency and correctness before further processing. CUG_VALIDATE_ADDRESS_PVT exposes the validation logic that underpins that verification, returning a status that downstream code can use to accept, flag, or reject an incident address record.
Key Procedures and Functions
The documented metadata identifies two procedures:
- VALIDATE_INCIDENT_ADDRESS — Accepts an incident address record (a PL/SQL table type defined in the public package specification) along with the standard API parameter conventions. It inspects the validation_status attribute of the address record. Where the status is null or 'S', the procedure sets the return status to success; where the status is 'N', it returns an error status. This allows batch or transactional callers to determine programmatically whether an incident address passed validation.
- VALIDATE_INCIDENT_TYPE — The companion routine that performs validation connected to the incident type. The visible source excerpt shows the same API parameter signature style (api version, init message list, commit flag, incident type identifier, incident address record, and the standard OUT parameters for message count, message data, and return status), indicating it applies type-level validation to the incident address collection supplied by the caller.
Tables Accessed
The ETRM metadata documents a single referenced table via APPS synonyms: PLITBLM. This table is associated with the PL/SQL item-type infrastructure used in EBS forms, and its presence suggests that validation relies on reference or setup data held in that repository. No direct DML against core incident address tables appears in the documented excerpt; the package largely operates on the in-memory record collection passed by reference through the NOCOPY parameter convention, which keeps validation efficient by avoiding copy propagation overhead. Any persistence of validated addresses is therefore expected to be handled by the calling public API rather than by this private package body itself.
Usage Notes
Because this is a private (PVT) package, it is not intended to be invoked directly by forms, concurrent programs, or external custom code. The metadata records that it is referenced by one other package — almost certainly CUG_VALIDATE_ADDRESS_PUB — which acts as the public entry point. Typical invocation flows are: an Oracle Forms incident entry screen or a custom concurrent program calls the public wrapper, which in turn delegates to VALIDATE_INCIDENT_ADDRESS or VALIDATE_INCIDENT_TYPE here. Developers working with Oracle EBS 12.1.1 or 12.2.2 should call the public API, observe the standard FND_API return-status values (G_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXP_ERROR), and avoid referencing this package body directly, since private APIs may change without notice between patches.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
SYNONYM: PUBLIC.PLITBLM 12.1.1
-
SYNONYM: PUBLIC.PLITBLM 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1