1. Implementation Guide
  2. Data Loads and Initial Batch Processing
  3. Data Requirements
  4. Uploading ZIP Packages

Uploading ZIP Packages

When providing data to the platform, push the compressed files into Object Storage using a ZIP file format. Review the File Transfer Services section for details on how to interact with Object Storage. The ZIP file you use will depend on the data you are attempting to load. The default ZIP file packages are below, but the history ZIP file name is configurable in C_ODI_PARAM using parameter name HIST_ZIP_FILE if a different one is desired.

Table 3-3 Platform ZIP File Usage

Filenames Frequency Notes

RAP_DATA_HIST.zip

Ad Hoc

Used for:

  •  Historical files, such as sales and inventory history for the last 1-2 years.

  •  Loading initial dimensions, such as calendar, merchandise, and location hierarchies prior to history loads.

  •  Initial seeding loads.

RAP_DATA_HIST.zip.1

RAP_DATA_HIST.zip.2 …

RAP_DATA_HIST.zip.N

Ad Hoc / Intraday

Multiple zip uploads are supported for sending historical fact data which should be loaded sequentially. Append a sequence number on the ZIP files starting from 1 and increasing to N, where N is the number of files you are loading. Track the status of the files in C_HIST_FILES_LOAD_STATUS table.

RAP_DATA.zip

RI_RMS_DATA.zip

RI_CE_DATA.zip

RI_MFP_DATA.zip

RI_EXT_DATA.zip

Daily

Can be used for daily ongoing loads into the platform (for RI and foundation common inputs), and for any daily data going to downstream applications through AIF DATA nightly batch. Different files can be used for different source systems.

RI_REPROCESS_DATA.zip

Ad Hoc

Used to upload individual files which will be appended into an existing nightly batch file set.

ORASE_WEEKLY_ADHOC.zip

Ad Hoc

Used for loading AI Foundation files with ad hoc processes.

ORASE_WEEKLY.zip

Weekly

Used for weekly batch files sent directly to AI Foundation.

ORASE_INTRADAY.zip

Intraday

Used for intraday batch files sent directly to AI Foundation.

Other supported file packages, such as output files and optional input files, are detailed in each module’s implementation guides. Except for Planning-specific integrations and customizations (which support additional integration paths and formats), it is expected that all files will be communicated to the platform using one of the filenames above.