SAP_PP_002 scheduling algorithm

[Former Member]

Dear SAP gurus,

We face to the issue that at /SAPOAPO/PPT1 during product heuristic SAP_PP_002 system generates procurenment proposals (source of supply TLane) too early creating an excess stock.

As you see from below system has generated the Purc. Req according to round value creating 91 days of supply (whereas a target is 7).

I am curious what is a scheduling principle (backward + reverse) for SAP_PP_002 in case of externally procured materials? What paramteres are taken into account?

Pls., note: GR time is not being used.

Regards, Nazar

[Former Member]

Hi Gents,

It looks like i found what is an issue about.

At product_location Demand Tab >>> Pegging subtab >>> Maximum Earliness of a Receipt i had an entri 0.

It looks like that while planning by sap_pp_002 my first receipt (as shown above, PO) did not cover the first requirement (receipt avail. date < req. date).

Maintaining Maximum Lateness of a Receipt:

We got the receipt element generated close (diiference in dates the safety time) to a second requirements, which does not create excess stock:

Q1. What else does "Maximum Lateness of a Receipt" have impact on?

Regards, Nazar

[claire_yang]

Hi Nazar,

"Maximum Lateness of a Receipt" will be considerred when dynamic pegging is used. It's for excluding receipts which are too late for a requirement. Therefore, when your planning involves dynamic pegging, this flag will be considerred, e.g.  It has impact on PPDS heuristic run, scheduling, CTM planning, ATP check, etc..

Claire

[Former Member]

Hi Claire,

As i understood this defines the ending point of pegging interval.

Anyway maintaining helped to solve the issue with excess supply.

Regards, Nazar

[Former Member]

Hi Nazar,

Please check your lot size (or lot size tab in product master for various fields like safety stock, days of supply, target stock level, reorder point etc) and planning type (whether reorder point planning with maximum stock level is being used).

[Former Member]

Dear Oz,

I found the root cause of "too eraly" receipts generation. This is because of pegging:

1. Initial situation: there is first DepDmd 153963435 on 03.07.2012 and the next req. starts on DepDmd 154019345/5 - 06.11.2012

2. Pegging Overview: we see that first req. DepDmd 153963435 has been partially covered by stock. A Purch.Ord. from 04.07.2012 is covering the next dep. demand 154019345

3. Hence when i run SAP_PP_002 system creates receipt element for the first dep. demand 153963435. The reason why it has placed it on 14.08.2012 - is 57 days of lead time.

4. Above statement could be proved from the peggimg overview, where we see that 1st dep. demand is covered by newly created purch. req.

Situation described causes me the high inventory level.

Note: when i manually readjusted pegging relationship - Purch. Req has been created on 29.10.2012; 7 days prior to the 154019345 (2nd dep.demand), because of safety days from product_location MD.

Now questions:

Q1. Why do i have such strange pegging relationship as described at pic. 2 - firmed receipt element covers late demand (not the 1st one)?

Q2. What is a solution here: should i re-adjust pegging all the time, is there any program, i may schedule prior to production run SAP_PP_002 or should i use another production run algorithm, whic one?

Regards, Nazar