List of UBEs that Must Be Run through a Single Threaded Job Queue in EnterpriseOne

Purpose
Scope
Details

Purpose

This document provides a list of standard EnterpriseOne Financials UBE reports that must be run through a single-threaded job queue. Some exceptions may be noted. A single threaded UBE means the UBE cannot have more than one instance running at the same time. If a UBE is not listed in this document, it most likely runs in a multi-threaded queue.

NOTE: For UBE reports not specifically listed in this document, when deciding to run concurrent versions and/or queues, processing options and data selection should be used to prevent selection of the same records. It is crucial that the data selections of the individual versions not overlap to avoid data corruption or data inconsistency.

Scope

This document is intended for the system administrator who will be defining the job queues within the EnterpriseOne environment and maintaining and troubleshooting the execution of the reports within the environment.

Details

This is a list of standard Financial UBE reports that must run in a single-threaded job queue(s) defined in EnterpriseOne.

List of Standard Financial UBEs

System Code

System Name

UBE

UBE Name

Reason/Comments

03B

Accounts Receivable

R03B16A

Statistical History Refresh

When two distinct submissions of this UBE are waiting for one another to complete its processing of a table, a deadlock may occur. It is recommended that these two processes are not run concurrently.

04

Accounts Payable

R04571

A/P Auto Payments - Printer Driver

When two distinct submissions of this UBE are waiting for one another to complete its processing of a table, a deadlock may occur. It is recommended that these two processes are not run concurrently.

Duplicate check numbers may be assigned because sequential numbers from a table are used. All payment formats share this limitation.

04

Accounts Payable

R04575

A/P Auto Payments - Update Driver

When two distinct submissions of this UBE are waiting for one another to complete its processing of a table, a deadlock may occur. It is recommended that these two processes are not run concurrently.

Duplicate internal payment number may be assigned because sequential numbers from a table are used.

09

General Ledger

R093021

Indexed Allocations

When two distinct submissions of this UBE are waiting for one another to complete its processing of a table, a deadlock may occur. It is recommended that these two processes are not run concurrently.

10

General Accounting

R10861

Delete Prior Consolidation program

Clears the account balances from the F0901 and F0902 tables so that when you run subsequent consolidations, the balances do not include amounts from previous consolidations. This program also deletes prior consolidation records from the F0911 table if journal entries were created to consolidated accounts.

10

General Accounting

R10862

Refresh Consolidation program

This program creates additional records in the F0902 table for the fictitious business units, accounts, and account balances within the fictitious company that you specify in the processing options. But, if you do not delete the information in the consolidation database before you run a new consolidation, the system displays an error message that balances exist, and you must run the R10861.

Special Considerations:

This is a list of UBE reports that should not be run at the same time in EnterpriseOne Financials when another instance of a different UBE report is running. The explanation is provided within the following table.

System Code

System Name

UBE

UBE Name

UBE to NOT run concurrently

UBE Name

Reason/Comments

03B

Accounts Receivable

R03B525

Credit Analysis Refresh

R03B16A

Statistical History Refresh

Some of the tables updated by R03B525 are the same tables updated by the R03B16A. It is recommended that these two processes are not run concurrently.

03B

Accounts Receivable

R03B672

Draft Remittance

R03B16A

Statistical History Refresh

Some of the tables updated by R03B672 are the same tables updated by the R03B16A. It is recommended that these two processes are not run concurrently.

03B

Accounts Receivable

R03B671

A/R Batch Draft Creation

R03B16A

Statistical History Refresh

Some of the tables updated by R03B671 are the same tables updated by the R03B16A. It is recommended that these two processes are not run concurrently.

03B

Accounts Receivable

R03B16A

Statistical History Refresh

R03B525
R15105
R03B50
R03B671
R03B8101
R03B672
R15199

Some of the tables updated by R03B16A are the same tables updated by the R03B525, R15105, R03B50, R03B671, R03B8101, R03B672 and R15199. It is recommended that these processes are not run concurrently.

03B

Accounts Receivable

R03B551

Update Receipts Register

R03B16A

Statistical History Refresh

Some of the tables updated by R03B551 are the same tables updated by the R03B16A. It is recommended that these two processes are not run concurrently.

03B

Accounts Receivable

R03B50

Apply Receipts to Invoices

R03B16A

Statistical History Refresh

Some of the tables updated by R03B50 are the same tables updated by the R03B16A. It is recommended that these two processes are not run concurrently.

03B

Accounts Receivable

R03B8101

Recycle Recurring Invoices

R03B16A

Statistical History Refresh

Some of the tables updated by R03B8101 are the same tables updated by the R03B16A. It is recommended that these two processes are not run concurrently.

15

Real Estate

R15105

Revenue Fee Generation

R03B16A

Statistical
History
Refresh

Some of the tables updated by R15105 are the same tables updated by the R03B16A. It is recommended that these two processes are not run concurrently.

15

Real Estate

R15199

Post Invoices / Vouchers

R03B16A

Statistical
History
Refresh

Some of the tables updated by R15199 are the same tables updated by the R03B16A. It is recommended that these two processes are not run concurrently.