How To Fix FS4BPU_EMPL_MINIMSTR155 - Conversion of Central Person &1 skipped: Valid From &2 is in future.

FS4BPU_EMPL_MINIMSTR155 - Overview

• Message type: E = Error

• Message class: FS4BPU_EMPL_MINIMSTR -

• Message number: 155

• Message text: Conversion of Central Person &1 skipped: Valid From &2 is in future.

What causes this issue?

The conversion of Central Person &V1& is skipped, because the user
differs from the actual user in a future validity period.

System Response

Conversion of Central Person &V1& skipped.

How to fix this error?

Use transaction SE16 and check in table HRP1001 the entries for OTYPE =
'CP', OBJID = '&V1&', PLVAR = '<active plan variant>', RELAT = '208' and
SCLAS = 'US'. The User ID is stored in field SOBID. You should decide
which User ID should be used.
You can identify the related Business Partner via transaction SE16 and
check in table HRP1001 the entries for OTYPE = 'CP', OBJID = '&V1&',
PLVAR = '<active plan variant>', RELAT = '207' and SCLAS = 'BP'. The
Business Partner ID is stored in field SOBID.
Use transaction BP and open the Business Partner with the Business
Partner ID you identified. Under the tabstrip 'Identification' you can
see the Employee ID.
Please use Fiori App "Maintain Employees" to assign the correct User
ID.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FS4BPU_EMPL_MINIMSTR155 - Conversion of Central Person &1 skipped: Valid From &2 is in future. ?

  The SAP error message FS4BPU_EMPL_MINIMSTR155 indicates that there is an issue with the conversion of a Central Person (CP) due to a date-related problem. Specifically, the message states that the "Valid From" date for the Central Person is set in the future, which prevents the system from processing the conversion.
  
  Cause:
  
  Future Date: The "Valid From" date (&2) for the Central Person (&1) is set to a date that is later than the current date. This means that the system cannot process the record because it is not yet valid.
  Data Entry Error: There may have been an error during data entry where the date was incorrectly set to a future date.
  System Configuration: In some cases, the system configuration or data migration processes may have inadvertently set future dates for certain records.
  
  
  Solution:
  
  Check the Date: Review the "Valid From" date for the Central Person in question. If it is indeed set to a future