‎2010 Jan 11 7:42 PM
Hello,
I implemented business transaction event 1030 because this event has the document number available. Within the custom function module I call a screen for some line items that match certain criteria. From that screen I am populating a custom table with the document #, CO, year, line #, and the additional data that the user enters on the screen.
This business transaction event works fine for documents that are not inter-company. Inter-company documents cause an error when the screen is called: the transaction ends and the document is not saved. This is the text of the error.
Call screen (not modal) in modal dialog box not allowed .
At this point I don't see any way around this problem. Has anybody else seen this? If so, what did you do?
Thanks
Bruce
‎2010 Jan 11 10:47 PM
Hi,
you are hitting a technical limitation of SAP. So it looks like your only way is to define your custom screen as modal dialog box. I am not sure if it is acceptable for you.
Cheers
‎2010 Jan 12 5:13 PM
Martin,
I needed my screen to be normal screen because there is a fair amount of logic in the PBO and PAI as well as data entry on the screen. A modal window would not have met my needs.
I got past the limitation I was experiencing by removing the "call screen" statement and instead writing a new ABAP program which calls the screen and submitting that program.
Changed call screen ...
to submit Z... and return
Bruce
Edited by: Bruce Tjosvold on Jan 12, 2010 12:16 PM