|
Parameter Name
|
Parameter Default Value
|
Parameter Sample Value
|
Parameter Comments
|
Explanation/Notes
|
Module
|
Manual/ Programmatic
|
|
JOB_TM_PROCESS_BATCH_ID
|
1506
|
|
The batch id for the current DAILY_TM_PROCESS_JOB job.
|
|
TMS
|
P
|
|
TM_EXCHANGE_RATE_TYPE
|
FIXED
|
|
Determines what Exchange Rate Type to use for currency conversion (FIXED, SPOT, and so on).
|
|
TMS
|
M
|
|
TM_JOB_CHAINING_ENABLED
|
N
|
|
Y if a job starts the next TMS job in the list automatically as it ends, N otherwise.
|
|
TMS
|
M
|
|
TM_CORP_CURRENCY_CODE
|
USD
|
EUR
|
Corporate currency code
|
|
TMS
|
M
|
|
TM_LOAD_JOB00XX
|
|
|
TM Job number 00XX
|
TM modules jobs in the proper order. Do not modify; add any custom jobs to the end of the job chain.
|
TMS
|
M
|
|
TM_LOAD_LOOKBACK_DAYS
|
428
|
|
The number of days to look back into TMS when extracting data.
|
|
TMS
|
M
|
|
TM_LOAD_SINGLE_SOURCE
|
N
|
|
Flag to identify whether to load only a single source or all defined sources (Y/N).
|
|
TMS
|
M
|
|
TM_LOAD_SOURCE_S01
|
|
|
Name of the source system loaded as the 01 job.
|
|
TMS
|
M
|
|
TM_LOAD_TRANS_TYPES
|
‘S’, ‘T’
|
|
|
|
TMS
|
M
|
|
TM_LOAD_TRANS_TYPES_S01
|
‘S’, ‘T’
|
|
|
|
TMS
|
M
|
|
TM_PROCESS_CONNECTION_NAME
|
|
|
Indicates the connection name the TM process job uses.
|
|
TMS
|
P
|
|
TM_PROCESS_DAYS
|
100
|
|
The number of days of TM to extract and process from permanent staging tables.
|
|
TMS
|
M
|
|
TM_PROCESS_RUNNING
|
N
|
|
Flag indicating if TM Process is running. Y/N
|
|
TMS
|
P
|
|
TM_TOLERANCE_DAYS
|
3
|
|
Grace period (in days) after which package is deemed to be failed delivery
|
|
TMS
|
M
|
|
TM_UNKNOWN_VALUE
|
Unknown
|
Unknown
|
Default value to insert for a column containing NULLs. Used for Primary Key Columns.
|
|
TMS
|
M
|
|
TM_WEIGHT_CAT_MAX
|
150
|
|
MAX Weight Value to individually categorize
|
|
TMS
|
M
|
|
TM_WEIGHT_CAT_UNITS
|
1
|
|
Units to increment each weight category. Value MUST be greater than 0
|
|
TMS
|
M
|
|
TM_WEIGHT_CAT_UOM
|
LB
|
|
Unit of Measure for Weight Category Buckets (LB or KG)
|
|
TMS
|
M
|
|
TM_SourceConvert_SchemaORA
|
p2009dev
|
|
The name of the Oracle schema. Not necessary for Progress source because it always uses PUB.
|
|
TMS
|
M
|
|
TM_SourceConvert_TargetSource
|
oracle
|
|
Tells the conversion procedure what the type of db the load tables will source from. Values either: oracle or progress
|
|
TMS
|
M
|
|
TM_SourceConvert_TMSMSTRConnectionName
|
TMS_MASTER
|
|
The name of the connection the TMS load tables are using. ***All load tables using this connection are updated.
|
|
TMS
|
M
|
|
Related to:
|
Information Needed
|
|
Progress Database
|
Have they already set up ODBC connections to Progress? If not, answer the following Progress database questions for each data source being implemented.
|
|
Progress Database
|
ERP Version
|
|
Progress Database
|
Progress Version (must be 10.1B03 or above)
|
|
Progress Database
|
Preferred connection name.
|
|
Progress Database
|
Host Name
|
|
Progress Database
|
Port Number
|
|
Progress Database
|
Database Name
|
|
Progress Database
|
User ID
|
|
Progress Database
|
Password
|
|
Tomcat
|
URL
|
|
Tomcat
|
Port Number
|
|
SQL Server
|
Host Name
|
|
SQL Server
|
Port Number
|
|
Email for Portal
|
Host Name
|
|
Email for Portal
|
Port Number
|
|
Email for Portal
|
Authorization? Y or N
|
|
Parameter Name
|
Parameter Default Value
|
Parameter Comments
|
Notes
|
Module
|
|
AP_EE_HISTORY_DATE_MIN
|
<customer defined - usually three years back. YYYYMMDD>
|
The date the AP aging table refreshes from. Three years back is common. For example, 20081231
|
|
FIN
|
|
AP_EE_SNAPSHOT_HIST_START_DATE
|
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
|
|
AP_SE_SNAPSHOT_HIST_START_DATE
|
2009-01-01
|
The first date in the AP aging snapshot table in the format YYYY-MM-DD for the first run
|
|
FIN
|
|
AR_EE_HISTORY_DATE_MIN
|
<customer defined - usually three years back. YYYYMMDD>
|
The date the AP aging table refreshes from. Three years back is common. For example, 20081231
|
|
FIN
|
|
AR_EE_SNAPSHOT_HIST_START_DATE
|
2008-12-31
|
The first date in the AR aging snapshot table in the format YYYY-MM-DD for the first run
|
|
FIN
|
|
AR_SE_SNAPSHOT_HIST_START_DATE
|
2009-01-01
|
The first date in the AR aging snapshot table in the format YYYY-MM-DD for the first run
|
|
FIN
|
|
CORP_CURRENCY_CODE
|
USD
|
Corporate currency code used for high-level reporting
|
The currency code for corporate amounts calculations. Same for entire warehouse.
|
COM
|
|
DAILY_LOAD_SOURCE_S01
|
<Enter data source name here for initial setup>
|
Name of the source system loaded as the 01 job.
|
The connection name of the first or primary source system.
|
COM
|
|
DAILY_LOAD_SOURCE_S02 - DAILY_LOAD_SOURCE_Sxx
|
Does not exist by default; add if additional source(s)
|
|
If needed, the connection name(s) of the second and subsequent source systems
|
COM
|
|
DEFAULT_ACCOUNT
|
00000
|
The default value used for unknown account
|
Must not be a real account code
|
COM
|
|
DEFAULT_COST_CENTER
|
0000
|
The default value used for unknown cost center
|
Must not be a real cost center code
|
COM
|
|
DEFAULT_DOMAIN
|
00000
|
The default value used for unknown domain
|
Must not be a real domain code
|
COM
|
|
DEFAULT_ENTITY
|
0000
|
The default value used for unknown entity
|
Must not be a real entity code
|
COM
|
|
DEFAULT_PROJECT
|
00000
|
The default value used for unknown project
|
Must not be a real project code
|
COM
|
|
DEFAULT_SOURCE
|
|
The default value used for unknown source system
|
Must not be a real source system code
|
COM
|
|
DEFAULT_SUB_ACCOUNT
|
0000000
|
The default value used for unknown sub-account
|
Must not be a real sub-account code
|
COM
|
|
GL_LOAD_DAYS
|
152
|
The number of days to load from the look back days forward for GL-related transactional tables
|
NOTE: Set to a high value for History loads to load all data desired for historical purposes. Then set to a lower value for Daily loads. Must always be larger than GL_LOAD_LOOKBACK_DAYS.
|
FIN
|
|
GL_LOAD_LOOKBACK_DAYS
|
150
|
The number of days to look back for changes in QAD in a table for GL-related transactional tables.
|
NOTE: Set to a high value for History loads to load all data desired for historical purposes. Then set to a lower value for Daily loads. Must always be smaller than GL_LOAD_ DAYS.
|
FIN
|
|
GL_PERIOD1_FISCAL_ACCOUNT_ZERO_TYPES
|
|
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.
|
|
FIN
|
|
HIST_LOAD_SOURCE_S01
|
<Enter data source name here for initial setup>
|
QMI
|
Name of the source system loaded as the 01 job.
|
COM
|
|
HIST_LOAD_SOURCE_S02 - HIST_LOAD_SOURCE_Sxx
|
Does not exist by default; add if additional source
|
2010SE
|
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_01
|
<Enter data source name here for initial setup>
|
Name of the connection 01 used as a source system for cloning jobs.
|
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_01_RUN
|
N
|
This determines if the Initial Job Setup has been run against this data source yet or not. Any new data source must have an N. Value is set to C when historic load has completed.
|
Used by INITIAL_JOB_SETUP job to ensure that existing data sources are NOT rerun as part of the historic load when new sources are added.
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_01_TYPE
|
<Enter source type - SE, EE, or EAM>
|
Connection Type - SE for Standard Edition Financials, EE for Enterprise Edition Financials, and EAM for Enterprise Asset Management. Defaults to SE
|
Used to determine whether to set up EE Financial or SE Financial jobs for this data source.
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_02_DAILY_MODULES
|
COM, OM, OP, FIN, EAM
|
Example: 'COM, FIN' - List Modules to be part of DAILY job chain.
|
Added in 3.7 - Set to list of modules appropriate to the source. Default is fine for most installations as any uninstalled modules are skipped.
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_02_HIST_MODULES
|
COM, OM, OP, FIN, EAM
|
Example: 'COM, FIN' - List Modules to be part of HIST job chain.
|
Added in 3.7 - Set to list of modules appropriate to the source. Default is fine for most installations as any uninstalled modules are skipped.
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_02
|
|
Name of the connection 02 used as a source system for cloning jobs.
|
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_02_RUN
|
|
This determines if the Initial Job Setup has been run against this data source yet or not. Any new data source must have an N.
|
Added in 3.4.1 – Used by INITIAL_JOB_SETUP job to ensure that existing data sources are NOT rerun as part of the historic load when new sources are added.
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_02_TYPE
|
<Enter source type - SE, EE, or EAM>
|
Connection Type - SE for Standard Edition Financials, EE for Enterprise Edition Financials, EAM for Enterprise Asset Management. Defaults to SE.
|
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_02_DAILY_MODULES
|
COM, OM, OP, FIN, EAM
|
Example: 'COM, FIN' - List Modules to be part of DAILY job chain.
|
Added in 3.7 - Set to list of modules appropriate to the source. Default is fine for most installations as any uninstalled modules are skipped.
|
COM
|
|
INITIAL_JOB_SETUP_CONNECTION_02_HIST_MODULES
|
COM, OM, OP, FIN, EAM
|
Example: 'COM, FIN' - List Modules to be part of HIST job chain.
|
Added in 3.7 - Set to list of modules appropriate to the source. Default is fine for most installations as any uninstalled modules are skipped.
|
COM
|
|
INITIAL_JOB_SETUP_DATE
|
<Set to today's date before starting the initial history load>
|
Added in 3.4.1. INITIAL_JOB_SETUP uses this date to populate ussthe majority of the previously manually populated date fields for job setup.
|
|
COM
|