Master data overwrite working for 0GL_ACCOUNT

[#1]

Hi Team,

I am facing  a strange issue , I have master data flow in which I have a DSO staging between the InfoObject & Datasource. But strangely when I am running the DTP from DSO to InfoObject , no records gets updated.

[Former Member · Accepted solution]

Hi,

may be because of duplicates(if you enable "handle duplicates " in info object dtp), nothing is updating to info object? (or) check if are there any validations in between DSO to info-object .

[Former Member · Accepted solution]

Hi Jyothi,

No "handle duplicates" checkbox is not checked in my case. I ideally I would expect to do overwrite even though the records already exist in the master data tables. Also I didn't put any validation from DSO to InfoObject.

Regards,

Fox

[Former Member · Accepted solution]

Hi,

I ideally I would expect to do overwrite even though the records already exist in the master data tables

info-object does overwrite the records, however, if there are duplicates from source(either in PSA/dso in your case..) then it throws error if you dont handle duplicate/ and if you handle duplicates.. it ignores duplicates and load only one record .

anyway, back to your issue, is the first load to gl account from dso?

[Former Member · Accepted solution]

Yes , I have loaded 1st time from DSO but is that anyways matters. Also since the DSO keys are as good as master data infoObject(same), so not point of Having DSO to have duplicate records.

[Former Member · Accepted solution]

ok, with this information, couldn't guess where might have it gone wrong.. can you share dso to info-object mapping ? and dtp with extraction and update tabs?

[Former Member · Accepted solution]

Hi Jyoti,

From DSO to InfoObject its just one to one mapping, I have loaded many request to this InfoObject via DSO as showing below in the screenshot but the last "highlighted one" you can see no record gets added thought transferred. Also there is not setting change from then to now. Don't where it is going wrong.

[Former Member · Accepted solution]

hmm, just check whether any of those new records from last run updated in info-object? (take one record from dso last request and try to find it in info-object display data).

[Former Member · Accepted solution]

Yes Offcourse.

[Former Member · Accepted solution]

so, data is updated to info-object, but from manage screen added records are displaying as zero?

can't say the exact reason, however from my understanding, if the same records are updated again (with no single new /change record) then added records will be zero..

sometimes, you get "no more data available" when you run DTP, at times added records will be zero.

[Former Member · Accepted solution]

No I was also an same illusion, but then I change one of the attribute but still no records gets added in manage, When I open the InfoObject P table, I found the attribute remains unchanged. In the error stanck its says that the GL_ACCOUNT duplicate record found. Do not understand why this is happening .

[Former Member · Accepted solution]

as you are loading from DSO, check whether the records are updating change log, if, yes, then there will be duplicate entries for a changed record.. and info object might be picking record mode N, which is the reason, you didn't see changed record in P table..

if you are sure that records are updating from change log, then you can pull only changed records (using a routine in transformation).

[Former Member · Accepted solution]

My change is log is having 548 entries & same will be transferred in the DTP for the InfoObject(refer the screenshot given above), but none of them gets added.

Since the DTP picks exactly the same no of the records, then is there any point of putting change log.

[anindya_bose · Accepted solution]

If there is no change, you would get "No More Data" message . But here , you get records in DTP but that is not being added. That means problem is with "Error Stack" probably.

My Guess:  You are loading GL Account.  GL Account should of have compounding object 0CHRT_ACCTS .  Do you have 0CHRT_ACCTS as a part of DSO key and in InfoObject "Compounding" tab ?

If this is not the case, you are probably getting same GL account for more than one COA , which in turn creating duplicate entries and sending records to "Error Stack"

Regards

Anindya

[Former Member · Accepted solution]

The issue is resolved by setting 'Handle duplicate records' checkbox in DTP setting.

[anindya_bose · Accepted solution]

That's what I said in my previous reply.

If this is not the case, you are probably getting same GL account for more than one COA , which in turn creating duplicate entries and sending records to "Error Stack"

Handle duplicate records would would remove entries if same GL account is coming from two Chart of Accounts . If you are working with only one COA, then it is fine, else GL account should be computed with COA.

Regards

Anindya

[Former Member · Accepted solution]

Hi Anindya, it not because of same GL_ACCOUNT with different CHRT_ACCTS instead what happened is business is also sending text for master data via the same datasource, so its happens that for one load cycle they just changed all the text of GL_ACCOUNTS causing the change log with before and after text change apart from any attribute change & when updating the attribute since DTP picks from the change log(delta DTP), it reads two records with same technical key.

Thanks everyone for the advice.

Regards,

Fox