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

Batch input error in background mode.

Former Member
0 Likes
8,271

Hi all,

i am running a batch input session in background mode and getting an error. When I run it in foreground there is no error. What I am doing wrong?

Error 00349: Field XXX does not exist on screen SAPPKLPP0.

Help!!!

21 REPLIES 21
Read only

FredericGirod
Active Contributor
0 Likes
4,228

Hi Maria,

make a recording of your transaction with the transaction SHDB, and select the option "simulate background mode".

The screen are not the same between foreground & background mode.

regards

Fred

Read only

former_member585060
Active Contributor
0 Likes
4,228

Can you paste your code here.

Read only

satyabrata_sahoo3
Contributor
0 Likes
4,228

Are you trying BDC of any Enjoy Transaction codes?

Read only

0 Likes
4,228

The transaction is kp06

Read only

Former Member
0 Likes
4,228

Hi,

Are you getting any popup in during the foreground mode?

If you are getting one then you are not handling the popup.

Else, while executing the bdc in foreground mode check if you are going through the screen SAPPKLPP0 and if so check there is a field which is displayed in the error.

Read only

0 Likes
4,228

HI, the foreground mode is working without problem.

Read only

0 Likes
4,228

Hi Maria,

run your BDC in mode 'E'  stop when Error.

Take the dynpro name & the dynpro number, Go in SE51 enter the values, press F8 (simulate) that will give you the screen you failed.

A lot of time it's organizationnal value to be enterred, and you could bypass this value with a parameter ID set to the user (SU3)

and one time again, next time, run the transaction SHDB and active the option to simulate the background mode, you will not have this kind of problem !

regards

Fred

Read only

gaurab_banerji
Active Participant
0 Likes
4,228

when recording standard transactions simulate background mode else it will mostly throw error. this is because sap processes different screens in background mode for many standard transactions

Read only

Former Member
0 Likes
4,228

Additional information.

I had the same problem before while processing in  foreground. The problem was that for one fields data was taken from the user paramaters and filled automatically. Because it was not going to work with these data   I had '!' in my code to fill the field. It then worked in foreground.

The same problem is appearing in background. What to do?

Read only

Former Member
0 Likes
4,228

To fix the problem in foreground I had this line to my code:

Perform BCD_FIELD using 'KPPOB-VALUE(04)' '!'.

What can I add to make this work in background too?

Read only

0 Likes
4,228

What is the field name, is it Fiscal year or Cost center field?

Read only

0 Likes
4,228

To create a batch input session my report read a file. In this file I retrieve the information "Cost center". In the user parameter setting the field Cost center group is filled. Only one of them can used during the transaction processing. So I hided the field cost center group coming from the user parameter settings.

It worked in foreground but not in background processing.

The missing field in background. processing is : sender activity type

The field is shown in foreground processing

Read only

Former Member
0 Likes
4,228

Please keep posting. I havent found a solution yet.

Read only

0 Likes
4,228

What are you passing for Sender Activity in foreground mode?

Read only

0 Likes
4,228

The sender activity data are read from a file while creating the batch input session in my report.

Please keep sending answer. I need a solution for this.

It is all fine in foreground only the background mode is not working.

Read only

Former Member
0 Likes
4,228

Additional information:

I have tried again but the problem is coming in all processing mode: foreground, background, display error only.

- Field KPPOB-VALUE(15) does not exist in the screen SAPLKPP0

- No Batch input data for screen SAPLKPP0

Please keep posting. I need to fix this.

Read only

0 Likes
4,228

Do you try the recording with the SHDB simulate background mode ?

Read only

0 Likes
4,228

I dont understand your question. I am using a report to create the batch input session. The report read data from a file. I am having the error while processing the session in all mode: background, foreground, display error.

Read only

0 Likes
4,228

How did you know the screen, the field ... the sequence of the dynpro ?

To create a batch-input, the more simple is to use the transaction SHDB.

http://wiki.sdn.sap.com/wiki/display/ABAP/Batch+Input+FAQ#BatchInputFAQ-Recording%28SHDB%29

Read only

0 Likes
4,228

Hi Maria,

I guess in foreground mode also you are getting the same message 'Field XXX does not exist on screen SAPPKLPP0.' but as a success message, and so no problem and it is working fine.

But while executing it in background mode, the same will come as an error, and it will stop the session from execution.

I suggest to modify your BDC code to populate that particular field conditionally, only for cases the field appears on the screen. So that in the cases when the field not appears on the screen, then program also will not try to populate data on the screen for that field, and session will not be stopped even in background mode.

Thanks.

Read only

0 Likes
4,228

The field should always appeared on the screen and be populated. It has to be a programm error from SAP side.

I found a note on the SAP support page:

Note 1234774 - Cost planning: batch input sessions are terminated.

Error: 00344 "No batch input data for screen &&"

SAP strongly recommends not to use batch input programs for manual planning.

Cause and prequisite: this is caused by a programm error.

Solution (just a part): the program change is not contained in the standard system, since other already existing batch input programs can possibly not executed anymore.