Track Changes on IBP Master Data

[bkoll]

Hi all,

I'm currently looking into the functionality to track changes to Master data in IBP. The reason for that is, that we have a manual process in place to flag our planning combinations. We would like to track those changes in order to see who did the change. The functionality is described here.

However, SAP is recommending to not use this functionality to track general changes due to possible performance issues. Did anyone here already used that functionality and can give me some insights on the volume and it's impact to performance?

Thanks in advance

[sap_km]

We are using this for only one attribute with the retention period of 30 days and are not facing any issues.

[former_member654033]

Hi,

Please check, if below new feature can be of any help (Relevant for changes made in master data workbook from excel) and you can see the details in application log.

https://help.sap.com/viewer/5437585031a24ca0bf67f833f7b940e1/2111/en-US/c49c7e5e2170425ea8b7114a9cca...

Thanks

Girish

[SatishWaghmare]

Hi bkoll

The version copy is another alternative you could use to keep the copy of master data and use that for cross reference as necessary. Of course it comes up with some limitation, but much easier alternative in terms of doing the version copy and then using that from end user's point of view.

You can schedule version copy job to copy Master Data from Baseline to another version.

Hope this will help.

Thank you

Satish Waghmare

[AyanBishnu]

Hello bkoll

SAP's recommendation is absolutely correct. If you enable this feature then IBP system creates incremental master data snapshot in a cronological manner. In the background from a database perspective everytime a change is made a change pointer is generated which saves the master data snapshot. One snapshot will almost increase the DB size by 60 to 70% of the initial MDT size.

This will result in data recdundancy and will increase the load time and processing in IBP exponentially. You might need to look for alternative approach, one of which could be using Odata service to extract master data snapshot (e.g on a daily basis) and store it in any data lake ( BI or Azure BI) and then make it available to users as reports.

Hope this helps

[Adi_Janjanam]

Hello

[Adi_Janjanam]

Hello Ayan Bishnu, " One snapshot will almost increase the DB size by 60 to 70% of the initial MDT size', can you please help us understand how can we track the increase in MDT size which you have mentioned