topic Primary Key Transport Problem in Application Development and Automation Discussions

Primary Key Transport Problem

Former Member — Tue, 29 Apr 2014 15:48:20 GMT

Dear Gurus,

I had a requirement wherein I had to make an existing non-key field of a Z-table as a Primary Key field, so I moved that non key field next to the existing primary key fields & made it as a key field by going se14 'Adjust and Activate' functionality.

Now, when the requested was imported to quality it showed error and no changes were seen.. What should I do now, there are lot of programs dependent to that Z table.. Should I ask to activate and adjust in the Quality too?... Then how about Production??

Thank you for your kind perusal.

Re: Primary Key Transport Problem

former_member194739 — Tue, 29 Apr 2014 19:10:29 GMT

Dear Hari,

Adjust individual landscape.

Regards,

Abbas.

Re: Primary Key Transport Problem

Former Member — Wed, 30 Apr 2014 04:00:26 GMT

Hi Hari,

Can you shows us the error log?

Also, check if you have table maintenance generator then delete it and create the new table maintenance generator.

Regards,

Sudeesh Soni

Re: Primary Key Transport Problem

yogendra_bhaskar — Wed, 30 Apr 2014 06:24:18 GMT

Hi Hari ,

Yes , you have to repeat the same " se14 'Adjust and Activate' functionality. " on quality and PRD server.

Regards,

Yogendra Bhaskar

Re: Primary Key Transport Problem

Former Member — Wed, 30 Apr 2014 06:29:16 GMT

Hi Hari,

Delete the Table maintenence generator and create new.It will work

Regards,

Ankit

Re: Primary Key Transport Problem

RaymondGiuseppi — Wed, 30 Apr 2014 06:37:39 GMT

Yes database should be adjusted. For production note that SE14 can be scheduled for execution in background, so schedule transport and adjustment out of peak hours.

Regards,

Raymond

Re: Primary Key Transport Problem

Former Member — Wed, 30 Apr 2014 07:23:01 GMT

Hi Hari,

As per my past experience, you dont need to activate and adjust the database manually in Production.

Check the same with basis team.

Also, i will advise you to take table backup before deploying transports to Production because there are chances of reduction in table entries if any duplicate record will be identified for your new primary key fields combination.

Regards,

Sudeesh Soni