cancel
Showing results for 
Search instead for 
Did you mean: 

Change Tracker via Web Pane not working (when using multiple DF fields)

Former Member
0 Kudos

All,

We are using MDM 5.5 SP06, version 5.5.62.53

I have configured the Change Tracker so that I can use it in the Data Manager Web pane. I also set the configuration options of the Data Manager for the "Web Pane URL for selected records" to this link, so everything should work fine (it is working for another reporistory with just one DF field in the main table).

The main table (for which I want to track the changes on) has two DF fields. The first DF field of the main table is a look-up field (where the look-up table itself has two DF fields as well) and the second DF field of the main table is just a text field.

The URL link to the Change Tracker makes use of the parameter: searchrecord=<f:n>, as described in the reference guide for MDM Console.

When I select a record in the Record pane in the Data Manager and go to the Web Pane, then the Change Tracker is showing, but the change history for that record is not shown in the Change Tracker!!

This is caused by the fact that the records in the History table are stored with the following information in the "record" field (example): 113786=1000010 - Enfa B.V, 100075. Appearantly this is a combination of the two DF fields of the main table, and because the first DF field is a look-up it shows the values of the DF fields of the look-up table as well (including the ID of that look-up record)!!

I tried the following in the URL link: searchrecord=<f:n>,<f:n2>, but then the Change Tracker receives the following value (which is an invalid value): 1000010, Enfa B.V, 100075

How can I configure the URL link in the Console in such a way that the Change Tracker recognizes the searchrecord parameter as a valid entry (because when you start Change Tracker in separate browser it expects value of e.g. 113786=1000010 - Enfa B.V, 100075 in the "record" search field, otherwise it does not find any records).

Or do I need to change the DF fields and make an MDM-ID field to be the only DF field, and use that field in the searchrecord=<f:n> parameter???

Has anyone any experiences with this? Any suggestions how to solve this issue?

Thanks in advance,

Marcel

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

All,

It is solved as of SP06 Patch03 Hotfix03 (build 5.5.63.64).

See also below OSS notes.

The <rp> parameter should be used now in the URL link, in combination with the new version of the Change Tracker that uses the permanent record ID for looking up the correct change history!

[https://service.sap.com/sap/support/notes/1248071]

[https://service.sap.com/sap/support/notes/1245174]

Regards,

Marcel

Former Member
0 Kudos

Hi

You are right in your interpretation.

Try to make your MDM Id or some other ID such as Product Id or Business partner Id as DF.

The reason why you should not use look upid in change tracker is that you want to track changes on Main Table hence logically you have enabed Change Tracking on main table.

Same process needs to be followed for Look up tables separately in case you need to track look up table.

So make your Id as DF and then search for records based on this id. Hope this helps,.

Former Member
0 Kudos

Hi,

We are indeed tracking changes on the main table. It is the standard SRM-MDM Catalog repository where Supplier and Supplier Part Number are the DF fields of the main table. From standpoint of the datamodel these two DF fields are correct, since these two fields make up an unique record.

Of course I can change the DF field and make the MDM-ID the DF field, but we want to stick as much as possible to the standard SRM-MDM Catalog!

It would be better if the URL to the Change Tracker has additional parameters that can be filled (like the Record Contains field instead of the Record field) or that you could specify the MDM-ID as parameter (without having to change the DF fields of the main table) so that the Change Tracker knows exactly for which record we require the change history!

I will investigate futher and see if we can live with the MDM-ID as the only DF field.

Thanks anyhow for your reply.

Regards,

Marcel