How Does the CheckNoMatch Property of a Multi-Value Link Affect How and When Foreign Key Values are Changed?
Last updated on DECEMBER 01, 2016
Applies to:Siebel Tools - Version 7.5.2  to 8.1.1  [Release V7 to V8]
Information in this document applies to any platform.
Area(s):Configuration - General
Release(s):V7 (Enterprise), V6 (Siebel 2000-Enterprise), V5 (Siebel 99-Enterprise), Version 4
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
Keywords:MVL, Foreign Key, CheckNoMatch, No Match Row Id, Check No Match
This document was previously published as Siebel FAQ 1232.
""Checked for relevance on 25-Nov-2013""
""Checked for relevance on 30-Jun-2015""
How Does the Check No Match Property of a Multi-Value Link Affect How and When Foreign Key Values are Changed?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms