Sync APO landscape

[AA3]

Since our DEV, QA and PROD are not in Sync as we did not follow strict procedures for development, we have been facing trouble to maintain the systems.

Can any one suggest what are the relevant settings and config needed to sync up the whole APO landscape considering the fact that APO has built in BI.

Edited by: AAL123 on Jun 7, 2011 11:30 AM

[former_member698542 · Accepted solution]

Hi,

One suggestion is that download all the transports requests from all the system DEV,QAS and PRS and compare the requests. Then re-transport the missed transports in the respective system.

Also while transporting the requests please make sure that the transports are transported in ascending order of transport numbers.

Kindly mention what kind of issue you are facing, we can give better detailed suggestions.

thanks and regards

Murugesan

[AA3 · Accepted solution]

How do we download the requests , is there a TCODE to look at

[AA3 · Accepted solution]

In our case certain development and config functionalites were performed in each system directly.

For example - Macros created directly in prod ,

Variants of certian data load programs directly set up in production

some of the issues we face only in Prod but did not encounter in QA

process chains directly in prod

[Former Member]

Hi,

I am curious if you found a strategy to sync your APO systems up. We have a similar issue here where macros are maintained directly in Production.

Thanks.

[Former Member]

Debra (& AAL),

A curious person might wonder how the functionality was tested, before executing in Production. I would speculate that executing untested Macros in the productive client wouldn't lend itself to stability......

Macro books, with all contained Macros, are transportable. You could export them from the productive client and import into whichever destination client required. //ADVM. Select the book, then Tools > Transport Macro Books. Naturally, the Macros will only work if the underlying planning books are also similar. After transporting, it is generally desirable to re-generate all Macros in the destination client.

In General, most DP/SNP related objects can be transported via the Manual Transport Connection. //TSOBJ. Here also, objects can be exported from Prod and then imported into other systems.

You may have to ask your Basis team to provide support to export from Prod > Qual and/or Dev, if these transport paths do not already exist.

Another method to synchronize Qual and Dev environments with Productive environments is to perform periodic refreshes. Speak to your Basis team about updating these two environments. Many companies do this regularly.

Best Regards,

DB49

[AA3]

No option we are doing the manual way of listing down BI and APO ojects and plan to take baseline as production.

comparing, DEV and PROD, and finding differences and apply changes in DEV and transport to QA.