RF transactions, required fields & exit-command

[Former Member]

Hi! All,

I am creating custom RF transactions. I have 8 fields on screen of which 4 are required. I have made those mandatory in se51 in element attributes. I have a 'Back' pushbutton for which I have used AT EXIT-COMMAND module (to escape the required field auto-check). This works just fine in SAP but when I try this on SAP Console the back button doesnt work.

1) Can I make fields required or should I separate the screen fields and code to check if required fields are initial?

2) Does the E command work on RF transactions or not?

I see that in standard RF programs, they have used the EXIT module but they dont have any required fields in teh element attributes.

Thank You for your help,

Will reward promptly,

-Priyanka

[naimesh_patel]

I think E command will not work with RF transactoin.

Remove that E command and handle the BACK buttton also in the normal PAI module, not in the EXIT-COMMAND module.

In the back button, just do like this:

  LEAVE TO SCREEN 0.

Regards,

Naimesh Patel

[Former Member]

Thank You Naimesh,

Thats what I did initially. But the user has to enter all the required fields just to exit!! So I wanted to use the E command to by-pass the auto-checks.

Right now, the design is like this. First 4 are required marked mandatory. Upon user entry the other 3 fields populate (only display) and when the document is posted the document number appears in the 8th field. Can you suggest if this is a good idea?

Or if you are sure that E command is not supported should I separate the screen for the required fields (I will not make it required but code for if it is initial send error message).

I have seen EXIT-COMMAND modules in standard RF transactions too.

Thank You for the quick response,

-Priyanka

[naimesh_patel]

Your design seems to be OK.

You can try without the EXIT command and message for all 4 fields which are requried. If it works than you are through.

About the EXIT-COMMAND, as I have said in my eariler post, I am not much sure.

Regards,

Naimesh Patel

[Former Member]

Thank You,

I will try that. Just that I wanted the user to visully see what are required.

-Priyanka

[naimesh_patel]

One more optoin.

You can put one "button" on the screen. By pressing this button you can exit from the transaction.

In the properties of the button, give the FUNCTION CODE (FctCode) and FctType as E. By using this may be you will able to use the EXIT-COMMAND.

Regards,

Naimesh Patel

[Former Member]

Thank You,

I know this. Thats how it worked on SAP screens but when I ran the same Tcode on sapcnsl, this function code isnt working. Please klet me know if you have any suggestions (about why it works in SAP and not on sapcnsl)

-Priyanka

[Former Member]

RF Transactions behaves differently than SAP.

So do not use SAP GUI Elements when you design RF Transactions.

Disable all GUI Elements like BACK, CANCel, and EXIt; instead of this you should use Push button with in screen.

Here you need to maintain Function codes properly.

Use these Function codes where ever required.

Thanks

Seshu

[Former Member]

Hi! Seshu,

I am aware of that. I am not talking about GUI status, I am talking about push buttons only.

I need to know only one thing, can I use required field (in se51, in element attributes, turn the input to required from possible). Can I do that for RF transactions. I dont see any standard LM transactions using that.

If I can, then, to by-pass required-field checks I need to use exit-command (E -function type) for the back 'pushbutton' which doesnt seem to be working.

Thank you,

-Srividhya

[Former Member]

Hello Priyanka,

Not sure but you can raise error message when that field is initial..

My guess would be E exit command applicable only GUI .

Thanks

Seshu

[Former Member]

Thank You, Will try. Otehrwise I will code for initial errors.

Thank You,

-Priyanka