Personalization in BEx: transport activation to production ?

Hi,
on our development system (SAP BW 3.1) we have activated the "personalization in bex" via "BW Customizing - Implementation Guide - Business Information Warehouse - Reporting-relevant Settings - General Reporting Settings Activate Personalization in BEx".
Is there a possibility to transport the activation to consolidation/production system.
Thanks for your help.

Locking the users is the primary step. This is done so that while transporting the changes there are not entries made.
If there are entries made, there is every chance that you will loose that data as your Data source has undergone a structural change.
Users have to be locked. Its a must.
You can minimize your downtime if you are not filling the Setup tables for History Data.
Or if you are filling the Setups for history data, then you will have to plan it out in such a way that it requires minimum time.
Users need not be locked if the change is not affecting any Data Source (Live or New). But in your case, there is a change to the DS. So, please Lock the users before transporting.
Regards
Vishal

Similar Messages

Bex transport in SAP BW 3.1

Hello everybody,
how do you organize Bex transport in SAP BW?
In our installation, we find it necessary that some queries need to be designed in development system and tested before transport in production. We would like the person who's creating these queries to be able to create and release the transport for his query himself. With just one standard Bex transport this seems difficult to implement: In our constellation, the standard Bex transport can not be transported to production system, because it may contain test queries, which are not wanted in productive system at all and collects changes of different projects and persons, so it may contain objects that are still in test status, while others need to be transported to production system. Collecting into different requests is only possible if the concerned objects belong to different packages?
Collecting the needed objects in a transport request manually can't be done without releasing the Bex transport first because otherwise the objects are locked.
How do you organize Bex transports in your system landscape?
Thanks for any suggestions, Kathrin!

Hi Kathrin,
if you create a query in the development-system, the query will go to the Package $TMP, so no Transport is necessary. If you have a naming-convention, like <InfoProvder>_QU_nnnn or someting else for non-test Queries, it is easy to fetch them in the Transport Connection (Admin Workbench) and transport them in the production-system.
Hope this helps,
Regards
Frank

Recent Workflow Version not active in Production server

Hi Gurus,
Recently, I made a minor change to an existing workflow. After the changes, it was transported to QA and Production. In QA, the changes are reflected and when I click on the version overview tab of the workflow, I can see that my last changed version is the active version. But, In production server the last version is not active. The previous version before my changes remains as the active version. Though it shows my version their, it is not active and the change are not yet reflected.
To solve this I tried following ways,
1) I refreshed the buffer in SWU_OBUF in Production, but no improvements.
2) Then I tried to check, if there could be any errors when I activate the workflow in Development server. But, there are no errors except few warnings like some of the variables declared for the workflow but not used. So, this also does not help.
3) Then I tried changing the workflow to tag it again to a transport request thinking in a way, previously there might be a problem in attaching the active object. But, even after transporting the second changes, the workflow version is still not active in Production. But, it is active in QA.
Please let me know, if I can try any other ways which is not mentioned above!
Thanks a million.
AM

Hello,
Check the transport logs for any errors and make sure all the transports have been done, and in the right order.
What was the minor change that you made?
You can get situations like this when you eg create a task, don't transport the task, and then add the task to a workflow and transport the workflow. In Development all will be fine, but not so in QA and/or Production.
regards
Paultje Bakker
Hanabi Technology

Transport activation date needed

Hello,
following problem. We imported too many design objects from dev into production. We would like to find out for which objects in production a new version was created by the transport. That information cannot be derived by the XI 3.0 Transport GUI functionality (we are using file transport) because:
- the history lists in dev and production are identical because of the transport
- the history entry does not show the date when this version was made active in production. It only shows when it was originally created in dev. So we do not know if before the transport, the newest version already existed in production !
- the number of imported objects also does not help on that issue. It also counts objects which have already had the same version in production, meaning transport did not touch them. According to my understanding, the transport import function detects when the versions are already the same and skips that object.
Isn't there a way to get a list of objects which have REALLY been changed by that import in production ? Maybe a logfile from the transport ?
The problem is that there may have been some changes in dev which were not meant to be transported.
CSY

Hi,
I think there is no other way to check this...
even though its a file transport i think everyone uses the Transport request process in ABAP stack where in each Export file will be tagged to a TR number which will differentiate the transports.
i know this is not solution for your problem, but i think this is a good procedure to follow to avoid problems like this...
Thanks..
Karna.

Abort Released BEx Transport

