My Oracle Support Banner

Population Update of Payment Period End Dates - SFA_PAYPR_END_DT on LOAN_DISBMNT and PELL_PAYPR_END_DT on PELL_DISBMNT - Cannot be Peformed Using Population Select as the Fields Were not Added to SFA_PU_LDSB_BND and SFA_PU_PDSB_BND (Doc ID 2874840.1)

Last updated on JANUARY 25, 2024

Applies to:

PeopleSoft Enterprise CS Financial Aid - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When using Population Update to update the Payment Period End Date fields -  SFA_PAYPR_END_DT on LOAN_DISBMNT and/or  PELL_PAYPR_END_DT on PELL_DISMNT - the fields can only be updated using values specified in the 'Select Fields to Update' section of the run control.

The expectation is that Population Selection should also be an option for updating the fields, as that is the case for other fields on the LOAN_DISBMNT and PELL_DISMNT, including the payment period start date fields. However, because SFA_PAYPR_END_DT and PELL_PAYPR_END_DT were not added to the respective bind records SFA_PU_LDSB_BND and SFA_PU_PDSB_BND, the fields cannot be updated using Population Selection results.

The issue can be reproduced with the following steps, which are given for LOAN_DISBMNT; the same equivalent steps can be performed also for PELL_DISBMNT.

  1. On Set Up SACR > System Administration > Utilities > Population Update > Population Update Setup > Population Update Setup, add record for LOAN_DISBMNT.
  2. In the field dropdown, choose SFA_PAYPR_END_DT.
  3. On Set Up SACR > System Administration > Utilities > Population Update > Population Update Process > Population Selection Update, choose LOAN_DISBMNT.
  4. In Population selection section, choose PSquery, click magnifying glass and choose CS_SFA_PU_LOAN_DISB.
  5. In query manager, open the query CS_SFA_PU_LOAN_DISB, and expand the SFA_PU_LDSB_BND record on the Query tab.
  6. Note that the 10 previous updateable fields, including SFA_PAYPR_STRT_DT, are on the record, but SFA_PAYPR_END_DT is not.

Changes

 The issue is observed after applying the fix for <Bug 34008594>, which delivered the changes to Population Update to include the two new fields.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.