How to transport Variant Configuration through the landscape

[tvdz]

Customer question: S/4HC Extended.

Customer has re-enginereed tVariant Configuration in S4 manually. However, we are looking for a mechanism to transport these re-developed models through the landscape.
Is there standard functionality available to do this?
What is the standard approach for this?

Thank you, on behalf of my customer

[aditya_palekar]

I have a requirement where the variant configuration import into subsequent systems in the landscape like Quality and Production is controlled via a workflow process. Would you know if this is possible? So the ALE model is triggered only if the workflow is approved by someone which also means that no one can directly trigger the ALE interface without an approval

[former_member132187]

Hello Twan,

The best way to handle the transport of the VC model is to adopt the approach for master data transportation if already defined in your landscape. This is because VC model just consists of master data like material master, variants, bill of material, VC functions, classes, characterstics etc.

If you are open to adopting a new strategy, please evaluate ALE as this is extended and with in SAP landscape.

Please use SALE t-code to setup the ALE integration.

The following are message types that you may consider for integration.

1. Characteristics and its values: CHRMAS

2. Classes: CLSMAS

3. Variant Table Structure/Content: VTAMAS

4. VC Functions : VFNMAS

5. VC Dependency/Constraint Objects KNOMAS

6. Constraint Nets DEPNET

7. VC Profile CNPMAS

8. Materials MATMAS

9. Classified Materials CLFMAS

10. Bill Of Material BPMMAS

You may need other message types depending on the VC model/Functions that's using the master data.

Also, I advise disabling the ALE after the integration set up as normal so that you can trigger transport only when you need it on demand. This will give a bit of stability across the landscape.

[a__engfehr]

Hello twan.zanden,

I have a few things to correct and add to the previous post.

3. Variant Table Structure/Content: VTAMAS >> This is structure only. Content is VTMMAS

11. You will also want to set up a user interface type, VCUI_SAVEM

12. You can transport pricing conditions using T-code VK13

13. You can transport cositing conditions using T-code MEK3

14. Routings LOIROU (T-code POIM)

Here is a link with many of the T-codes.https://blogs.sap.com/2013/09/04/sap-vc-master-data-distribution-using-ale/

Also, once you get ALE setup you can look at transporting an entire model using Product Data Replication by bundling your model into a Knowledge Base.

https://help.sap.com/viewer/c3a3d119b64a497d9ce8e9b6531404db/6.05.17/en-US/4929ba538c95b54ce10000000...