On-demand Process Groups allow users to run processes directly from Accounts Payable and Accounts Receivable transaction entry pages. The Process Groups generally consist of logically-related and sequentially-ordered processes that a transaction might require

It is recommended to establish each user with the specific access associated with their job duties and is not recommended to simply copy one user's access to another user as this could lead to overallocation of access. However, there are situations where a group of staff within a single department all require the same access to perform similar work. In that case, the COPY function provides the ability to apply all Process Group definitions from one user to another without having to search and enter each Source Transaction and Process Group combination.

Local security administrators need to assess the users access needs individually. Some newer, and more inexperienced users may not need process groups, that would allow them to process transactions outside of batch processing. These newer users are probably limited to more of data entry type access and their transactions would be picked up when the batch processes ran, instead of running those directly on each transaction. It is important from an audit perspective to only allow transactional processing to the users that require that level of access and understand the impacts of those processes.

Navigation: NavBar > Navigator > Set Up Financials/Supply Chain > Common Definitions > User Preferences > Define User Preferences

On the Process Group page, ensure the following boxes are checked:

• Allow Processing: This controls if on-demand processing is enabled, then the user will be able to run certain batch processes from the transaction screens. For example, a user can execute batch processes such as Voucher Post, Journal Generator, and so on from the voucher entry page itself rather than navigating to a different page to run that particular process.
• Use Event Notification: Check the box to allow the ability to use Event Notification.

Source Transaction: indicates a specific system feature from the Receivable or Payable module. For example, the VOUCHER source transaction controls the processing options for the voucher entry function in Payable, while ARPAYWS controls the actions that a user can perform for Payment worksheets in the Receivable module.

In the Source Transaction section, click the Look Up (spy glass) icon and select the Source Transaction, for example: VOUCHER-Voucher Entry.

Process Group: indicates what level of privileges is granted to a user for a selected source transaction. For example, the following options (Process Groups) are related to payment worksheets: ARACTIONA (Do not post), ARACTIONL (Batch standard), ARACTIONN (Batch priority), ARPOST (Post now), ARPOSTGL (Post now through to GL). If the user needs to be able to post the payment worksheets to GL, then selecting the value ARPOSTGL in the Process Group field will provide the needed access.

In the Process Group section, click the Look Up (spy glass) icon and select the following values, clicking the Plus (+) symbol between each entry to open a new row. For example for the Source Transaction VOUCHER - Voucher Entry the following values are listed:

BUDGET_CHK- Budget Checking

MATCHING- Matching

PST_VCHR- All processes through Voucher Post

PST_VCHRGL- All processes through Journal Generate

Click the Plus (+) symbol by the Source Transaction field (see blue arrow) to open a new Source Transaction block.

Accounts Payable transactions can be processed in a batch, or you can process it on demand on the following pages:

In PeopleSoft Receivables a process group is not associated with a process; it is associated with a posting action. The posting action that is associated with a process group determines which processes to run, and when to run those processes.