Is there an option to verify the content in QATEXT upon transport release in STMS_QA?

[BaerbelWinkler]

Hi All!

Several years ago, I implemented BADI CTS_REQUEST_CHECK in order to verify that a transport can only be saved when its title contains certain "key words". This is working quite nicely and has improved the quality of the transport titles considerably, making it for example easy to trace a transport back to the original request for the change (we don't use CHARM or any other tools).

Now, I would like to implement a similar check later in the process, namely when transports are released to production in STMS_QA. I would like to ensure that the reason text contains some agreed upon content, like a reference to documented testing of the change.

The field QATEST is what I'd like to check

Is there a user exit or BADI within STMS_QA or another option to implement such a check? I already tried finding something online but wasn't successful.

Update (Jan 31): the content entered in the pop-up ends up in table TMSQNOTESH and field TEXT and we would like to ensure that it contains some mandatory content.

We are on NW7.50 with EHP8

Thanks much and cheers

Bärbel

[Ryan-Crosby]

The two interface methods for checking before release are not suitable?

[BaerbelWinkler]

@Ryan-Crosby 

Hi Ryan,

aren't the interface methods not just available in development and SE10? What I'm looking for is a check in STMS_QA during QA-approval in the test/consolidation system.

Cheers

Bärbel

[Ryan-Crosby]

Aha, I misunderstood the query.

[BiberM]

Hi Bärbel, 

I know that you asked for something different. But still I want to stress out the checking before release:

If you check naming only before Import, the name cannot be change any more and therefor the whole transport has to be replaced creating New versions in the Dev system(s). If you block the Request upon release this cannot happen. 

[BaerbelWinkler]

Thanks - we don't have issues with the transport titles themselves but would just like to verify that a meaningful text gets put into the QATEXT field upon release to production which ends up in table TMSQNOTESH and field TEXT.

I tried to clarify my initial question.