Results for “op_slsr_mst”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The table GML.OP_SLSR_MST is the sales representative master table within the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite, documented as valid in the ETRM reference for releases 12.1.1 and 12.2.2. It functions as a foundational master data object used to define and maintain sales representatives who are assigned to orders, proposals, commissions, and customers across the process manufacturing sales cycle.
Based on the foreign key topology provided in the metadata, this table is classified as hub-leaning in a Data Vault modeling heuristic. This suggests it should be treated as a hub entity, with SLSREP_CODE serving as the business key that anchors related descriptive attributes and downstream transactional associations. The single unique index, OP_SLSR_MST_PK, confirms SLSREP_CODE as the definitive business key candidate.
Key Information Stored
The table contains 24 documented columns. The most significant are:
SLSREP_CODE— Primary key and business identifier for the sales representative.SLSREP_NAME— Descriptive name of the representative.ADDR_ID— Foreign key toSY_ADDR_MST, storing the representative's address.SLSREP_TYPEandSLSREP_CLASS— Classify the representative;SLSREP_CLASSreferencesOP_SLSR_CLS.MGRSLSREP_CODE— Identifies the managing sales representative for reporting hierarchies.SLSREP_TERRITORY— Territory assignment for the representative.COMMISSION_CODE— Links to the commission setup inOP_COMMISSION.PRICESLSREP_CODE— Associates the representative with pricing responsibility.SLSREP_PHONE1andSLSREP_PHONE2— Contact telephone numbers.CO_CODE— Operating company/organization, referencingSY_ORGN_MSTandSY_ORGN_MST_B.TEXT_CODE— Foreign key toOP_TEXT_HDRfor descriptive text attachments.- Audit columns such as
CREATION_DATE,LAST_UPDATE_DATE,CREATED_BY,LAST_UPDATED_BY,LAST_UPDATE_LOGIN,DELETE_MARK, and concurrent program identifiers (PROGRAM_ID,REQUEST_ID).
Note that TRANS_CNT and the program-related columns are less central to functional use but support auditing and process tracking.
Common Use Cases and Queries
Typical reporting and integration scenarios include validating sales representative assignments on orders and proposals, reconciling commission setups, and building territory or hierarchy reports.
SELECT s.SLSREP_CODE, s.SLSREP_NAME, s.SLSREP_TERRITORY, s.COMMISSION_CODE
FROM GML.OP_SLSR_MST s
WHERE s.DELETE_MARK = 0
ORDER BY s.SLSREP_NAME;
SELECT h.ORDER_NO, d.LINE_NO, s.SLSREP_NAME
FROM GML.OP_ORDR_HDR h,
GML.OP_ORDR_DTL d,
GML.OP_SLSR_MST s
WHERE h.ORDER_ID = d.ORDER_ID
AND d.SLSREP_CODE = s.SLSREP_CODE(+)
AND s.SLSREP_TERRITORY = :territory;
Such queries support sales performance analysis, commission calculation verification, and exception reporting where representatives may lack commission or class assignments.
Related Objects
The following objects are the most significant referenced by or referencing this table through documented foreign keys:
OP_COMMISSION— Referenced viaCOMMISSION_CODE; defines commission structures.OP_SLSR_CLS— Referenced viaSLSREP_CLASS; defines representative classifications.SY_ADDR_MST— Referenced viaADDR_ID; provides address master data.SY_ORGN_MSTandSY_ORGN_MST_B— Referenced viaCO_CODE; operating company definitions.OP_TEXT_HDR— Referenced viaTEXT_CODE; header text repository.OP_ORDR_HDRandOP_ORDR_DTL— ReferenceSLSREP_CODE, tying representatives to sales orders.OP_CUST_MSTandOP_CUST_MST_OPM— ReferenceSLSREP_CODE, linking representatives to customers.OP_PRSL_HDRandOP_PRSL_DTL— ReferenceSLSREP_CODE, associating representatives with proposals.OP_COMM_CDS— ReferencesSLSREP_CODE, connecting commission codes to representatives.
These relationships establish OP_SLSR_MST as a central hub supporting order capture, proposal management, customer assignment, and commission processing within Process Manufacturing Logistics.
-
Sales representative master table.
-
Sales representative master table.
-
SYNONYM: APPS.OP_SLSR_MST 12.1.1
-
SYNONYM: APPS.OP_SLSR_MST 12.2.2
-
TABLE: GML.OP_SLSR_MST 12.1.1
-
TABLE: GML.OP_SLSR_MST 12.2.2
-
VIEW: GML.OP_SLSR_MST# 12.2.2
-
TABLE: GML.OP_SLSR_MST_INT 12.1.1
-
TABLE: GML.OP_SLSR_MST_INT 12.2.2
-
VIEW: GML.OP_SLSR_MST# 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
View: PMIFV_SALES_DETAILS_V 12.2.2
Details of all shipped sales orders which are associated to corresponding GL periods.
APPS.PMIFV_SALES_DETAILS_V·↳ FND_PROFILE·↳ GL_PERIODS·↳ GL_PLCY_MST·Explore PMI module →
-
Commission code detail.
-
Commission code detail.
-
Table: OP_CUST_MST 12.1.1
Customer master.
Not implemented in this database·Explore GML module →
-
Table: OP_CUST_MST 12.2.2
Customer master.
Not implemented in this database·Explore GML module →
-
View: PMIFV_SALES_DETAILS_V 12.1.1
Details of all shipped sales orders which are associated to corresponding GL periods.
APPS.PMIFV_SALES_DETAILS_V·↳ FND_PROFILE·↳ GL_PERIODS·↳ GL_PLCY_MST·Explore PMI module →
-
Table: OP_SLSR_MST_INT 12.2.2
Sales representative interface table used to transfer data from Oracle Receivables.
-
Table: OP_SLSR_MST_INT 12.1.1
Sales representative interface table used to transfer data from Oracle Receivables.
-
Table: SY_ORGN_MST 12.1.1
Organization code master.
Not implemented in this database·Explore GMA module →
-
Table: SY_ORGN_MST 12.2.2
Organization code master.
Not implemented in this database·Explore GMA module →
-
Sales Order Header table.
-
eTRM - GML Tables and Views 12.1.1
Tax reporting classes.
-
Sales Order Header table.
-
Customer master.
-
eTRM - GML Tables and Views 12.2.2
Tax reporting classes.
-
Customer master.
-
Order Profile Header and Blanket Sales Order Header.
-
Order Profile Header and Blanket Sales Order Header.
-
Order profile lines and blanket sales order lines.
-
PACKAGE: APPS.GMF_GLSYNCH 12.1.1
-
PACKAGE: APPS.GMF_GLSYNCH 12.2.2
-
Order profile lines and blanket sales order lines.
-
Order detail (order lines).
-
Order detail (order lines).