1. Implementation Guide
  2. Data Loads and Initial Batch Processing
  3. Loading Data from Files
  4. Load History Data
  5. Other History Loads

Other History Loads

While sales and inventory are the most common facts to load history for, you may also want to load history for other areas such as receipts and transfers. Separate ad hoc history load processes are available for the following fact areas:

  • HIST_CSV_ADJUSTMENTS_LOAD_ADHOC

  • HIST_CSV_INVRECEIPTS_LOAD_ADHOC

  • HIST_CSV_MARKDOWN_LOAD_ADHOC

  • HIST_CSV_INVRTV_LOAD_ADHOC

  • HIST_CSV_TRANSFER_LOAD_ADHOC

  • HIST_CSV_DEAL_INCOME_LOAD_ADHOC

  • HIST_CSV_ICMARGIN_LOAD_ADHOC

  • HIST_CSV_INVRECLASS_LOAD_ADHOC

  • HIST_STG_CSV_SALES_WF_LOAD_ADHOC

  • HIST_SALES_WF_LOAD_ADHOC

All of these interfaces deal with transactional data (not positional) so you may use them at any time to load history files in each area.

Note:

These processes are intended to support history data for downstream applications such as AI Foundation and Planning, so the tables populated by each process by default should satisfy the data needs of those applications. Jobs not needed by those apps are not included in these processes.

Some data files used by AIF and Planning applications do not have a history load process, because the data is only used from the current business date forwards. For Purchase Order data (ORDER_DETAIL.csv), refer to the section below on Seed Positional Facts if you need to load the file before starting your nightly batch processing. For other areas like transfers/allocations used by Inventory Planning Optimization, those jobs are only included in the nightly batch schedule and do not require any history to be loaded.