6Submit and Monitor Flows

This chapter contains the following:

Submit Flows

Submit a Flow

Use the Submit a Flow page to submit a flow. You can submit these flow types from the flow submission page:

  • Process, such as Calculate Payroll. This type of flow has a single task.

  • Report, such as the Run Payroll Activity Report. This type of flow has a single task.

  • Data Load, such as a task that loads payroll setup objects into the Oracle HCM Cloud application stage tables.

  • Task Flow, such as the Payroll Cycle, which lists the payroll tasks to complete for a payroll period in a best practice flow.

Navigate to My Client Groups > Payroll from your Home page and click Submit a Flow under the Flow Submission and Results section. The Submit a Flow page opens.

What You Can Do on the Submit a Flow Page

Search on the flow pattern name or use the filters on this page to select the flow pattern you want to submit. Use the Show Filters field to view the fields on which you can filter.

Select an LDG to narrow your search to flows specific to the selected LDG.

After you search and select the flow, the Submit a Flow page opens. Follow these steps to submit the flow from this page:

  1. Enter a name for the instance of the flow that you're about to submit. For example, if you're submitting the Calculate Payroll flow pattern for a weekly payroll run, enter a flow name that uniquely identifies the payroll run, such as 'Weekly Payroll 10/10/19'.

    Note: It's best practice to enter a name that includes the payroll period, so that it's easier to identify later.
  2. Use the Parameters section to enter the flow parameters, including, process date, run type, and payroll. The flow pattern controls which parameters are available on the page.

  3. Use the Schedule section to schedule the flow. You can use a predefined schedule if available or select 'As soon as possible' to run the flow as soon as you submit the flow.

  4. Use the Linked Flows section to link another flow to your current flow, or link your current flow to another flow. Your data security access controls which flows you can view and submit, and therefore, which flows you can connect. For more information, refer to the 'Examples of Linking Flows' topic in the Help Center.

  5. If you have enabled logging, a message appears on the page to indicate that logging is enabled. Before submission of the flow, either disable logging of the defaulted group or select another process configuration group that doesn't have logging enabled. For more information, refer to 'Enable Logging for Payroll Flows ' topic in the Help Center.

When you submit the flow, you're taken to the Checklist page. Monitor and manage the tasks within the flow from the Checklist page.

For more information, refer to the 'Checklist and Flow Tasks' topic in the Help Center.

Combine Payroll Flows

Use flow pattern connectors, consolidation groups, and link flow options to consolidate the results of more than one payroll or QuickPay into a single flow. You combine flows to consolidate payroll results for your business activities, such as reporting.

Recollect that you can use flows for monitoring and managing payroll tasks, such as calculating payrolls, running reconciliation reports, and for making payroll payments.

Let's consider this scenario where the Payroll Manager wants to consolidate some of their payroll flows. Each payroll period, Vision Corp completes all payroll tasks within the regular weekly payroll cycle. And the payroll flow ensures that all weekly paid employees receive their payments on the payment date. Every day, the Payroll Manager runs multiple off-cycle payroll runs to handle exceptions, such as late payments or final payments for terminated employees. The manager might decide to make these types of off-cycle payments on any day within the same payroll period.

Note: Segregate the regular and off-cycle payroll run results even when payment dates fall on the same day.

As shown in this table, you can use these options to combine both your regular and off-cycle payroll flows.

Task and Option Page Where You Can Configure the Option Used To

Flow Pattern Connectors

Payroll Flow Patterns

Segregate and combine flows using the connector rules that you define on the flow patterns page. For example, segregate QuickPay results from calculate payroll results in your daily payroll reporting flows, and combine QuickPay results and calculate payroll results in your weekly transfer to subledger accounting flow.

Note: When defining flow pattern connector rules, use the same consolidation group for all calculations within the payroll cycle, such as all regular and on-cycle flows.

Consolidation Groups

Consolidation Groups

Note: Assign the consolidation group to a payroll definition.

Segregate or combine the results of multiple payroll runs. For example, limit the payroll results included in the payroll costing report by entering a consolidation group parameter when submitting the report.

Linked Flows

Flow Submission

Link a flow to another completed flow.

Combined Payroll Run Results

You can consolidate the run results of more than one payroll or QuickPay into a single flow. Use the information in this table to understand which type of run results you can combine in a flow task.

For example, use flow connectors, consolidation groups, or the link flows option to consolidate the results of multiple payroll runs in reports such as the Payroll Activity Report and Payroll Costing Report.

Type of Payroll Run Results Combined in Flow Task

Retroactive Pay Results

Run Retroactive Entries Report

Payroll and QuickPay Results

Run Gross-to-Net Report

Run Payroll Activity Report

Run Element Results Register Report

Run Payroll Costing Results Report

Run Payroll Deduction Report

Run Payroll Balance Report

Run Employee Active Payroll Balance Report

Prepayment Results

Prepayment Results

Archive Periodic Payroll Results

Run Payment Register Report

Archive Results

Run Payroll Register Report

Generate Check Payments

Generate Check Payments for Employees and Third Parties

Make EFT Payments

Archive Results and Check and EFT Results

Generate Payslips

Payment Results

Run Third-party Payment Register Report

Check and EFT Results

Transfer to SLA

Flow Connectors

To consolidate one or more payroll flows using flow pattern connectors, you configure flow connector options, such as connector status and connected flows.

Connector Status

Indicate whether you want the flow pattern to include payroll results generated by tasks in other flows or by tasks in the same flow.

This table lists the values you can select in the Connector Status field.

Connector Type Used to Include Payroll Results Best Practice

Task Flow

That are generated by tasks in other flows.

Select this option if you're using any of the options to combine flows, such as the flow connector.

Parameters Only

That are generated by tasks within the flow.

Don't select this option if you're using any of the options to combine flows, such as the flow connector.

Connector Name

Indicates the name used to identify the flow pattern for the purpose of flow connector rules. This field is defaulted to the name of your flow pattern.

Connected Flows

Select the connector name of each flow pattern you want to connect to your flow pattern. These connector rules are automatically applied each time you submit the flow.

Let's assume that your flow pattern includes all payment related tasks, such as prepayments and the EFT process. Use the connected flows option to identify the flow pattern you want to include in this payment flow, such as your QuickPay flow.

When you submit a flow task, the application automatically evaluates the connected flow rules. For example, each time you submit your payment flow, the application automatically includes all QuickPay run results from the connected flows. The payroll results from other flow patterns, such as your regular payroll flow, isn't included in your payment flow unless connector rules are defined.

