R12: AP: "ERROR: After call to Check_Valid_Party_ID" When Trying To Create A Non-Employee AP Supplier Linked To A PERSON-type Party AR customer.
(Doc ID 2534578.1)
Last updated on JANUARY 03, 2023
Applies to:
Oracle Payables - Version 12.2.7 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.7 version, Supplier Issues
Unable to create link a new Non-Employee AP supplier to a PERSON-type party AR customer.
The AP_VENDOR_PUB_PKG.Check_Valid_Party_Id Unable to create Vendor for a defined Customer / TCA Party.
FND Debug Log messages show the following
...
AP.PLSQL.AP_VENDOR_PUB_PKGValidate_Vendor Call to Validate payee
AP.PLSQL.AP_VENDOR_PUB_PKG Call to Validate party_id
AP.PLSQL.AP_VENDOR_PUB_PKG.Check_Valid_Party_Id Begin Check_Valid_Party_Id API
AP.PLSQL.AP_VENDOR_PUB_PKG.Check_Valid_Party_Id Validate Party_id for Non-Employee Type Supplier
AP.PLSQL.AP_VENDOR_PUB_PKG.Check_Valid_Party_Id Invalid Party_ID. For a Non-Employee Type Supplier, PARTY_ID cannot be of type PERSON
AP.PLSQL.AP_VENDOR_PUB_PKG.Check_Valid_Party_Id End Check_Valid_Party_Id API
AP.PLSQL.AP_VENDOR_PUB_PKGValidate_Vendor ERROR: After call to Check_Valid_Party_ID(p_party_id... Parameters: party_id: 11532053 p_employee: N
AP.PLSQL.AP_VENDOR_PUB_PKGValidate_Vendor Call to Validate vendor number
...
AP.PLSQL.AP_VENDOR_PUB_PKGValidate_Vendor Call to Validate payee
AP.PLSQL.AP_VENDOR_PUB_PKG Call to Validate party_id
AP.PLSQL.AP_VENDOR_PUB_PKG.Check_Valid_Party_Id Begin Check_Valid_Party_Id API
AP.PLSQL.AP_VENDOR_PUB_PKG.Check_Valid_Party_Id Validate Party_id for Non-Employee Type Supplier
AP.PLSQL.AP_VENDOR_PUB_PKG.Check_Valid_Party_Id Invalid Party_ID. For a Non-Employee Type Supplier, PARTY_ID cannot be of type PERSON
AP.PLSQL.AP_VENDOR_PUB_PKG.Check_Valid_Party_Id End Check_Valid_Party_Id API
AP.PLSQL.AP_VENDOR_PUB_PKGValidate_Vendor ERROR: After call to Check_Valid_Party_ID(p_party_id... Parameters: party_id: 11532053 p_employee: N
AP.PLSQL.AP_VENDOR_PUB_PKGValidate_Vendor Call to Validate vendor number
...
Changes
This works well in Release 12.1.3 but fail to process after upgrade to Release 12.2.7.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |