Search Results process_zone




Overview
Explore in AI Chat

Overview

FTE_REGION_ZONE_LOADER is an Oracle E-Business Suite PL/SQL package owned by APPS that provides region and zone handling utilities for the R12 Bulk Loader used by Oracle Transportation Management / Freight and Trade Execution (FTE) functionality. Its header comment, sourced from FTERZLRS.pls (version 120.2.12000000.1, dated 2007/01/18), explicitly describes the package as containing "Zone and Region functions for R12 Bulk Loader." In EBS 12.1.1 and 12.2.2, the package therefore serves as a data-loading and lookup helper that bridges interface staging tables and the base region/zone master tables, allowing batch processes to resolve, create, and persist geographic regions and zones required for transportation lane and freight setup. The package is classified as an API of type OTHER in the ETRM documentation, indicating that it is a utility/loader package rather than a formal public business API. It defines two PL/SQL collection types at specification level: ZONE_RECORD, a record type containing an id and name, and ZONE_TABLE, a binary-integer-indexed table of ZONE_RECORD used to return lookup results.

Key Procedures and Functions

  • GET_NEXT_REGION_ID — Returns the next available region identifier for insertion, and returns -1 if an error occurs.
  • GET_REGION — A documented function concerned with retrieving region information; the specification excerpt lists it among the loader's region and zone accessors.
  • GET_REGION_ID — Returns a region identifier, supporting resolution of an existing region during load processing.
  • GET_ZONE_ID — Retrieves the region_id associated with a zone from the WSH_REGIONS_TL table. It accepts a zone name and an exact-match flag (per the header comment block, which references p_zone_name and p_exact_match). Where a match is found, the returned collection contains a single zone record with the name and id of the first match; where no match exists, the record is NULL.
  • ADD_ZONE — Adds a zone record, used when a zone referenced during loading does not yet exist.
  • INSERT_PARTY_REGION — Inserts a party-to-region association as part of region loading.
  • PROCESS_ZONE — Encapsulates zone-level processing logic invoked by the loader.
  • PROCESS_REGION — Encapsulates region-level processing logic invoked by the loader.
  • PROCESS_DATA — The top-level driver procedure that orchestrates region and zone processing for a load run.

Tables Accessed

The package operates against a set of region, zone, and lane tables accessed through APPS synonyms. Base and translated region data are held in WSH_REGIONS, WSH_REGIONS_S, and WSH_REGIONS_TL, with WSH_REGIONS_TL referenced specifically by the zone-lookup logic. Interface and staging tables include WSH_REGIONS_INTERFACE, WSH_REGIONS_INTERFACE_S, and WSH_REGIONS_TL_INTERFACE, which receive bulk-loaded region and zone data before validation and transfer to the base tables. Zone-to-region mapping is maintained in WSH_ZONE_REGIONS and WSH_ZONE_REGIONS_S. FTE_LANES is referenced for transportation lane context, DUAL supplies single-row utility queries, and PLITBLM is the standard EBS PL/SQL index-by table used for bulk operations and array processing.

Usage Notes

FTE_REGION_ZONE_LOADER is typically invoked during bulk loading of region and zone data rather than through an end-user form. The PROCESS_DATA entry point suggests execution from a concurrent program or batch driver that processes staged interface rows, resolves existing regions and zones via the GET_* functions, and creates missing ones through ADD_ZONE and INSERT_PARTY_REGION. The package is referenced by six other packages, confirming it is a shared low-level dependency called by higher-level loader and setup code. Because GET_NEXT_REGION_ID returns -1 on error, callers should check return values before inserting. Custom code invoking this package should treat it as an internal loader utility and validate that required interface and base-table data are staged before execution in both 12.1.1 and 12.2.2 environments.