Results for “office_number”

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

Overview

OE_PRINT_SREP_LOCTN_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the Order Management (ONT) product family. Its documented status is VALID in both EBS 12.1.1 and 12.2.2. The view exists to supply salesperson contact and location attributes — including email address, internal location, mailstop, and office number — for use in order-related document printing and reporting. In practice it supports the correspondence and routing information that appears on order acknowledgements, pick/pack documents, and similar printed output, where the sales representative assigned to a transaction must be identified with reachable internal addressing details. Because the view filters resources to the employee category and enforces the effective-dating window on the person record, it returns only currently active sales representative assignments of type EMPLOYEE, which keeps printed documents free of stale or non-employee resource data.

The name itself reflects its purpose: "PRINT" indicates a print/reporting orientation, "SREP" denotes sales representative, and "LOCTN" denotes location-related attributes. This aligns with the user search term internal_location, which is one of the six projected columns.

Underlying Base Objects

The view is defined over three referenced base objects, all accessed through APPS synonyms:

• JTF_RS_SALESREPS — aliased JRS; the sales representative assignment table joining resources to salesrep identifiers.
• JTF_RS_RESOURCE_EXTNS — aliased JRE; the resource extension table carrying the resource category and source person reference.
• PER_ALL_PEOPLE_F — aliased PP; the effective-dated HR person table supplying contact and location attributes.

Join conditions are explicit and worth noting for performance and correctness. JRS.RESOURCE_ID equals JRE.RESOURCE_ID links the salesrep to its resource extension. JRE.CATEGORY is restricted to the literal value 'EMPLOYEE', excluding non-employee resource types. JRE.SOURCE_ID equals PP.PERSON_ID links the resource to the HR person record, and the predicate SYSDATE BETWEEN PP.EFFECTIVE_START_DATE AND NVL(PP.EFFECTIVE_END_DATE, SYSDATE) restricts results to the currently effective person row. The NVL on EFFECTIVE_END_DATE ensures open-ended records (null end date) are treated as still active.

Key Columns

• SALESREP_ID — the sales representative identifier from JTF_RS_SALESREPS, the primary linking key to order and salesrep assignment data.
• CATEGORY — resource category from JTF_RS_RESOURCE_EXTNS; by construction of the WHERE clause this is always 'EMPLOYEE' in returned rows.
• EMAIL_ADDRESS — the person's email address from PER_ALL_PEOPLE_F, used for electronic correspondence on printed output.
• INTERNAL_LOCATION — the person's internal office location, the attribute most directly associated with the "internal_location" search term and the principal reason for querying this view.
• MAILSTOP — the internal mailstop designation, used for physical routing of documents.
• OFFICE_NUMBER — the office telephone number associated with the sales representative.

Common Use Cases and Queries

Typical usage resolves a salesperson's current internal contact details for a report or print program. A direct lookup by salesrep identifier is the most common pattern:

• SELECT salesrep_id, email_address, internal_location, mailstop, office_number FROM oe_print_srep_loctn_v WHERE salesrep_id = :p_salesrep_id;
• SELECT internal_location, mailstop FROM oe_print_srep_loctn_v WHERE salesrep_id IN (SELECT salesrep_id FROM oe_order_headers_all WHERE order_number = :p_order);

Because the view already applies the effective-dating and employee-category filters, callers do not need to re-implement those predicates, which reduces the risk of duplicated or inconsistent logic across custom reports. When joining to order tables, the SALESREP_ID column is the appropriate join key. Note that the view returns at most one effective row per person per point in time; historical salesperson location data is not exposed, since only the currently effective PER_ALL_PEOPLE_F record survives the SYSDATE predicate.

Oracle proprietary and confidential. Refer to ETRM documentation for the authoritative definition in the target release.