Let's assume that you want your costing flow pattern to include all QuickPay and calculate payroll results. Use the connected flows option to connect your QuickPay flow pattern and your regular payroll run flow pattern to your costing flow. Each time you submit your costing flow, the application automatically includes the results from all QuickPay and calculate payroll run results from the connected flows.

You can connect the following types of flow patterns:

  • Predefined flow patterns, which are within the same LDG as your flow pattern.

  • User-defined flow patterns, which you have added to the lookup values.

  • Flow patterns, which have a status of active and hidden.

Security

You can edit a flow pattern and the connected flows only if you have the required functional security to perform the tasks.

For example, to connect the QuickPay and Off-Cycle Payment flows, you must have security access for both flows. When submitting a flow, you need security access to the flow pattern that you're submitting.

Where Can I view My Flow Connector and Linked Flows

You can view your flow connector details on these pages.

  • Flow Submission Page

    The Connected Flows region on the Submit a Flow page displays the connector names associated with your flow pattern. Perform any updates to these rules on the Flow Pattern page. When submitting your flow, you can't add, delete, or edit the connector rules.

  • Checklist Page

    The Checklist page displays any linked flows that you defined when you submitted the flow.

    However, this page doesn't display the connected flows you defined on the flow pattern page. This is because the application dynamically evaluates the rules each time you submit a flow.

  • Process Results Page

    The Process Results Summary and the Person Results pages display the Connector Name for the flow pattern as read-only information. You can use this information to troubleshoot any flow connector issues.

Use the Flow Pattern Connector options to consolidate the results of one or more payroll or QuickPay into a single flow. The application runs the flow connector rules each time you submit a payroll flow.

Scenario

Vision Corp runs daily off-cycle runs for making early payments to terminated employees. The company consolidates the results of such off-cycle runs for the purpose of reporting and for processing payments. However, any on-cycle runs that are processed on the same day should be excluded from the off-cycle reports and payments. Also, for the monthly costing processes, the company wants to consolidate the results of all on-cycle and off-cycle runs.

Best Practice Configuration

On the Payroll Flow Patterns page, create flow pattern connectors to consolidate the payroll run results. Specifically, create and consolidate these flows.

  1. Use the Regular Weekly Payroll flow to segregate the results of your regular on-cycle flow. This flow pattern includes all tasks required for your regular payroll including the payroll calculation, reconciliation, and payment tasks.

  2. Use the Quick Pay flow to identify off-cycle payroll runs and to calculate daily QuickPay details.

  3. Use the Off-Cycle Payment flow to consolidate the results of all daily QuickPays. This flow pattern includes all tasks required to reconcile and pay the daily off-cycle runs. Use connector rules to ensure this flow pattern includes the payroll results of all daily QuickPay flows.

  4. Use the Monthly Costing flow to consolidate all on-cycle and off-cycle payroll results. This flow pattern includes all tasks for costing reconciliation and for transferring payroll costs to the general ledger. Use connector rules to ensure that this flow pattern includes payroll results of both the Regular Weekly Payroll and QuickPay flows.

Flow Connector Rules

This example illustrates how you could use connector rules to ensure that your reconciliation reports include the relevant payroll results.

Your payroll department is notified of a late hire, Joe Smith, who requires immediate payment. The payroll team has already processed multiple off-cycle QuickPays for the day and has generated all reconciliation reports as part of their Off-Cycle Payment flow.

To account for the additional new hire and late payment in the latest reports for the day, the Payroll Manager performs these tasks:

  • Submits an additional QuickPay flow for Joe Smith.

  • Reruns the reconciliation reports, for example, the Gross-to-Net report, using the Off-Cycle Payroll flow. This action ensures that the QuickPay results for Joe are included in the latest reconciliation reports.

The manager can now continue with all remaining tasks in the daily Off-Cycle Payment flow.

Note: When you copy a flow within the same LDG, the application copies the connector rules to the new flow pattern.

Link Flows

When you submit a flow, you can link it to one or more completed flows from the Linked Flows section of the flow submission page. For example, you can link the Payroll Activity Report to the Calculate Payroll flow to verify and validate the run results, before processing the payments.

If you link the flow to active flows, the Linked Flows section of the active flows list the newly submitted flow. You can't combine flows that are in progress, but you can submit a flow and link it to an active or completed flow.

Since you're linking the flows on the flow submission page, you can link the individual runs only at the flow instance level.

Note: If you frequently link a flow to another flow, such as an extract to a weekly payroll run flow, add that flow to the payroll flow pattern for your weekly payroll run. The next time you submit the flow, the checklist includes the task.

Your data security permissions control which flows you can view and submit, and therefore, which flows you can link.

You can view the linked flows on the Checklist page. You can view details such as name of the flow linked to the current flow, when the linked flow was submitted, status of the linked flow, and so on.

Examples of Linking Flows

When you submit a flow, you can link it to one or more completed flows from the Linked Flows section of the flow submission page. Your data security access controls which flows you can view and submit, and therefore, which flows you can link.

This topic explains how you can link flows. You can link them at the beginning or end of a flow, or within an active flow, as explained here. Each of these options include several examples of linking flows.

Link a Flow at the Beginning or End of Another Flow

Submit a flow and link it to the beginning of a flow that you haven't started or to the end of a completed flow. For example, submit the costing of payments flow and link it to the end of a completed QuickPay and payments distribution flow to cost the payments for both flows.

Here's an example of submitting a report flow and linking it to the end of the prepayments flow to view the prepayments results in the report.

A report task flow added to an active flow to view the
results.

This example illustrates submitting a flow to cost payments and linking it to a monthly and weekly payroll flow to process the combined results.

Two completed flows linked to a costing of payments flow.

Link a Flow Within an Active Flow

You can't combine two flows that are in progress, but you can insert a new flow into an active flow.

  • You can do this to perform tasks in an activity, such as the payments or accounting activity.

  • You can link flows to process two sets of records in a single prepayments process. For example, if you remove records for correction from the regular payroll run flow, and then process them with several QuickPay flows, you can merge them to calculate the QuickPay payments.

When you link flows, consider whether the submitted flow includes the same tasks as the active flow after the insertion point as given here.

Tasks After Insertion Point Action

Same tasks

Select the Use to Calculate Results option to process the results of both flows in the remaining tasks

Different tasks

Specify where to stop the active flow and complete tasks in the submitted flow before returning to the active flow

This figure shows the sequence of tasks processed if you submit a QuickPay flow and link it to the payroll run flow for the same payroll and payroll period to process the payments tasks together.

  1. After the payroll calculation in the payroll run flow completes, the QuickPay calculation starts.

  2. The application waits to run the Gross-to-Net task until the task to verify the QuickPay results complete.

  3. The application skips the remaining tasks of the QuickPay flow, which are the same as the payroll run flow, and uses the results of the QuickPay flow in the payroll run flow.

