EAR 9.2: PS_PAYMENT_WS_ATT.PAYMENT_ID Becomes Out Of Sync From PS_PAYMENT.PAYMENT_ID If Value Changed Online After Uploading Attachments

Last updated on JUNE 15, 2017

Applies to:

Symptoms

ISSUE:

A problem has been detected with Record Field PS_PAYMENT_WS_ATT.PAYMENT_ID not being properly updated if the Payment ID value of an existing transaction, that already had uploaded attachments, gets modified by the user. As a result, the system creates an out of sync problem between Record Fields PS_PAYMENT.PAYMENT_ID, and PS_PAYMENT_WS_ATT.PAYMENT_ID, which generates orphan rows in PS_PAYMENT_WS_ATT Table.

REPLICATION STEPS:

     1.- Log into the FSCM Online Application as User ID VP1
     2.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > File Attachments > Administer File Attachments
     3.- Ensure that we have Pick Active Server 3, with Type DB, and pointing to Server/Record Name/URL Id = PV_ATT_DB_SRV
     4.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
     5.- Create a new Regular Deposit Group, with one Payment instance, and mark it as Journal Directly
     6.- Proceed to upload a new file as an Attachment for this Payment transaction, and save the changes
     7.- Query PS_PAYMENT, and PS_PAYMENT_WS_ATT Records, and ensure that their Field PAYMENT_ID are insync on both Tables
     8.- Navigate to: Accounts Receivable > Payments > Review Payments > All Payments
     9.- Open the newly created Payment, and confirm that the Attachment is listed properly, and downloadable
     10.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
     11.- Open the Deposit Group, go to the Payments tab, modify the Payment ID value to something else, and save the changes
     12.- Query PS_PAYMENT.PAYMENT_ID, and confirm that the value stored is the newly updated one
     13.- Query PS_PAYMENT_WS_ATT.PAYMENT_ID, and confirm that the value is still the old one, causing an un-sync problem with the involved transaction
     14.- Navigate to: Accounts Receivable > Payments > Review Payments > All Payments
     15.- Open the affected Payment, and confirm that the Attachment link is not displaying no files available

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

ACTUAL RESULT:

The values stored within Record Fields PS_PAYMENT.PAYMENT_ID and PS_PAYMENT_WS_ATT.PAYMENT_ID become out of sync, causing the link between Payment transaction and its loaded attachments to be broken. Users are unable to download, and review the Payment documentation.

EXPECTED BEHAVIOR:

The value stored within Record Field PS_PAYMENT_WS_ATT.PAYMENT_ID should always be updated while the Payment ID field is editable, and should a User modify its value.

Cause