Any required configuration on PI Server side to establish the connection of AVEVA Historian 2023 replication to AVEVA PI Server?

There isn't a lot to configure on the PI server side. You do need to have PI WebAPI installed and configured and have OMF enabled (it is by default). After that, the main issue is getting the security set up correctly: the main issue here is PI WebAPI favors using Kerberos (which works well for user and machine accounts), but the Historian "Replicate to PI" runs as a "virtual service account" (least privileges locally), which is more awkward to enable the Kerberos trust. There is more detail in the docs--the actual software requirements are the same between Historian 2023 and 2023 R2, but the R2 docs have more details.  
Adding AVEVA PI Server as a Replication Server

There isn't a lot to configure on the PI server side. You do need to have PI WebAPI installed and configured and have OMF enabled (it is by default). After that, the main issue is getting the security set up correctly: the main issue here is PI WebAPI favors using Kerberos (which works well for user and machine accounts), but the Historian "Replicate to PI" runs as a "virtual service account" (least privileges locally), which is more awkward to enable the Kerberos trust. There is more detail in the docs--the actual software requirements are the same between Historian 2023 and 2023 R2, but the R2 docs have more details.  
Adding AVEVA PI Server as a Replication Server

Elliott Middleton  Thank you for great support and advice. This means I need to get AVEVA PI experiences people to involve these activities.