Oracle Retail Knowledge Base

A Batch Schedule Spreadsheet Template

23 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.

A

Batch Schedule Spreadsheet Template

Overview

This appendix explains how to set up the Batch Schedule Spreadsheet template. The template was originally developed for internal Oracle use and has since been made available to System Integrators and Customers for customizing Retail Application provided Batch Schedules or for developing custom Schedules. For the latter use, custom Batch Schedules may be less complex and may not require some tabs and fields.

Structure

The purpose of this template is to design the batch metadata that can be seeded into a Batch Schedule within POM. A Batch Schedule, at minimum, must define a Nightly Flow, consisting of a start and end Job. The Recurring and Adhoc Cycles are optional and need not contain any Processes or Jobs in them.

The spreadsheet template has a default nightly flow pre-populated with start and end Nightly jobs. These jobs are seeded with DUMMY job type so that they will be skipped during execution.

Tabs

The following tabs are available on the Spreadsheet Template.

Tab NamePurpose
ScheduleDefnes the name, display schedule name and version of the
Batch Schedule.
FlowDefnes all the Flows in POM. Since the Nightly Flow is already
in-built within POM, this refers to the Flows on the Adhoc and
Hourly Cycles.
ProcessDefnes all the Processes in POM, across all Batch Cycles.
JobDefnes all the Jobs in POM, across all Batch Cycles.
FlowProcessMappingCreates mappings between Flows and Processes.
ProcessJobMappingCreates mappings between Processes and Jobs and maintains
the sequence order of jobs within a process and also the
parameter value.
DependencyCreates internal dependencies between Processes.
ApplicationDefnes the Applications to which the Jobs belong. It also defnes
a mapping between an Application and the name of the Job
Agent that must run those Jobs.
ModulesDefnes Modules within Applications. These are mainly used to
synchronize with the Modules defned for the Application in
Retail Home. See Sync with MDF in the_POM User Guide_for
further details.

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-1 of A-22

Appendix A Structure

Tab NamePurpose
SystemOptionLists all the system options available to the Jobs at execution
time.
ThrottlingConfigurationDefnes the throttle settings at an Application level.
InterscheduleDependencyDefnes dependencies with a different Batch Schedule on the
same POM instance
ExternalDependenciesDefnes External Dependencies usually on a customer’s internal
process
BatchLinksAlso known as Schedule Links. If the Nightly Flow is going to be
invoked via a different Job on a different Schedule, then a
Schedule Link can be defned.
JobTypesCustom ReST based types of Jobs that need to be run
Schedule ErrorsEmpty tab that is populated with the list of errors, either by the
macro or when being transformed by the Batch Schedule
Transformer.
Macro Validation

This Excel Template is equipped with a macro that can be run to validate the entries on the spreadsheet. Upon encountering failures, the macro publishes the error entries in the Schedule Errors tab.

Schedule Validation Processes

Applications can set up processes and jobs for use by the provisioning process to validate the setup. After POM has been provisioned/patched, the provisioning tool will attempt to run the validation job(s) to ensure that POM is functional end to end. Following are the steps to setup these processes/jobs:

1. In the Process tab, add new processes that end with _POM_VPROCESS . Examples: RMS_SALES_POM_VPROCESS , REIM_EJB_POM_VPROCESS

2. In the Process tab, set the value in the AdhocInd field to Y because validation processes can only be part of the adhoc cycle.

3. In the ProcessJobMapping tab, make sure the newly created validation processes are mapped to any valid job that shouldn’t run for more than 5 minutes. Validation jobs should obviously be benign in that they should not alter data.

4. If there is more than one job in a validation process, make sure the pre and post dependencies are correctly defined in the Dependency tab.

Schedule Upgrade Directives

These are directives solely to the Batch Schedule upgrade process, altering values as specified, when the default settings are not acceptable. For instance, all newly added Jobs are marked DISABLED by default. To enable a Job, the AMS team or the Customer is asked to do so through the POM UI. This is not ideal as it involves manual intervention. To overcome this, we use the “enableOnNew” directive on the Job tab, to ensure that the Job is marked ENABLED when its added for the first time.

