-
Batch Job Completes with Ended Status but has Errors
It creates confusion for the end users when batch jobs completes with the status of "Ended" but when you review the log there are errors. This is a very time consuming process to have to review each batch job's log to see if there are errors. We understand the need to differentiate between an error that stops processing and one that allows processing to continue through other records. In our case, we definitely want the job to continue processing through the remaining records. It seems to us that there should be 3 different statuses instead of just 2:
- One to indicate that a batch job finished successfully without encountering any errors.
- One to indicate a batch job finished successfully, but with some errors.
- One to indicate a “hard” error was encountered and processing has stopped.
It would also be nice to be able to set alerts on the batch job that it has ended, but there are errors.
-
External Catalog on Purchase Order Lines
We appreciate the concept of utilizing External Catalogs, but our business process does not use nor require Purchase Requisitions. We would prefer to have the capability to access External Catalogs directly from a Purchase Order so we could utilize the purpose/vision behind this functionality. Implementing a new process with additional workflows and configurations would add unnecessary steps and complicate our streamlined business process where our users are already accustomed to only using Purchase Orders.
You’re offline. This is a read only version of the page.
