OOTB Edit Merge Feature Not Working For Positions (Doc ID 2026838.1)

Last updated on AUGUST 05, 2015

Applies to:

Siebel CRM - Version 8.1.1.8 [23012] and later
Information in this document applies to any platform.

Symptoms

On :  8.1.1.8 [23012] version, Client Functionality
Basically team tables (S_ORDER_POSTN and S_ACCNT_POSTN) are getting updated however the main tables are not getting updated with new position row IDs.

ERROR
-----------------------
NA


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Steps to recreate the problem on merging Positions

1. Create two Positions, two users:
  PostnA - UserA
  PostnB - UserB

2. Login as UserA and:-
  a. Create two Account (S_ORG_EXT) Party records
  b. Create an Order on each Account

3. Login as UserB and:
  a. Create two Account (S_ORG_EXT) Party records
  b. Create an Order on each Account

4. Navigate to the All views and verify that there are:-
  a. Four Accounts visible
  b. Four Orders visible

5. Navigate to the My views and verify that there are:-
  a. Two Accounts visible
  b. Two Orders visible

6. Login as Siebel Administrator and:-
  a. Navigate to "Administration Group -> Positions"
  b. Select PostnA and ctrl-select PostnB (so both are highlighted)
  c. On the Menu, click "Merge"
  d. Confirm that PostnA will be merged to PostnB (the order of selection determines the merge order)

7. Login as UserA and navigate to the All views, verify that there are:-
  a. Two Accounts visible
  b. Two Orders Visible

8. Login as UserB and navigate to the All views, verify that there are:
  a. The same two Accounts visible from #7 above
  b. The same two Orders visible from #7 above

9. Using SQL, verfiy the values of the Primary Position Id:
  a. Two Accounts reference PostnB
  b. Two Accounts have a bad PR_POSTN_ID
  c. Two Orders reference PostnB
  d. Two Orders have a bad PR_POSTN_ID

10. Using SQL, verify that there are:
  a. All four Accounts have entries in S_ACCNT_POSTN referencing PostnB
  b. All four Orders have entries in S_ORDER_POSTN referencing PostnB

11. Using SQL, update the PR_POSTN_ID that is bad to reference PostnB  - this is just for testing purpose and it should not be performed in production.

12. Login as UserA and navigate to the All views, verify that there are now:-
  a. Four Accounts visible
  b. Four Orders Visible


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, records are not up to date

Cause

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