CharM questions (mix Transport strategy)

Hi ChaRM-experts!
I plan to map the existing transport landscape into ChaRM scenario of SOLMAN and have the following questions:
1) Is it possible to combine ChaRM-functionality and still use the old transport settings (without ChaRM) for the same system landscape:
DEV --> QAS --> VO1 (Without ChaRM and with virtual system)
DEV:101 --> QAS:101 --> PRD:101 (With SOLMAN ChaRM)
Can e.g. the target group concept help in this situation?
2) Is it possible, after the CharM implementation, to allow the developers create transports in DEV system?
Thank you very much!
Holger

Similar Messages

Mass transport strategy but satellite system is configured for ChaRM

We want that all transports are automatically transported in the development test client.
We have calling a job with program TMS_BCI_START_SERVICE in the satellite system. But this program can only be used for mass transports and does not work when single transports strategy is activated.
Question:
Is there no solution to transport all this transports automatically in development test client via mass transport strategy if satellite system is configured for ChaRM scenario?
Thanks a lot in advance.
Regards Urs

Hello Michele,
Please, check the point 5 in the link below:
/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
I think that this information can help you.
Best Regards,
Diego Fischer

ChaRM: usage of ChaRM and none-Charm transport strategy

Hi ChaRM-TMS Gurus!
We have the following [SAP system landscape |http://www.file-upload.net/view-1086963/SDN_TMS_Ist_Soll.jpg.html] and would like to use ChaRM approach simultaneously.
What are the minimal requirements concerning transport layers/routes, which settings should be changed?
How much and which transport layer/routes does ChaRM need?
a) 1 any new transport layer/route
b) standard transport layer, transport layer "SAP" and others
Should all the standard transport layer/routes from virtual systems to real QAS and PRD systems or can I start as follows:
1) Leave the current TMS settings unchanged
2) Activate the extended transport control
Result: the current setting will be client specific and all the old transport requests will be moved to client specific transport routes
3) change the transport strategy (from mass transport to single transport)
3) Define new transport layer
4) Define new transport route for SAP objects from DEV to QAS
and assign the transport layer from 3) (client specific)
5) Define new transport route ZXXX from DEV to QAS
and assign the transport layer from 3) (client specific)
6) Define the delivery transport route from QAS to PRD (client specific)
7) activate and distribute the settings
Thank you very much indeed!
Thom

Hi Martin,
Solmaniacs' assumptions are correct. You can have as many source clients as you want.
As long as
- STMS configuration (transport routes, and domain links) are consistent
- SMSY configuration (logical components are declared properly with assigning the right role types to systems/clients)
- Project declaration are done correctly (so that from Solman solar_project_admin you can read the STMS as confiured in the distant STMS domain)
- IMPORTANT: those configuration GO ALONG with each other !! (SMSY should nt contradict STMS for example...)
The tasklist that is generated for each Solman project will be as follow
- Node 1: Header Tasks (commun to all systems)
- Node x: Corresponding to track x declared in Project (each Source System will have his own node with the corresponding track under)
- Node x+1
- Node ...
- Last Node : Tasks for Tasklist closure - checks on scma consistancy and CTS projects closure
So you'll always have n+2 nodes in your tasklist; n beeing the number of declared source (=dev) systems in project
For each action launched from change docuemnts like creation of TR, release of TR or Retrofit (as Solmaniac said) you'll have an additional pop-up that will appears letting you choose the system you want to use for the action
Hope its helpful
Regards
Khalil

Charm implemenation for transports in solman 7.1

Hi Guru's,
Can anyone help me to get knowledge in charm implementation for transports in solman.
I am new to solman , can anyone help here.
Help is much appreicated.
Thanks,
Pradeep.

Hi Pradeep.
Please check the following blogs:
http://scn.sap.com/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
http://scn.sap.com/people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples
http://scn.sap.com/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
Thanks
Vikram

ChaRM with several transport layers

Hi!
We would like to use Solman ChaRM approach.
According to SPRO-documentation ChaRM only supports consolidation routes from standard transport layer.
We have besides the standard transport layer other transport layer and have the following question
1)What will happen when the developer try to change and import into QAS system object assigning to none-standard transport layer?
1a) ChaRM does not allow to change this object and the appropriate pop up window comes up
1b) ChaRM integrate this transport layer as standard transport layer
Any helpful information will be very appreciated
Thank you very much!
regards
Thom

