topic Re: call transaction problem in Application Development and Automation Discussions

call transaction problem

Former Member — Wed, 01 Mar 2006 09:38:33 GMT

Hi all,

when I call transaction with mode 'a' update 's',

it works.

but when i turn it back to mode 'n' update 's', it doesn't work.

what's wrong are there?

thanks.

Re: call transaction problem

Former Member — Wed, 01 Mar 2006 09:42:55 GMT

have you tried with type 'E'

It will stop only if there is an error!

Regards,

Re: call transaction problem

Former Member — Wed, 01 Mar 2006 09:43:02 GMT

Hi Macy,

I suggest you to test the sy-subrc after your 'call transaction'

Morover, do you save messages like this :

  
DATA: BEGIN OF WT_MESSTAB OCCURS 0.
        INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF WT_MESSTAB.

...

CALL TRANSACTION 'T-CODE' USING WT_BDCDATA MODE 'N' UPDATE 'S'
MESSAGES INTO WT_MESSTAB.

Hope it helps,

Erwan.

Re: call transaction problem

Former Member — Wed, 01 Mar 2006 09:43:25 GMT

hi macy,

MODE

A Display all

E Display errors only

N No display

<update> : Update mode:

S Synchronous

A Asynchronous

L Local update

SINCE U GAVE 'N' IT DOESN'T DISPLAY ANYTHING..JUST CHANGE THE MODE..

REWARD IF USEFUL

Message was edited by: Ashok Kumar Prithiviraj

Re: call transaction problem

Former Member — Wed, 01 Mar 2006 09:43:40 GMT

if there is any inconsistency in screen population it may not give u correct results. try to catch errors in BDCmsgcoll table if theer is any message no 1001.

Re: call transaction problem

Former Member — Wed, 01 Mar 2006 09:43:58 GMT

hi,

try to change it to......

mode 'A' update 'S' or mode 'N' update 'S'

regards

vijay

Re: call transaction problem

Former Member — Wed, 01 Mar 2006 09:44:27 GMT

Hi macy,

1. it doesn't work.

What is the meaning of that ?

2. When we give mode N

No screens will be displayed on the computer.

The processing mode can take the following values:

'A' Display screen

'E' Display only if an error occurs

'N' Do not display

'P' Do not display; debugging possible

regards,

amit m.

Re: call transaction problem

Former Member — Wed, 01 Mar 2006 09:44:46 GMT

Mode N will have problems if some unexpected popups (or screen sequence changes) occur during the program run and the BDC is not coded to handle those. These could be information popups like 'Delivery date has been changed' or warnings like 'Are you sure you want to change', in short, anything.

The only way to analyze the problem is to first run online and see if any of these require user input during runtime, or scan the messages saved in the BDCMSGCOLL after the background run.

Sudha

Message was edited by: Sudha Mohan

Re: call transaction problem

hymavathi_oruganti — Wed, 01 Mar 2006 09:53:10 GMT

where it is being stuck? it does not work means?

u try in 'E' mode and find error

Re: call transaction problem

Former Member — Wed, 01 Mar 2006 09:58:05 GMT

Hi Macy,

I hope you have given mode 'N' in Caps.

other wise it will take defaults.

Regards

vijay

Re: call transaction problem

Former Member — Wed, 01 Mar 2006 10:18:52 GMT

Hi,

The processing mode can take the following values:

'A' Display screen

'E' Display only if an error occurs

'N' Do not display

'P' Do not display; debugging possible

If the MODE addition is omitted, then the processing mode is 'A'.

If a screen is displayed in processing mode 'E' because the system reached the end of the BDC data, the system automatically switches to processing mode 'A'.

If breakpoints are set in a transaction tcod called using the CALL TRANSACTION tcod USING itab variant, these are not actually reached in 'N' mode. The system tries to insert data in the Debugger screen; the call ends with SY-SUBRC = 1001 and the message "Batch input data is not available for screen SAPMSSY3 0131" (S 00 344).

Conversely, in 'P' mode, transaction screens are processed in the background (as in 'N' mode) and debugging is possible.

Re: call transaction problem

Former Member — Thu, 02 Mar 2006 08:34:09 GMT

Hi,

Is your problem solved?

Regards,