1) Unlike the concurrent request form, only exact job numbers can be submitted via the sheet.
2) At More4apps we try to cover all possible situations when error happens after the upload, but in the case of WIP Close Discrete Job template, this is not possible. This template will not be able to bring back the details of the records with error status.
This loader uses functionality which corresponds with Oracle error handling. Hence, user will require to navigate to “Application Interface Wizard > Concurrent Processing > View Concurrent Request” ribbon option and click “log” or “out” button next to the errored concurrent request as shown in the below image.
3) The loader submits a concurrent request for each uploading records. Because of that, More4apps recommends uploading 5 records at a time to avoid potentially hold up other concurrent requests/resources.
If an organization hits this issue, they only need to reduce the priority sequence of the Concurrent program so other requests take priority. In the unlikely event that this is still not enough they can create another concurrent manager to segregate all WIP processing.
To close the priority of the WIP Job:
a) Login system administrator /Application developer and go to define concurrent screen
Under Concurrent >> Program >> Define
b) Find the Program name “Close Discrete Job”
c) On this screen you can set priority of this request by entering value in “Priority” field. By default the value is 50, you could change the value to 60 if it is causing concurrent requests to backlog.
Alternatively, you could place the concurrent request, along with the “Discrete Job Value Report” on a separate concurrent manager.
4) Download will not include cancelled, unreleased or completed jobs.
5) Due to the technical structure of the template, “Background Upload Selected” or “Background Upload All” upload options are not possible for uploading records when using this template.
