Entry Event Processing

After you set up entry event codes, you create the transaction or document and run the entry event processor based on the application's instructions. The order in which the entry event processor runs depends on the type of document or transaction that you process. Six methods of entry event processing exist:

  • Normal accounting transaction entry event processing.

  • PeopleSoft Purchasing document entry event processing.

  • Commitment Control budget journal entry event processing.

  • Commitment Control budget close entry event processing.

  • Commitment Control general ledger budget adjustment journal entry event processing.

  • Project Costing budget entry event processing.

Normal Accounting Transaction Entry Event Processing

Here are the steps for normal accounting transaction processing with entry events:

  1. You edit transaction lines as usual.

  2. The entry event processor runs and generates the additional accounting lines based on the procedures and steps that are set up for the entry event code.

  3. If the transactions are controlled by a budget, the budget processor runs to update the budget records.

  4. After all the accounting lines are generated, Journal Generator creates journals from the Payables, Receivables, and Billing transactions.

    Note:

    General Ledger automatically generates journal lines for online journal entry transactions.

  5. The system posts the journals to the respective ledgers in General Ledger.

PeopleSoft Purchasing Document Entry Event Processing

Accounting entries are normally neither generated nor posted for purchase requisitions and POs. However, if you use commitment-controlled budgets, the Commitment Control feature tracks purchase requisitions and POs as preencumbrances and encumbrances, respectively. You set up specific entry event codes to generate the preencumbrance and encumbrance accounting lines that the system eventually posts to the appropriate actuals ledgers in General Ledger.

Here are the steps for Purchasing document processing with entry events:

  1. You enter and edit the purchase requisition or PO.

  2. The budget processor runs and updates the preencumbrance or encumbrance budget record based on the purchasing document that you enter.

    Note:

    If the document is a purchase requisition, the preencumbrance amount is updated for a specific budget and the remaining amount of the budget is updated. If it is a PO and a preencumbrance amount was already created, the preencumbrance amount is liquidated and the encumbrance amount is updated.

  3. The entry event processor runs and generates accounting lines for the purchasing document based on the accounts that you set up in the entry event code.

  4. Journal Generator creates a journal from the accounting lines.

  5. The journal is posted to General Ledger.

Commitment Control Budget Journal Entry Event Processing

To process Commitment Control budget journals with entry events:

  1. Select Commitment Control, and then Budget Journals, and then Enter Budget Journals.

  2. Enter a commitment control budget journal and select the appropriate entry event code.

  3. Select Post Journal to edit and process the budget journal and run the entry event processor.

    When you post Commitment Control budget journals online, entry event transactions are created when the journal is posted and the Skip Entry Event Processing check box on the User Preferences - General Ledger page for this operator is not enabled. Similarly, when a Commitment Control budget journal is posted through batch processing, entry event transactions are created when the journal is posted unless the user selects the Skip Entry Event Processing check box. In both cases, if entry event processing is bypassed, you can run the Entry Event processor in batch mode.

Commitment Control Budget Close Entry Event Processing

To process Commitment Control budget close using entry events:

  1. Perform the Commitment Control Budget Close process.

  2. Run the Entry Event Processor to generate the accounting lines.

  3. Run Journal Generator to create the accounting journals.

  4. Post the journals to the actuals ledgers set up for the business unit.

See Using Entry Events with Commitment Control Budgets.

Commitment Control General Ledger Budget Adjustment Journal Entry Event Processing

To adjust a Commitment Control budget's preencumbrance, encumbrance, or collected revenue amount, you create a budget adjustment journal to update the amounts for the budget and use entry event codes to update the amounts for the appropriate actual ledger. The process is similar to the process for a Purchasing document; however, you do not adjust the original document in Purchasing.

To process Commitment Control budget adjustments with entry events:

  1. Create a journal entry and—depending on the type of adjustment that you need to make—select preencumbrance, encumbrance, or collected revenue as the Commitment Control amount type.

  2. Create the journal lines and select the entry event code for a budget adjustment journal.

  3. Save and then run Journal Edit online or using batch.

  4. Run budget checking to update the budget record for the adjustment.

    Note:

    For example, if it is an adjustment to an encumbrance amount, the amount of the encumbrance is updated along with the remaining amount of the budget.

  5. Run the entry event processor to generate the adjustment's accounting lines based on the entry event code.

  6. Run Journal Generator to generate the accounting journal.

  7. Post the journal to the appropriate ledger.

Project Costing Budget Entry Event Processing

To process entry events for project costing:

  1. Set entry event options on the Installation Options – Entry Event page for General Ledger.

    Note:

    The Project Costing budget uses the General Ledger Entry Event option to process entry events. Installation options of required or optional determine how the Project Costing Budget Entry Event Interface Processor (PC_TO_EE) is run.

  2. Establish commitment control budget definitions and setup entry event steps within the PC entry event processes, and codes.

    Note:

    When you define commitment control project budget definitions, make sure the PC Business Unit is another ChartField other than Project ID. Define a step for each ledger and ledger group combination that will impact Project Costing budgeting.

  3. On the Ledgers For A Unit - Commitment Control Options page, set the Entry Event Option for each commitment control ledger group that will be used in Project Costing budgets.

  4. Select the entry event codes that are applicable for your project costing budget rows on the Commitment Control Detail tab of the Project Budget Items - Adjust Budget Items page.

  5. Save, finalize, and successfully budget-check your budget plan.

The Project Costing Budget Entry Event Interface Processor (PC_TO_EE) initiates the Entry Event Generator (FS_EVENTGEN) to process Project Costing budget data and generate supplemental accounting entries that support entry event generation and inquiry drill down to the project costing source data.

The Project Costing Budget Entry Event Interface Processor (PC_TO_EE) can be run in two ways:

  • If entry events are specified as Required for the Commitment Control Ledger Group on the Ledgers For A Unit - Commitment Control Options page, the finalized budget plan initiates the Project Costing to Commitment Control Application Engine Budget Posting Interface process (PC_TO_KK) and after budgets are successfully posted to the ledger, the final step in the Project Costing to Commitment Control process is to automatically call the Project Costing Budget Entry Event Interface Processor (PC_TO_EE) process.

  • If the system fails to generate the entry event journal accounting entries, or if entry events are specified as Optional for the Commitment Control Ledger Group on the Ledgers For A Unit - Commitment Control Options page, you manually run the Project Costing Budget Entry Event Interface Processor process (PC_TO_EE) on the Entry Event Budgets run control page in Project Costing to reprocess budget entry events.