Results for “preprocessing_lead_time”

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

Overview

The MRP_ATP_PROPERTIES_V view is a reporting and integration construct within the Oracle E-Business Suite Master Scheduling/MRP (MRP) product. Owned by the APPS schema and validated against Oracle EBS 12.1.1 and 12.2.2, it exposes ATP (Available-to-Promise) planning attributes assembled during an ATP inquiry or scheduling session. The view's principal function is to present transient ATP computation results — lead times, capacity constraints, substitution windows, and operational attributes — in a de-normalized, human-readable form. This makes it suitable for diagnostic queries, custom concurrent programs, and downstream integrations that need to reconcile the numeric flags stored in the working table with their descriptive lookup meanings.

The view is of particular interest to implementers searching on atp_flag, because it resolves the raw ATP_FLAG and ATP_COMPONENT_FLAG code values into their FND_COMMON_LOOKUPS meanings directly in the SELECT list.

Underlying Base Objects

Per documented ETRM metadata for 12.2.2, the view is defined over the following objects:

• MRP_ATP_DETAILS_TEMP (SYNONYM) — the primary source, accessed in the view text via the alias MRP. This temporary table holds per-session ATP detail rows; the view restricts results to RECORD_TYPE = 3, isolating a specific record category.
• FND_COMMON_LOOKUPS (VIEW) — joined twice as FND1 and FND2 for ATP_FLAG and ATP_COMPONENT_FLAG decoding, using APPLICATION_ID = 401 and LOOKUP_TYPE = 'ATP_FLAG'.
• MFG_LOOKUPS (VIEW) — joined three times as MFG1, MFG2, and MFG3 to decode BATCHABLE_FLAG and ROUNDING_CONTROL against SYS_YES_NO, and BASIS_TYPE against MSC_RES_BASIS_TYPE.
• FND_GLOBAL (PACKAGE) and MRP_GET_PROJECT (PACKAGE) — supporting objects referenced by the view environment, typically for session context and project-segment derivation.

Key Columns

• SESSION_ID / PEGGING_ID — identify the ATP session and the planning pegging relationship for each row.
• FIXED_LEAD_TIME, VARIABLE_LEAD_TIME, PREPROCESSING_LEAD_TIME, PROCESSING_LEAD_TIME, POSTPROCESSING_LEAD_TIME, INTRANSIT_LEAD_TIME — the decomposed lead-time components used in scheduling calculations.
• ATP_FLAG — decoded through FND_COMMON_LOOKUPS (LOOKUP_TYPE = 'ATP_FLAG'), returning the descriptive meaning rather than the raw code. The join applies NVL(ATP_FLAG,'N'), so a null flag resolves to the default "N" meaning.
• ATP_COMPONENT_FLAG — similarly decoded, indicating whether ATP applies at component level.
• ROUNDING_CONTROL, BATCHABLE_FLAG — decoded via MFG_LOOKUPS using SYS_YES_NO.
• REQUIRED_QUANTITY / REQUIRED_DATE / PTF_DATE — the demand context driving the promise date.
• ATP_RULE_NAME, INFINITE_TIME_FENCE, SUBSTITUTION_WINDOW — the governing ATP rule and its fences.
• EFFICIENCY * 100, UTILIZATION * 100 — resource percentages returned already scaled.

Common Use Cases and Queries

Typical scenarios include validating that ATP flags were set as expected during an order-scheduling run, and integrating ATP attributes into custom dashboards. A representative query filtering on the very attribute users search for:

SELECT SESSION_ID, PEGGING_ID, ATP_FLAG, ATP_COMPONENT_FLAG, ATP_RULE_NAME, REQUIRED_QUANTITY, REQUIRED_DATE FROM APPS.MRP_ATP_PROPERTIES_V WHERE ATP_FLAG = 'Y';

Because the view already decodes flags, the ATP_FLAG column returns descriptive lookup meanings rather than the single-character codes; consumers should compare against the decoded value or join back to FND_COMMON_LOOKUPS when the raw code is required. Additional use cases include lead-time analysis across sessions, substitution-window reporting, and capacity constraint review via WEIGHT_CAPACITY and VOLUME_CAPACITY. Since the source is a temporary table, results are session-scoped and should not be treated as persistent historical records.