Processing front end split for projects

Use this information to process front end splits on project contracts when no Finance Dimension 2 (FD2) is included on the finance code block. This list shows the reasons that FD2 may not exist on the finance code block:

  • When front end split is enabled on the FEG or on the contract after transactions are posted to the posting projects on the contract.
  • When transactions for features that are not included for the front end split must be split.
  1. Journalize the subsystem distributions.
  2. Global Ledger Journal Post. To quick-post one or more journal entries, use the Journals Released tab. To post several journal entries, you can schedule the posting in the Post Journals action.
  3. Generate Front End Split Distributions. This action is required for project contacts where the front end split feature is enabled. GL Transaction Detail records are split if Finance Dimension 2 is blank and new GL Transaction Detail records are created with the appropriate funding source. A record for each split is based on the Project Contract Funding Source priority, percentage, funding group, and funded amount.
    These actions occur as a result of the generate action:
    • The originating GL Transaction Detail records are reversed.
    • The billing and revenue fields are updated to processed on the original entry and reversing entry so that these transactions are not included when the Generate Project Invoice or the Recognize Revenue actions, or both are run.
    • A budget edit check is performed when allocating.
    • A GL Transaction Interface record is created for each split.
    • A journalize group is created.
    • The Interface Transactions action is run. Budget checks are performed before the GL Transaction Detail records are created.
  4. Correct the errors. Errors are denoted with a red alert on the Front End Split Results tab for the journal group. Correct the errors and reprocess the interface transactions action.
  5. Post the front end splits. Generating the front end splits creates a released journal. Post these transactions before indirect burdens or invoices are generated.
  6. Generate and Journalize Indirect Burdens actions. These actions are used to create and journalize indirect cost transactions. We recommend that you include the Finance Dimension 2 in the selection criteria. Post the indirect burden transactions before you generate invoices.
  7. Generate and Journalize Invoices actions. These actions are used to create project contract invoices and to journalize the distributions.