Report canceled with message 'No forms available',

[Former Member]

We are stumped.

I created a simple ABAP HR report using the PNP logical database. It pulls benefits info and master data for displaying on the screen. (Associates Eligible for FMLA) No ALV grid, just a simple write to the screen.

The job runs fine in in the background as well as foreground in DEV, QAS, and STA .

But now that the program is in PRD, when we run it in BACKGROUND, the job CANCELS after 10 minutes.

The spool lists the message 'No forms available', several dozen times, and then 'No memory for cua processer'.

Oddly, the program runs fine in forground.

Any clues how I can get this program to run in background?

[Former Member]

Hi,

Check the statements prior to the 'No forms available' message display.

Are you using some 'Check statements', are you checking for any SY-BATCH value or checking the SY-MANDT field in your code.

Regards

Subramanian

[Former Member]

Job log Messages:

12:48:38 Job started

12:48:38 Step 001 started (program ZPRCR_DISABILBITY_ELIGIBLE)

12:48:50 No forms available

" " " "

12:57:47 No forms available

12:57:48 No memory for cua processor

12:57:49 Job canceled

-

---

I looked at the code and there are no ABAP 'check' statements, nor reference to sy-mandt.

There is code in the 'at selection-screen' section that puts out a warning if the program is ran in foreground without a date.

  if pn-begda is initial and sy-batch is initial.
    message e000(zpa) with 'Please enter a run date'.
  endif.   

Other than that, the program runs fine in foreground in PRD, but cancels in background. The same code runs fine in foreground and background in all our other clients. Our BASIS group is stumped too.

Thanks

Doug

[Former Member]

Have you checked the Dump Analysis (ST22) to see if there is a dump for the "no memory" message"?

Rob

[Former Member]

HI,

Can you please check the Date format of the user and also the Format of the field which is giving the error.

Regards

Sudheer

[Former Member]

Mystery solved!

The user running the report in PRD did not have the security authorization to run the job in background.

Once that was granted, the job finished without a problem.

Thanks for your suggestions!

Doug at Publix Super Markets