How to download message mapping from PI 7.31 pack service pack 14

[former_member188831]

I tried those option Control + Shift + Alt + zero or O. and control + shift + 0 or O. Not working.

Also tried tool -> export design object and selected individual message mapping and downloaded to .tpz file , after I made some changes and when am tried with import it is not showing the  old version it still shows my changes only.

Please help me.

Thanks,

Mahesh

[former_member188831]

I could do import export with .tpz file by selecting the individual object.

I am in situation now my prod message mapping is inconsistent version with dev message mapping.

I got .tpz file from prod by selecting individual object and could imported to Dev. Dev gives me message imported successfully but not showing up the imported version.

Instead I see it find transport it shows the log and the mapping object but that version I not turning into change/edit mode or activation mode it is grayed out.

any idea ?

Thanks,
Mahesh

[Harish]

Hi Mahesh,

Please check if the mapping object is in conflict. you need to resolve the conflict with activating the desired version of the object. Please refer the below help page

Conflicts When Importing Objects - Enterprise Services Repository for SAP NetWeaver CE - SAP Library

regards,

Harish

[former_member182412]

Hi Mahesh,

Why are you taking the version from production to development, why dont you send the latest mapping or particular version which is active in production currently to production.

Coming to your questions

• Since you take the version from production and import it to development you dont find this version in development because you already have the latest version in development, for example if your development version is 11 and production version 9 then when you try to import the version 9 into development system will ignore this version because you already have higher version in development.
• When you import the mapping by default system will make software component not editable that is why you cannot change the mapping. you need enable these check boxes for the software component.

         

Regards,

Praveen.

[bhavesh_kantilal]

Hello Praveen,

Just one correction in your statement -

Since you take the version from production and import it to development you dont find this version in development because you already have the latest version in development, for example if your development version is 11 and production version 9 then when you try to import the version 9 into development system will ignore this version because you already have higher version in development.

In fact, if you import version 9, you will get a Version Conflict in PI and you would need to resolve this version Conflict.

@Mahesh - If you have imported the object from Production to Dev and it is not reflected, i would check the Conflicts tab and resolve the conflict..

Regards,

Bhavesh

[former_member182412]

Hi Bhavesh,

I gave the wrong example but system ignore the mapping which is imported from production because the development mapping version date is higher than the production.

I got this version in production currently which changed at February 10, i exported this mapping and imported into PID.

I did not see any version conflicts after i imported this mapping because development mapping version date is 6th of May that is why system ignore the imported mapping.

Regards,

Praveen.

[bhavesh_kantilal]

Hello Praveen,

This is rather interesting.

Below is a case where version conflict would typically occur,

• Same version 8 in Dev and Version 8 in Prod / QA
• Make change in QA / Prod Directly - make a version lets say 8a.
• Now make change in Dev - lets say version 9
• Import version 9 into Prod, you should get a Version Conflict in Prod
• Import version 8a from Prod to Dev and there will be a version conflict in Dev.

What happens in the above example is - a change that does not exist in the history of the object is getting overwritten and hence conflicts occur.

In the case you have mentioned, looks as the object version from Production already exists in Dev and hence it is not getting reflected as the last object..

My understanding was it would still throw a version conflict but looks like it does only if a version does not already exist. Probably a change in one of the later version of PI!.. Having said this - if this is the new behavior, your answer is definitely right!

Thanks for the clarification and let me know if the scenario i described makes sense!

Regards,

Bhavesh

[former_member186851]

Hello Mahesh,

You have two ways of doing it .

1.Using API.

2.Using NWDS.

NWDS will be easy. Refer the below link

[bhavesh_kantilal]

Do you want to revert the changes done on your mapping? If yes you can use the version history of your mapping to revert the same. Is that what you are trying?