You can adapt your existing system configuration for the normal change process, to be able to use the preliminary import function.
Note
This procedure is only relevant if you have been using the normal change process in your SAP Solution Manager system before the preliminary import function was introduced, by copying the standard normal change transaction type into your namespace.
When you create a new user status, the system generates a new technical number. In the SAP standard delivery, the preliminary import function introduces four new user statuses, with technical numbers ranging from E0011 to E0014. As these numbers might already be in use by your customer-specific user statuses, you have to adapt the user status profile manually.
In the SAP standard delivery, the preliminary import function is a side-process starting in the standard user status “Tested Successfully” (E0004) and returning status “Imported into Production” (E0006) to the user. You have to analyze the equivalent user statuses in your user status profile, as they are the start and end point in your process.
If you use your own authorization keys in your customer-specific user status profile for the normal change, create four new authorization keys.
In Customizing, choose
.Choose
and change to edit mode.Select the authorization keys SMMJ_04
, SMMJ_05
, SMMJ_06
, and SMMJ_07
.
Choose Copy
.
Adapt the standard authorization keys to your namespace.
In Customizing, choose
.Select your normal change status profile, and choose Details
.
Insert four new user statuses, based on the SAP standard preliminary import user statuses, as follows:
The preliminary import user statuses should have a status number between the start and end user status numbers identified in the process, so they should be between the user statuses for “Successfully Tested” and “Imported into Production”.
In the Status
field, enter the same values as in SAP standard.
In the Lowest
, field enter the user status number of the “In Development” user status (or the equivalent customer-specific user status).
In the Highest
field, enter the number of the next preliminary import user status, to only reach the next user status. The last user status, “Released for Import”, should have the status number of the “Imported into Production” user status (or customer-equivalent user status).
Add the newly created authorization keys to the user statuses.
Save your entries.
Note
The system automatically creates new EXXX status numbers for your new user statuses. You can display them in table TJ30, in transaction SE16. In the STSMA
field, enter the name of the normal change status profile. The system displays all technical user statuses for the status profile.
The following table shows the placeholders for the customer-specific user status, as used in this documentation:
SAP Standard User Status Description | SAP Standard User Status | Placeholder for Customer-Specific User Status | Authorization Key |
---|---|---|---|
Preliminary Import Requested |
|
| <Transaction type>_X1 |
Test for Preliminary Import |
|
| <Transaction type>_X3 |
Tested for Production Import |
|
| <Transaction type>_X4 |
Released for Import |
|
| <Transaction type>_X5 |
Adapt the roles in authorization object B_USERSTAT
, in transaction PFCG
.
User status | Authorization key | Role |
---|---|---|
| <Transaction type>_X1 | All roles used in Change Request Management |
| <Transaction type>_X2 | Change Manager, System Administrator |
| <Transaction type>_X3 | Tester, System Administrator |
| <Transaction type>_X4 | IT Operator, System Administrator |
To create the PPF actions that set the user statuses, and to adapt old PPF actions, in Customizing, choose
.Create the PPF actions in the table with HF_SET_STATUS
implementation, container element USER_STATUS
, and the values listed in the table. You can also copy another PPF action with the HF_SET_STATUS
implementation, but the texts in all languages are copied with it.
Action Definition | Sets User Status (in PPF container element | Further PPF Container Element | Definition of Container Element |
---|---|---|---|
<Transaction type>_REQUEST_PRELIMINARY_MJ |
| ||
<Transaction type>_APPROVE_PRELIMINARY_MJ |
|
|
|
<Transaction type>_CONFIRM_SUCC_TEST_MJ |
| ||
<Transaction type>_AUTHORIZE_PRE_IMPORT_MJ |
| ||
<Transaction type>_CANCEL_PRELIMIN_IMPORT_MJ |
| ||
<Transaction type>_DIRECT_PRLIMINARY_APPR_MJ (not relevant for SAP Solution Manager 7.1 SP07 and above) |
| ||
<Transaction type>_SET_BACK_TO_DEVELOP_MJ (not relevant for SAP Solution Manager 7.1 SP07 and above) |
|
|
|
<Transaction type>_IMPORT_NC_INTO_PROD_MJ |
|
You can compare your Customizing entries to the standard action (SMMJ_...in the PPF action SMMJ_ACTIONS action profile).
Note
Since SAP Solution Manager 7.1 SP07, action <transaction type>_DIRECT_PRLIMINARY_APPR_MJ has been replaced by <transaction type>_APPROVE_PRELIMINARY_MJ, and <transaction type>_SET_BACK_TO_DEVELOP_MJ has been replaced by <transaction type>__TESTED_AND_NOT_OK, by adopting the PPF conditions of the replacing PPF actions.
In Customizing, choose
.Choose Schedule Conditions
, and make the following entries:
PPF Condition | Schedule Condition |
---|---|
<transaction type>_REQUEST_PRELIMINARY_MJ | &CRM Service Process.User Status& [*] E0009++MJHEAD and &CRM Service Process.ErrorFreeFlag& = X (or equivalent user status for “Tested Successfully”) |
<transaction type>_APPROVE_PRELIMINARY_MJ |
|
<transaction type>_CONFIRM_SUCC_TEST_MJ | &CRM Service Process.User Status& [*] EXXX2++++HEAD and &CRM Service Process.ErrorFreeFlag& = X |
<transaction type>_AUTHORIZE_PRE_IMPORT_MJ | &CRM Service Process.User Status& [*] EXXX3++++HEAD and &CRM Service Process.ErrorFreeFlag& = X |
<transaction type>_CANCEL_PRELIMIN_IMPORT_MJ (not relevant for SAP Solution Manager 7.1 SP07 and above) | &CRM Service Process.User Status& [*] EXXX2++++HEAD or &CRM Service Process.User Status& [*] EXXX3++++HEAD or &CRM Service Process.User Status& [*] EXXX4++++HEAD |
<transaction type>_DIRECT_PRLIMINARY_APPR_MJ (not relevant for SAP Solution Manager 7.1 SP07 and above) | &CRM Service Process.User Status& [*] E0009++++HEAD and &CRM Service Process.ErrorFreeFlag& = X (or equivalent user status for “Tested Successfully” instead of E0009) |
<transaction type>_SET_BACK_TO_DEVELOP_MJ | &CRM Service Process.User Status& [*] EXXX2++++HEAD and &CRM Service Process.ErrorFreeFlag& = X |
<transaction type>_IMPORT_NC_INTO_PROD_MJ | &CRM Service Process.User Status& [*] EXXX4++++HEAD and &CRM Service Process.ErrorFreeFlag& = X |
<transaction type>_TESTED_AND_NOT_OK_MJ | Starting with SAP Solution Manager 7.1 SP07: or &CRM Service Process.User Status& [*] E0004++MJHEAD or &CRM Service Process.User Status& [*] E0012++MJHEAD |
Make the following entries for the PPF start conditions:
PPF Condition | Start Condition |
---|---|
<transaction type>_REQUEST_PRELIMINARY_MJ | No |
<transaction type>_APPROVE_PRELIMINARY_MJ | No |
<transaction type>_CONFIRM_SUCC_TEST_MJ | No |
<transaction type>_AUTHORIZE_PRE_IMPORT_MJ | No |
<transaction type>_CANCEL_PRELIMIN_IMPORT_MJ (not relevant for SAP Solution Manager 7.1 SP07 and above) | No |
<transaction type>_DIRECT_PRLIMINARY_APPR_MJ (not relevant for SAP Solution Manager 7.1 SP07 and above) | No |
<transaction type>_SET_BACK_TO_DEVELOP_MJ | No |
<transaction type>_IMPORT_NC_INTO_PROD_MJ | No |
To create the relevant Change Request Management settings for the preliminary import function, in Customizing choose
.Transaction Type | Status Profile | User Status | Sequence | Action | Logic |
---|---|---|---|---|---|
<your normal change transaction type> | <transaction type>HEAD |
| 10 | SAVE_PARTNER | Inserts current user's business partner in a partner function |
<your normal change transaction type> | <transaction type>HEAD |
| 10 | SAVE_PARTNER | Inserts current user's business partner in a partner function |
<your normal change transaction type> | <transaction type>HEAD |
| 20 | PRM_NEXT_IMP | Synchronizes transports in test systems |
<your normal change transaction type> | <transaction type>HEAD |
| 10 | PRM_NEXT_IMP | Synchronizes transports in test systems |
To register the relevant Change Request Management action as executed late, after the consistency checks have been executed, in Customizing, choose
.Make the following entries:
Transaction Type | Status Profile | User Status | Sequence | Action | Time |
---|---|---|---|---|---|
<transaction type> | <transaction type>HEAD |
| 20 |
| Execute After Checks |
To create the relevant Change Request Management conditions for the preliminary import function, in Customizing, choose
and make the following entries:Trans.Type | Status Profile | User Status | Seq. | Condition Status Transition | Application Area | Message | MT | User Status |
---|---|---|---|---|---|---|---|---|
<trans.type> | <trans.type>HEAD |
| 10 |
| Cancel |
| ||
<trans.type> | <trans.type>HEAD |
| 10 | SAME_USER |
| 069 | Warning |
|
<trans.type> | <trans.type>HEAD |
| 20 |
| Cancel |
| ||
<trans.type> | <trans.type>HEAD |
| 10 |
| Cancel |
|
In Customizing, choose
.For your normal change transaction type and status profile (<Transaction type>HEAD), make the following entries under Specify Status Attributes
:
User Status | System Role Type | Type | Sequence |
---|---|---|---|
EXXX1 | Test System | Processing Phase | 1 |
EXXX2 | Test System | Processing Phase | 1 |
EXXX3 | Test System | Processing Phase | 1 |
EXXX4 | Test System | Processing Phase | 1 |
To create the relevant partner settings for the preliminary import function, in Customizing, choose
.For your normal change transaction type and status profile (<transaction type>HEAD), make the following entries under Specify Partner Assignment and Check
. You can either enter the SAP standard partner functions or your specific partner functions.
User Status | Partner to | Partner from |
---|---|---|
| SMCD0001 | SDCR0002 |
| SDCR0002 | SMCD0002 |