SAP Datasphere: Using Replication Flows on Finance Foundation Business Content

[wsamuel]

Good day,

I've been attempting to utilize replication flows from S4H to Datasphere on the finance foundation business content, following the instructions outlined in the documentation (https://help.sap.com/docs/SAP_DATASPHERE/6eb1eff34e4c4b1f90adfbfba1334240/a878c25f6bfc1014a79e69594c...).

Despite installing the business content and creating the replication flow as instructed, I encountered the below error when attempting to deploy and run the replication flow.

Error creating replication for dataset
I_FISCALYEARFORCOMPANYCODE: data type of source column FiscalYear StartDate (vtype:com.sap.core.date) is incompatible with target column FiscalYearStartDate (vtype:SDYNAMIC.string 8); please map the source column to a target column with a compatible data type

Has anyone experienced this or managed to use the finance foundation business content in Datasphere? Please advise on the steps taken, thank you.

[TuncayKaraca · Accepted solution]

Hi @wsamuel 

As @NataschaM pointed out there might some missing SAP Notes in your S/4HANA source and you need to apply. 

I had come across exactly same issue for Finance foundation package for SAP S/4HANA and SAP S/4HANA Cloud there is one way to fix that you need to change all Date types fields in local tables in Datasphere from Date to String(8) - in your example I_FISCALYEARFORCOMPANYCODE table's FiscalYearStartDate column and all other date fields / columns. By changing the field / column type may affect upper stream objects as well.  I had fixed all local tables that way then the replication flows worked successfully. 

Regards,
Tuncay

[sakthi1 · Accepted solution]

I am also facing issue for finance foundation package for SAP S/4HANA and SAP S/4HANA cloud in I_SEMTAGGLACCOUNT CDS view. while mapping I_SEMTAGGLACCOUNT with local table in datasphere I am facing below issue (Change target object. The target object cannot be used because it does not have the required technical column __load_package_id. You can rename the target object using a name that does not exist yet. The system then creates a new object that has the same definition as the source object and contains the technical column. Alternatively, you can map the target object to an existing object that has the required technical column (__load_package_id).