cancel
Showing results for 
Search instead for 
Did you mean: 

PPDS plant by plant roll-out in a Live ECC system

Former Member
0 Kudos

Good day colleagues,

We have a customer that is currently live with 2 plants in ECC only. They are rolling out a 3rd plant but this time PPDS will be in the scope of that plant (the 2 others will be on PPDS a a later date).

They are running into an issue when using STO's between an ECC plant and the new ECC-APO plant, here is the issue:

-


in order to have the STO taken into account by the planning run in APO-PPDS of NKF(Plant planned in APO) an a ECC plant, the receiving plants must also use APO for planning.

As an example : LPlant ECC (plant 1121 planned in ECC) is requesting rolls from Plant-APO (plant 2041 planned in APO).

Plant 1121 initiates Stock Transfer Order (supply element in 1121) that is seen at Plant APO-2041 (as a requirement at 2041). Because Plant-1121 is using ECC this STO is seen at Plant-APO-2041 in ECC.

However it is not seen at Plant-APO-2041 in APO-PPDS. Therefore, as the planning run for Plant-APO-2041 is done in APO-PPDS, the STO requirement is never taken into account.

This means that until all plants are in APO the STO scenario cannot be implementd and the classical process (Sales order / Purchase order) must be used."

-


My question is what is based on your experience the best way to fix this issue between an ECC plant and a ECC-APO plant. You have to take into acount that we cannot change the roll-out schedule nor the scope.

One th question we are asking ourselves is : could we not acivate the CIF on the none APO plant (which would bring the elements in APO and at the same time continue running regular ECC-MRP in that plant ?

Thanks in advance for all your comments.

Eric

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks colleagues for your answers, I will keep this question open to see if we have other colleagues going in the same direction.

Eric

former_member209769
Active Contributor
0 Kudos

Hi,

I have not worked much in PPDS, but for an order element that has a source and destination location, you need to have both locations in the APO system. The source and destination should be connected in APO through the Transportation Lane, and materials should exist at both the ends.

If your only requirement is to send STO created in R/3 to APO, then you would need to have the corresponding plants, materials, (would automatically select Special Procurement to create Transportation Lane in APO). Then you also need to include PO (Purchase Orders) in an integration model.

Without this very minimal setup, you can't use STO in APO.

Thanks - Pawan

Former Member
0 Kudos

Eric

You can do what you suggested - Get both plants CIF'ed to APO as locations. Activate Purchase Order CIF Integration model for both plants. Other integration models can be for 2041 only. Run PPDS for 2041 only. Plan 1121 in ECC.

Rishi Menon

Former Member
0 Kudos

Eric,

Well, first, rollout schedules can ALWAYS be changed, depending upon who wants it to be so. However, I am guessing that you have no say in the matter. Which is usually the case for analysts.....

In order for an STO to work in APO planning, you have to integrate:

Source plant (master data)

Destination plant (Master Data)

Material Masters (Master Data) for both plants

Vendors (if used)

Purchase orders/Purchase Reqs (Transactional data) for both plants

Purchase Info Records (if you have any)

Planning does not have to be done in both plants in APO. You can continue to use ERP planning by refraining from changing the Material Master to 'X0'. You do not need to send stock over for plants that will continue to be planned in ERP.

In this scenario, your STO/STPurq's are created in ERP using ERP planning methods. If you are also implementing GATP in the source plant, you will need to set up GATP for STOs/STPurqs as well. The STOs are integrated into SCM, but no planning is done in the destination plant in SCM.

To summarize, you probably just have to create or modify a few of integration models to make this work.

Best Regards,

DB49