Search Results alpha_prefix

Overview

ENG_AUTONUM_ALL_ORGS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ENG (Engineering) product module. Its documented purpose is to expose autonumbering information for all organizations, rather than for a specific organization. It accomplishes this by restricting the underlying engineering autonumbering table to rows where the ORGANIZATION_ID is null, which effectively represents the global or cross-organization autonumbering definition.

In the context of Oracle EBS 12.1.1 and 12.2.2, the view functions as a reporting and integration surface for the Engineering Change Number (ECN) autonumbering configuration. Rather than requiring a caller or report to filter the base table directly, the view already presents the "all organizations" subset, which simplifies queries and consistent consumption by forms, reports, and interfaces.

Underlying Base Objects

The view is defined over a single documented base object, ENG_AUTO_NUMBER_ECN, referenced through a synonym. Its defining text selects from this table (aliased EANE) with the predicate WHERE EANE.ORGANIZATION_ID IS NULL. Consequently, ENG_AUTONUM_ALL_ORGS_V returns only the rows of the base table that carry no organization identifier, which is the convention for defaults shared across all organizations.

Because it is a simple select view with no joins or aggregation, its behavior mirrors the base table exactly for the filtered subset. The set of columns it projects is identical to the base table, including the base table's ROWID surfaced as ROW_ID. Note that the view is a derived metadata object and inherits the base table's grants and access characteristics through APPS.

Key Columns

• ROW_ID — the ROWID of the underlying ENG_AUTO_NUMBER_ECN row, exposed as a stable identifier for the record.
• USER_ID — the user associated with the autonumbering configuration row.
• ORGANIZATION_ID — always null in this view by definition; its nullability distinguishes "all organizations" defaults from organization-specific rows.
• ALPHA_PREFIX — the alphabetic prefix applied to generated engineering change numbers; this is the column most directly relevant to the user's search for the prefix value.
• NEXT_AVAILABLE_NUMBER — the next numeric value to be assigned when the autonumbering mechanism generates a number.
• CHANGE_TYPE_ID — identifies the engineering change type to which the autonumbering rule applies.
• Audit and concurrency columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, tracking the request and program that last touched the row.

Common Use Cases and Queries

Typical uses include auditing the alphabetic prefix currently in force for all organizations, verifying the next available number before or after a number generation, and extracting the global ECN autonumbering configuration into external reporting or integration flows.

• Retrieve the global prefix and next number:

  SELECT alpha_prefix, next_available_number
  FROM   eng_autonum_all_orgs_v;

• Inspect rows by change type:

  SELECT change_type_id, alpha_prefix, next_available_number
  FROM   eng_autonum_all_orgs_v
  ORDER BY change_type_id;

• Audit who last maintained the configuration:

  SELECT last_updated_by, last_update_date, created_by, creation_date
  FROM   eng_autonum_all_orgs_v;

Because ORGANIZATION_ID is null for every row, callers should not expect organization-specific filtering from this view; queries that require a particular organization value must target the base table rather than this view. In practice it serves as the canonical source of shared autonumbering defaults across the enterprise.