2 Process Orchestration and Monitoring

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.

2 Process Orchestration and Monitoring

The Process Orchestration and Monitoring (POM) application is a user interface for scheduling, tracking and managing batch jobs. It’s also a facility for migrating data from one environment to another.

Process Orchestration and Monitoring has the following tabs:

• Oracle Digital Assistant

• Batch Monitoring

• System Configuration

• Batch Administration

• Scheduler Administration

• Schedule Maintenance

• AMS Utilities

• Data Migration

• Reports

Oracle Digital Assistant

POM includes the POM Assistant, an AI-powered assistant integrated with Oracle Digital Assistant. The assistant is designed to help users find information and answer questions about POM using the User Guide, Implementation Guide, and Oracle’s internal POM support knowledge base. The POM Assistant can be accessed by clicking the POM Assistant icon

located at the bottom-right corner of the application.

Note

Oracle Digital Assistant is applicable only to Production environments.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

Download TEST Cycle Summary for 3/25/2…

@ Confirmation

AIF APPS Schedule has already run and is complete for 2023-06-22. Re-opening will clear the execution history for 2023-06-22 and load fresh schedule instance. Would you like to proceed?

Note

• A green tile with a green target icon in the top left indicates that the schedule is in progress.

• A green tile with a green checkmark icon in the top left indicates that the schedule has completed.

• A red tile with a red cloud icon indicates that a new schedule version upgrade has failed. Navigate to the Schedule Maintenance screen by clicking on the View Upgrades button to address the failure.

• A blue spinner icon in the top left of the tile (2) indicates that the schedule is in the process of being upgraded to a new version. The user can navigate to the Schedule Maintenance screen by clicking on the View Upgrades button to check the progress of the upgrade.

When a schedule is being upgraded or when the schedule upgrade has failed, the user is prevented from most activities on the Batch Monitoring and on the Batch Administration screen.

• An amber warning circle icon in the top left of the tile (2) indicates that the schedule is set to run in safe mode. This means that the batch schedule will simulate a complete run but without the jobs actually executing on the application server. Aside from the amber warning circle icon displayed in the top left of the tile, an amber ‘Safe Mode’ message is displayed in the area right below the tile area.

• An amber warning circle icon in the top left of the tile also indicates that patching is currently in progress and run executions will be paused until the patching completes. Aside from the amber warning circle icon displayed in the top left of the tile, an amber ‘Patch Mode’ message is displayed in the area right below the tile area.

• An amber tile indicates that there is no instance of the schedule for the selected business date.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

• Request Type

• Cycle

• Flow

• Scheduler Day

• Total Jobs

• Completed

• Pending

• Skipped

• Failed

• System Held

• Submitting

• Submitted

See Table Menu Options in the Common User Interface Controls for information about the options available for this section.

Execution Details

This section displays the following information about each job run by the execution request:

• Job Run ID

• Status

• Job Name

• Process Name

• Log – Download log in text file format.

• Job Execution ID

• Last Update

• First Job

• Error Info

See Table Menu Options in the Common User Interface Controls for information about the options available in this section.

Agent Job Requests Window

The Agent Job Requests window displays information about batch requests submitted to the POM Agent. The agent is the component of POM usually deployed on the application server where the batch jobs actually execute.

Click Done or the close window icon ( ) to close the window.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

The Scheduler Tasks window for the Nightly and Recurring cycles display the same task attributes listed below. The difference is that there is only one Nightly task for a scheduler day whereas there could be multiple Recurring flows running throughout the day.

Nightly/Recurring Scheduler Tasks

This section displays the following information about each Nightly/Recurring Scheduler task:

• Task ID

• Enabled - Switch to enable or disable the execution of the task

• Status - Possible values are: Enabled, Disabled, Completed, Skipped On Delay, Scheduled, Error, or Cancelled

• Flow Name - Nightly or recurring flow name

• Schedule Date

• Schedule Time

• Time Zone

Note

When the New Scheduler Day is created, if the start time for a certain task has elapsed, the task will be scheduled for the next day. The Next Schedule Run column will show the next time the task will execute.

See Table Menu Options in Common User Interface Controls for information about the options available for this section.

Task Executions

This section displays the following information about each task executions:

• Status - Possible values are: Completed, Error

• Start Time

• Info - If the Status is Error, this field changes to a link which, when clicked, will open a dialog showing error details.

See Table Menu Options in Common User Interface Controls for information about the options available in this section.

The user can edit the Nightly or Recurring tasks to change the time they run for the day. Permanent changes need to be entered in the Scheduler Administration screen.

Note