QuickPay flow merged at the Run Gross-to-Net Report
task.

This figure shows the sequence of tasks processed if you submit a QuickPay flow and select the option to use the results of the QuickPay calculation in the reports generated for the payroll run flow. In this example, the flows don't include the same tasks.

  1. After the payroll calculation in the regular run completes, the QuickPay calculation starts.

  2. After the QuickPay verification task completes, the application processes the two reports that include the results of the QuickPay flow.

  3. The application returns to the QuickPay flow to process the external payment.

  4. After the QuickPay payment verification task completes, the application processes the payments for the regular run.

QuickPay results included in the regular run verification
reports and excluded from the payments process.

How Do I Link a Flow to a Current Flow

In this example, you link the Calculate Prepayment Flow to the monthly payroll cycle to process prepayments using the payroll run results.

You can manually run both of these tasks as standalone tasks, however, by linking the two tasks, you automate the tasks, so that the Calculate Prepayments task runs immediately after completion of the Calculate Payroll run. The Calculate Prepayments task uses the payroll run results from the Calculate Payroll task to process the payments.

In this example, the payroll manager submits the Calculate Prepayments flow to view the payments for the current and previous monthly payroll runs. Rather than run the standalone Calculate Prepayments task, the manager links this task after the Calculate Payroll task so as to process the prepayments using the monthly payroll run results.

Before you begin, complete these tasks:

  1. Create a payroll flow pattern to process a biweekly payroll.

  2. Submit the monthly Calculate Payroll January 2020 flow for the payroll period that ends January 31, 2020.

Submit the Calculate Payroll Flow

  1. Navigate to Payroll in My Client Groups, and click Submit a Flow.

  2. Select the legislative data group.

  3. From the Select a Flow section, search for and select Calculate Payroll. Click Next.

  4. In the General Information section, enter the payroll flow name as Calculate Payroll January 2020.

  5. On the Enter Parameters section, complete these fields.

    This table lists field names and their respective values to run the Calculate Payroll flow.

    Field Value

    Payroll Flow

    Calculate Payroll January 2020

    Payroll

    Monthly Payroll

    Payroll Period

    01 2020 Calendar Month

    Run Type

    Regular

  6. In the Schedule section, chose to either run the flow as soon as possible or enter the schedule details.

  7. In the Linked Flow section, click Add.

  8. Enter these details in the row.

    This table lists field names and their respective values to link flows.

    Field Value

    From Payroll Flow

    Calculate Payroll January 2020

    From Task

    Calculate Payroll

    To Payroll Flow

    Current Flow

    To Task

    Calculate Prepayments

    Used to Calculate Results

    Select this check box to enable prepayments calculations.

  9. Select the Process After Error check box.

    This allows the tasks in the flow to continue processing, irrespective of a previous task, in the current flow or a cross flow that you have linked, encountering errors. You can later run a warnings or error report to review and analyze the errors and take

  10. Click OK.

  11. Click Submit.

    Go to the Checklist page to view and monitor the progress of the tasks.

FAQs for Combine Payroll Flows

Can I use flow pattern connectors and consolidations groups together?

Yes, you can use consolidation groups in conjunction with the connected flow feature. However, when defining flow pattern connector rules, use the same consolidation group for all calculations within the payroll cycle, such as all regular and on-cycle flows.

What's the difference between using flow pattern connectors and consolidation groups for flow combination requirements?

Flow pattern connectors provide the flexibility to combine and segregate payroll results for downstream processes and reports. For example, flow connectors enable you to segregate payroll results for reporting purposes but combine the results for payroll costing purposes.

Consolidation groups support more basic requirements such as the combination of payroll results for reporting and payroll costing purposes.

If you choose to define flow connector rules, use the same consolidation group for all calculations within the payroll cycle.

What happens if I enter a consolidation group parameter, does it override my flow pattern connector rules?

When you define flow pattern connector rules, use the same consolidation group for all calculations within the payroll cycle. For example, use the same consolidation group parameter for Calculate Payroll and Make EFT Payments tasks, within the payroll cycle, so that the process executes the flow connector rules. If you enter a consolidation group parameter to limit the results included in a process and you have also defined flow connector rules, the flow connector rules take precedence and the consolidation group parameter may not be applied.

What type of payroll results are supported by the flow pattern connector feature ?

The results of all payroll calculations and QuickPays (including payroll costing), and optionally balance adjustments are supported. Use connected flow rules to segregate or combine these results in downstream payroll tasks such as reconciliation reports, payment tasks, and transfer to subledger accounting.

No, if you have defined connected flow rules for a flow pattern, the link flow feature is disabled for use on the Submit a Flow page.

Monitor and Manage Flows

When you submit a flow pattern it creates an instance of the flow. For every submitted flow, the application generates a checklist by default. When you submit a flow, you're taken to the Checklist page so that you can manage and monitor the tasks and other parameters within the flow.

You can also use the View Flows page, and click on a flow to go to the Checklist page of the selected flow.

Here's what the checklist might include, depending on the flow pattern.

  • Automatic tasks, such as extracts, reports, and processes

  • Manual tasks, such as the Verify Payroll Process verification task, required to complete a flow

Here's what you can do with checklists.

  • Monitor the status of the flow tasks

  • Manage the flow tasks, such as reassigning tasks, marking tasks as completed, and performing corrective actions

  • View task details, such as a list of records processed by the flow

While working on a task in the flow, you can remain on the Checklist page or go to a related page that includes tasks in the flow. For example, while reviewing the results for the Calculate Payroll task, you can go to the related pages to review the person's calculation card or element entries.

What You Can Do on the Checklist Page

