Following things you must keep in your mind. Actually implementation of a successful SAP printing depended upon only on a good and sustainable policy. This job is being done by infrastructure consultant (only purchasing and installation) and SAP Basis consultant (configuration of spool and/or SAP user Configuration) and/or SAP Security consultant (SAP user Configuration). but main thing is to create policy and look into following three aspects, do some little forecasting and then publish and abide by.
1. From the very beginning deploy a policy to use only the enlisted hardware from SAP. This will be slightly tough to make people agree with, but it will help minimize the operational cost.
2. Decide from very beginning, whether you want to keep spool in database or in file system. If your volume is very high and spread-ed over WAN on the locations without direct IT operation support, I will prefer database storage. Otherwise I will prefer the filesystem storage. Second option will give you faster printing, but SAP do not guarantee to support all kind of spool issues if stored in the file system. <a href=”http://soumen.wordpress.com/2009/12/15/tuning-sap%E2%80%A6is-spool-configured-correct-%E2%80%A6decide/”>You may refer here also for initial pointers</a>
3. From the very beginning, please also enforce a policy, to “delete spool immediately after printing”. This should be adhered by Basis and SAP security person, strictly. Doing so you will always have less quantity of spool to be managed. this will in turn ensure a better and healthy enqueue system, lesser down time and finally less storage place.