BATCHINPUT: Screen appears only the first time

[Former Member]

Hi everybody,

I have the following situation in R/3:

On transaction ABZON when the user selects this transaction for the first time, appears a window asking for the company field (BUKRS). If the user enters the same transaction again without login off, that window doesn't appears going directly to the transaction's main screen.

The problem is that I have to make a batch input of this transaction but doesn't want the user to logoff every time it needs to run the batch input again.

How can I avoid that screen to appear or force the batch input to always show that screen.

If anyone can help me will be appreciated.

Thanks,

Orlando.

[LucianoBentiveg]

Before CALL TRANSACTION, use:

SET PARAMETER 'BUK' FIELD ccode.

By this way, popup dosen't appear.

Regards.

[RichHeilman]

Orlando, I've ran across this is same problem in another transaction. What I did was I "separated" the transaction. Meaning the first thing that happens when the transaction runs, is to take care of the window that appears only once during a log on session. Then later when doing the BDC to actually do something, it will not need to have this part of the recording.

So for example, do your recording for the window that pops up enter a value, and back out of the transaction. Call this BDC code before doing any of the rest of the transactions. Not that the value is filled, it will not pop up again during the rest of the session. Call your BDC to process the rest of the transaction.

Regards,

Rich Heilman

[RichHeilman]

Or of course, Peluka's suggestion would work in this case as well. It actually did not work in my case, when I ran into this type of thing before in another transaction.

Regards,

Rich Heilman

[Former Member]

Thanks for your suggestion Richard,

I have manage the screen to only appears once in the batch input. But my concern is what happens is the user already had enter to the transaction before calling the batch input or if needs to run another batch input of the same transaction, still will have to logout before calling it again because in the second batch input run the screen will not appear and the program is expecting it at least once...

Regards,

Orlando

[RichHeilman]

If the first BDC, which is to handle the popup fails, then so what, right? The first BDC is only supposed to handle the popup and then leave the transaction. If it fails, there is not problem, that just means that the popup never was fired, which means that the second BDC will be successful since the pop has been handled. Please try Peluka's suggestion first, though.

Regards,

Rich Heilman

[LucianoBentiveg]

Yes man!!!! <i>"Show me that points"</i>

[Former Member]

Sorry for the delay.

Thanks Peluka aparently your suggestion worked.

Here are your points.

PD: Thanks to you too Rich.

Regards,

Orlando

[Former Member]

Hi Orlando,

I faced same problem while uploading the data for business partnet creation

what I did is I excuted and entered that transaction before starting the recording of the batch input then I recorded the transaction at this point I didn't get the popup window. I completed the batch input coding.

When I wish to upload the data, I executed the trasaction once before running the batch session. Thats it, it workedout fine for me

Regards,

Naveen

[RichHeilman]

Also, another way around this problem, is to set the parameter id in the user profile. Click System>User Profile>Own Data. Click the Parameters Tab. In an empty row at the bottom, enter "BUK" as the parameter id and the company code in the parameter value . Save. Now go back to the transaction, you will not get a popup because it is deriving it from the users defaults. Of course you will need to make sure that the certain users that use your program have this as the default. Otherwise you will need to set it manually, as Peluks has suggested.

Regards,

Rich Heilman