Perform these tasks to manage and monitor flows from the Checklist page.

  • Manage and track all tasks within the task flow.

    For Task Flows with multiple tasks, the Checklist page provides the status summary of the tasks:

    • Completed Tasks

    • Completed With Alerts

    • Critical Alerts

    • Pending

    Expand the Tasks section and drill down to each individual task and view the task status and take an action specific to the individual task.

    The actions available to you when working with a task depends on its status and the status of the tasks that precede or follow it. For example, if a task has completed with alerts, it indicates that the process has completed with one or more records in error status, the process has been rolled back, or marked for retry.

    Click on the task to view the process results and drill down to the records that have errors and need correction. After making the corrections, you can come back to the Checklist page and resubmit the task to process the records that were in error.

  • Validate a manual task within the flow and mark as complete, so that downstream tasks within the flow can begin.

    For example, a payroll manager may review and validate the details of the generated payments register and make corrections if any, before enabling the payments processing task to proceed. The payroll manager must manually set the status of the Run Payments Register task to complete, so that other downstream tasks can be initiated.

  • View task status and drill down to the task parameter details.

  • Reassign a task to a different owner. Drill down to a task and select the Change Owner task action to change the owner of the task.

  • Drill down to the Parameters section to view the flow parameter details.

  • Drill down to the Linked Flows section to view flows and tasks linked to the current flow. Click on the flow to view the details of the flow linked to the current flow. Use the Back arrow to return to the current flow page.

  • Drill down to the Process Results page to view all messages and errors for a task. Once you have identified the records that have errors, click on the person name to see what the error is, and take corrective action on them. You may have to return to the person's record to correct the errors.

  • Drill down to the Process Results page to access output information for a task such as reports and log files.

  • Use the Roll Back All option from the Actions menu on the checklist page to roll back multiple tasks within a flow. You don't have to manually select each task to roll back the tasks within the flow.

After you have taken appropriate corrective action, you can go back and use the Actions menu and mark the record for retry.

Use the View Flows page to view the status of submitted flows that are in progress and require your attention. The flows on this page display a high-level status of the flow.

To open the View Flows page, navigate to Payroll in My Client Groups from your Home page and click View Flows under the Flow Submission and Results section.

The View Flows page displays the overall status of a flow, and each task within the flow can have a different status.

For this reason, the View Flows page displays the flow status based on the flow hierarchy. The flow hierarchy is used to display a flow status based on the task within the flow that has the most critical status.

What You Can Do on the View Flows Page

Search on the flow pattern name or use the filters on this page to select the flow pattern you want to submit. Use the Show Filters field to view the fields on which you can filter.

You can filter on a wide range of filter choices such as Legislative Data Group, payroll, submission date, submitted by, flow type, flow patterns, flow status, and so on.

Use the Submission date to filter and view at a glance active flows submitted:

  • On the same day

  • In the last seven days

  • Within a date range

Use the Submitted By field to filter on the person who has submitted a process. The Submitted By field is a free text field and you can only use the 'contains' filter option, you can't use any other filter option for this field.

After you search and select the flow, you can perform these tasks on the View Flows page:

  • Monitor and track all tasks within the flow.

  • Monitor issues with the flow such as processes in error, and review processes that are running slower than average.

  • Select a task to go to the Checklist page or Process Results page.

From the payroll dashboard, view the status of submitted flows that are in progress and require your attention. You can also drill down to the payroll checklist and view details of a specific flow.

This topic explains how you can monitor the status of the flows and take corrective action if required. The payroll dashboard has separate sections to view the items requiring your attention and view details of flows that are in progress.

View Items Requiring My Attention

The Items Requiring My Attention region monitors notifications that you receive about the flows. You can view:

  • The number of error notifications and warning messages about flows that need your attention.

  • The reminders about tasks that are overdue and require an action from you.

To view items requiring my attention:

  1. Click the Payroll Dashboard link from the Navigator.

  2. On the Items Requiring My Attention toolbar, click Errors. You can see the list of errors that you must fix.

  3. Click a specific error to drill down further and investigate the error.

  4. On the Items Requiring My Attention toolbar, click Warnings. You can see the list of warnings that needs your attention.

  5. On the Items Requiring My Attention toolbar, click Tasks. You can see the list of tasks errors that needs your attention.

You can use the Refresh button to view an updated status of your notifications.

View Flows in Progress

From the Flows in Progress region monitor the status of submitted flows, either by graph or by listing.

  1. Click an item on the analytic graphic, for example, the US Simplified Payroll Cycle, to view the details of the flows that are in progress. The submitted flows are all listed in the payroll flows section.

  2. Highlight a flow and click the name to open the specific payroll checklist. The checklist organizes the tasks within the flow by payroll activity and task groups.

  3. If you don't find a specific payroll flow, click Query by Example and search for a flow.

The Task Type column identifies tasks as either manual or automatic. Manual tasks are identified by a person icon with a check mark. Automatic tasks are shown with spoke wheel icons. Automatic tasks begin automatically when the task before it's complete.

Manual tasks work like stop points in the flow where you can verify results and perform any corrections required before continuing with the next task. They generally involve tasks that require validating results, for example generating reports and validating report results.

View the Task Details

To view the status of a task, you may have to drill into the task group. For example, you may want to view the details of the records processed for the Calculate Payroll task.

  1. Expand the Calculate activity within the specific payroll flow.

  2. Expand the Calculate and Validate Payroll task group.

  3. Click the Go to Task icon for the completed Calculate Payroll task.

The View Person Process Results: Calculate Payroll page lists the records (persons) processed in the flow. The Action Status column shows the status of the records. It shows the records that are processed successfully and those that have errors and require further action.

Take Corrective Action

Once you have identified the records that have errors, you must take corrective action on them. Click the person name to see what the error is. You may have to return to the person's record to correct the errors.

Use the Actions menu to take any of these actions on a record:

  • Mark for Retry

  • Rollback

  • Reversal

After you have viewed the error and taken appropriate corrective action, you can go back and use the Actions menu and mark the record for retry.

View the Payroll Run Results

After a task is completed, you can verify the run results and view a report. For example, you may want to view the Gross-to-Net report.

  1. Click the Go to Task icon of the completed task, for example the Run Gross-to-Net Report task.

  2. Click the Task Results (glasses) icon to view the PDF output of the report.

For completed tasks, you can view the process results in these pages:

  • Process Results Summary page to view all processes. The default view will display all processes submitted in the last seven days. Use the filters to expand the date range.

  • Process Results Details page to view details of a specific process.

  • Person Process Results page to get an overview of processes run for a person and view details of each process.

Process Results Summary Page

The Process Results Summary page displays by default processes that have been submitted and completed in the last seven days. It displays processes with these statuses:

  • Critical Alerts

  • Completed

  • Completed With Alerts

  • In progress

The page doesn't display processes that are pending or scheduled or that have been corrected, such as rolled-back.

Navigate to Payroll in My Client Groups from your Home page and click Process Results Summary under the Flow Submission and Results section. The Process Results Summary page opens.

