EIM and Updating PR_PER_ADDR_ID = NULL
(Doc ID 487716.1)
Last updated on SEPTEMBER 07, 2018
Applies to:Siebel Enterprise Integration Manager - Version 18.104.22.168 SIA  and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 22.214.171.124  Life Sci
Database: Oracle 126.96.36.199
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: IBM AIX 5L 5.2
This document was previously published as Siebel SR 38-1980624521.
We are using Pharma Address link to store our Addresses.The primary address in our implementation is stored on the S_POSTN_CON table in PR_ADDR_ID as per vanilla.We migrated our data from Siebel 6 to Siebel 7 just a couple of months back.When we migrated data, we populated PR_PER_ADDR_ID on S_CONTACT and PR_ADDR_ID on S_POSTN_CON using EIM_CONTACT1.Same value is stored in these 2 columns when data was loaded.Everything went fine until now.We figured out that when our users started deleting old addresses and putting new addresses on Contacts we found out that our Dynamic Assignment is not assigning Territories/Positions correctly.When we did our research we found out that Batch Assignment looks at PR_PER_ADDR_ID (S_CONTACT) and PR_ADDR_ID (S_POSTN_CON).When the users deletes an Address and puts in a new address this is only reflected on the PR_ADDR_ID on S_POSTN_CON but not on the PR_PER_ADDR_ID on S_CONTACT.And unfortunately Assignment Manager looks at this column before it actually looks at PR_ADDR_ID on S_POSTN_CON.So the only way to get around with this is to nullify the PR_ADDR_PER_ID so that Batch Assignment looks at PR_ADDR_ID on S_POSTN_CON.
The EIM process somehow doesnt reset the PR_PER_ADDR_ID using EIM_CONTACT1.When we created an Contact from the GUI and associate an Address we get No Match Row Id in the PR_PER_ADDR_ID.Can we update this column using EIM to No Match Row Id or NULL uisng EIM.
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