Search Results eng_list




Overview

APPS.WF_ENG_LIST_ROLES is a reporting view in the Oracle E-Business Suite that exposes Engineering Change Order (ECO) approval list definitions in a format compatible with the Oracle Workflow directory services model. The view name suggests a mapping between Workflow role/approver resolution and the Engineering Change Management approval lists stored in ENG_ECN_APPROVAL_LISTS. Rather than functioning as a transactional entity, it acts as an integration and reporting surface, allowing the Workflow engine — or custom reporting code — to enumerate the approval lists defined for engineering changes as though they were directory roles.

The view is owned by APPS and is available in both EBS 12.1.1 and 12.2.2. Its defining query returns a single row per engineering approval list, projecting list identity, description, and a set of literal and NULL placeholders that conform to the column shape expected by the Workflow directory/role-listing interface. This design makes it a bridge between the Engineering module's approval configuration and Workflow's role resolution facility.

Underlying Base Objects

The metadata documents exactly one referenced base object: the synonym ENG_ECN_APPROVAL_LISTS, which resolves to the Engineering Change Management approval list table owned by the Engineering schema. The view is defined with a simple, non-joining SELECT — there are no outer joins, aggregations, or additional lookups in the documented view text. Consequently, the relationship is strictly one-to-one: every row in ENG_ECN_APPROVAL_LISTS produces exactly one row in WF_ENG_LIST_ROLES.

Because the dependency is limited to a single table, the view is lightweight and its performance characteristics are governed almost entirely by the selectivity of the underlying approval list table, which is typically small to moderate in volume.

Key Columns

  • Role identifier (column 1): A concatenation of the literal 'ENG_LIST', a colon, and approval_list_id. This produces a namespaced key such as ENG_LIST:1234 that uniquely identifies the approval list within the Workflow role namespace and separates engineering lists from other role sources.
  • Name (column 2): approval_list_name from the base table — the display name of the approval list.
  • Description (column 3): description from the base table — optional descriptive text for the list.
  • Type discriminator (column 4): The literal 'QUERY', indicating the role resolution mechanism is query-based rather than explicitly enumerated.
  • Null placeholders (columns 5–8): Returned as NULL, occupying positional slots required by the consuming Workflow interface.
  • Source tag (column 9): The literal 'ENG_LIST', echoing the source system classification.
  • Identifier (column 10): approval_list_id, the numeric primary key of the underlying list.
  • Date and status columns (columns 11–14): Date values are returned as NULL via TO_DATE(NULL), and the status column carries the literal 'ACTIVE', marking every list as available for use.
  • Flag and ordinal columns (columns 15–16): A literal 'N' and a constant 7, which serve as interface control values and sort/type ordinals respectively.

Common Use Cases and Queries

Typical applications include validating approval list availability before submitting an ECO, driving reports of configured engineering approvers, and supporting Workflow integrations that need to present engineering lists as resolvable roles.

  • List all active engineering approval lists: SELECT role_id, name FROM apps.wf_eng_list_roles ORDER BY name;
  • Retrieve a specific list by its key or identifier: SELECT * FROM apps.wf_eng_list_roles WHERE role_id = 'ENG_LIST:1234'; or WHERE approval_list_id = 1234;
  • Search by name fragment for reporting: SELECT approval_list_id, name, description FROM apps.wf_eng_list_roles WHERE UPPER(name) LIKE '%CHANGE%';

Because the view performs no joins, these queries execute efficiently and can be embedded safely in concurrent programs, BI Publisher data models, and custom Workflow role-resolution routines.