Here's the list of tasks you can do on the Process Results Summary page:

  • Check the status of recently submitted processes.

    For example, before processing payments, as a payroll manager, you may want to review and ensure that all the payroll processes and reports have completed without any errors. If any of the person records have errors, use the Process Results page and search for a person record to see what the error is. You can return to the person's record to correct the errors, before resubmitting the payroll process.

  • Use the filter option to view flows as per your choice and for a wide range of filter choices such as LDG, payroll, submission date, submitted by, flow type, flow patterns, flow status, and so on.

  • Monitor the status of all processes and reports submitted across Legislative Data Groups.

  • Drill down to the Process Results Details page to access detailed information for a specific process such as messages, output reports, and log files.

  • View single task parameters.

  • Take corrective action on records that have errors and submit the task.

  • Use the Submitted By field to filter on the person who has submitted a process. The Submitted By field is a free text field and you can only use the 'contains' filter option, you can't use any other filter option for this field.

Process Results Details Page

The Process Results Details page is accessible from a task in the Checklist or Process Results Summary pages. View further details of the selected task in these four sections on this page:

  • Person Process Results

  • Output and Log Files

  • Parameters

  • Linked Flows

Since this page is in the context of a process, you can view these details of a specific process and take corrective actions as required.

  • View error details for an employee by drilling down to the messages and reviewing the cause for the errors.

  • Identify employees with rolled-back records and ensure that the employee records are processed before moving onto the next downstream task in the process.

  • Identify employees marked for retry so that they're not left out. For example, after you have started the payroll run, you come to know that a few employees are eligible for a bonus or an extra raise. You identify these employee records and mark them for retry. After the process is completed, check the run results to ensure that the records marked for retry are processed. The employee reports should reflect receipt of the extra bonus or pay raise.

  • Drill down to the Output and Log Files section and view the employee-level output, such as the employee's statement of earnings or the payslip, to check if the corrections you made in their records reflect correctly.

  • Use the View Log column in the Output and Log Files section of the Process Results Details page to view the number of log files generated by a submitted process. Click on the log file name to view and download the log file and the attachments. You can only view and download log files returned by the processes that you have submitted or have permission to view.

Person Process Results Page

The Person Results page provides details of all the processes run for an employee. Use this page to view the reports of an employee, such as Statement of Earnings, or employee's payslip.

Navigate to Payroll in My Client Groups from your Home page and click Person Results under the Flow Submission and Results section. The Person Results page opens.

All payroll results are captured at the payroll relationship level. Search for a person and select an assignment number. The Person Results page displays the results for the payroll relationship associated with the selected assignment.

The page displays results of all completed processes, details of pending and rolled-back processes aren't shown.

The type of report output is dependent on the process run for the employee and the process you select to view the details. For example, select Calculate Payroll or QuickPay to view the details of the employee's statement of account. Similarly, select Archive Results to view the archived payslips or other personal details of the employee.

You can also review the messages report to identify and correct errors. You can then roll back or mark for retry a process or reverse the process.

Payroll Messages Report

Run the Payroll Messages Report to view error, warning, and information messages from payroll processes. Generate the report for a specific flow or for all processes within a specific period. For example, run the payroll messages report to view errors and warnings for all QuickPay runs for the last month.

The report can be run by a Payroll Administrator or Manager who has security access to the payroll flow pattern for which the report is generated.

Report Parameters

The parameter values determine which records to include in the report. The following parameters have special meaning in the context of this report.

Process Start Date

Use this field to specify the first effective date of the payroll process to include in the report. All processes with an effective date same or greater than the Process Start Date are reported.

Process End Date

Use this field to specify the last effective date of the payroll process to include in the report. For Payroll Runs this is the 'Payroll Run Date'. All processes with an effective date equal to or prior to the Process End Date are reported.

Task Name

Select a task, such as Payroll Activity Report, to view the messages generated for a specific task.

Process Type

Select a specific process type such as Payroll Run to limit your report for a specific process type.

Source Flow Name

Select the name of the flow for which you want to generate the messages report.

Payroll

The name of the payroll flow you use to run this report.

Payroll Relationship Group

Select the payroll relationship group name, if you have defined one. A payroll relationship group limits the persons included in this report.

Person

Select the name of the person for whom you want to generate the messages report.

Include Information Messages

Select Yes to include information messages. Since the volume of information messages is high, it’s recommended that if you want to view information messages, you generate the report for a specific person or process. The default value for this field is No.

Person Process Status

Select a value to include only those persons with a specific processing status, such as persons In Error, or persons Marked for Retry.

Process Configuration Group

Use this field to run the report for a specific process configuration group, instead of the default one. A process configuration group is used to set rules for payroll processes, such as passwords or number of threads. You can select a value only if you have a predefined process configuration group.

Note: Use the Payroll Process Configuration task to define a Process Configuration Group, before you can use it here.
Run Mode

Use this parameter to decide if the extract-based report must retain or discard the transient data created during the report execution. The default value is Normal, the temporary transient data produced during report execution is discarded.

Report Results

The report is generated in Excel format with separate worksheets for these two types of messages:

  • Person level messages, such as error messages generated when reporting or processing a person.

  • Process level messages, such as messages generated for process failures or execution errors.

After addressing the root causes, you can rerun the payroll process and regenerate the report to ensure all issues are resolved.

Sort the report using the Line Sequence field to view the order in which the messages are generated. This helps you to track when in the process the message was generated. You can then investigate and resolve issues effectively.

Each message has a message name and message text. Samples of messages are:

  • Error Message: Formula Salary can’t be executed because the formula isn’t compiled.

  • Warning Message: Net pay exceeds 10, 000.

The report for person level messages also includes the payroll relationship number and assignment number of the person for whom the report is generated.

  • A person can have multiple payroll relationships, but each payroll process is associated with a single payroll relationship and hence the messages for a payroll process is identified with the specific payroll relationship number.

  • Some messages can be specific to an assignment such as a formula issue for a salary element entry and hence is identified by the assignment number.

Flow Statuses, Task Actions, and Notifications

Use the View Flows and Checklist pages to view the status of the tasks within a flow.

This topic covers:

  • Flows Statuses and Sub-Statuses

  • Flow Status Hierarchy

Flows Statuses and Sub-Statuses

Use the flow status information to do the following:

  • Monitor issues with the flow such as processes in error, reconciliation issues, and processes running slower than average.

  • Manage and track all tasks within the flow. Monitor the progress of a task by reviewing the percentage completion of the task. The Action menu displays the actions available for a task based on its status.

Each high-level status has a set of sub-statuses grouped together as shown in this table.

Status Group Sub-Status Sub-Status Description Displayed on View Flows Displayed on Checklist Displayed on Process Results Summary

Critical Alerts

Critical Errors

Indicates that the payroll process isn't processed due to critical errors, such as a server breakdown.