If the user makes a change to the time, he or she needs to click the Run action to schedule the task.

It is alternatively possible for the user to circumvent the steps mentioned above and click on Run Now if they intend to schedule the task for immediate execution.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

P 4

Held - An administrator placed the job on hold.

– Skipped - An administrator has skipped the running of the job so the remaining jobs in the cycle can proceed.

• Running - Job is currently running on the system.

– Long Running - The job’s run time has exceeded a threshold. If a Threshold Run Time is specified for the job on the Edit Job popup of the Batch Administration screen, then a job is deemed long running if its current run time exceeds that value. Otherwise, if a Threshold Run Time is not specified, then the job is deemed long running when its current run time exceeds the Long Run Average Time Multiplier (specified on the Edit Settings popup of the System Configuration screen) times the average run time of that job + Long Running Tolerance Level. The value for the Long Running Tolerance Level can be overridden by changing the value of batch schedule variable

defaultLongRunningToleranceLevel on the System Options screen accessed from the System Configuration screen. The value is in seconds.

For example, if a job’s average run time is 3 minutes, and the Long Run Average Time Multiplier is 3, and the Long Running Tolerance Level is 6 minutes, then the job is considered long running if it has been running for at least 15 minutes. A notification is sent when a job is deemed long running.

If the Threshold Run Time field for a job is 0 or blank, and there is no history of job run, the job will be considered long-running when its run time exceeds the default long running threshold run time of 10 minutes. This default value can be overridden by changing the value of batch schedule variable

defaultLongRunningThresholdRunTime on the System Options screen accessed from the System Configuration screen. The value is in seconds.

• Disabled - Job was disabled by an administrator on the Batch Administration screen.

• System Held - Job was placed on hold by the system due to a lack of resources to run it.

• Skipped on Error - Job was preconfigured to be skipped on a failure.

– Waiting - Job is waiting for completion of pre-dependencies (Hourly Cycle, Nightly Cycle, External Dependency and Inter-Schedule Predecessor Jobs).

• Job - Click to open the job in the Batch Job Details screen.

• Application

• Last Update

• Parameter

• Job Type - Depending on the value, determines if a job is service based or shell script based.

• Process Name

• Process Status

• Log - When the job is in error, this field will display a down-arrow icon which when clicked will display the content of the log. There’s also a ‘View Live Log’ icon which when clicked will show the streaming log.

• Job Description

• Start Time

• End Time

• Duration

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

Table 2-1 Batch Jobs - Actions Menu/Icons and Description

Actions Menu/Icons	Description
Show Disabled	Use theActions > Show DisabledorShow Disabled. By Default, the table won’t show any jobs with Disabled Status. Use Show Disabled button or action to see the list of Disabled job.
Hold	Use theActions > Holdor theHoldbutton to put the process on hold.
Skip	Use theActions > Skipor theSkipbutton to skip the process.
Run	UseActions > Runor theRunbutton to run the job manually and immediately.
	Runis disabled for both Nightly and Recurring Cycles but jobs from both of the cycles can be run fromAMS Utilities > Manual Job Runmenu.
Rerun	Use theActions > Rerunor theRerunbutton to run the job again.
Kill	Use theAction>killor theKillbutton to stop the execution of the job. The job needs to be running for this action to be enabled. When the Kill command is enacted on the screen one of two confrmation messages opens depending on whether a cleanup script is associated with the job being killed. If a cleanup script is associated with the job, the confrmation message presented is “a cleanup will be performed after this job is terminated. It is advisable to wait a few minutes after termination before proceeding with the remaining batch schedule” This is because it may take a minute or so for the cleanup to complete. If a cleanup script is not associated with the job, the user is cautioned to make sure he or she is sure about proceeding without a cleanup script. That maybe be acceptable, as not all jobs require cleanup when terminated. The confrmation message in this case is “there is no post termination cleanup script associated with this job. the job will be terminated but not post cleanup will be performed. This may or may not be ok for this job. Check with Oracle Support if this is a concern.
Edit Parameters	Use theActions > Edit Parametersor theEdit Parameters button to edit the parameters for the job. The new parameters are only effective for the current day’s batch run.

View Menu

See View Menu for information about the options in the View menu.

Skip Recurring Flow(s)

A job in a recurring flow can be skipped by selecting the job and clicking the Skip button in the table toolbar. The confirmation pop up (below) opens asking the user if the job should to be skipped for the currently selected recurring cycle or for this and all subsequent recurring cycles as well.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

Skip A3_ADHOC_JOB2

€) Warning Skipping a job may result in data corruption. You are required to enter a detailed reason for this action.

