Question on PeopleSoft AR requirement to unpost groups in order
Hi,
While I was there supporting PeopleSoft, I remember that we introduced code that would prevent a group (payment, transfer, or maintenance) from being unposted out of sequence. For ex, if an item has the following transactions:
1. Partial payment
2. Partial write off in maint WS
3. Transfer
PeopleSoft AR does NOT allow the unpost of transaction #2 before #3 is unposted.
However, I was thinking about this more and wondering what the original reason was for putting in this limit. Was there data corruption? It's been awhile and I could not recall the exact business reason as to why we placed these edits in place.
While I was there supporting PeopleSoft, I remember that we introduced code that would prevent a group (payment, transfer, or maintenance) from being unposted out of sequence. For ex, if an item has the following transactions:
1. Partial payment
2. Partial write off in maint WS
3. Transfer
PeopleSoft AR does NOT allow the unpost of transaction #2 before #3 is unposted.
However, I was thinking about this more and wondering what the original reason was for putting in this limit. Was there data corruption? It's been awhile and I could not recall the exact business reason as to why we placed these edits in place.
0