Search Results read_table_attributes




Overview
Explore in AI Chat

Overview

WSH_FLEXFIELD_UTILS is an Oracle Shipping (WSH) utility package that manages descriptive flexfield (DFF) processing for shipping-related entities. It is owned by the APPS schema and is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the calling user rather than the definer. This design allows the package to be invoked safely from forms, concurrent programs, and custom code that operate under varying privilege models while relying on APPS synonyms to resolve underlying tables.

The package provides a centralized mechanism to read, cache, default, and validate descriptive flexfield segments associated with shipping transactions. The ETRM metadata classifies it as an API of type OTHER, indicating it is a supporting infrastructure package rather than a primary public application programming interface. The 12.2.2 documentation lists six documented routines: CACHE_DFF_SEGMENTS, GET_DFF_DEFAULTS, WRITE_DFF_ATTRIBUTES, READ_TABLE_ATTRIBUTES, VALIDATE_DFF, and GET_FLEXFIELD. The source header references version 120.0, last modified in May 2005, reflecting that the package has remained stable across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

  • CACHE_DFF_Segments — Retrieves and caches the segments of a specified descriptive flexfield. Per the source comments, it currently accepts only wsh_new_deliveries as input, with extension planned for wsh_trips and wsh_trip_stops. It is documented as a function that returns a binary integer status and reports an out status parameter. This is the routine most commonly associated with the search term "cache_dff_segments."
  • GET_DFF_Defaults — Retrieves the default context and segment values for a given flexfield. Like CACHE_DFF_SEGMENTS, it initially supports only wsh_new_deliveries.
  • WRITE_DFF_ATTRIBUTES — Persists flexfield attribute values, presumably writing segment values to the appropriate DFF columns.
  • READ_TABLE_ATTRIBUTES — Reads the attribute values associated with a given table, supplying the data needed to populate or compare flexfield content.
  • VALIDATE_DFF — Performs validation of descriptive flexfield values against segment definitions and value sets.
  • GET_FLEXFIELD — Returns flexfield metadata, consistent with the DFLEX_DR record type declared in the package specification, which captures the title, table name, description, segment delimiter, default context field, default context value, protected flag, context prompt, and context column name.

No parameter lists are documented in the ETRM excerpt beyond the CACHE_DFF_SEGMENTS signature, and none are asserted here.

Tables Accessed

The package references the following tables through APPS synonyms:

  • FND_APPLICATION — Used to resolve the application short name for the flexfield's owning application, as reflected in the DFLEX_DR record type's table_app field.
  • WSH_NEW_DELIVERIES — The primary entity whose descriptive flexfield segments are cached and defaulted; the documentation explicitly limits current support to this table.
  • WSH_DELIVERY_DETAILS — Delivery detail records associated with the shipping flexfield context.
  • WSH_TRIPS — Trip records referenced in the planned extension of the caching and defaulting routines.
  • PLITBLM — The Oracle Forms PL/SQL table interface used to pass tabular data between the database package and the calling form.

Usage Notes

WSH_FLEXFIELD_UTILS is referenced by six other packages within the EBS code base, indicating its role as shared infrastructure for shipping flexfield handling. It is typically invoked from Oracle Forms attached to shipping windows, where PLITBLM mediates the transfer of segment arrays, and from concurrent programs or custom extensions that need to pre-cache or validate DFF segment values for deliveries. Because the package is AUTHID CURRENT_USER, custom code invoking it must execute under a schema with the necessary grants on the APPS synonyms. Developers extending shipping functionality should call the documented routines rather than querying DFF tables directly, to preserve cache consistency and default-value behavior.