The processing of these directives is designed as a stage in the Schedule Import process. The following directives are currently supported in POM.

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-2 of A-22

Appendix A Structure

Template TabDirective NameDescription
JoboverrideParameterOnUpgra
de		This directive provides a
controlled, version-based
mechanism for Oracle to reset
specifc job parameters during
an upgrade after a retail has
overridden the parameters
from the UI. For example:
overrideParameterOnUpgrade=
v:26.1.201.13.
If this directive is present, the
job parameters specifed for a
particular job will become the
active parameters even if the
customer overrode those from
the UI. This will only happen if
the version being upgraded to is
equal or less than the version
specifed.
If left blank, the parameter will
only be updated when it has not
been modifed from the POM
UI.”
ProcessJobMappingoverrideParameterOnUpgra
de		modifed from the POM UI.”
This is the same directive as
mentioned in the Job tab
previously. The difference here
is that in the Process Job
Mapping tab, this directive will
only change the parameters for
the specifed Process and Job
combination, while on the Job
tab, it would change the
parameters for all instances of
the Job across processes.
ProcessJobMappingenableOnNewOnly when being loaded for the
very frst time, the Job will be
enabled. When this directive is
not used, the job will be
disabled by default when added
for the frst time.
ProcessJobMappingenableLikeJobOnNewOnly when being loaded for the
very frst time, the status of the
Job (for which the directive is
specifed) will match that of the
“LikeJob”.
ProcessJobMappingenableLikePJOnNewOnly when being loaded for the
very frst time, the status of the
Job (for which the directive is
specifed) will match that of the
“LikeProcessJob” defned.
Batch LinksenableLinkOnNew
Only when being loaded for the
very frst time, the status of the
Batch Link will be enabled.
When this is not used, batch
link will be disabled by default
when added for the frst time.

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-3 of A-22

Appendix A Tab Definitions

Template TabDirective NameDescription
Batch LinksenableLikeLinkOnNewOnly when being loaded for the
very frst time, the status of the
Batch Link (for which the
directive is specifed) will match
that of the “LikeLink”

If any Process-Job combination has multiple directives that are semicolon delimited, they get executed in the following order:

1. enableOnNew

2. enableLikePJOnNew

3. enableLikeJobOnNew

4. enableLinkOnNew

5. enableLikeLinkOnNew

6. overrideParameterOnUpgrade

Tab Definitions

Process Tab

This tab allows you to define all processes for the schedule at hand. A process is a group of jobs that are to be run sequentially from start to end. The following is a description of all fields on this tab:

  • ProcessName

    • Uniquely identifies a process. The Process Name should be in upper case only with no spaces. Use an underscore if needed. It should end with XXX_PROCESS . Validation processes should end with _POM_VPROCESS .

See Schedule Validation Processes above for an explanation of the validation processes.

  • The process name is the batch job name appended with _PROCESS .

For example: DEALUPLD_PROCESS

SA_TRANSACTION_LOADING_PROCESS
  • For non-Merchandising processes, the process name should start with the Application name.

For example: REIM_POSTING_PROCESS, ALC_DAILY_CLEANUP_ PROCESS

  • If a process is part of the nightly batch cycle but is also an ad hoc job, or if it’s also part of a recurring flow, three separate processes should be defined. The ad hoc process should end with XXX_PROCESS_ADHOC and the recurring process should end with XXX_CYCLE_PROCESS .

For example:

  • SA_TRANSACTION_LOADING_PROCESS – for the sales audit transaction loading jobs that will run in the nightly batch cycle.

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-4 of A-22

Appendix A Tab Definitions

  • SA_TRANSACTION_LOADING_PROCESS_ADHOC – for the sales audit transaction loading jobs that will run ad hoc.

  • SA_TRANSACTION_LOADING_CYCLE_PROCESS – for the sales audit transaction loading jobs that will run multiple times a day.

Description

  • Short description of the process. There should be no special characters. If the process contains just one job, the description can be the same as the batch job name.

