Primary Ship-to Site Not Correctly Defaulted On Transaction UI When Ship-to Site Changed At Customer Account Level
(Doc ID 1995576.1)
Last updated on APRIL 03, 2019
Applies to:Oracle Fusion Receivables Cloud Service - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Qn1:On : 220.127.116.11.0 version, Bill Customers-Create and Process Bill
Customer has 3 sites, one designated as primary for both bill-to and ship-to. A third site has been end-dated and its sites deleted. When you create an invoice, the ship-to site that is being defaulted pertains to the third site that has been end-dated without existing sites. It is also tagged as primary in the LOV. Why this is happening?
Qn2:On : 18.104.22.168.0 version, Bill Customers-Create and Process Bill
Please provide the navigation to view the Party site where it is designated as primary? Also, wouldn't a definition at site level override definition at Party level?
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