The print or archive parameters required by the user for a report within a background job do not work.
Numerous.
SolutionTo test which print or archive parameters are used by a report which is starting within a background job, proceed as follows:
- Define a job using transaction SM36 or using the function modules JOB_OPEN / JOB_SUBMIT / JOB_CLOSE which execute the test report 'RSBPTP03' as the only step.
- When defining the step, enter the required print parameters (in SM36 or with FM JOB_SUBMIT). When using the FM JOB_SUBMIT, take care that the print or archive parameters are determined using the FM GET_PRINT_PARAMETERS (do not fill the parameters ARCPARAMS and PRIPARAMS 'manually').
- Choose 'Immediate' as start date in SM36 and save the job or set the parameter STRTIMMED = 'X' in the FM JOB_CLOSE.
- Go into the job overview (transaction SM37) and select the job just started.
- Display the spool list generated by the job. There you can find the print or archive parameters which 'arrived' in the test report RSBPTP03.
- If these parameter values do not correspond to the ones you need, check the values set in the job definition again. When using the FM JOB_SUBMIT, the error is frequently made that the parameters ARCPARAMS and PRIPARAMS are set 'manually'. The correct way is to call the FM GET_PRINT_PARAMETERS before calling JOB_SUBMIT and to transfer the values returned by this FM directly to OUT_ARCHIVE_PARAMETERS or OUT_PARAMETERS and JOB_SUBMIT.
No comments:
Post a Comment