Symptom
Two different note values for an opportunity are shown in a report.
Environment
SAP Cloud for Customer
Reproducing the Issue
- Go to the Business Analytics work centre
- Go to the Design reports view
- Search for an opportunity report
- In the field "Opportunity ID" enter the relevant ID 123 (123 represents the relevant opportunity)
- Add the fields "opportunity ID", "Notes" and "Notes (Opportunity)" to the view
- Run the report
- Here you will notice two different values for the notes field. Your expectation is, that it should only be one value in Notes(Opportunity)
Cause
Therefore, the value shown in the report is quite arbitrary and the value of the two characteristics might deviate.
The UI supports several instances of TextCollection-TEXT_CONTENT only if the scoping question "Do you want to enable users to see earlier versions of opportunity notes?" is switched on.
As this scoping question is switched off in the system, the Opportunity UI shows only one note.
The second note value is not visible in the Opportunity UI. According to the scoping question the UI shows only the first note.
In Reporting, however, the second note can appear, too.
Resolution
To check or change the settings:
- Go to the Business Configuration work centre
- Go to the Implementation Projects view
- Select and enter the relevant project
- Navigate to step 4., Questions
- Expand Sales > New Business > Opportunities
- Select the question and as per your requirement either include or exclude it in the scoping
- Finish/Save and refresh the system.
If you had the history turned on, but in the meantime changed the scoping, those notes would still be in the system.
If there are several Opportunities which might have this issue and some might have not only one additional text but sometimes several Versions/additional texts, then manual correction is not the ideal option here.
The Notes can be exported via Data Workbench Individual Object "Opportunity Notes", filtered by the Opportunity ID.
Via Data Workbench these notes can also be deleted (add column "ToBeDeleted" with value "True"; Update Individual Object).
But this should only be done, if really an issue is there.
Keywords
Note, Reporting, Notes, wrong, , KBA , LOD-CRM-OPP , Opportunity Management , Problem