E Appendix: MFPCS Scheduling in JOS/POM

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.

E

Appendix: MFPCS Scheduling in JOS/POM

MFPCS provides a default job schedule with a detailed list of jobs with pre-defined dependencies with RI and AIF schedules in RAP integration. The customer can easily customize their batch process by controlling the batch control files without changing the batch schedule. Each batch job in MFP is connected to hooks in the batch control files that can be changed by customers. The MFP job flow only contains daily and weekly jobs. Jobs scheduled in the Daily flow are scheduled to run every day except Sunday (other than the Start and End Job for the process) and jobs scheduled to run in the Weekly flow are scheduled to run only on Sunday by default.

The following table shows the list of jobs in MFP Schedule. Only jobs with Template configuration entries are pre-configured for the MFP Template version. The rest of the jobs are placeholder jobs to allow changes to the schedule of the jobs or to add more jobs by changing the batch control file. Each MFP job calls the same set names in the batch control file without JOB in the name, which in turn allows it to call respective *hook jobs, so even if it is not linked to a batch set. The batch can be controlled without changing the job flow by adding or changing the hooks.

For more details about the implementation of JOS/POM, see the Oracle Retail Predictive Application Server Cloud Edition Implementation Guide . For more details about how to use JOS/POM to schedule and maintain the job flows, see the Oracle Retail Process Orchestration and Monitoring User Guide .

MFP Job Name	Description/Comments	Daily/Weekly	Template Configuration
MFP_PRE_EXP_START_JOB	Dummy Job, to specify the start of pre-batch exports.	Daily
MFP_PRE_EXP_RDX_D_JOB	To schedule any daily plan exports to RAP integration before the calc cycle.	Daily
MFP_PRE_EXP_OBS_D_JOB	To schedule any daily plan exports to Object Storage before the calc cycle.	Daily	Exports Standard Plans, if the Export Daily Plans Boolean is enabled.
MFP_PRE_EXP_RDX_W_JOB	To schedule any weekly plan exports to RAP integration before the calc cycle.	Weekly	Exports Plans to RI, if RDX is enabled.
MFP_PRE_EXP_OBS_W_JOB	To schedule any weekly plan exports to Object Storage before the calc cycle.	Weekly	Exports Standard Plans Weekly, if the Export Weekly Plans Boolean is enabled.
MFP_PRE_EXP_END_JOB	Dummy job to specify the end of pre-batch exports.	Daily
MFP_COM_HIER_IMP_START_ JOB	Dummy job to specify the start of a common hierarchies import.	Daily
MFP_COM_HIER_IMP_RDX_D_ JOB	To schedule any daily common hierarchy imports from RAP integration.	Daily
MFP_COM_HIER_IMP_OBS_D_ JOB	To schedule any daily common hierarchy imports from Object Storage.	Daily

July 15, 2026 Appendix E-1 of E-8

Appendix E

MFP Job Name	Description/Comments	Daily/Weekly	Template Configuration
MFP_COM_HIER_IMP_RDX_W _JOB	To schedule any weekly common hierarchy imports from RAP integration.	Weekly	Imports common hierarchies from RI, if RDX is enabled.
MFP_COM_HIER_IMP_OBS_W _JOB	To schedule any weekly common hierarchy imports from Object Storage.	Weekly	Loads common hierarchy files from Object Storage, if uploaded.
MFP_COM_HIER_IMP_END_JO B	Dummy Job, to specify the end of a common hierarchies import.	Daily
MFP_COM_DATA_IMP_START_ JOB	Dummy job to specify the start of common data imports.	Daily
MFP_COM_DATA_IMP_RDX_D_ JOB	To schedule any daily common data imports from RAP integration.	Daily
MFP_COM_DATA_IMP_OBS_D_ JOB	To schedule any daily common data imports from Object Storage.	Daily
MFP_COM_DATA_IMP_RDX_W _JOB	To schedule any weekly common data imports from RAP integration.	Weekly	Imports data files from RI, if RDX is enabled.
MFP_COM_DATA_IMP_OBS_W _JOB	To schedule any weekly common data imports from Object Storage.	Weekly	Loads data files from Object Storage, if uploaded.
MFP_COM_DATA_IMP_END_JO B	Dummy job to specify the end of common data imports.	Daily
MFP_HIER_IMP_START_JOB	Dummy job to specify the start of application-specific hierarchies import.	Daily
MFP_HIER_IMP_RDX_D_JOB	To schedule any daily application-specific hierarchy imports from RAP integration.	Daily
MFP_HIER_IMP_OBS_D_JOB	To schedule any daily application-specific hierarchy imports from Object Storage.	Daily
MFP_HIER_IMP_RDX_W_JOB	To schedule any weekly application-specific hierarchy imports from RAP integration.	Weekly	Imports application-specific hierarchies from RI, if RDX is enabled.
MFP_HIER_IMP_OBS_W_JOB	To schedule any weekly application-specify hierarchy imports from Object Storage.	Weekly	Imports any application-specific hierarchies from Object Storage.
MFP_HIER_IMP_END_JOB	Dummy job to specify the end of application-specific hierarchies import.	Daily
MFP_PRE_DATA_IMP_START_J OB	Dummy job to specify the start of application-specific data imports before the calc cycle.	Daily
MFP_PRE_DATA_IMP_RDX_D_ JOB	To schedule any daily application-specific data imports from RAP integration before the calc cycle.	Daily	Imports OO Data from RDX.

