sequence missing issue while printing bulk deliveries units through Zebra printer

[ratnakar_potineni2]

HI SAP Experts,

We are facing a sequence missing issue while printing bulk deliveries units. These issues started recently, when we are trying to print a stack of delivery units.

Issue:

1) When user is printing like 80 - 100 delivery units, The sequence is missing between delivery numbers. Ex: It is printing delivery number 30 ,1 of 5 label , then 2 of 5 label . Then it is picking delivery number 58th 7 of 7 & 6 of 7 label and then it is starting back to delivery number 30, 3 of 5 and 4 of 5. Which is causing users to spend lot of time to segregate from stack of more than 1000 labels.

It is not happening on regular basis, This is happening randomly, whenever we give more than 40 delivery units at a time.

2) We are using customized program for printing these delivery units, Which my developer confirmed that they are using SAP Standard program with customize selections options.

3) All these labels were developed using SAP SCRIPT.

Our current Printer setup and printer used: Zebra 110Xi4 203dpi

1) We are using Host spool Access method as: "S" - Using windows host spool server.

2) From SAP - It goes to Windows host spool server - from there it points to our zebra printer.

Steps taken so far to overcome this issue:

1) We have enabled process request sequentially in SPAD.

2) We have increased our CPU /Memory/Configuration in our windows spool server.

3) We have upgraded our SAP Sprint services in our windows host spool server.

4) We make sure that enforce serialization option is checked in SAP print option editor in windows spool server.

5) Currently our option for "use separate thread for job reception” is checked, as per note 1054561, we unchecked and tried, It became more disaster by slowing the prints and still we see missing sequence issue.

6) We checked with our network team, If there is any network glitch, They have confirmed that there is no issue or communication issue between SAP - Windows spool server and printer.

I have attached the document with current printer setting and SP01 screen shot when we see missing sequence issue.

It would be great help, if you can give your wise inputs.

Thanks

Ratnakar Potineni

[former_member585891 · Accepted solution]

Hello Ratnaka.

The mentioned configurations are correct, as they are described in Note #1054561.

However, the application is responsible for the creation of the spool requests. In rare cases it could happen that the output sequence is lost even if SAPSprint processes the requests in a correct order. SAPSprint puts the print jobs into the OS queue and what happens afterwards is a Windows/printer driver specific.

A workaround can be made, but could be troublesome as lots of configurations are needed. If setting option 'Use separate thread for job reception' is an issue then you could move the effected devices to their own SAPSprint server where the options are set and only effect the printers that need this.

Ultimately, if you require a correct sequence, the spool requests must be created by the application process sequentially in one SAP process.

I hope the mentioned information was helpful.

Best regards,
Bálint Ujvári
SAP PS

[ratnakar_potineni2 · Accepted solution]

Thanks Balint for your time and inputs. Currently with help ABAPer , We are pooling all the small spool request as 1 request and printing . But i am assuming this is not the right work around.

[ratnakar_potineni2]

HI Balint

Thanks for the inputs. Assuming the parameter value rspo/global_shm/job_list fixed the issue 300 to 1400.

Scenario 1: We have reduced the WP from 3 to 1 and parameter value :rspo/global_shm/job_list from 300 to 1400.( Sequence came out properly but performance was very slow).

Scenario 2: We have maintained 3 WP and parameter value :rspo/global_shm/job_list from 300 to 1400.( Sequence came out properly but there were few blanks labels in between).

We are still testing the different scenario with various load. Will keep you posted with the approach . Thanks for your help and inputs.

Thanks

Ratnakar

[former_member585891]

Hello Ratnakar,

Please check Note #2233300 and #118057-"Flexible Configuration of the Spool Service". The SPO wps can be 'tuned' to get a better.

You can also adjust the application that generates the huge spool load so that it will not release that many spools at once.

Best regards,
Bálint

[former_member585891]

Hello Ratnakar,

Please check Note #2233300 and #118057-"Flexible Configuration of the Spool Service". The SPO wps can be 'tuned' to get a better.

You can also adjust the application that generates the huge spool load so that it will not release that many spools at once.

Best regards,
Bálint

[ratnakar_potineni2]

HI Jaya,

Thanks for your time and inputs. We are not maintaining any load balancing in spool server. I have pointed to single application server only .As mentioned this issue is happening only when we give multiple 80 - 100 deliveries which prints close to 1000 labels.

Currently all my CI and APPS server in production has 3 spool work process , I am thinking to reduce spool work process from 3 to 1 and also would like to increase the following parameter value rspo/global_shm/job_list from 300 to 1200 . Please share us your thoughts on this approach and let me know the value in your systems. Appreciate your time and inputs.

I am currently seeing following errors in my WP trace file while giving prints :

S *** ERROR => overflow of internal job queue [rspowunx.c 1005]

[vkjpbasis]

Hi Ratnakar Potineni

We also had a similar issue the during label printing where the spool server configured __AUTOSPOOLSERVERin SPAD for the output device TEST_lable_print and its randomly few labels where printing and few labels was not printing / missing.

Reason: - Not all the application servers configured with Label print file system, so the printing happened only to the application server where the label file system mounted and rest of the application server printing is not happening / missing

Please check is the similar issue in your scenario, or change the spool server only to CI and test the sequence of printing

Regards

Jayaprakash Kuppusamy