Results for “bis_fn_save_fields_v”

16 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIS_FN_SAVE_FIELDS_V is an Oracle E-Business Suite view owned by the APPS schema and delivered under the BIS (Applications BIS) product family. It presents configuration metadata that links Oracle EBS form functions to specific form fields and to the descriptive flexfield (DFF) attribute segments defined for those fields. In practice, the view answers the question: "for a given form function, which fields are enabled for save, and which flexfield attribute codes carry that data?"

The view has a documented status of VALID in ETRM 12.2.2 and is a reporting and integration surface rather than a transactional object. Because it joins function metadata to flexfield attribute metadata, it is commonly used when building extracts or diagnostics that need to reconcile form-function registration with attribute definitions without querying each underlying table separately.

Underlying Base Objects

The view text defines a three-way join over the following base objects:

Note that although AK_ATTRIBUTES_VL appears in the documented view text, no explicit join predicate linking A to S is shown in the excerpt; the DISTINCT operator is applied to suppress duplication arising from the joined set. ETRM lists no other documented referenced base objects beyond these three.

Key Columns

  • ROW_ID — the ROWID of the BIS_FN_SAVE_FIELDS row; useful for uniquely identifying a configuration record.
  • FUNCTION_ID — the surrogate key of the EBS form function, the principal join key across the view.
  • FIELD — the form field identifier that participates in the save configuration.
  • ATTRIBUTE_CODE — the flexfield attribute (segment) code associated with the field; exposed twice in the projection.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns inherited from BIS_FN_SAVE_FIELDS.
  • USER_FUNCTION_NAME, FUNCTION_DESCRIPTION — the user-facing function name and description from FND_FORM_FUNCTIONS_VL.
  • ATTRIBUTE_NAME — the descriptive attribute name for the associated attribute code.
  • APPLICATION_ID — the application owning the function.

Common Use Cases and Queries

Typical uses include auditing which form functions have save fields configured, mapping function names to flexfield attribute codes for integration or data migration, and troubleshooting missing attribute values on a form.

  • List all configured fields for a given function:
SELECT function_id, user_function_name, field, attribute_code
FROM   apps.bis_fn_save_fields_v
WHERE  user_function_name LIKE 'XX%'
ORDER BY user_function_name, field;
  • Locate the attribute name behind a field:
SELECT field, attribute_code, attribute_name
FROM   apps.bis_fn_save_fields_v
WHERE  function_id = :p_function_id;
  • Audit recently changed configurations using the WHO columns:
SELECT user_function_name, field, attribute_code, last_update_date, last_updated_by
FROM   apps.bis_fn_save_fields_v
WHERE  last_update_date >= SYSDATE - 30;

Because the view returns DISTINCT rows and joins multilingual (VL) objects, queries should filter on FUNCTION_ID or name rather than relying on row counts. All access should be granted through the APPS schema or a custom synonym.