Product Master Data Management (MDM) Process Integration Pack (PIP): Overrided Item if EXCLUDED in PIM still shows up in Siebel after Publishing (Doc ID 1677302.1)

Last updated on JANUARY 30, 2022

Applies to:

Symptoms

Product MDM PIP - > Siebel Option - Version 11.x (Where x is 1 OR 2)

Current Behavior:

Exclusion of an Overridden Item in PIM and publishing to Siebel will STILL Keep that excluded item in the Siebel Webservice Call Payload
Thus showing a difference in the PIM and Siebel Item Structures

Steps to Reproduce
1. Structure created in PIM as follows

Test_Package_20131205   ==> promotion
 Test_SB_20131205           == Root Product
   Test_OG_20131205          ==> Option Group /Relationship
     Test_Item_20131205_1     ==> Child Item/Domain Product
     Test_Item_20131205_2
     Test_Item_20131205_3

Case 1:
Ensure to have Min, Max Default Cardinality for Child items - 0,1,0 and for Option Group (OG) : 0,2,0

Test_Package_20131205   ==> promotion
 Test_SB_20131205           == Root Product
   Test_OG_20131205          ==> Option Group /Relationship    -- Min Cardinality - 0, Max Card - 2, Default Card - 0
     Test_Item_20131205_1     ==> Child Item/Domain Product    -- Min Cardinality - 0, Max Card - 1, Default Card - 0
     Test_Item_20131205_2                                      -- Min Cardinality - 0, Max Card - 1, Default Card - 0
     Test_Item_20131205_3                                      -- Min Cardinality - 0, Max Card - 1, Default Card - 0
 
Publish Structure to Siebel

Expected Result: All three child items (domain products) -Test_Item_20131205_1/Test_Item_20131205_2/  Test_Item_20131205_3 - in short, Child Item  1,2 & 3 - should be created in Siebel.
Actual Result: Same as expected.

Case 2:
Exclude Child Item 3 . Specify Override Cardinality = 1 for  the included item -- child item  1 & 2 -  and Exclude Child Item 3 from  workbench.

Test_Package_20131205   ==> promotion
 Test_SB_20131205           == Root Product
   Test_OG_20131205          ==> Option Group /Relationship
     Test_Item_20131205_1     ==> Child Item/Domain Product   -- Override Cardinality = 1
     Test_Item_20131205_2                                     -- Override Cardinality = 1
     Test_Item_20131205_3                                     -- Exclude

Publish Structure to siebel

Expected Result: Child Item 3 should be deleted from siebel and Child Item 1 & 2 should exist
Actual Result: Same as Expected

Case 3:
Exclude Child Item 2, by blanking out/removing its Override Cardinality .
Exclude from PIM workbench

Test_Package_20131205   ==> promotion
 Test_SB_20131205           == Root Product
   Test_OG_20131205          ==> Option Group /Relationship
     Test_Item_20131205_1     ==> Child Item/Domain Product   -- Override Cardinality = 1
     Test_Item_20131205_2                                     -- Blankout Override Cardinality set in Case # 2 & Exclude in PIM
     Test_Item_20131205_3                                     -- Already in Excluded in Case # 2

and publish structure to Siebel.

Expected Result: Child Item 2 should be deleted from siebel and Child Item 1  should exist
Actual Result :  
             Child Item 2 still exists in Siebel with its Default Quantity blanked out. ==> This Item shouldn't be there in Siebel
             Child Item 1 has Default Quantity = 1 ==> This is fine as this Item has Override Cardinality as 1.
            

Expected Behavior:
Overrided Item when Excluded in PIM, shouldn't show up in Siebel after Synchronization

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.