Approach to transport in BI 7.0

Hi Guruz
BI 7 being new, i am a bit worried about the approach to use for transportation. Can someone give some broad guidelines on the approach to take for tranport to QA, like how to group, and any particular things to be kept in mind?
Also, we have created some proxy connections, using RFC datasources. how do i transport this proxies?
Thanks in advance.
Sushmita

Thanks Ravi for your prompt reply. Have awarded points.
But can you throw some light on the next part of the question?
We have built some RFC connections with XI, and we are using ABAP proxy methods to receive data from XI.
How can i transport these things? or do i need to re-build them in the QA and production system?
Pls throw some light on this as well.
Thanks
Sushmita

Similar Messages

Transporting a SAP Query from DEV to PRD

Hi,
We created a Query Report using SQ03, SQ02 and SQ01 for Travel Report in DEV and is working fine. Now, we want to move this query to PRD. For this, we tried create a Transport using SQ02>Environment>Transports and finally a transport request was generated and moved to PRD.
But the requisite Query, Infosets and User Groups are not there in PRD. Are we using the correct approach to Transport a Query to PRD?
Please help.
Regards,
CMC Team

1. While saving User Group in SQ03, save it in correct Package (not as Local Object) and a Transport Request will be created.
2. Create Infoset in SQ02 and save it in same Transport which was created in Step 1 above.
3. Create Query in SQ01 and again it in same Transport which was created in Step 1 above.
Release this Transport Request and move to PRD.
Hope it will help you.

Interactive Scripting Transport

Hi experts
I have created the interactive scripts in Dev System. I have used transport icon in ISE to transport from Dev to QA. But, when i have imported in Quality, Branching action (which is included in script) is missing / not got transported. I have transported the relevant ABAP class first, before transporting the actual scripts.
Can anyone guide me what is the best practice for scripting transport.
1) Is there anything i have missed?
2) How does delta-transport will work? Means, if i makes any change in Dev and transports again to QA, how it behaves?
3) What is the approach to transport Scripts that contain Branching/Non-branching actions?
4) Once transport is finished, can i activate the script again in Dev? Does it impact anything?
I would appreciate your expert help in this regard.
Thank you
Surya

Hi Surya,
Very valid questions asked and I feel disappointed that despite 4 yrs, I still stand at same place where you were in 2010. I also have the exact questions as I could not find any proper document related to IS transports. There many ifs and buts and dos and don't and with my experience in SAP CRM, I generally prefer to find the right ways and learn from the lessons others might have learnt when trying the same thing.
Can you please advice from your experience your take on the approach and procedure for IS transports for these questions ?
Thank you so much in advance.
Best Regards
Suchita

Large transports a problem?

Hello Folks,
in previous projects we always went for collecting objects into transport by type buttom up e.g.
1. Infoobjects
2. Data Sources
However, now we have enabled standard transport system and get prompts for every object creation. Which is convinient for developers as you save the collection process and you don't forget any object to collect.
General idea we got is to group now objects into process deliveries e.g. shipment load -> this would then contain all DSO, Cubes, Proces chains and even queries associated with this process.
With this approach the transports can get quite packed with objects.
Are large transports of any problem? My assumption is that it simply will run a bit longer on the target and yes there might be some exercise to fix problems (dependent object is in another transport). But overall large transports will work or did anyone had negativ experience.
Thanks for all replies in advance,
Axel

>
Axel wrote:
>
> However, now we have enabled standard transport system and get prompts for every object creation. Which is convinient for developers as you save the collection process and you don't forget any object to collect.
Actually, we dont't have standard transport switched on in our system, as we don't want to collect everything we create, it has its own pros and cons.
Anyway regarding large transports, we once tried to transport 150 queries in one transport along with dataflow (in a landscape where we have several transports transported in a day across tracks). We were not able to release the transport (the reason may be as suggested by shailesh patil ) , it used to get stuck in red.
Finally we managed to take help from Basis and load it in splits
On contrary, this may be successful sometimes too.

Dashboards - Transport methods

