Using ALE to synchronize Variant Configuration data from Production to Dev

[Former Member]

SAP Gurus,

We are trying to move away from opening our production environment every time with need to add new Variant configuration for products.

In order to do so, we need to ensure that our development and staging systems are in line with production LO-VC data. We have been looking at a possible ALE solution but I would like to get other suggestions.

Any thoughts you may have with regards to either pros and cons of ALE, or another solution we may have overlooked. If your clients are transporting Variant Configuration to production, what method are they currently using to ensure data consistency between environments.

Our landscape currently has two production environments for two separate business lines but both use LO-VC therefore we would like to standardize the process.

Thanks and Regards,

Kevin Webb

SAP SD Senior Consultant

[Former Member · Accepted solution]

Hi Webb,

General its a complex process to transport VC but for system consistency you can:

1. do the changes Manually in each system

2. Use ALE idoc process to transport.

But ALE transport generally used for fresh VC transport, if the VC already present in transporting system, it may cause inconsistency. Hence if you want to transport some changes then I can suggest you to do MANUALLY.

But if you are transporting VC freshly in each system, go for ALE.

try and revert

[Former Member · Accepted solution]

Thank you for your quick reply. This has been very helpful

Kevin