Hello Thom,
I think, your question is almost independent from CHaRM. This is handled by the transport management system (TMS). If your developer changes the object assignment to a transport layer, and there is a transport track for this layer to the (same) QAS it should work. But if this QAS is not configured in CHaRM as a target system (in SOLAR_PROJECT_ADMIN), SolMan will probably raise an error message.
Also if the transport layer assignment / dev package not valid for this transport track, you will not able to release the transport -> SolMan is just using TMS mechanism and this will bring up an error message in CRMD_ORDER.
Unfortunately you can't see the transport logs in CRMD_ORDER directly, so the answer to 1a) is: In case of trouble releasing the transport you will get an error, but not the full error message.
1b) ChaRM cannot change a transport layer to a standard transport layer, this must be done using STMS on the transport daimn controller.
Regards,
Holger

Transport strategy of BI-BO Objects

How to transport the BI-BO objects across the landscapes? I mean WEBI, DEKI, XCELCIUS, Crystal and all other BO reports
created on BI Queries/Infoproviders.
Can we have BO reports saved along with our regular BEX Queries in BEX folders?
Can we publish BO reports in BI portal?
Plz help in understanding the transport strategy of BI-BO objects!!

If you're using XIR2 you have only one option - Import Wizard tool. If you are on Xi3.1 you have 2 options Import Wizard or LCM (Life Cycle Manager).
Documentation for both available at http://help.sap.com/businessobjects.
Can we have BO reports saved along with our regular BEX Queries in BEX folders?
No
Can we publish BO reports in BI portal?
Yes, if you're using CR reports.

Transport strategy for your transport landscape is inconsistent

Hello everybody,
we had 4 system landscape.
DEV>QAS>TST-->PRD.
we move the request from DDEV >QAS>TST and then forward request from TST to PRD system.
Now, we have delete the system TST from TMS, after deletion it give the warning.
Transport strategy for your transport landscape is inconsistent.
Message No. XT481
Please suggest, what is meaning of this warning and how to correct.
Thanks
Ganesh

You need to do following
1. Logon to domain controller client 000 -->STMS --> Overview System --> Select TST --> SAP System --> Delete
2. Reconfigure STMS DEV>QAS>PRD
3.STMS --> Overview Transport Routes --> Configuration --> Distribute and Activate (To All System)
Note : You should do this from Domain Controller client 000
I assumed you know Step 2. If you dont please let me know i can guide you on that as well
Cheers !
Manish

SAP Query Use and Transport Strategy

Anyone wish to share their experience in the use of SAP Query? We generally have an understanding that we don't want to be giving out this tool to end-users in Production. We would like to create queries, and when we wish to give them out we'll attach t-codes to them and roll them out.
However in practice, this is becoming difficult. An example is where in our gold client we create queries and then we would typically transport to our unit test client. But whenever we do an export, it generates a transport request. Before we are done testing we may end up with 10's of transports for a single query?
Anyone have some ideas on a transport strategy for SAP Query? How about it's use in Production? Our landscape for changes are typically DEV Gold -> DEV Test -> QAS -> PRD. We would ideally like our transport strategy for queries to match what we do for everything else.

HI,
Query objects are transported in different ways according to the query area in which they were created.
In order to know which transport options are available, you must first understand how query objects are created.
Standard Area
Query objects are stored in the client-specific table AQLDB. They are not connected to the Change and Transport Organizer.
Global Area
Query objects are stored in the cross-client table AQGDB. They are connected to the Change and Transport Organizer.
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb467f455611d189710000e8322d00/content.htm
Global area objects can be transported into other systems. Standard area query objects can not only be transported to other clients within their own system, but into all clients of other systems as well. In addition, query objects can be transported from the global query area to the standard query area and back within the same system.Transports are normally performed by the system administrator, not by end-users. For this reason, you need the appropriate authorizations
Check the below links for detailed explanation
Transporting Global Area Objects
http://help.sap.com/saphelp_47x200/helpdata/en/ec/052786a30411d1950a0000e82de14a/content.htm
Transporting Standard Area Objects
http://help.sap.com/saphelp_47x200/helpdata/en/ec/052789a30411d1950a0000e82de14a/content.htm
General Transport Description
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb4699455611d189710000e8322d00/content.htm
Generating Transporting Datasets
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb46a6455611d189710000e8322d00/content.htm
Reading Transport Datasets
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb46e7455611d189710000e8322d00/content.htm
Managing Transport Datasets
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb46f4455611d189710000e8322d00/content.htm
Transporting Objects between Query Areas
http://help.sap.com/saphelp_47x200/helpdata/en/ec/05278ca30411d1950a0000e82de14a/content.htm
I hope this solves your purpose.
Regards,
Vara
Message was edited by:
varaprasad bhagavatula