Hello
We have imported the Best Practice Dashboards and Crystal reports using our ECC development system as the datasource.
Does anyone have a method or approach to transporting these into QAS and Production without the need to individually map each one to the relavent source system.
Kind regards
Elaine

Hi
1) Import All is recommended & is supposed to be faster
1223360 - Composite SAP Note: Performance optimization during import
c) Use the "import all" strategy wherever possible.
If you can use organizational measures to ensure that the sequence of transport requests in the queue is correct, you should ideally process it with the "import all" strategy. Even if you are still working with individual imports in the Q system, it may be an option for subsequent systems.
1008058 - Performance of individual imports
The best solution is to change the TMS import strategy to the "import all strategy".
Import all is supposed to execute the import in a way that avoid sequence problems (it is supposed to process every import steps for all the orders avoiding dependency conflict).
2) Import of multiple orders selected in the import queue (that is not an import all but a multiple single imports) will be performed in the order of the request in the queue (oldest request first) this can lead to dependency problems if the order in the import queue is not good (and from my experience it is very often the case, as it is rare that developer / consultants synchronize themself to release order in an appropriate sequence).
Regards

Table record Transport

Hi
I have entered records in a table using transaction SM30 .Now I want to transport this data to another server using a transport request, but when I am saving the data it is not creating any transport request. Anyone please suggest me how to transport the data? TIA

Find one more approach to transport the entries:-
1. goto SE10 & create a work bench request. You can delete the Unclassified task under it.
2. Then double click on the main task. Fill it as mentioned in below :-
Program ID :-R3TR
Object type:- TABU
Object name :- Table name
then ENter, one key symbol will appear under Function column.
3. Now double click on this record which will lead you to fill the table keys. There you have to fill in the entries of the key values of the table.

Transport sequence in BI

I would like to know from your past experience, what is the best approach while transporting the objects. E.g. I learnt that infoobjects should go first then other objects etc. But I would like to have a list.

Shailesh,
transportation is an oft discussed topic on the forums - please search the forums before posting.
Arun

Using UC Correction as a NC correction workflow

I am trying to set up CHARM and I have found the the Normal Correction workflow is too cumbersome and actually may cause problems in our environment. I would like to use the UC Correction workflow as our maintenance cycle which occurs ever 2 weeks. Corrections that need to be imported into production could be imported as needed and the others could be imported on the 2 week schedule. Can anyone give me an argument as to why this is not a good idea.
Thanks,
Tania

The first time you install ChaRM I think there is a tendency to want everything to be ur.gent for flexibility. I would personally fight the urge to do this and also push back on the others that will try to coerce you into doing so.
Brilliant Point, something I came back to post in this thread, almost everything has to move quickly to prod as per most requirements, but moving into ChaRM's direction is not about just getting a new tool to handle your transports, but rather changing your approach to transports altogether. You need to convince your business stake holders to adapt to the mentality of moving to the release based approach of handling SAP ie become proactive and not reactive in terms of change management.
The normal correction brings structure to your changes and allows for proper testing. If you're throwing things in daily for non break/fix issues, I doubt you're testing everything properly before promoting it to production. It's not a best practice for sure, and *I would question why you're using ChaRM at all.*
You can establish multiple transaction types based on what needs to be delivered, but you must at all times adhere to the concept of having 2 primary types of changes, a normal one which works on the release concept, and an urgent one.
If everything moves urgent, eventually an auditor or someone like me will take issue with it.
Just my thoughts
Cheers!

Migrating from SAP BW 7.0 to SAP BW 7.4 on HANA

Hi Gurus
At present we are having a SAP BW 7.0 system on oracle database. We are planning to move it to HANA. as part of pre-requisites we need to upgrade the BW system to BW 7.3/7.4..After looking up various approaches, we have decided to re-implement BW 7.4 on sap HANA. so we have 2 distinct SAP BW systems - one on Oracle ( Up and running ) and 2nd on SAP HANA (newly build).
Some of the critical flows will be rebuild in the new server. Just wanted to know that is it possible to transport the flow completely from SAP BW 7.0 on oracle db system to BW 7.4 on HANA db system with the help of a Transport Request ??
Would you please advise any restrictions or limitations with any functionalities not being operational on newer version on HANA. and whats the best approach to transport and do we need to do any work at DB level ?
Thanks
Kris

