Customizing Synchronization

[Former Member]

Hello experts...

Can any one using solution manager4.0 for implimentation project???

I'm thinking of using solution manager to move transports using Customizing Synchronization .....is this is the right way of approch ???

or can any one tell me how to handle this situation to move transports from one ENV to other ( DEV to QA)???

Thanks,

padma

[former_member322647 · Accepted solution]

Hi Padma,

I think your understanding is not correct. If you have a three system landscape like DEV -> QAS -> PRD, you are using classical TMS (transport management system) to transport your changes. If you have several DEV systems which have the same or similar customizing you can use customizing distribution to deliver the customizing. There for you need rfcs between the systems and SolMan. Using rfcs we are distribution the customizing. In the target DEV system we consolidate the changes in a classical transport request. This transport request has to be transported via the defended transport routes to QAS and PRD.

I hopefully answered your question.

Regards,

uDo

[Former Member · Accepted solution]

Thanks for the reply Udo...

I'm just confused here...Classical TMS means ...

Are we using to create and release transports from satellite systems by using solution manager??? if yes requesting you to explain me the scenario...

my exact question is how to create a transport reuest and releas the request in DEV system by using solman4.0? and how to import also?

Thanks

[Former Member · Accepted solution]

Hey Udo Lang...

Can you please clarify me is there any thing we can use from SOLAR_PROJECT_ADMIN --> Project --> systemlandscape --> IMG Projects

><Satellite sytem IMG>-->Transport Requests tab

I think we can create transport request from there in satellite system...but how extensively it is use full i'm not sure abt that??? and even i'm not sure how to release and import from solman...

If any body has some inputs that will Great....

Thanks,

Praveen

[former_member322647 · Accepted solution]

Hi Praveen,

your question is not easy to answer. To make it simpler, forget customizing synchronization. You only want to have the option to create transport request for your satellite systems via Solution Manager.

This function is not available in that way you expect.

Your proposal in the solar_project_admin.

There you have the option to build up a "chain" from your SolMan project to your IMG project in your sat. system and your IMG project has a CTS project assigned which is a attribute at your transport request (you can make this attribute mandatory). What do you get with this "chain" you can control your transport requests in the sat. system. You can check who makes in which project changes. BUT the transport requests have to be created manually in the sat. system.

I expect you which to create the requests centrally.

This is possible using Change Request Management, BUT this scenario includes much more then you want. This includes a full controlled approval process of each transport request, "may I create a transport request?, Can I export ? Can I import?" all these questions are controlled by the tool or by approvals.

Now to your second question TMS

In any case finally we handel a transport from TMS.

In TA SE09 you can create transport and release requests.

Normally you create in TA STMS a transport route from your DEV to QAS to PRD system. Then after export the request is automatically send into the import buffer of the next system in the transport route. Then it can be imported manually in TA STMS, or you can create a batch job which imports all or classified requests into your system.

So if you want to use the scenario Change Request Management you have to build up the TMS in a defined way which is described in your IMG. You also have to build the mentioned "chain". You have to set up several settings in CRM. What I want to say is, it is a little bit complex, and the question is is that the function you look for?

Regards,

uDo

[Former Member · Accepted solution]

Thanks for the reply Udo Lang...

I' pretty much convinced with your thoughts...but my understanding was i can use change request management after GO LIVE ....i mean for maintenance project...

If i use change request management for realization phase also ...can you please tell me how can i make link to development objects( SOLAR02) to tasks in Change request management????? Even though it is bit complicated i just wanted understand the concept......

Once again thanks for your help...

Praveen

[former_member322647 · Accepted solution]

Hi Praveen,

thank you for your positive feed back, so we can go further :-).

Again, your question is not easy to answer

Technically you can use Change Request Management with quite all project types. The most common is the maintenance project. My picture is the following one. The maintenance project handles the cycle with the necessary project IMG/CTS project ID. The SOLAR01/02 in the maintenance project is NOT used. You can use it, BUT so far there is no link between the change request and the process in the project. We are just developing it , but it will take same time until it will be available. So again to my picture. You create a maintenance project, the create a cycle for the change request management. Then you can use this "infrastructure" for changes in solutions or all kind of project. The reason of dividing this into two is the system landscape. The system landscape of a maintenance project should be quite stabile, but the system landscape of a project (impl./uprade) or solution can be changed. That is the reason why I would handle it separately.

In realization phase you may control in the test phase the creation of new transport request, there for ChaRM fits excellent. But again, the change request does not know any thing about the solution or project or process, this will come.

I hope my info is helpful

Regards,

uDo

[Former Member · Accepted solution]

Thanks for the reply Udo Lang...

With this good understanding discussion it is bit difficult for me to convince myself to use the solution manager completely in realization phase .The value addition to me by using solution manager rather doing it in individual satellite systems is bit less ( For development ) except central tool for documentation and synchronizing business process from ARIS.

Still if i wanted to use solution manager completely in realization phase, i have to handle it in two different approaches . One is for project /processes and another one is for ChaRM to control the transports.

But how to control the ChaRM with respect to implementation project. I mean if a developer wanted to create transport request ,initially task has to be created then go on...Is this is the good practice???? Hope i understood your thoughts correctly.

Once again thanks for the help.

Thanks,

Praveen

[former_member322647 · Accepted solution]

Hi Praveen,

a developer never wants to be restricted to get a transport request or a task in a request. But project management want to get stabile coding. There for the idea is to say, from a dedicated point all new request needs an approval. So the developer can not create new requests in the DEV system, he has to go to SolMan and create a change request, which has to be approved. Then he gets a request an can continue with his corrections. This is the way we develop, and I got the feed back that many customers (not developers) wants such a process.

Regards,

uDo

[Former Member · Accepted solution]

Thanks For the Information...

Before closing the discussion , My last question could be is there any specific standard Naming convention document for Solution manager in any aspect?

And thanks for the suggestions and important information.

Praveen,

Praveen.sunkari@gmail.com.

[Former Member]

Hi Padma....create a new account for you...

I got some information from SAP help...

1. Create a project in the Project Administration.

2. Define a system landscape for this project. Ensure that development systems are defined for all components.

3. Generate a project IMG for all development systems.

You go to the Project Administration in the system. Transports, which are also used during customizing, must be created for this project, in the component systems.

4. Create customizing and workbench transports for this project.

5. If you want to distribute customizing changes after transport change or transport release, create tasks for all customizers in the systems involved, in the transport requests.

6. If you want to distribute customizing with the Initial Distribution or timed, as system administrator, create tasks for yourself in the transport requests in the systems involved. If you want to Redistribute Customizing after Errors, you must also have a task in the transport requests in the systems involved.

Even i'm trying the same....I will let you know..

Thanks,

Praveen.