Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
S-H
Active Participant
In S/4HANA for employee-business partner’s Correspondence Lang. (Correspondence Language) field is read only in ‘Maintain Business Partner’ app or in BP transaction.

 

But during creating or editing an Employee-Business Partner’s Vendor, error “Required field Correspondence Lang. has no entry” (R1 304) appears if this field is initial.



 

Correspondence Lang. field is synchronized from employee’s information to BusinessPartner (source of the data is Employee).

In such cases, kindly maintain the language for the employee like:

  • In case of SucessFactors integration;


Kindly maintain ‘Native Preferred Language’ ( which might appear under ‘Personal Information’ section) for the employee in SuccessFactors or EC.


  • In case of Employee in uploaded to S/4HANA Cloud using Import Employee App;


Correspondence language could be filled using the column ‘Language’ in Import Employee.


  • In case of Employee in uploaded to S/4HANA Cloud using Public API (Replicate Basic Master Data for Workforce from External HR Systems - WorkforcePersonMasterDataReplicationRequestResponse_In );


Correspondence language could be filled using the column ‘CorrespondenceLanguage’ field in ‘PersonalInformation’ section.


  • In S/4HANA onPremise;


Maintain infotype 2 field SPRSL (Communication Language) for the employee.

 

For cloud; On maintaining the language value for employee (using one of the above approach) and successful replication of this employee information to S/4HANA system, you could see Corresponding Language for the business partner.

 

For onPremise; on synchronizing employee to business partner using synchronization report, then you could see Corresponding Language for the business partner. For information refer simplification list documentation 2340095.
1 Comment