How To Fix 5F089 - Contract type not identified between &1 and &2 (conf. infotype)

5F089 - Overview

• Message type: E = Error

• Message class: 5F - HR F: Error Messages (France)

• Message number: 089

• Message text: Contract type not identified between &1 and &2 (conf. infotype)

What causes this issue?

For the selected period, there is no record of infotype <ZK>"Assignment"
(0001)</> or <ZK>"Contract elements" (0016)</> relating to the
employee's contract type.

System Response

The system interrupts the contract processing.

How to fix this error?

Complete the relevant infotype.
Note:
Make sure that the following parameters have been set for identification
of the contract and contractual properties.
The CONTR constant of table T551K must indicate the infotype in which
the program will read the contract type. Value 0 (used by default)
refers to infotype 0016, value 1 refers to infotype 0001.
The contract field of the infotype in question must be completed: CTTYP
field for infotype 0016 and ANSVH for infotype 0001.
Table T5F42 parameters must be set so as to indicate the properties of
the different contract types.

Error message extract from SAP system. Copyright SAP SE.

5F089 - Details

• The SAP error message 5F089 indicates that there is an issue with the contract type not being identified between two specified entities (usually between a vendor and a customer or between two business partners) in the context of a configuration infotype. This error typically arises in the context of contract management or when dealing with business partner relationships in SAP.
  
  Cause:
  
  Missing Configuration: The contract type may not be properly configured in the system. This could be due to missing entries in the customizing settings for contract types.
  Incorrect Business Partner Relationships: The relationship between the two entities (e.g., vendor and customer) may not be correctly defined or may not exist.
  Data Inconsistencies: There may be inconsistencies in the data entered for the business partners or contracts, leading to the system being unable to identify the correct contract type.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or create the