Error “Clause XXXXX has transactional binds from a different source than the specified Source Transaction. (10420,347)” Triggered when Try to Add a New Clause to a Configuration
(Doc ID 2910451.1)
Last updated on DECEMBER 23, 2022
Applies to:
PeopleSoft Enterprise SCM Supplier Contract Management - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
When try to add a new clause to a configuration, the system returns error
Steps to Reproduce the Issue:
1. Create new Clauses
Navigation Supplier Contracts > Manage Contract Library > Clause Definition
Add Description,
Full text = Vendor Name: %%VENDOR_NAME%%
Press Submit for Approval> and Save
Clause is approved and ready to be used.
2. Add a new Document Configurator definition for Source Transaction = Multiple Sources
Navigation Supplier Contracts > Manage Contract Library > Document Configurator,
Add Description,
Select in <Applicable Sources > section:
Adhoc = Y
Purchasing Contract = Y and press <Save>
3. Add the clause created previously using Insert plus + icon
4. Pres save after approve doc config
Error (10420,347) is triggered even the clause was removed.
If leave the page, it can be noticed the Configurator is not saved as expected.
5. Try to add a clause created previously to TESTMULTISRC configurator
It is triggered the same error < Clause CL_POITEMTABLE01 has transactional
binds from a different source than the specified Source Transaction.
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 |
Cause |
Solution |
References |