Skip to Content

How-To Integrate the Preliminary Import Functionality for Customers with existing and changed Normal Change user status Profile in Solman 7.1 – SP5 – Part 1



SAP Solution Manager SP5 delivers the new functionality ‘Preliminary Import for the
Normal Change. A Normal Change is used for project development. After the Project
Cycle was in Phase ‘Test’ and the Normal Change has passed the different tests
(Integration, acceptance, scenario tests) it is imported via the task list
project import.
The Preliminary Import functionality introduces a workflow to handle a Normal
Change like an Urgent Change, so that the transports are imported into the
production system after it was tested successfully which means a faster way to
get the Normal Change into the production system. This faster way has to be
Customers who use already the Normal Change normally adapt the user status profile to adapt
it to their process. This means the introduction of new user status in the user
profile. When a user status is created, a new technical EXXXX number is
created. The Preliminary Import functionality as well introduces four new user statuses
from E0011 to E0014. But these numbers might already be occupied by the
customer by his added customer-specific user status. So, what has to be to be
done if you want to use the Preliminary Import functionality and integrate it
into your process?
The Preliminary Import functionality is a side-process starting in the standard
user status ‘Tested Successfully’ (E0004) and returns to the user status
‘Imported into Production’ (E0006). First you have to analyze these equivalent
user statuses in your user status profile, they are the start and end point in
your process.
Pic 1: Process overview of Preliminary Import functionality:
Updated Pic see here…


The To-Do list consists of different activities:

  1. Create new authorization codes (optional)
  2. Add Preliminary Import user statuses in user status profile
  3. Adapt the roles in authority object B_USERSTAT
  4. Create PPF actions and conditions
  5. Assign ChaRM action and ChaRM conditions
  6. Specify Status Attributes
  7. Save Partner Customizing

Pic 2: Technical Overview of Preliminary Import Customizing Elements:

Updated Pic…see here

Create new authorization codes (optional)

If Z authorization codes are used in the customer Normal Change user status profile, 4 new authorization codes have to be created. This customizing can be accessed from the user status profile customizing via ‘Environment->Authorization key’

Pic 3: menu path


  • Mark the 4 authorization keys

Pic 4: Copy authorization keys


the roles in authority object B_USERSTAT

Standard Authorization Key Copied Auhtorization Keys Description
SMMJ_04 <Transaction_type>_X1> Request
Preliminary Import
SMMJ_05 <Transaction_type>_X2> Authorize
Preliminary Import
SMMJ_06 <Transaction_type>_X3> Confirm
Successful Test
SMMJ_07 <Transaction_type>_X4> Released
for Import

Add Preliminary Import user statuses in user status profile

Insert 4 new user statuses which reflect the SAP Standard Preliminary user status

Pic 5: SAP standard process new Preliminary Import user statuses:


  • The Preliminary Import user statuses should have a status number between the start
    and end user status numbers identified in the process. Meaning, between the
    equivalent user status ‘Successfully Tested’ and ‘Imported into Production’.
  • It is recommended to use the same values in the field ‘Status’ as in SAP standard
  • The ‘Lowest’ field should contain the user status number of the ‘In Development’
    user status (or customer equivalent user status)
  • The ‘Highest’ field should contain the number of the next Preliminary Import user
    status, so we reach only the next one. The last one ‘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

The user statuses get automatically new created E-status. They are visible in table TJ30
(use transaction SE16). For convenience (so I can use them later down) let us
assume they are named.

SAP Standard user status description SAP standard user status Placeholder user status Authorization key
Preliminary Import Requested E0011 <EXXX1> <Transaction_type>_X1>
Test(ing) for Preliminary Import E0012 <EXXX2> <Transaction_type>_X2>
Tested for Production Import E0013 <EXXX3> <Transaction_type>_X3>
Authorized/Released for Import E0014 <EXXX4> <Transaction_type>_X4>
Pic 6 and 7: Finding the created technical E user statuses:

Adapt the roles in authority object B_USERSTAT

Authority object B_USERSTAT
Placeholder user status Authorization key Role
<EXXX1> <Transaction_type>_X1> All ChaRM roles
<EXXX2> <Transaction_type>_X2> Change Manager, Administrator
<EXXX3> <Transaction_type>_X3> Tester, Administrator
<EXXX4> <Transaction_type>_X4> IT Operator, Administrator

