Changing Data type for used Keyfigure from QUAN to FLTP

[Former Member]

Hi All ,

We have changed the data type for key figure & while activating infoobject system thrown error to covert Tables .

On continue Screen moved to SE14 & adjusted Data bases tabel (P-table).

And reloaded data , its working fine in Dev .

But in QA data load is throwing short dump error 'OBJECTS_TABLES_NOT_COMPATIBLE'

Should i convert table manually again in QA ??

Is there any programe  to convert table  or should i go to se14 and execute ??

Any other inputs to fix this are highly appreciable.

Regards ,

Hari.

[Former Member]

Dear Sander ,

Thank you so much for your quick inputs

We have created new keyfigures and made needed changes in targets & in routines ..

Its working fine .

Regards ,

Hari

[sander_vanwilligen]

Hi Hari,

First of all, be careful with changing data type of a key figure if it's productively used. The problem which you faces in Development indicates that. Table conversion using t/code SE14 is normally not necessary.

I suggest to execute the same actions (incl. SE14) in Quality and later on in Production.

A work-around might be to delete data in the affected InfoProviders, change the key figure and reload data. Another work-around might be to define a new key figure, delete data from the affected InfoProviders, replace the key figure and reload data. I cannot judge if this approach is realistic in terms of effort.

Best regards,

Sander

[Former Member]

Hi Sander ,

Thank you so much for your reply .

These Key figures are attribute of material & used in multiple conversion routine in  sales & inventory .

To decide whether to going SE14 changes or creating new keyfigure

Can you help me by pointing on risk with se14 changes option  ??

we are yet go live ,developments are  available in QA

Regards ,

Hari

[sander_vanwilligen]

Hi Hari,

I have a preference for one of the work-arounds. No conversion should be necessary. The reason for being so careful is that table conversion (t/code SE14) is bypassing the SAP BW application layer. Normally you create your data model (incl. InfoObjects) in BW and during activation BW requests the ABAP layer to create/change/delete the ABAP Data Dictionary objects. If something goes wrong or needs conversion using ABAP tools, it might lead to unexpected issues/inconsistencies in the future.

One issue I faced was that space occupation of an InfoCube was disrupted. It is too long ago to remember the details and it occurred in an SAP BW 2.0B system.

Anyway, if you read SAP Note 579342 - Changing key figures that are used in InfoProviders it should be possible to go ahead with your approach. Table conversion will have to place in every target system, Please note that according to SAP Note  1248769 - Inconsistency between database and ABAP Dictionary table conversion should be done using user-id DDIC.

Best regards,

Sander

[former_member202718]

Hi,

I would still prefer not to play with SE14 in Production.Incase if tables get corrupted then it wud be difficult to revive.

Only if you are very sure then you can try to venture into it,..else go for the workaround.

rgds

SVU