Yes

Yes

Yes

Critical Alerts

Stopped

Indicates that the payroll process has stopped processing due to a critical ESS error.

Yes

Yes

Yes

Completed with Alerts

Errors

Indicates that the payroll process has completed but one or more records are in error status.

Yes

Yes

Yes

Completed with Alerts

Rolled Back Errors

Indicates that the payroll process has completed but one or more records have been rolled back. You can process these records once you have corrected them.

Yes

Yes

Yes

Completed with Alerts

Marked for Retry

Indicates that the payroll process is marked for recalculation or retry. You can run the retry process for these records once you have corrected them.

Yes

Yes

No

Corrected Processes

Skipped

Indicates that the payroll process is skipped and not processed.

Yes

Yes

No

Corrected Processes

Canceled

Indicates that the payroll process is canceled and not processed.

Yes

Yes

No

Corrected Processes

Full Roll Back

Indicates that the process is rolled back for all records and results are removed.

Yes

Yes

No

Pending

Not Started

Indicates that the payroll process hasn't started.

Yes

Yes

No

Pending

Scheduled

Indicates that a payroll process or report is scheduled for processing.

Yes

Yes

No

In Progress

Processing

Indicates that the payroll process is currently running.

Yes

Yes

No

Completed

Complete

Indicates that the payroll process has completed successfully (for all records).

Yes

Yes

Yes

As indicated in this table, the process page displays only submitted processes. For example, it doesn't include pending processes because the flow has been scheduled to run at a later date. And, it doesn't include processes that have been corrected such as rolled-back.

Flow Status Hierarchy

A task flow indicates any flow that contains two or more tasks. For example, a flow that contains all the tasks your company completes for a specified payroll cycle is classified as a task flow

The Checklist displays the status of each task within the payroll cycle flow. However, the View Flows page displays the overall status of a flow, and each task within a task flow can have a different status.

For this reason, the View Flows page displays the flow status based on the flow hierarchy as given in this table. The flow hierarchy is used to display a flow status based on the task within the flow that has the most critical status.

Hierarchy Level Status Group

1

Critical Alerts

2

Completed with Alerts

3

In Progress

4

Corrected Processes

5

Pending

6

Completed

Submit a flow and monitor the status of the tasks within it and take actions from the generated checklist. You can also perform certain tasks from the View Flows and Process Results pages. Review the status of a flow by checking the status icons and notifications.

This topic covers:

  • Task Actions

  • Available Task Actions Based on Task Status

  • Actions Available on a Page

  • Notifications

Task Actions

This table lists the actions you can take and how it impacts a flow.

Action Description

Skip

Skip a task and set the status of the task to complete. The process skips the task and continues with the remaining tasks within the flow.

Roll Back Errors

Roll back a task, all records in error are rolled back and a payroll relationship group created for the employees in error status. You can correct data before resubmitting the process.

Roll Back All

All tasks within a task flow are rolled back. The status of the task flow is set to 'In Progress' with the number of completed tasks set to zero.

Roll Back

Available only for single tasks. Once the task is rolled back, the Status for this task is "Full Roll Back" .

Mark for Retry

Available only for single tasks. Once the task is marked for retry, the status for this task is set to "Completed with Alerts".

Retry

Resubmit records marked for retry or in error.

Retry a process that has completed with alerts to rerun any incomplete records. For example, if a process completes but has 5 errors, you can correct the data for the 5 errors and retry the task for the 5 records.

Force Resubmit

Force resubmit a task if a process is stuck due to a system issue. The task status is then set to 'In Progress'.

Submit

You can only use this action when a task has been fully rolled back.

Cancel Current and Recurring Schedule

Cancel the process due to run currently and also all processes scheduled for a future date. This action can't be supported in process results because the process has completed.

Cancel Recurring Schedule

Cancels the processes planned as part of the schedule plan for a future date, but doesn't cancel the running of the current process. This action can't be supported in process results because the process has completed. This action can't be supported in process results because the process has completed.

Only owners of the flow task, and the user who submitted the flow, can take this action. Actions aren't available to other types of users.

Available Task Actions Based on Task Status

The Action menu displays the actions available for a task based on its status. Here's a list of actions you can perform based on the status of a task.

Action Stopped with Critical Alerts Completed with Alerts In Progress Corrected Processes Pending Completed

Skip

Yes

Yes

No

Yes

Yes

No

Roll Back Errors

No

Yes

No

No

No

No

Roll Back All

Yes

Yes

No

Yes

No

Yes

Roll Back

Yes

Yes

No

No

No

Yes

Mark for Retry

Yes

Yes

No

Yes

No

Yes

Retry

No

Yes

No

No

No

No

Force Resubmit

Yes

No

No

No

No

No

Submit

No

No

No

Yes

No

No

Cancel Current and Recurring Schedule

No

No

No

No

Yes

No

Cancel Recurring Schedule

No

No

No

No

Yes

No

The actions available to you when working with a task depend on its status and the status of the tasks that precede or follow it, as given here.

Action on Current Task Status of Current Task Status of Previous or Subsequent Tasks in the Flow

Roll Back or Retry

Completed

All subsequent task must have a status of Rolled Back or Completed.

Submit

One of the following:

  • Roll Back

  • On Hold

  • Mark for Retry

All previous tasks must have a status of Completed.

Note: Only owners of the flow task, and the user who submitted the flow, can take this action. Actions aren't available to other types of users.

Actions Available on a Page

This table lists the actions available to you and from where you can use them.

Action Task or Task Flow Available in View Flows Available in Payroll Checklist Available in Process Results Summary

Skip

Both

Yes

Yes

No

Roll Back Errors

Task

No

Yes

No

Roll Back All

Task Flow

No

Yes

No

Roll Back

Task

No

Yes

Yes

Mark for Retry

Task

No

Yes

Yes

Retry

Task

No

Yes

Yes

Force Resubmit

Task

No

Yes

No

Submit

Task

No

Yes

Yes

Cancel Current and Recurring Schedule

Both

Yes

No

No

Cancel Recurring Schedule

Both

Yes

No

No

Apart from the above actions that you can perform using the Actions menu, you can also perform the following actions on the respective pages as given here.

Action Task or Task Flow Available in View Flows Available in Payroll Checklist Available in Process Results Summary

View Results

Task

No

No

Yes

View Process Details

Both

No

Yes

Yes

Single Task Parameters

Both

Yes

Yes

Yes

Task Flow Parameters

Task Flow

Yes

Yes

No

View Log Files

Yes

Yes

Yes

View Error and Warning Messages

No

No

Yes

Display Linked flows