July 15, 2026 Appendix E-2 of E-8

Appendix E

MFP Job Name	Description/Comments	Daily/Weekly	Template Configuration
MFP_PRE_DATA_IMP_OBS_D_ JOB	To schedule any daily application-specific data imports from Object Storage before the calc cycle.	Daily	Imports OO Data from file if uploaded.
MFP_PRE_DATA_IMP_RDX_W_ JOB	To schedule any weekly application-specific data imports from RAP integration before the calc cycle.	Weekly
MFP_PRE_DATA_IMP_OBS_W_ JOB	To schedule any weekly application-specific data imports from Object Storage before the calc cycle	Weekly
MFP_PRE_DATA_IMP_END_JO B	Dummy Job to specify the end of application-specific data imports before the calc cycle	Daily
MFP_BATCH_AGG_START_JOB	Dummy job to specify the start of the Batch Aggregation Cycle.	Daily
MFP_BATCH_AGG_D_JOB	To schedule any daily batch aggregation jobs.	Daily	Runs Daily Batch Calcs or Aggregations.
MFP_BATCH_AGG_W_JOB	To schedule any weekly batch aggregation jobs.	Weekly	Runs Weekly Batch Calcs or Aggregations.
MFP_BATCH_AGG_END_JOB	Dummy job to specify the end of the Batch Aggregation Cycle.	Daily
MFP_EGRS_EXP_START_JOB	Dummy job to specify the start of Egress Export jobs.	Daily
MFP_EGRS_EXP_RDX_D_JOB	Daily export of hierarchy and actuals data to RDX for Egress.	Daily
MFP_EGRS_EXP_RDX_W_JOB	Weekly export of hierarchy and actuals data to RDX for Egress.	Weekly
MFP_EGRS_EXP_END_JOB	Dummy job to specify the end of Egress Export jobs.	Daily
MFP_POST_DATA_IMP_START _JOB	Dummy job to specify the start of application-specific data imports after the calc cycle.	Daily
MFP_POST_DATA_IMP_RDX_D _JOB	To schedule any daily application-specific data imports from RAP integration after the calc cycle.	Daily
MFP_POST_DATA_IMP_OBS_D _JOB	To schedule any daily application-specific data imports from Object Storage after the calc cycle.	Daily
MFP_POST_DATA_IMP_RDX_W _JOB	To schedule any weekly application-specific data imports from RAP integration after the calc cycle.	Weekly	Imports Forecasts from RI, if RDX is enabled.
MFP_POST_DATA_IMP_OBS_W _JOB	To schedule any weekly application-specific data imports from Object Storage after the calc cycle.	Weekly

July 15, 2026 Appendix E-3 of E-8

Appendix E

