cancel
Showing results for 
Search instead for 
Did you mean: 

Avoid manual step to clear cache every time flavor moves from C to P

Ritz
Active Contributor
0 Kudos

Hello Experts,

 

We are SP14 and will be migrating to SP18 soon.

We are facing issues when ever we move our flavor from development to production without clearing cache first on production, could you please suggest how to avoid it.

As its not possible to perform these steps to clear cache first then move TR.

I can see note "SAP Note 3246963 - Flavor cache not cleared in target system after importing transport request." Is already implemented in SP14 and not relevant for SP18.

Appreciate if you could share your experience and how to fix it.

Thanks

RD

Accepted Solutions (0)

Answers (3)

Answers (3)

Thomas_Mangler
Active Participant

Hi,

we had the same issue some time ago. At that time i reported a issue to SAP.

Please check SAP Note 3246963

 

Regards,

Thomas

Ritz
Active Contributor
0 Kudos
Thanks , 3246963 I already check and see code correction in Production SP14 as well as Development SP18. We are waiting to upgrade to SP18 as found issues with hiden fields and working with SAP Support on same.
tamas_hoznek
Product and Topic Expert
Product and Topic Expert

Hello Ritesh,

Just to clarify: Are you saying that you are "experiencing issues" (what exactly?) after transporting flavors, and the problem is fixed by clearing caches in the target system?

From SP16 and up, the corrections introduced by note 3246963 are already part of the standard SP delivery, so having to clear the caches manually is unexpected. If you happen to have an example of such a situation, I'd suggest creating a support incident, with detailed description of how to reproduce the problem and providing access to the systems (both source and target).

Ritz
Active Contributor
0 Kudos

.

Ritz
Active Contributor
0 Kudos

Hi @tamas_hoznek, When TR move to production , flavor cache is not cleared on all app servers and the user which are on app server 2 or 3 , see original transaction screens, missing button etc. once cache is cleared it solve the issue. As mentioned we are in process to upgrade to SP18 , but there are few issues with SP18 and we are working with SAP support to fix those issue. In production we are still on SP14 and there we are facing this issue. 

Incident is already submitted.

Thanks

RD

Ritz
Active Contributor
0 Kudos

Hello @tamas_hoznek @Thomas_Mangler,

Does the code correction mention in SAP Note 3246963 only play role when we use TR to move flavor between system or it also work same way if we upload the flavor created in another system to production system , flavor cache will be cleared automatically ?

Appreciate if you could suggest what do SAP recommend as best practise for moving flavor between systems.

Thanks
Ritesh

tamas_hoznek
Product and Topic Expert
Product and Topic Expert
0 Kudos

The changes in note 3246963 relate to using the transport system to move objects and clear the flavor- and theme cache after importing a transport request. If you are using the export/import feature to download a flavor and upload from a local file, the updated code is not called - but then again, you should not import a flavor that was moved via the transport system earlier.

I'm not sure your exact scenario is clear here...