Hi all,
I made a mistake when I want to transport my ODS and infosource to production from Development by clicking the BEx transport. I realized that I made a mistake is when I try to open Query designer in development. it give me an error "BEx transport request '' is not available or not suitable". anybody know how to solve this problem without overwrite the query in production?
thank you in advance

Hi,
The query will not be overwritten till the released request is imported to prod. If imported it will overwrite with the changes. If released but not imported to prod you can collect the ODS and Infosource in a new request from transport connection (manual collection) and release the request. If the request is already imported to prod just collect the query in a new request and revert the changes and transport it again.
Check the possibilities.....

Version not active in production

Hi experts,
I have transported workflow from development to QAS and production but my workflow having 5 versions but no one is selected as active in production,
in quality version is active.
i executed transaction SWU_OBUF. also i activated in dev, created transport request and released but still version is not active.
please tell me step to activate the version
Thanks Deep

Hi,
If there is no error's in workflow, then it might be the buffer issue.
Create a new version in Development client and then save the workflow. Surely it will ask for the request. Then activate the workflow and Transport it to production via Quality.
During the transport, try to close your workflow in all clients.
After Transport is successful, Log in to Production and check it.
Thanks,
Viji.

Activate Personalization in BEx

Hi
I have read in the forums about Activate Personalization in BEx but its not very clear to me.
1. What is the advantage of activating Activate Personalization in BEx?
2. If we DONT activate, is it not possible to run BEX Reports?
3. What will happen if i activate and advantages and disadvantages?
4. Is it used as user point of view or performance point of view?
REgards
Annie

Annie,
Forgot your questions part...
1. What is the advantage of activating Activate Personalization in BEx?
Have already discussed above
2. If we DONT activate, is it not possible to run BEX Reports?
Yes, its pretty much possible to run Bex Reports, as this personalization is just for users comfort
3. What will happen if i activate and advantages and disadvantages?
If you activate: Only Advantages, no particular disadvantages as such.
i) By personalizing the Variables, as in your list of personal values will be displayed for you to pick
ii) By personalizing the history view in the BEx Open Dialog you can select BW objects from those that you opened recently (such as queriesand Web templates) from your history.
iii) By personalizing the start views of Web applications, you can save a user-specific navigational state in Web applications as a personalized start view of the Web application.
4. Is it used as user point of view or performance point of view?
User point of view
Hope this helps you...
Regards,
Habeeb

Standard BEx transporting Request

Hi Dudes,
Can u explain me with a scenario, what is this Standard BEx Transporting Request and what is the purpose of this,
Thankyou.

