Results for “old_value_number1”

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

Overview

AS_CHANGED_TERRITORIES_ALL is a Sales Foundation (AS) transactional table owned by the OSM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the before-image of territory definitions that have been modified, disabled, or transferred, capturing the values a territory attribute held prior to a change. The table functions as a change-staging and audit construct within the Territory Manager and Sales Force administration flow, allowing territory updates to be processed asynchronously by concurrent programs rather than applied immediately.

Under the heuristic Data Vault classification derived from the foreign-key structure, this table is best modeled as a link. Its primary key, TERRITORY_ID, plus multiple foreign keys to dimension-like parent tables (AS_TERRITORIES_ALL, AS_SALESFORCE, AS_TERRITORY_VALUES_ALL) indicate a relationship/associative role rather than an independent hub. Implementers designing an analytical or integration model should treat it as a junction between territory, sales force, and territory value entities, with the old-value columns acting as attribute payload.

Key Information Stored

• TERRITORY_ID — Surrogate primary key (AS_CHANGED_TERRITORIES_PK) and foreign key to AS_TERRITORIES_ALL; identifies the territory being changed.
• TERRITORY_VALUE_ID — Foreign key to AS_TERRITORY_VALUES_ALL, tying the change record to the specific territory value row affected.
• SEEDED_QUALIFIER_ID — Identifies the seeded qualifier (for example, a numeric or range qualifier) whose value is being altered.
• OLD_VALUE_NUMBER1, OLD_VALUE_NUMBER2, OLD_VALUE_NUMBER3 — Prior numeric values of the qualifier, retained so the change can be reversed or audited.
• OLD_VALUE_LOW, OLD_VALUE_HIGH — Prior lower and upper bounds for range-based qualifiers.
• TRANSFER_ONLY_FLAG — Indicates whether the change represents a transfer of the territory without a value modification.
• TRANSFER_TO_SALESFORCE_ID — Foreign key to AS_SALESFORCE, identifying the sales force organization receiving the transferred territory.
• DISABLE_FLAG — Marks whether the change disables the territory or territory value.
• ORG_ID — Multi-org operating unit discriminator; critical for row-level security and reporting partition.
• CURRENCY_CODE — Currency context for the stored numeric values.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns identifying which request and program performed the change, and when.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns aiding audit and reconciliation.

The documented metadata does not identify a business-key unique index beyond the TERRITORY_ID primary key, so business-key candidates must be inferred from the FK combination of TERRITORY_ID, TERRITORY_VALUE_ID, and SEEDED_QUALIFIER_ID.

Common Use Cases and Queries

Primary use cases include territory re-organization, sales force transfer validation, and audit reporting on deleted or disabled territory qualifiers. A typical pattern joins the change table to its parent territory table:

• Reconcile pending territory changes before running the Territory Manager concurrent program, filtering on REQUEST_ID.
• Report territories transferred to a new sales force by joining TRANSFER_TO_SALESFORCE_ID to AS_SALESFORCE and returning the sales force name.
• Audit historical qualifier values by selecting OLD_VALUE_LOW and OLD_VALUE_HIGH against AS_TERRITORY_VALUES_ALL.
• Multi-org reporting constrained by ORG_ID to isolate changes per operating unit.
• Sample SQL: SELECT t.name, c.old_value_low, c.old_value_high FROM as_changed_territories_all c, as_territories_all t WHERE c.territory_id = t.territory_id AND c.org_id = :org_id;

Related Objects

• AS_TERRITORIES_ALL — Parent territory definition; joined via AS_CHANGED_TERRITORIES_ALL.TERRITORY_ID.
• AS_TERRITORY_VALUES_ALL — Territory qualifier values; joined via TERRITORY_VALUE_ID.
• AS_SALESFORCE — Sales force organization receiving transferred territories; joined via TRANSFER_TO_SALESFORCE_ID.
• FND_CONCURRENT_REQUESTS — Resolves REQUEST_ID to the concurrent request that generated the change record.
• FND_USER — Resolves CREATED_BY and LAST_UPDATED_BY to application users.
• AS_TERRITORY_QUALIFIERS and AS_SALES_TERRITORY_MEMBERS — Downstream consumers of territory and sales force assignments affected by the change.
• ORG_ORGANIZATION_DEFINITIONS — Provides the operating unit name for ORG_ID.

Because the table participates in the Territory Manager change pipeline, dependent concurrent programs and views should be validated whenever AS_CHANGED_TERRITORIES_ALL is purged or archived.