Saexprocsales.ksh - Usage Appears Incorrect (Doc ID 2979307.1)

Last updated on OCTOBER 09, 2023

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
saexprocsales.ksh - Usage appears incorrect

Trying to figure out how to run the new saexprocsales.ksh batch program released in the 16.0.3 Jul CHFs and the parameter required seems to not be as documented per the program's USAGE function.

Based on the USAGE, we should pass in 'Y'es if running in trickle cycles so that a failure to get a store/day lock won't result in failure of the batch.

function USAGE
{
  echo "USAGE: . $pgmName &

   Username/xxxx@connect. Use "'$UP'" if using Oracle Wallet.
  
   Required parameter. Valid process modes are:
  Y Trickle poll mode
  N Batch mode

   optional parameter. (valid values are:
  SQL_TRACE1, -- no binds and waits
  SQL_TRACE4, -- trace with binds
  SQL_TRACE8, -- trace with waits
  or SQL_TRACE12).-- trace witn binds and waits

"

And here is the code from SA_EXPROC_SALES_BI. PROCESS_EXPORT, which indicates a failure to get a store/day lock will result in failure of the batch during trickle cycles which is incorrect:

  if L_error_encountered then
  O_error_message := SQL_LIB.CREATE_MSG('STORE_DAY_PROC_ERR',
  NULL,
  NULL,
  NULL);
  if I_batch_mode = 'Y' then
  return FALSE;
  else
  return TRUE;
  end if;
  end if;
 

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. saexprocsales.ksh - Usage appears incorrect

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.