Results for “jtf_rs_salesreps”

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

Overview

JTF_RS_SALESREPS is a core CRM Foundation table in Oracle E-Business Suite (12.1.1 and 12.2.2), owned by the JTF schema. It stores the master record for every sales representative defined in the system. Each row links a sales representative to an underlying resource in JTF_RS_RESOURCE_EXTNS, tying the CRM resource model to the receivables and order-capture subsystems that use salesrep numbers and sales credit assignments.

The table is registered as VALID in ETRM with 41 documented columns. Its primary key, JTF_RS_SALESREPS_PK, is defined on SALESREP_ID. A unique business-key constraint, JTF_RS_SALESREPS_U1, exists on the composite (SALESREP_ID, ORG_ID); the documentation further notes that when resource category is 'OTHERS', SALESREP_NUMBER combined with ORG_ID is also unique. The Data Vault classification mined from the foreign-key structure is hub-leaning, so a modeling suggestion is to treat JTF_RS_SALESREPS as a Hub entity, with SALESREP_ID as the durable business key, and to represent the surrounding reference relationships as links or satellites rather than blending them into the hub. This reflects the fact that the table's FK columns point outward to resource, sales-credit type, and security-group reference data rather than to other transactional facts.

Key Information Stored

The most important columns and their roles are:

• SALESREP_ID — surrogate primary key; unique identifier of the sales representative.
• RESOURCE_ID — foreign key to JTF_RS_RESOURCE_EXTNS, the CRM resource record that provides party and contact details.
• SALESREP_NUMBER — the operational salesrep number used in transactions; unique with ORG_ID when resource category is 'OTHERS'.
• ORG_ID — operating unit identifier; partners with SALESREP_NUMBER for the business-key uniqueness rule.
• NAME — the display name of the sales representative.
• STATUS — the active/inactive state driving eligibility in transaction flows.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range for the salesrep record.
• SALES_CREDIT_TYPE_ID — foreign key to SO_SALES_CREDIT_TYPES_115, classifying the sales credit type.
• SET_OF_BOOKS_ID — ledger context relevant to Receivables (AR) integration.
• PERSON_ID — link into the TCA person model.
• EMAIL_ADDRESS — contact channel for the sales representative.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant/security partitioning.
• OBJECT_VERSION_NUMBER — optimistic concurrency control column maintained by the framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF/descriptive flexfield columns for client extensions.
• WH_UPDATE_DATE — warehouse update timestamp used in data-extraction and load patterns.

Common Use Cases and Queries

This table is queried whenever salesrep identity, territory assignment, or sales credit must be resolved. Typical patterns include:

• Valid salesrep lookup by operating unit: filter ORG_ID, STATUS, and the active date window to return only currently effective reps.
• Salesrep-to-resource resolution: join RESOURCE_ID to JTF_RS_RESOURCE_EXTNS to obtain resource details.
• Sales credit reporting: join FII_AR_SALES_CREDITS on SALESREP_ID to report credit assignments.
• Territory analysis: join JTF_RS_SRP_TERRITORIES on SALESREP_ID for territory membership.
• Integration extracts: use WH_UPDATE_DATE as the delta watermark for incremental data warehouse loads.
• Extensibility: read ATTRIBUTE1–15 for customer-specific reporting fields.

A representative query joins the resource extension table and filters on effective status and date range, restricting by ORG_ID when reporting for a single operating unit.

Related Objects

• JTF_RS_RESOURCE_EXTNS — referenced via JTF_RS_SALESREPS.RESOURCE_ID; supplies resource/master details.
• SO_SALES_CREDIT_TYPES_115 — referenced via SALES_CREDIT_TYPE_ID; defines sales credit types.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; supports security partitioning.
• FII_AR_SALES_CREDITS — references this table via SALESREP_ID; transaction-level credit lines.
• JTF_RS_SRP_TERRITORIES — references this table via SALESREP_ID; salesrep-to-territory assignments.

Together these relationships position JTF_RS_SALESREPS as the hub of salesrep identity, with Receivables credits and territory assignments as the principal downstream consumers.