Migration to WFA permission to RBP permission: tree security section is missing

[gattara]

tree-security.jpgIn Migration from WFA permission to RBP permission, I am missing the tree security section in the grant this role to in manage permission role, can someone help, thanks. I followed the implementation guide

SF_ANA_Migr_WFA2RoleBased_User

I already reached out to sap experts on that matter and they suggested to reach out to a WFA expert or to ask my question here because we already verified and troubleshoot.

[former_member47568 · Accepted solution]

Hello Gina.

To confirm what you probably already know, the Tree Security section is a long way from the other Analytics permissions in terms of page space. It is in the Edit Granting section, right at the bottom.

The most likely reason why it might be missing is if RBP integration is not enabled for Measures and Dimensions. This is common as many instances only use it for Functional and Optional permissions. You can check this in "Manage Workforce Analytics" in the Admin Tools menu; seek help from an admin if you do not have access.

Another possible reason is that the WFA cube data has not been synced in BizX, and therefore BizX does not know what the dimensions are. A cube info sync button exists in Provisioning -> Company Settings, and another tool in Admin Tools is named "Manage WFA Permission Artifacts Sync Job" and can be set to run specifically on "Structural Dimension(s)". Running one of these might be necessary depending on the circumstances, especially if RBP integration has been applied very recently to your instance.

Best of luck with your troubleshooting based on the above. We're here in Cloud Product Support if you need further assistance.

[gattara · Accepted solution]

Thank you Alex for your answer, very helpfull, I will troubleshoot and see.

[gattara · Accepted solution]

Hey Alex, I performed all of the aboves and tree security is still not available .

Thanks

Gina

[former_member47568 · Accepted solution]

Well done going through it all. At this point we can probably go no further in the general case and you should raise an incident so we can investigate your instance directly.

Regards.

- Alex

[gattara · Accepted solution]

Thanks for you help