Using a Single Entry Event Code in Multiple Documents or Products

To use an entry event code in multiple documents or for multiple products, you must identify each process and its steps in the entry event code definition. Using the PeopleSoft procure-to-pay process as an example, you can enter an entry event code one time in the requisition document. It then flows through the entire process creating entry event transactions for each document. Before an entry event code can successfully move between documents and products, you first must set it up to run for each of the processes in the procure-to-pay cycle.

The PeopleSoft procure-to-pay cycle consists of several documents and processes. Entry event processing uses the following processes:

  • REQPOST

  • POPOST

  • VCHRPOST

  • PAYMENT

You must set up an entry event code and associate it with all four processes.

See Entry Event Code Definition Page.

Example of Defining One Entry Event Code to Use with Multiple PeopleSoft Applications

Here is an example of how to define an entry event code for multiple PeopleSoft applications:

  1. Set up the PROCURE entry event code.

    Term Definition

    Entry Event

    PROCURE

    Description

    Requisition to Cash Clearing

  2. In the Entry Event Process group box, add the REQPOST process.

    Term Definition

    Entry Event Process

    REQPOST

    Effective Date

    01/01/1900

    Status

    A

  3. In the Entry Event Step group box, add the REQPOST step.

    Term Definition

    Entry Event Step

    REQPOST

    Account

    696800 (example)

    Source Record Jrnl Template

    Not applicable (NA)

    Journal Template

    EE_PURCH

  4. In the Offset Accounts group box, add the preencumbrance and general expenses offset accounts.

    Term Definition

    DR/CR

    DR

    Account and Short Desc

    696700 (example) - Preenc Res

    DR/CR

    CR

    Account and Short Desc

    696500 (example) - GenExpOffs

  5. In the Entry Event Process group box, add the POPOST process.

    Term Definition

    Entry Event Process

    POPOST

    Effective Date

    01/01/1900

    Status

    A

  6. In the Entry Event Step group box, add the POPOST step.

    Term Definition

    Entry Event Step

    POPOST

    Account

    696800 (example)

    Source Record Jrnl Template

    Select if a source record journal template exists.

    Journal Template

    EE_PURCH

  7. In the Offset Accounts group box, add the encumbrance and general expenses offset accounts.

    Term Definition

    DR/CR, Account, and Short Desc

    DR, 696600 (example), Enc Res

    DR/CR, Account, and Short Desc

    CR, 696500 (example), GenExpOffs

  8. In the Entry Event Process group box, add the VCHRPOST process.

    Term Definition

    Entry Event Process

    VCHRPOST

    Effective Date

    01/01/1900

    Status

    A

  9. In the Entry Event Step group box, add the ACCRUAL step.

    Term Definition

    Entry Event Step

    ACCRUAL

    Account

    696800 (example)

    Source Record Jrnl Template

    Select this option.

    Journal Template

    NA

  10. In the Offset Accounts group box, add the general expenses and accounts payable offset accounts.

    Term Definition

    DR/CR, Account, and Short Desc

    DR, 696500 (example), GenExpOffs

    DR/CR, Account, and Short Desc

    CR, 200000 (example), Accts Paybl

  11. In the Entry Event Process group box, add the PAYMENT process.

    Term Definition

    Entry Event Process

    PAYMENT

    Effective Date

    01/01/1900

    Status

    A

  12. In the Entry Event Step group box, add the PAYMENT step.

    Term Definition

    Entry Event Step

    PAYMENT

    Account

    NA

    Source Record Jrnl Template

    Select this option.

    Journal Template

    NA

  13. In the Offset Accounts group box, add the accounts payable and bank disbursement offset accounts.

    Term Definition

    DR/CR, Account, and Short Desc

    DR, 20000 (example), Accts Paybl

    DR/CR, Account, and Short Desc

    CR. 10006 (example), UBANK Disb