Symptom
How do we set the visibility for MDF Objects to ensure that these objects are visible for external onboarding users?
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors Onboarding
Resolution
To set the external user visibility, please add a rule under initialize rules or save rules for each MDF object:
- Go to Admin Center > Configure Object Definition
- Search for MDF Object Name > Click on Create new rule icon (+)
- Select the "Rules for MDF Based Objects" option under the "Metadata Framework" section
- Enter the below Fields and Click on the Continue button:
Rule Name: provide any name
Start Date: provide a current date or any past date
Base Object: select the object that has been noted down in step 2
Purpose: Initialise/evaluate - Set "Always True" for if condition and in then block Set
'mdfSystemexternalUserVisibility' field to 'yes'
- Navigate to the Configure Object definition page (Go to Admin Center > Configure Object Definition) select the object definition noted down in step 2 and click on the Make correction link (Take Action-> Make Correction)
- Click on the Initialise/Save Rules dropdown, select the created new rule, and save the object definition
Root Cause:
The issue occurs because external user visibility is not enabled for the Payment Information object. When the external onboardee submits their personal data, the system attempts to create or update Payment Information. Since this object is not configured for external visibility, the system cannot properly evaluate existing records, which results in a duplicate save attempt and triggers the database error related to a unique constraint violation.
Keywords
PaymentInformationV3, Payment, Information, MDF, Object, External, User, Visibility, Visibility, Rule, Object, Custom, Object , KBA , LOD-SF-OBX-EC , Integration EC - MPH, Hire , How To
SAP Knowledge Base Article - Public