Solution manager- Transport management

Dear Experts,
I working at a client place who is planning to impliment SAP Solution manager for transport management, can some one please point me to the right documentation related to transport management in solution manager.
Any presale presentations would be really helpful.
Thanks for your time.
-Amit.

Hi,
For presales oriented presentation on transport management in conjunction with Solution Manager, this is the topic on Change request management (CHARM); please kindly proceed to the site
service.sap.com/rkt-solman -> SAP Solution Manager 7.0 -> Presales & IT Managers
There are two sub topics within, the 2 are
SAP Solution Manager - The SAP Application Management Solution
SAP Solution Manager - Scenarios
Please look for the subtopics within them, which talks on CHARM.
Hope this helps.
Cheers
SH

Similar Messages

Transport Management System with Solution Manager

Dear all,
Do you know the function transport management system(TMS) with solution manager, I already search in SAP document but not found this function.
Do you know how to config solution manager for TMS and documents related with this function please guide for me!
Thanks all very much !

Hi,
Check this link.
https://websmp103.sap-ag.de/~sapdownload/011000358700000508502008E/ChangeRequestManagement.pdf
Hope this answers your questions.
Feel free to revert back.
-=-Ragu

Transport Management in SOlution Manager

Hello All,
We are currently running a Conf. Room Pilot for our customer. As part of the CRP, the customer has created a new template project in Solman and have also a created a new sandbox as a copy of their production for the CRP where we have got full access.
The customer wants us to use SAP transport management functionality in Solman where all transports & changes made in the sandbox can be tracked and they can be moved to their production if required using solution manager.
Now customer doesnot want to configure ChaRM.
Two possiblities I see are
1. Create an IMG project in Sandbox system through Solution Manager and in the Sandbox systems' project activate CTS functionality. Give TR Create authorization to team members with restriction of assignment to CTS project only. (Dis-allow TR creation w/o CTS project assignment in Sandbox)
2. Activate Change Request Management (ChaRM ) in the template project with only CTS functionality (No other functionality of ChaRM is useful here). At the moment I am not sure if this will be allowed.
please let me know, how do I restrict creation of TR without assigning to CTS?
Regards,
Shyam

Any answer to this?

Manage transports (without ChaRM) in Solution Manager?

Hi,
How do I manage transports in target systems (ECC, APO, etc.) using Solution Manager. We have the Dev systems (ECC, APO) connected using RFC to Solution Manager. Configuration (SOLAR02) will be done using Solution Manager. So the question is - how do we manage transports (without ChaRM being present) using Solution Manager?
Any suggestions/recommendations? I would greatly appreciate any feedback.
Edited by: GiveMeFood on Sep 22, 2011 10:05 PM

Hi,
One of the main features available with the Solution Manager is ChaRM. It has been introduced to basically deal with the diverse transports management and related control framework over the SAP lanscape. Having a Solution Manager and not using ChaRM defeats the purpose of installing a Solution Manager in the first place. A better approach would be to incorporate the features provided by the system.
In my opinion - you should configure ChaRM, else it would not make sense to have the SolMan in the landscape. You would start using one of the features which you already have !
Regards,
Srikishan

CTS+ Configuration for Transporting non-ABAP objects in Portal Landscape using solution manage 7.1 sp8

Hi,
Currently we have cts+ already configured for our portal systems in our landscape through solution manager 7.0.
Recently we had setup a new solution manager 7.1 and need to perform cts+ configuration using this new solution manager 7.1 as we are planning to remove our old solution manager 7.0 very soon.
We are using NWDI system for transporting our portal transports.
Please help me with steps on how to configure cts+ using solution manager 7.1 using NWDI.

Hi Naveen,
Please find given below BBPCRM & SAP_BW version..
BBPCRM 500 0013 SAPKU50013 BBPCRM BBP/CRM Supp. Pack.
SAP_BW 701 0003 SAPKW70103 SAP Business Warehouse Component Supp. Pkg.
This problem is not only with Bussiness process tab (T-Code: Solution_manage) also System monitoring Still i searching solution for this But once we are restarting System that time this problem is not occuring but after some time system is giving this DUMP
Regards,
Suresh

How do we make automatic and mass transports via Solution Manager

How do we make automatic and mass transports via Solution Manager ..
how can we do this is there any specific procedure please let me know
Regards
Karthik

To attempt a new chat session...
For the link below click the Still Need Help? option in the blue area at the bottom and choose the chat option...
http://helpx.adobe.com/x-productkb/global/service1.html

Solution Manager/Charm and Transport Dependency Check

Hello Everyone,
I apologize if this question has an obvious answer. I have searched SDN and could not get a 100% answer.
We are just now in the process of rolling out Charm/Solution Manager and I have noticed that it appears to not perform transport dependency checks. For example, let's say I am working on object ABC and have completed my testing (ready for transport to production) and then another developer also starts development on object ABC. When my change is moved to production, it will pick up the other developers modifications without giving a warning or an error that a dependency has been encountered between the two transport requests.
Does Charm/Solution Manager offer the option of producing a warning should a transport depedency be identified? If so, will someone explain (or point me to the appropriate documentation) how this can be set up?
Best Regards,
Scott

