topic OBLIGATORY field problem in Application Development and Automation Discussions

OBLIGATORY field problem

Former Member — Tue, 13 Oct 2009 12:38:07 GMT

Hi,

Fist off - I am no ABAPer but are investigating and programming issue.

We have a problem with a custom report where one field was previously marked as "OBLIGATORY". This was transported to our production system. After review the user wanted the "OBLIGATORY" removed from the field. This was removed and also transported to production.

When executing the report, the field still shows as being OBLIGATORY, even though the code in the production system shows that the OBLIGATORY code was removed from the field.

Any ideas why the report would still show the field as mandatory even after the OBLIGATORY code has been removed?

Regards,

Re: OBLIGATORY field problem

SuhaSaha — Tue, 13 Oct 2009 12:40:09 GMT

Hello CJ,

Is this a simple report or some module pool program?

If the former, are you using any variant to execute the report?

BR,

Suhas

Re: OBLIGATORY field problem

Former Member — Tue, 13 Oct 2009 12:41:10 GMT

check the at selection-screen ouput.

is there any thing written as screen-required = '1' ??

is the program in production active?

and

after removing that 'OBLIGATORY' is the program activated?

Re: OBLIGATORY field problem

Former Member — Tue, 13 Oct 2009 13:02:42 GMT

Hi,

First check whether the code is activated after the change.

Thanks,

Harini

Re: OBLIGATORY field problem

ThomasZloch — Tue, 13 Oct 2009 13:28:00 GMT

I think it's not about the activation of the source code, but the generation of the selection screen. In production system, go to SE38, enter program name, choose program->generate. Not sure why this happens in the first place.

Thomas

Re: OBLIGATORY field problem

Former Member — Tue, 13 Oct 2009 14:08:46 GMT

If the program runs by transaction with variant check if the varian has setup the field as obligatory

Re: OBLIGATORY field problem

Former Member — Tue, 13 Oct 2009 14:36:50 GMT

Hi Cornelius,

I think it could be a mistake to transport the report. Review the log. Creates another order and transported again to the report.

Regards,

José

Re: OBLIGATORY field problem

christine_evans — Tue, 13 Oct 2009 14:39:52 GMT

You can change the attributes of any field dynamically at runtime using a LOOP AT SCREEN. Check for this.

Re: OBLIGATORY field problem

Former Member — Tue, 13 Oct 2009 15:47:26 GMT

Hi All,

Thomas was spot-on with his suggestion. Regenerating the report solved the issue. I am also not sure why this did not do so in the first place. I saw no errors in the transport logs...

Anyways, thank you all for the quick responses - P*ints rewarded to all for the willingness to helpout so quickly.

Regards,