SAP C4C integration wirh SAP FSM - ChecklistInstance replication error

[samot]

Hi guys,

we have set up an integration between the SAP C4C and SAP FSM via the SAP Cloud Integration of the SAP Integration Suite on SAP BTP.

We were able to set-up all of the iFlows and necessary configurations on both systems.

However we are encountering the following error caught by the Web Service Message Monitoring in the SAP C4C, when we try to replicate the ChecklistInstance from FSM:

- error message in text form:

<ERROR_CONTEXT>
  <ERROR_INFO>
    <EXCEPTION_INFO>
      <TYPE>CX_GFS_METADATA_ERROR</TYPE>
      <ERROR_TEXT>No join index metadata for View FSI_CKL_TEMPL_QUERY_BY_EL, View is NOT active</ERROR_TEXT>
      <CX_FATAL_EXCEPTION>
        <TRIGGERING_COMPONENT/>
        <APPLICATION_INFORMATION/>
        <CALLSTACK/>
        <DUMP_SOURCE/>
        <PROXY_BO_NAME/>
        <PROXY_NODE_NAME/>
        <PROXY_ACTION_NAME/>
        <PROXY_ASSOCIATION_NAME/>
        <SAP_NOTE_NUMBER>0000000000</SAP_NOTE_NUMBER>
        <MV_SUPPRESS_DUMP/>
      </CX_FATAL_EXCEPTION>
      <CX_GFS_METADATA_ERROR>
        <BO_NAME/>
        <BO_NODE_NAME/>
        <DB_NAME/>
        <FSI_VIEW_NAME>FSI_CKL_TEMPL_QUERY_BY_EL</FSI_VIEW_NAME>
        <INDEX_ID/>
        <META_KEY/>
        <ERROR_INFO/>
      </CX_GFS_METADATA_ERROR>
    </EXCEPTION_INFO>
  </ERROR_INFO>
  <PROVIDER_INFO>
    <PROCESSING_UNIT>Sector 4: Provider</PROCESSING_UNIT>
    <PROCESSING_MODE>Asynchronous</PROCESSING_MODE>
    <PROCESSING_TYPE>Remote</PROCESSING_TYPE>
    <WORK_PROCESS_NUMBER>89</WORK_PROCESS_NUMBER>
    <WORK_PROCESS_PID>24128</WORK_PROCESS_PID>
  </PROVIDER_INFO>
</ERROR_CONTEXT><br>

This error results in the ChecklistInstance not replicating and we are not sure where to start looking what's wrong.

As additional information:

1. We have succesfully replicated all of the ChecklistTemplates from FSM to C4C (we have verified this through checking the C4C Datasource)

2. The iFlow for the ChecklistIntance replication shows no error:

We are open to disclose any additional information about our configuration if needed.

Thank you.

[samot · Accepted solution]

This issue was solved for us via the SAP incident, that we have created. SAP support technician has replied that they have activated the mentioned View in our tenant.