|
Parameter Name
|
Parameter Default Value
|
Parameter Sample Value
|
Parameter Comments
|
Explanation/Notes
|
Module
|
Manual/ Programmatic
|
|
AP_CHECK_PROCESS_DAYS
|
60
|
60
|
Used to find any checks to be processed which covers up to 60 days backdated.
|
|
FIN
|
M
|
|
AP_EE_HISTORY_DATE
|
|
20081231
|
The date the AP aging table is to be refreshed from. Three years back is common. For example, 20081231
|
Set from AP_EE_HISTORY_DATE_MIN when initial job setup is run.
|
FIN
|
P
|
|
AP_EE_HISTORY_DATE_MIN
|
<customer defined - usually three years back. YYYYMMDD>
|
20081231
|
The date the AP aging table refreshes from. Three years back is common. For example, 20081231
|
Added this in 3.4.1 to handle historic loads from multiple EE sources.
|
FIN
|
M
|
|
AP_EE_HISTORY_DATE_Sxx
|
|
20081231
|
Inserted via WsParameterWrite
|
Created by procedures. - 3.4.1, using the AP_EE_HISTORY_DATE. Sxx references which EE source number this date is for.
|
FIN
|
P
|
|
AP_EE_SNAPSHOT_FREQUENCY
|
M
|
M
|
The frequency of snapshots in the AP aging snapshot tables. Possible values are: D for Daily, W for Weekly, M for Monthly, B for both weekly and monthly.
|
Daily results in seven times the amount of data as Weekly; Weekly is approximately four times the amount of data as Monthly. Both Weekly and Monthly means that you get a record for each end-of-week date as well as a record for each end-of-month date. Determine frequency based upon desired view level (i.e., do you want to be able to compare things on a monthly, weekly, or daily basis), number of days of data to view (i.e., how far back should the data go in the fact table), and amount of physical disk space available
|
FIN
|
M
|
|
AP_EE_SNAPSHOT_HIST_START_DATE
|
2008-12-31
|
2008-12-31
|
The first date in the AP aging snapshot table in the format YYYY-MM-DD for the first run
|
Date used for start of AP snapshot in History load. Used for History load only; Daily loads use AP_EE_SNAPSHOT_NUM_DAYS
|
FIN
|
M
|
|
AP_EE_SNAPSHOT_NUM_DAYS
|
31
|
31
|
The number of days of snapshots to load back each run.
|
Number of days to include in snapshot. Used to determine AP_EE_SNAPSHOT_START_DATE, which is calculated as TODAY - this value.
|
FIN
|
M
|
|
AP_EE_SNAPSHOT_REPLACE_FLAG
|
N
|
N
|
Indicates that snapshots are replaced or not. Y for replace, N for not replaced.
|
Y to replace the snapshot for recalculated periods when the snapshot job is run; N to add new records and not update previously calculated records. Default value is N.
|
FIN
|
M
|
|
AP_EE_SNAPSHOT_START_DATE
|
1996-11-12
|
1997-05-24
|
The first date in the AP aging snapshot table in the format YYYY-MM-DD
|
Calculated as TODAY minus AP_EE_SNAPSHOT_START_DATE
|
FIN
|
P
|
|
AP_PROCESS_CONNECTION_NAME
|
|
2010SE
|
Indicates the connection name used by the AP process job
|
Connection name used by the currently running AP process, or if no AP job is running, the last-used source connection
|
FIN
|
P
|
|
AP_PROCESS_DAYS
|
10
|
10
|
The number of days of AP to extract and process from permanent staging tables.
|
|
FIN
|
M
|
|
AP_PROCESS_RUNNING
|
N
|
N
|
Indicates if an AP process is currently running (Y,N)
|
Used to prevent multiple copies of the AP job from running at the same time. Under normal conditions, you should not update this manually. However, if a job fails and is deleted, reset this to "N" to run the job again. But use caution and ensure that there really is no copy of the job running before changing from to "N" from "Y".
|
FIN
|
P
|
|
AP_PROCESS_RUNNING_JOB_NAME
|
|
DAILY_EE_AP_CHAINED
|
Indicates the current or last run job name for AP processing.
|
|
FIN
|
P
|
|
AP_REVALUE_PERIODS
|
30
|
30
|
The number of periods to revalue in invoice history
|
|
FIN
|
M
|
|
AP_SE_HISTORY_PROCESS_DATE
|
Current date
|
2012-01-31
|
Generally internal use only. Internally set to current date, unless DAILY_HISTORY_DATE_SET_CURRENT = N.
|
Used for testing purposes to process AP records for a different date. Typically should be programatically set to the current date.
|
FIN
|
M/P
|
|
AP_SE_SNAPSHOT_FREQUENCY
|
M
|
M
|
The frequency of snapshots in the AP aging snapshot tables. Possible values are: D for Daily, W for Weekly, M for Monthly, B for both weekly and monthly.
|
|
FIN
|
M
|
|
AP_SE_SNAPSHOT_HIST_START_DATE
|
2009-01-01
|
2009-01-01
|
The first date in the AP aging snapshot table in the format YYYY-MM-DD for the first run
|
Date used for start of AP snapshot in History load. Used for History load only; Daily loads use AP_SE_SNAPSHOT_NUM_DAYS
|
FIN
|
M
|
|
AP_SE_SNAPSHOT_NUM_DAYS
|
31
|
31
|
The number of days of snapshots to load back each run.
|
Number of days to include in snapshot. Used to determine AP_SE_SNAPSHOT_START_DATE, which is calculated as TODAY - this value.
|
FIN
|
M
|
|
AP_SE_SNAPSHOT_REPLACE_FLAG
|
N
|
N
|
Indicates that snapshots are replaced or not. Y for replace, N for not replaced.
|
Y to replace the snapshot for recalculated periods when the snapshot job is run; N to add new records and not update previously calculated records. Default value is N.
|
FIN
|
M
|
|
AP_SE_SNAPSHOT_START_DATE
|
2009-01-01
|
2009-01-01
|
The first date in the AP aging snapshot table in the format YYYY-MM-DD that loads this run.
|
Calculated as TODAY minus AP_SE_SNAPSHOT_START_DATE
|
FIN
|
P
|
|
AR_EE_HISTORY_DATE
|
|
20081231
|
The date the AR aging table refreshes from. Three years back is common. For example, 20081231
|
|
FIN
|
P
|
|
AR_EE_HISTORY_DATE_MIN
|
<customer defined - usually three years back. YYYYMMDD>
|
20081231
|
The date the AP aging table refreshes from. Three years back is common. For example, 20081231
|
Added this in 3.4.1 to handle historic loads from multiple EE sources.
|
FIN
|
M
|
|
AR_EE_HISTORY_DATE_Sxx
|
|
20081231
|
Inserted via WsParameterWrite
|
Created by procedures. - 3.4.1, using the AP_EE_HISTORY_DATE. Sxx references which EE source number this date is for.
|
FIN
|
P
|
|
AR_EE_SNAPSHOT_FREQUENCY
|
M
|
M
|
The frequency of snapshots in the AR aging snapshot tables. Possible values are: D for Daily, W for Weekly, M for Monthly, B for both weekly and monthly.
|
|
FIN
|
M
|
|
AR_EE_SNAPSHOT_HIST_START_DATE
|
2008-12-31
|
2008-12-31
|
The first date in the AR aging snapshot table in the format YYYY-MM-DD for the first run
|
Date used for start of AR snapshot in History load. Used for History load only; Daily loads use AR_EE_SNAPSHOT_NUM_DAYS
|
FIN
|
M
|
|
AR_EE_SNAPSHOT_NUM_DAYS
|
31
|
31
|
The number of days of snapshots to load back each run.
|
Number of days to include in snapshot. Used to determine AR_EE_SNAPSHOT_START_DATE, which is calculated as TODAY - this value.
|
FIN
|
M
|
|
AR_EE_SNAPSHOT_REPLACE_FLAG
|
N
|
N
|
Indicates that snapshots are replaced or not. Y for replace, N for not replaced.
|
Y to replace the snapshot for recalculated periods when the snapshot job is run; N to add new records and not update previously calculated records. Default value is N.
|
FIN
|
M
|
|
AR_EE_SNAPSHOT_START_DATE
|
1996-11-12
|
1997-05-24
|
The first date in the AR aging snapshot table in the format YYYY-MM-DD
|
Calculated as TODAY minus AR_EE_SNAPSHOT_START_DATE
|
FIN
|
P
|
|
AR_PROCESS_DAYS
|
10
|
10
|
The number of days of AR to extract and process from permanent staging tables.
|
|
FIN
|
M
|
|
AR_PROCESS_RUNNING
|
N
|
N
|
Indicates if an AR process is currently running (Y,N)
|
Used to prevent multiple copies of the AR job from running at the same time. Under normal conditions, you should not update this manually. However, if a job fails and is deleted, reset this to "N" to run the job again. But use caution and ensure that there really is no copy of the job running before chaning from to "N" from "Y".
|
FIN
|
P
|
|
AR_PROCESS_RUNNING_JOB_NAME
|
|
DAILY_EE_AR_CHAINED
|
Indicates the current or last run job name for AR processing.
|
|
FIN
|
P
|
|
AR_REVALUE_PERIODS
|
30
|
30
|
The number of periods to revalue in invoice history
|
|
FIN
|
M
|
|
AR_SE_SNAPSHOT_FREQUENCY
|
M
|
M
|
The frequency of snapshots in the AR aging snapshot tables. Possible values are: D for Daily, W for Weekly, M for Monthly, B for both weekly and monthly.
|
|
FIN
|
M
|
|
AR_SE_SNAPSHOT_HIST_START_DATE
|
2009-01-01
|
2009-01-01
|
The first date in the AR aging snapshot table in the format YYYY-MM-DD for the first run
|
Date used for start of AR snapshot in History load. Used for History load only; Daily loads use AR_SE_SNAPSHOT_NUM_DAYS
|
FIN
|
M
|
|
AR_SE_SNAPSHOT_NUM_DAYS
|
31
|
31
|
The number of days of snapshots to load back each run.
|
Number of days to include in snapshot. Used to determine AS_EE_SNAPSHOT_START_DATE, which is calculated as TODAY - this value.
|
FIN
|
M
|
|
AR_SE_SNAPSHOT_REPLACE_FLAG
|
N
|
N
|
Indicates that snapshots are replaced or not. Y for replace, N for not replaced.
|
Y to replace the snapshot for recalculated periods when the snapshot job is run; N to add new records and not update previously calculated records. Default value is N.
|
FIN
|
M
|
|
AR_SE_SNAPSHOT_START_DATE
|
2009-01-01
|
1997-05-24
|
The first date in the AR aging snapshot table in the format YYYY-MM-DD loads this run.
|
Calculated as TODAY minus AR_SE_SNAPSHOT_START_DATE
|
FIN
|
P
|
|
BUDGET_ACTUAL_ROW
|
ACTUAL
|
ACTUAL
|
The source data for the actual row in the budget dimension
|
|
FIN
|
M
|
|
GL_EE_POST_MAX
|
0
|
0
|
0
|
|
FIN
|
P
|
|
GL_EE_POST_MAX_Sxx
|
Does not exist until first EE GL load
|
441563
|
DON’T UPDATE MANUALLY. Maximum Posting Id to extract this iteration.
|
|
FIN
|
P
|
|
GL_EE_POSTLINE_MAX
|
0
|
0
|
0
|
|
FIN
|
P
|
|
GL_EE_POSTLINE_MAX_Sxx
|
Does not exist until first EE GL load
|
441569
|
DON’T UPDATE MANUALLY. Maximum Posting Line Id to extract this iteration.
|
|
FIN
|
P
|
|
GL_EE_SOURCE_Sxx
|
Does not exist until first EE GL load
|
QMI
|
Inserted via WsParameterWrite
|
|
FIN
|
P
|
|
GL_HISTORY_LOAD_REQUIRED
|
Y
|
N
|
Controls initial processing of loading of historical GL data. Always 'N' unless an initial history load is required
|
|
FIN
|
P
|
|
GL_LOAD_DAYS
|
152
|
52
|
The number of days to load from the look back days forward for GL-related transactional tables
|
|
FIN
|
M
|
|
GL_LOAD_LOOKBACK_DAYS
|
150
|
50
|
The number of days to look back for changes in QAD in a table for GL-related transactional tables
|
|
FIN
|
M
|
|
GL_LOAD_PERIOD_FROM
|
199301
|
199705
|
The starting period for changes in QAD in a table for GL-related transactional tables. Calculated using parameter GL_LOAD_LOOKBACK_DAYS.
|
|
FIN
|
P
|
|
GL_LOAD_PERIOD_TO
|
201002
|
201012
|
The finishing period for changes in QAD in a table for GL-related transactional tables. Calculated using parameters GL_LOAD_LOOKBACK_DAYS and GL_LOAD_DAYS.
|
|
FIN
|
P
|
|
GL_PERIOD1_FISCAL_ACCOUNT_ZERO_TYPES
|
|
“I”,”E”
|
Account types to set to zero in fact_gl_balances when a new fiscal period starts. If null, none are set. The proper values in this parameter should be a list of account codes such that the string would be appropriate in an "IN" clause.
|
Make sure this is formatted such that it can be inserted directly into a SQL “In” clause – including single-quotes around the value(s)
|
FIN
|
M
|
|
GL_POST_LOOP_NO
|
0
|
0
|
|
|
FIN
|
P
|
|
GL_PROCESS_CONNECTION_NAME
|
|
2010SE
|
Indicates the connection name used by the GL process job
|
|
FIN
|
P
|
|
GL_PROCESS_DAYS
|
10
|
10
|
The number of days of GL to extract and process from permanent staging tables.
|
|
FIN
|
M
|
|
GL_PROCESS_RUNNING
|
N
|
N
|
Indicates if a GL process is currently running (Y,N)
|
Used to prevent multiple copies of the GL job from running at the same time. Under normal conditions, do not update this manually. However, if a job fails and is deleted, reset this to "N" to run the job again. But use caution and ensure that there really is no copy of the job running before chaning from to "N" from "Y".
|
FIN
|
P
|
|
GL_PROCESS_RUNNING_JOB_NAME
|
|
DAILY_EE_GL_CHAINED
|
Indicates the GL process that is currently running or the GL process that last ran.
|
|
FIN
|
P
|
|
GL_YEAR_END_ACCOUNT
|
121100
|
121100
|
The default account for the year end carries over amount
|
Not used currently
|
FIN
|
M
|
|
GLTR_HIST_CONNECTION_NAME
|
|
2010SE
|
Inserted via WsParameterWrite
|
|
FIN
|
P
|
|
GLTR_HIST_DOMAIN
|
|
'QAD','QP','QPAU','train'
|
Inserted via WsParameterWrite
|
|
FIN
|
P
|
|
GLTR_HIST_LOAD_MAXSIZE
|
500000
|
500000
|
The maximum number of rows to load in an iteration loading gltr_hist
|
|
FIN
|
P
|
|
GLTR_HIST_LOOP_NO
|
0
|
0
|
DON’T UPDATE MANUALLY. The iteration number loading tr_hist.
|
|
FIN
|
P
|
|
GLTR_HIST_ROW_COUNT
|
0
|
4919
|
DON’T UPDATE MANUALLY. Number of rows loaded into gltr_hist.
|
|
FIN
|
P
|
|
GLTR_HIST_TRAN_MAX
|
0
|
200704110004148000.00
|
DON’T UPDATE MANUALLY. Maximum Transaction Id to extract this iteration.
|
|
FIN
|
P
|
|
GLTR_HIST_TRAN_MIN
|
-1
|
-1
|
DON’T UPDATE MANUALLY. Minimum Transaction Id to extract this iteration.
|
|
FIN
|
P
|
|
HIST_LOAD_EE_AP_RUNNING
|
N
|
C
|
Indicates the EXTRA_DAY_EE_AP_HISTORY load processes is underway. C for completed, Y for yes or N for no.
|
Added in 3.4.1 – Used by the HIST_EE_AP_AR_FINISH_CHECK job to determine if it can let the next set of jobs run.
|
FIN
|
P
|
|
HIST_LOAD_EE_AR_RUNNING
|
N
|
C
|
Indicates the EXTRA_DAY_EE_AR_HISTORY load processes is underway. C for completed, Y for yes or N for no.
|
Added in 3.4.1 – Used by the HIST_EE_AP_AR_FINISH_CHECK job to determine if it can let the next set of jobs run.
|
FIN
|
P
|
|
HIST_LOAD_GLTR_HIST_RUNNING
|
N
|
C
|
Indicates a gltr_hist history load processes is underway. C for completed, Y for yes or N for no.
|
|
FIN
|
P
|
|
JOB_AP_PROCESS_BATCH_ID
|
0
|
749
|
The batch id for the current DAILY_AP_PROCESS job.
|
|
FIN
|
P
|
|
JOB_AR_PROCESS_BATCH_ID
|
0
|
750
|
The batch id for the current DAILY_AR_PROCESS job.
|
|
FIN
|
P
|
|
JOB_GL_PROCESS_BATCH_ID
|
0
|
751
|
The batch id for the current DAILY_GL_PROCESS job.
|
|
FIN
|
P
|