Job Profile Builder - Legal Entity Specific Content

[meldeeb86]

Background & Requirements statement:

In today’s diversified organizational landscape, managing competency structures and job profile content within SAP SuccessFactors can pose significant challenges.

I will try through this solution to full-fill requirements where multiple legal entities (Same Instance) can independently create and edit their own Job Profile Builder (JPB) content along with Competency Structure objects (e.g., Family, Roles, Competency, Role-Competency Mapping, and Role-Job Code Mapping...etc). By following the below steps, organizations/Legal Entities can achieve a streamlined and secure way of handling job profile data independently in same instance.

Solution step-by-step :

1. Defining Legal Entity Custom Field in Desired Job Profile Content Objects(Family, Role, Job Responsibility...etc)

• from Object Definition: search for desired object. In our example here is Family then Take Action>Edit
• Scroll down and select a field name for your custom field (cust_LegalEntity) selecting Generic Object as data type then click details for more attributes changes (i.e make field as mandatory, label…etc)
• Valid Value source to be “LegalEntity” then “Done”

• Securing Family object: by selecting Yes in Secured field then select desired permission category.
• Defaulting legal entity based on logged-in user same as mentioned in below business rule and assign it in initialize Rule (it’s mandatory step since JPB UI is not supporting any custom fields visibility)

 Since Legal Entity (custom field) added to our desired objects will not be visible through UI, Ensure these steps are followed for both job profile content objects and competency structure objects to maintain consistency.

2. Restricting Job Profile Builder Associated objects:

We have two primary job profile objects—Family & Roles—each with their associated objects require specific levels of access restriction. Thus, when a user attempts to map data for any of those two objects, only the data created for their respective legal entity will be visible. We can implement this by following these guidelines:

let's see how can we restrict Family associated Objects based on earlier configuration:

i. Competency (object ID: FamilyCompetencyMappingEntity)
To restrict visibility to only Competencies created within the current legal entity, use field criteria. In the Competency object details, scroll down to the field criteria. The source field name should be "cust_LegalEntity" (custom field for Legal Entity) in Competency, and the destination field name should be "parent.cust_LegalEntity," where "parent" refers to the Family object.

ii. Skills (object ID: FamilySkillMappingEntity): Apply the same field criteria method used for Family-Competency mapping above.

Now, follow the same steps for all associated objects for the Role object:

i. **Competency (object ID: RoleCompetencyMappingEntity)

ii. Skills (object ID: RoleSkillMappingEntity)

iii. Talent Pool (object ID: RoleTalentPoolMappingEntity)

Note: You cannot restrict the Role-Job Code Mapping associated object because Job Code field type in this object "Role" is a String type, not a Generic Object type.

3. Final Step: Updating Desired Permission Role

a. Select Permission Role: In Manage Permission Roles screen, choose the desired permission roles for users who will manage Job Profile Content.

b. Add Permissions
- Add the necessary permissions for the objects you secured by selecting the relevant permission category specified earlier in our solution.

c. Set Restriction Criteria
- In the Assignments tab, select "Edit."
- Scroll down to view the permissioned objects. (Family in our example)
- In the "Restrict Target Criteria to…" section, select the legal entity field you added for your desired role.

Now following with the same context you will be able to restrict the rest of Job Profile Content Objects in addition to Competency Structure Objects.

Try it and let me know if you face any issues or more clarifications needed.