DependencyType

  • Valid values are TIME , JOB and BOTH .

  • If the first job in this process is triggered on completion of another job, mark as JOB .

  • If the process is scheduled to run at a specific time (for example, the first job of the nightly batch cycle, or part of a recurring flow process), mark as TIME .

  • If the process needs to run at a specific time and at the same time is dependent on another process, mark as BOTH .

  • If the process is ad hoc and is not part of the nightly batch cycle, leave as NULL .

ApplicationName

  • This holds the application name which the batch process belongs to.

  • Valid values are RMS , RPM , REIM , RESA , ALLOC , RDE , MFP , AIPFSL , RDF , and so on.

AdhocInd

  • Valid values are Y and N .

  • If the job(s) in the process are ad hoc jobs (can be run any time and not part of the nightly batch cycle), mark as Y . Otherwise, mark as N .

  • A process should not have a mix of ad hoc and scheduled jobs in it.

Job Tab

The Job tab contains all the individual jobs to be executed as part of the schedule at hand.

  • JobName

    • Uniquely identifies a job. The Job Name should be in upper case only with no spaces. Use an underscore if needed. It should end with XXX_JOB . If the same job is part of multiple processes, define separate jobs for it.

Examples:

  • EXPORT_DIFFS_JOB (under EXPORT_DIFFS_PROCESS ) – for the export_diffs.ksh program passing in ‘delta’ as a parameter

  • EXPORT_DIFFS_FULL_JOB (under EXPORT_DIFFS_FULL_PROCESS ) – for the same export_diffs.ksh program but this time passing in ‘full’

  • For non-Merchandising jobs, the job name should start with the Application, (for example, REIM_POSTING_JOB , ALC_DAILY_CLEANUP_JOB , RDE_SEASNSDE_JOB )

  • If the job is part of the nightly batch cycle and is also part of a recurring flow, define two separate jobs for it.

Examples:

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-5 of A-22

Appendix A Tab Definitions

  • UPLOADSALES_JOB belonging to SALESPROCESS_PROCESS – for the uploadsales.ksh program run as part of the nightly batch cycle

  • UPLOADSALES_CYCLE_JOB belonging to SALESPROCESS_CYCLE_PROCESS – for the same uploadsales.ksh program run as part of a recurring flow

Description

  • Short description of the batch program. There should be no special characters.

RmsBatch

  • This holds the exact batch executable that the job refers to. For Pro*C programs, this should be the binary without the .pc extension. For KSH scripts, include the .ksh extension. This field is case-sensitive.

  • For service type jobs (non-shell script REST_EXEC type jobs), this field should be left blank.

RmsWrapper
  • If applicable, this holds the exact batch wrapper name used to call the batch program. This field is case-sensitive.

– For service type jobs (non shell script REST_EXEC type jobs), this field should be left blank.

ScriptFolder

This holds the directory path where the Wrapper file resides in the system.

  • For service type jobs (non-shell script REST_EXEC type jobs), this field should be left blank.

ParameterValue
  • This field is also present on the ProcessJobMapping tab. So it can be populated either on this Job tab or on the ProcessJobMapping tab. This depends on whether the same or different parameter values apply at the Job level versus the ProcessJob level.

– This holds the entire parameter value to be passed in to a shell script type job. This field is case sensitive.

  • For parameters that can have multiple values (for example, purge days parameter), provide a default value so that the batch can still be executed.

  • Placeholder parameter #JobCtxt.businessDate can be defined on the Job sheet for jobs that require a POM business date parameter ( DDMMYYYY format).

  • Parameters are updated in the BASE_PARAMETER column of the BATCH_PROCESS_JOB_LIST table. On a schedule upgrade, the ACTIVE_PARAMETER column value is updated with the BASE_PARAMETER only if the parameter value has never been changed from the UI.

ApplicationName

  • This holds the application that the batch program belongs to.

It should be a valid application mentioned in the Application tab.

