SAP Knowledge Base Article - Public

2699819 - Behavior of Previous Value in Job Relationships - Employee Central

Symptom

  • You have a business rule that retrieves the Previous Value of the "relationship-type" field in Job Relationships
  • Upon downloading the rule execution log, the "Previous Value" obtained is "null"
  • You are not certain as to how "Previous Value" is properly derived for the Job Relationships portlet

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 Employee Central

Reproducing the Issue

Configure the following sample rule and assign as onSave in the jobRelationships HRIS Element.

Rule.png

See the Resolution section for the scenarios where the previous value is properly determined.

Resolution

Previous records are usually determined by looking for a record with the same key, but an earlier date.

In the case of Job Relationships, the Relationship Type is part of the key. In other words, in order for the "Previous Value" to be properly derived in this case, there has to be an earlier record in the Job Relationships portlet with the same Relationship Type.

Examples:

Scenario A: Existing earlier record with same Relationship Type

Imagine, you have the following existing Job Relationship record for Paul Johnson.

Effective Date: May 01, 2017
Relationship Type: Custom Manager
Name: Franco Alexandre

1-History.png

If you do Take Action > Change Job Relationships or Insert New Record for this employee, say, on January 1, 2018 and you change the assigned "Custom Manager", the rule will be able to properly derive the previous "Relationship Type" from the May 01, 2017 record.

1-InsertNewRecord.png

Result: Previous Value found.

1-KeyFound.png

Scenario B: Existing earlier record, but different Relationship Type

Imagine, you have the following existing Job Relationship record for James Sandler.

Effective Date: January 01, 2015
Relationship Type: Matrix Manager
Name: Alexis Moore

2-History.png

If you do Take Action > Change Job Relationships or Insert New Record for this employee, say, on January 1, 2018 and change "Matrix Manager" to "Custom Manager" and assign a new employee, since the rule is checking the Relationship Type "Custom Manager" and there's no earlier record containing such Relationship Type, the "Previous Value" derived is null.

2-InsertNewRecord.png

Result: Previous value NOT found.

2-KeyNotFound.png

This also holds true if you add a new Relationship Type on the UI. The system will look for the previous record with the new Relationship Type, but may not find anything. In this case, the "Previous Value" is still null.

newRelationshipType.png

Result: Previous value NOT found.

newRelationshipType2.png

Please refer to Rule Guide : Implementing Business Rules in SAP SuccessFactors

See Also

  • 2437420 - Which Portlets Support Cross Portlet Business Rules
  • 2092849 - How to create a Business Rule to validate data on change/save, and provide a Warning or Error message
  • 2257064 - Employee Central - Business Rule Execution Log 
  • 2331851 - Employee Central - Business Rules
  • 2621890 - Troubleshooting Business Rules in Employee Central

Keywords

job relationships, previous value, null, relationship type, key, job relationships model, ECT-105604, ECT-95632, rule , KBA , LOD-SF-EC-JRL , Job Relationships , LOD-SF-EC-JOB-RUL , Job Info Business Rules , How To

Product

SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HXM Suite all versions