Hi Scott,
ChaRM supports imports from DEV->QAS->PRD by transport by transport requests level not by transport request task level. So don't worry(i.e., You can't import only your change of object ABC to production. It allows to import your change and other user's change of object ABC together to production).
This is how it works(if more than an user works on the same object):
1. Requester creates a support message from satelitte system to report a problem.
2. Service desk employee creates a change document because some changes need to be done on object ABC to correct that reported problem.
3. Change Manager approves the change document. So a normal correction is created automatically.
4. This normal correction is assigned to 2 developers(your scenario) like for an example DVPR1 and DVPR2.
5. DVPR1 creates a transport request and does some changes on object ABC. So a transport task will be created for DVPR1 under that transport request automatically.
6. When DVPR2 tries to do some changes on the same object ABC, a seperate transport task(not a transport request) will be created for DVPR2 under the same transport request because the object ABC is locked under the transport request. So DVPR2 can't create a separate transport request for the same object if any transport request is pending(not released).
7. Now object ABC will have one transport request. That transport request will have 2 transport tasks(1 for DVPR1 and 1 for DVPR2).
8. Each developer relases their transport task only(not transport request) once he/she completes his/her change on the object ABC.
9. DVPR1 or DVPR2 will change the status of normal correction to "Development Completed".
10. Now, IT operator or DVPR1 or DVPR2 can release the transport request. The transport request can be released only if all tasks are released under the same transport request.
(In this example: DVPR1 completed his change and released his transport task. Next DVPR2 completed and released his transport task).
11. Finally IT operator import the transport request to QAS and PRD.
Hope you are clear now. Let me know if you have any doubts.
Regards,
Sanjai

Solution Manager Change Management: Transport Request Administration

Hi.
We want to use the CHARM functionality of Solution Manager to improve our transport operations. We have several customers and expend´s a lot of time making tranports to different systems.
I don want to activate CHARM completely. Which activities do i must perform, and which activities do i must leave ?
Regards
Alvaro

Hi Avinash
This is the Business Scenario: Our company is using SAP Solution Manager to perform monitoring and administration activities for over than 30 customers.
Dayly we espend over 85% of the basis team time making transport for all of the customers. We decide to set some internal politics to bundle transports, stablishing several releases of them, at specific hours of the day. So we want to use SOLMAN`S change logistics instead of CHARM Scenario to control and improve this activitiy, releasing time to perform other activities.
Regards
Alvaro

Solution Manager transports

What is the procedure of transporting XI objects within Solution Manager 4.0?

Hi,
I think as in all SAP systems it will be through STMS, you need to define target system group. and configure your transport route. Hope it was useful.
Feel Free to revert back..
--Thanks and Regards,
RaguERP,
Suzlon Energy Limted, Pune
Extn: 2638
+919370675797
I have no limits for others sky is only a reason

How to transport solution (in dswp) in solution manager system

how to transport solution (in dswp) in solution manager system ??

Hello,
I don't think this is possible in DSWP.
Please refer to this link for information related to change management.
http://wiki.sdn.sap.com/wiki/display/SM/ChangeRequestManagement
Regards,
Paul

Managing Transport Request with Solution Manager

Hi Experts,
Kindly advise what is the pros and cons of using Solution Manager to manage Transport Request in R3.
Thanks,
Chris

You call transaction STMS on your Solution Manager. If you have
created a local transport domain, you have to delete it. Menu
Overview-> Systems-> Extras-> Delete TMS Configuration. Confirm the
popups. On the Popup: TMS:Include System in Transportdomain you can
change to "Other Configuration" (F6) (second button from left)
then select "include system to domain". Enter the application server
and system ID from your domain controller. After this your domain
controller get the information that a new system wants to be part of the
domain, then you have to activate this on the controller,
then the status changed.
That should be all you have to do.
But the recommendation from SAP is that the system with the newest basis
should be the domain controller.

Error message in solution manager while importing transport using CHARM.

Hi All,
I am gettting below message while i am trying to import a change request using CHARM from solution manager
"You are not allowed to work on a CR for UNITEOPS"
"Data type-specifc customizing missinge for a data type"
But other user in our team able to do the import of change request. I checked all roles and authorization are same for both the user but still it is not working for my user-id and it is working for my team member user-id
Can you please guide? Is there any customizing missing for my userid?
Thanks

Hi,
Perhaps the info in this thread could be useful:
ChaRM roles or profile missing for Developer and Change Manager
Regards,
Srikishan

Solution Manager: documentation of Retrofitting transport requests

Hi All
I would know if anyone has implemented retrofit functionality in SAP Solution Manager? The documentation for this functionality is very poor in sap service market place and I would improve my knoleges for a new project.
Thank you for collaboration.
Best regards
giovanni

Hi Giovanni,
I was about to ask the same question, i am investigating on Retrofit and i confirm that documentation is very poor...
Here are the informations i found :
Retrofit functionalities :
It is native after SP12 and completly usable after SP14
SP16 most of the bugs are corrected.
If you encounter some issue during functional implementation you can read these 3 OSS notes to help you.
- Note 1264918 -> Corrections for retrofit list
- Note 1250430 -> Retrofit usability
- Note 1246877 -> Performance problems displaying
retrofit list
I woul like to know how we can manage retrofit but it is hard like searching the Graal

Solution Manager & Workflow driven Transport Mangement

Dear SDN Members,
I would like to know if it is possible to use a workflow drivene TMS within the Solution Manager 3.2 using serveral approval steps. For instance an approval between DEV and QAS and an approval between QAS and PRD.
We would like to implement the workflow for our 4 system R/3 landscape, 3 system BW and XI landscape.
Regards,
Niek Weustink

Hi Mrutyunjay,
As far as I know, you can only attach one CTS project per Solution Manager Project.
The idea is that for each different project you have for your satellite systems you´ll have to have one Solution Manager project.
This way you can use the features on Solution Manager side to control all changes ( for instance, using Change Request Management ).
Part of the CTS functionalities that we have on standard SAP installations are being migrated to Solution Manager controls.
So, you can have as many CTS projects you need on your ECC as long as you have their correspondent Solution Manager projects.
Based on ITIL standards, Solution Manager is the central point to control all changes you make in your systems.
Regards,
Valdecir

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

Solution manager- Transport management

Similar Messages

Maybe you are looking for