Module

  • This holds the name of the module under the application which the batch program belongs to. The Application / Module entered here should be a valid combination in the Application tab.

  • If there are no modules defined for the corresponding application in the Application tab or the Modules tab, then this column can be left blank. Otherwise it is required to enter the module(s) it belongs to.

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-6 of A-22

Appendix A Tab Definitions

  • A job can belong to multiple modules under the same application. In this case the list of those modules should be entered here with || as a delimiter.

For example:

MODULE1||MODULE2||MODULE3

– If the corresponding Application have some modules defined in Application Sheet then this column cannot be left blank.

FixedParameterInd – VARCHAR(1)

  • Valid values are Y and N .

  • This indicates whether the parameter value can be changed on the Batch Administration screen. If this is Y , the parameter will be changeable on the UI. This is applicable if the parameter cannot have a default value, or if the parameter can have different values.

If this is N , the parameter value is fixed and will not be changeable on the UI.

ParameterUpdated – VARCHAR(1)
  - This field is deprecated and is no longer in use.

-

  • Valid values are Y and N .

  • This indicates whether the parameter value column has changed from the previous value.

  • If Y , then the parameter value is passed and updates the existing job information with the newly passed parameter value. If N the parameter value won’t be updated for the existing job information.

SkipOnError – VARCHAR(1)
  • Valid values are Y and N .

– A value of Y indicates that the job should be skipped if an error occurs and the batch schedule continues to run. Otherwise the batch schedule is stopped.

JobType – VARCHAR (50)

– The default value set is REST_EXEC , which represents shell-script based Jobs. Other pre-defined service based job types are RI , RASE , BDI , RPAS , OMS , OB , RDS , and DUMMY .

  • Custom Job types defined in the JobType tab can also be used in this field. In this case POM is directed to execute the job using the endpoint defined on the JobType tab.

KillCleanupScript – VARCHAR (1000)

  • Absolute path of the cleanup script to be run after killing a shell script ( REST_EXEC ) type job from the POM UI. Example: /u01/retail/rms/batch/outgoing/ app_cleanup_script.sh

  • Can include arguments as well along with the script.

The post-kill cleanup script is executed automatically by POM after a Kill is performed from the UI. It does not perform the kill itself. It is defined by the application teams such as Merch. Here’s how it works: The user performs a Kill on a running job from the POM Batch Monitoring screen. If a KillCleanupScript is defined for that job on the Job worksheet of the batch schedule spreadsheet, POM will execute it after killing the job on the server. Application teams usually include database clean-up as part of the clean-up script.

For example:

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-7 of A-22

Appendix A Tab Definitions

Dependency Tab

The Dependency tab allows you to define the dependencies between processes.

  • ProcessName – VARCHAR(50)

    • This should match the ProcessName in the ProcessJobMapping tab.

  • PredecessorProcessName – VARCHAR(50)

    • This holds the process name that should run before the current job. This can be the same process (if there are multiple jobs in the process) or a different process than the current one.
Example
ProcessNamePredecessorProcessName
SAPURGE_PROCESSSAEXPRMS_PROCESS
SAPURGE_PROCESS_STARTSAPURGE_PROCESS
SAPURGE_PROCESS_ENDSAPURGE_PROCESS_START
Note

Dependencies between adhoc processes of named adhoc flow / invokable flow can also be defined in this tab.

If an invokable flow only contains one adhoc process, there’s no need to fill up the Dependency tab for such flow.

If an invokable flow has more than one adhoc process, the dependencies of processes 2, 3, and so on need to be defined. There is no need to define the dependency of the first process, because this will not be dependent on another process.

Example

The invokable / named adhoc flow FCUSTOMERUPLOAD_ADHOCFLOW has 2 processes:

  • FCUSTOMERUPLOAD_PROCESS_ADHOC

  • FCUSTOMERPURGE_PROCESS_ADHOC

Only the dependency of the second process ( FCUSTOMERPURGE_PROCESS_ADHOC ) needs to be defined:

ProcessNamePredecessorProcessName
FCUSTOMERPURGE_PROCESS_ADHOCFCUSTOMERUPLOAD_PROCESS_ADHOC

