Configuring the Preliminary Import Function

You can adapt your existing system configuration for the normal change process, to be able to use the preliminary import function.

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.

Prerequisites

You have been using the normal change process in your SAP Solution Manager system.

Procedure

Step 1: Create new authorization keys (optional)

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 SAP Solution Manager Capabilities Change Request Management Transactions Status Administration Define Status Profile for User Status .
Choose Environment Authorization Key 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.

Step 2: Add preliminary import user statuses to user status profile

In Customizing, choose SAP Solution Manager Capabilities Change Request Management Transactions Status Administration Define Status Profile for User Status .
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:
1. 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”.
2. In the Status field, enter the same values as in SAP standard.
3. In the Lowest, field enter the user status number of the “In Development” user status (or the equivalent customer-specific user status).
4. 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).
5. Add the newly created authorization keys to the user statuses.
Save your entries.

Note 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.

End of the note.

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	`E0011`	`<EXXX1>`	<Transaction type>_X1
Test for Preliminary Import	`E0012`	`<EXXX2>`	<Transaction type>_X3
Tested for Production Import	`E0013`	`<EXXX3>`	<Transaction type>_X4
Released for Import	`E0014`	`<EXXX4>`	<Transaction type>_X5

Step 3: Adapt roles in authorization object B_USERSTAT

Adapt the roles in authorization object B_USERSTAT, in transaction PFCG.

User status	Authorization key	Role
`<EXXX1>`	<Transaction type>_X1	All roles used in Change Request Management
`<EXXX2>`	<Transaction type>_X2	Change Manager, System Administrator
`<EXXX3>`	<Transaction type>_X3	Tester, System Administrator
`<EXXX4>`	<Transaction type>_X4	IT Operator, System Administrator

Step 4: Create PPF actions and conditions

To create the PPF actions that set the user statuses, and to adapt old PPF actions, in Customizing, choose SAP Solution Manager Capabilities Change Request Management Transactions Actions Change Actions and Conditions Action Profile Define Action Profiles and Actions .

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 `USER_STATUS`)	Further PPF Container Element	Definition of Container Element
<Transaction type>_REQUEST_PRELIMINARY_MJ	`EXXX1`
<Transaction type>_APPROVE_PRELIMINARY_MJ	`EXXX2`	`PRELIMINARY_APPROVE` (used for authorization)	In the container editor, choose `PRELIMINARY_APPROVE`. Under D. Type ABAP Dict. Data Type , enter `CHAR1` in the Type Name field.
<Transaction type>_CONFIRM_SUCC_TEST_MJ	`EXXX3`
<Transaction type>_AUTHORIZE_PRE_IMPORT_MJ	`EXXX4`
<Transaction type>_CANCEL_PRELIMIN_IMPORT_MJ	`E0009` (equivalent to “Successfully tested” status)
<Transaction type>_DIRECT_PRLIMINARY_APPR_MJ (not relevant for SAP Solution Manager 7.1 SP07 and above)	`EXXX2`
<Transaction type>_SET_BACK_TO_DEVELOP_MJ (not relevant for SAP Solution Manager 7.1 SP07 and above)	`E0002` (equivalent to “In Development” status)	`PREDOC_STATUS` (used to set the request for change to `E0005`)	In the container editor, choose `PREDOC_STATUS`. Under Initial Value ABAP Dict. Data Type , enter `E0005`.
<Transaction type>_IMPORT_NC_INTO_PROD_MJ	`E0006` (equivalent to “Imported for Production” status)

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.

End of the note.
In Customizing, choose SAP Solution Manager Capabilities Change Request Management Transaction Types Actions Change Actions and Conditions Define Conditions .

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	Up to SAP Solution Manager 7.1 SP06: &CRM Service Process.User Status& [] EXXX1++MJHEAD and &CRM Service Process.ErrorFreeFlag& = X and &PRELIMINARY_APPROVE& = X (or equivalent user status for “Tested Successfully”) From SAP Solution Manager 7.1. SP07: &CRM Service Process.User Status& [] E0009++HEAD or &CRM Service Process.User Status [*] E0011++HEAD and &CRM Service Process.ErrorFreeFlag& = X and &PRELIMINARY_APPROVE& = X
<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

Step 5: Assign Change Request Management actions and conditions

To create the relevant Change Request Management settings for the preliminary import function, in Customizing choose SAP Solution Manager Capabilities Change Request Management Change Request Management Framework Make Settings for Change Transaction Types Assign Actions .

Transaction Type	Status Profile	User Status	Sequence	Action	Logic
<your normal change transaction type>	<transaction type>HEAD	`<EXXX1>`	10	SAVE_PARTNER	Inserts current user's business partner in a partner function
<your normal change transaction type>	<transaction type>HEAD	`<EXXX2>`	10	SAVE_PARTNER	Inserts current user's business partner in a partner function
<your normal change transaction type>	<transaction type>HEAD	`<EXXX2>`	20	PRM_NEXT_IMP	Synchronizes transports in test systems
<your normal change transaction type>	<transaction type>HEAD	`<EXXX1>`	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 SAP Solution Manager Capabilities Change Request Management Change Request Management Framework Make Settings for Change Transaction Types Define Execution Time of Actions .
Make the following entries:

Transaction Type

Status Profile

User Status

Sequence

Action

Time

<transaction type>

<transaction type>HEAD

<EXXX2>

20

PRM_NEXT_IMP

Execute After Checks

Transaction Type	Status Profile	User Status	Sequence	Action	Time
<transaction type>	<transaction type>HEAD	`<EXXX2>`	20	`PRM_NEXT_IMP`	Execute After Checks

To create the relevant Change Request Management conditions for the preliminary import function, in Customizing, choose SAP Solution Manager Capabilities Change Request Management Change Request Management Framework Consistency Checks Assign Conditions to Status Values 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	`<EXXX1>`	10	`PRELIM_PRD_NOT_IMP`			Cancel	`E0009` (equivalent to “Successfully Tested”)
<trans.type>	<trans.type>HEAD	`<EXXX2>`	5	`DGP_CHECK_OK`	`AI_CRM_CM_MESSAGE`	072	Cancel	`EXXX1`
<trans.type>	<trans.type>HEAD	`<EXXX2>`	10	SAME_USER	`AI_CRM_CM_MESSAGE`	069	Warning	`E0009` (equivalent to “Successfully Tested”)
<trans.type>	<trans.type>HEAD	`<EXXX2>`	20	`PRELIM_PRD_NOT_IMP`			Cancel	`E0009` (equivalent to “Successfully Tested”)
<trans.type>	<trans.type>HEAD	`<EXXX3>`	5	`DGP_CHECK_OK`	`AI_CRM_CM_MESSAGE`	072	Cancel	`E0004` (equivalent to “To be Tested”)
<trans.type>	<trans.type>HEAD	`<EXXX3>`	10	`PRELIM_TR_IN_PRD_BUF`			Cancel	`EXXX2`

Step 6: Specify status attributes

In Customizing, choose SAP Solution Manager Capabilities Change Request Management Standard Configuration Change Request Management Framework Make Settings for Change Transaction Types .

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

Step 7: Save partner Customizing settings

To create the relevant partner settings for the preliminary import function, in Customizing, choose SAP Solution Manager Capabilities Change Request Management Change Request Management Framework Make Settings for Change Transaction Types .
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

EXXX1

SMCD0001

SDCR0002

EXXX2

SDCR0002

SMCD0002

User Status	Partner to	Partner from
`EXXX1`	SMCD0001	SDCR0002
`EXXX2`	SDCR0002	SMCD0002