ERROR_MSG KEY IS NOT PARSED In Saexprocsales.ksh
(Doc ID 3000218.1)
Last updated on JANUARY 26, 2024
Applies to:
Oracle Retail Merchandising System - Version 16.0.3 and laterInformation in this document applies to any platform.
Symptoms
When errors occur during the saexprocsales.ksh, both the messages written to the batch error log (err.saexprocsales.Mmm_DD.PID) and to the SA_EXPROC_SALES_LOG) are written as cryptic messages with Keys rather than decoded to their error message. Some examples as follows:
1) In batch error log we see the following: @0STORE_DAY_PROC_ERR
Should be: Error in processing one or more store/days.
2) In SA_EXPROC_SALES_LOG we see the following: @0STR_DAY_LOCKED
Should be: The select Store Day is currently being used by another user or process and cannot be modified at this time. Try again later.
Cause
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
Symptoms |
Cause |
Solution |
References |