MFP Job Name	Description/Comments	Daily/Weekly	Template Configuration
MFP_POST_DATA_IMP_END_J OB	Dummy Job, to specify the end of application-specific data imports after the calc cycle.	Daily
MFP_POST_EXP_START_JOB	Dummy job to specify the start of post-batch exports.	Daily
MFP_POST_EXP_RDX_D_JOB	To schedule any daily data exports from RAP integration after the calc cycle.	Daily
MFP_POST_EXP_OBS_D_JOB	To schedule any daily data exports from Object Storage after the calc cycle.	Daily	Exports Plans to RI, if RDX is enabled.
MFP_POST_EXP_RDX_W_JOB	To schedule any weekly data export from RAP integration after the calc cycle.	Weekly
MFP_POST_EXP_OBS_W_JOB	To schedule any weekly data exports from Object Storage after the calc cycle.	Weekly
MFP_POST_EXP_END_JOB	Dummy job to specify the end of post-batch exports.	Daily
MFP_WB_BUILD_START_JOB	Dummy job to specify the start of workbook build/refresh jobs.	Daily
MFP_WB_BUILD_D_JOB	To schedule any workbook build/ refresh steps daily.	Daily	Runs daily scheduled workbook builds and refresh.
MFP_WB_BUILD_W_JOB	To schedule any workbook build/ refresh steps weekly.	Weekly	Runs weekly scheduled workbook builds and refresh.
MFP_WB_BUILD_END_JOB	Dummy job to specify the end of workbook build/refresh jobs.	Daily
MFP_ADHOC_XX_JOB	To schedule any adhoc jobs with the batch execution set name as a parameter. XX varies from 01 to 10. 10 Jobs available to schedule any adhoc steps with any set name as the parameter.	Adhoc

Even if the customer is using a non-template version of the application, they should have the following entries in their batch control file (batch_exec_list.txt) with the necessary hooks connected to the customer job steps in order to execute those steps using pre-defined MFP jobs from JOS/POM.

Generic Schedule Mapping in JOS/POM

MFP_PRE_EXP_RDX_D | exec | *hook_MFP_PRE_EXP_RDX_D

MFP_PRE_EXP_OBS_D | exec | *hook_MFP_PRE_EXP_OBS_D

MFP_PRE_EXP_RDX_W | exec | *hook_MFP_PRE_EXP_RDX_W

MFP_PRE_EXP_OBS_W | exec | *hook_MFP_PRE_EXP_OBS_W

MFP_COM_HIER_IMP_RDX_D | exec | *hook_MFP_COM_HIER_IMP_RDX_D MFP_COM_HIER_IMP_OBS_D | exec | *hook_MFP_COM_HIER_IMP_OBS_D MFP_COM_HIER_IMP_RDX_W | exec | *hook_MFP_COM_HIER_IMP_RDX_W

July 15, 2026 Appendix E-4 of E-8

Appendix E

MFP_COM_HIER_IMP_OBS_W | exec | *hook_MFP_COM_HIER_IMP_OBS_W MFP_COM_DATA_IMP_RDX_D | exec | *hook_MFP_COM_DATA_IMP_RDX_D MFP_COM_DATA_IMP_OBS_D | exec | *hook_MFP_COM_DATA_IMP_OBS_D MFP_COM_DATA_IMP_RDX_W | exec | *hook_MFP_COM_DATA_IMP_RDX_W MFP_COM_DATA_IMP_OBS_W | exec | *hook_MFP_COM_DATA_IMP_OBS_W MFP_HIER_IMP_RDX_D | exec | *hook_MFP_HIER_IMP_RDX_D MFP_HIER_IMP_OBS_D | exec | *hook_MFP_HIER_IMP_OBS_D MFP_HIER_IMP_RDX_W | exec | *hook_MFP_HIER_IMP_RDX_W MFP_HIER_IMP_OBS_W | exec | *hook_MFP_HIER_IMP_OBS_W MFP_PRE_DATA_IMP_RDX_D | exec | *hook_MFP_PRE_DATA_IMP_RDX_D MFP_PRE_DATA_IMP_OBS_D | exec | *hook_MFP_PRE_DATA_IMP_OBS_D MFP_PRE_DATA_IMP_RDX_W | exec | *hook_MFP_PRE_DATA_IMP_RDX_W MFP_PRE_DATA_IMP_OBS_W | exec | *hook_MFP_PRE_DATA_IMP_OBS_W MFP_BATCH_AGG_D | exec | *hook_MFP_BATCH_AGG_D MFP_BATCH_AGG_W | exec | *hook_MFP_BATCH_AGG_W MFP_EGRS_EXP_RDX_D_JOB | exec | *hook_MFP_EGRS_EXP_RDX_D MFP_EGRS_EXP_RDX_W_JOB | exec | *hook_MFP_EGRS_EXP_RDX_W MFP_POST_DATA_IMP_RDX_D | exec | *hook_MFP_POST_DATA_IMP_RDX_D MFP_POST_DATA_IMP_OBS_D | exec | *hook_MFP_POST_DATA_IMP_OBS_D MFP_POST_DATA_IMP_RDX_W | exec | *hook_MFP_POST_DATA_IMP_RDX_W MFP_POST_DATA_IMP_OBS_W | exec | *hook_MFP_POST_DATA_IMP_OBS_W MFP_POST_EXP_RDX_D | exec | *hook_MFP_POST_EXP_RDX_D MFP_POST_EXP_OBS_D | exec | *hook_MFP_POST_EXP_OBS_D MFP_POST_EXP_RDX_W | exec | *hook_MFP_POST_EXP_RDX_W MFP_POST_EXP_OBS_W | exec | *hook_MFP_POST_EXP_OBS_W MFP_WB_BUILD_D | exec | *hook_MFP_WB_BUILD_D MFP_WB_BUILD_W | exec | *hook_MFP_WB_BUILD_W