Task

No

Yes

No

Flow Notifications

Update the flow pattern to have flow notifications sent to you to remind you of upcoming tasks or to warn you of tasks that are overdue. Completing a task removes its notifications. The setup of notifications include specifying the type of notifications and when to send them on the flow pattern. Only flow owners receive the notifications.

Specifying the number of days before the application automatically deletes a notification for the Notification Expiration Offset parameter on the Payroll Process Configurations page. To open this page, use the Payroll Process Configuration task from Quick Actions on the Home page.

Note: You receive notifications when you resubmit a task but not when you select Force Resubmit from the Actions menu.

When you submit an extract report or process or a flow, a checklist is generated. The checklist lists tasks sequentially; the sequence in which you perform to complete the flow.

This topic covers these aspects of working with flows:

  • Complete flows

  • Delete and skip flows

  • Correct tasks in a flow

Complete Flows

The Tasks Details tab of the checklist lists the manual and automatic tasks required to complete the flow. Review status icons to monitor the progress of tasks.

An automatic task is complete when the application finishes it successfully and marks it complete. A manual task is complete when you mark it complete or update its progress to 100 percent. With the exception of skipped tasks, you must complete a task before you can update the status as complete.

Delete and Skip Flows

Use the Payroll Flow Patterns task to delete a flow you copied or created, if you haven't yet submitted it. You can skip an entire flow or a task in a flow if you have submitted it.

Skip tasks, if you don't require the results when processing later tasks. If you submit a flow in error, skip the entire flow.

The details of when and who can control a flow or a flow task is given here.

Object Who Can Skip It Condition

Task in a flow

Flow or task owner

The task isn't in progress.

An entire flow

Flow owner

None of the tasks are in progress.

Skip the flow from the Checklist page

Correct Tasks in a Flow

To correct records for a task, such as records in error or missing information, the actions you take in the checklist depend on whether the correction involves the current task in the checklist or a previous one.

For a current task:

  1. Mark the records for retry.

  2. Correct the records.

  3. Resubmit the task.

Tip: If records require more investigation, avoid delaying the start of the next task by rolling back the records and processing them separately. Resubmit the task to change its status to Complete.

If you discover you must correct an earlier task, you can undo the intervening tasks, correct the data and then resubmit the tasks.

For a previous task:

  1. Start with the last manual task in progress, even if it occurs in the next activity or task group.

  2. Set the status of the manual task to incomplete.

    • Roll back all the records processed by the task.

    • Retry to change the status to Paused to correct and retry records processed by the task.

  3. Repeat this process for each intervening task.

  4. Correct the records for the task in error.

  5. Resubmit the task.

If you submit separate flows, roll back or mark for retry the flows that lock the records in the current flow before you can process the correction.

For example, you have a user-defined flow that has the Calculate Payroll task after which you run the payroll and audit reports tasks. You have submitted the flow and all the tasks in the flow have completed successfully. You then discover that you have to correct some employee records for the Calculate Payroll task and resubmit the flow. Follow these steps to correct the records from the earlier run and resubmit the flow:

  1. Open the Calculate Payroll task from the checklist, use the Actions menu to set some records as 'Mark for Retry'. The status of the task changes to 'In Progress with Error'.

  2. Set the status of each sequential task in the flow as 'Mark for Retry'.

  3. Edit the records and then set the status of the Calculate Payroll task to 'Mark as Complete'.

  4. Resubmit the flow. The subsequent tasks run automatically.

Note: If you don't complete Step 2 above, you may not see the 'Mark as Complete' status for the Calculate Payroll task.

Before defining flow patterns to correct payroll run or payment results, consider whether the flow owners can correct individual records or tasks by using these options:

  • Task Actions

  • Predefined processes

  • Predefined flows, such as the Cancel Payments flow

Use Task Actions

Most tasks support corrective task actions at the task level or individual record level. The type of task and its status determine which corrective actions the flow owner can select from the Actions menu when viewing results.

This figure shows the task actions available from the Actions menu when you work on the Payroll Flow Checklist or the Processes and Reports tab of the payroll flow.

Mark for Retry, Retry, and Roll Back task actions available
from the Actions menu when working on the Payroll Flow Checklist or
the Processes and Reports tab of the Payroll Flow.

Here's how you can confirm whether the task includes the task actions:

  1. Edit your flow pattern on the Payroll Flow Pattern page.

  2. Select the task on the Tasks tab, and edit it.

  3. Review the Execution Mode column on the Edit Task Details: Basic Information page to confirm that the task supports the Mark for Retry, Retry, and Roll Back task actions.

Use Predefined Processes

Flow owners can use the Submit a Flow task to submit these corrective processes:

  • Roll Back Process

  • Retry Payroll Process

The flow owner can use these processes to roll back or retry a flow that includes a single process and that's in progress with errors.

Use Flow Patterns

If your enterprise performs several tasks to correct problems, flow owners can use any of these.

  • A predefined flow pattern, such as the Cancel Payment flow

    The Cancel Payment flow pattern includes tasks to view the person process results, void the payment, process an external payment to prevent reissue of the original payment, and reverse the original prepayment and payroll run calculations.

  • A flow pattern you create, such as a flow pattern to reissue a lost check

    This flow pattern might include tasks to void the payment, issue an external payment, and view the person process results.

Add an Individual Flow Task within a Checklist

Use the Submit Another Task option from the Actions Menu in the checklist to add an individual flow task to a flow that's 'In Process'.

You can submit a task that's initially not included in the checklist. For instance, you're analyzing the payroll run and require additional information about pay elements included in the run. You can run an additional deduction report that's not in the initial flow.

Use the Submit Another Task option from the Actions Menu, and select any process or flow pattern and submit it.

After you select the task, select or modify the parameters presented to you. The list of parameters are the task parameters inherited from the task you have selected. The parameters are prepopulated with the entries you have made in the main flow. You can retain the same values and add new parameters or change the values of existing parameters as required.

After you submit the task, you can view the task in the Linked Region of the checklist. After you submit the task, you can either:

  • Stay in the existing checklist, or

  • Click Go to Checklist and access the checklist of the task you have just submitted. To return to the original flow, go to the related flows section and select the original flow. From here you can see the task you previously submitted in the Related Flows section. Click the task to view the checklist of the task.

Roll Back Errors Rule for Payroll Flows

When there are partial errors in a payroll flow, the process goes into an error state, and you can't move ahead. You can continue with the flow only after you take corrective action on the tasks that are in error.

