topic Re: Grey out fields in Application Development and Automation Discussions

Grey out fields

Former Member — Tue, 08 Feb 2011 19:44:55 GMT

I am calling a transaction from a program with some fileds in the BDCDATA. Once the user sees that transaction I would like to have the fields grey so that he cannot enter something...can you help me?

Thanx

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 19:52:01 GMT

You mean to say that the user is executing your program in foreground and transaction is called with MODE 'A', so that all screens are displayed... While displaying the screens, the user has ability to change the input and you want to disable it?

If that is the case, why use mode 'A', you can use MODE 'E' to display the screens only at error? If my understanding is not correct, please elaborate

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 19:56:27 GMT

No, because when the screen will appear to the user he will have the choice of running the transaction or going back t the other screen that called the transaction

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 20:01:24 GMT

Most of the times, it is common to execute the BDC programs in background (in MODE 'N').. Unless there is a very specific requirement for user to do manipulation and it seems like there is no requirement in your case, I would stick with MODE 'N'... that way user will not be able to see the screens itself...

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 20:07:39 GMT

However the requirement from analyst is for the user to chose either to run the transactions with the fields already entered or to cancel and go back to previous screen

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 20:22:10 GMT

I don't know if this is feasible... You not only want to allow the user to pass a value to a screen and then turn around to ensure that same user cannot edit the screen value...

I would go back to your analyst and tell him that you can provide an ALV screen (from which the users can choose which transactions he want to POST)... and which transactions he doesn't want to Post... But once he has started on the journey, he has to continue thru the posting and will not have ability to cancel (in MODE 'N')

Or give him the full MODE access 'A' and make an assumption that Users are smart enough to not change the values.

I would really be interested in knowing business justification for such a requirement (and the transaction that he wants to post)

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 20:37:48 GMT

they are using Z transactions and they want to do this to integrate a transaqction that runs in background. SO they either do the job or they just cancel it.

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 20:44:37 GMT

Since it is a Z transaction, you can change it to test SY-BINPT and grey-out the fields as you see fiit.

Rob

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 20:49:19 GMT

Im not sure I understand what sy-binpt would do?

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 21:08:05 GMT

Maybe I misunderstood the question.

Is the transaction you are running in batch input a custom one or an SAP transaction (which one)?

Rob

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 21:47:19 GMT

What is the transaction code used in Call Transaction? Is it 'Z' or standard SAP..

If your call transaction is 'Z', Rob is suggesting that you can then change the PBO screen of your call transaction program to check for SY-BINPT (SY-BINPT is a system variable that identifies if the program is called thru batch input)... If sy-binpt is set, you can set the screen attributes to be non-ediatble in PBO of your called transaction.

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 22:04:36 GMT

Well, almost - further work would be needed.

Rob

Re: Grey out fields

Former Member — Tue, 08 Feb 2011 22:27:20 GMT


> Well, almost - further work would be needed.
> 
> Rob

Could you please elaborate what else would be needed?

Re: Grey out fields

Former Member — Wed, 09 Feb 2011 13:55:10 GMT

It depends on which is the custom transaction. The OP needs to answer my question.

Rob

Re: Grey out fields

Former Member — Wed, 09 Feb 2011 17:32:12 GMT

Hi Kris and Rob,

the program also calls a Z transaction...so i will try doing what Kris told me...

Thanx

Re: Grey out fields

Former Member — Wed, 09 Feb 2011 17:56:21 GMT

The program calls a Z transaction and shows the user the selection screen. «so from the called program there is no other screen than the selection screen...how would i write in the PBO?

Re: Grey out fields

Former Member — Wed, 09 Feb 2011 18:06:24 GMT

So, you are calling a report program in batch input. Is that correct?

Rob

Re: Grey out fields

Former Member — Wed, 09 Feb 2011 18:10:45 GMT

im doing CALL TRANSACTION Z.

Re: Grey out fields

Former Member — Wed, 09 Feb 2011 18:19:33 GMT

OK, assuming this is a Z report, you can use SIBMIT rather than CALL TRANSACTION. and then in the AT SELECTION-SCREEN OUTPUT event, grey out the SELECT-OPTIONS and PARAMETERs if it is in the background.

Rob

Re: Grey out fields

Former Member — Wed, 09 Feb 2011 18:32:51 GMT

thanx Rob!! im not sure but should i use the SCREEN structure?