W_ETL_LOAD_DATES - Prune Days

Charles M

Hi All -

Does anyone have clarity on the following columns in the W_ETL_LOAD_DATES table: LAST_MAX_DATE, ETL_LOAD_DATE, AND WIP_LOAD_START_DATE? I think that I may have a "fuzzy" understanding of them . Also, I am not totally clear on their relationship with the prune days parameter either.

Here's my take:

After recently finding a table named W_ETL_LOAD_DATES_LOG, I could view historical data of executions, versus only the current record in W_ETL_LOAD_DATES. I was then able to compare to records from the SNP_SESSION table, which has startup variables, session begin & end times, etc. It looks to me like the W_ETL_LOAD_DATES/LOG.ETL_LOAD_DATE column is the same as SNP_SESSION.SESS_END - so, when the session is finished, the load date gets updated. Now, the W_ETL_LOAD_DATES/LOG.WIP_LOAD_START_DATE columns shows a value which is 1 day/24 hours earlier. This makes sense because the SNP_SESSION.STARTUP_VARIABLES value for prune days was '1'. So, each time there was a change to the prune day parameter, I can see that it gets updated here - we've done multiple values, many times, and it seems to check out each time. However, the W_ETL_LOAD_DATES/LOG.LAST_MAX_DATE doesn't seem to make as much sense, from what I can see. It does change, but I can't correlate it to anything 100% of the time. Please let me know if anyone has found more meaning than this.

OBIA 11.1.1.10.1

Regards,

Charles