Search Results as_terr_type_quals_u2

Overview

The OSM.AS_TERR_TYPE_QUALIFIERS table is a core data definition table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Sales (AS) module. It functions as a junction or mapping table that defines the allowable qualifiers for different territory types. In the context of Oracle's territory management engine, a territory type (e.g., "Sales," "Service") can have specific qualifiers (attributes like "Industry" or "Revenue Band") assigned to it to define the criteria for territory assignment. This table establishes which pre-defined (seeded) qualifiers are valid for use with a given territory type, thereby enforcing data integrity and business rules in the territory configuration.

Key Information Stored

The table stores the relationship metadata between territory types and their qualifiers. Key columns include:

• TERR_TYPE_QUALIFIER_ID: The primary key (PK) uniquely identifying each record in this mapping table.
• SEEDED_QUALIFIER_ID: A foreign key (FK) referencing a seeded, system-defined qualifier from a master list. This column, combined with TERRITORY_TYPE_ID, forms a unique constraint (AS_TERR_TYPE_QUALS_U2).
• TERRITORY_TYPE_ID: A foreign key (FK) referencing the territory type to which the qualifier is being assigned. A non-unique index (AS_TERR_TYPE_QUALS_N1) exists on this column for performance.
• OVERLAP_ALLOWED_FLAG: A critical business rule column indicating whether territories of this type, when using this qualifier, are permitted to have overlapping assignments (e.g., 'Y' or 'N').
• Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track record history.

Common Use Cases and Queries

This table is primarily accessed during the setup and administration of territory management rules. A common use case is retrieving all qualifiers enabled for a specific territory type to validate user input during territory definition or to populate a list of values in the application UI. For reporting, administrators may query the table to audit territory configuration rules.

Sample query to list all qualifiers for a specific territory type (ID=100):
SELECT sq.QUALIFIER_NAME, attq.OVERLAP_ALLOWED_FLAG
FROM OSM.AS_TERR_TYPE_QUALIFIERS attq,
     AS_SEEDED_QUALIFIERS sq
WHERE attq.SEEDED_QUALIFIER_ID = sq.SEEDED_QUALIFIER_ID
AND attq.TERRITORY_TYPE_ID = 100
ORDER BY sq.QUALIFIER_NAME;
Another critical query pattern involves checking the OVERLAP_ALLOWED_FLAG when creating or modifying territory rules to ensure compliance with the defined business policy.

Related Objects

Based on the provided metadata, the table's structure indicates relationships with other key AS objects, though explicit foreign key names are not listed. The columns imply the following critical dependencies:

• AS_TERRITORY_TYPES_B: The TERRITORY_TYPE_ID column is a foreign key to this table, which stores the definition of territory types.
• AS_SEEDED_QUALIFIERS: The SEEDED_QUALIFIER_ID column is a foreign key to this reference table, which holds the master list of system-defined qualifier codes and names.

The table itself is referenced by the APPS synonym AS_TERR_TYPE_QUALIFIERS, which is the name used by EBS application code and reports to access this table. The unique indexes (U1, U2) enforce that the primary key and the combination of territory type and qualifier are not duplicated.