6 Notifications

This chapter provides the list of notifications sent by POM to alert users about events that occur throughout the batch execution.

By default, all notifications are shown on the POM application. It is an option to configure notifications to also send e-mails. This is accomplished through the Notifications Administration function of Retail Home. Refer to the "Notifications Administration" chapter of the Retail Home Administration Guide for more information.

1. Error: This notification is sent whenever a running batch fails for some reason. This notification is for Oracle internal users.

2. Warning type: This notification is sent when application/user is trying to run an already running job.

3. InformationNotification: This notification is for System information. This notification is for Oracle internal users.

4. SystemErrorNotification: This notification is to notify of all unexpected system exceptions. This notification is for Oracle internal users.

5. New scheduler day failure: This notification is sent when there is an issue while setting up the new scheduler day, e.g. previous scheduler day has not yet been completed.

6. Intraday cycle completed: This is a low priority notification that is sent whenever an intraday cycle is completed.

7. Intraday Cycle Skipped: This is a low priority notification that is sent whenever an intraday cycle is skipped.

8. NightlyStart: This notification is sent when the Nightly cycle is kicked off.

9. Nightly cycle completed: This notification is sent when the nightly batch completes for the scheduler day.

10. Long running job: This notification is sent whenever a job is taking more than the configured threshold time for getting completed.

11. NightlySummaryReport: This notification sends out a batch summary report to the configured mail addresses when the nightly cycle is completed. This notification is for Oracle internal users.

12. IntradayCycleSummaryReport: This notification sends out a batch summary report to the configured mail addresses when an intraday cycle is completed for each flow.

13. JosSyncFailed: This notification is sent out when there is an issue in publishing disabled jobs from POM to JOS.

    Note:

    Disabled jobs are published to JOS as a part of the New Scheduler Day process. If the previous day's nightly cycle is still running at the time of New Scheduler Day creation, then publishing of the disabled jobs to JOS is done when the last job of the nightly cycle completes.

14. ScheduleChangesSummaryReport: This notification sends out the Delta Summary Changes Report to the configured mail address. Delta changes include the Jobs added to the current Schedule or Jobs removed or Jobs Status changed from the previous schedule. The External Dependency changes are also shown on the report. If there are no changes between the previous and current schedules, the notification is not sent out.

15. ExternalDepPending: This notification is sent when a Job is waiting for and External Dependency.

16. InterSchedDepPending: This notification is sent when a Job is waiting for an Inter-Schedule Dependency.

17. InterSchedDepIssue: This notification is sent when:

    • The business date between the interdependent Schedules vary by more than a day.

    • The External Schedule is day ahead of the current Schedule and previous day data is not available.

    • The inter-schedule dependencies are not valid and disabled.

    • A schedule includes inter-schedule dependencies or execution links that are not valid.

18. ApplicationModuleDisabled: This notification is sent when applications or modules are disabled during MDF synchronization.

19. ErrorNotificationExternal: This notification is sent whenever a running batch failed for some reason. This notification is for external customers.

20. NightlySummaryReportExternal: This notification sends out a batch summary report to the configured mail addresses when nightly cycle is completed. This notification is for external customers.

21. ExternalDepComplete: This notification is sent when an external dependency is completed.

22. ExecutionLinkIssue: This notification is sent if there is a failure/warning in the Execution Link invocation.

23. ApplicationModuleEnabled: This notification is sent when applications or modules are enabled during MDF synchronization.

24. ExecutionEngineIssue: This notification is sent when there are important/critical events/failures with the Execution Engine. For example:

    • When the Job Admin invocation fails or

    • When the request is stuck in SUBMITTING state and not able to auto recover or

    • When the request is stuck in SUBMITTING state with auto reconcile or

    • When the Job is stuck in STARTING state in Job Admin

25. BatchScheduleImport: This notification is sent as an update on progress/errors encountered during the schedule import process.

26. BatchScheduleConfigImport: This notification is sent when the Import Configuration function is used on the Batch Administration screen. When this notification is associated with an e-mail address, the e-mail notification is sent with an attached report. This report lists all mismatches between the imported configuration and the target batch schedule. For example, this report will list a job present in the import configuration file but is not there in the target schedule.