Create PPF actions and conditions

To create the relevant PPF actions setting the user statuses and adapting old PPF actions, choose IMG activity ‘Define Action Profiles and Actions’ in the IMG with path ‘…Change Management->Standard Configuration->Transaction Types->Action Profile’

  • Create the PPF actions in the table with implementation ‘HF_SET_STATUS’ and container element USER_STATUS and the value listed in the table. You can copy as well another PPF action with HF_SET_STATUS implementation but be aware
    that the texts of all languages are copied with it.
  • Be aware, you can always compare your customizing with the relevant standard action, starting with SMMJ_…in the PPF action SMMJ_ACTIONS action profile.
  • Be aware that starting SP7 the actions <Transaction_type>_DIRECT_PRLIMINARY_APPR_MJ is replaced with <Transaction_type>_APPROVE_PRELIMINARY_MJ and action <Transaction_type>_SET_BACK_TO_DEVELOP_MJ is replaced with <Transaction_type>_TESTED_AND_NOT_OK. This is accomplished by adopting the PPF conditions of the replacing PPF actions.

More information of the handling with PPF actions and PPF conditions can be found here:
Create PPF action
Sets User status
(in PPF container element USER_STATUS)
Further PPF container element
<Transaction_type>_CONFIRM_SUCC_TEST_MJ <EXXX3>
<Transaction_type>_AUTHORIZE_PRE_IMPORT_MJ <EXXX4>
<Transaction_type>_CANCEL_PRELIMIN_IMPORT_MJ E0009 (‘Successfully Tested’ equivalent)
<Transaction_type>_DIRECT_PRLIMINARY_APPR_MJ (not relevant for SP7 and above) <EXXX2>
<Transaction_type>_SET_BACK_TO_DEVELOP_MJ (not relevant for SP7 and above) E0002 (‘In Development’ equivalent)
<Transaction_type>_IMPORT_NC_INTO_PROD_MJ E0006 (‘Imported for Production’ equivalent)

PPF Schedule Conditions
PPF condition Schedule



table 1.png



table 2.png

starting SP7: approve preliminary import.png



table 3.png



table 4.png



(not relevant for SP7 and above)

table 6.pngtable 6-1.png



(not relevant for SP7 and above)

table 7.png



table 8.png



table 9.png



starting SP7 adapted: Tested and not ok.png
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 no
<Transaction_type>_DIRECT_PRLIMINARY_APPR_MJ no
<Transaction_type>_SET_BACK_TO_DEVELOP_MJ no



Pic 8: Definition of the Container element PRELIMINARY_APPROVE (used for authorization):


Pic 9: Definition ofthe Container element PREDOC_STATUS (used to set the Request for Change to E0005)


ChaRM actions:

To create the relevant ChaRM actions setting for the Preliminary Import
functionality, choose IMG activity ‘
Actions – Depending on Status’ in the IMG with path ‘…Change Management-> Standard
Change Request
Management Framework->
in Change Request Management’.

Pic 10: SAP standard process ChaRM actions


Transaction type Status profile User Status Seq. Action Logic
<transaction type> <transaction type>HEAD <EXXX1> 10 SAVE_PARTNER Inserts current users business partner in a partner function
<transaction type> <transaction type>HEAD <EXXX2> 10 SAVE_PARTNER Inserts current users business partner in a partner function
<transaction type> <transaction type>HEAD <EXXX2> 20 PRM_NEXT_IMP Synchronizes transports in test systems
<transaction type> <transaction type>HEAD <EXXX3> 10 PRM_NEXT_IMP Synchronizes transports in test systems

The second part can be found here:–sp5–part-2

You must be Logged on to comment or reply to a post.
  • Hi Michael,

    We would like to implement functionality that requires approval before a transport can be moved to the production system. Ideally, instead of the transport being released when the action Confirm Test Success is performed, the transport would be released when Preliminary Import has been approved. Can the Preliminary Import functionality do this? Can we disable the functionality to go from Tested Successfully directly to Imported into Production without using Preliminary Import?