topic regarding validations of screen in modulepool programming in Application Development and Automation Discussions

regarding validations of screen in modulepool programming

Former Member — Tue, 17 Apr 2007 10:53:54 GMT

hi experts,

I have to do field control based on some fields, the fields may undergo "optional", "mandatory", "display only after first entry" "warning message" for "mandatory" fields and "Error Message" for "mandatory fields".

But the above should not be hard coded. It should be controlled via a maintenance table.

can any one tell me how to do this?

Re: regarding validations of screen in modulepool programming

former_member196299 — Tue, 17 Apr 2007 11:27:03 GMT

Hi Srinivas ,

If you d't want to handle the errors directly using message statement , then you can handle in the following way . Collect the message numbers and the messages in an i. tab. and then pass it to a function module BALW_BAPIRETURN_GET2 .In return you will have an internal table with all the error messages . If you want to show the user a popup for error messages then you can use fm FB_MESSAGES_DISPLAY_POPUP.

Thanks

Ranjita

Re: regarding validations of screen in modulepool programming

Former Member — Wed, 18 Apr 2007 10:13:58 GMT

Hi,

For your requirement, the type of messages you want to give during execution has to be done by calling a Function Module "CM_F_MESSAGE". exporting

ARBGB = <Message Id>

MSGNR = <Message Number>

MSGTY = either I or E or W depending on your requirement

MSGV1 = <Message you want to give>

thanks,

sksingh

Re: regarding validations of screen in modulepool programming

alejandro_bindi — Fri, 20 Apr 2007 05:36:08 GMT

If I get right what your requirement is (modify statuses of the fields depending on program status and conditions) I think what you need to do is to create a Z customizing table with the key field defined as "fieldname" (i don't recall the data element as of now). Then you select from that table and set each field screen status depending on what the table has defined for that field (other key fields of the table could be the conditions and the remaining fields the properties to set). Then you create a mainteinance view of the table (from SE11) and finally create a transaction to call the SM30 trx with the table as parameter.

Hope that helps.

Greetings

Re: regarding validations of screen in modulepool programming

Former Member — Thu, 03 May 2007 03:34:36 GMT

Thanks experts i got my answer.