Two APO systems connected to one ECC system

[former_member1359445]

Hi,

We are trying to figure out if it is possible to connect to APO systems to an ECC systems.

We are facing CIF-ing issues with respect to transaction data in such a scenario (using the same set of materials and plant, for this purpose), only one system is able to transfer T-data to ECC.

Has anyone worked on such scenario before ? if yes, how does the system behave fir same set of data.

Thanks

[Former Member · Accepted solution]

Hi Vinayak,

Technically distributed ECC systems will be connected to single APO system and that can achieved by assigning the logical system of individual ECC and APO system to a Business Server Group and further integration settings.

Multiple APO system will not be an efficient way to work for a Business Solution, you have an example already for that - inconsistencies will be huge in size, Performance will also be affected and you would need a high system resources/maintenance to hand them.

May i know whats the Business Requirement behind multiple APO systems.

Thanks

Vinoth

[former_member1359445 · Accepted solution]

Hi Vinoth,

Thanks for your response.

Our client wants to continue planning with their existing DP system for a while (for a particular division) before moving to new system. So there will be a overlap for some duration.

We wanted to see if both APO systems can continue with the same ECC for planning same & different materials.

BR

[Former Member · Accepted solution]

Hi Vinayak,

Considering this overlap required between the two APO systems what can be done is:

1. Integration models for transaction data between ECC and one of the APO systems (say APO2) should not be activated.

2. Publications for transaction data between ECC and APO2 (distribution definitions) should not be created.

If we do above 2 settings right from the beginning, I think this client requirement can be taken care of.

As Vinoth said above Multiple APO system will not be an efficient way to go ahead.

Hope this helps.

Regards,

Subhash

[Former Member]

We had this scenario of connecting two SCM systems to one ECC system when we were upgrading at one of our major clients to EHP3. In our case this was primarily for testing purpose and there was only on ECC system which had the right configuration and data to serve our purpose. We did encounter significant queue related issues with transaction data.

For instance whenever transaction data details is changed simultaneously  in 2 different SCM systems like production order start time , when this gets CIFed back over to ECC, ECC is unable to pick up the valid change causing a dump or queue error

So we did face significant issues in transaction data and these queues were manually deleted until we switched over to one ECC-SCM system.

My recommendation is that since DP is primarily a planning tool connect your DP to another ECC system which is refreshed daily by the live ECC system. In this way your users can perform demand planning related activities with minimal impact to existent production system.