Simply speaking, subsystem processing allows a quick-running UBE to be submitted both automatically and repetitively. Subsystems begin by loading environment specs when started and then continually submit subsequent runs of the job. This allows for more efficient processing, as only the UBE logic needs to be executed during all subsequent submissions of the UBE.
There is a ton of information about subsystem processing out there, but how do you know where to start? Or where to find reference info? Or – the horrors – troubleshooting guides?
In Managed Services, we encounter subsystems issues on a regular basis, and we need to work through them with our customers. I’ve searched the following frequently used Oracle Support links, and organized them here for our readers in a quick reference guide.
Following are links for the technical side of this process –
Overview and setup:
Overview of Subsystem Processing in EnterpriseOne (Doc ID 1265778.1)
Both high-level and in-depth information
Subsystem Processing (Doc ID 625418.1)
This document also has a section on capturing logs for Subsystem UBEs
How to Set Up a Custom UBE Report for Subsystem Processing (Doc ID 649658.1)
Printer Usage – Subsystems use the default printer of the user who submitted the subsystem.
Workarounds: Subsystem and Printer Inheritance (Doc ID 650274.1)
Additional Information / Issues:
Create a Batch Application to End Subsystem Jobs (Doc ID 1066429.1)
(To end subsystem processing prior to restarting JDE services, etc)
Subsystem Jobs In A Wait State
Why is table F986113 full of records in a wait state?
Embedded BI Publisher and Subsystem UBEs (Doc ID 1074931.1)
There was a bug in 22.214.171.124 where only the first BIP job printed if job was run as a subsystem. This is fixed in Tools Releases 126.96.36.199 and 188.8.131.52
Email notification when Subsystem fails:
Oracle currently has no method of sending email notification when subsystem job fails. This is Bug #22969144