cancel
Showing results for 
Search instead for 
Did you mean: 

Table z-table could not be activated during transport to QAS

Former Member
0 Kudos

Hi Experts,

I am having problem with transporting my newly created custom tables.

Checked all dependencies activated everything including domains & data elements.

All tables are active in Dev but cant transport to QAS. It always says cant activate.

Why?

Checked other posts and lacking table space was mentioned. Could this be a possibility?

Do I need help from Basis guy?

Thanks,

Jc

former_member226519
Active Contributor
0 Kudos

what exactly is the error message?

Former Member
0 Kudos

Hi Volker,

Table zcustom could not be sctivated.

Nametab for table Zcustom cannot be generated.

Appreciate your help.

Regards,

Jc

matt
Active Contributor
0 Kudos

Have you tried activating via SE14?

Former Member
0 Kudos

I did perform se14

Activate and save data

Jelena
Active Contributor

And? What happened? Kindly don't make the SCN members pry the information out of you.

Besides, there are 296 of SCN posts already about the same error. Have you tried Google?

Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

It could be that the data element of one of your fields is saved locally and not assigned to a package. Make sure all your objects are assigned to a package for transport.

Regards

Taha

Former Member
0 Kudos

Hi Raymond,

I checked activation log,no issues.

Also se13 tech settings,just used APPL0 data class.

What else did I miss?

Thanks again.

raymond_giuseppi
Active Contributor
0 Kudos

Check again for every data element, domain, check and value table, search help, etc. for missing objects: locked in another transport request, or local object types?

former_member226519
Active Contributor
0 Kudos

are you sure you don't use restricted field names?

try SE14 to activate your table.

raymond_giuseppi
Active Contributor
0 Kudos

So you get a "Nametab for table Zcustom cannot be generated". Did you check with SE11 in activation log of the table or in the import log, did you find more information in the log,

e.g. Did you check technical settings of the table (SE13) Look for Data Class in source/target system is the class available in target system, are the database parameters of existing classes correctly define (Maintaining Technical Settings)