Symptom
- "No Permission" error when saving data via MDF portlet.
- "No Permission" error when creating data via Manage data.
- Can I set the externalCode to Not visible or ReadOnly for an MDF object?
- When editing a MDF portlet in the employee profile it returns the following error: 'No data available or you do not have the necessary permission.'
Environment
- SAP SuccessFactors HCM Suite
- Metadata Framework (MDF)
Reproducing the Issue
This issue can occur in two places, Manage Data and in MDF portlet in People Profile Page.
- Go to employee profile
- In the portlet click on Edit
- Change the data
- Click in save, the error appears:'No data available or you do not have the necessary permission.'
Same error can be seen if instead of Edit you select the History icon -> Insert New Record
Cause
There can be different reasons why an user can receive the No Permission error on the MDF object
- externalCode has been set as "Read Only" or "Not Visible" on the Configure Object Definition
- The editable option for externalCode on the configured UI in Manage Configuration UI page has been disabled or the field has been made invisible (check for both the parent/associated object)
- Deleting the externalCode field while configuring the UI for the object (this can be for the parent/associated object)
- If the object is RBP secured, then the create/insert/correct permission has been disabled for the object. (Actual Permission Issue)
- If the object is RBP secured and you have the "insert" permission but not the "correct" permission the permission error will show when clicking in Insert New Record in case there is already a record for the effective date you try to add. This is because the system will convert the insert into a correct since there is already a record for that effective date
- One target population grant the permission to:exclude Granted User from having the permission access to him/herself, and another:
everyone in self. These two target populations that grant the user permission to create and insert in this MDF are contradictory causing an inconsistency. - A field from the Child Object is placed in the Parent Object section in Manage Configuration UI
Resolution
To investigate the No Permission error when creating/saving MDF data check for the following permissions on your object definition:
- Check for the permission on the externalCode of the object (either parent or the child) has been set as Read Only or Not Visible.
- Verify the UI configured for the MDF object has the externalCode field available and editable (for both the parent and the child object)
- Check for RBP permission on the object for the affected user. (Note: if you have the "insert" permission and not the "correct" permission the error will show if there is already a record for the effective date you are trying to add)
- Check the target population for the MDF object
- If all the above are correct, creata a new UI for testing purpose and replace the old one in the People Profile and retry to add data in the object. If you can add data with the new UI, the previous UI configuration was causing the error.
Exception: ExternalCode field can be hidden for child object when it has Data type = AutoNumber
See Also
Keywords
MDF, Metadata Framework, permission, mdf data, no permission error, custom MDF , KBA , LOD-SF-MDF-RBP , RBP Permissions on Objects , LOD-SF-MDF-UI , UI Config, Layout & Rules , How To