PeopleSoft Products That Use Entry Events
Each PeopleSoft product uses different entry event source transaction definitions, processes, steps, and codes. Some products require that you perform additional activities to use entry events.
You normally enter entry event codes into product documents on the distribution line. The entry event codes that appear within each product depend on the processes that are set up for the codes.
The following applications use entry events:
-
General Ledger.
-
Purchasing.
-
Payables.
-
Receivables.
-
Billing.
-
Project Costing.
Entry event transactions do not need to be associated with Commitment Control budgeting, with the following exceptions:
-
Entry events used in General Ledger budget adjustments that adjust preencumbrance, encumbrance, or collected revenue amounts for specific Commitment Control budgets.
-
Entry events used in Project Costing budgets that post project budget amounts for specific Commitment Control budgets.
-
Entry events used in Purchasing for requisitions and POs that are set up to account for the preencumbrance and encumbrance amounts in Commitment Control budgeting.
Note:
The system loads all Billing entry events into Receivables, where they are processed for entry event generation.
For each product, the following table lists:
-
Transaction types that use entry events.
-
Predefined entry event source transaction definitions.
-
Predefined entry event processes.
-
Additional setup requirements.
| Product or Feature | Transaction Types | Predefined Definitions for Entry Event Source Transactions | Predefined Entry Event Processes | Additional Setup Requirements |
|---|---|---|---|---|
|
Project Costing |
Project budgets |
PC_BUDGET (create control budget) |
PCBUDG (PC Budget Processing) To use entry events to create additional debit and credit entries for Project Costing budgets, the PeopleSoft system delivers the PC Budgets process with the following steps:
However, you might need to modify, add, or delete the steps depending on the budget ledger names and budget ledger group names. |
The budget plan must be saved, finalized, and successfully budget-checked before the Entry Event Generator process can create additional accounting entries. The Project Costing Budget Entry Event Interface Processor (PC_TO_EE) calls the Entry Event Generator (FS_EVENTGEN) to process Project Costing budget data to generate supplemental accounting entries, and support inquiry drill down to Project Costing source data. |
|
Billing. |
Billing. (All entry events used in Billing are loaded into Receivables where they are processed for entry event generation. Refer to information for Receivables.) Billing transactions use entry events:
|
Receivables source definitions. |
ARUPDATE (AR Update process). |
None. |
|
General Ledger. |
|
|
|
See PeopleSoft Commitment Control: Setting Up Budget Journal Entry Event Codes. |
|
Commitment Control feature. Note: You must use General Ledger to use the Commitment Control feature. |
|
|
BUDG (Budgets process). Note: To use entry events to create Commitment Control budget journals, the PeopleSoft system delivers the Budgets process with the following steps; however, you may need to modify, add, or delete the steps depending on the budget ledger names and budget ledger group names:
|
See PeopleSoft Commitment Control: Setting Up Budget Journal Entry Event Codes. |
|
|
|
|
|
|
|
Payables. |
|
|
|
None. |
|
Purchasing. |
|
|
|
Select to access the Control Budget Options page. Select the Entries Must Balance check box. Select to access the Offsets page. Set up offset accounts for the commitment control detail ledger group specified on the Ledgers For A Unit — Commitment Control Options page. For the source transaction type, select the appropriate account:
|
|
|
|
|
|
|
|
Receivables and Billing. |
|
|
|
Set up an entry event code containing the ARUPDATE process to enable you to enter and process entry events on the item distribution line for items. Set up an entry event code containing the ARDIRJRNL process to enter and process entry event codes as a direct journal entry for payments. Set up an entry event code containing the ARUPDATE process to enter and process entry event codes on the billing distribution line for invoices. |