Would you like to skip this job

@) for just the immediate next execution of the job ?

© for all the job executions on the current business date ?

RPASCE_START_JOB Info

oracle.retail.apps.oam.common.rest.exception.ReSTInvocationException: Not Found I Done Auto Refresh: Refresh: = None None vy Last refreshed: refreshed: 09/15/23 16:04:47 GMT+5:30 16:04:47 GMT+5:30 GMT+5:30 ~—Refresh Rerun Failed Job(s)

When the icon is clicked, the Activity Feed panel opens on the right side of the screen. The panel displays up to seven days’ worth of activities performed both by the system and by users through the user interface.

Click the close window icon ( ) to close the window.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

Business Date : 13/09/2023

Scheduler Day Started No Comments

15/09/2023, 15:49:51 GMT+5:30 amish.sinha@Oracle.com

Business Date : 12/09/2023

Skipped Elapsed Hourly Flow(s) Skipped elapsed hourly cycle(s) [all avai lable] for all enabled flows as part of Ni ghtly request start since Nightly is waiti ng for 12-SEP-23 12/09/2023, 14:05:39 GMT+5:30 System

Business Date : 12/09/2023

Scheduler Task Run

Action Performed on [ Nightly/DUMMY _START_NIGHT_BATCH_PROCESS ] wit h Comment [ Run Job Dummy_Nightly from Rpas test Nightly for day 09/12/2 3] 12/09/2023, 14:05:37 GMT+5:30 amish.sinha@Oracle.com

Business Date : 12/09/2023

Scheduler Day Started No Comments 12/09/2023, 14:05:24 GMT+5:30 amish.sinha@Oracle.com

Note

For custom schedules, the Agent URL must be set to http:// pomagentservice:8080/POMAgent . This will enable POM to use its internal/ common Agent to run jobs.

• Schedule Variables (Optional) - These variables hold System (POM) level configurations such as IDCS or OCI IAM URL, or Job level configurations such as batch directory, DB_ALIAS, and so on. The job level configurations can also be defined on the batch schedule spreadsheet. Attributes for this section are:

  • Type - Job or System

  • Variable Name

  • Value

• Services (Optional) - This section allows for entry of services POM integrates with. These include the BDI Process Services, IDCS or OCI IAM, and all services corresponding to the different applications with service-type batch jobs. Attributes for this section are:

  • Type - This is a drop down for all the possible service types; for example, the RI Web Services URL which POM would use to invoke RI service-based batch jobs.

  • Application - Application Name to which this service corresponds such as RI.

  • URL

