Create batch input, does not include all records

[former_member300655]

Have anyone experienced, when doing Create Batch Input from the LSMW menu it does not include all rows.

For example I have a .txt file with 3000 records that I specify in "Specify Files"

"Read Data" reads 3000 records.

"Convert Data" Converts 3000 records

"Create Batch input Sessions" creates 2461 records? ?

I have noticed that this happen when the system is busy running many batches and Idocs.

[JL23]

I have never see such an issue in all the years I am working with LSMW (and 3000 records is a small number in my environment)

Are you sure you dont mix records with transactions?

the read step counts records.

the conversion step shows number of records read, number of records written, number of transactions written

the step create batch input shows the number of transactions copied into the BI session.

[former_member300655]

(3000 was just an example.)

It is transactions like you said.

In the conversation step it says that 3000 records, and 3000 transactions converted.

But in the BI Session it only shows 2461 transactions.

I can not understand why there is a difference in the amount.

[JL23]

these 2461 transactions, are these transaction 1 to 2461 from LSWM and all transactions after these 2461 are missing.

Or do you miss transactions randomly?

Sometimes when you save a Excel file as a txt file then you can have empty lines in this text file.

SAP reads the empty lines, like any other line with data.

Maybe the last 339 lines were empty and creating the batch input omitted them.

[Former Member]

Or are the missing records simply errors from the batch input session?

Rob

[Former Member]

Hi ,

which LSMW object you are talking abt ,it totally depends how you created the batch input session.....

for exp...im loading condition records ...in the LSMW direct program.(RV14BTCI).. i have following options...

Max no records per transaction
Max. no. cond. recs per screen
Max no. scales per screen
Max. no. cond. recs in table

[Former Member]

Hi Dmoney,

sometimes there is issue that there are let's say 3000 records in read Data step but when they are converted there might be 2461 records or less.But this happens when we have put some validations in LSMW for a particular condition and used either SKIP_TRANSACTIOn or SKIP_RECORD in step 5 " Mapping and conversion Rules of LSMW.

I am not able to understand as to why till converted data it is coming fine.

If at all there are any validations it should have been filtered out at convert Data step only.

Experts,Please correct if i am wrong anywhere.

Regards,

Rahul

[former_member300655]

I'm talking about LSMW programs with regular Batch input Recording.

I haven't noticed which transactions it skips since I do not run the Batch, when I notice that it does not include all rows as I have read and converted.

However usually if I "Create the batch input session" once again it includes all the records from the conversion before.

But since Create a batch input can take a long time depending on the amount of transactions it creates this is not a desired option.

So it is not possible that the transactions it does not create are errors since its possible to run them successfully. And I haven't used any SKIP TRANSACTION in the mapping step.

But like I said this only happens when the system is running many batches / idocs at the moment, for example if we are loading the material master at the same time as I run my batch input programs.

[Former Member]

So, have you gone to SM35 to see if there were errors?

When you run multiple batches in parallel, there can be locking issues that don't appear when the transactions are run sequentially, one at a time. And the error sessions can then be successfully processed.

Rob