Problems and question with Transport

Hi,
I have two questions about transporter tool I cannot solve by myself :
-When Transporting from dev system to quality system, data (result of each KPIs) are also transported. How to avoid that ?
- When Transporting in Production, How to avoid to overriding data already entered by users ?
Thanks in advance
Matt

Matt-
SSM Transporter is not like BW in that there is no delta option for data. When using the Transporter you will transport all the Entry & Approval data with your metadata. SSM Transporter cannot transport subsets of data, other than those specified in the Transporter list.
I am not sure what you are trying to accomplish here, but assuming that you want to upgrade 7.5 in dev and then move that to prod, here is a suggested sequence.
Upgrade DEV to the new SP and transport your PROD data into DEV for testing. You also have to move PAS models as well to make sure that the structure of the models are the same. The PAS models are where your data is going to be. The Entry & Approval data is also carried in the SSM metadata as mentioned above. So when transporting PROD data into DEV select the Delete all data in database before import -YES.
Figuring that your testing will take some time, probably additional data will be loaded in PROD during that time. When you've completed your testing, you will have to find a weekend or some period to take your SSM PROD system offline. When you do that you take the PROD system offline and Transport the data again, so you capture all current data and transport that into your upgrade DEV system ( In DEV when transporting Delete all data in database before import - YES). So now your DEV system is the same as your PROD. If you want to make any quick tests to verify, it's recommended. When confident they are the same-
Now, upgrade your PROD system to the new SP and when complete you can transport the data from DEV back in. Check your system and if it checks out put PROD back online. This ensures your data matches the current sets.
This is the very shorthand version, you still have to do all the steps of backing up customizations and all the other things that go along with installing SPs as specified in the guides.
Regards,
Bob

SAP-XI Transport Strategy

Hello
Can anyone please point me to SAP-XI transport strategy document. e.g what would you transport, what tool would you use etc.
Thanks.

Hi,
We have two options
-- one is File transfer method through which we can export the objects into a file and that can be imported in another.
here we can export individual obeject and SWCv wise,namespace wise also.
-- Another one is CMS
through this option tracks are to be defined from DEV-QA-PROD
see the below links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db6306
Also...
How to configuring the CMS for XI?
Please see the below links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e
Where can I get installation files of DTR, CBS, and CMS?
https://websmp201.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202 -> How to Guide on
'How ToTransport XI Content Using CMS'.
/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
Regards
Chilla
reward points if it is helpful..

Transport strategy for BOE landscape

I am looking for a transport strategy for BOE landscape from security viewpoint. Basically we want to transport crystal reports, webi reports and folders along with security principles (BW roles/users included). Can anybody provide more info on this?
Regards,
Prasad

Yeah...we have LCM (XI 3.1 onwards) and Import Wizard for BOE tranports. But if we use BW roles as principles, transporting reports/folders with Security doesn't give desired results.
For example, if I am transporting a webi report with principle DEV001@RoleA from Dev to QA/PRD, I would get a new group in QA with name DEV001@RoleA instead of QAS001@RoleA. *I am looking for a pointer change here from DEV001 to QAS~001*. I think we have this feature of changing system pointers for Connections/Universes/Crystal Reports in LCM.
I know we need to move crystal reports and publish them again in QAS/PRD but this way we need to assign security for folders. I want to avoid these efforts by doing one time configuration in DEV and moving it to QAS/PRD through LCM. This is more consistent with current SAP Netweaver transport strategy.
Regards,
Prasad

CHARM - Refresh and Transport Log

Hi
We have configured charm if i refresh Dev or Qas system what will happen to the transport change log created by Charm.
is there any procedure to save the transport log(out side the system) or to take back up of the data before refreshing the systems.
Thanks
Nanda.

Hi Nanda,
the transport logs are neither stored in Solution Manager nor in the database of the refreshed system. They are stored in the transport file system /usr/sap/trans/log. So a system refresh should not have any impact to ChaRM regarding the transport logs. As Solution Manager is only controlling tp in satellite systems, there is no big difference in a system copy with Change request management and without (as long as you don't overwrite the transport domain controller).
So you can follow the same procedure as you did before activating ChaRM. Just make sure, that all RFCs between Solution Manager and Satellite system still work and user and roles in the satellite system after the refresh are being restored (but this you should always do even without ChaRM).
If you mean the history of change documents in Solution Manager: They are not affected by the system copy.
Best Regards,
Holger Slomka

Re: Workflow controlled Transport Strategy

Hi friends,
we are using workflow controlled transport strategy in our landscape. So far we are using existing help help.sap.com to configure the same. But we found that it is not enough for completing configuration in perspective of out client requirement. Can anybody help to get the more help on this?
Any help would be highly appreciated.
thanks,
krishna

SAP Note : 313991
Due to the approval of a request in the QAS system, this becomes
active in the import queue of system VDE (status: Request is ready
for import). Refused requests receive the following status:
Request was refused.
o The RSTMS_DIST_APPROVED_REQUESTS program is used to transfer the
requests with the status "Request is ready for import" from the VDE
import queue to the supply system of VDE (that is, the PRD
production system or, if necessary, several production systems and
clients) and then to delete them from the import queue of VDE.
Refused requests (status: Request was refused) are also deleted
from the VDE queue.
You can choose between the following options:
- Transfer all approved requests:
All approved requests from the VDE queue which are before the
end are transfermark (stop mark) red. All requests that have
not yet been processed with the QA procedure remain in the VDE
queue until a decision (approval or refusal) has been made.
cheers
dEE

Transport strategy for BPC

Hi all,
Is there a transport strategy for BPC. How do we move changes made in the development to the testing to the production environment? How do we transport the changes? Is it done manually or does BPC have a feature that automatically transport the changes? Does BPC keep automatically track of the changes?
Thanks.

I think this OP's message was posted in the wrong forum. In any case, there's a whitepaper on the transports for BPC 7.0NW.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b048ecf4-9414-2c10-ceac-fb2492a8016c
Hope this helps.
-Ken

ChaRM: Transport strategy

Hi!
We have the following system landscape:
EO1 --> QO2 --> VO2
EO1 --> VO3
VO2 and VO3 are both the virtual systems.
Between EO1 and VO3 and Q02 and VO2 we have a lot of transport routes (SAP, YABK, ZEO1, .., ZIAN).
Now we would like to use ChaRM approach with new client specific transport routes (EO1 --> QO2 --> PO1) as well as leave the old TMS settings unchanged.
The questions we have:
1) Do we need standard transport route u201CSAPu201D for the ChaRM approach?
2) Can we leave the old TMS configuration for old requests, but use ChaRM with new configuration?
Thank you very much!
regards
Thom

Thom,
1) The suggestions I see:
    a. create a Transport Group which contains your VO3 and QAS system and create the necessary transport routes to this group. If you now setup your project for ChaRM and only specify the real systems, SolMan will recognize the correct systems (even though it will give you a full overview of STMS when clicking the button 'Shipment Routes' in the System Landscape of the project - once the Task List is created, you'll see ChaRM only mentiones the systems you've added in the System Landscape). The disadvantage of this is that all Transport Requests you release in your DEV system will be added to the import queue of QAS and VO3. This is of course only a disadvantage if both systems don't need to receive the same changes.
   b. Not 100% sure if this is technically possible. Create separate consolidation routes for VO3 and QAS from DEV. Again when you specify the correct systems in the project, SolMan will use only those.
As far as I know, ChaRM doesn't make a choice based on type of transport route, such as 'SAP'.
2) a. I know 'single transport' is recommended by SAP, but this is not a showstopper for the configuration of ChaRM. ChaRM also works with 'mass transport'.
    b. ChaRM needs to be client-specific, can be that here there is some interference between ChaRM and non-ChaRM.
    c. As ChaRM corrections are all assigned to a Maintenance Cycle and a Maintenance Cycle is based on a CTS project in your DEV satellite system; SolMan is in complete control of your Transport Request. What I mean with this is that if you do automatic import on your systems, only your non-ChaRM changes will be imported. Because by default ChaRM changes all status switches of the CTS project to 'inactive'. From the moment you trigger the import from a Transport Request out of ChaRM in Solution Manager; only then the necessary status switch will be activated and it will be possible to import a change into your satellite system. Periodic import of ChaRM changes is also possible, but has to be scheduled using the correct Task List out of SolMan.
You can look and change these status switches manually in your satellite system with TA SPRO_ADMIN, select the correct project and navigate to tab Transport Request. Here is a button 'CTS Status Switches'.
Hope this helps you a little further!
Good luck and let me know if you have any more questions...
Roel

CharM questions (mix Transport strategy)

Similar Messages

Maybe you are looking for