bdc OK_CODE

[Former Member]

Hi all,

We have created a bdc program to load personal data(Infotype 0002) for an employee (TCODE PA30)

We are able to load the data in 200 client but we are not able to load the data in 600 client as it is giving error as 'No Batch Input Data for the Screen'.

If we run the bdc program in foreground mode, we found that OK-CODE pop up is not coming for save button.

Could you please guide us, why pop up is not coming ?

Thanks in advance.

Regards,

K.Tharani.

[Former Member]

Hi,

In the client 600, as you are able to do it manually, so do the recording using the transaction SHDB and check the screen flow generated with the existing one.

If it is specific and varies for client 600, then put a condition like when client is 600, populate the BDC TABLE separetely as required.

It will resolve your issue.

Regards,

Santhosh.

[former_member302911]

Hi,

the best way to resolve the problem is debug the program, open the bdc internal table while debug is started and press F6 until or before the ok_code for save is reached.

Angelo.

[Former Member]

Hi,

could you please copy the BDC code.

It should be like when you save.

eg:

PERFORM bdc_dynpro USING 'SAPMF05A' '0700'.

PERFORM bdc_field USING 'BDC_OKCODE'

'=BU'.

Regards,

Satish

Edited by: Meenugu Satish on Jun 24, 2009 4:25 PM

[martinborda]

Hi Tharani,

Error "Batch Input Data for the Screen'" in BDC is triggered when the screen flow is different that the one sent by program.

So, there's a screen that shows in client 600 that is not there in client 200.

The bdc program records in the BDCDATA table sth like this:

DYNPRO 1 ==> DYNPRO 2

(okcode 1) (ok code that is not running)

but in client 600 the screen flow must be different:

DYNPRO 1 ==> DYNPRO 3

(okcode 1)

You can check these in foreground mode, BDC executes every ok code in the specific screen (not other), but when it stops, there must be a wrong screen comparing to the screen flow you programmed: it cannot put the save ok code because it's not the screen you told it to do that.

[Former Member]

Hi,

The problem is solved.

The problem raised because the program name for a particular screen are different in both the client.

Thanks for all your guidance.

Thanks,

K.Tharani.