topic Data inconsistency in database view in Application Development and Automation Discussions

Data inconsistency in database view

former_member382013 — Thu, 08 May 2014 13:54:49 GMT

After Executing one database view, i m getting 22000 records. But as per the requirement after deleting the duplicate entries, only 800 records are there but customer is expecting more than 2800+ records. As I am new so don't know the initial approach.

Experts plz help...........

Re: Data inconsistency in database view

ThomasZloch — Fri, 09 May 2014 09:02:18 GMT

What do you mean with "executing a database view"?

What means "getting 22000 records"?

How are you deleting duplicate entries?

Where are the 800 records?

What is the requirement and what does the customer expect?

Please don't use SMS speak like "plz".

Thomas

Re: Data inconsistency in database view

former_member382013 — Sun, 11 May 2014 10:06:44 GMT

executing means clicking on contents
after clicking on contents 22000 records are coming
some records are same (that is one record is repeating 7 or 8 times)
as in point 3, after deleting the duplicate entries, only 800 records are there.
expected records are more than records coming. End user is expecting more than 2800 records
I will not use SMS speak like "plz".

Re: Data inconsistency in database view

Former Member — Sun, 11 May 2014 12:18:06 GMT

Hi Anand,

Is it custom database view?

If yes then show me the screenshot of database view created by you because duplicate entrries should not exist in database view.

Regards,

Sudeesh Soni

Re: Data inconsistency in database view

former_member382013 — Sun, 11 May 2014 14:18:17 GMT

hi Sudheesh.

screenshot for join conditions

screenshot of contents

thanks

Anand

Re: Data inconsistency in database view

Former Member — Sun, 11 May 2014 18:13:24 GMT

Hi Anand,

You need to keep a note that in database view try to mapped most of the table key fields with another table if not possible then give the not mapped field value in Selection condition.

Also, always mapped field MANDT as a 1st table condition in table join.

Please recheck your database view and incorporate above mentioned point, i hope it will give much more accurate result in view output.

Refer below mentioned thread in which we resolved the same issue.

Regards,

Sudeesh Soni

Re: Data inconsistency in database view

matt — Mon, 12 May 2014 04:33:04 GMT

"Executing means clicking on contents

No - that doesn't mean anything either. What exactly are you doing?

Why does the user expect 2800 records? If there are only 800, then there are only 800. A user's expectation is kind of irrelevant when faced with facts. A user may expect all kinds of things.

Re: Data inconsistency in database view

Former Member — Mon, 12 May 2014 04:42:29 GMT

If your key field is getting duplicate then you need to re-evaluate join conditions.

you need to concentrate on other primary keys from all other tables

and apply specific condition to them so they will also come unique .

for example...consider

vendor master company code (LFB1 - here bukrs)

Vendor master record purchasing organization data (LFM1 - here Purchasing Organization)

Re: Data inconsistency in database view

former_member382013 — Wed, 21 May 2014 06:59:12 GMT

Hi Sudeesh,

Sorry for being late.

I Checked all the join conditions. All of them are correct.

But one point that I noted is, For some vendors LFBK, ADR2,ADR6,LFM1,ADR3 tables do not contain any value.

is this the reason for improper data.

Please let me know.