Results for “as_changed_territories”

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

Overview

AS_CHANGED_TERRITORIES is a Sales Foundation (AS) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes changed territory records in a multi-org context. The ETRM metadata classifies the object as Obsolete, and the "Implementation/DBA Data" section explicitly notes "Not implemented in this database," meaning the view should not be relied upon in current implementations. Its historical purpose was to surface rows from the territory change staging table so that downstream concurrent programs and territory assignment processes could identify records whose territory values had been modified and required propagation to related entities.

The view is documented in the AS - Sales Foundation product and carries a multi-org restriction. This indicates it was intended to be queried within an operating unit context, where the current organization is derived from the session's CLIENT_INFO value. The presence of columns such as TRANSFER_ONLY_FLAG and TRANSFER_TO_SALESFORCE_ID reflects the integration-oriented design of territory data, including the ability to transfer changed territory assignments to external or downstream systems.

Underlying Base Objects

According to the documented view text, AS_CHANGED_TERRITORIES is defined over a single base object: AS_CHANGED_TERRITORIES_ALL. This is a multi-org table that holds all organization rows, from which the view filters a subset based on the organization identifier. The view performs no joins; it is a projection and filter over the base table, selecting a defined list of columns.

No other referenced base objects are documented. The ETRM metadata lists the owner as unspecified and records no additional base objects, which is consistent with the simple definition shown in the view text. The relationship between the view and its base table is therefore one of direct filtering: every row returned by the view originates from AS_CHANGED_TERRITORIES_ALL and satisfies the multi-org predicate built from USERENV('CLIENT_INFO').

Key Columns

• TERRITORY_ID — Identifier of the territory whose values changed.
• TERRITORY_VALUE_ID — Identifier of the specific territory value row affected.
• SEEDED_QUALIFIER_ID — Reference to the seeded qualifier associated with the territory value.
• OLD_VALUE_NUMBER1/2/3, OLD_VALUE_LOW, OLD_VALUE_HIGH — Prior numeric or range-bound values retained for audit and change tracking.
• TRANSFER_ONLY_FLAG — Indicates whether the record is intended solely for transfer processing.
• TRANSFER_TO_SALESFORCE_ID — Integration column associated with transferring the changed territory to an external system.
• ORG_ID — Operating unit identifier used by the multi-org filter.
• CURRENCY_CODE — Currency context for monetary qualifier values.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit attributes identifying the process that last touched the row.
• Audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — Standard EBS who-columns.
• DISABLE_FLAG — Indicates whether the territory value is disabled.

Common Use Cases and Queries

Historically, this view supported diagnostics and extraction of pending territory changes within a specific operating unit. A typical query resembles the following, executed after setting the multi-org context:

• SELECT territory_id, territory_value_id, old_value_number1, transfer_only_flag, transfer_to_salesforce_id, org_id, currency_code FROM as_changed_territories WHERE org_id = :p_org_id;
• SELECT request_id, program_id, program_update_date, last_update_date FROM as_changed_territories ORDER BY last_update_date DESC;
• SELECT COUNT(*) FROM as_changed_territories WHERE transfer_to_salesforce_id IS NOT NULL; to estimate the volume of records flagged for external transfer.

Because the object is documented as obsolete and not implemented, these queries should be validated against the target instance before use. In 12.1.1 and 12.2.2 environments where the view is absent, equivalent data must be obtained directly from AS_CHANGED_TERRITORIES_ALL or from the currently supported territory assignment tables. The TRANSFER_TO_SALESFORCE_ID column is the primary driver for the user's search term and is best inspected through the base table if the view is unavailable.