Oracle Journeys – PersonId Token {PersonId} Is Not Passed to BI Publisher Report from Advanced Task

We are facing an issue in Oracle Fusion Journeys while invoking a BI Publisher report from an Advanced Task using an XMLP Server URL.

We have configured the following URL in the Journey Advanced Task:

https://<host>/xmlpserver/Custom/Human Capital Management/DOR/Change in Work Location/Change in Work Location Report.xdo?_xmode=6&_xpt=0&P_PERSON_ID={PersonId}

The expectation is that the {PersonId} Journey token is dynamically substituted with the employee's Person ID when the task is launched.

However, the BI Publisher report does not receive the Person ID. Instead, the token is not substituted (or the parameter is received as blank/literal), causing the report to fail to retrieve employee-specific data.