Standard transaction returning wrong values in background

[Former Member]

Hi All,

BDC for SAP transaction KKBC_ORD is running fine in foreground, but it is returning wrong values in background run.

What is needed to make it run fine in background? I am using CALL TRANSACTION method in the program.

Thanks in advance,

Neethu Mohan

[Former Member]

Hi All,

BDC for SAP transaction KKBC_ORD is running fine in foreground, but it is returning wrong values in background run.

What is needed to make it run fine in background? I am using CALL TRANSACTION method in the program.

Thanks in advance,

Neethu Mohan

[Former Member]

This message was moderated.

[Former Member]

It can be because of the asynchronous updates So use synchronous updates.

Just Update mode = S (Upd 'A' in call tCode'

Use:

Call transaction <TCODE> UPD 'S'.

Also type to check the screen resolution used in foreground and background

Regards,

Gurpreet

[dev_parbutteea]

Hi,

please give some more info on what is wrong and if possible paste the "call transaction" code part.

Regards.

[Former Member]

Hi ,

Please find the code part:

PERFORM bdc_dynpro USING 'SAPMKKB0' '0100'.

PERFORM bdc_field USING 'BDC_CURSOR'

'KKB0-AUFNR'.

PERFORM bdc_field USING 'BDC_OKCODE'

'=OSNY'.

PERFORM bdc_field USING 'KKB0-AUFNR'

wa_caufv-aufnr.

PERFORM bdc_field USING 'TIME_CUMU1'

'X'.

PERFORM bdc_dynpro USING 'SAPLSLVC_FULLSCREEN' '0500'.

PERFORM bdc_field USING 'BDC_OKCODE'

'=&F03'.

PERFORM bdc_dynpro USING 'SAPMKKB0' '0100'.

PERFORM bdc_field USING 'BDC_OKCODE'

'/EBACK'.

CALL TRANSACTION tcode USING bdcdata

MODE l_mode

UPDATE l_update

MESSAGES INTO messtab.

IMPORT g_t_kkbcs_out[] FROM MEMORY ID memid.

where tcode is KKBC_ORD

l_mode is 'A'

and l_update ' L'.

I tried with synchronous and assynchronousupdate mode , and these are not having any effects.

We have used EXPORT in the standard transaction and IMPORTed the internal table with values of Cost Analysis data got from transaction KKBC_ORD in the program.

While the program is executed in background, I noticed in debugging that the internal table is getting filled with wrong values even before EXPORT statement. So naturally when these values are imported to our program, it is giving the wrong values.

Thanks,

Neethu