Error in Control Framework at PC00_M99_HRF

[Former Member]

Dear Experts, We are facing issue with PC00_M99_HRF payslip generation as background jobs. We have total 3000 employee and we want to run it via background job because it goes timeout if we run as foreground. But if we run for few employee it run successfully and generate some adobe files at some location at users workstation. See the below screen.

But if we run it as a background job it getting cancelled immediately. the Error log of cancelled job is like below:

Date       Time     Message text                                                                                      Message class Message no. Message type

04.02.2016 11:18:43 Job started                                                                                            00           516          S

04.02.2016 11:18:43 Step 001 started (program /1PYXXFO/ZAFHPY_PAYSL_RAK_PRNT, variant &0000000000000, user ID GPAPAR)      00           550          S

04.02.2016 11:18:44 Error in Control Framework                                                                             FES          022          E

04.02.2016 11:18:44 Job cancelled after system exception ERROR_MESSAGE                                                     00           564          A

Can anybody help me to resolve this issue ?

Thanks

ASad

[ted_dinh]

Since you mentioned the output (pdf) file is created on the user's work-station, this means that the output of this is writing to a presentation server (e.g. user's PC), an not application servers. Since background job can't write to presentation servers, you get this error.

Please check if the user's default printer is set to write output to local file by any chance.

Rgds.

[Former Member]

hi ted dinh, Is it possible to change the forms attribute to save files at different location? Thanks Asad

[ted_dinh]

Normally, the output of this would go to a printer, not a file. First, please check if the user has his/her default printer set to save to a local file, and if that's the case, why does the output need to be saved to a file instead of being sent to a printer?  If it really needs to go to file, then check with BASIS group to see if they can set this up (i.e. define a printer that goes to an app server file instead).