topic Re: LDB changes do not reflect on ABAPQuery in Application Development and Automation Discussions

LDB changes do not reflect on ABAPQuery

Former Member — Mon, 16 Jan 2012 04:12:09 GMT

Hi All,

My requirement is to extend the dynamic selections to some EKKN fields for transaction ME80FN.

Transaction: ME80FN

Report: RM06EAAW

Query: ME80FN

Assigned report: AQZZ/SAPQUERY/MEME80FN========

Logical database: MEPOLDB

I managed to change MEPOLDB and looks OK when testing on its own. Nevertheless this change doesnu2019t reflect on the query itself when called through transaction ME80FN.

What else needs to be done?

We are on ECC 6.0.

Thanx

Re: LDB changes do not reflect on ABAPQuery

Former Member — Mon, 16 Jan 2012 04:37:33 GMT

regenerate the query program.

Re: LDB changes do not reflect on ABAPQuery

Former Member — Tue, 17 Jan 2012 07:12:25 GMT

Thanx Soumyaprakash,

Your suggestion sounds like the perfect solution, but I couldn't make it work. It looks like regenerating the query, but it is too fast to see what the message blinks up on the bottom of the screen.

The initial aim was to add more fields to the dynamic selection criteria of trx ME80FN. I managed to add the required fields to the relevant field-group and also add those to the logical database MEPOLDB. It allowed me to add the new selection view but can't regenerate neither the selections nor the program itself. It sees as a 'repair' despite it created a normal change request for the new selection view. Catch 22?

We are on ECC 6.0

Thanx

Karl

Re: LDB changes do not reflect on ABAPQuery

Former Member — Tue, 17 Jan 2012 07:18:33 GMT

karl. explain me this bit of yours


>"but it is too fast to see what the message blinks up on the bottom of the screen."

Re: LDB changes do not reflect on ABAPQuery

Former Member — Tue, 17 Jan 2012 10:42:46 GMT

I know it doesn't sound too professional, but exactly that what I mean. On the bottom status line flashes up something, but can't catch. That happens during the generation. It doesn't stay and it doesn't require an answer of any kind.

The only way to 'catch' it would be debug, which I think would be a lengthy exercise.