Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BTE 1030 problem with Inter-CO document

Former Member
0 Likes
729

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

2 REPLIES 2
Read only

mvoros
Active Contributor
0 Likes
472

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

Read only

Former Member
0 Likes
472

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