My Oracle Support Banner

R12: AP: Payment Address Getting Populated in AP_CHECKS_ALL For Employee Quick Payments (Doc ID 1308167.1)

Last updated on SEPTEMBER 24, 2021

Applies to:

Oracle Payables - Version 12.0.4 and later
Information in this document applies to any platform.
APXPAWKB.fmb


Symptoms

When submitting a Payment Process Requst (PPR) for an employee, the 'Payment Address' column is populated, and can be seen in the Payment Workbench afterward. The data in AP_checks_all table includes the payment address columns such as adress1, address2, city, state, etc.

But if a user creates a Quick Payment from the Payments Workbench, the data for address
columns is not populated.

According to Bug 9037499, it is intended functionality that the Payment Address should not be populated in the Payment workbench due to the Safe Harbour Regulation Act.   So when making a payment thru the Payments Manager, the behavior should be the same -- the AP_checks_all table should not be populated with the employee's address information.

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
Cause
Solution
 Standard Patching Process
 Patch Wizard
 Have more questions?
References


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