Search Results delete_geo_struct_mapping

Overview

HZ_GEO_STRUCT_MAP_PUB is a public PL/SQL API package in the APPS schema that supports the geography structure mapping layer of Oracle E-Business Suite's Trading Community Architecture (TCA). Geography structure mapping defines how a geography model's hierarchical levels correspond to address validation rules, address styles, and territory usages. This package is one of the foundational components beneath the higher-level HZ_GEOGRAPHY_STRUCTURE_PUB package, which consumes its functionality to configure and maintain geography hierarchies used by Receivables, Order Management, and other modules that rely on geography-based validation and territory assignment.

The package is classified as PUB (public) in ETRM, indicating it is intended for supported external invocation rather than internal-only use. Its central role is to create, update, and remove the mappings between a geography structure and its associated levels, geography types, and address usage definitions.

Key Procedures and Functions

The package exposes four documented procedures:

• CREATE_GEO_STRUCT_MAPPING — Establishes a new mapping between a geography structure and the components that define its usable hierarchy. It serves as the primary entry point for building the structural relationship records consumed by downstream geography validation logic.
• DELETE_GEO_STRUCT_MAPPING — Removes an existing geography structure mapping, allowing obsolete or superseded structural definitions to be cleaned up without leaving orphaned detail records.
• CREATE_GEO_STRUCT_MAP_DTLS — Creates the detail rows associated with a geography structure map, typically defining how individual structure levels align with address usage columns or geography type attributes.
• UPDATE_GEO_STRUCT_MAP_DTLS — Modifies existing map detail rows, supporting maintenance of level-to-attribute associations after initial creation.

All four operate within the standard TCA API conventions, using FND_API for message handling and returning standard API result codes. Parameter lists are not reproduced here; refer to the package specification for exact signatures.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• HZ_GEO_STRUCT_MAP and HZ_GEO_STRUCT_MAP_DTL — the primary mapping header and detail tables that this API maintains.
• HZ_GEO_STRUCT_MAP_S — the sequence source used to generate primary keys for new map records.
• HZ_GEO_STRUCTURE_LEVELS — defines the levels within a geography structure that mappings reference.
• HZ_GEOGRAPHY_TYPES_B — supplies the geography type definitions against which mappings are validated.
• HZ_ADDRESS_USAGES and HZ_ADDRESS_USAGE_DTLS — provide address usage and usage detail context for the mapping.
• FND_TERRITORIES — validates territory assignments tied to the mapping.
• FND_TABLES and FND_COLUMNS — supply metadata used when validating column-level mapping targets.
• DUAL and PLITBLM — standard utility references used for scalar selection and PL/SQL table handling.

Usage Notes

HZ_GEO_STRUCT_MAP_PUB is invoked indirectly rather than directly by end users. Its documented referencers include HZ_GEOGRAPHY_STRUCTURE_PUB and the generated package wrapper HZ_GEO_STRUCT_MAP_PUB_W, which exposes the API to concurrent processing and forms-based invocation. Typical invocation paths include the Geography Hierarchy setup forms in Oracle Receivables and Order Management, concurrent programs performing geography structure maintenance, and custom TCA extensions that automate geography model deployment across environments.

Because it participates in TCA geography configuration, it should be called through the public API rather than by direct DML against HZ_GEO_STRUCT_MAP. Callers should honor the FND_API return status and follow commit or rollback handling appropriate to the calling context, as geography structure setup is typically transactional across multiple levels.