3758676 - Invalid Association Between Configured Data Objects on the Add Contingent Worker Page

While hiring a Contingent Worker on the Add Contingent Worker page, the transaction may fail with a validation error if configured data object associations change across effective dates. For example, if a Division is associated with one Business Unit for an earlier effective date and a different Business Unit for a later effective date, the following error may occur: Division “XXX” is not associated with Business Unit “XXX”. Check the Division data object configuration and enter a valid Business Unit.

SAP SuccessFactors Employee Central - Contingent Worker

1. Navigate to the Division data object and associate a Division with a Business Unit for a given effective date.
2. Create a new record for the same Division with a later effective start date and associate it with a different Business Unit.
3. Go to the Add Contingent Worker page and enter a Termination Date and Work Order End Date that fall within the later effective date range.
4. Submit the transaction and observe that the system throws a validation error due to invalid Division–Business Unit association.

This is the expected behavior.

• The system creates both Start Contingent and End Contingent records in Job Information during the hiring process based on Work Order details.
• While creating the End Contingent record, the system uses a later effective date.
• At that effective date, the Division–Business Unit combination is no longer valid as per configuration.
• As a result, the system triggers a validation error.

Add Contingent Worker, Business Unit, Division, Association, Invalid, not associated with, valid, error , KBA , LOD-SF-EC-CWF , Contingent Workforce , Problem