Receive Invalid RowIdField Data Error When Trying to Merge Two Duplicate Accounts Through Data Quality [ID

827943.1] Modified 01-JUN-2011 In this Document Symptoms Cause Solution Type PROBLEM Status MODERATED

Created from <SR 3-899036107> with ODMPlatforms: 1-914CU; This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:
Siebel Data Quality - Version: 7.5.3 [103] to 8.1.1.4 SIA [21225] - Release: V7 to V8 This problem can occur on any platform.

Symptoms

We encounter some issues when trying to merge 2 duplicated accounts record at the Firstlogic Account Duplicates Batch View. Sometimes we receive the following error: SBL-DAT-00499: Invalid RowIdField data. Please continue or ask your systems administrator to check your application configuration if the problem persists. Standard merge works fine after restoring the hierarchy.

Cause
Siebel provides two merge functionality. One is Standard Merge which is performed using the application level Edit menu item, and the other is Sequential Merge which is performed in Administration - Data Quality > Duplicate <Contact, Accounts or List Management>. > Resolution view, or in the pop-up applet for real-time deduplication. Both merge functionality will reassociate child records to the surviving record. Sequential Merge also update null fields in the surviving records if the merging record contains a value. Sequential Merge also allows you to specify the sequence order of multiple records being merged. When performing Standard Merge on an Account record, it was successfully merged. When performing Sequential Merge, the following error was observed for some records: SBL-DAT-00499: Invalid RowIdField data.

The cause of the issue has to do with Sequential Merge also updating null fields that in the surviving record, and implicit joins to extention table. For instance, S_ORG_EXT is an extension table with implicit join to S_PARTY in the Account BC. This means that the column PAR_ROW_ID of table S_ORG_EXT is a foreign key that holds the ROW_ID of S_PARTY. The error occurs because the merging record contains an entry in S_ORG_EXT whereas the surviving record does not. You will get the same error message in the UI if you try to update a field that is base on column in S_ORG_EXT, but that record does not have an entry for the record.

Solution
To correct the issue, you must populate the extension table for each record. For instance, if you have a record in S_PARTY with ROW_ID = '1-23OF'. In your extension table, there must also exist a row with column PAR_ROW_ID = '1-23OF'. The easiest solution is to populate these tables using EIM. Also note that the above mentions S_ORG_EXT as an extention table to S_PARTY in the Account BC. This is just one of many extention table that exist in the Account BC, so you will have to make sure for all extension table there is a row for the record in S_PARTY.

Related

Products

Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Data Quality

Keywords KM Errors SBL-DAT-00499 Back to top Rate this document

Article Rating Rate this document Excellent Good Poor Did this document help you? Comments

Yes No Just browsing How easy was it to find this document? Very easy Somewhat easy Not easy

Provide feedback for this article. Please use 'Contact Us' for other feedba

Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support. Cancel