Prerequisites

Before using entry events in General Ledger, you must:

  1. Perform the normal setup activities for General Ledger and the Commitment Control feature.

  2. For General Ledger, in the Entry Event field on the Installation Options - Entry Event page, select either Optional or Required.

  3. Only for GLJEADJ - Commitment Control Adjustment Journals, enable the Commitment Control feature for General Ledger in the Enable Commitment Control group box on the Installation Options - Installed Products page.

  4. Select Allow GL Entry Event Bypass for selected users on the User Preferences - General Ledger page, if desired.

    This option enables specific users to bypass selecting entry event codes that are identified as required for General Ledger on the Installation Options - Entry Event page.

  5. Select Skip Entry Event Processing in the Budget Post Options group box for selected users on the User Preferences - General Ledger page, if desired.

    This option enables specific users to post a budget without running the Entry Event Processor Application Engine process (FS_EVENTGEN).

  6. Verify that the ledger group for entering journal entries with entry events (normally the actuals ledger group, which is named the Recording ledger group in the predefined data) is associated with the standard ledger group type.

    This is the only ledger group type that you can use to enter entry events for General Ledger journal entries.

    Note:

    If you plan to create multibook journals with entry events, make sure that all of the multibook ledgers are set up, that the ledger group type is set to standard, and that you select the Keep Ledgers in Sync check box on the Ledger Groups - Definition page.

  7. Refer to the documentation regarding the setup of the entry event codes for an organization based on the entry event source transactions and processes that are predefined for General Ledger.

See Application Fundamentals: Understanding Entry Events.

Note:

You can create your own entry event codes that use the predefined source transactions and processes; however, do not modify the predefined data.

Related Topics