Table could not be activated.

[Former Member]

Hi Experts,

I have this problem with my Z-table, it could not be activated. My table has 100+ fields. And when i tried to activate it.

It tells me the following error message:

Table ZCTD_MIGCUST could not be activated

(E- Table ZCTD_MIGCU is too long (>4030) )

how can i solve this problem.

Please advise.

Thanks

Lawrence

[Former Member]

Hi Experts,

I have this problem with my Z-table, it could not be activated. My table has 100+ fields. And when i tried to activate it.

It tells me the following error message:

Table ZCTD_MIGCUST could not be activated

(E- Table ZCTD_MIGCU is too long (>4030) )

how can i solve this problem.

Please advise.

Thanks

Lawrence

[Former Member]

check the following conditions

1. all data elements and domains should be active.

2. if you use any RAW data type it should be last field

[Former Member]

Your Table Record size is exceeding the Maximum possible value defined at the Database level, which is probably 4030.

Try decreasing your number of fields and you should be happy.

[Former Member]

the problem here is i cannot decrease the number of fields.

anymore ideas guys?

[Former Member]

any ideas??

[Former Member]

Hi,

Try changing the size category from technical settings to 7.

[Former Member]

nope. changing the size category from technical settings to 7 does not work.

[Former Member]

Hi,

Try this:

SE11

Utilities->Database Object->Database Utility->Activate and adjust database

[Former Member]

nope. still cannot work.

[Former Member]

Hi,

What you can do is you can try to move some of the fields to a new structure and then try to append that structure to your database table... Just try this option .. maybe it will work...

[Former Member]

Hi,

I thought of this idea also.. but just want to see there is other solution before i take this step.

[Former Member]

Hi,

I think this will be the best solution because as of now you might be exceeding the maximum database record size.. But, appending a new structure with some of your fields might solve your problem...

[sravya_ch]

Hi

Reduce the number of fields and add a structure is the only way to solve this problem

Edited by: Sravya Ch on Jun 29, 2009 8:22 AM

[Former Member]

Hi Lawrence.

I request you to use Normalization Techniques in Database table creation. Means, Use the same key, you used in your Z table,

but create new Z-Table, and keep all logically related fields in Table 1 into Table 2.

I don't know if you are using the table where it allows you only to use single table, but this could be the best practice give you more readability and maintainability.

Best example for normalization you can see in Info type tables or in Logistic tables like MARA, MARC, MARD, MAKT e.t.c ..

All the very best.

- Mohan Vamsi

[Former Member]

Hi Lee,

Try Appending a new structure..

or the best option is to have 2 or 3 tables (convince ur Client,why its important to have 2 or more fields - normalisation concept)

Regards

Sajid.

[Former Member]

Hello,

besides the solutions here listed in the post, you should have a look at SAP note 636217.

It explains the limits in table width (and why it is now 4030 bytes).

[Note 636217 - DDIC activation error as table width greater than 1962 bytes|https://service.sap.com/sap/support/notes/636217]

Greetings,

Stefan

[Former Member]

I'm not sure about this at all, but I don't think the restriction applies to cluster tables.

Rob

[Former Member]

Hello,

I don't know much about the cluster tables, I tried it and came to the following results:

• LRAW Type can be up to 32000 in length

• CHAR Type can be max. 255 in cluster tables

• If the standard length of the transparent tables is exceeded, a warning is displayed by the checker/activator,

that you cannot revert the table to a transparent one

• Documentation states, that business data should not be saved in cluster tables.

May be it helps,

Best regards,

Stefan

[Former Member]

Hello,

Additional info on LRAW from ABAP Dictionary Documentation:

LRAW: Uninterpreted byte string of any length, but with a minimum length of 256. Fields of this type must be located at the end of transparent tables and must be preceded by a length field of type INT2. If there is an INSERT or UPDATE in ABAP programs, this length field must be filled with the length actually required. A fields of this type cannot be used in the WHERE condition of a SELECT statement.

Best regards,

Stefan

[Former Member]

Hi,

You can check to the size category and change that according to your requirement.You can either use the size category as 1 or 2. And see to that all the domains and data elements are activated.

Thanks & Regards,

Dhanalakshmi.

[Former Member]

Hi ,

Just check wheather every dataelement and domain are activated or not and while creating table maintaince generator specify the size catogery as 2. Hope this will work.

Regards,

Pavan.

[Former Member]

Even i faced a issue while trying to create a database table. It showed an error "could not determine the structure width of ... " This error was due the fields present in my code. On checking i found those fields didn't exist. This happened when i was trying to follow a tutorial on developer.sap.com