rsvconsulting
VIP Member
Setup Report A to call Report B using report interconnect. Report B version is setup as a Report Definition (RD) job with blind submission unchecked. When this RD job is directly submitted from P95620 or from Batch Versions to the server, Submit Report Definition (P95601|W95601D) screen appears (Sample screen-print shown below). It does not bring up P95601|W95601D screen when called from report A when it is run on the server. As a result the user cannot override certain properties for the child RD job.
When report A is run on FAT client locally, the above screen appears.
Is there a way to have the Submit Report Definition (P95601|W95601D) prompting appear for child RD job when the parent job is run on server?
As per the current design, it is not possible to have the Submit Report Definition (P95601|W95601D) prompting appear for child RD job when the parent job is run on server. Since parent UBE is processed on server, there is no way for UBE engine to prompt an interactive screen on web client. Running parent UBE locally will prompt for Submit Report Definition screen because the UBE runs as a local process on the FAT client.
If there is a requirement to have this prompting for the child report, consider running this child report as an independent job directly from P95620 or from Batch Versions.
When report A is run on FAT client locally, the above screen appears.
Is there a way to have the Submit Report Definition (P95601|W95601D) prompting appear for child RD job when the parent job is run on server?
As per the current design, it is not possible to have the Submit Report Definition (P95601|W95601D) prompting appear for child RD job when the parent job is run on server. Since parent UBE is processed on server, there is no way for UBE engine to prompt an interactive screen on web client. Running parent UBE locally will prompt for Submit Report Definition screen because the UBE runs as a local process on the FAT client.
If there is a requirement to have this prompting for the child report, consider running this child report as an independent job directly from P95620 or from Batch Versions.
sonal_m
Active Member
Hi Lucy,
Al has already explained the usage of blind execution but I would like to add in from my side that if we have blind execution turned ON - there is no way we could modify the output fields during run time.
On the other hand, if it is not check in - user can modify the output type, language etc every time the report is submitted. This is useful in the cases where we require different output types or languages in each run. Hope that helps you.
Al has already explained the usage of blind execution but I would like to add in from my side that if we have blind execution turned ON - there is no way we could modify the output fields during run time.
On the other hand, if it is not check in - user can modify the output type, language etc every time the report is submitted. This is useful in the cases where we require different output types or languages in each run. Hope that helps you.
johndanter
Legendary Poster
Hi Lucy
As others have explained above, it's to stop the JDE engine prompting a user for values at run time.
Be they Processing Options or Data Selection. This could be for security or just convenience
A good example of where you'd want this is for scheduled UBE versions or UBEs that are spawned by something else where a user isn't present/not needed.....endless list of examples
As others have explained above, it's to stop the JDE engine prompting a user for values at run time.
Be they Processing Options or Data Selection. This could be for security or just convenience
A good example of where you'd want this is for scheduled UBE versions or UBEs that are spawned by something else where a user isn't present/not needed.....endless list of examples
Similar threads
- ccornagg
- JD Edwards® EnterpriseOne Developers
- patrick.lemos
- JD Edwards® EnterpriseOne Developers
- ccornagg
- JD Edwards® EnterpriseOne Developers