Hi,
This is what note says:
Symptom
Editing of a query in Query Designer may return the various error messages concerning transport system. Query or query component can not be changed or saved.
The following error messages are possible:
'Query could not be saved due to a problem in transport' message R9 124;
'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
'Object ELEM XXX... could not be saved to order YYY...';
'A dependent object is being locked by the transport system' message R9 113
'The dependent objects are in different transport orders' message R9 114;
'The upgrade is already running - you are not able to change objects'.
In some particular cases using NW 2004s server with 3.x Query Designer
'Operation failed, no message available from server'.
Other terms
Query, Query Designer, Correction and Transport System, CTS, ELEM, Transport Request, Changeability.
Reason and Prerequisites
The error messages rise as the result of wrong administration of Correction and Transport System (CTS).
Transport System Mode
Two main modes of Transport System can be used for BW system: Standard Transport System and BW Transport System. Both modes require different administration efforts.
Standard Transport System (system default)
Within this mode an assignment of newly created query elements is done during save procedure. System asks for appropriated Package and corresponding Transport Request within this Package. The mode allows separating of changes done in the system different users in different Transport Requests. Users must be authorized to create new Transport Requests or to write into existing Transport Requests.
BW Transport System (recommended for handling of BEx objects)
Within BW Transport System initial assignment of newly create query elements is done automatically to $TMP Package. This is a Package for temporary objects and does not require modifiable Transport Request. Changes of those query elements can be done without further restrictions. Further assignment to a Package and corresponding Transport Request can be performed using Transport Connection of Administrator Workbench (transaction RSA1).
All kinds of changes for query elements which already have been assigned to any Package different from $TMP (for example, queries transported from another system) must be registered in so-called Standard BEx Request. Using Standard BEx Request all changes done to query elements can be also transported to any other system. If the old Standard BEx Request has been released, another one must be created immediately in order to allow further changes for query elements.
The typical reason for error messages listed above is a situation when NO Standard BEx Request is available anymore in the system. The algorithm of query SAVE contains a transport systems check. If the transport system check fails, no changes are possible.
Changeability of query elements
The recommended setting for query element (ELEM) is 'Everything Changeable'. Using of other settings, like 'Original Changeable' or 'Nothing is Changeable', will make editing of objects not possible when the general system changeability will set to 'not changeable' (SCC4).
Setting 'Original Changeable' allows changes only for query elements which have been created in this particular system. Quite often an ordinary query may contain, for example, variables or other reusable components created in the other systems. In this case changing of a query containing those objects will be not possible.
Changeability of Package
Package (Development Class) where the corresponding Transport Request has to be created must be changeable. If a Package has a property 'Package is not extendable' set to true, no requests can be created within this Package. This means no objects can be registered.
Solution
The following messages mainly happen if BW Transport System is activated. The existence of Standard BEx Request and correct settings for object changeability should be checked.
'Query could not be saved due to a problem in transport';
'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
'Operation failed, no message available from server'.
How to create a new Standard BEx Request?
Start Administrator Workbench (RSA1) --> Transport Connection. Find button BEx. Under the button user is able to create/assign a new Standard BEx Request.
How to check Changeability of object?
Start Administrator Workbench (RSA1) --> Transport Connection. Find button 'Object Changeability'. Set property 'Everything changeable' for query elements (ELEM).
How to check Changeability of Package?
Start transaction SE80 --> select corresponding Package --> find properties dialog. Check whether the property 'Package is not extendable' is set to false. Assignment of query elements (R3TR ELEM) to a corresponding Package is stored in the table TADIR (field DEVCLASS). In order to obtain a list of query elements used in a definition of a particular query having problems use the function RSZ_X_COMPONENT_GET with the I_OBJVERS = 'A', I_COMPID = technical name of a query. Execute the function and copy all elements (ELTUID) from the exporting table C_T_ELTDIR. Use this selection as the input parameter for selection from TADIR table (field OBJ_NAME). Collect all Packages and check the changeability as described above.
The following messages mainly happen if Standard Transport System is activated. The problem happens in case, when one or several objects from definition of a particular query have been already written in another modifiable Transport Request. In BW 3.x each object can be processed only within one Transport Request.
'Object ELEM XXX... could not be saved to order YYY...';
'A dependent object is being locked by the transport system';
'The dependent objects are in different transport orders';
The situation may happen, for example, if a Query A contains a variable which has been already used in another Query B assigned to different Transport Request. In this case, saving of Query A will be not possible while the Transport Request containing the shared variable is not released.
How to find an assignment of object to a Transport Request?
Start transaction SE03 and select 'Search for objects in requests/tasks'. Provide ELTUID of the element which can not be saved. Object type is R3TR ELEM. Search for modifiable Transport Requests containing this element. If corresponding Request is found, it can be released. After that is will become possible to save this query element into another Request.
Changing of query elements during running upgrage is not possible. The system sets a global lock in order to prevent any change which may potentially affect the consistency of objects. In such situation users should stop the upgrade procedures and wait until the process will finish.
Regds,
Shashank

BEx transports

Hi,
I have created a Bex Transport and I know how to transport the changes. But just want to make sure, what is the diff between two truck symbols
in the transport connection when we collect the objects. It looks like all my changes are already captured in my change request which I created
using the Create Transport requests for Bex, now do I need to collect the query and Query elements in another request by clicking the transport objects
Or just relesing the one I already have will update the changes in Porduction ? Please advice.
I know that once I release my request, I need assign new one to capture all bex changes...thanks
Sam

Thanks Srinivas, yes it has already collected all my changes. So I'm wondering if just releasing this req will take care of the updates ? Release the request it will transport all the changes to target system
Do I need to collect the query in new request or not required ?.... Not required
also once I release this requeste I need to create new one right , Yes. Create new for future changes if any, they will be saved in this new req
so that all the bex changes will be captured...But I'm wondering what if some one dont want to import their changes in to production...Please advice. .. One person has to take incharge for all these things... he will co-ordinate all the people and will make sure which query to be transported! If there are too many people doing changes in the queries... better not to create Bex transport request.... assign your query modifications to one normal request and tranport to avoid conflicts

Problem during import of 121 transport requests to productive system

