Transporting Value mappings

[manish_bhalla2]

Hi,

We are using the Value Mapping replication functionality to maintain Value Mappings in a PI 7.1 system.

How do we transport the values we maintain from Dev to QA and beyond? Will these be visible to transport in the Integration Directory, or should we look at transporting the source data (and then re-replicating in PI)?

Cheers

Manish

[Former Member · Accepted solution]

Hey

You can assign a value mapping group to your value mapping and then transport this group.

Tools->export configuration objects->Value mapping group.

Thanx

Aamir

[Former Member]

Manish,

As you said you are using "Value Mapping Replication". So for this you must have written some ABAP code in your R3 side, Right?? Basically there will be outbound proxy to send the data to XI runtime cache.

Any way, In this case you need to transport the ABAP program from Dev system to QA system and then you need to run this program again in QA system in order to replicate the values into runtime cache of XI. After running the program you can see the values in XI under "Runtime Workbench----> Cache Monitoring."

But if you have created "value mapping groups" in Integration Directory then you need to transport it directly from there. From Tools->export configuration objects->Value mapping group. You can select multiple groups by pressing & holding Ctrl key.

Regards,

Sarvesh

[manish_bhalla2]

Hi Sarvesh,

Thanks for your reply. You are right, we have an ABAP program on our CRM system to maintain the values. We could potentially transport that across, along with the proxies etc to enable the same mechanism of maintenance in the other environments.

What we are struggling with is... do we transport the data across to the other environments, or do we manually re-enter and replicate in each environment? Transport of a table will probably work with an initial load, but what about delta changes that occur to the data? They are trickier to manage. It would be so much easier if the Integration Directory allowed transport from one PI environment to the next for data maintained via the replication mechanism.

However, there is an even broader issue here... as a post-go-live policy, do we ask the business users to maintain the data in Dev and transport them across the landscape, or do we allow them to maintain values directly in production?

Cheers

Manish

[Former Member]

> What we are struggling with is... do we transport the data across to the other environments, or do we manually re-enter and replicate in each environment? Transport of a table will probably work with an initial load, but what about delta changes that occur to the data? They are trickier to manage.

You have to transport the ABAP report and Ztables if any. We do not trasport the data accross other environments. Once you transport the report just run it, the data will automatically come itno run time workbech under cache monitoring.

>It would be so much easier if the Integration Directory allowed transport from one PI environment to the next for data maintained via the replication mechanism.

>

You can transport from ID only when you are using the value mapping group.

> However, there is an even broader issue here... as a post-go-live policy, do we ask the business users to maintain the data in Dev and transport them across the landscape, or do we allow them to maintain values directly in production?

The data in Dev & Production is never same so you will not transport it from Dev to PRD, so end user should maintain the correct data into production system.

Regards,

Sarvesh

[manish_bhalla2]

> You can transport from ID only when you are using the value mapping group.

That is what I was thought.

> The data in Dev & Production is never same so you will not transport it from Dev to PRD, so end user should maintain the correct data into production system.

That's not entirely true. Things like status codes will remain the same across environments.

Thanks for all your help... much appreciated.

Regards

Manish

[Former Member]

Hi Manish

You can transport value mapping as suggested by Amir. These groups will be visible in transports and you can verify.

One more thing. Transport the business system/service as well used in value mapping else you can face error after the transport. It is always good to transport all together.

Thanks

Gaurav

[VijayKonam]

I do not think the value mapping objects are transportable. You might have to configure them in every environment as per my knowledge.

VJ