Introduction and Terminology
With Duet Reporting Management, report templates are defined in the backend and delivered to end users’ Outlook following a role-based concept. These templates are organized in report catalogs as represented in the Outlook folder structure. Each template can be executed by end users with either the default parameters or any individual parameter values. User-defined parameter settings can be saved as personalized templates.
This blog provides a checklist of steps in case not all report templates arrived at the clients as expected. If all report templates arrived, but the data reports get stuck after executing a template on the client, I recommend the blog Follow your ERP report in Duet.
In addition to the shipped documentation, please take a look at the Duet How-to Guides in SDN. For Reporting Management, these guides cover the following topics:
- How to configure your Duet landscape for BW Reporting
- How to Create and Configure System and Duet Timepoints
- How to Add a Report Template to Duet
Given the situation, you have configured report templates for your Reporting users following above SDN guide and some of these templates do not arrive in Outlook, these are the steps to take:
1. Which Duet Reporting role(s) does the user with missing templates have?
Within the browser, open Web Service Navigator on the Duet Server with the following URL: http://:/wsnavigator and log in as Administrator. Select web service SimpleRoleManagement, then click on Test and select operation getContentGroups. Enter the userID as parameter, click Send and provide backend user credentials. The response will list all roles of this specific user.
The default Duet Reporting role is REMA.Users. On the screenshot, you can also see a custom-defined role REMA.JochenTest. You can find out more about custom-defined roles in another blog of mine: Extend Duet Reporting Management with your own Roles.
If the user does not have any REMA.* role assigned, this would explain why no templates are delivered. In this case, consult Duet documentation how to perform a role-mapping to assign all users with a specific backend role to a REMA.* role. If other Duet users of your landscape already have REMA-roles assigned, compare their backend roles with those of the user with missing templates.
2. Which report templates are assigned to this role in the backend?
Now that we know the User<->Role assignment, let’s check what report templates are assigned to that role. Log on to the backend and call function module /OSP/RAUI_CATALOG_READ in transaction SE37. Add the role(s) from step 1 as import parameter USER_ROLES, then execute. Within the list of export parameters, you can see all reports for that user role in export parameter ET_RP_DETAIL
Click on the “Show Details” button to list all report templates the user is supposed to get. You will see the catalog and template id in the first column and a report description if you scroll to the very right. If any template is missing here, go back to transaction SIMGH and double-check if both a REMA.* role is assigned to the template and the template is activated (checkbox [X] Active). To verify latter, you can also check flag ACTIVE in table /OSP/T_RAUI_SEL for all reports at once.
3. Which templates does the backend expect the user to have already?
The backend tracks all delivered templates in a bookkeeping table. Open this table /OSP/T_REPMD5BKT with transaction SE16. On the selection screen, enter the user id as parameter USERID and click “Execute”. You will get a list of all report templates the backend expects to be in the user’s Outlook already. If no results are shown, continue with the next step. Otherwise, delete all lines for the corresponding user to ensure all templates are sent out in the next step.
4. What happens when template delivery is triggered manually?
The reporting catalog in the end-user’s Outlook is updated automatically in a regular interval. To reduce traffic and processing load, templates that already exist on the client and did not change since last update are not sent again. To ensure all missing templates are sent out, either delete lines of the bookkeeping table as described in step 3 or change the missing report templates in the backend, e.g. by adding a character to the report description.
To trigger report template delivery, open Web Service Navigator in the browser at the following URL: http://:/wsnavigator and log in as Administrator. Select web service ReportingFacadeWS, then click on Test and select operation getAdminReportCatalog. Enter the locale as parameter (e.g. EN), click Send and provide backend user credentials.
Since this is an asynchronous call, the response will indicate if the call was successful. If responseStatus is true, report templates will be sent from the backend to the Duet Server, converted to Mail items and routed through Exchange to the end-user’s Outlook. There, they will reside in OBAControlMessages folder (as explained in Stefan’s Follow your ERP report in Duet) until being transformed to Reporting templates.
You can find out more about the web services that are called by Duet scenarios in this blog Testing the Duet scenario Web Services from your browser If responseStatus is not true, any exception is displayed in Web Service Navigator or no templates arrive in OBAControlMessages folder, advance to the next step.
5. Which exceptions are logged in J2EE default trace?
Log on to Duet Server Visual Administrator, standalone Log Viewer or open the J2EE default trace in a text editor of your choice. Check for exceptions starting with the time when you called getAdminReportCatalog in step 4. For more detailed troubleshooting, enhance the log severity for location com.sap.xapps.osp to ALL in Log Configurator.
If all templates are failed to be delivered, this could relate to an authentication issue. Double-check trust and correct credentials between all instances in the delivery chain: Backend -> Duet Add-On/Server -> Microsoft Request Handler -> Microsoft Exchange Server.
If some templates get delivered while others are missing, this could relate to oversized messages. In this case, an exception similar to ‘com.sap.xapps.osp.itemhandler.exception.resource.IHErrors’, ID=’The message size exceeded the maximum limit!’ is logged indefault trace. To solve this issue, increase maximum item size in Duet Administration Environment, Request Handler and Exchange Server. Alternatively, you can decrease the actual item size by deactivating large documentation from affected templates in transaction SIMGH. In each case, repeat steps 4 and 5 afterwards.
This is where things are getting too complex for a single blog. If you spot an exception that seems to relate with the issue, please feel free to share with the SDN community in the Duet [To remove]. If you experience this issue on your system, you can also open an OSS message, describe the situation and attach the default trace of this time slot.