Hi @johndi ,
I think you misunderstood the report description. You need to focus on below highlighted line:
"This report will display all completed Travel Requests that do not have a Travel Request line item associated to a report entry. This will allow finance departments to identify liabilities and plan appropriately."
Here, they are NOT referring to just any expense report. They are specifically talking about the associated expense report entry where the travel request is not linked.
Let me explain how this works for better clarity.
Assume you have the approved travel request below, and it has been linked to an expense report.
This is why the record is still appearing in your Cognos report. You may expect it not to show up because, from your understanding, the travel request has already been linked to the report.
The report will only be excluded from Cognos when the travel request is actually linked within the specific expense report entry. In this case, since the travel request is for the “taxi” expense type, you need to select the “taxi” expense type in the expense report and associate the approved travel request, as shown below.
Once this is done, the expense report record will no longer appear in the Cognos report results.
Note: In the backend, each expense type in the Request module is mapped to a corresponding expense type in the Expense module. That’s why the “Request” field appears only in certain expense entry forms. In other forms, this field will not be visible, as it is controlled by backend configuration.
In your scenario, employees may have linked the travel request to the expense report, but not to any specific expense entry. As a result, those records are still appearing in your Cognos output. You can verify this by manually reviewing such records in Concur.
Hope this helps to clarify your understanding! 🙂
If this answers your query, then please mark solution as accepted.
Hi @johndi ,
Could you please describe the exact issue you’re facing? If possible, share a screenshot along with the error message—that would help clarify the problem.
If your query is about why an approved travel request is still visible in the expense report—even though it has already been used in a paid expense report—it could be due to your request policy configuration. The policy may be set up to allow a single approved travel request to be linked to multiple expense reports. This setting is part of the request policy configuration component.
If this answers your query, then please mark solution as accepted.
Hi @johndi ,
I think you misunderstood the report description. You need to focus on below highlighted line:
"This report will display all completed Travel Requests that do not have a Travel Request line item associated to a report entry. This will allow finance departments to identify liabilities and plan appropriately."
Here, they are NOT referring to just any expense report. They are specifically talking about the associated expense report entry where the travel request is not linked.
Let me explain how this works for better clarity.
Assume you have the approved travel request below, and it has been linked to an expense report.
This is why the record is still appearing in your Cognos report. You may expect it not to show up because, from your understanding, the travel request has already been linked to the report.
The report will only be excluded from Cognos when the travel request is actually linked within the specific expense report entry. In this case, since the travel request is for the “taxi” expense type, you need to select the “taxi” expense type in the expense report and associate the approved travel request, as shown below.
Once this is done, the expense report record will no longer appear in the Cognos report results.
Note: In the backend, each expense type in the Request module is mapped to a corresponding expense type in the Expense module. That’s why the “Request” field appears only in certain expense entry forms. In other forms, this field will not be visible, as it is controlled by backend configuration.
In your scenario, employees may have linked the travel request to the expense report, but not to any specific expense entry. As a result, those records are still appearing in your Cognos output. You can verify this by manually reviewing such records in Concur.
Hope this helps to clarify your understanding! 🙂
If this answers your query, then please mark solution as accepted.
Hi @johndi ,
As per my understanding, yes—it will still appear since one request is still pending to be linked to an expense entry.
But again, backed request policy configuration wise scenarios could be different.
- As mentioned in my earlier response, there is a configuration that determines how many expense reports a travel request can be assigned to. In your company, it might have been set to “multiple.” For example, if a user links five requests to one expense report but forgets to link one request to any expense entry, that request may still be linked to another expense report and its associated expense entry. So, it ultimately depends on the configuration.
- Now, if the backend is configured to allow assignment to only “one” expense report, and the request is not linked to any expense entry, then it will definitely appear in the Cognos output.
So, based on your example, my overall assumption is that yes, it will appear in the Cognos output.
If this answers your query, then please mark solution as accepted.
