Results for “gl_id_freight”

50+ results




Overview
Explore in AI Chat

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

Overview

JTF_RS_DEFRESOURCES_SRP_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified under the FND – Application Object Library product family and is currently flagged as VALID in the ETRM object registry. Functionally, the view exposes the default resource and salesrep records that underpin Oracle's resource management and order capture flows. It presents the sales representative (SALESREP) attribution data used by Order Management, Receivables, and CRM modules, joining the salesrep master data to the sales credit type reference so that a credit-type name is available alongside each salesrep record. Because it sits directly on the multilingual operational view JTF_RS_SALESREPS_MO_V, it is most commonly consumed by reporting layers, concurrent programs, and integration extracts that need a denormalised, credit-type-labelled view of sales representatives. The "_SRP_" token in the name denotes SalesRep and the trailing "_V" confirms it is a view rather than a physical table.

The reported search term jtf_rs_salesreps_mo_v is the primary underlying object for this view, so users arriving from that search are typically trying to understand the layered relationship between the salesrep base view and the credit-type-enriched reporting view.

Underlying Base Objects

The ETRM metadata documents two referenced base objects for JTF_RS_DEFRESOURCES_SRP_V, both referenced as synonyms in the APPS schema:

  • JTF_RS_SALESREPS_MO_V — the salesrep master view supplying the SRP alias rows, including all descriptive, auditing, accounting, and attribute columns.
  • OE_SALES_CREDIT_TYPES — the sales credit type reference table joined by SALES_CREDIT_TYPE_ID to resolve the credit type name via the SALES_CREDIT_TYPE alias.

The view definition performs an inner join between these two objects on SALES_CREDIT_TYPE_ID. Because the join is not outer, salesrep rows whose SALES_CREDIT_TYPE_ID does not resolve in OE_SALES_CREDIT_TYPES are excluded from the result set. This is an important behavioural characteristic: the view returns only those salesreps that carry a valid, defined credit type. The ROWID of the salesrep source row is carried forward as ROW_ID, which supports tools that depend on ROWID-based identification of view rows.

Key Columns

The view exposes the full column set of the salesrep source view plus the resolved credit type name. Notable columns include:

Common Use Cases and Queries

Typical uses include validating active salesreps by operating unit, driving commission and credit allocation reports, and populating integration extracts that require the credit type name alongside the salesrep. The following query lists currently active salesreps for a given operating unit with their credit type:

SELECT salesrep_number, name, sales_credit_type, email_address FROM apps.jtf_rs_defresources_srp_v WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

A second frequent pattern joins the view to order or invoice credit lines via SALESREP_ID and SALES_CREDIT_TYPE_ID to reconcile credit allocation to named representatives. Because the view is a reporting object and performs an inner join, any reconciliation should account for salesreps whose credit type is undefined, as those will not appear. Queries should be schema-qualified with APPS and, where multi-org is enabled, filtered by ORG_ID to respect operating unit security.