This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Hello team,
I need below fields in the report, there are few employees only on L1 and I can use employee assigned to step filter but I am not getting report exceptions and other details in the same report, please help me to build such report
| Report Name | Employee name | L1 Head Name | Employee ID | Employee Location | Step | Step Entry Date/Time | Org Unit 2 - Code | Org Unit 4 - Code | Policy | Reimbursement Currency | Total Approved Amount (In local currency) | Approved Amount in USD | Entitlement in USD | Exception amount in USD | Country (of Employee) | TAT W/O Weekends | First Submitted Date | Approval Status | Employee Assigned to Step | Report Exception | Policy |
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Hi @Rahul4
Topic: Cognos reporting
Please check the below. Hope this helps.
-----
SAP Concur Cognos Reporting – L1 Approval Workflow, Exceptions & TAT
Yes, this reporting requirement can be approached in SAP Concur Intelligence (Cognos).
However, the challenge is combining Expense Report details, Approval Workflow history, Employee information
and Report Exceptions into a single report without duplicating records.
The key issue is that these fields may belong to different Cognos query subjects and operate at different reporting levels.
The main challenge is combining Expense Report details, Approval Workflow information and Report Exceptions,
as these come from different query subjects.
Create the below Three Queries:
Apply the L1 filter within the Approval Workflow query, then join the queries using the common Expense Report identifier.
Use an appropriate Outer Join to retain reports without exceptions.
Please also ensure that multiple exceptions do not duplicate the report-level approved amounts.
For TAT excluding weekends, you may need a calculated field or Business-Day Calendar.
The exact query subjects and relationships will depend on your Cognos Reporting Package.
Cognos Build Sequence:
Do not sum the approved amount after joining workflow and exception detail rows unless the data has first been brought to the correct reporting grain. Otherwise, amounts may be overstated.
Thanks & Regards
--
Samantha
SF_EC & ECP / SAP Concur Consultant