Process Defaults - Application-Specific

These additional Process Defaults are included for this ERP application:

Process Defaults	Description
Journal posting - no table locks	Specify whether to launch a SQL job to prevent an exclusive table lock from being set on the journal table during mass journal posting. The default is 0 (do not launch). To launch the job, set it to 1. The job name is "JournalNoTableLock" + the current date and time. If the job fails for any reason, it stays in the job list, and users can view the job history in SQL to see any errors that occurred. If the job runs successfully, it deletes itself when it completes. It completes when the Posting Journals function becomes unlocked again. This happens at the end of journal posting. If this value is set to 1, then SQL Server Agent must be running on the database server.
Lock job items	Indicate whether job items are locked during certain operations. The default value is 0 (not used). If set to 1, operations such as releasing a job - which copies the BOM - and posting a job will lock all the item records in blocks according to the operation number. This prevents deadlocks on the item table when your bills of materials contain many items. Most companies probably will not use this option.

Process Defaults

Description

Journal posting - no table locks

Specify whether to launch a SQL job to prevent an exclusive table lock from being set on the journal table during mass journal posting. The default is 0 (do not launch). To launch the job, set it to 1.

The job name is "JournalNoTableLock" + the current date and time. If the job fails for any reason, it stays in the job list, and users can view the job history in SQL to see any errors that occurred. If the job runs successfully, it deletes itself when it completes. It completes when the Posting Journals function becomes unlocked again. This happens at the end of journal posting.

If this value is set to 1, then SQL Server Agent must be running on the database server.

Lock job items

Indicate whether job items are locked during certain operations. The default value is 0 (not used). If set to 1, operations such as releasing a job - which copies the BOM - and posting a job will lock all the item records in blocks according to the operation number. This prevents deadlocks on the item table when your bills of materials contain many items. Most companies probably will not use this option.