TR is imported into production but status in Solman is still authorized for imported

[Atul_Sharma]

Hi Everyone,

- Main TR to be released from Dev system

- Main TR to be imported into respective QA system (using automatic transport import job with frequency of 15 mins)

- Main TR to come to Production import queue

- Main TR to be imported into Production system (manually by schedule import job for Transport Request)

- Normal Change Document status to be moved to next "Imported into Production" automatically once TR import is successful (not working)
but in my case, this is not working
Anyone knows how to configure this 

[Vera_Jiang]

We helped you to accept the answer, since there were no updates after 7 days. You can unaccept it anytime if the answer provided was not helpful enough and you have further questions.

[deepa_m_s · Accepted solution]

Hello, 

Kindly check and verify the below points with respect to Import feedback in general along with the configuration needed for automatic status change : 

• Please check the KBAs 2746697 - Active Import Feedback - Additional information and 2635017 - Updating Change Document Status After Import of Transport Requests - additional information, carefully. In principle, there should be a background job SM:AI_CRM_CM_COM_IMPORT_FEEDBACK scheduled for event SAP_AI_CM_IMPORT_FEEDBACK using the SM_CHM user. There is also a step in the SOLMAN_SETUP to configure this job. 
  
  
• Ensure that the correct BACK RFC destination to the Solution Manager system is maintained in the managed system. The user of this BACK RFC : SMB_<SolManSID> needs to have authorizations from role SAP_SOLMAN_BACK according to SAP Note 2257213 - Authorizations for RFC users for SAP Solution Manager 7.2 SP02 and higher
  
  
• Ensure that the SM_CHM User has correct authorizations assigned for the statuses that you want to move the change document to.  
  
  
• Make sure that the configuration in the view AIC_CRM_CM_ST_CH, is correctly maintained. Remove unwanted/duplicated entries or any empty lines for the transaction type in question. 

If you have checked all these points and the issue persists, kindly create a case and direct it to the component SV-SMG-CM for further checks. 

Best Regards, 
Deepa
SAP Product Support