Results for “as_pe_int_categories”

50+ results




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

Overview

AS_PE_INT_CATEGORIES is a Sales Foundation (AS) mapping table owned by the OSM schema in Oracle E-Business Suite. Its documented description is a "mapping table between plan elements in OSC and forecast," indicating that it bridges Oracle Sales Compensation (OSC) plan-element definitions and forecast-related constructs within the Sales Foundation data model. The table carries a primary key, AS_PE_INT_CATEGORIES_PK, defined on the PE_INT_CATEGORY_ID column, and a unique index, AS_PE_INT_CATEGORIES_U1, also on PE_INT_CATEGORY_ID. It is classified as VALID in the ETRM metadata and contains 19 documented columns in the 12.2.2 physical schema. When interpreted through a Data Vault lens, the mined foreign-key structure suggests a link classification: the table resolves several many-to-many relationships between quotas, interest types, interest codes, and product category constructs, rather than functioning as a standalone hub or descriptive satellite. This classification should be treated as a modeling heuristic, not an Oracle-declared design attribute.

Key Information Stored

The table's most significant columns are its identifiers and mapping attributes. PE_INT_CATEGORY_ID is the surrogate primary key and the unique business-key candidate exposed through AS_PE_INT_CATEGORIES_U1. MAPPING_TYPE records the category or nature of the mapping between the OSC plan element and the forecast construct. QUOTA_ID references CN_QUOTAS_ALL, tying a mapping row to a quota definition. INTEREST_TYPE_ID references AS_INTEREST_TYPES_B, and PRI_INTEREST_CODE_ID and SEC_INTEREST_CODE_ID both reference AS_INTEREST_CODES_B, providing primary and secondary interest-code assignments. SECURITY_GROUP_ID references FND_SECURITY_GROUPS and supports multi-org/security-group partitioning. PRODUCT_CATEGORY_ID and PRODUCT_CAT_SET_ID capture product categorization and the associated category set. Standard EBS audit columns are present: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. OBJECT_VERSION_NUMBER supports optimistic locking for concurrent updates.

Common Use Cases and Queries

The primary use case is reconciling OSC plan elements with forecast categories. Analysts query this table to determine which interest type, interest codes, and quota are associated with a given mapping category. A typical query joins the table to its reference tables to resolve descriptive names:

  • Join AS_PE_INT_CATEGORIES to AS_INTEREST_TYPES_B on INTEREST_TYPE_ID to validate interest-type context.
  • Join to AS_INTEREST_CODES_B twice, on PRI_INTEREST_CODE_ID and SEC_INTEREST_CODE_ID, to retrieve both interest codes.
  • Join to CN_QUOTAS_ALL on QUOTA_ID to attribute mappings to quota plans.
  • Filter by SECURITY_GROUP_ID to enforce row-level security in reporting extracts.
  • Track changes via LAST_UPDATE_DATE, LAST_UPDATED_BY, and the PROGRAM_* columns for audit and concurrent-program diagnostics.

Because the table is a mapping link, reporting usually aggregates counts of mappings per quota, interest type, or product category, and flags rows with MAPPING_TYPE values of interest.

Related Objects

The documented foreign-key relationships identify the most significant related objects. CN_QUOTAS_ALL is referenced through QUOTA_ID. AS_INTEREST_TYPES_B is referenced through INTEREST_TYPE_ID. AS_INTEREST_CODES_B is referenced twice, through PRI_INTEREST_CODE_ID and SEC_INTEREST_CODE_ID. FND_SECURITY_GROUPS is referenced through SECURITY_GROUP_ID. The AS_PE_INT_CATEGORIES_PK and AS_PE_INT_CATEGORIES_U1 indexes enforce identity on PE_INT_CATEGORY_ID and are the entry points for any lookup or de-duplication logic. Product category columns PRODUCT_CATEGORY_ID and PRODUCT_CAT_SET_ID imply dependencies on product category definition tables within the EBS product-catalog model, though these are not listed among the documented foreign keys in the ETRM metadata.