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

Similar Messages

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

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

SPAU SPDD Transport Strategy for following Upgrades

Hello All,
We are doing CUUC from 4.7 NUC to ECC 6 Ehp4 UC
After completing our Upgrade from 4.7 NUC to ECC 6 NUC in the original host, I stopped the Upgrade tool at the point when it asks for SPAU adjustements in Post Processing Step, did the Unicode Conversion in which we built the Target ECC 6 UC System in a separate host (host: ecctemp).
So,
1. The Upgrade Directory and ECC 6 NUC System resides on the first host.2. The Second host(ecctemp) contains only the ECC 6 UC System.
3. We started our SPAU activities in the ECC 6 UC System after CUUC process completed.
4. Now, with SPDD & SPAU activities getting completed. I want the 2 Transports to be used for rest of the Upgrades.
How do I go about this?
1. I cannot run 'SELECT FOR TRANSPORT' or run the commands as per 68678 in the ECC 6 NUC System as thats where I didnot do SPAU.
2. I cannot even run the commands as per 68678 in the host ecctemp, becuase there is no upgrade directory here.

Hi,
You can add SPDD transport on your non-unicode system in umodauto.lst file and take this file to your quality system (also data file and cofile). So, when you will start upgrade on your quality system then upgrade tool will first read this umodauto.lst file and it will prompt you on the screen to has this transport as SPDD transport. And upgrade tool will then import this SPDD request.
For SAPU, you can simply move data file and cofile from your final system to quality system. And once your quality system will be ready after upgrade and UC conversion then you can simple import this transport from STMS. This will solve your issue.
Thanks
Sunny

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

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

Release strategy for Transport requests

Hi,
Can anybody give me the detail steps to configure release strategy for transporting requests?
we are having Dev and Prd systems.
Regards,
Vinnu.

Hello,
I hope you have configured TMS for two system landscape.
Just make the transport routes also, make DEV system as a Domain Controler.
Then transport requests will automatically come in to the request queue.
Using tx stms_import , import those request sequentially !!
Note: Points always encourage me to reply !!

Transport target for business system not found in System Landscape Director

Folks,
We have new installed new PI 7.1 system and importing interfaces from the OLD XI 3.0 system in to new PID 7.1 system.
We are getting following error when we try to import an interfaces in to new PID system:
Import failed because of business system transfer object
Communication component XID_FileSystem: Obligatory
transport target for business system XID_FileSystem not found in
System Landscape Directory
We are yet to install PIQ system.
All the interfaces in the old XID system have transport target of XIQ system. I removed the transport taget for the interface, but transport target is still showing in the Business system under transport target head.
How can we overcome this issue as we will not have PIQ system atleast for two weeks.
Thanks in advance,
Regards
Chandu

Hi,
You need to maintain Transport Groups and target for business systems while SLD transports between your XI system and PI 7.1
Illustrated with DEv & PRD here.
Procedure:
1) Call Integration Builder screen on DEV Server with http://hostname:J2ee Port/rep
2) Call SLD (System Landscape Directory) Component from the Integration builder
Save all the Following .zip files on the Local Desktop
3) Select the Software Component & say Export that you want to Export from DEV
Server to Production server and which is going to use in the IR of XI
4) Also Select the Product of the above SWC and say Export
5) Select the Technical Systems (TS of XI & TS of the SAP R/3) and say Export
6) Select the Business System(s) & say Export; those are associated with above Exported
Technical systems.
In Production Server
1) Logon to the SLD of the Production Server.
2) Create a Technical System and Business system which points to the Production SAP R/3
3) Go to Administration TAB in the main page of SLD
4) Select the Import option to Import the SWC , PRD, TS,& BS which we Exported Earlier in DEV Server
5) Click on Browse and select the .zip files that is to Import into Production Server,
Which were stored on the local desktop at the time of DEV Server Export
And say Import Selected File Option
By this we exported and imported the SLD Objects
Now we have to create transport groups and transport targets in the Production server of SLD
Creation of Transport Groups
Edit GroupsGroup1) Select the Business systems
2) Click on New Group and give the name of the group as DEV_group & select the
Corresponding Development serveru2019s integration Server
3) Similar way create another group for Production serveru2019s business system as
PRD_group and select the Production serveru2019s integration Server
Creation of transport targets
This is to Define which business systems in two different groups correspond to each other
1) Select each Business system in the SLD and select transport TAB---click on
Add/Change Target and select its corresponding target business system.
For Example:
If you select the business system of Production XI server means
In the target you have to select group as DEVGROUP and the business system of Development XI server.
Like this do the same for other business systems also
Ex:
BS_PRD_Integration Server----
BS_DEV_Inetration Server
How to create Transport Groups & transport Targets
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
Regards
Seshagiri

Define Derivation Strategy for Control Objects - Value Not Transport