Hi,
See the BW on HANA - Migration Best Practice TechEd 2014 Las Vegas/Berlin - ITM206
and the SAP First Guidance Document - SAP First Guidance - Migration BW on HANA using the DMO option in SUM
Best Regards Roland

Migrating 'production queries' back to DEV/QA in 04s

Hi All,
We anticipate that some of our 04s BW queries/reports will be developed in our dev system and migrated to QA/production, and that some reports will be developed directly in production as 'ad hoc' reports. These 'ad hoc' production-built reports are often valuable reports to have in the dev/qa landscape for future project/regression testing.
In BW 3.x, SAP documented an approach using transports to collect BW queries in a production system and transport them back to a dev/qa system.
Has this process changed in 04s? Is there a different recommended that we should consider? Advice on using XML export/import instead?
Thanks!

Hi Lonnie,
I haven't tested it but it should be the same in NW2004s. Using XML is not a good option for transporting between SAP systems. That's what the transport mechanism was designed for!
Regards, Klaus

Best approach for backup and transport (NW BPC 7.5)

Hi,
we are currently in a situation, where we have developed a prototype in a Q (quality) envoirnment. This has been a standalone system sofar.
Now we have a Development->Quality->Production envoirnment - and I want to move my prototype from the Quality system to my Development system.
I'm thing about the "UJT_BACKUP_RESTORE_UI" program. I will not copy masterdata and transactional data.
My question is now. Is it possible to backup my Appset prototype in Quality and restore it under a new Appset Name in development, and then put in it a transport request ?
Or would I have problems with technical names for cubes and dimensions ?
What is the best approach ?
Thank you,
Joergen
Edited by: jdalby on Jun 14, 2011 9:49 PM

Hi,
First of all, you should have posted your question in the BPC for NW forum.
Coming back to your question, you can try the transaction UJBR. You can take the backup of metadata / masterdata / transaction data or any combination of those.
I wont suggest you to change the name of the backup files. Instead, you can create a copy of the appset and then take the backup and restore it in DEV.
Hope this helps.

Transporting of the Hyperlink approach with the hardcoded url's

Hi. VC guru's.
                   We have developed VC models with Hyperlink
option with the hardcoded url's.
                  when we execute the model we could be able
to get result. But our concern is
       1) There could be any issues we need to consider before
we Transporting models with hyperlink option with hard coded url's?
      2) how we transport the Hyperlink approach with the hardcoded url's through the landscape?
      3) As per my understanding , Based on the target system in the landscape we would have to adjust the hyperlinks. Not sure if the Portal transport system allows us to do that.
          Then in this situation what could we have to do?
                       Please provide your valuable inputs. we are
waiting for your inputs. Points assured.
                       Thanks and Regards
                        Prabhakar. B

Hi,
The same method we used to pass parameters to the 2nd and 3rd i-views (Thread: Hi. Friends. Unable to Pass Parameters in Visual Composer) can be used here to pass parameters to the first i-view, one of which can be the address of the machine which is running the i-view.
This means that the 1st i-view will have a start point with for example, the field "host_address", which can be stored in a datastore, and then the URL of the button will be dynamically built using this field.
(for example the formula will be in the form of =datastore@host_address & "/irj/portalu2026")
Alternatively we can use 2 parameters for the accurate address of the 2nd i-view and of the 3rd i-view.
Hope this helps.
Regards.
Omer.

Tcode or a easier approach to release bunch of transport requests at once

Hi all,
Can anyone tell me if there is tcode or a way to release transport requests in mass i.e., selecting all the requests created by a user and releasing them all with one click.
CATT might work but I am not sure..can anyone confirm that it can be used?
Any easier way than doing it one by one is highly appreciated. Points will be awarded for the help.
Thanks,
Kumar

