Last updated on SEPTEMBER 21, 2016
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9 to 9.2 [Release 9]
Information in this document applies to any platform.
This question is about Data Archive Manager for Accounts Receivable.
The process for pending item selection is finished (archive date 01-01-2010) and the archive table PS_AR_GROUP_CNTL_H has the correct number of rows.
Archive Selection SQL for GROUP_CONTROL:
%InsertSelectWithLongs(AR_GROUP_CNTL_H, GROUP_CONTROL A, PSARCH_ID = 'ARPEND', PSARCH_BATCHNUM = 0) FROM PS_GROUP_CONTROL A
WHERE A.ACCOUNTING_DT < %DATEIN('2010-01-01')
AND A.POST_STATUS = 'C'
AND ( A.GROUP_TYPE <> 'P'
OR ( A.GROUP_TYPE = 'P'
AND NOT EXISTS (SELECT B.DEPOSIT_BU
FROM PS_DEPOSIT_CONTROL B
WHERE B.DEPOSIT_BU = A.DEPOSIT_BU
AND B.DEPOSIT_ID = A.DEPOSIT_ID)))
However it's not clear why the data linked to a deposit is not selected.
PeopleBooks is showing the following order for archiving:
When archiving data, remove data in the following order (taking into consideration your removal or archive date requirements):
- Pending item data for completely posted groups.
- Payment data for completely posted deposits.
- Direct debit data for completed or rejected direct debits that are posted.
- Inactive conversation data.
- Inactive statement data.
- Inactive dunning data.
- Inactive overdue charge data.
- Closed action data.
- Closed posted item data.
- Inactive posted customer data.
- Inactive customer definition data.
It's expected the system NOT to look at this unless it's expected that we have to run the pending item selection again after archiving payments.
Are the steps in PeopleBooks incomplete, or is the order incorrect?
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