Symptom
- Service URL is not populated when a communication arrangement is created based on a custom communication scenario.
- The external API used is created based on standard CDS view I_CO_ElectronicDocInvoice, and the element CO_ElectronicDocDateTime is exposed.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Create a custom CDS view.
- Include the element `I_CO_ElectronicDocInvoice.CO_ElectronicDocDateTime` with the data type `XSD Time (UTC): yyyy-mm-ddThh:mm`.
- Publish the external API scenario based on the custom CDS view.
- Create a communication arrangement using the custom communication scenario.
- Observe that the service URL field is blank and does not populate as expected.
Cause
- The field `I_CO_ElectronicDocInvoice.CO_ElectronicDocDateTime` with the data type `XSD Time (UTC): yyyy-mm-ddThh:mm` in the custom CDS view YY1_ELECTRONICDOCINV_v2 is not supported by the external API scenario, causing the service URL to not populate.
Resolution
- Remove the element `I_CO_ElectronicDocInvoice.CO_ElectronicDocDateTime` from the custom CDS view.
- Alternatively, use the cast function to convert the element `I_CO_ElectronicDocInvoice.CO_ElectronicDocDateTime` to the DATE type to resolve compatibility issues.
Keywords
service URL blank, communication arrangement, custom communication scenario, external API, YY1_ELECTRONICDOCINV_v2, YY1_ELECDOCFILE, CDS view, XSD Time UTC, CO_ElectronicDocDateTime, SAP S/4HANA Cloud Public Edition, communication management, integration , KBA , BC-SRV-APS-GKE , Generic CDS Key User Editor , BC-SRV-APS-COM , Maintain Communication System and Arrangement , Problem
Product
SAP S/4HANA Cloud Public Edition all versions
SAP Knowledge Base Article - Public