VC configuration source system

[akrason]

Hello,

We are in ECC6 still before S/4HANA conversion.

Prior to this changeover, we would like to implement in ECC6 production a simple model of sales price configurator.

We are happy with the mockup for variant pricing that we have prepared and evaluated in our sandbox.

Now, we would like to implement it in production.

We have 4 systems, development included, which are periodically refreshed starting from production:

- Production

- Test

- Development

- Sandbox.

Therefore, we need to decide where to maintain (the source) data for our configurator.

At first, we thought about production. Most of data is rather master entries (classification). Of course, we have constraints and configuration profiles but only few customizing transports. The advantage is the copying of these data during our system refresh. The disadvantage is that in case of configuration model changes (enhancements, new variants, etc.) we will have to make the adjustments in test or in sandbox and then report them manually to production.

Is there any other technique (copying tables, exchanging IDocs, other?) to keep our system landscape simple before S/4HANA conversion but still to be able to benefit from sales price configurator in the meantime?

[Michael_W]

Hi.

If we are talking here about variant configuration model:

Maybe google for 'sap vc golden client' to learn more about best practices and google for 'sap product data replication' to learn more about the PDR tool that should be used to transport product models.

But I can't remember anymore if PDR was supposed to also distribute variant condition keys or only the assignments of keys to cstic values or none of them.