Exporting syndicated records from MDM

[Muniyappan]

Hi,

i am working in PI. we integrationg mdm using pi with JMS systems.

our project development is done.now support is going on.

every day nearly 100 records have been sysndicated from mdm to other application through PI.

At the end of the day i need to send the report saying that this many records passed from PI.

And i have to list down the records in xl sheet which has nearly 20 columns.

to do this i need to go sxmb_moni to get the xml and copy paste the records in xl sheet.

for one records i need to do the copy pasting for 20 times(20 columns).

is there any was to export the records from MDM which are sydicated for perticular day?

like simple example: i have 10 records which are updated today for 4 times.

in the archive folder i will be having 40 xml files once the records are picked by PI.

i want to export these 40 records into xl sheet.

please help me on this.

[Former Member · Accepted solution]

Hi,

If i understand correct,only those records that get updated on day to day basis are syndicated.

I am not sure if a field "Update Date" is available (Pls check with MDM resource). If available, you can select the records based on "Update date" and have them syndicated with all columns/fields into excel sheet.

Second option would be to open the xml file that is obtained from PI.

When you open an XML file in Excel, you are prompted to select one of the following methods to import the XML data: 

• As an XML list
• As a read-only workbook
• Use the XML Source task pane

Select to open an XML source document as a "read-only workbook".The rest of the tags are sorted alphabetically and placed across.

Let me know if this helps.

Regards,

Ali

Message was edited by: Mir Ali

[Muniyappan · Accepted solution]

Hi Mir Ali,

first option

we have update date  field in mdm.

my question is for example i have record which is having the country Id 100.

if this record is updated 3 times on 20/06/2012.

then i can see only one record for country Id 100 not three records on 20/06/2012.

i want every version of the updated records as it is present in the archive folder.

second option

opening xml as read-only workbook it is working as you said.

but i have two xml files one has 15 columns(elements) and another one 20 colums(elements).

if i do the same for these two files while combining it will create inconsistency.

Regards,

Muniyappan.

[Former Member · Accepted solution]

Muniappan,

I think u must find a possible workaround with excel itself. I do not think of a better way.

[former_member193350 · Accepted solution]

Hi,

You can also syndicate the updated records using "Suppress Unchanged Records" option in MDM Syndicator.

This will syndicate only those records that are updated from previous time stamp.

Regards

Prateek Agarwal

[Former Member]

I guess you should just branch out & keep appending this data to a single file from within PI, or write another PI feed which reads in the same file as feed 1 and appends the data you want to a single file on a daily basis.

But a larger question would be why would you want to do this, just for auditing, change tracking? there can be many ways to achieve this anywhere from simple unit scripts to custom middleware feeds or just MDM change tracking depending on volume I guess.

[Muniyappan]

Hi Sudir,

Yes. you are correct. it is for change tracking.

My receiver is a mainframe systems. they are not receivig the messages properly.

To cross check that we are noting the records in xl sheet which are processed in xi and send it to customers.

then they will verify the records with respect to xl sheet.

since it is master data we thought it is going to be only 2 to 5 message per day.

then it is possible to note down all the messages.

but now it is increasing like anything 300 or 500 messages per day.

we are convincing them that this is not feasible.

may be they can take export of records from mdm data manager which are syndicate on perticular day and they can verify it from the receiver side.

Regards,

Muniyappan.

[Former Member]

Hi Muniyappan,

Since your requirement is for Change Tracking of records, then you should enable "Change Tracking" in MDM. But make sure to enable it for critical fields only as it requires memory and affects performance of the system also if you have enabled many fields for change tracking.

Then there could be a Portal application designed to check changes and display at user screen.

It will track all the changes done to those fields and you can see them whenever you want.

But as you say that daily master data changes done are 300-500 messages a day(and increasing), so i don't think it is feasible to cross check for data synchronization of these many records manually and that too taking one record at a time. So what you can do is that take latest version of updated records from MDM and the same from target system(in single file), then you should can develop a program which would return the mismatches in the data of source and destination. Then you can manually check and rectify those as they won't be much in number. In my opinion, this should be the feasible way to ensure data synch in both the systems considering number of records processed daily. Let me know if it is of some help to you.

Regards,

Ankush Bhardwaj

[Former Member]

Hi Muniyappan,

Please detail how data creation/Updation approval is taking place.Which workflow are you using?

Thanks,

Ravi

[Muniyappan]

Hi Ravi,

Webdynpro java team developed screens for mdm.

users use these screens using portal application.

say user is at the country screen which has all fields related to country.

if the country exists and user want to change something that is update.

if not extisting then then user can create new one that is create.

workflow:

1.requestor-will request for create or update the country

2.DataSteward -will approve the country

3.Specialist-will approve the final master data of country.

thanks.

Regards,

Muniyappan.

[Former Member]

Hi Muniyappan,

Lets discuss this solution -

I think you can pick these multiple xmls form a new location - this will be the syndicated location of data.What you will have to do is modify the current xsd and in map use the configuration "send all the xmls in 1 file",this map wil be linked to a new port.This will NOT modify the current solution.This is only for a last sydication step it can be on a daily/hourly basis.This will send the data to new folder.

Advantages:

All xml in 1 file

Since you can make fields/segments required you will have all the 25 columns in the data

You can open with Notepad/Excel and have all the data in one file

Now there are limitations too:

Your requirement is to have all versions of a record in the file.If you have hourly syndication it might not have any changes done in between,it will only send the last version.

However this is near accurate solution and the risk can be mitigated by checking xmls from archive.

Thanks,

Ravi