Partnership Cutback Transaction Generation GL430

This process generates cutback entries on a general partner's books from a specified partnership company. Entries are created from the partnership's unposted_transaction_master. You can run it in 'F'orecast or 'A'ctual mode.

In order to run this process, you must have already set up tables that are used to determine processing sequence, companies, accounts, and percentages for generation of cutback entries.

In 'F'orecast mode, the transactions are generated to a temporary file where they can be reviewed by running Partnership Cutback Analysis (GL440) and Partnership Cutback Generated Transactions (GL474). These reports allow you to analyze the effect of 'A'ctual mode processing before running in 'A'ctual mode. If appropriate, you can then modify the master file data in Partnership Cutback Master (GL400), Partnership Cutback Account Control (GL410), or Partnership Cutback Percent Master (GL420) before processing in the 'A'ctual mode. You can run forecasts any number of times before doing the actual run.

In 'F'orecast mode, all transactions are created on the ptr_cutback_utm_forecast file that is used for the review reports. This allows you to review the entries before the actual entries are generated.

In 'A'ctual mode all transactions are created on the unposted_transaction_master file and all transactions used to create those items are flagged with a date indicating that the cutbacks have been completed for that transaction. These UTM transactions are now eligible for System Batch Posting (GL210). You can also use the GL440 and GL474 reports to review actual transactions generated.

If the process encounters an account in the partnership company that does not have a corresponding cutback entry set up, or if it tries to process an account class (for percent type 2) or location (for percent type 4) with no associated cutback percentage, the program creates an error report and skips the updates for this transaction. The error can then be corrected and the process rerun to capture the skipped transactions.

The cutback processing can be run at any time. Only those transactions from the specified partnership companies that have not previously been processed are selected. Consequently, cutback processing is independent of particular sequencing in overall posting. The only requirement is that all transactions be processed by the cutback routine prior to running month-end financial reports, so that the general partner's interest is properly reflected on its books.