Flow Tab

The Flow tab allows you to define jobs that runs Adhoc flows and hourly or multiple times a day.

  • RecurringFlowName – VARCHAR(50)

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-10 of A-22

Appendix A Tab Definitions

  • Valid values are Y and N .

  • If the process holds the last job of the recurring/ adhoc flow, mark as Y . Otherwise, mark as N .

Example

The SALESPROCESS_CYCLE recurring flow has only 1 process, so the first and last jobs of the recurring flow is in the same process.

The REPLENISHMENT_CYCLE recurring flow has multiple processes. The first job of the recurring flow is in the first process, and the last job is in the last process.

RecurringFlowNameProcessNameFirstProcessIn
d		LastProcessInd
SALESPROCESS_CYCLESALESPROCESS_CYCLE_PROCESSYY
REPLENISHMENT_CYCL
E		REPLENISHMENT_CYCLE_PROCESSYN
REPLENISHMENT_CYCL
E		SUPSPLIT_CNTRPRSS_CYCLE_PROCE
SS		NN
REPLENISHMENT_CYCL
E		INVESTMENT_BUY_CYCLE_PROCESSNN
REPLENISHMENT_CYCL
E		RPLBLD_CYCLE_PROCESSNN
REPLENISHMENT_CYCL
E		REPLENISHMENT_END_CYCLE_PROC
ESS		NY
AdhocFlowTest1APIPGHL_ADHOC_PROCESSYY
AdhocFlowTest2RDF_ADHOC_PROCESSYY

SystemOption Tab

The SystemOption tab contains the system level options used to control certain aspects of the POM application, such as whether to enable throttling. It can also be used to define shell script error or warning exit codes. If any such codes are specified, they will cause a shell script based job to fail or complete with warning.

  • Name – VARCHAR(255)

    • Holds the name of the System Option value needed in JOS; for example, enableThrottling , WarningCode110 , ErrorCode40 , RIRestartableErrorMessages , TARGET_BATCH_DURATION .

A value of WarningCode110 , for example, causes POM to mark the job status as completed with a warning if the job’s shell script exits with a code of 100. A value of ErrorCode40 , for example, causes POM to mark the job status as error if the job’s shell script exits with a code of 40.

For a value of <<JOB_TYPE>>RestartableErrorMessages , the description field holds a list of comma-separated error messages that determine the auto-restart capability of the jobs. If the response contains one of those error messages, POM will retry the job for a maximum of 3 attempts.

For example, to add this capability to the RI Job Type when encountering either of the messages “context not found” or “500 internal error”.

  • Type – VARCHAR

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-12 of A-22

Appendix A Tab Definitions

Example
  • Application with modules defined.
NameDescriptionModulesJosJobAdminNam
e
COMMONAll apps required
programs		COMMONMAINTAIN
ORASERCIORASE and RCI
required		ORASERCICUSTOMER
programsTRADEAREA
RCIRCI required
programs		RCICUSTOMER
RSPRSP required
programs		AC

  • Applications without any modules defined.

NameDescription ModulesJosJobAdminName
RMSRMSRMS
ALLOCALLOCRMS
RDERDERDE
REIMREIMRMS
RESARESARMS
RPMRPMRMS

Schedule Tab

The Schedule tab contains the name of the schedule along with version and description. Increasing the version is necessary to upload a spreadsheet with any changes to POM.

  • ScheduleName – VARCHAR(10)

    • Holds the name of the Schedule (for example, MERCH , RDE , or RI ).

  • Description – VARCHAR(100)

    • Description of the Schedule.

  • Version – VARCHAR(50)

    • Version of the Schedule.

  • DisplayScheduleName – VARCHAR(1000)

    • Holds the display name of the Schedule (for example, MERCH , RDE , or RI ).

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-14 of A-22

