Results for “salesrep_number”

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

Overview

JTF_RS_SALESREPS_INT is an interface (staging) table owned by the JTF schema within the CRM Foundation product family of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold inbound sales representative records prior to validation and transfer into the production JTF_RS_SALESREPS table. The table therefore acts as a controlled landing zone for bulk data conversions, third-party integrations, and legacy migrations involving salesperson definitions, sales credit assignments, and associated general ledger and tax attributes.

The ETRM metadata classifies the object status as VALID and documents 23 columns. From a heuristic Data Vault perspective, the table is mined as standalone, with no downstream foreign-key dependencies recorded against it. In Data Vault modeling terms, this suggests the interface table functions more like a staging structure feeding a satellite or hub load rather than a persistent hub or link itself; it is transient by design and is typically purged after successful processing.

Key Information Stored

The primary surrogate key is INTERFACE_ID, which is enforced by the unique index JTF_RS_SALESREPS_INT_U1 and serves as the sole documented business-key candidate. The most significant columns include:

• SALESREP_GUID — globally unique identifier supporting cross-system reconciliation.
• BATCH_ID — groups records into logical load runs for parallel or restartable processing.
• OPERATION and OPERATION_STATUS — indicate the intended DML action (typically CREATE or UPDATE) and the current processing outcome.
• OPERATION_MESSAGE, OPERATION_CREATION_DATE, OPERATION_PROCESS_DATE — capture error text and audit timestamps for troubleshooting failed rows.
• SALESREP_ID and RESOURCE_ID — carry the target identifiers so the concurrent program can link to the resource model.
• SALES_CREDIT_TYPE_ID — references SO_SALES_CREDIT_TYPES_115, governing how the salesperson is credited.
• STATUS, START_DATE_ACTIVE, END_DATE_ACTIVE — define the active window of the salesperson assignment.
• SALESREP_NUMBER — the human-readable business identifier.
• ORG_ID and SET_OF_BOOKS_ID — enforce multi-org and ledger context.
• GL_ID_REV, GL_ID_FREIGHT, GL_ID_REC — general ledger codes for revenue, freight, and receivables.
• EMAIL_ADDRESS, SALES_TAX_GEOCODE, SALES_TAX_INSIDE_CITY_LIMITS — contact and tax jurisdiction data.

Common Use Cases and Queries

Typical uses include monitoring interface load health and diagnosing rows that failed import. A simple health check groups records by batch and status:

• SELECT BATCH_ID, OPERATION_STATUS, COUNT(*) FROM JTF.JTF_RS_SALESREPS_INT GROUP BY BATCH_ID, OPERATION_STATUS;
• Error triage: SELECT INTERFACE_ID, OPERATION_MESSAGE FROM JTF.JTF_RS_SALESREPS_INT WHERE OPERATION_STATUS = 'ERROR';
• Validation prep: joining to SO_SALES_CREDIT_TYPES_115 on SALES_CREDIT_TYPE_ID to confirm valid credit types before submission.

Related Objects

• JTF_RS_SALESREPS — the target table populated from this interface.
• SO_SALES_CREDIT_TYPES_115 — referenced via SALES_CREDIT_TYPE_ID.
• JTF_RS_RESOURCE_EXTNS — source of RESOURCE_ID linkage.
• JTF_RS_SALESREPS_INT_U1 — unique index on INTERFACE_ID.
• Concurrent programs and PL/SQL APIs that import, validate, and purge interface rows.