Customer Workbench Issue: Inactivating an Identifying Party/Account Site Causes Corresponding Site Uses to Be Made Inactive But None of Remaining Active Sites and Uses are Marked as Primary
Last updated on AUGUST 04, 2016
Applies to:Oracle Receivables - Version 188.8.131.52 and later
Information in this document applies to any platform.
When you update the existing Primary/Identifying Site associated to a Party/Account and set it to Inactive, all the site use/business purpose associated to that inactivated site are also set to Inactive as expected. However, the Party/Account is now left without an Primary/Identifying Site because the inactivation does not take care of setting one of the other Sites as Primary.
Steps to Reproduce:
Responsibility: Receivables Manager
Navigation: Customers > Standard
- Query a customer that has multiple sites associated with it
- Pick the Primary Site and set it to Inactive and Save
- Re-query the customer, all the site uses associated to the site inactivated in step 2 are now also inactive - this is good.
- Notice however that there is no longer a Site marked as Primary - this is bad.
The reverse action also manifests an issue. If you pick a customer that already has an Inactive Site and you attempt to re-activate it and save your changes, When you re-query the customer the site remains inactive.
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