Integrity of data in Pending_dst and Item_dst tables in PeopleSoft v 9.0
My question is as follows:
We converted data into PeopleSoft, and in that effort some of the items were converted with only the Account chartfield being populated. It was later determined that based on combo edit rules and business rules, the other chartfields should have been populated (Operating Unit, Fund, Class, etc..). This was only applicable to our OA (On Account) transactions that had not been applied to open items.
When the decision was decided to update those chartfields via SQL, only the ITEM_DST table was updated. The Pending_DST table wasn't. Now those tables are out of sync. When future transactions are created with those OAs that were manipulated via SQL the system goes back to the PENDING_DST table and picks up the transaction that doesn't carry the additional chartfield data.
We converted data into PeopleSoft, and in that effort some of the items were converted with only the Account chartfield being populated. It was later determined that based on combo edit rules and business rules, the other chartfields should have been populated (Operating Unit, Fund, Class, etc..). This was only applicable to our OA (On Account) transactions that had not been applied to open items.
When the decision was decided to update those chartfields via SQL, only the ITEM_DST table was updated. The Pending_DST table wasn't. Now those tables are out of sync. When future transactions are created with those OAs that were manipulated via SQL the system goes back to the PENDING_DST table and picks up the transaction that doesn't carry the additional chartfield data.
0