Symptom
The Ticket notes and interactions are missing in custom report created from the "All Tickets with All Interactions" Data Source.
Environment
SAP Cloud for Customer
Reproducing the Issue
- Go to Business analytics.
- Go to Design report.
- Open the desired report.
- The field Internal Note is displayed as "#".
- Now go to Service > Tickets.
- Open the desired Ticket.
- Go to Interactions > notes are populated.
Cause
The combined data source SEODSRQINTERACTIONU01 (All Tickets with All Interactions) includes basic data source SEODSRQINTNOTESB (All Tickets with Internal Notes) as one of its combined data sources, from which the ticket internal note data is retrieved for display in the report.
However, there are two pre-requisites to use this data source:
- In order to get Internal Notes, the Ticket must have a Buyer assigned as involved party. The Buyer Party is required because there is a restriction rule in underlying FSI view with Buyer Party in order to get notes available in the Ticket. For those Tickets which have a Processor Party maintained within Involved Parties tab, the 'All Tickets with All Interactions' (SEODSRQINTERACTIONU01) data source brings expected results for 'Internal Note' field.
- And only Customer Support Tickets can add Buyer (Processor) involved party for Tickets. The Employee Support Ticket does not support this party.
Resolution
Due to this reason, the "All Tickets with All Interactions" data source will not bring results for Employee Support Ticket type. This is the system expected behavior.
There is currently no standard data source that would support Internal Notes for Employee Customer Support Tickets.
Keywords
C4C, service_request, tickets, interaction, notes, internal notes, internal memo, portal, report, data source, analytics , KBA , LOD-CRM-SRP , Service Request Processing , AP-RC-ANA , C4C, ByD, Travel: Analytics Tools & Frameworks , Problem
SAP Knowledge Base Article - Public