cancel
Showing results for 
Search instead for 
Did you mean: 

Create transport request based on SDMI transaction type

Former Member
0 Kudos

Hello,

a customer of mine intends to use transaction type SDMI in a kind of unusual way. He only creates SDMIs without creating projects, cycles or change requests in ChaRM. He uses a customized copy of the normal correction to track his changes and now needs to activate the functionality to create transport requests as an auditor requirement.

As I'm not proficient in ChaRM, I would like to know if that is at all possible.

Assuming it is possible, what would be the preferences to use action "Create Transport Request" regarding IBase etc.?

Assuming it is not possible, what would be necessary as a minimum to establish the link to the respective system in which the transport request should be created to get that action working, a maintenance cycle? How is the maintenance cycle linked to the ticket?

That are a lot of questions, and it would be highly appreciated if somebody could lighten up the fog there for me.

Thank you in advance!

Kind regards,

Emanuel

Accepted Solutions (1)

Accepted Solutions (1)

frank_wagner2
Participant
0 Kudos

Hi,

I have customized chaRM for some customers and have detail knowledge of internal ChaRM logic. I can tell you for sure that you cannot work with ChaRM without maintainance cycles or projects.

But you can use ChaRM without forcing all users to use it, too. Therefore I would recommend to setup it normal (maybe consider using SDMJ transaction type, it is much better implemented). Do not active global features like global object lock or option for obligatory project within transport.

Before setting it up, you have also to make sure that your customer is not using QA queue or workflow approval in TMS - this is not compatible with ChaRM. I would also try to convince customer to use it for all users because when once set up it makes transport handling much more easier.

Regards,

Frank

Former Member
0 Kudos

Hi Frank,

thanks for your fast reply. Unfortunately, switching to SDMJ would be too much an effort, therefore we need to stick to SDMI.

May I ask you some further questions on ChaRM?

Are the following steps correct?

We have a solution that contains a production landscape with DEV, QUA and PRD system. Inside DSWP, I would navigate to Solution Landscape Maintenance and have a maintenance project created and assigned there. From the project, I first would create the IMG project, then activate the project for ChaRM and create a task list for it. The maintenance cycle (type SDMN) should be automatically created. And now I should be able to use change requests and normal correction as in SAP default process, right?

Former Member
0 Kudos

Had to cut the message as it was concatenated into one long chain of words without line breaks. This is the second part:

Some additional questions:

(1) Do I need to perform any steps in the task list before ChaRM can be used?

(2) How is the maintenance cycle ticket (SDMN) linked to the change requests? Is this linkage done in the SDCR ticket via the maintenance project in the "Customer fields", where solution, maintenance project etc. can be assigned? Or is this implicitly done by the chosen IBase?

(3) Is there any need to add solution / maintenance project / software maintenance in tab "Customer fields" in one of the tickets involved in ChaRM? E.g. if I'm adding a maintenance project, the system will choose one of the upgrade projects that are currently opened with the same solution assigned. I expected that it would choose the respective maintenance project assigned to the solution.

(4) Is it possible from your point of view to use the SDMI without the change requests? This is the customer's requirement and I wonder if it is possible to directly link the SDMI to the maintenance cycle to get it work, i.e. to have transport requests created out of the SDMI etc.

(5) Which system assignment is the leading one when it comes to creating transport requests? There is a logical system assignment in the maintenance project, an IBase in the ticket, and it is also possible to assign a system in tab "Customer Fields" adding node "Software Maintenance" (while I am thinking this might be utilized for other SolMan functions). Do you know something about that and can explain in a few words?

Sorry for asking so many questions, but there are several gaps in my knowledge of ChaRM that I'm trying to fill without having a test system available, which is some kind of impossible.

Your answers would be highly appreciated and would help me very much. Thank you in advance!

Kind regards,

Emanuel

prakhar_saxena
Active Contributor
0 Kudos

Hi,

1) Do I need to perform any steps in the task list before ChaRM can be used?

No once task list is in active state and sdmn is created for ur project u can start using charms

2) How is the maintenance cycle ticket (SDMN) linked to the change requests? Is this linkage done in the SDCR ticket via the maintenance project in the "Customer fields", where solution, maintenance project etc. can be assigned? Or is this implicitly done by the chosen IBase?

Yes everything is dependent on IBASE and logical component.

Check this links

https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF

/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario

http://help.sap.com/saphelp_sm32/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm

Check SMP/SDN

https://websmp208.sap-ag.de/changecontrol

[original link is broken]

Hope it solves ur queries

Regards

Prakhar

Former Member
0 Kudos

Does anyone have further ideas regarding the other questions? They would be highly appreciated. Thanks!

Former Member
0 Kudos

Hi Emanuel,

(2) How is the maintenance cycle linked to the change request?

While you save the Change Request, it will ask you to select the Maintenance Cycle. Thus is the CR getting assigned to your maintenance cycle and in turn to your maintenance project.

So, before creating the CR, you should have created your maintenance project and the maintenance cycle(in the SOLAR_PROJECT_ADMIN txn of the Maintenance Project).

(3) The answer for question (2) itself answers this. No need to do anything in the customer fields to establish the relationship between your CRs and the Maintenance cycle or solution.

(5) The leading system of transport requests is based on how you have configured your STMS. SolMan's ChaRM feature uses the transport path defined in your STMS.

best regds,

Alagammai.

Former Member
0 Kudos

when i create a change request and put it into development, it is going back to created status after being in "in development " status.

This is happening everytime i make some changes and save , it is automatically going to back to created status.

Can you help me with this issue. It seems like a bug but not sure how to resolve it or if anyone faced the same issue?

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Gurus,

Can anyone help me with the following issue.

When i create CR its and make any changes after putting back to created status from in development status

regards,

bobby

Former Member
0 Kudos

hello Bobby,

were you able to resolve the issue? We have the same issue, when trying to change the status of normal creation after setting it to "in development", the phase is going back to created.

Thanks,

Ravali