JD Edwards EnterpriseOne

You invested in JD Edwards EnterpriseOne because you recognized its extensive functionality—JDE offers you a lot in the way of business application functionality. However, managing jobs with more complexity than just basic time/date parameters can be difficult in JD Edwards EnterpriseOne. You might find that your batch processing windows are running too long and impacting end-user service and performance, and you might have run into problems basing processing triggers on external actions or other applications.

UC4 Software's solution enhances automation and controls of your EnterpriseOne applications ensuring reduced run time for your batch workload and improved levels of end-user service.

Compress the Batch Window
Reduce elapsed times with parallel processing of EnterpriseOne workload. Automate exception handling and error recovery procedures. Avoid lengthy reruns by restarting job streams at the point of failure.

Manage User Submitted Jobs
Intercept and queue ad-hoc jobs. Prioritize EnterpriseOne processing based on business demands and current availability of IT resources. Ensure that end-user performance and response times are not impacted by execution of rogue jobs.

Centralize Management and Monitoring
Manage submission and monitor execution of UBE jobs executed by EnterpriseOne scheduler. Control workload based on advanced dependencies and "what-if" conditions. Integrate JD Edwards processing with the entire IT environment. Track progress of all EnterpriseOne workload from a single point.

Automate Report Distribution
Easily configure EnterpriseOne reports to be sent only to the people who need them. Provide authorized users with online access with an integrated PDF viewer. Distribute output via fax, printers or email, saving time for operations staff and money on printing costs.

UC4 Extends JD Edwards (Example)
Bonland Dairies employs over 200 people and generates annual revenues of approximately $600 million (AUD). And in 2001, Bonland Dairies had a problem: support for their current Data Warehousing scheduler had been discontinued. They had to find a replacement, and quickly. The new scheduler needed to launch, monitor, and manage multiple sets of jobs across multiple instances at multiple corporate locations. The data warehouse is driven by data extracted from their J. D. Edwards ERP application, which is then loaded into an Oracle database using Oracle SQL*Loader. Various transformations are performed by custom PL/SQL packages. All of this takes place in a Windows environment. Their goal was full-scale automation and high reliability, as the majority of their processing must occur overnight when there are no operators. After evaluating the major players, they selected UC4 Software to provide solutions including grouping jobs, running multiple environments, and supporting dependency/predecessor requirements.