cancel
Showing results for 
Search instead for 
Did you mean: 

No able to create TO in background with transaction LB10

Former Member
0 Kudos

Scenario:

1) LP21 to create Repleninshment TRs for fix bin

2) LB10 to convert the TRs to TOs

Situation:

When I click on create TO in foreground, following by F6 (stock removal background) it follows my search strategy and it works.

BUT when I select the TR and click on TO in Backgroung (see picture below)

I receive the follwoing message: No batch input data for screen SAPLSTXC 0100

Thank you

Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

Looks like you have no settings for printing

.

go to transaction SE51 and enter program SAPLSTXC with screen 0100

select Screen painter and click display to see how the screen looks like.

Former Member
0 Kudos

Thank you.

I did my print control config. It picks it up when I create it in foreground.

What would be the next step?

JL23
Active Contributor
0 Kudos

Can you post this screen filled with data when processing in foreground.

You really do not enter anything manually here ?

All printing is setup in OMLV?

Former Member
0 Kudos

http://You are right Jurgen. There is not printer defaulting here.

I had to enter a printer (LOCL) manually for the TO to automatically print in foreground processing.

I checked my OMLV configuration, I compared it to a Sandbox environnment that for some reason prints well and they are the same.

So what else can it be that does not populate a printer in the output device field?

I checked SPAD also. It seems ok too.

Thanks again.

JL23
Active Contributor
0 Kudos

Please use LX31 and enter warehouse and TO number to analyze the printer determination.

Answers (1)

Answers (1)

mihailo_sundic
Active Contributor
0 Kudos

Can you try if report RLAUTA10 works for you?


After doing LP21, instead of LB10 use SE38 => RLAUTA10.

Get back with the results.

Former Member
0 Kudos

Thanks all for your help. Special thanks to Jurger for your guidance.

The reason why it did not populate the printer was that the printer was not manintained in SU3 in that environment with the user I was testing. Lesson learnt!