Appendix A Tab Definitions

  • Module – VARCHAR(50)

    • Holds the module name in the case where we need to set a throttle value at module level.

    • It is possible to just set throttling at the application level. Modules would then inherit the application’s throttle value. In this case, leave module blank.

    • This Application / Module combination must be valid per the Application tab.

  • ThrottledValue – NUMBER

    • Holds the throttle value for this Application / Module.

    • This can’t be blank and should be a non-zero positive number.

Example
  • For an Application without any modules defined.
ApplicationModuleThrottledValue
RMS2
ALLOC5
REIM3
RDE2
  • For an Application with modules defined, define throttle values at either application or module level or both.
ApplicationModuleThrottledValue
COMMON3
COMMONCOMMONMAINTAIN1
ORASE2

If you don’t want any jobs to be throttled at Application / Module level, then leave this tab empty.

InterScheduleDependency Tab

The InterScheduleDependency tab allows you to define dependencies from jobs on this schedule to jobs on other schedules on the same instance of POM. For example, job A of this schedule can be made dependent on job B from another schedule. Job A will then wait for completion of job B.

ProcessName – VARCHAR(50)

  • Holds the name of the process from the current schedule that is dependent on a different schedule.

  • This process name should be listed in the Process tab.

  • JobName – VARCHAR(50)

    • Holds the name of the corresponding job within the above process that has the dependency on another external schedule.

    • This Process Job combination should be valid per the Process Job Mapping tab.

  • ExternalScheduleName – VARCHAR(10)

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-16 of A-22

ProcessName JobName ExternalScheduleName ExternalPredecessorProcessName ExternalPredecessorlobName ALLOCBT_PROCESS ALLOCBT_JOB RDE RDE_SETUP_PROCESS RDE_REFRESHODIVARIABLESJOBJOB DISTROPCPUB_PROCESS DISTROPCPUB_JOB RDE RDE_SUPSDE_PRDITMSUPSDE_PROCESS RDE_SUPSDE_JOB CMPUPLD_PROCESS CMPUPLD_JOB RPAS RPAS PROCESS PROCESS RPAS JOB ALC_PURGE_WRK PROCESS ALCPURGE_WRK_JOBPURGE_WRK_JOB RIORASE RIORASE_PROCESS RIORASE JOB

ProcessiMame * Jobiame * |temaifredecessoriobaame |~ FILE VALIDATION PROCESS ORBATCHVERIFY RICOMMON JOB EXT JOB 1 FILE VALIDATION PROCESS ORBATCH_VERIFY_RMI_JOB EXT JOB 2 FILE VALIDATION PROCESS ORBATCH VERIFY_RCI_IOB EXT OB 3

AB
iq		DE
1
ProcessName		JobName
InvokerScheduleName		InvokerProcessNameInvokerJobName
2
RDE_SETUP_PROCESS
3		RDE_REFRESHODIVARIABLES_JOB MERCHSTART_BATCH_PROCESSSTART_BATCH_JOB

Appendix A Tab Definitions

  • JobStartPath – VARCHAR (4000)

    • ReST Endpoint path to start a job (for example, /start ).

    - Mandatory field if a job type is defined on this tab.

  • JobRestartPath – VARCHAR (4000)

    • ReST Endpoint path to restart a failed job (for example, /restart ).

    • Can be left blank on this tab but, if so, needs to be provided later on the UI.

  • JobStatusPath – VARCHAR (4000)

    • ReST Endpoint path to check the status of a previously submitted job (for example, / status ).

    - Mandatory field if a job type is defined on this tab.

  • JobLogPath – VARCHAR (4000)

    - ReST Endpoint path to fetch log file of a job (for example, `/logs` ).
    • Can be left blank on this tab but, if so, needs to be provided later on the UI.

  • JobKillPath – VARCHAR (4000)

    - ReST Endpoint path to kill a running job.
    • Can be left blank on this tab but, if so, needs to be provided later on the UI.

  • OAuthScopes – VARCHAR (4000)

Comma-separated list of OAuth scopes for invoking the endpoints.

  • Mandatory field if a job type is defined on this tab.

If there are no custom job types in the schedule, then leave this tab empty.

