Results for “validate_geography_id”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
HZ_GEO_STRUCTURE_VALIDATE_PVT is a private (PVT) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides the server-side validation engine that supports the Geography Structure and Geography Hierarchy functionality within Oracle Trading Community Architecture (TCA). Its core purpose is to enforce referential integrity and uniqueness rules governing geography types, zones, geographies, and the relationships formed between them before those entities are written to the TCA model.
The package belongs to the Trading Community Architecture schema (HZ), and its private classification means it is intended primarily for consumption by sibling HZ packages that expose public geography-structure application programming interfaces rather than for direct invocation by external code. In the context of a search for validate_geography_type, this package is the object that contains the named procedure VALIDATE_GEOGRAPHY_TYPE, which validates a geography type against the unique-flag semantics of the geography model.
Key Procedures and Functions
The ETRM metadata documents five procedures in this package:
- VALIDATE_GEOGRAPHY_TYPE — Validates that a supplied geography type is consistent with the geography use flag. When the master reference flag is set, the procedure confirms that the geography type is designated for master reference use; otherwise it confirms general validity of the type. Failure raises the standard HZ_API_INVALID_FK message against the geography_type foreign key.
- VALIDATE_GEOGRAPHY_ID — Confirms that a supplied geography identifier references a valid, existing geography record prior to its use in a structure or relationship operation.
- VALIDATE_GEO_REL_TYPE — Validates the geography relationship type, ensuring that the relationship being established between geographies is permitted by the defined relationship-type metadata.
- VALIDATE_GEO_STRUCTURE — Validates the overall geography structure definition, checking that the hierarchy of geography types and their ordering conform to configured structural rules.
- VALIDATE_ZONE_TYPE — Validates a zone type against the geography model, ensuring zone definitions are consistent with the associated geography types.
Each procedure follows a consistent convention, accepting input parameters describing the entity under test and an IN OUT NOCOPY x_return_status parameter through which success or failure is communicated back to the caller.
Tables Accessed
The package reads from the following TCA tables through APPS synonyms:
- HZ_GEOGRAPHY_TYPES_B — The base table of geography type definitions; queried by VALIDATE_GEOGRAPHY_TYPE to confirm the existence and use classification of a geography type.
- HZ_GEOGRAPHIES — The geography master table; consulted to confirm that a referenced geography identifier exists.
- HZ_GEO_STRUCTURE_LEVELS — Defines permitted levels within a geography structure; used to validate structure composition and ordering.
- HZ_RELATIONSHIP_TYPES — Defines valid relationship types between geographies; used to validate geography relationship types.
- PLITBLM — A PL/SQL index-by table helper referenced in validation processing, typically for bulk membership or lookup handling.
Usage Notes
Because this package is classified as PVT, it is not intended as a public entry point. It is referenced by two other packages within the HZ schema, which act as the public-facing wrappers that invoke these validation routines during geography structure and hierarchy maintenance. In practice, the validations are triggered when administrators or applications define or modify geography types, geography structures, zones, and geography relationships — for example, through the Geography Hierarchy administrative forms in Oracle EBS, or through concurrent programs that seed and maintain TCA geography data.
Custom code should generally not call HZ_GEO_STRUCTURE_VALIDATE_PVT directly, as its signature and behavior are private and subject to change. Developers requiring equivalent validation should invoke the documented public HZ geography APIs, which internally delegate to this package. This preserves upgrade safety across 12.1.1 and 12.2.2, where the underlying validation logic remains encapsulated behind the public interface.