Results for “electronic_mail_address”
46 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MRPBV_PLANNERS is a read-only Oracle EBS view owned by the APPS schema and validated in both 12.1.1 and 12.2.2. It belongs to the MRP (Master Scheduling/MRP) product family and is a key reference object for users who search on the base table mtl_planners. The view presents a denormalized, reporting-friendly picture of every defined planner, enriched with the inventory organization code from MTL_PARAMETERS and the organization display name from HR_ALL_ORGANIZATION_UNITS. Because MRP and ASCP functionality rely on associating planners with inventory organizations, this view serves as the canonical lookup for planner assignments across planning, sourcing, and reporting workflows. Its read-only nature (WITH READ ONLY) prevents accidental DML and makes it safe for BI Publisher reports, OBIEE/OBIA extracts, and integration interfaces that need planner identity without navigating the raw MTL_PLANNERS table directly.
Underlying Base Objects
Per the documented ETRM metadata, the view is defined over three referenced base objects, all accessed via public synonyms in the APPS schema:
- MTL_PLANNERS (PL) — the primary table holding planner attributes such as planner code, description, e-mail, organization ID, and person/employee references.
- MTL_PARAMETERS (PA) — joined on ORGANIZATION_ID to supply the ORGANIZATION_CODE for the inventory organization.
- HR_ALL_ORGANIZATION_UNITS (AL) — joined on ORGANIZATION_ID to provide the organization NAME.
The view text joins PL.ORGANIZATION_ID to both PA.ORGANIZATION_ID and AL.ORGANIZATION_ID, and applies an organization-security predicate ('_SEC:PL.ORGANIZATION_ID' IS NOT NULL) so that access is filtered by the MO: Operating Unit or security profile assigned to the session. This means the same query can return different rows depending on the operating unit context of the logged-in user, which is important for multi-org environments.
Key Columns
- PLANNER_NAME — maps to PL.PLANNER_CODE; the unique planner identifier used throughout MRP, ASCP, and purchasing.
- ORGANIZATION_CODE — from MTL_PARAMETERS; the short inventory organization code.
- ORGANIZATION_NAME — from HR_ALL_ORGANIZATION_UNITS; the descriptive organization name.
- DESCRIPTION, ELECTRONIC_MAIL_ADDRESS, DISABLE_DATE — planner descriptive attributes; DISABLE_DATE indicates when the planner was deactivated.
- ORGANIZATION_ID — the inventory organization context and the security key column.
- PERSON_ID — maps to PL.EMPLOYEE_ID; the HR employee associated with the planner.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns for change tracking.
Common Use Cases and Queries
Typical scenarios include reporting active planners by organization, validating planner assignments before running a plan, and joining planner data into supply/demand or item-master extracts. A representative query listing enabled planners is:
SELECT planner_name, organization_code, organization_name, electronic_mail_address FROM apps.mrpbv_planners WHERE disable_date IS NULL AND organization_id = :org_id;- To find all planners in an organization:
SELECT planner_name, description, person_id FROM apps.mrpbv_planners WHERE organization_code = 'M1'; - To feed an integration extract:
SELECT planner_name, organization_code, electronic_mail_address, last_update_date FROM apps.mrpbv_planners;
Because of the organization-security predicate, callers should always run these queries within the correct operating unit context or supply an explicit ORGANIZATION_ID filter.
-
View: MRPBV_PLANNERS 12.1.1
APPS.MRPBV_PLANNERS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·↳ MTL_PLANNERS·Explore MRP module →
-
This table stores and maintains a list of planner codes.
-
View: MRPBV_PLANNERS 12.2.2
APPS.MRPBV_PLANNERS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·↳ MTL_PLANNERS·Explore MRP module →
-
View: MRPFV_PLANNERS 12.1.1
- Retrofitted
APPS.MRPFV_PLANNERS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·↳ MTL_PLANNERS·Explore MRP module →
-
View: MRPFV_PLANNERS 12.2.2
- Retrofitted
APPS.MRPFV_PLANNERS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·↳ MTL_PLANNERS·Explore MRP module →
-
Planner code definitions
-
Planner code definitions
-
The staging table used by the collection program to validate and processdata for table MSC_PLANNERS....
-
This table stores and maintains a list of planner codes.
-
The staging table used by the collection program to validate and processdata for table MSC_PLANNERS....
-
VIEW: MSC.MSC_ST_PLANNERS# 12.2.2
-
VIEW: INV.MTL_PLANNERS# 12.2.2
-
VIEW: MSC.MSC_PLANNERS# 12.2.2
-
VIEW: APPS.MRPFV_PLANNERS 12.1.1
-
VIEW: APPS.MRPBV_PLANNERS 12.2.2
-
VIEW: INV.MTL_PLANNERS# 12.2.2
-
VIEW: APPS.MRPFV_PLANNERS 12.2.2
-
VIEW: APPS.MRPBV_PLANNERS 12.1.1
-
VIEW: MSC.MSC_PLANNERS# 12.2.2
-
VIEW: MSC.MSC_ST_PLANNERS# 12.2.2
-
TABLE: INV.MTL_PLANNERS 12.1.1
-
TABLE: INV.MTL_PLANNERS 12.2.2
-
TABLE: MSC.MSC_PLANNERS 12.2.2
-
TABLE: MSC.MSC_PLANNERS 12.1.1
-
TABLE: MSC.MSC_ST_PLANNERS 12.2.2
-
TABLE: MSC.MSC_ST_PLANNERS 12.1.1
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MRP Tables and Views 12.1.1
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MSC Tables and Views 12.1.1
This table contains the mapping between user-defined zone and included regions
-
eTRM - MSC Tables and Views 12.2.2
This table contains the mapping between user-defined zone and included regions
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2