Note

MFP_EGRS_EXP_* jobs are placeholder jobs needed only for Egress customers migrated to a new release to export their hierarchy and actuals data to RDX so that AI Foundation can use the data to generate forecasts. Those jobs will execute batch steps in GA only when the Egress Export Hierarchies and Egress Export Actuals Boolean flags are enabled using the Measure Analysis template. New customers in RAP can ignore these jobs if they are getting standard hierarchies and actuals from RAP.

July 15, 2026 Appendix E-5 of E-8

Appendix E

Note

In a Multi-App set up, only one application should import the common shared hierarchies using the *COM_HIER_IMP * jobs. In GA apps, it is controlled by the shared Boolean measure Primary to Load Common Data. If MFPCS is not the first planning application deployed in RAP and if another planning application such as APCS or IPOCS-Demand Forecasting is already deployed, then set Primary to Load Common Data to true in only one of the application under the Planning Administration → Batch Setup in show/hide, to avoid trying to load the common data again for shared planning applications through the JOS/POM schedule. If not set by the user in GA apps, that Boolean will be set to true only for the first deployed GA application for which the initial post build batch is run.

Note

Adhoc jobs are available with the SET_NAME (AdhocXX) and RESTART_STEP (restartStep) parameters so that those jobs can be ordered in and used to restart any failed job by using the failed jobs set_name from the batch_exec_list.txt control file and step number to restart as parameters. restartStep is a common parameter so it should be set for each adhoc job run. Adhoc jobs are also set up with the parameter SINGLEDAILYRUN=FALSE and that allows them to re-run multiple times for the same scheduled day.

Note

When using POM for executing batches for a planning application, the value of RPAS_TODAY should be unset within OAT. It will then automatically use the current business date as defined in the POM UI, plus or minus an offset value if you need the application to run for a different date than the POM UI displays. This process is explained in more detail in the Oracle Retail Predictive Application Server Cloud Edition Administration Guide chapter on RPASCE Batch Schedule with POM.

External Dependencies

In RAP Integration, MFP gets data from RI and AIF. Those dependencies are pre-defined in the schedule. In the following table are the pre-defined dependencies of MFP jobs. The customer needs to enable those dependencies based on the modules enabled on the RI and AIF side, so that the dependent job on the MFP side wait for the completion of that interface on the source side.

JobName	ExternalScheduleName	ExternalPredecessorJobName
RPASCE_HIER_IMP_START_JOB	RI	RDX_EXPORT_DIM_MILE_MARKE R_JOB
RPASCE_DATA_IMP_START_JOB	RI	RDX_EXPORT_FACT_MILE_MARK ER_JOB
MFP_POST_DATA_IMP_START_JO B	RSP	RSE_MFP_FCST_EXPORT_JOB

Schedule and Mapping in JOS/POM for Multi-Instance

July 15, 2026 Appendix E-6 of E-8

Appendix E

Customers can provision second or multiple instances of MFPCS. But second or multi-instance can only be deployed as a Custom (non-template) configuration and when it is provisioned, a new schedule will also be provided for multi-instance with <APP_INSTANCE_CODE> (example: mfpscs2 or mfpscs3) as RPASCE-<APP_INSTANCE_CODE>. Multi-instance uses the standard schedule, and the customer can customize it for the steps that it needs to execute using the corresponding entries in their custom batch control files.

