If Wrapper and Field criteria is enabled together at the same time, then Wrapper association is displayed in the invalid admin alerts
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Employee Central : Association
Reproducing the Issue
Field criteria for Cost center to dept association is added to CDM and SDM.
Now add a dept wrapper object in the cost center object definition
Now go to Dept D and have association between, Dept D and Cost center C
Now go to the cost center GO- C and add another association: B and save.
Select a user: nsanders, add cost center C, now dept D will only be displayed in the dropdown(as field criteria is being respected). So, select dept D and save job history.
Go to admin alerts for cost center and see that Cost center association B is displayed in invalid admin alerts
If both field criteria and the FO Wrapper object is configured for association, which one takes precedence?
In current behaviour, Field criteria is taking precedence as expected.
Expected behavior : Field-criteria configured association should take priority
Association, Wrapper Object, FO, GO, Employee Central , KBA , LOD-SF-EC-PRV , Provisioning Changes , LOD-SF-EC , Employee Central , Problem