Understanding the Indexed Computations Compute & Print Program

After you review the indexed allocations and determine that they are correct, run the Indexed Computations Compute & Print program (R093021).

When you run this program in proof mode, the system prints a report that shows the entries that it creates in final mode. Review the report to determine whether to make any changes to the allocation before running the program in final mode.

In final mode, the system:

  • Reads balances or transactions, based on the allocation method, from one or more accounts.

  • Multiplies each balance or transaction by the specified rate index.

  • Creates journal entries with batch type D in the F0911 table.

    For the balance allocation method, the system creates journal entries based on the balance of an account or a range of accounts. For the transaction allocation method, the system creates journal entries in a one-to-one ratio with the transactions that it reads.

  • Calculates an offset to balance the resulting journal entries, if needed, and distributes the offset to a contra/clearing account.

  • Increases the general ledger date incrementally according to the recurring frequency for the allocation, which ensures that the allocation is ready for future processing.

  • For the update allocation method, updates balances only in the F0902 table for ledger types other than AA.

  • Prints the Indexed Computations Journal report.

    This report lists detailed allocation information and errors, such as invalid accounts and entries posted before cutoff (PBCO). Invalid accounts appear with *** on the report.

You should create different versions of the Indexed Computations Compute & Print program for various recurring frequencies and for specific companies and specific document types. This allows you to include specific groups of allocations.

After you run this program in final mode, review and post the journal entries.

Note: When you run the Indexed Computations Compute and Print report, the system displays an error if you try to rerun a voided transaction. To avoid this error, you must revise the doc number, doc type, or G/L date on the allocation and then rerun the program to create a new document.