In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |

  •     QAD Glossary

  • Historic Reload Instructions
    The following is a checklist of things to consider and keep in mind when doing a historic reload:
    Is this a complete reload from the ERP or is it a historic reload from the perm tables? A complete load of the ERP is required only if there is a problem with the data in the relevant perm tables, such as perm_transaction_history. It is a time-consuming process, in particular with the large tables like tr_hist or gltr_hist.
    Is the environment being reloaded a single source or a multi-source environment? For multiple data source environments, account for extra considerations to ensure that parameters are set properly so that the load tables pick up the data from the right source and label that source properly.
    Is there a need to only load a single fact or load all facts for the module? If all the fact tables should be reloaded, fewer steps are needed because the relative historic load job for that module can be run. If only one table should be loaded, it is smarter to clone an existing job and remove all the parts relative to loading of other fact tables, leaving in only the things needed for the fact table in question.