This content has been marked as final. Show 6 replies
goal is similar to default profile. only difference is on maintainence. In case of default profile( which has same name as resource object name) whenever any change happen on RO you need to re-generate reconciliation profile which basically update the Horizonatal table (RA_xxxxx). In this case if you have multiple child table attached on RO and if any changes on child table then re-generate is not an easy job. First you need to drop all (RA_xx ) tables associated to the recon profile along with RA_UD_xx tables. Then you can re-generate using “create Reconciliation Profile”. Which is very much tedious task.
That’s why we have option of nonedefault profile which can be managed by MDS export/import utility.
Yes, But where do we specify now use this nondefault reconciliaiton profile?
try defaultProfileFlag="true" in the profile xml
few things to be consider here
1. file name should be same as profile name element of recon-profile i.e. <generalconfig .... name="Modified AD User"
2. do not change the element value i.e. objname="AD User"
3. update/create schedule task - the Target Resource Object should be same as profile name i.e. Target Resource Object=Modified AD User
Run the reconciliation..
Yes, it's working now.
Target Resource Object parameter value in reconciliation task should be same as profile name i.e. Target Resource Object=Modified AD User