QA Validation Error when Bill To, Sold To and Install At sites have different sites from different parties
Last updated on MAY 23, 2017
Applies to:Oracle Lease and Finance Management - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version,
When attempting to book a lease contract where Bill To, Sold To and Install At sites have different sites from different parties, QA Validation errors with the following:
Check Functional Constraints,
For Asset Number MX4090144 and Serial Number MX4090144, the party (XXXXXXX)
defined on the contract does not match the party (YYYYYYY) in Install Base. Please select a valid Serial Number.
This failure only occurs when Bill To, Sold To and Install At sites have different sites from different parties. There are no issue when Bill To and Sold To are same but Install At is different.
There is relationship defined in all three parties but contract creation still fails. The service contract gets created without error but OLFM does not.
The issue can be reproduced at will with the following steps:
Sold To (Signing) Customer : YYYYYYY
Bill To Customer: XXXXXXX
Install At Customer: ZZZZZZZ
1. Create Sales Order
2. Create Receipt (creates IB instance)
3. Complete ship Confirm (updates IB instance to the customer name)
4. Create Lease Contract through Interface table and try to book the contract.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms