Original ITEM_EFFECTIVE_DT Retained During Payment Swapping Creates an Issue with Accounting Lines Created
Last updated on MAY 04, 2018
Applies to:PeopleSoft Enterprise CS Student Financials - Version 9 to 9.2 [Release 9]
Information in this document applies to any platform.
On Campus Solutions the original ITEM_LINE_SF.ITEM_EFFECTIVE_DT is used when a credit swaps from one account type to another. There may be several lines, each with a unique line sequences for the same item number on ITEM_LINE_SF. An increase in the credit amount may have a different ITEM_LINE_SF.ITEM_EFFECTIVE_DT. The accounting lines created for the increases, with an ITEM_EFFECTIVE_DT representative of when the increase occurred, are for the correct accounting period. However, the accounting lines created when the payment swaps, utilizing the original ITEM_LINE_SF.ITEM_EFFECTIVE_DT, are often in a prior accounting period.
Payment swapping from the item number after an increase in the amount, evidenced by an increase in the amount on ITEM_LINE_SF, uses the original ITEM_EFFECTIVE_DT to be used on accounting lines for any excess amount.
The ITEM_EFFECTIVE_DT of the most recent posting to the credit item should be retained for accounting lines for the excess.
The issue can be reproduced at will with the following steps:
1. Post an increase amount for a credit. The credit item was originally posted to the account on an earlier date;
3. Payment swapping occurs;
3. The reduction row on ITEM_LINE_SF uses the original item effective date and not an effective date reflective of the date the transaction occurred;
4. Upon posting to the new account type, the ITEM_LINE_SF.ITEM_EFFECTIVE_DT has the original item effective date of the credit;
5. Accounting lines for the transactions for the reversal and repost reflect an accounting date in the past.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms