Search Results get_fac_info




Overview
Explore in AI Chat

Overview

FTE_LOCATION_PARAMETERS_PKG is a public PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Freight and Transportation Management (FTE) module, part of the Oracle Transportation Management integration within EBS 12.1.1 and 12.2.2. Its central business purpose is the creation, registration, and retrieval of facility definitions tied to inventory and shipping locations. A "facility" in this context is the transportation-facing representation of a location — a distribution center, warehouse, supplier site, or customer site — for which freight calculation parameters, loading protocols, charge basis, handling time, currency, and unit-of-measure attributes must be maintained.

The package declares the AUTHID CURRENT_USER directive, meaning execution privileges are evaluated against the invoking schema. It defines several PL/SQL collection and record types, most notably TL_FAC_INFO_REC_TYPE, which models the full attribute set of a transportation facility (location and stop identifiers, facility code, loading protocol, charge basis, handling time, currency, modifier and price list identifiers, and weight, volume, distance, and time UOM class/unit pairs), and the associated associative array TL_FAC_INFO_TAB_TYPE. These types form the data contract for the package's retrieval and creation routines.

Key Procedures and Functions

  • Create_Facility — Creates a single transportation facility for a given location. It accepts a location identifier and an optional facility code, and returns a status and error message through its OUT parameters. This is the procedure most commonly sought by developers searching for "create_facility," and it is the atomic unit of facility registration from which the bulk variant is built.
  • Create_Facilities — The bulk counterpart, creating facilities for a set of locations. It consumes collections of location identifiers, company names, and site names (using types shared from WSH_LOCATIONS_PKG) and returns aggregate status and error information. This is the entry point used when onboarding many locations at once, such as during implementation or batch synchronization.
  • Get_Fac_Info — Populates an IN OUT collection of TL_FAC_INFO_REC_TYPE rows with the current transportation parameters for the requested facilities, returning status information. It is the primary read interface for exposing facility configuration to callers.
  • Get_Fac_Lat_Long_and_TimeZone — Resolves geographic attributes (latitude, longitude, and time zone) from address components such as country, city, postal code, state, county, and province. This supports distance-based freight calculation and scheduling logic that depends on accurate geolocation and time zone data.

Tables Accessed

The package reads and writes through APPS synonyms. FTE_LOCATION_PARAMETERS and FTE_LOCATION_PARAMETERS_S hold the core transportation facility parameter definitions and are the principal target of the create routines. FTE_PRC_PARAMETERS stores freight processing parameters. Location and party data are drawn from WSH_LOCATIONS, WSH_LOCATION_OWNERS, PO_LOCATION_ASSOCIATIONS_ALL, HR_ORGANIZATION_INFORMATION, MTL_PARAMETERS, HZ_PARTIES, HZ_PARTY_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_RELATIONSHIPS, supplying the address, organization, and trading-partner context needed to derive facility attributes. PLITBLM is an Oracle-supplied temporary/internal table used for collection processing. These references confirm that the package acts as a bridge between Oracle's location, party, and inventory models and the transportation parameter model.

Usage Notes

FTE_LOCATION_PARAMETERS_PKG is classified as an OTHER API and is referenced by two other packages, indicating it is invoked both directly and indirectly within the FTE stack. It is typically called from Freight and TransportationManagement setup forms when users register facilities against locations, from concurrent programs that batch-create or refresh facility data, and from custom PL/SQL that must provision transportation facilities during conversions or integrations with external transportation systems. Callers must inspect the x_return_status and x_error_msg OUT parameters after every invocation, since the procedures signal success and failure through these outputs rather than exceptions. Because parameters are passed using NOCOPY for large collections, callers should treat the IN OUT facility collection as modified in place. The optional facility code parameter on Create_Facility allows the calling process to control naming; when omitted, the package derives an appropriate code.