Results for “cug_validate_address_pub”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.CUG_VALIDATE_ADDRESS_PUB is a public PL/SQL package body in the Oracle E-Business Suite environment that supports address validation for incident records. The package resides in the APPS schema and is classified as a PUB (public) API, indicating that it is intended to be invoked by external callers rather than restricted to internal use. The header comment references a modification made to address Bug 2657648, in which the obsolete HZ_LOCATION_PUB API was replaced with HZ_LOCATION_V2PUB, reflecting the package's dependence on the Oracle Trading Community Architecture (TCA) location model for validating and persisting address information.
Functionally, the package validates incident-related address data associated with a given incident type. It accepts caller-supplied incident address records, applies validation logic, and returns status information through standard Oracle EBS API output parameters. The package follows the canonical PL/SQL API conventions of EBS, including the FND_API message-handling framework as evidenced by parameters such as p_init_msg_list, p_commit, x_msg_count, x_msg_data, x_return_status, and p_validation_level (defaulting to FND_API.G_VALID_LEVEL_FULL). This design allows callers to control transaction commit behavior and to receive structured error messages through the standard API messaging stack.
Key Procedures and Functions
The ETRM metadata documents two procedures exposed by the package:
- VALIDATE_INCIDENT_ADDRESS — The primary validation routine. It processes an incoming incident address record (of type CUG_VALIDATE_ADDRESS_PUB.INCIDENT_ADDRESS_TBL) and validates it against the underlying address model. The procedure accepts an API version, initialization and commit flags, and an incident type identifier, and returns message count, message data, and return status. Internally, the procedure navigates the collection of address records and, per the documented source, sets jurisdiction_status and validation_status to 'S' (success) for the first record. It invokes HZ_LOCATION_V2PUB for location handling, consistent with the TCA location API.
- VALIDATE_INCIDENT_TYPE — A companion validation procedure that verifies the incident type associated with the address validation request. This supports the package's prerequisite that the incident type be valid before address validation proceeds.
Both procedures adhere to EBS API standards, using NOCOPY for OUT parameters to improve performance and returning status via x_return_status.
Tables Accessed
ETRM documents one table referenced through APPS synonyms: PLITBLM. This table is accessed during the validation flow, most likely to retrieve or confirm reference data required for the incident address validation. The package also interacts indirectly with the TCA location model through HZ_LOCATION_V2PUB, which manages data in the HZ_LOCATIONS and related TCA tables. No direct DML against HZ tables is performed by this package; location persistence is delegated to the TCA public API.
Usage Notes
CUG_VALIDATE_ADDRESS_PUB is typically invoked from forms or custom code during incident entry and maintenance, where the incident address must be validated before being saved. It is referenced by three other packages in the ETRM environment, indicating that it acts as a shared validation service. Callers should provide a valid API version, appropriate commit flag, and the incident type and address data; they must then inspect x_return_status and the message stack before proceeding. The package's reliance on TCA location APIs means callers should ensure that the underlying location and party data is itself valid prior to invocation.
-
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.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1