2993636 - Error with Imported GUIDs Validity in Check Tool (Check ID: JDMImportedGUIDInvalid or JPBImportedGUIDInvalid) - Sequence Issues in JDM and JPB

• Getting errors when trying to save new objects in Job Description Manager or Job Profile Builder UI or via Import;
• This article will cover sequence issues in Job Description Manager and Job Profile Builder: what are they, how to avoid, and what is needed to fix them.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP SuccessFactors Job Description Manager (JDM)
• SAP SuccessFactors Job Profile Builder (JPB)

Trouble managing Families and Roles in JDM or creating new Objects for JPB (Families, Roles, Competencies, Behaviors, Job profiles, or any job profile sections) under Manage Job Profile Content, Manage Job Profile Templates, Manage Job Profiles or via Import, the easiest way to confirm this is indeed a sequence issue, is to run the Check Tool for data sequence issues. Complete information on Check Tools available for JDM and JPB, review the WIKI JDM & JPB Check Tools.

This can be done under Admin Center > Check Tool > Job Description Manager or Job Profile Builder application, and select check Data Sequence Issue.

Sequence is a unique ID that defines the GUID for any newly created fields for JDM and JPB in database, and it works as an incremental list, which is shared by most of the JDM and JPB fields, which means that when creating a Family, and system assigns GUID '10" to it, and then creating a new Role after that, the system will use GUID "11", if no other data has been created in between.

If we create data via import, for example, this same behavior will apply. However, it is possible to manually assign a GUID to newly created data, and if it hasn't been used already, system will allow the data to be created under the GUID that manually set in the import file, instead of getting it from the sequence number list.

However, once you create more and more data, via UI or import, the sequence number will be increased, and once it gets to a value that was already manually set to a field, it will not be able to proceed, and thus it will not allow you to create any new objects. 

To avoid this type of issue, whenever you are creating new data for JDM or JPB via import, make sure to leave the GUID column blank. NOTE: for objects that are only being edited via import you should keep the same system-generated GUID in there, as this is only valid for the creation of new data.

Some checks have a Quick Fix, which can be used to immediately correct any issues found by that check. For the Data Sequence Issue in JDM and JPB, users with permission "Allow Check Tool Quick Fix" granted in RBP can click the results and will see the four-step process at the top of the Detailed Results dialog:

Complete all four steps to fix the sequence issue, providing your approval for the data selected, and click Close to complete the process. Procedure can be found in the Using the Quick Fix Feature section of the Check Tool Guide,

Once completed, the check for Data Sequence Issue will run again to verify if the fix was completed successfully:

• KBA 2276692 - Best Practices on JDM to JPB Migration
• SAP SuccessFactors Platform > Using the Check Tool > Using the Check Tool to Solve Issues

JPB Sequence, Sequence Job profile, cannot create JPB Objects, Job Profile Check Tool, Save JPB Data, Add Job Profile Data, error when saving new Family Role Job Code Competency, JDM, JDMv1.0, JDMv1, Families & Roles, check tools, PTCH-36455, JDMImportedGUIDInvalid , KBA , LOD-SF-TIH-JPB , Job Profile Builder , LOD-SF-TIH-JDM , Job Description Manager , Problem