Use the Roll Back Errors option from the Actions menu within the checklist to roll back a process that has errors so that it proceeds to completion. The application automatically creates a payroll relationship group for the employees having errors and removes them from the process, so that the payroll proceeds to completion.

After reviewing and correcting the errors, you can use cross-flow interactions to bring back the employees into the parent flow or process them separately in a subsequent process.

Monitor the status of tasks within a flow from the checklist generated when you submit the flow. Let's look at the steps to roll back the errors generated in a payroll process:

  1. Within the checklist, select the task that has errors.

  2. Select the Roll Back Errors option from the Actions menu within the checklist. The application displays a message that the rollback action has started. The status of the process changes from 'Error' to 'Processing'.

  3. Click the Corrective Actions icon to open the Rollback Relationship Group window to view all the rollback actions that are initiated for your process.

    You can view these details on the Rollback Relationship Group window.

    Field Description

    Name

    The name of the payroll relationship group that's created.

    Creation date

    The date of the Rollback Action and the creation of the payroll relationship group.

    Created by

    The person who submitted the Rollback Errors action.

    Rollback Count

    The number of employees that are rolled back and created in the payroll relationship group.

  4. Click the payroll relationship group Name to open the Object Groups page and view the details of the created payroll relationship group.

  5. Click Next to view the details of employees who are rolled back.

  6. Click Cancel to return back to the Checklists page.

  7. Use the Refresh button to refresh the page.

You notice that the status of the task that was in error changes to completed. You can perform the Roll Back Action any number of times and for each rollback action, the application creates a new payroll relation group. You can't use the Roll Back Errors option for a completed task.

Run a Report After a Process Errors

You can use the Allow Processing option in the Payroll Flow Patterns UI on the Tasks tab to run a report or process after a prior process has errors.

When there are partial errors in a payroll flow, the process goes into an error state, and you can't move ahead. You can continue with the flow only after you take corrective action on the tasks that have errors. Set the value of the Allow Processing column as Yes for each task in the flow that you want to run, irrespective of the status of a prior task, in the same flow or a cross flow. The tasks in the flow continue to process until it encounters a manual task or a task on the checklist that doesn't have the Allow Processing value set to Yes.

For example, if the Calculate Payroll flow has a few records that have errors, you may want to run a report to study and understand the generated errors. Reports can be run either as:

  • A separate task in a single flow. For example, the Calculate Payroll Flow may have a separate task to run all the reports after completion of the Calculate Payroll task. In this case, the Reports task can't run if the Calculate Payroll task errors.

  • A separate flow. For example you can have a separate flow for all the reports and you can have cross flow interaction to link this flow to the Calculate Payroll flow. Once the Calculate Payroll flow completes, it initiates the Reports flow. You can't run the Reports flow if the Calculate Payroll flow errors.

In both of the above cases, set the Allow Processing option on the Reports task to Yes, so that the reports are generated, even if the Calculate Payroll task has errors. You can view the report to understand the errors and take corrective actions.

Roll Back Multiple Tasks within a Flow

Use the Bulk Roll Back option from the Actions menu within the checklist to roll back multiple tasks within a flow. You don't have to manually select each task to roll back the tasks within the flow.

Let's say that you want to run a flow that has these five tasks:

Task A, Task B, Task C, Task D, and Task E

If you have performed tasks A, B, and C, and want to roll back all the tasks, you can use the Bulk Roll Back option from the Actions menu and roll back all the three completed tasks. You can then reprocess the tasks within the checklist.

Once the bulk roll back action is in progress, the roll back icon displays to indicate that the task is being rolled back. If the checklist has a large number of tasks and a bulk roll back action is in progress, only the activity that has tasks that are being rolled back are open, so that you know that a roll back action is in progress.

The Last Updated field reflects the person who took the bulk roll back action for each of the tasks. You can't bulk roll back tasks, if::

  • You don't have access to those tasks within the flow.

  • Any of the flow task instance has the IN_PROGRESS status.

  • A bulk roll back is in progress for the current flow instance.

In all of the above cases, the Actions menu doesn't display the Bulk Roll Back action.

Monitor the status of tasks within a flow from the checklist generated when you submit the flow. Complete these steps to initiate a bulk roll back action in a payroll process:

  1. Within the checklist, select the task that you want to roll back.

  2. Select the Bulk Roll Back option from the Actions menu within the checklist. The application displays a message that the roll back action has started. The status of the process changes to 'Processing'.

  3. Click Next to view the details of employees who are rolled back.

  4. Click Cancel to return back to the Checklists page.

  5. Use the Refresh button to refresh the page.

You will notice that the status of the task that was rolled back changes to completed. You can perform the Bulk Roll Back action any number of times.

FAQs

How can I regenerate a report that uses archived data ?

After submitting a report that uses archived data, you can use the Redeliver Output action from the Payroll Checklist page to regenerate the report. If the report supports additional delivery types, you can optionally change delivery options before you resubmit the report.

Locate and open the flow you submitted that includes the process, report, or extract. On the flow's Process and Reports tab, click the Process link, which is listed below the task. On the Oracle Enterprise Scheduler Output page, click the View Log button for the process. In the log window, select an option to view or save the log.

Why is the task name on checklist different from the predefined task name?

All predefined payroll processes and reports are delivered with a corresponding flow task. For example, the Payroll Calculation process is delivered with a predefined Calculate Payroll task and the Calculate Payroll flow pattern.

When you create a user-defined flow pattern and include a predefined task, you can rename the task to reflect the context of the user-defined flow pattern. For example, if you're defining a payroll cycle for your company's weekly payroll cycle, you can add the Payroll Calculation task and rename it as 'Weekly Payroll'.

After you submit the user-defined flow, the checklist displays this user-defined task name.

Cancel current and recurring scheduled flows that you own from the flow's checklist. Select the appropriate menu command from the Actions menu to cancel the current flow and the recurring schedule, or the recurring schedule only.

If you can't cancel the scheduled flow from the checklist, your system administrator can stop the job. If you based the schedule on a formula, review the formula to ensure that it contains no negative numbers. Negative numbers will produce a continuous recurring schedule.

You can delete a flow that you copied or created if you haven't submitted it. Use the Payroll Flow Patterns task to delete the flow. If you submitted a flow, you can skip the entire flow or tasks in the flow.

Payroll flow owners can also mark an entire flow as skipped from the Payroll Flow Checklist page. Marking the entire flow as skipped marks any remaining uncompleted tasks as complete.

Confirm that your role grants you security access to the flow pattern, for example to an extract report or process. For payroll, confirm your role grants you security access to the payroll definition. Finally, determine whether the task or flow owner specified in the flow pattern is for your role or user name.