Function RS_TESTREPORT_GENERATE

[former_member185171]

Hi,

since we upgrade to 7.40 there seem to be some changes to function module RS_TESTREPORT_GENERATE.

There are some authority-checks added and it is called on a condition we don't understand in CHECK_REPORT_GENERATE

    elseif trdir-vern <> c_testprog_version .

      perform gu_generate_testprogram using p_function

                                            testprog.

      was_generated = 'X'.

    else.

What is the meaning of this c_testprog_version? It has value '18' but in are system (view PROGDIR) most of the entries have a lower value?

Is there some conversion necessary?

Thanks for any info.

Kris

[Former Member]

Hi Kris,

If you can see the declaration of c_testprog_version the value has been defaulted to '17'. If it is not equal to '17' then it is not a test program

DATA: c_testprog_version LIKE trdir-vern VALUE 17.

I don't think any conversion needed for this since it is to check whether the version has to generate for each version or not. If the version is '17' then it won't go for creation of any new generation.

Thanks,

Siva

[former_member185171]

That is exactly the issue. In ou system this constant has the value '18' and a lot of entries have value '17' ...

data: c_testprog_version like trdir-vern value 18.
data: c_testpattern_version type i value 32.

if sy-subrc <> 0.
  perform gu_generate_testprogram using p_function
                                        testprog.
     was_generated = 'X'.
elseif trdir-vern <> c_testprog_version .
  perform gu_generate_testprogram using p_function
                                        testprog.
  was_generated = 'X'.
else.

I have no idea what it could mean.

Kris

[Former Member]

I suggest you to check with the functional guy, might be it is a configuration issue. Let the functional guy come back on this issue then we will surely have a right fix for this issue.

Thanks,

Siva

[former_member201275]

I don't have the answer for you, but in my opinion it seems to be related to security around authorisations, rather than config, so I would approach the security team. I may be completely wrong though.