cancel
Showing results for 
Search instead for 
Did you mean: 

Urgent:How to mark records as syndicated after initial load to repository?.

Former Member
0 Kudos

We are implementing Vendor scenario in MDM 5.5 SP03. We loaded around 12000 Vendors to MDM repository from SAP R3 and an inhouse Vendor management system. Now the concern is that whenever we start syndication using Java API's the system tries to syndicate everything(when run the first time), instead of the masked records. We dont want to syndicate all records manually after initial load as that would take a long long time. Is there a way to mark all records as syndicated (some field at database level) or are we missing something during initial load?

Any suggestions would be appreciated.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello nirmal:

when you create the syndication map, please check the option Map Properties -> Supress Unchanged Records.

This should syndicate only deltas

Greetings!

Alejandro

Former Member
0 Kudos

Hi Alejandro,

Even after supressing unchanged records we are facing the same issue. It seems after initial load all records are taken to be as changed.

Any suggestions from any SDN member would be appreciated.

Nirmal.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Nirmal,

If I understand the problem,

1. You load 12K records into your repository

2. The first syndication after the load obviously finds all of them as "Changed", and tries to syndicate out

3. You do not want this.

'Suppress unchanged records" option helps out from second time but not the first time.

You could try the following but it is not a complete solution:

1. To avoid the first "bulk" syndication, you can use a map that explicitly uses a timestamp comparison of a change stamp field. If you loaded today, you can design your map to syndicate any changes starting tomorrow.

2. If you can live with this hard coded comparison, and use the same map for deltas too, then with change suppression, it would work great.

The key point to remember is that Syndicator inherently keeps track of when and which records it syndicated last.

Another option (more graceful) is, why can't you run the first syndication after the bulk load during off hours to get the syndication tracker bumped up. Obviously, you would not have the bulk load every day, correct?

Hope this helps

Former Member
0 Kudos

Thanks Savitri, you had a very helpfull reply. Aparently one of my friends solved this for me.

Former Member
0 Kudos

and could you please write how did your friend solved this problem?