cancel
Showing results for 
Search instead for 
Did you mean: 

How to setup QA approval in D system

Former Member
0 Kudos

Hi,

We have a three-system landscape (D -> Q -> P).

My requirement is -

When I release a TR from D system, it shoud go into D system queue worklist.

Once I approve the same, it should be available in Q system STMS import queue for import.

This is like I want to implement QA approval in two-system landscape.

Wherever I have checked so far, I can see solutions for implementing the QA approval system in Q system but not in D system.

Can anyone please help me here.

Thanks.

Accepted Solutions (0)

Answers (1)

Answers (1)

TomCenens
Active Contributor
0 Kudos

Hello Anisha

Acccording to what you are requesting I think it's best you take a look at [change request management |http://service.sap.com/changecontrol] also called CHARM in short.

It will enable you to put specific roles for users which can give the effect you would like.

Another possibility is that person X creates a transport request with task Y where task Y is assigned to another person Z.

Where X is the person who needs to approve the release of the transport request and Z is the person who does the customizing change or development and places it in task Y.

You can then use authorizations so that person Z cannot release transport request Y.

Person X can then release the transport request when he approves the change.

Such manual actions can be done using Change Request Management in a nice interface with defined roles for users along with other additional functionality compared to regular CTS. You should view Change Request Management as an upper layer above the regular CTS.

Kind regards

Tom

Former Member
0 Kudos

Thanks Tom.

We cannot roll out CHARM functionality in our systems right now due to client requirement and plan constraints.

The other solution seems fine but then it will create dependencies.

Is there any other way via which we can configure this in the system?? The way we can for Q systems.

Thanks.

TomCenens
Active Contributor
0 Kudos

Hello Anisha

Doesn't an approval list create a dependency ? If the same person does the approval it becomes obsolete. Then your approval is the fact that you release your transport request.

I don't see a good reason why you want to achieve this.

Kind regards

Tom

Former Member
0 Kudos

Hi Tom,

If a person is approving TRs, he only needs to goto the QA worklist, select TRs (Example 50) in bulk and approve them.

But if he releases these many TRs one-by-one, he needs to go into each request and release it which is highly time consuming.

REASON FOR ACHIEVING THIS -

We have some pre-checks to do (as per client) and after these pre-checks only we import TRs into our Q systems. If any TR doesnt fit into these pre-checks, we reject the TRs. Hence, right now we check a TR and then import it in Q system.

To make all this automatic, we need to QA approval so that a person can check TRs and approve the ones that follow the standards. The approved ones will then get auto-imported in Q system.

Thanks.

TomCenens
Active Contributor
0 Kudos

Hello Anisha

Sounds like you would be better off with an additional SAP system in front of your productive SAP system.

D --> Q --> PreProd --> Prod

Normally you let developers make their development in D without complicated checks as you describe.

Then if you see there are issues with the transport request after import in Q you will not approve the transport request to be listed in the import queue of production through your approval list.

The process then is to build a new transport request (and not do anything anymore with the transport request that was denied) that includes the fix or corrects the prerequisite that was wrong and follow the process again.

Using CTS projects is a good idea if not yet used, it's easy to setup and it's good at keeping together transport requests.

You can define simple CTS project using transaction SPRO_ADMIN and after setting a title and saving you can enable them for use in CTS.

In customizing you can put setting that it's obligated to use CTS project when creating a transport request.

In fact almost all CHARM functionality exists and is possible through customizing settings but since it's much more work do set the customizing manually it's more useful to have an interface that does the appropriate steps for you.

If it's not yet what you seek you should give more detailed information on what kinds of checks you wish to perform, perhaps customizing setting exist for it.

Kind regards

Tom

Former Member
0 Kudos

Thanks again Tom.

Having a pre-prod is good but right now we are checking if this can be automated with existing systems only.

We already use CTS projects and have auto-import set for some systems based on them as well.

The pre-check is a TR description. Everything about a TR (its module, its issue etc) is derived from this description. There is a proper format under which you give this description. Any TR that doesnt follow this description standard is rejected.

We want that a person goes to queue, checks TR descriptions and approve the ones which follow standards.

We cant put QA approval in Q because there is no point in rejecting TRs after they are successfully tested in Q system and they are ready to be moved into production.

Hope this justifies.

TomCenens
Active Contributor
0 Kudos

Hello Anisha

Perhaps a solution for you would be to use custom attribute values for your transport requests.

In transaction SE03 under Display/Change Request Attributes you can create new attributes ZMODULE, ZISSUE and flag them as being required (this can be done per client and so on). This will force the developer to have to fill in those attributes for the transport request and thus it should also solve the issue of the manual checks each time.

It doesn't take away the fact that a user can still make typos or not do his job but having to review every word someone types seems like a serious overhead.

I don't directly find a possibility to restrict the values entered by means of a list of possible values but at least it can force them to fill in details.

Kind regards

Tom

Former Member
0 Kudos

We can implement all this to avoid mistakes.... but as you said, there can be manual mistakes.

We finally cannot implement QA approval in a D system, right??

TomCenens
Active Contributor
0 Kudos

Hello Anisha

I think you can but you need to take into account the fact that a QA approval list is used when a transport request is to be added to the import queue.

This is not the case when you release a transport request.

Perhaps you could try to use transport route from client XXX in Dev to client YYY in Dev and not yet to Quality and approve the transport request through the QA approval list because it's in the import queue for client YYY.

Then create a transport route from client YYY in Dev to QA so that after import into client YYY which requires approval the transport request is added to the import queue of QA.

Although it's not great practice in my opinion to have to check word by word of someone's work.

Kind regards

Tom

Former Member
0 Kudos

Hi Tom,

I will check the feasibility of this option.

Thanks a lot for the inputs

Thanks,

Anisha