The customer should have the following entries in their batch control file (batch_exec_list.txt) with the necessary hooks connected to the customer job steps in order to execute those steps using pre-defined jobs from JOS/POM. Replace with corresponding instance <APP_INSTANCE_CODE> code value during deploy.

Schedule also as _ADHOC_XX_JOB for the adhoc schedule purpose.

Batch Control in JOS/POM for Multi-Instance

_PRE_EXP_RDX_D | exec | *hook_PRE_EXP_RDX_D _PRE_EXP_OBS_D | exec | *hook_PRE_EXP_OBS_D _PRE_EXP_RDX_W | exec | *hook_PRE_EXP_RDX_W _PRE_EXP_OBS_W | exec | *hook_PRE_EXP_OBS_W _HIER_IMP_RDX_D | exec | *hook_HIER_IMP_RDX_D _HIER_IMP_OBS_D | exec | *hook_HIER_IMP_OBS_D _HIER_IMP_RDX_W | exec | *hook_HIER_IMP_RDX_W _HIER_IMP_OBS_W | exec | *hook_HIER_IMP_OBS_W _PRE_DATA_IMP_RDX_D | exec | *hook_PRE_DATA_IMP_RDX_D _PRE_DATA_IMP_OBS_D | exec | *hook_PRE_DATA_IMP_OBS_D _PRE_DATA_IMP_RDX_W | exec | *hook_PRE_DATA_IMP_RDX_W _PRE_DATA_IMP_OBS_W | exec | *hook_PRE_DATA_IMP_OBS_W _BATCH_AGG_D | exec | *hook_BATCH_AGG_D _BATCH_AGG_W | exec | *hook_BATCH_AGG_W _POST_DATA_IMP_RDX_D | exec | *hook_POST_DATA_IMP_RDX_D _POST_DATA_IMP_OBS_D | exec | *hook_POST_DATA_IMP_OBS_D _POST_DATA_IMP_RDX_W | exec | *hook_POST_DATA_IMP_RDX_W _POST_DATA_IMP_OBS_W | exec | *hook_POST_DATA_IMP_OBS_W _POST_EXP_RDX_D | exec | *hook_POST_EXP_RDX_D _POST_EXP_OBS_D | exec | *hook_POST_EXP_OBS_D _POST_EXP_RDX_W | exec | *hook_POST_EXP_RDX_W _POST_EXP_OBS_W | exec | *hook_POST_EXP_OBS_W _WB_BUILD_D | exec | *hook_WB_BUILD_D _WB_BUILD_W | exec | *hook_WB_BUILD_W

July 15, 2026 Appendix E-7 of E-8

Appendix E

The following Interschedule Dependencies are pre-defined with the RI, AIF, and RPASCE schedules for the Hierarchy and Data Imports. If any external export dependency is needed in RI/AIF for any exports from multi-instance, that needs to be added directly in the POM UI. For information about how to add Inter-Schedule Dependencies with other applications, see the Oracle Retail Process Orchestration and Monitoring User Guide and Oracle Retail Process Orchestration and Monitoring Implementation Guide .

JobName	ExternalScheduleName	ExternalPredecessorJobName
_HIER_IMP_START_JOB	RI	RDX_EXPORT_DIM_MILE_MARKE R_JOB
_PRE_DATA_IMP_START_J OB	RI	RDX_EXPORT_FACT_MILE_MARK ER_JOB
_POST_DATA_IMP_START_J OB	RSP	RSE_AP_FCST_EXPORT_JOB
_HIER_IMP_START_JOB	RPASCE	RPASCE_HIER_IMP_END_JOB
_PRE_DATA_IMP_START_J OB	RPASCE	RPASCE_DATA_IMP_END_JOB

July 15, 2026 Appendix E-8 of E-8

---

In this guide

• Guide: Merchandise Financial Planning Cloud Service Implementation Guide
• Previous: D Appendix: MFPCS Specific Custom Functions, Procedures, and Special Expressions

Related chapters

• POM — Assortment Planning Cloud Service Implementation Guide · shares APP_INSTANCE_CODE, COM_HIER_IMP, ER_JOB, RDX_EXPORT_DIM_MILE_MARKE