If an urgent change you have made in a production system is also relevant for other, parallel production systems or for another productive client in the same project, you can distribute it to them with the ”Distribute change” action. The system creates a new urgent change containing the data of the original urgent change, and transports the corrections to the specified system.
To activate this functionality for the SAP standard transaction type for urgent changes (SMHF), make the following settings:
In Customizing for SAP Solution Manager, under Inactive
flag for the action definition SMHF_DISTRIBUTE.
In Customizing for SAP Solution Manager under
, activate the action definition SMHF_DISTRIBUTE.In Customizing for SAP Solution Manager under
, assign the following Customizing settings for consistency checks to the user statuses of your process.User Status | Sequence | Consistency Check | Application Area | Message Number | Message Type |
To Be Tested | 60 | DISTRIBUTOR | CHM1_ACTION_LOG | 057 | Information |
Successfully Tested | 60 | DISTRIBUTOR | CHM1_ACTION_LOG | 057 | Information |
Authorized for Production | 60 | FATHER_IS_PRODUCTIVE | CHM1_ACTION_LOG | 063 | Cancel |
Authorized for Production | 70 | DISTRIBUTOR | CHM1_ACTION_LOG | 057 | Information |
Note
DISTRIBUTOR consistency check: The system checks the condition to see whether a transaction that is to be distributed is assigned to the urgent change. If this condition finds a distributed change, the system displays the message CHM1_ACTION_LOG 057.
FATHER_IS_PRODUCTIVE consistency check: The system checks whether the transport request of the urgent change from which the distributing urgent change was created has been imported into the production system. If so, the system displays the message CHM1_ACTION_LOG 063.
To activate this functionality for your customer-specific urgent change transaction type, make the following settings:
If you have copied your urgent change transaction type from the standard transaction type before SAP Solution Manager 7.1 SP08, create a PPF action in the PPF action profile, with the same settings as the SMHF_DISTRIBUTE action. The name of your new PPF action must contain the character string DISTRIBUTE, for example, ZMHF_DISTRIBUTE_NEW.
If you have copied your urgent change transaction type from the standard transaction type in SAP Solution Manager 7.1 SP08 or higher, the system automatically copies the action SMHF_DISTRIBUTE, to [XX]HF_DISTRIBUTE. Activate this PPF action in Customizing for SAP Solution Manager, under
.In Customizing for SAP Solution Manager under
, assign the following Customizing settings for consistency checks to your customer transaction type to the user statuses of your process.User Status | Sequence | Consistency Check | Application Area | Message Number | Message Type |
To Be Tested | 60 | DISTRIBUTOR | CHM1_ACTION_LOG | 057 | Information |
Successfully Tested | 60 | DISTRIBUTOR | CHM1_ACTION_LOG | 057 | Information |
Authorized for Production | 60 | FATHER_IS_PRODUCTIVE | CHM1_ACTION_LOG | 063 | Cancel |
Authorized for Production | 70 | DISTRIBUTOR | CHM1_ACTION_LOG | 057 | Information |
When an urgent change has status “Successfully tested”, you can choose the “Distribute change” action.
The system displays all production systems into which the change can be distributed.
After selecting a production system, the system confirms that the change has been distributed. The IBase and the data for developer, tester, IT operator and change manager are copied into the new urgent change.
Note
When the action triggers the import of the distributed urgent change, a downgrade check is performed. For more information, see Downgrade Protection.