EEBI 9.2: Customer No Longer Has Ship To, Sold To, nor Correspondence Primary Addresses After Deleting Billing Address From eBill Payment
(Doc ID 2792577.1)
Last updated on JULY 21, 2021
Applies to:PeopleSoft Enterprise SCM eBill Payment - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
A problem has been detected in the Customer Portal eBill Payment module, when a Contact User has deleted what had been the Primary Billing Address (Bill To, Ship To, Sold To, and Correspondence Address) for a Customer, after defining a new Address as the Primary one. This leaves the new Customer Address as the Primary Bill To, but not for Ship To, Sold To, nor Correspondence Address.
As such, the old deleted Address still has the Primary flag selected on Ship To and Sold To, and Correspondence Address selected, but has a Status of INACTIVE.
1.- Have a Customer defined with one single Address Location, set as Primary for Bill To, Ship To, Sold To, and Correspondence
2.- Have a Contact defined for this Customer
3.- Get the Contact User log into the CUSTOMER Portal, and access the Account Settings under eBill Payment module
4.- Click on Billing Address section, and confirm that the system lists the Customer's Address Location existing, and flagged as Primary
5.- Have the User create a NEW Billing Address, with all needed fields (Address 1, Address 2, Postal, City, State, etc...), and mark it as PRIMARY
6.- Confirm that the old existing Address is no longer defined as Primary. Open it, and click on DELETE button.
7.- Save the changes at this stage
8.- Log as User ID VP1 into the EMPLOYEE Portal, and navigate to the Customer General Information main page, to see that:
a.- The old existing Address has a new Effective Date row with today's date, and a Status of INACTIVE. While this is expected, what is not, is that the Ship To, and Sold To PRIMARY flags are still selected, as well as Correspondence Address flag, for this INACTIVE Address now
b.- The new Address entered by the Contact has also an Effective Date row, which is correct, and a Status of ACTIVE, which is also correct, and the Bill To and Primary flags selected, which is also correct. However, the Ship To, and Sold To Primary flags are NOT selected, and neither is the Correspondence Address flag.
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
When trying to create new transactions, or further process existing ones, for this one Customer, on other FSCM modules, issues will arise as Users cannot select, or the system cannot find, a valid and active Ship To, Sold To, or Correspondence Address.
When a Contact User deletes in eBill Payment, the Billing Address that is flagged as Primary for Ship To, Sold To, and Correspondence, the system should then set the other existing Billing Address flagged as Bill To Primary, as the Primary as well for Ship To, Sold To, and Correspondence. Or if not, allow the Contact to define which of the existing Addresses should qualify for that in case there would still be multiple ones left.
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