Results for “role_model_id”

50+ results




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

Overview

CN_PLAN_TEXTS is a transactional configuration table in the Oracle E-Business Suite Incentive Compensation (CN) module. It stores customized text content used to render compensation contracts and plan documents for individual sales roles. According to the ETRM metadata, the table "contains the customized information on compensation contract for each sales role," allowing administrators to tailor the contract title, club qualification language, terms and conditions, and approver information presented to each participant.

Because the table captures role-specific plan text rather than serving as a master list of roles, quota categories, or models, the heuristic Data Vault classification supplied in the metadata is link. This classification reflects that CN_PLAN_TEXTS sits between several reference entities — roles, quota categories, and role models — and records the association of textual content with those entities. In practice, a satellite classification could also be argued for the descriptive TEXT columns, but the documented FK structure supports treating the table as a relationship-bearing link.

Key Information Stored

The table's physical schema in 12.2.2 comprises 31 columns in the CN schema. The most significant columns are:

Common Use Cases and Queries

The principal use case is generating role-specific compensation contract output. Reporting typically joins CN_PLAN_TEXTS to CN_ROLE_DETAILS to resolve role names and to CN_QUOTA_CATEGORIES to resolve category labels. A representative query retrieves all text for a given role:

  • SELECT t.plan_text_id, t.text_type, t.text, r.role_name FROM cn.cn_plan_texts t, cn.cn_role_details r WHERE t.role_id = r.role_id AND t.role_id = :p_role_id ORDER BY t.sequence_id;

Other common scenarios include auditing which roles have customized contract language versus default text, verifying that club qualification statements exist for each quota category, and extracting approver information for workflow or correspondence generation. Administrators may also query by SECURITY_GROUP_ID to confirm that plan text is visible only to the appropriate operating unit or responsibility set.

Related Objects

  • CN_ROLE_DETAILS — joined via CN_PLAN_TEXTS.ROLE_ID; the primary parent defining the sales role.
  • CN_QUOTA_CATEGORIES — joined via CN_PLAN_TEXTS.QUOTA_CATEGORY_ID; scopes text to a quota category.
  • CN_ROLE_MODELS_ALL — joined via CN_PLAN_TEXTS.ROLE_MODEL_ID; associates plan text with a compensation role model.
  • FND_SECURITY_GROUPS — joined via CN_PLAN_TEXTS.SECURITY_GROUP_ID; enforces multi-org style data security.
  • CN_PLAN_TEXTS_PK / CN_PLAN_TEXTS_U1 — the primary key constraint and unique index that govern row identity.