UCM Transaction Manager and PubSub Uses BC View Mode
Last updated on DECEMBER 22, 2015
Applies to:Siebel Universal Customer Master - Version 184.108.40.206 SIA  and later
Information in this document applies to any platform.
Generally UCM is used with one Organization and one Position for all the records.
If different positions are used in UCM records and an incoming request is processed with another position the process will fail once UCM Transaction Manager and Publish/Subscribe process use BC visibility (BusComp View Mode) in its queries.
For UCM Batch Process for example it can result in an error like "SBL-IAI-00461: UCM Batch Manager: Invalid Match Id 1-7QA2 for AutoMatch" if an existing record is found.
For Publish/Subscribe process it will just not find the record and this won't be sent to external systems.
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