• Job Type (Optional) - This is an optional section for setting up one or more custom job types other than the standard, pre-defined job types provided by the retail applications, such as REST_EXEC, RI, RASE, BDI, RDS, OB, OMS, and RPAS. The user then associates a custom job type with the base URL for endpoints at the destination system. These are endpoints for starting a job, restarting a job, killing a job, checking status of a job, fetching the log for a job, and validating the URL. By setting up a custom job type, the user must then create a custom schedule spreadsheet containing jobs with that job type. When this batch schedule runs, POM executes that job using the corresponding, defined Start endpoint. If the user misses the opportunity to configure the job type at this point, they do have the opportunity to add that using the Job Type Configuration screen (see Create / Edit Job Type for more information). Attributes for this section are:

  • Name – A short, alphanumeric identifier of the job type. This typically reflects the system or application where associated jobs are to be executed (for example, RDS ).

  • URL – Base URL for endpoints at the destination system where batch is to be invoked (for example, https://server/services/batch ).

  • OAuth Scope – Authentication scope for accessing the batch endpoints at the above URL.

• Seed Nightly Cycle (Optional) - This is an optional section to auto-seed the nightly jobs in the new schedule. Entering a Schedule Name and turning on this switch creates a basic batch schedule by seeding the Nightly cycle with default start and end jobs.

Schedule Settings and Connections Configuration

Select the Schedules tab on the System Configuration screen to configure the settings and connections for an environment.

The following information is shown for each environment:

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

RI 23.2.301.0 (RI)

ra

Note

By default, logs are retained for 30 days, based on the Object Store retention setting.

• Long Run Average Time Multiplier - Used to calculate when a job is considered long running.

If a Threshold Run Time is specified on the Edit Job popup of the Batch Administration screen, then a job is deemed long running if its current run time exceeds that value.

Otherwise, if a Threshold Run Time is not specified, then the job is deemed long running when its current run time exceeds this Long Run Average Time Multiplier times the average run time of that job + Long Running Tolerance Level. The value for the Long Running Tolerance Level can be overridden by changing the value of batch schedule variable defaultLongRunningToleranceLevel on the System Options screen accessed from the System Configuration screen. The value is in seconds.

For example, if a job’s average run time is 3 minutes, and the Long Run Average Time Multiplier is 3, and the Long Running Tolerance Level is 6 minutes, then the job is considered long running if it has been running for at least 15 minutes. A notification is sent when a job is deemed long running.

If the Threshold Run Time field for a job is 0 or blank, and there is no history of job runs, a job will be considered long-running when its run time exceeds the default long running threshold run time of 10 minutes. This default value can be overridden by changing the value of batch schedule variable defaultLongRunningThresholdRunTime on the System Options screen accessed from the System Configuration screen. The value is in seconds.

• Default Average Time - Used instead of multiplying a job’s average run time by the Multiplier (defined on this screen) when the job does not have run history. This is to determine whether a job can run on a certain node when the Node Repaving is upcoming. For example, say a node’s repaving is taking place in 30 minutes. If a job has a run history and its average runtime multiplied by the Multiplier is greater than 30 minutes, then the job will run on a different node. If however the job has no run history, then this Default Average Time is used instead.

• Background Jobs - Enable or disable background jobs.

• External Dependencies - A switch for enabling or disabling external dependencies.

• InterSchedule Dependencies - A switch for enabling or disabling InterSchedule dependencies.

• Nightly Batch Window Long Running Alerts A switch for enabling or disabling longrunning alerts when the Nightly batch is projected to miss the target batch duration. To take advantage of this option, a customer needs to make sure the Target Batch Duration (defined a few bullets down) is set to a reasonable time period.

• Non-Nightly Long Running Alerts A switch for enabling or disabling long-running alerts for non-Nightly runs, including Ad Hoc and Hourly executions.

• Manual Run Callback A switch for enabling or disabling External Status Updates or Callbacks for manually run jobs.

• Repave Strategy - This strategy together with the next field’s value is used to determine if a job should be allowed to run on a particular server node. When a node is scheduled to be repaved (updated with the latest software patch), no batch job should be running on it when the repave starts. To prevent such a situation, a best guess is needed as to when a node should stop accepting jobs to be run. There are two strategies for determining when that time is:

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

**

Configuration URLs

Type Url IOcS hitps://ides-caé?887b7ea445lebdfMs7ezasb3629e.identity, cPdev2.oc?qadev.com POM https: ///home.retail.us-phoenix-1.ocs.oc-test.com/rgbu-common-pomdev-dev1210-pom RDSURL ugiyftucxgghyj RPASWSURL http://pomagentservice:8080/POMAgent

External Configuration for AIF DATA 25.1.101.0

a

Create New Job Type For SIOCS

Create New Job Type For SIOCS

a

After the sync is complete, a JSON file with the batch schedule summary is downloaded. This file contains the current and previous status of an application and module in MDF and POM after sync.

The following is a sample of that JSON file:

{

    "scheduleName":"RI","synced":true,"enabledModules": [
        {
            "state":"MATCHED_MODULE",
            "mdfStatus":"ENABLED",
            "prevMdfStatusInPom":"ENABLED",
            "prevStatusInPom":"ENABLED",
            "publishToPom":true,
            "applicationName":"RI",
            "moduleName":"RMI_SI_ONORDER",
            "matchedModule":true
        },
        {
            "state":"MATCHED_MODULE",
            "mdfStatus":"ENABLED",
            "prevMdfStatusInPom":"ENABLED",
            "prevStatusInPom":"ENABLED",
            "publishToPom":true,
            "applicationName":"RI",
            "moduleName":"RMI_SI_WHOLESALE",
            "matchedModule":true

        },
        {
            "state":"MATCHED_MODULE",
            "mdfStatus":"ENABLED",
            "prevMdfStatusInPom":"DISABLED",
            "prevStatusInPom":"ENABLED",
            "publishToPom":true,
            "applicationName":"RI",
            "moduleName":"RCI_SI_SALES",
            "matchedModule":true
        }
    ]
}

Also, the status of the updated jobs is changed to either ‘Loaded’ or ‘Disabled’ based on the module activation/deactivation in Retail Home’s Customer Modules Management.

4. Export - Use this button to export Schedule Configuration or Custom Entities for the selected schedule and cycle. Schedule configuration includes Scheduler tasks, throttle limit values, data retention values, notifications settings and (most importantly) which jobs are enabled or disabled. Custom Entities include schedule customizations that a user has performed on this Batch Administration screen such as addition of custom flows, processes and jobs.

When clicked, the user is presented with a dialog for selecting the data to export – Schedule Configuration or Custom Entities .

If ‘Schedule Configuration’ is selected, then the type of file to export (Excel or JSON) also has to be selected.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

Export AIF

• Opening RI_config.json x You have chosen to open: 5 RI_config.json

which is: JSON file (375 KB)

from: data:

What should Firefox do with this file?

; © Save File |_| Do this automatically for files like this from now on. OK Cancel

• Job Type - A Job Type is an attribute of a Job in POM and signifies the kind of Job that is run. POM has the following pre-built Job types. Other custom job type can be used that are built using the Job Type feature of the System Configuration screen.

  • REST_EXEC - For all shell-script based jobs

  • RI - DIS-based jobs for the RI schedule

  • RASE - DIS-based jobs for the RSP schedule

  • BDI - BDI Jobs

  • RPAS - RPAS-Web Service jobs for the RPAS schedule

  • OB – OB-based jobs for the OB schedule

  • OMS – OMS-based jobs for the OMS schedule

  - RDS – RDS-based jobs
  

• Kill Cleanup Script - Name of a script that will be executed after the kill is performed. This is an optional field as not all jobs require cleanup after termination.

• External Status Update - Job status for which POM is to call a customer’s URL. The URL is defined in the External Configuration section of the System Configuration screen. This column has the following possible values:

  • ALL - POM will make a call for this job’s execution regardless of success or failure.

  • FAILED - POM will make a call only for if this job fails.

  • NONE - POM will not make a call.

• Notification At

  • Start of Job – Send notification of type JobStarted when the selected job starts.

  • Completion of Job - Send notification of type JobCompleted when the selected job completes successfully. Note that there is a separate notification of type Error that is sent when a job fails.

• Skip On Error - Skip this job if it fails.

• Threshold Run Time (Seconds) - Amount of time greater than which the job is deemed long running. If a Threshold Run Time is specified here, then a job is deemed long running if its current run time exceeds that value. Otherwise, if a Threshold Run Time is not specified, then the job is deemed long running when its current run time exceeds the Long Run Average Time Multiplier (defined on the Edit Settings popup of the System Configuration screen) times the average run time of that job + Long Running Tolerance Level. The value for the Long Running Tolerance Level can be overridden by changing the value of batch schedule variable defaultLongRunningToleranceLevel on the System Options screen accessed from the System Configuration screen. The value is in seconds.

For example, if a job’s average run time is 3 minutes, and the Long Run Average Time Multiplier is 3, and the Long Running Tolerance Level is 6 minutes, then the job is considered long running if it has been running for at least 15 minutes. A notification is sent when a job is deemed long running.

If the Threshold Run Time field for a job is 0 or blank, and there is no history of job runs, the job will be considered long-running when its run time exceeds the default long running threshold run time of 10 minutes. This default value can be overridden by changing the value of batch schedule variable defaultLongRunningThresholdRunTime on the System Options screen accessed from the System Configuration screen. The value is in seconds.

• Notes

• Job Name

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

Edit Job(s)

Updating Job(s) AP_BATCH_AGG_D_JOB,AP_BATCH_AGG_END_JOB,AP_BATCH_AG…

Other custom job type can be used that are built using the Job Type feature of the System Configuration screen.

• Enable Job – Enable or disable a job

• Priority - The user can change the Priority of a job with a value from 1-10 (With 10 being the highest and 1 being the lowest and 0 as default value meaning no priority set). As long as the Priority is not modified on the UI, it can be overridden from the spreadsheet. However, once modified on the UI, the priority cannot be overridden from the spreadsheet, but only from the UI.

• Phase – The user can select a saved phase (if any) from the dropdown. Alternatively, the user can type in a new alphanumeric value.

• Parameters – Add or remove from the customized list of parameters, if allowed for that batch.

• Kill Cleanup Script - Name of a script that will be executed after a kill is performed.

• External Status Update - Job status for which POM is to call a customer’s URL. The URL is defined in the External Configuration section of the System Configuration screen. This column has the following possible values:

  • ALL - POM will make a call for this job’s execution regardless of success or failure.

  • FAILED - POM will make a call only for if this job fails.

  • NONE - POM will not make a call.

• Notification At

  • Start of Job – Send notification of type JobStarted when the selected job starts execution.

  • Completion of Job - Send notification of type JobCompleted when the selected job completes successfully. Note that there is a separate notification of type Error that is sent when a job fails.

• Skip On Error - Skip this job if it fails.

• Threshold Run Time (Seconds) - Amount of time greater than which the job is deemed long running. If a Threshold Run Time is specified here, then a job is deemed long running if its current run time exceeds that value. Otherwise, if a Threshold Run Time is not specified, then the job is deemed long running when its current run time exceeds the Long Run Average Time Multiplier (defined on the Edit Settings popup of the System Configuration screen) times the average run time of that job + Long Running Tolerance Level. The value for the Long Running Tolerance Level can be overridden by changing the value of batch schedule variable defaultLongRunningToleranceLevel on the System Options screen accessed from the System Configuration screen. The value is in seconds.

For example, if a job’s average run time is 3 minutes, and the Long Run Average Time Multiplier is 3, and the Long Running Tolerance Level is 6 minutes, then the job is considered long running if it has been running for at least 15 minutes. A notification is sent when a job is deemed long running.

If the Threshold Run Time field for a job is 0 or blank and there is no history of job runs, the job will be considered long running when its run time exceeds the default long running threshold run time of 10 minutes. This default value can be overridden by changing the value of batch schedule variable defaultLongRunningThresholdRunTime on the System Options screen accessed from the System Configuration screen. The value is in seconds.

• Notes

• Days of the Week - Days of the week for which the job is to be run.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

• Filter by Job – Search for invokable by entering job name or job-enabled value.

• Flows/Processes - The following information is shown for each flow/process:

  • Flow/Process Name

  • Enabled or Disabled

  • Flow/Process Label

Right Pane of Screen

• Jobs - Select an invokable (flow or process) from the left pane to view all jobs for that flow or process. The Jobs list shows the following information for each job. The user can also update the job by selecting it and clicking on the Edit icon. Refer to the Nightly cycle above for an explanation of each field:

– Mandatory - Indicates whether the jobs is configured by Oracle to always run. It cannot be disabled on the UI.

• Enabled

• Job - Click the Job to open the batch in the Batch Job Details screen.

• Process Name

• Base Priority

• Active Priority

• Application

• Module

• Base Phase

• Active Phase

• Parameters

• Active Parameter

• Job Type - Job Type of ‘REST_EXEC’ Indicates that the job executable is shell script based. All other job types, such as ‘BDI’, ‘RI’, and so on, indicate that the job is servicebased. Service-based job types require different configurations than shell-script based.

• Kill Cleanup Script - Name of a script that will be executed after the kill is performed. This is an optional field as not all jobs require cleanup after termination.

• External Status Update

• Skip On Error

• Threshold Run Time (Seconds)

• Notes

• Job Name

• Job Wrapper Name

• Days of the Week

Create Custom Entities - Create Flow

The user can select Create Custom Entities and click on the Create Flow option to create a new flow and its associated process(es) and job(s).

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

New Flow Details

• Can also be a custom job type defined either in the JobType tab of the Batch Schedule spreadsheet or built using the Job Type feature on the System Configuration screen.

Application

This holds the application that the batch job belongs to. It should be a valid application defined in the Application tab of the Batch Schedule spreadsheet.

Skip On Error

If the switch is on, it indicates that the job should be skipped if it fails, and the batch schedule should continue to run. Otherwise, the batch schedule is stopped.

– Fixed Parameter

If the switch is on, it indicates that the parameter value can be changed on the Batch Administration screen. The switch should be on if the parameter cannot have a default value, or if the parameter can have different values.

• Script Directory (Applicable only for REST_EXEC Job Type)

Directory where the executable batch script is located.

• Batch Name (Applicable only for REST_EXEC Job Type)

The name of the batch script to be executed which is located within the Script Directory.

• Job Wrapper Name (Applicable only for REST_EXEC Job Type)

Name of the batch file that encloses the executable batch scripts.

Base Parameter

• This holds the entire parameter value to be passed into the 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.

• A placeholder parameter #JobCtxt.businessDate can be used for jobs that require a POM business date parameter ( DDMMYYYY format).

• Kill Cleanup Script

Absolute path of the cleanup script to be run after killing a shell script (REST_EXEC) type job from the POM UI. It can include arguments as well along with the script.

For example: /u01/retail/app/batch/app_cleanup_script.sh

– Days of the Week

Days of the week for which the job is to be run if scheduled. Select all if job is to be run every day of the week.

For example, if a job is part of a process that runs every day and Days of the Week is set to MONDAY and FRIDAY , this job will only run on those two days while the rest of the jobs may run every day.

– Threshold Run Time (Sec)

Amount of time greater than which the job is deemed long running. If a Threshold Run Time is specified here, then a job is deemed long running if its current run time exceeds that value. Otherwise, if a Threshold Run Time is not specified, then the job is deemed long running when its current run time exceeds the Long Run Average Time Multiplier (defined on the Edit Settings popup of the System

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

Parameters

• This holds the entire parameter value to be passed into 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 used for jobs that require a POM business date parameter ( DDMMYYYY format).

• Kill Cleanup Script

Absolute path of the cleanup script to be run after killing a shell script ( REST_EXEC ) type job from the POM UI. It can include arguments as well along with the script.

For example: /u01/retail/app/batch/app_cleanup_script.sh

• Days of the Week

Days of the week for which the job is to be run if scheduled. Select all if job is to be run every day of the week. For example if a job is part of a process that runs every day and Days of the Week is set to MONDAY and FRIDAY , this job will only run on those two days while the rest of the jobs may run every day.

• Threshold Run Time (Sec)

Amount of time greater than which the job is deemed long running. If a Threshold Run Time is specified here, then a job is deemed long running if its current run time exceeds that value. Otherwise, if a Threshold Run Time is not specified, then the job is deemed long running when its current run time exceeds the Long Run Average Time Multiplier (defined on the Edit Settings popup of the System Configuration screen) times the average run time of that job + Long Running Tolerance Level. The value for the Long Running Tolerance Level can be overridden by changing the value of batch schedule variable defaultLongRunningToleranceLevel on the System Options screen accessed from the System Configuration screen. The value is in seconds.

For example, if a job’s average run time is 3 minutes, and the Long Run Average Time Multiplier is 3, and the Long Running Tolerance Level is 6 minutes, then the job is considered long running if it has been running for at least 15 minutes. A notification is sent when a job is deemed long running.

If the Threshold Run Time field for a job is 0 or blank and there is no history of job runs, the job will be considered long-running when its run time exceeds the default long running threshold run time of 10 minutes. This default value can be overridden by changing the value of batch schedule variable defaultLongRunningThresholdRunTime on the System Options screen accessed from the System Configuration screen. The value is in seconds.

2. Add Existing Job

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

External Dependencies

This section allows for the maintenance of the following information about a job’s external dependencies. An external dependency is normally a process internal to a customer’s system.

• Enabled - Switch to enable or disable the external dependency.

• Job

• A Remove button is available to delete the external dependency.

Inter-Schedule Dependencies

This section allows for the maintenance of the following information about a job’s interschedule dependencies. An inter-schedule dependency is a dependency for the current job on a job belonging to another batch schedule. The job for which this Jobs Detail screen is shown will wait for the job entered here.

• Enabled - Switch to enable or disable the inter-schedule dependency.

• Job - Name of job belonging to the other schedule.

• Process - Name of process containing Job.

• Schedule - Name of other schedule containing the dependency.

• A Remove button is available to delete the inter-schedule dependency.

Custom Dependencies

This section allows for the maintenance of the following information about a job’s custom dependencies. A Custom Dependency is a dependency that includes entities (process/flow) that are executed prior to the current job in Nightly or Recurring cycles. The nightly or recurring job on which the dependency is placed is triggered once the dependency completes successfully.

• Target Entity – Option to add either an Adhoc Flow or Adhoc Process

• Flows/Processes – List of Adhoc Flows or Processes.

• An Edit Sequence button is available to set the sequence of execution for the added target flow/process.

Schedule Links

This section allows for the maintenance of the following information about schedule links for a job. Schedule links are a way to link schedules together where the completion of the job in the current schedule causes the start of execution of the dependent schedule.

• Enabled - Switch to enable or disable the schedule link.

• Job - Name of job belonging to the dependent schedule.

• Process - Name of process containing Job.

• Schedule - Name of the dependent schedule.

• A Remove button is available to delete the schedule link.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

Scheduler Administration

The Scheduler Administration screen displays information about the different cycles’ Scheduler tasks and allows for their administration.

When an application’s batch schedule is initially seeded in POM, Scheduler tasks are created for each of the different Nightly, Recurring, and Standalone cycles. An administrator would then access the Scheduler Administration screen to configure the execution schedule for all available tasks according to customer’s needs.

Note

Scheduler tasks are not automatically seeded for Adhoc Custom Entities that are created using the Create Custom Entities button on the Batch Administration screen. Scheduler tasks for these custom entities need to be manually added using this Scheduler Administration screen.

A scheduler task can be configured in one of many frequencies as depicted in the table and Edit task screenshot below:

Frequency	Description
Daily	Run daily at the specifed time
Once	Run once at a specifed date and time
Weekly	Run every at the specifed time
Monthly (By Date)	Run on a particular day of each month at a specifed time; for example, on the 15th of each month at 10pm
Monthly (First Day of the Month)	Runs at the beginning of every month
Monthly (Last Day of the month)	Runs at the end of every month
Monthly (By Weekday)	Runs on the First/Second/Third…./Last weekday of the month. For example, Second Wednesday of the month

The Standalone (or Adhoc) cycle support a recurrence within each of the above frequencies.

Recurrence	Description
Single	Will run just once at the time defned on the frequency
Multiple	Will run multiple times at regular intervals starting at the time defned on the frequency

The following are restrictions enforced on scheduler task frequencies:

• Recurring cycle supports only Daily frequency. It does not support the MULTIPLE recurrence.

• Nightly cycle supports only Daily and Weekly frequencies. It does not support the MULTIPLE recurrence.

• When Nightly is setup with Weekly frequency, it needs to be setup for every day of the week. This is due to the fact that when Nightly completes for a certain day, it sets up the schedule for the next business day which cannot be skipped.

User Guide G58509-01 Copyright^© 2026, Oracle and/or its affiliates.

BATCH_EMAIL_ALERT_ADHOC_PROCESS Task Configuration

MERCH Schedule Change Summary ( 23.1.319 vs 23.1.318 ) & Entities Added ED GE Entities Removed ED @ Entities Modified (J Dependency fF Dependeney(s)Aculed Fiver ° Process Name 2 JebMame > Predecestor Process Name © Predecessor JobName > Recurring Dumeny_Process21 Recurring normal_job? Recurring Dumey_Process.21 Recurting. durwmy_job3 RecurringDumeny Process 21 Recurring normal_fob? RecurringDummy _Process_21 Recurring_normal_jobt RecurringDumeny Process_22 Recurring dummy_jobl RecurringDummy _Process_21 Recurring normal_job? RecurringDumeny Process_22 Recurring dummy_job2 Recurring Dummy Process_22 © Recurring dumeny_jobl Recurring Dumeny_Process_22 Recurring dummy_job3 Recurring Dummy_Process22 — Recurring_dummy_jobe Recurring Gumeny_Process_22 Recurring _normal_jobl RecurringDummy _Process_22 © Recurring_durwmy_job3 Recurring Dumeny_Process_22 Recurring_normal_job2 Recurring Dumey_Process_27 — Recurring_normal_job! Recurting Dumeny_Process_23 Recurring dummy_job! Recurring Dummy_Process_22 = Recurring norrrtal_job? Recurring Dumeny_Process_23 Recurting dummy_job2 Recurring Dumey_Process_25 Recurring. dumrenmy_jobt Recurring Dumeny_Process_23 Recurring dummy_job3 RecurringDummy _Process_23 Recurring dumwmy._job2 Recurring Oumeny_Process_23 Recurring normal_jobl RecurringDummy Process_23 — Riecurring_durmy_jobS Recurring Dumeny_Process_2% Recurring normal_job2 Recurring Dummy_Process_25 Recurring_normal_jobt RecurringOumeny Process_24 Recurring dummy job’ Recuning Dummy_Process25 — Recurring_normal_job2 Recurting Dumeny_Process_24 Recurting dummy_jobz Recurring Dumey_Process_24 Recurring. durrwny_jobt RecurtingDummy Process 24 Recurting. dummy_job3 Recurring Dummy_Process.24 Recurring dumwny_job? RecurtingDumeny Process_24 Recurring normal_jobl Recurring Dummy.Process24 Recurring. durmy_jobS RecurringDumeny Process 24 Recurring normal_job# Recurring Dummy Process_24 Recurring normal_jobt Recurring Dumeny_Process_17 Recurring dummy_jobl Recurring Dummy_Process 1 Recurring_normal_job RecurringDummy Process Recurring dummy_job3 RecurringDummy _Process_09 = Recurring durmamy_job?

Manual Job Run

eC‘I

Restart Process ADB_CLONE_APPLY / MFCS

Would you like to restart this process

© by retrying the current failed step ?

© by skipping the current failed step ?

Cancel Process

Cancelling this migration will stop the operation after cleanup is complete. Once cleanup finishes, the process will be marked cancelled. Do you want to continue?

eo. Skip cleanup ‘== Stop immediately without cleanup and mark the process abandoned.

Available= Clone Time= Intervals

Select a date, interval, and time within the selected interval

Batch Failures

By Week

---

In this guide

• Guide: POM User Guide
• Previous: 1 Common User Interface Controls
• Next: 3 User Roles

Related chapters

• POM — Assortment Planning Cloud Service Implementation Guide · shares AP_BATCH_AGG_D_JOB, AP_BATCH_AGG_END_JOB