Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor
0 Kudos

Normally there're three methods to print out one Smartforms:

  1. Print out directly without preview and no print setting popup window;

  2. Print out with the Print button at the print setting popup window;

  3. Print preview button at the print setting popup window, then Print button at the print preview screen.

For point 3, the standard program of NAST processing already considers this potential leak point. And the solution is simple and effective: just grey out the print button on the print preview screen.

To achieve this grey out for the customized programs, may need to do some implicit enhancement to include LSTXBWFCC (check this).

But what if the user wants to keep the print button on the print preview screen for some customized printouts separated from NAST processing? Then how to fetch the status of the SmartForm printout if further actions like customized DB updates must be carried on when the user clicks the print button at the print preview screen? If the user clicks BACK to the caller program after printout at the print screen, then no issue as the caller program can get all user command at that time. What if the user closes the preview window after printout at the preview screen?

The solution is also simple:

  1. The field SSFCRESCL-OUTPUTDONE will return whether a printout occurs or not from preview windows.

  2. The field SSFCOMPOP-TDIEXIT will Immediately exit after printing/faxing from the print preview, the user has no chance to close the print preview window after clicking the print button.

There're lots of other control parameters that can be used for various purposes. After so many years, I am still not aware of most of them : P

Labels in this area