Guidance for SAP RISE Customers: How to Retrieve the Panaya Custom Code File
Overview
For customers running Panaya on SAP RISE environments, there is an important operational consideration during the custom code extraction process.
Because SAP controls system access and infrastructure in SAP RISE landscapes, the output file generated by the Panaya extraction job may be saved in an SAP-managed environment rather than being immediately accessible to the customer. In these cases, the customer typically needs to open a ticket with SAP to obtain the extraction file before it can be uploaded into Panaya.
This can introduce additional turnaround time, so it is important to plan accordingly.
Why does this happen on SAP RISE
In traditional customer-managed SAP environments, customers often have direct access to the application server or to the location where extraction files are written.
In SAP RISE, however, the hosting and infrastructure are managed by SAP. As a result:
The extraction job may run successfully,
But the generated custom code file is saved in an SAP-controlled location,
and the customer may not be able to retrieve it directly without SAP assistance.
Under the standard SAP RISE support model, SAP generally does not upload the file directly to Panaya, since that step is outside SAP’s standard scope. Instead, SAP usually sends the file to the customer, who then uploads it to Panaya.
Standard recommended process
For SAP RISE customers, the expected process is usually:
Run the Panaya extraction according to Panaya instructions.
If the extraction is run in the background (recommended), the output file will be saved in the SAP-managed environment.
Open a support ticket with SAP requesting delivery of the generated extraction file.
Once the file is received from SAP, upload it to Panaya.
Important planning consideration
This extra handoff can add delay to the onboarding or analysis timeline. From past experience, it can take 2–3 business days.
For this reason, customers on SAP RISE should expect that retrieving the custom code file may require additional lead time compared to non-RISE environments.