| Oracle® Retail Assortment & Item Planning for Fashion/Softlines Cloud Service Implementation Guide Release 19.0 F24867-12 |
|
 Previous |
| Oracle® Retail Assortment & Item Planning for Fashion/Softlines Cloud Service Implementation Guide Release 19.0 F24867-12 |
|
Previous |
RPAS CE Batch schedule in JOS/POM provides a default job schedule for all applications within RPAS with more placeholder jobs for each application, so that both EE and GA customer can use the same schedule with minimal changes. The customer needs to disable/enable the jobs needed for the applications that they are using. This appendix provides information about the list of jobs for A&IP FSL. The customer can easily customize their batch process by controlling the batch control files without changing the batch schedule. Each batch job in A&IP FSL is connected to hooks in the batch control files that can be changed by customers. The A&IP FSL job flow contains both daily and weekly jobs. Jobs scheduled to run weekly are scheduled to run only on Saturday by default and daily jobs are scheduled to run on days other than Saturday.
The following table shows the list of jobs that run in order in the A&IP FSL Schedule in JOS/POM. Only jobs used in the GA configuration entries are pre-configured and the task or step it runs in the batch is specified as GA Task/Step Mapping. The rest of the jobs are simply placeholder jobs to allow changes to the schedule of the jobs to run additional steps by changing the batch control file. Each A&IP job calls the same set names in the batch control file without _JOB in the name as batch set name (except
jos_jobs which are kept as in previous releases for backward compatibility). This allows it to call the respective *hook_<set_name> steps, so even if it is not linked to a batch set, the job will run without failure. The batch can be controlled without changing the job flow just by changing the corresponding hooks in batch control files.
In addition to the standard jobs, the A&IP job flow also provides additional adhoc jobs with the names APF_ADHOC_XX_JOB (where XX ranges from 00 to 10) with their own system option parameters (apfAdhocXX) to call their preferred set names from their batch control files, which can be used to schedule independently. Those adhoc jobs can also be triggered from external systems using web service calls.
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 JOS/POM User Guide.
| Job Name | Job Description | Frequency | Batch Set Name | GA Task/Step Mapping |
|---|---|---|---|---|
| APIPFSL_DAILY_PRE_JOB | APIPFSL Daily Pre-Job | Daily | jos_daily_pre | |
| APIPFSL_DAILY_JOB | APIPFSL Daily Job | Daily | jos_daily | |
| APF_PRE_AGG_D_JOB | APIPFSL Pre Agg Daily Job | Daily | APF_PRE_AGG_D | calc_batch |
| APF_PRE_EXP_D_JOB | APIPFSL Pre Exports Daily Job | Daily | APF_PRE_EXP_D | exp_plan |
| APF_PRE_IMP_D_JOB | APIPFSL Pre Imports Daily Job | Daily | APF_PRE_IMP_D | |
| APF_BATCH_AGG_D_JOB | APIPFSL Batch Aggregation Daily Job | Daily | APF_BATCH_AGG_D | calc_daily |
| APF_POST_IMP_D_JOB | APIPFSL Post Imports Daily Job | Daily | APF_POST_IMP_D | |
| APF_POST_EXP_D_JOB | APIPFSL Post Exports Daily Job | Daily | APF_POST_EXP_D | |
| APF_POST_AGG_D_JOB | APIPFSL Post Aggregation Daily Job | Daily | APF_POST_AGG_D | |
| APF_WB_BUILD_D_JOB | APIPFSL Workbook Build/Refresh Daily Job | Daily | APF_WB_BUILD_D | rebuild_db |
| APIPFSL_DAILY_POST_JOB | APIPFSL Daily Post-Job | Daily | jos_daily_post | |
| APIPFSL_WEEKLY_PRE_JOB | APIPFSL Weekly Pre-Job | Weekly | jos_weekly_pre | |
| APIPFSL_WEEKLY_JOB | APIPFSL Weekly Job | Weekly | jos_weekly | |
| APF_PRE_AGG_W_JOB | APIPFSL Pre Agg Weekly Job | Weekly | APF_PRE_AGG_W | calc_batch |
| APF_PRE_EXP_W_JOB | APIPFSL Pre Exports Weekly Job | Weekly | APF_PRE_EXP_W | exp_plan |
| APF_PRE_IMP_W_JOB | APIPFSL Pre Imports Weekly Job | Weekly | APF_PRE_IMP_W | batch_rms/batch_non_rms, load_adm |
| APF_BATCH_AGG_W_JOB | APIPFSL Batch Aggregation Weekly Job | Weekly | APF_BATCH_AGG_W | ap_set_datr, calc_weekly |
| APF_POST_IMP_W_JOB | APIPFSL Post Imports Weekly Job | Weekly | APF_POST_IMP_W | batch_mfp, batch_fcst, batch_rse |
| APF_POST_EXP_W_JOB | APIPFSL Post Exports Weekly Job | Weekly | APF_POST_EXP_W | |
| APF_POST_AGG_W_JOB | APIPFSL Post Aggregation Weekly Job | Weekly | APF_POST_AGG_W | |
| APF_WB_BUILD_W_JOB | APIPFSL Workbook Build/Refresh Weekly Job | Weekly | APF_WB_BUILD_W | refresh_apfa, refresh_ipcs, rebuild_db |
| APIPFSL_WEEKLY_POST_JOB | APIPFSL Weekly Post-Job | Weekly | jos_weekly_post |
Enterprise Edition customers can use the same frame work as GA shown below in their batch control file and only use the *hook entries to connect to execute the required steps without changing the job flow in JOS/POM.
jos_daily_pre | exec | *hook_jos_daily_pre
jos_daily | exec | *hook_jos_daily
APF_PRE_AGG_D | exec | *hook_APF_PRE_AGG_D
APF_PRE_EXP_D | exec | *hook_APF_PRE_EXP_D
APF_PRE_IMP_D | exec | *hook_APF_PRE_IMP_D
APF_BATCH_AGG_D | exec | *hook_APF_BATCH_AGG_D
APF_POST_IMP_D | exec | *hook_APF_POST_IMP_D
APF_POST_EXP_D | exec | *hook_APF_POST_EXP_D
APF_POST_AGG_D | exec | *hook_APF_POST_AGG_D
APF_WB_BUILD_D | exec | *hook_APF_WB_BUILD_D
jos_daily_post | exec | *hook_jos_daily_post
jos_weekly_pre | exec | *hook_jos_weekly_pre
jos_weekly | exec | *hook_jos_weekly
APF_PRE_AGG_W | exec | *hook_APF_PRE_AGG_W
APF_PRE_EXP_W | exec | *hook_APF_PRE_EXP_W
APF_PRE_IMP_W | exec | *hook_APF_PRE_IMP_W
APF_BATCH_AGG_W | exec | *hook_APF_BATCH_AGG_W
APF_POST_IMP_W | exec | *hook_APF_POST_IMP_W
APF_POST_EXP_W | exec | *hook_APF_POST_EXP_W
APF_POST_AGG_W | exec | *hook_APF_POST_AGG_W
APF_WB_BUILD_W | exec | *hook_APF_WB_BUILD_W
jos_weekly_post | exec | *hook_jos_weekly_post
