Search Results partner_number




Overview
Explore in AI Chat

Overview

MRP_AP_VENDORS_V is a reporting view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It presents supplier (vendor) records in a partner-oriented format, exposing vendors from the purchasing schema alongside scheduling-relevant flags maintained by the MRP application. The view is primarily consumed by Oracle Advanced Supply Chain Planning and related planning products, which reference suppliers as "partners" within the planning data model. Because the naming convention follows the MRP_AP_* family — views that bridge MRP planning entities to Oracle Payables and Purchasing master data — this view serves as a read-only integration surface rather than a transactional object.

In the ETRM documentation the view is marked as "Not implemented in this database," indicating that it is a seeded, dictionary-defined object whose presence depends on the installed product set. It is defined as a join of a scheduling snapshot (or staging) object and the standard purchasing vendor view. No base tables are formally documented as dependencies in the ETRM metadata.

Underlying Base Objects

The view text references two objects:

The relationship is a one-to-one (or filtered one-to-one) join on the vendor identifier, meaning only vendors present in both sources appear in the output. The RN column is carried through from the source and likely supports deduplication or ordering logic in downstream consumers.

Key Columns

  • SR_TP_ID — sourced from SN.VENDOR_ID; the internal identifier of the source trading partner (supplier) record.
  • DISABLE_DATE — sourced from SN.VENDOR_END_DATE_ACTIVE; the date on which the supplier becomes inactive. Null indicates an active supplier.
  • PARTNER_TYPE — a literal value of 1, distinguishing this partner class (supplier) from other partner types in the planning model.
  • PARTNER_NAME — sourced from SN.VENDOR_NAME; the display name of the supplier.
  • PARTNER_NUMBER — sourced from V.VENDOR_NUMBER; the user-facing supplier number. This is the column most relevant to searches for "partner_number," as it is the business key planners and buyers recognize.
  • RN1 — aliased from SN.RN; an internal row/sequence indicator.

The naming strategy deliberately remaps purchasing terminology (vendor) to planning terminology (partner), which is why the PARTNER_NUMBER column corresponds to VENDOR_NUMBER at the base layer.

Common Use Cases and Queries

Typical uses include validating that supplier numbers are correctly synchronized into the planning schema, resolving a partner number back to its internal vendor identifier, and filtering out inactive suppliers before planning runs.

Retrieve all active partners with their numbers:

  • SELECT partner_number, partner_name, sr_tp_id FROM mrp_ap_vendors_v WHERE disable_date IS NULL;

Look up a specific partner by number:

  • SELECT sr_tp_id, partner_name, disable_date FROM mrp_ap_vendors_v WHERE partner_number = :vendor_number;

Identify suppliers disabled after a cutoff date:

  • SELECT partner_number, partner_name, disable_date FROM mrp_ap_vendors_v WHERE disable_date > SYSDATE;

Because the view is not implemented in every database, availability should be confirmed via ALL_VIEWS before deployment.