MandatoryScheduling Tab

  • Name – VARCHAR (4000)

    - Holds the name of the Adhoc Process or Flow.
    • The process or flow name should be defined in Process or Flow sheet respectively.

  • Description – VARCHAR (4000)

    • Holds the description of reason for scheduling this Adhoc flow/process at the specified time.

  • Frequency – VARCHAR (4000)

    - Holds the Frequency at which this Adhoc process/flow is to be run.
    • Valid values are: ONCE DAILY, WEEKLY, MONTHLY, MONTHLY_START, MONTHLY_END, MONTHLY_BY_WEEKDAY

  • Nth Day of the Week in a Month – VARCHAR (4000)

    - Holds the Nth day of week in a month on which task must be run.
    • Valid values are: FIRST, SECOND, THIRD, FOURTH, LAST.

  • Day of Week – VARCHAR (4000)

    • Holds the day of the week on which the task must be run

    • Valid values are: MONDAY , TUESDAY , WEDNESDAY , THURSDAY , FRIDAY , SATURDAY , SUNDAY.

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-20 of A-22

Appendix A Tab Definitions

  • Day of the Month – VARCHAR (4000)

    • Holds the day of the month on which the task must be run

    • Valid values: [1-31]

  • Start Date – VARCHAR (4000)

    • Holds the Start Date of the task, only for frequency set to ONCE

    • Valid value: valid date in the format yyyy-mm-dd. For example: 2023-01-05.

  • Recurrence – VARCHAR (4000)

    • Indicates if an activated task is meant to run just once or recurs multiple times.

    • Valid values: SINGLE/MULTIPLE.

  • Interval – VARCHAR (4000)

  • Indicates an interval number of minutes the at which the task should run again.

– Valid values: Any positive integer number of minutes starting from 1. For example: 5, meaning this Adhoc will run every 5 minutes.

  • Limit Occurrences – VARCHAR (4000)

    • Relevant only when frequency of EVERY:x is used. If a Limit Occurrences value is entered, the process will run a maximum of times equal to the specified limit.

    • Valid values : A positive integer. For example: Frequency of DAILY with a Limit Occurrences of 4 and Interval 2 means the process/flow will run every two minutes a maximum of four times

  • Prevent start during Nightly – VARCHAR (4000)

    • A flag which, when set to Y, indicates that this process is not to be started when the Nightly cycle is running. If the Scheduler tries to start a run while Nightly is running, the execution’s status is set to Error with an Info message of “Nightly started running so can’t run the process.”

    - Valid values are: Y or N.

  • Do not start nightly – VARCHAR (4000)

    • A flag which, when set to Y, indicates that Nightly cycle has to wait for this process to get completed.

    • Valid values are: Y or N.

  • Schedule Time – VARCHAR (4000)

    • POM supports the following keywords for the scheduling of the Mandatory tasks:

    • start - This is a reference to the Scheduler Day creation event. Positive offsets from this event can be added

    • nightly - This is a reference to the Nightly scheduled task. Positive and negative offsets to this time can be added.

Examples :

  • start+8 – 8 minutes after Scheduler Day creation;

  • nightly-8 – 8 minutes before the Nightly start time;

  • nightly+8 – 8 minutes after the Nightly start time.

  • Timezone Region ID – VARCHAR (4000)

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-21 of A-22

Appendix A Tab Definitions

  • Timezone corresponding to the time entered in the subsequent cell(s). Timezone region ID is required rather than a UTC offset such as UTC-06:00. This is to accommodate Daylight Saving Time.

  • Valid timezone region IDs such as US/Eastern can be found as TZ database name at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones.

Example

Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.

July 15, 2026 Appendix A-22 of A-22

In this guide

  • Import Configuration — POM Implementation Guide · shares MONTHLY_BY_WEEKDAY, MONTHLY_END, MONTHLY_START, REST_EXEC
  • 4 Scheduler Tasks — POM Implementation Guide · shares MONTHLY_BY_WEEKDAY, MONTHLY_END, MONTHLY_START

Graph View

Backlinks