FPSAPP.CFG_TABLES

TABLE_NAME

VARCHAR2(30)

APF_REP_PARM_W_COLON_DELIM

VARCHAR2(128)

We pass this value to the APF report as the parameter(s). The script replaces colon so we must use colon as the delimiter. This column works only for QE, CLR, CLRA and not ST because the dispatcher handles parameters differently.

CHK_UPD_COLUMN_NAME

VARCHAR2(30)

Our most important check on the DWH is the check for no recent day in key tables. For a table to be part of this check, enter the column to check here which must be a DATE and the number of minutes to warn in CHK_UPD_MINUTES. 30 minutes is a reasonable number for a table that is part of the 3min load which means we will send warning emails if the newest record is more than 30 minutes old.

CHK_UPD_MINUTES

NUMBER(5)

See CHK_UPD_COLUMN_NAME.

DO_NOT_CHECK_DIFFS_LOOP

CHAR(1)

For tables loaded by ADM_TABLE_LOOP the default is to use a minus query to check for differences and only update the necessary rows. But if we know that all rows will change on each load then we can skip this check and just update all rows.

DO_NOT_WARN_FPSINPUT_DBPR

CHAR(1)

We strongly discourage use of DBPR for FPSINPUT tables because the refresh deletes and reinserts every row in the table. CHK_LOAD warns against this configuration. But there are certain cases where DBPR is appropriate, for example when the start date in WIP_STARTS changes almost every query in the customer data, so if this flag is set then we do not warn about this.

DURATION_SEC

NUMBER(9)

Duration in seconds of the period to be used to run the APF report. Used only for CLR, CLRA, and QE.

END_REP_START_SHIFT

CHAR(1)

This column is obsolete and will be dropped from the table in the next DWH version.

ERROR_PRIORITY

VARCHAR2(10)

This is just informative and used in FPSRPT objects but this could be used in SYSMNTR in the future. It is a string field so it can be a word or a number.

ERR_IF_NO_ROWS

CHAR(1)

If set to Y then the job will error if no rows are inserted. This cannot be used with DBPM because the match logic frequently updates no rows.

GATHER_STATS_ALWAYS

CHAR(1)

For large history tables, we normally check if we should skip gathering stats during ADM_STATS_ALL. This flag forces the procedure to always gather stats on this table.

GATHER_STATS_NEVER

CHAR(1)

This flag causes ADM_STATS_ALL to never gather stats. This would typically be used for history tables to override the normal checks but could be used for any table if needed.

IS_CHGLOG_ADDL_ENABLED

CHAR(1)

This column allows us to enable CHGLOG table/trigger functionality on additional tables which would not otherwise have it based on our normal manual table or manual columns logic.

IS_CHGLOG_PERM_DISABLED

CHAR(1)

Our FPSINPUT tables have the capability to record all changes in a CHGLOG table as built by BLD_CHGLOG. You can disable this by setting this to Y.

IS_LARGE_MANUAL

CHAR(1)

GrimRepo stores the data for manual tables and it really slows down if the table is large so CHK_TABLES warns if any manual table has over 500 rows. This flag tells CHK_TABLES to stop complaining.

IS_REF_VIEW_USABLE_BY_OTHERS

CHAR(1)

REF views exist solely to refresh their corresponding table. Therefore in CHK_ALL, we flag if a REF view is used by any other object. Usually the solution to escape the wrath of this warning is to use a LOAD_xxx view for the commonly used logic. But occasionally there is a case when it is either impossible or extremely undesirable to do this and we really want to use the REF view in another object. For these special cases we added this column but we hope that you never use it!

LOG_QUERY_START

CHAR(1)

This is for tables loaded by APF only where we run the APF report first and then the sqlplus query. Normally we just log the start and end of the object so the total time includes both report and query. If you want to track each independently set this to Y and we will log a record in ADM_LOAD_HIST at the end of the report which is also the start of the query.

METHOD

VARCHAR2(6)

N

Method used to load data in table or execute procedure (* from FPSADMIN.GEN_LOAD_METHODS)

OTHERS_TO_LOAD_IF_CHG

VARCHAR2(128)

This allows us to load a table only if another table changed. This is rarely used but can save time.

OTHER_TABLE_WHERE_LOADED

VARCHAR2(30)

Some of our APF reports load multiple tables in the same report. It is required to pick one of those tables to name the update. The other tables will have the method of OTHTAB with the name of the other table whose job loads it in this column.

OVR_PURGE_CHGLOG_DAYS

NUMBER(5,1)

By default we purge history from CHGLOG tables at 365 days for small tables and 99 days for large tables. To override that default for the corresponding CHGLOG table then set in this value. If you do not want to purge at all then set this to 9999.

OVR_STATION_VAR

VARCHAR2(12)

This allows us to pass a value for $Station to an APF report or rule. This is rarely used.

OWNER

VARCHAR2(30)

N

PURGE_COLUMN_NAME

VARCHAR2(30)

This must be the name of a DATE or TIMESTAMP column which is the first column in an index. See PURGE_DAYS.COLUMN_NAME comment for purge details.

PURGE_DAYS

NUMBER(5,1)

All history tables must have the PURGE_COLUMN_NAME and PURGE_DAYS set. We automatically purge data older than DAYS to keep the history tables to a reasonable size. We must keep at least 10 days worth of data in all tables (except DASH_P_H_SHIFT_SUMMARY) with the logic being that gives us 3 days to append from the raw table to the week history. If you do not want to purge then set DAYS to 9999.

RPT_OWNER_NAME

VARCHAR2(64)

This field is used to indicate who owns this FPSRPT object. It is for informational purposes only and not used in the FPS DWH.

RPT_PROJECT

VARCHAR2(50)

This field is used to categorize FPSRPT objects. It is for informational purposes only and not used in the FPS DWH.

TIMEOUT_SEC

NUMBER(4)

This column is required with the status_tool (ST) method which calls the APF dispatcher but only works with this method. Status_tool allows a -timeout parameter as one of the inputs and we will pass that if specified here.