I would like to understand what's the reason for having the Product_Id, Cont_Id, Admin_Product_Id and Admin_Client_Id the ProductPartyRole table. If this table is used to establish the product to party relationship wouldn't it be sufficient to store the PRODUCT_EQUIV_ID( primary key of the ProductEquiv table ( thereby indirectly linking the PRODUCT_ID) ) and the CONT_EQUIV_ID ( Primary key of the ContEquiv table (thereby indirectly linking the CONT_ID) ? Are Admin_Product_Id and Admin_Client_Id added just to facilitate search?
Also why is Admin_Sys_Tp_Cd required in the ProductPartyRole table? what does it signify?
thanks & regards
This topic has been locked.
1 reply Latest Post - 2012-09-28T07:23:51Z by Sadagopan_Krishnamachari
Pinned topic Product Domain - Admin_Product_Id in both PartyProductRole&ProductEquiv
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-09-28T07:23:51Z at 2012-09-28T07:23:51Z by Sadagopan_Krishnamachari
Sadagopan_Krishnamachari 060000S1KR14 PostsACCEPTED ANSWER
Re: Product Domain - Admin_Product_Id in both PartyProductRole&ProductEquiv2012-09-28T07:23:51Z in response to Sadagopan_KrishnamachariI believe this provides the flexibility when the customer does not have one of the domains. So it could be possible that party domain has been used by the customer and hence there is no need of the Product model of MDM.