Different Dispute_code By The API Ozf_resale_pub.start_process_iface In R12.1.2 And R12.2.5
(Doc ID 2300457.1)
Last updated on MARCH 07, 2019
Applies to:Oracle Trade Management - Version 12.2.5 and later
Information in this document applies to any platform.
On : 12.2.5 version, All Others
Different dispute_code by the api ozf_resale_pub.start_process_iface in R12.1.2 and R12.2.5
In R12.1.2 passing the hard code value 'NOTFOUND' to the column bill_to_party_name and getting the correct dispute code "OZF_BILL_TO_PARTY_MAP_MISS".
In R12.2.5, getting a different dispute code, ideally should get the dispute code OZF_BILL_TO_PARTY_MAP_MISS.
The issue can be reproduced at will with the following steps:
1. In 12.1.2, hard code 'NOTFOUND' to the column bill_to_party_name and getting right dispute code "OZF_BILL_TO_PARTY_MAP_MISS"
2. In 12.2.5, getting a different dispute code than expected
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