Skip to Content
0
Former Member
Jun 17, 2014 at 12:58 PM

How to deal with generated programs in eCATT SAPGUI recording?

109 Views

Hi experts and professionals,

I am trying to automate testing of our solutions by eCATTs and so far i have not been able to find solution for following problem.

Whole test scenario is very simple:

  1. Check InfoProvider data (query, lookup, listcube,...)
  2. Create DAP on InfoProvider
  3. Archive InfoProvider
  4. Check InfoProvider data (query, lookup, listcube,...) again
  5. Compare results from step 1. and 4. (must match)
  6. Reload archived data
  7. Check InfoProvider data (query, lookup, listcube,...) again
  8. Compare results from step 1. and 7. (must match)

As you can see, one of the required test steps is to check InfoProvider's data in transaction LISTCUBE.

But transaction LISTCUBE generates its program "name" every time it is executed and

I am struggling to find a way how to deal with these generated programs in eCATT SAPGUI recording.

Key is that solution must be generic and work for all SAP BW releases from 7.0 upwards

(having in mind that LISTCUBE can read NLS data from SAP BW 7.3 release).

Error description from eCATT log:

Screen Check Error: Expected Transaction: LISTCUBE, Actual Transaction: LISTCUBE.

Expected Program: GP0KOZE7EFIUBN10MZUFWX90W80, Actual Program: GPBP24INA6VV77SL0XKU5NA642O.

Expected Screen Number: 1000, Actual Screen Number: 1000.

There Is Probably an Error in SAPGUI recording.

ExceptionClass:CX_ECATT_APL_CAPTURE ExceptionId:SCREEN_CHECK_ERROR

RaisingClass:CL_APL_ECATT_LINE_INTERPRETER Include:CL_APL_ECATT_LINE_INTERPRETER=CM00J Line:443

Is there any way how to avoid program check in eCATT script?

Anything that would help me to find solution will be greatly appreciated.

Best Regards,

Igor