Incorrect Sourcing: CTP & Block Planning

[andy_yeri]

Experts - dealing with the below situation

Master Data set up –

Finished Good A, consumes component B @ Plant # 1

We use CTP with Block Planning to produce Matl B.

Component B @ Plant # 1, sources of supply are –

Plant # 2 – where B is made on the Machine

Plant # 3 – where B can be procured from, but Plant 3 again procures it from Plant # 2.

Plant # 4 – where it can also be made on the machine

Transaction data -

Sales Order for “A” @ Plant # 1, entered with a RDD (Requested Delivery Date) – 12/01/2014.

Requirement for “B” driven to Plant # 2 with a date of 11/05/2014 (based on transit times).

With a BACKWARD + REVERSE scheduling setting on the strategy profile, the system doesn’t find a right block to meet the Requested Customer Delivery date, so, it skips Plant # 2 as the source of supply & goes to “other sources”.

Plant # 3 & 4 are set with the same priority (External Proc Relationship), so system goes to Plant # 3 & finds that it is again/in-turn sourcing from Plant # 2 & is going to delay the RDD. Keeps looping further. Finally, it confirms the Order for a much later date via Plant # 3 (sourcing from Plant # 2), even though sourcing via the priority Plant # 2 would have been earlier.

So, contrary to the standard SAP CTP theory of "meeting the Requested date with the least delay" the system seems to be delaying the customer requirement.

Expectation would have been to come back to Plant # 2, after all the gyrations & confirm with least delay to the order dates.

Any clue from your side?

[Former Member · Accepted solution]

Hi Anand,

This is CTP tries to meet demand and chooses source with least possible delay but when you combine with block planning and specially when it reverses scheduling direction this logic is not respected thats what we also observed in past and thing is if you reach out to  SAP SAP might come back saying its standarad.

Regards,

Santosh

[andy_yeri · Accepted solution]

Hi Santosh,

I agree. We could only hope that such things get ironed out in the future EHP's.

[andy_yeri · Accepted solution]

Hi Santosh,

Also wanted to add - this however, is contrary to the std SAP help documents, that claim SAP will evaluate the results of the CTP check carried out using all the sources & pick the one that gives the product "earliest". I've read this in the CTP with Finite Planning document somewhere.

Like this t-lane situation, we've a similar situation on how the system picks the Blocks while attempting to match Customer requirements, as well -

If the Customer Request date is say 01/15/15 & there are 2 Blocks (of matching characteristics), one on 12/19/14 & another on 11/09/14 (both with enough available capacities), the system picks & uses the 1st block it finds while doing the BACKWARD + REVERSE check (12/19/14) & in the process delays the customer order by a week (transit time - 30days to the customer). It would have been highly helpful for the system to recognize that the Order was getting delayed, trigger another ATP & find the 11/09/14 block, which would have met the Customer reqt correctly.

Did you interact with SAP on the 1st issue & did they come back saying it was the standard behavior?? Would be interesting to see your exhanges.

[Former Member · Accepted solution]

Hi,

No We did not interacted with SAP with a OSS message as such but we took expert consulting help from SAP GDC and  both the problems  discussedwere finding block which delays confimration and not finding source with minimum ldelay. SAP GDC told when you combine CTP with block planning this is standarad and any sort enhancement will be very complex to handle.

Regards,

Santosh