Why Does UPLOADSALES.KSH Throw "Invalid Thread Number" Error when POSU File Does Not Have an Extension?
(Doc ID 2564244.1)
Last updated on SEPTEMBER 13, 2019
Applies to:
Oracle Retail Merchandising System - Version 16.0.2 and laterInformation in this document applies to any platform.
Goal
The UPLOADSALES.KSH (Upload POSU File for Processing) batch throws error message for each POSU file. Appears to expect a threaded file name. POSU files are produced by SAEXPRMS.PC (Export of POS transactions from ReSA to RMS), but, which module is responsible for assigning thread IDs as extensions? Is there is a fix between these modules?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |