PowerView is Off (0)Arman (Available) Contact Us Help

Document Display Give Feedback...

Search: Rank in sourcing rule

Back to Results

API mrp_sourcing_rule_pub Errors Rank cannot be changed because sourcing rule is already assigned (1442633.1)

MRP Planned Order Quantity Is Incorrect When Using Multiple Rank Sourcing Rules and ASL Supplier Capacity (1950688.1)

How to enforce a hard/blind sourcing split in a constrained plan without considering the constraints? (1349479.1)

Generate Sourcing Rules And ASLs From Blanket Agreements Ranking not Behaving As Expected (1678447.1)

Planned order not split among suppliers according to Sourcing Rule Allocation Percentages in an ASCP unconstrained Plan(292335.1)

No Source Supplier information seen in the plan even though the item has a sourcing rule assigned. (1495097.1)

MRP Does Not Consider Sourcing Rule With rank2 Sources

When Same Allocation % Is Given As Sob (1168143.1)

MRPFDDSR Sourcing Rules Form Errors APP-MRP-22016 Overlapping in date range occurs at Effective Date(1546895.1)

MRP IS NOT HONOURING ALLOCATION PERCENTAGES IN SOURCING RULE (309425.1)

Memory Based Snapshot Fails With ORA-01455 in msclis_load_item_sourcing (1399253.1)

Load More... Back to Results

In this Document

Goal

Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

APPLIES TO:

Oracle Materials Requirement Planning - Version 11.5.10.2

and laterInformation in this document applies to any platform.

***Checked for relevance on 08-Nov-2013 ***

GOAL

MRP Does not consider Sourcing Rule with Rank 2 Sources when same allocation percentage is given as SOB

SOLUTION

The sourcing rule allocation is highly dependant on two

factors.

One the Value of profile : MRP : cut off history days and

allocation happened to the sourcing suppliers/orgs till then.For ex: In your case you have few splits in rank 1 and rank 2.

But the plan is going ahead with honouring split only at rank 1.

The reason here is its intended as teh MRP : cutoff history is zero.

The requirement for the planning to shift to next sourcing arises only if it gets an glimpse to see the sourcing history for each of the sources in the same rank and across the rank.

Suppose we set the profile MRP: cut off history to say 5 days,

then plan just tries to intially load all the sourcing on the first highest allocation percentage source on rank 1 and once it

reaches the pecentage, say we have 60% and 40% in rank 1 and 100% in rank 2, plan based on requirements loads intially

all supplies to rank 1 60% supplier by looking at history of 5 days, now when it reaches 60% loading , it starts loading the

second rank 1 supplier till 40% and this also by looking at 5 days history

Now when the sources at rank 1 are full , it goes to second rank.

Was this article helpful?

Document Details

Type:

Status:

Last Major Update:

Last Update:

HOWTO

MODERATED

Nov 8, 2013

Nov 8, 2013

Related Products

Oracle Materials Requirement Planning

Information Centers

No Information Center available for this document.

Document References

No References available for this document.

Recently Viewed

MRP Does Not Consider Sourcing Rule With Rank2 Sources When Same Allocation % Is Given As Sob (Doc ID 1168143.1)

To Bottom

Yes

No

MRP Planned Order Quantity Is Incorrect When

Using Multiple Rank Sourcing Rules and ASL Supplier Capacity [1950688.1]

WS: 34: How To Mark MRP Planned Orders As Firm Planned [636011.1]

E1: 34: P3411/R3411/R3450 MRP Detail Messages - Understanding and

Use [625973.1]

E1: 34:

R3482/R3483 Understanding & Use of MRP (Material Requirements Planning) [626116.1]

MRPSCPWB MRP Workbench - Hundreds of Released Wip Discrete Jobs With

Action = Cancell Unexpectedly

Copyright (c) 2015, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

Dashboard Service Requests Patches & Updates CommunityKnowledge

Page 1 of 1Document Display

13-05-2015https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=...