Hi ..
One thing you can do. Create two separate test program. In one program write simple one write statement and from another program submit the previous prog via job .
do 1000 times.
call function 'JOB_OPEN'
    exporting
      jobname          = l_name               "Job Name
    importing
      jobcount         = l_number             "Job Number
    exceptions
      cant_create_job = 1
      invalid_job_data = 2
      jobname_missing = 3
      others           = 4.
if sy-subrc = 0.
Submit the job in background
    submit z2nd_prog
    via job l_name number l_number and return.
    if sy-subrc = 0.
      call function 'JOB_CLOSE'
        exporting
          jobcount             = l_number
          jobname              = l_name
          strtimmed            = 'X'
        exceptions
          cant_start_immediate = 1
          invalid_startdate    = 2
          jobname_missing      = 3
          job_close_failed     = 4
          job_nosteps          = 5
          job_notex            = 6
          lock_failed          = 7
          others               = 8.
enddo.

Best approach for BDLS Transports

Hi floks,
we are having BWQ pointing over to R3Q and BWQ pointing over to R3Z.so while transporting the objects we are getting some difficulties and errors like RS Basis idoc table corrupted...can anyone suggest good methods for BDLS to switch from BWQ to R3Q and BWQ to R3Z..
I dont have an idea about BDLS transports...can anyone explain about it.
thanks,
andy

Based on my experience we ran TA BDLS in particular system e.g. after sys copy from PRD to TST system we exchanged SID of copied PRD system to SID=TST. I do not think that you have to transport any BDLS stuff.

Unit Testing approach

Hi,
We had done technical migration of value based roles to derived roles, and facing problem to design the unit testing approach for the same. can you please suggest what must unit testing approach and how to create test cases for authorizations specificaly to derived roles created from value based roles ?
goal is after testing, end users should not feel any changes done in roles approach.
Thanks.
Regards,
Swapnil
<removed_by_moderator>
Edited by: Julius Bussche on Oct 7, 2008 3:40 PM

Hi Swapnil,
The Testing of Security roles need to be taken in a two step approach
Step 1 Unit Testing in DEV
A. Prepare the test cases for each of the derived roles and ensure that your main focus is to see if you are able to execute all the tcodes that have been derived from the parent role with out authorization errors. You also need to verify if each of the derived roles are applicable to those respective Org level Values.
B. Because there will not enough data in DEV ( except In some cases where you have a refresh of fresh PROD data) it is always advisable to do the actual testing of the roles in QA. The goal here is to see if you are able to perform a dry run of all tcodes/Reports/Programs that belong to the roles.
C. You may create fewer Unit test ids as you only assign one ID with one role and once the role is tested you can assign the same ID to another role.
Step 2 Integration Testing in QA
A. Prepare the Integration Test cases for each of the Derived roles. Here most likely the testing will be performed by the end users/Business Analysts in that respective Business Process. Each test case must reflect the possible Org level Authorization Objects and Values that need to be tested.
B. As Integration testing is simulation of actual Production authorizations scenario, care must be taken when creating mulitple Integration test user ids and assigning them right roles and send the ids to the end users to perform the testing in QA.
C. The objective here is that end user must feel comfortable with the test cases and perform both Positive and Negative testing. Testing results must be caputured and documented for any further analysis.
D. In an event of any authorization errors from Integration testing, the authorization errors will be sent to the Security team along with SU53 screenshots. The roles will be corrected in DEV and transported back to QA and the testing continues.
E. Also the main objective of Integration testing would be to check if the transactions are reflecting the right amount of data when executed and any mismatch in the data will be direct implication that the Derived roles do not contain the right Org level values.
Hope this helps you to understand how testing of Security roles (Derived) is done at a high level.
Regards,
Kiran Kandepalli.
Edited by: Kiran Kandepalli on Oct 7, 2008 5:47 AM

Approach to transport in BI 7.0

Similar Messages

Maybe you are looking for