Search Results d_attribute10




Overview

APPS.INV_LOT_SERIAL_COLUMNS_V is a reporting and integration view in Oracle E-Business Suite that exposes the descriptive flexfield (DFF) column definitions associated with lot and serial number attributes. It serves as a metadata catalog: rather than storing transactional lot or serial data itself, the view describes which flexfield segments and database columns are available for capturing user-defined attributes on inventory lots and serial numbers. This makes it particularly useful for building dynamic reports, integration mappings, and user interfaces that must adapt to the configured DFF structure without hard-coding segment names.

The view was searched in the context of the token "d_attribute10," which is a standard descriptive flexfield attribute column. The view explicitly enumerates the D_ATTRIBUTE1 through D_ATTRIBUTE10 columns, confirming its role in surfacing these generic attribute slots alongside their end-user display names and the flexfield context under which they are enabled.

Underlying Base Objects

The documented base objects referenced by INV_LOT_SERIAL_COLUMNS_V are:

  • FND_DESCR_FLEX_COL_USAGE_VL (VIEW) — the descriptive flexfield column usage view from the Application Object Library (FND). This provides enabled segment-to-column mappings, end-user segment names, and the flexfield context code.
  • FND_TABLES (SYNONYM) — the FND table registry, used to identify the MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS tables and their table IDs.
  • FND_COLUMNS (SYNONYM) — the FND column registry, used to enumerate descriptive (type 'D') columns on the lot and serial number tables.

The view is a UNION of two branches. The first branch selects from FND_DESCR_FLEX_COL_USAGE_VL, filtered to application_id = 401 (Oracle Inventory), the descriptive flexfield names 'Lot Attributes' and 'Serial Attributes', enabled_flag = 'Y', and application_column_name restricted to D_ATTRIBUTE1 through D_ATTRIBUTE10. The DECODE assigns a query_for value of 'LOT' or 'SERIAL' depending on the flexfield name. The second branch joins FND_TABLES and FND_COLUMNS to list descriptive columns on MTL_LOT_NUMBERS and MTL_SERIAL_NUMBERS, excluding audit date columns and the ten D_ATTRIBUTE columns already handled, again tagging each row as 'LOT' or 'SERIAL'.

Key Columns

  • application_column_name — the underlying database column name (for example, D_ATTRIBUTE10) that stores the attribute value on the lot or serial table.
  • end_user_column_name — the user-facing segment name presented to the end user in the EBS forms and reports.
  • query_for — a derived discriminator returning 'LOT' or 'SERIAL' to indicate whether the row describes a lot attribute or a serial attribute.
  • descriptive_flex_context_code — the flexfield context code for the segment, indicating the context under which the attribute applies. For rows derived from the FND_TABLES/FND_COLUMNS branch, this value is a single space rather than a context code.

Common Use Cases and Queries

A frequent requirement is discovering which physical column stores a given user-facing lot attribute—critical when the DFF has been configured so that, for instance, "Expiry Date" maps to D_ATTRIBUTE10. The following query lists all lot and serial attribute columns:

  • SELECT query_for, application_column_name, end_user_column_name, descriptive_flex_context_code FROM apps.inv_lot_serial_columns_v ORDER BY query_for, application_column_name;

To locate the column behind a specific segment, filter on the end-user name:

  • SELECT application_column_name, query_for FROM apps.inv_lot_serial_columns_v WHERE end_user_column_name = :segment_name;

Because the view is driven entirely by FND flexfield setup, it automatically reflects configuration changes such as newly enabled segments or updated prompt text, which is why it is commonly referenced by custom concurrent programs, OAF pages, and integration extracts that must resolve lot and serial attributes dynamically at runtime rather than assuming a fixed column layout.