I created Rules Value in Define Derivation Strategy for Control Objects (SPRO). Then, I perform the below steps for Transport the Request to other client.
1. Select Derivation Strategy name, Table View > Transport
2. Select Request Number
3. Click Include in Request, then save
4. Go to the Steps in Logical Order, Extras > Transport
5. Select Request Number and back to SPRO screen
After SCC1, there is only Derivation Strategy Name appeared but the rules value (Steps in Logical Order) is not appeared.
How can I transport the Rule Value?
Regards
Ton

Hi,
When you are in the derivation transaction and select to transport it, the system asks you whether you want the values to be transported as well. If you choose 'yes' your change request will include this information.
Regards,
Eli

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

Landscape Strategy for SM1 & SM2

Hello all,
I am new to Solution Manager (and SAP in general) so I came here to seek for your opinions.
I have SM1 and SM2 installed in one box. SM1 serves as our playground (sandbox) and SM2 serves as the semi-prod.
SM1 is in Solution Manager 7.0 EHP1 SPS 20 while SM2 is still in Solution Manager 7.0 SPS 16.
Currently, I have 11 other systems as follows:
- ECC 6.0 (1st and 2nd instances)
- PI (with SAP NetWeaver 7.1)
- XI (with Netweaver 04)
- EP with NW 7.0 (1st and 2nnd instances)
- BI with SAP NetWeaver 2004s (1st and 2nnd instances)
- SRM 7.0 EHP1 SPS 03
- APO (SCM 5.00) (1st and 2nd instances)
all 1st instances are treated as dev systems while 2nd instances are treated as semi-prod systems
How can I go about the Landscape stategy for the two? That is, which systems to connect to SM1 and which sdystems to Connect to SM2?
i was thinking of the following concepts:
1st option:
#1   SM1 (dev't) - only satellite systems that are NOT on the path to production would be connected here - such as a sandbox. This solman system would be used for configuration of solman itself example, your solman team would configure solman functionality here. It is also a good practice environment for PM's because it would have a small landscape attached to it your sandboxes, remember? Migrations start here for solman functionality...
#2   SM2 (semi-prod) - ALL path to production satellite systems are connected here, except your sandboxes which were connected to SM1. This system also serves as a target system for migrations that came from the dev system (SM1) for solman functionality itself. This is the main solman box that most users will access for project management, blueprinting, config, charm, and so forth.
can this be possible?
2nd option:
#1   Sandbox Solman - no satellite system connectivity; open access; used for the purposes of testing patches and exploring solman functionality - mostly for basis' purposes.
#2   'Development' Solman - only satellite systems that are NOT on the path to production would be connected here - such as a sandbox. This solman system would be used for configuration of solman itself example, your solman team would configure solman functionality here. It is also a good practice environment for PM's because it would have a small landscape attached to it your sandboxes, remember? Migrations start here for solman functionality...
#3   'Production' Solman - ALL path to production satellite systems connected here, except your sandboxes which were connected to #2 remember?. This system also serves as a target system for migrations that came from #2 for solman functionality itself, This is the main solman box that most users will access for project management, blueprinting, config, charm, and so forth.
for the 2nd option, I will have to install a new SolMan system to have a three landscape.
please advise.
your insights will be very much appreciated.
thank you.
charisse

Hello Charisse,
I am not sure you are understanding the use of Solution Manager to manage your system landscape.
Typically one Solution Manager will manage the entire system landscape, and systems of all types, PRD, QAS, DEV, SANDBOX, TRAINING, etc.
You can still have DEV and TEST and Sandbox Solution Manager systems, but they would be for those functions, developing, testing, learning and would not be managing your system landscape as that would be the role of a production Solution Manager system, normally.
You should start here - https://websmp207.sap-ag.de/solutionmanager, then also navigate to the "Media Library" where you will find a collection of Presentations, Articles and Brochures, Documentation, Technical Papers and How-To's.
Of course you will find the Knowledge Transfer Ramp-up Kits very helpful - http://service.sap.com/rkt-solman
And also the help library is often quite useful - http://help.sap.com - select the Solution Manager product and then select the applicable version.
You should find these resources quite helpful in determining a strategy for your system landscape and grow your Solution Manager knowledge.
Regards,
Paul

Transport request for Maintenace Strategy in IP11

Hi
I have a querry
can we create a transport request for Maintenace Strategy in IP11.
Regards
Neelu

Hi
Pls check "Incl in Transport "will not be in enabled condition.
It is a master data which will be created directly by IP11
Regards
Jignesh

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.

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

CTS+ Transport Strategy

Dear all,
We are planning to setup CTS+ in our system landscape.
Please provide your inputs, on the pros and cons of this strategy.
Also direct me to links of CTS+ documents on SDN.
Thanks for the help.
Regards,
Younus

Hi,
CTS+ transport is like ABAP way of doing transport of ABAP objects in r/3..........after deploying CTS+ in your XI system, you can release your objects for CTS+ transport from IR, ID and then a transport request for it will be created for you, which you can then release and finally import it in target system.
Regards,
Rajeev Gupta

Transport strategy for BOE landscape

Similar Messages

Maybe you are looking for