SSFCOMPOSER - 154 - No output request open. End not possible.

Question

Hi Experts,
I'm trying to print multiple smartforms using FMs SSF_OPEN and SSF_CLOSE. Inside the main program RBDAPP01 (Inbound processing for IDOCS) there is a loop at the IDOCS to be processed. Deep within the processing, we have a custom FM being called which prints smartforms. Since there is a loop at the calling main program, I have organized the code in the custom FM such that the first IDOC calls SSF_OPEN and the last IDOC calls SSF_CLOSE, so that all IDOCS in between will be able to print their smartforms. Here is the call stack:
8
SAPLZCUSTOM                   
ZCUSTOMPROGRAM                             
113
FUNCTION                     
ZCUSTOMPROGRAM                                         
7
SAPLPPC1                               
ZCUSTOMPROGRAM     
136
FUNCTION                     
KK2A_GET_DATA_FROM_IDOC                                     
7
SAPLPPC1                               
LPPC1U01                               
1
FUNCTION                     
KK2A_GET_DATA_FROM_IDOC                                     
6
SAPLBD20                               
LBD20F0A                               
454
FORM                         
IDOCS_PASS_TO_APPLICATION                                   
5
SAPLBD20                               
LBD20F0B                               
69
FORM                         
IDOCS_PROCESS                                               
4
SAPLBD20                               
LBD20U05                               
260
FUNCTION                     
IDOC_INPUT                                                  
3
SAPLEDIR                               
LEDIRU02                               
182
FUNCTION                     
IDOC_START_INBOUND                                          
2
SAPLBD12                               
LBD12U04                               
37
FUNCTION                     
APPLICATION_IDOC_POST_IMMEDIAT                              
1
RBDAPP01                               
RBDAPP01                               
388
EVENT                        
START-OF-SELECTION                                          
The problem is:
1. When I only have 1 IDOC being processed, SSF_OPEN and SSF_CLOSE happens in the custom FM at the same time. This creates a successful spool.
2. Whereas, when I have 2 or more IDOCS, SSF_OPEN happens in the first IDOC, but then it goes back to the calling program, and then when the last IDOC is encountered SSF_CLOSE is called. The FM SSF_CLOSE in this scenario calls the exception INTERNAL_ERROR (sy-subrc = 2).
The system message is SSFCOMPOSER - 154 - No output request open. End not possible.
Why is this happening? Is it because that other programs (calling programs) may have affected the status of SSF_OPEN? It seems that the SSF_OPEN is no longer open.
Thanks in Advanced,
Jack

Answer 1

No, it will not hold the smartform open, but you don't need to hold it open in order for printout to be accumulated in one spool. Spool system does the accumulation automatically, provided the spool requests that are to be added to an existing spool request are:
- generated in the same transaction and
- have the same attributes (such as user, title, output device, client from which the request was issued, number of copies, priority, cover sheet setting, archive mode, and ABAP session number).
Important is: where do OUTPUT_OPTIONS like printer come from currently? Is print parameters popup displayed on first Idoc for user to choose printer and options? Or do you use USER_SETTINGS = 'X' to simply take over defaults from user master? If the print options dialog is displayed, it needs to be controlled as well so it's displayed only once.
Assuming print options come from the user in dialog, the logic without explicit open/close could look somewhat like this:
On first idoc:
- call SSF_OPEN  importing  JOB_OUTPUT_OPTIONS to display print options dialog; move-corresponding JOB_OUTPUT_OPTIONS to global OUTPUT_OPTIONS;
- set OUTPUT_OPTIONS-TDNEWID = 'X' and clear  OUTPUT_OPTIONS-TDFINAL, to ensure new spool will be started (overriding user choices for these parameters!);
- if the user has set OUTPUT_OPTIONS-TDIMMED = 'X' save it globally and clear it;
- set CONTROL_PARAMETERS-NO_OPEN = 'X';
On subsequent idoc:
- clear OUTPUT_OPTIONS-TDNEWID;
- clear CONTROL_PARAMETERS-NO_OPEN;
On last idoc:
- set OUTPUT_OPTIONS-TDFINAL = 'X' (this is not absolutely necessary, but prevents further appending to the spool);
- restore OUTPUT_OPTIONS-TDIMMED from the value saved on first idoc;
Calling Smartform:
- set CONTROL_PARAMETERS-NO_DIALOG = 'X';
- call smartform passing OUTPUT_OPTIONS and CONTROL_PARAMETERS;
The logic is somewhat complicated; I'd wrap it in a class (singleton, which would be de-instantiated after last idoc) to avoid global data and code other than simple method call(s) in FM.
Even if you decide to refactor the logic, it would still be important to understand, I think, why the current logic does not work (where and why smartform gets closed)... Maybe there are some nasty "surprises" somewhere, and your current algorithm should work.
cheers
Janis