Customized transaction type not working

[Former Member]

In Change Request Management, we have copied a transaction type from "Normal Correction" and tried to customize it. We have also copied a new action profile for this new transaction type. And copied exactly the same action conditions. However, when I trigger action "Set to 'In Development' " and save the change. Status of the message does not change to "In Development" as "Normal Correction" did.

Is there any setting missing that I should do?

[former_member349105]

Hi Martin,

which status value you have put in Method Call for this action?
The method call value should be " In Development "(E00*).

Please check and let me know if you still have any issue.

Thanks

Gaurav Patel

[Former Member]

Hey Martin,

First of all did you register the new transaction type as Change transaction.

How to ??

Ans:

Go to spro->solution manager img->Scenario specifc settings->change req management-> extended configuration-> Assign implementation to change tranasction type.

Notice the the normal correction is registered there.

Similarly you have to register your new created transaction type.

After doing this check out whether it works.

If it doesnt, revert back.

Reward points for usefull answer.

[former_member209604]

Hi Martin,

have you followed the instruction in the IMG, when copying the transaction type?

IMG: SPRO -> Configuration -> Scenario-Specific Settings -> Change Request Management -> Important Information

See copy of the IMG activity below:

1. IMG ###########################

<i>Important Information</i>

Before you start to configure Change Request Management, make sure that you have performed all the Solution Manager IMG activities under the following nodes:

Solution Manager -> Basic Settings

Solution Manager -> Scenario-Specific Settings -> General Settings

When you copy the standard Change Request Customizing into customer namespace, you should just change the first character to Y or Z e.g. SDCR -> YDCR or ZDCR but not Z1CR, if you change more characters you should be aware that modifications will be necessary and it is not standard SAP. This restriction is required for all CRM related objects like catalog, transaction type, status schema ...

##############################

Ruediger