DDIC_TYPE_INCONSISTENCY - ABAP

[former_member223134]

Dear ABAP Gurus,

I am getting lot of short dumps upon adjustment of data length of domain( reduced to 10 from current length of 40) and then using DB utlitity, and I am using it for PO screen enhancement using include CI_EKPODB. Now Table conversion has stopped at step 6(renaming of QCMEKPO to EKPO failed).

I am going thru already posted threads.

Can you guide me how to proceed.

regards,

Gautam

[former_member223134]

Dear ABAP Gurus,

I am getting lot of short dumps upon adjustment of data length of domain( reduced to 10 from current length of 40) and then using DB utlitity, and I am using it for PO screen enhancement using include CI_EKPODB. Now Table conversion has stopped at step 6(renaming of QCMEKPO to EKPO failed).

I am going thru already posted threads.

Can you guide me how to proceed.

regards,

Gautam

[jorge_ocampos]

Hi Nav

You have to check where this domain is used and re-activate all this objects. Also, if your are using this domain in a data element o a table, try to adjust it with SE14 transaction (without data deletion).

Best regards.

[former_member223134]

Thanks Jorge,

I tried activating the dependent objects using program RSDDCHECK

but structures EKPO, EKPODATA and WRF_POHF_EKPO_ADDON_STY couldn't be activated.

as EKPO is locked in SE14 (Table EKPO is inconsistant). I am trying to find out RCA somehow now onwards.

Error analysis

    An inconsistency was discovered during access to the description of

    data type "EKPO". According to ABAP load, the data type 3076 is bytes long

    but according to the dictionary information at runtime it is 3092 bytes.

    This situation could occur if the data type was changed during the

    runtime of the program.

Thanks,

Navneesh

[nabheetscn]

Hi Nav

When you basically change the length etc and try to activate it via SE14 it fails because you do not have authorization for the changes at database level. Since you do not have authorization the system finds different number of fields and raise this exception

You can execute report RSNTABCONSISTENCY and pass your table to check what is detail root cause of it. Plus please ask your basis person to activate it at database level

Thanks

Nabheet

[former_member223134]

Hello Nabheet,

thanks for your suggestion.

I have realised that runtime objects of several table are inconsistant with DATA dictionary definition. Would refreshing the buffer NAMETAB( using transaction /$SYNC) would help me.

Thanks,

Navneesh

[nabheetscn]

I believe it will be wise to involve basis also just to be on safer side

[former_member223134]

Hello Nabheet,

The error is there in SE14 database utlility as per the attached screenshot.please advise what to do.

Regards,

Nav

[nabheetscn]

In SE14 choose indexes and select the index choose activate and adjust.

To get which index needs to be adjusted use utilities-》database object

[nabheetscn]

In SE14 choose indexes and select the index choose activate and adjust.

To get which index needs to be adjusted use utilities-》database object

[former_member223134]

Hello Nabheet,

I have created indexes and missing view manually and started 'continue adjustment' but it failed with below messages.

   TABL EKPO already exists

   Renaming of table QCM8EKPO to EKPO failed

   Error in step EKPO-STEP6

did anybody had came across this situation.

pl advise.

Thanks,

Nav

[nabheetscn]

What does the processing log detail shows..? Please attach a screen shot

Nabheet

[former_member223134]

Hello ,

Following message is being generated upon choosing option 'continue adjustment'.

I got this message in ST22.

''Inconsistency in the length of DDIC data type "EKPO"

&

An inconsistency was discovered during access to the description of

data type "EKPO". According to ABAP load, the data type 3076 is bytes long

but according to the dictionary information at runtime it is 3092 bytes.

This situation could occur if the data type was changed during the

runtime of the program.

Although i have compared the length is same at moment both in data dictionary and runtime object.

(attached screenshot).

Regards,

Nav

[nabheetscn]

Did you execute report RSDDCHECK to check where the inconsistency lies in which object and execute each object individually?

Nabheet

[former_member223134]

Hello Nabheet,

I rechecked any inactive/inconsistent object with this report but it was not proceeding beyond step 6 execution. now i have proceeded with 'unlock table' option and is OK - no more dumps.

Thanks for your suggestion.

Nav

[Former Member]

Hi,

Please provide me the field which you want to adjust the length to cross verify!

If it is giving lot of problems, back out for time being and adjust as it is! will check it again

[Former Member]

Sorry If I am going off the track...changing the length of a domain, was it really unavoidable? Did you tried exploring other options where you could have managed/achieved the requirement without changing the standard domain?

[former_member223134]

Hello Amit,

It was a Z domain, and it's adjustment I had felt how easy it is

Nav