Message Mapping - Fix Values Transport Issue

[Former Member]

Hi,

There are few fix values in the Message mapping which is running fine in D, Q and P.

As per an enchancement, couple of additional values are keyed into Fix values of the Message mapping.

Exported the object into the Export directory.

Basis had moved the .TPZ file to import directory of Q, and imported into IR and activated.

The additional fix values in the MM are not reflected into Q.

Have tried exporting individual object (MM) as well as the entire namespace .

No Luck.

Can any one help me identify what's going wrong would be great...

Thanks,

Rao

[Former Member · Accepted solution]

Rao,

In the BPM editor there is a menu item which describes history (i think this is the 1st menu item).

Please check these on the D and Q environment.

It looks like your have a problem there, that the history version on D is lower then on the Q.

[Former Member]

Rao,

Just change the D version to ensure that this is on a higher version than the Q.

GReets

[Former Member]

Hi there,

Pelase ensure that the version on the Q environment is higher then the one on D.

At some of oour customers there were some amnual changes done and the version on Q was for instance 4 and the version on D was 3. So the version 3 was overwritten on the Q instead of creating a newer version.

Just edit the D version and ensure that the version is at least 1 higher as on Q.

Greets

[Former Member]

Rao,

One thing that comes to mind is that the object may have been edited in your Q system through the Integration Builder manually, before importing the new .tpx. If this has happened, a version confilct will occur when importing the .tpz. You can check this by opening the message mapping in your Q environment. It displays a 'version conflict' and you get the option to select one of the two versions.

Kind regards,

Koen

[Former Member]

Koen,

Kindly explain what we are suppose to do in case of version conflict.

Thanks

Rao

[Former Member]

If there's a version conflict, the mapping contains a button in the header with caption 'show ... version'. This allows you to compare the two conflicting versions and you can activate one of the two.

For details, see [Saphelp - Version Conflict|http://help.sap.com/erp2005_ehp_04/helpdata/EN/47/65993f7717fb47e10000000a114084/frameset.htm]

Kind regards,

Koen

[Former Member]

Hi Rao,

It seems the problem is with the Save,

when you enter new values, it will not be saved by simply clicking OK on fixed value table, so do like this

open your MM and add the new values to fixed value table save it and do some changes in the Description of the MM, so that MM will ask you to save and activate. now save the MM and activate it then export it.

Thanks...

Karna...

[Former Member]

Koen,

I dont see the mapping object under version conflicts tab.

But is there any way to check the versions in D and Q ?

Thanks

Rao

[Former Member]

Rao,

You can see the version of any object in the [Object History|http://help.sap.com/erp2005_ehp_04/helpdata/EN/47/65993f7717fb47e10000000a114084/frameset.htm].

I think you should also verify Karna's suggestion: sometimes 'small' changes are not saved. To verify this, test the mapping in Development for the new values.

Kind regards,

Koen

[Former Member]

Koen,

Thanks for the reply.

As you said the Object version in D is same as the object verion in Q which might be the reason the mapping changes are not reflected.

I have made changes in Object version 21 of D. While the basis is importing the file and activating the object in Q, The object version is still shown as 20 in Q and the changes are not reflected.

Please help....

Thanks

Rao

[Former Member]

Rao,

This can mean several things:

- The export does not contain the right objects (check in tools -> transport finder in D)

- The import fails (check with basis and also tools -> transport finder in Q)

- There's a version conflict as mentioned earlier

- The changed code is not activated in D before exporting

- There's a problem with the cache in Q (check sxi_cache in Q)

Kind regards,

Koen