Oracle Retail Knowledge Base

20 Batch Processing

5 min read

Mirror of Oracle documentation

Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.

20 Batch Processing

This chapter provides an overview of the batch processing capabilities available for the application.

Overview

The implementation process involves loading data files for dimensions and fact data into the database. For new implementations, the best practice is to test the interfaces in a logical sequence, in small test cycles..

Once all required data has been loaded and all interfaces have been tested, the scheduled batch cycles that perform different tasks can be used, depending on the frequency involved. The application has DAILY, WEEKLY, and QUARTERLY batch cycles, each of which performs different tasks, depending on which applications are being used.

Incremental Exports

All incremental export files are controlled by a set of dates that define the beginning and ending range of data to be exported. This data is stored in a configuration table called RSE_EXP_GRP and can be seen in the Manage Configuration screen. Each incremental export has a date associated with the data to be exported. Only data that has a date/time value between the FROM_DT and TO_DT columns of the RSE_EXP_GRP that it is associated with, will be exported when the export file is created.

When testing an application, it is important to realize that if a test export of data is required, you must make sure that data is available to be exported and that the data is associated with a date that is in the range of the export group. If an export runs and does not produce any data in the file, you should check the values of the Export Group to ensure the dates were not set incorrectly.

When you create or process data in the application user interface, want to test the export of that data, you must advance Export Group’s date range by running the appropriate export preparation step as described in this chapter. This causes the date range to advance and enables the exporting of the data that is available for exporting. Note that if the Export Group date range is advanced too many times, the data that you want to export may no longer be in the current range for exporting.

You may encounter such issues when using this custom batch process to trigger the execution of exports; however, these issues will not occur once the application is running the batch routines in an automated manner, because the batch processes are only executed once per batch cycle.

Batch Process Flow

Figure 20-1 illustrates the batch process flow.

Table 20-1 (Cont.) Supported Zip Files

Zip File NameFrequencyFile TypeNotes
ORASE_INTRADAY.zipIntradayInboundAny inbound file that has an intraday
frequency can be placed in here.
ORASE_WEEKLY_ADHOC.zipWeeklyInboundUsed for instances where AdHoc jobs are
run. Any inbound file for that AdHoc job that
does not start with W_* and has a weekly
frequency can be placed in here.
ORASE_WEEKLY_extract.zipWeeklyOutboundAny outbound file that has a weekly
frequency will be placed in here.
ORASE_INTRADAY_extract.zi
p		IntradayOutboundAny outbound file that has an intraday
frequency will be placed in here.

Configuring Additional Data Files

It may be necessary to configure support for additional data files into AIF, beyond the ORASE_WEEKLY.zip and ORASE_INTRADAY.zip. If this is required, it is possible to configure additional files to go along with those. This section describes how to add support for this.

It is possible to receive additional zip files, with additional suffixes to the existing zip. In this example, the assumption is that a new zip file named ORASE_WEEKLY_IP.zip must be processed when ORASE_WEEKLY.zip is processed. The IP portion of this is what can be configured, as explained below.

Using the Retail AI Foundation Platform’s UI, select the Data Management / Manage Configuration menu options. Then, select RSE_CONFIG_CODE as the table to configure. If you want to search for existing configurations, you can enter a search value of “%ZIP” in the PARAM_NAME Search field and select Search. There are no default extensions defined here, but once one has been created, this will display them.

To add a new entry to allow processing this additional file, select the Create Param icon to add a new configuration. You can enter values such as those shown in Table 20-2 into the dialog box.

Table 20-2 Additional Data Files

FieldValueNotes
APPL_CODERSE
PARAM_NAMEORASE_WEEKLY_ZIPThe format of this is important. If adding an
additional file for the Intraday batch, the
value would be ORASE_INTRADAY_ZIP
instead.
PARAM_CODEIPThis is the suffix that the additional zip will
use.
PARAM_VALUEYY to enable this, or N to disable this file.
CONFIGURABLE_FLGYFixed value.
UPDATEABLE_FLGNFixed value.
DESCRAdditional zip for IP files.Adjust this description so it describes the zip
contents/source.

Based on the example values in Table 20-2, a new zip file named ORASE_WEEKLY_IP.zip will now be expected when the ORASE_WEEKLY.zip is expected.

If a file configured as defined above must be temporarily disabled, you can edit the PARAM_VALUE via the UI,so that it has a value of “N” instead of a value of “Y”.

File Transmissions

Files required for processing such as the ORASE_WEEKLY.zip file and the ORASE_WEEKLY_IW.zip file must be uploaded to Object Storage using the File Transfer Service (FTS). For uploading to Object Storage, it must include the incoming prefix and file name. For more information on FTS, refer to the “Implementation Tools File Transfer Services” chapter in the Oracle Retail Analytics and Planning Implementation Guide .

In this guide

  • 8 Affinity Analysis — AI Foundation Implementation Guide · shares PARAM_CODE, RSE_CONFIG_CODE
  • 17 Configuration — AI Foundation Implementation Guide · shares APPL_CODE, CONFIGURABLE_FLG, PARAM_CODE, RSE_CONFIG_CODE

Graph View

Backlinks