Hello
We have problem during import of transport requests to productive system. Import of 121 transport requests stopped very soon in phase "N" (in TRBAT I have only one entry and in TRJOB as well).
In sm50 there is an BGD running under user DDIC in client 000 now for 14453 seconds (program SAPLSDB2). This should be import.
In SM37 I can see it as job "RDDGEN0L" with repport"RDDGENBB". Based on some literature it should perform "Converting all structure changes generated by the import and recorded in table TBATG, other than the structure changes to matchcode objects." Very interesting that TBATG has only four entries related to 2 indexes in table "DFKKOPK" , one in table "DFKKREP06" and one" ENQU" for EFKKEXC". (only this last one has not status error)
For fist two indexes I know they are not present as objects "LIMU""INDX" in any transport request beeing imported.
Also on productive system there is no"VOL" and "ZOL"indexes for table "DFKKOPK"(instead they are created on test system ie. not transported from development to test system)
Last command for that process is "CREATE INDEX "DFKKOPK~HKO" ON "DFKKOPK" ("MANDT", "HKONT", "OPBEL") PCTFREE 10 INITRANS 002 TABLESPACE PSA
PTR3 STORAGE (INITIAL 0000000016 K NEXT 0000000016 K MINEXTENTS 0000000001 MAXEXTENTS UNLIMITED PCTINCREAS"
There is enaught space on disk and in tablespaces (it is an oracle/HPux server).
Does anyone knows workaroun to solve production

are you importing these transport requests simultaneously into production?
I would suggest you try doing in smaller groups of 5 or 10 and then see whether you are able to import the requests
Rohit

What is the difference between Bex transportation and Normal Transportation

Hi experts,
I have doubt with Transporting queries , in this I've used the normal transport (truck icon) rather than Bex Transport. I would like to know which is the preferable one and what is the main difference between them.
Suggest me if I can go for normal Transportation rather than Ibex transport, as I've not tried Bex transportation before.
Give me some valuable inputs please.......
Regards
Kumar

Hi Kumar,
We have a Bex transport because we may make changes in the query very often and these changes will be automatically taken care by Bex transports.
Generally this is how it goes.
You will capture the queries by creating a transport request and immediately you will create a Bex transport request and you have to assign the previously created transport request number to this Bex transport request, so that everytime you make changes to the query will be taken care by the Bex transport.
You can even create a Bex transport request individually.
Hope this tip may be useful.
Assign points if you find useful
Thanks
Regards
Sam Mathew

Query transport-normal transport or BEx transport?

I could able to transport the backend objects but not sure about query transport. I would like to know difference between normal TRUCK transport and TRUCK-BEx transport in transport connection for queries. Can I use any or there are specific rules when to use what.

HI,
Bex transport truck mean you can create a global transport for you queries, when you transport your queries from dev to qa those queries wont be editable in development system unless you define this global transport. Everytime you make the changes in those queries these changes will be automatically gets updated in this global transport. Finally you dont have to retransport these changed queries, you have to simply release this global transport and the changes gets updated into quality server. The second transport truck is normal transport, and can be used to transport reports from dev to quality.
So bex transport is useful and you dont need to create a request after every change in report.
Hope this will help
regards,
ray

No active external product for the fuzzy search (FBL1N)

Hi,
I am in transaction FBL1N and want to search the vendor by F4 help.
1. When I hit F-4, the Search window appears.
2. It gives an pop-up message "No active external product for the fuzzy search".
3. When we open the help for the pop-up message it says :
No active external product for the fuzzy search
Message no. F2807
Diagnosis
The connection of an external product is required for the fuzzy search.
For more information, see Note 176559.
I have looked through the SAP Note 176559 but was not really relevant.
Regards,
Rohidas Shinde

How do you test any SAP objects before a transport to the production server

How do you test any SAP objects before a transport to the production server?

Hi Rama Krishna,
The actual process is develop the object in development system and unit test there with the available data.
Then move it to Quality server where the data will be the actual replica of production and where the integration testing and ened to end testing happens and also the user acceptance testing happens there.
and once everything is found fine there then it is moved to production system.
Award points if this is helpful.
Regards,
Ravi G

Create business activity with products

Hi,
I am Trying to create a business activity with products. Adding Activity Journals TAB in the activity u201CBus Act.:With Prodsu201D. The issue is that when I am trying to make a Journal template type in (CRMM_JOURNAL : Define Activity Journals) I am not getting my own transaction type under Transaction Type option (I have copied my own transaction type from the standard u201CBus Act:With Prodsu201D activity). I only get the standard activity type (0020 :Bus Act.:With Prods) in my drop down box. (attached is the screen shot)
Any ideas
I am using SAP CRM 5.0.

Hi,
first your transaction type has to be active.
Next, you need to assign item categories ACT0, ACT1 and ACT in SPRO, in order to use activity journals.
All three.
Regards

Personalization in BEx: transport activation to production ?

Similar Messages

Maybe you are looking for