topic Re: Problem After Moving Changes to Production in Application Development and Automation Discussions

Problem After Moving Changes to Production

Former Member — Sat, 30 Apr 2011 08:06:04 GMT

Weird problem occured when we moved our change to production. Background : The QMEL table has been extended using APPEND structures and around 10 fields were alread added and avaible in production.

Problem : During a recent change we had to add few more fields to the append structure in QMEl. After adding these fields and making necessary changes to Funciton modules to update these fields. We tested and it worked fine in Development environment. We moved the transport changes to quality and it imported without any errors. The changes in the quality system was tested by development team and the functional team and we didnt have any issue. QMEL table was active and the new fields were visible in both program and SE11 .

Now, when we tried to move the fields to production the transport request moved without any errors. The table QMEL shows the new fields in it and its active. However, when a program tries to read or update QMEL results in a short dump.

The 3 fields added to append structure are CHAR10,CHAR15 and Curr (13 dec 2).

Any reasons for this behaviour.

Thanks in advance.

Regards,

Kumaran

Re: Problem After Moving Changes to Production

Former Member — Sat, 30 Apr 2011 17:08:49 GMT

If you want any help, you'll have to post the relevant dump details.

Rob

Re: Problem After Moving Changes to Production

ThomasZloch — Sat, 30 Apr 2011 21:22:27 GMT

What Rob says, plus in any case you can try to adjust the table again using database utility SE14, something which is normally done automatically during import, but occasionally does not yield the desired result (don't ask me why).

Thomas

Re: Problem After Moving Changes to Production

Former Member — Sun, 01 May 2011 06:46:15 GMT

Thanks Rob and Thomas for your Response.

@Rob : Below the extract of the error message.

***********************************************************8

ABAP runtime errors DBIF_RSQL_SQL_ERROR

If this error occurred in ABAP/4 Open SQL, there is an inconsistency

between the ABAP/4 Dictionary and the database.

You can resolve this by converting the table in the database

to the definition in the ABAP/4 Dictionary.

To do this, call Transaction SE11 and then select

Utilities > Database utility.

Please make a note of the actions and input which caused the error.

To resolve the problem, contact your

SAP system administrator.

Choose "Print" for a hard coopy of the termination message. You can

display and adminster short dump messages using Transaction ST22.

*****************************************************************************

These were the steps that we tried to resolve however been unsuccesfull

1. SE14 : Database Utility. Adjust table and data. But no luck.

2. Tried to restore the old transporat from version management. Still no luck.

The last option decided by the Project Management team was to restore the database (dont ask me why ) to a state before transport. In that way we have lost some data. Not sure if thats the right way . So thought of asking the experts if there could have been any other options ?

Regards,

Kumaran

Re: Problem After Moving Changes to Production

madhu_vadlamani — Wed, 04 May 2011 04:05:07 GMT

HI Kumaran,

1)Check whether the append structure is activated or not 2) If need regenerate the table again and activate 3) Check in production system whether is activated or not 4) Check the particular requests moved or not.Post if need more help in this.

Regards,

Madhu.

Re: Problem After Moving Changes to Production

Former Member — Wed, 04 May 2011 15:37:49 GMT

Se11 -> Utilities -> Database Utility or SE14, Activate and Adjust database.

Use the database utility to adjust the database. This happens at times when the request is moved and for some reason the table is locked (happened with me many times due to batch job accessing the table at same time). This should fix the dump.

Thanks,

Santosh