Dso Activation Failure

[former_member184884]

Hi Mates,

I am facing one failure though even it is quite simple & may be many threads available in this forum

but still i need your suggestion in fixing my issue please excuse me in this regard.

here is my issue:

Their is data flow like in our BW system source-system(not ECC)--- > BW(PSA)----- > DSO -----> Cube(reporting layer)

data staging in BW happening through process chain once DTP loads from PSA to DSO during DSO activation we are facing below failure.

and I've attached the screenshot of the same please go through it, as per message it is showing sid is not generated for those materails due to this activation step is getting failure but when i checked in the 0MATERIAL master data SID are generated for those materials.

One thing i would like to stress here is recently our system has upgraded from 7.0 to 7.31 so due to upgradation their is some inconsistency has happened in the master data, even i did RSRV for 0MATERIAL i found many materials have inconsistent.

so to fix the issue I've 2 options to delete inconsistent 0MATERIAL data from BW and reload again to BW as it is tedious & quite risky one i am not opting for this, so I've chosen other option i.e. to change the DSO settings like "Sid generation upon activation" i am planning to deactivate this mode so that their is no SID are created and activation will goes fine as DSO is just staging layer hence it will not cause any issue anyhow from DSO again data is pulling to cube as per start schema architecture sid's will be created in the cube level..!!!

Can you please suggest can i make this settings in the DSO level and please tell me it will not impact on query performance.!!!!

Thanks & Regards,

Harish

[Former Member]

Hi Harish,

             If you want to create sid for this material id: 21062869, paste this entire number in RSKC tcode, and save, now activate the DSO again. some times it will help but not recommeded to use this procedure. Please check if it helps you to resolve your issue. if activation is done successfully, after that remove the value from RSKC and save it with old values.

Regards,

Ravi

[Former Member]

Hi,

You pointed out that you have upgraded to version 7.3 and that this problem has started after the upgrade on material data.

Before changing your DSO settings, please go to transaction OMSL and check if material length = 18, if not, please change it.

[Former Member]

This message was moderated.

[former_member184884]

Hi Folks,

Good morning just woke up.....

Thanks for all your speedy inputs.

@Michael & Martin i am aware their is conversion routine(CR) is missing at transformation level for source filed but same exist for target field but data load is going on fine  i am facing the issue at activation step so by adding CR in transformation level will fix my issue.!!!!

@raman as i said earlier report is built on Cube not on DSO but my concern here is if we remove that settings in DSO level it will not impact on report run right means report performance.

Please clear this 2 doubts so that i'll fix this today itself in my system....

Thanks & Regards,

Harish

[RamanKorrapati]

Hi Harish,

Then just turn off SID settings for DSO. if in future if you plan to do report on DSO. you may face sid issues.

Yes, DSO Sid settings won't impact on Report which your going to build on cube.During report on cube, SID will generate for which are not  generated.

Thanks

[former_member184884]

Hi Raman,

Thanks for inputs, one last concern report will work fine right as it was earlier mainly performance aspect.

FYI this DSO is not used anywhere except in this flow that too as staging layer so i took this brave decision to change the DSO settings even my leads & architects also accepted my proposal...

Cheers,

Harish

[RamanKorrapati]

Hi,

DSO SID Setting turning off is always best suggestion when we are not doing report on dso. So you can go ahead. . if your info objects(which are used at cube) don't have master data then during report time SID's will generate. So no issues. do at dev and check it once. it will give the clear idea.

Thanks

[Former Member]

Hi Harish,

This matnr conversion error may happen from DSO to cube load. As suggested by Raman, check it in dev system then proceed.

SID creation during report time will slowdown your reporting performance, but master data ACR will remove this problem.

[former_member184884]

Dear All,

as discussed with you all finally i am doing changes in DEV for DSO i.e. settings can you please suggest me i need to take any precuation measures before moving to production.

FYI data load is will goes through process chain but it's not daily here Every time process chain run’s in the beginning their is step which will delete data from the DSO which I am changing the settings.

Best Regards,

Harish

[RamanKorrapati]

Still if your in dilemma about sid settings then pls refer the sdn doc, page no 9.

Standard DSO

PS: Don't select this reply as helpful or correct answer.

[RamanKorrapati]

Hi Harish,

If your not doing report on DSO then better switch off DSO SID Settings during dso activation. its improves your loading performance also.

info object 0MATERIAL - Conversion routine need to be as MATN1.

Thanks

[MGrob]

Hi

Michael points out the right oss note. Make sure the conversion exit MATN1 is present and it will work again

hope it helps

Martin

[michael_devine1]

Hi,

Before trying that solution have you seen this KBA? 1786451 - Value of a characteristic is not converted - BRAIN068

Regards,

Michael