Bex Non transportable Request

Hi Friends ,
I have created a Dummy request for all my Bex objects which is non transportable, and assigned to a Package . Now when I am collectin all my queries in a new request I dont see this request under or as a sub task of my non transportable request but instead see is as a Separate request all by itslef. Why is this ? How can I see my request where actually the queries are collected under my non transportable request ?
thank you,

Hi,
goto se10 and do a right mouse click on your transportable request. Select the option receive objects (or similar). In the following screen select and/or enter your non transportable request and all objects of that will be added to your transportable request.
regards
Siggi

Similar Messages

BEx Standard Transport Request

Dear Experts,
I have 2 questions for BEx Standard Transport Request.
Could I create more than one BEx Standard Transport Request?
For example, I create a BEx Standard 1 Transport Request for Query A.
I also create a BEx Standard 2 Transport Request for Query B.
Is it possible?
If not, could you kindly tell me the difference between standard BEx transport request & common transport request?
Thanks and best regards
Alex yang

The Bex standard transport collects changes in queries, a standard transport can transport anything.
Once a query has had a package assigned to it and transported, it can't be changed in the dev environment without a Bex transport assigned. In a multiple developer enviroment, people end up transporting incomplete changes from other developers.
A common solution is to make the changes, release the Bex transport without moving it to next system, and recollecting the query in the transport collector and transporting ONLY the query selected.
John Hawk

Transportable and non transportable requests in the SRM EBP cusomizing

Hi friends,
can u please give the list of transportable and non transportable requests for the ebp configuration.
thank
Arun
Edited by: arun kumar on Aug 6, 2008 8:19 AM

wrong forum
Regards
Juan

No request has been set up as the standard transport request for BEx object

Hi gurus,
I have this error in a query . Have someone any ideea what is this?
Thanks,
Ramona

Hi,
Before you create a query you have to assign a global request to Bex application.
To do this goto Transport connection of RSA1, In the tool bar you will see a icon Bex (Create transport request for Bex). Assign a request for it. After doin so, you error will be resolved.
-- Selva

Database tables holding details for a non - released transport request

Dear All,
We are implementing SAP ECC 6.0 u2013 ABAP stack, on IBM iSeries / System i, i5/OS V5R4 -
SAP kernel release 7.00, kernel patch number 173
Could someone please guide me to the database tables holding the details for a non u2013 released transport request.
The problem is the following :
We encountered some data corruption in the database of our development system, so we did a restore from the previous day's backup (RSTLIB command) for the database library : R3DEVDATA, without restoring the /usr/sap/trans directory, then we did an APYJRNCHG command for the journal receiver spanning from the previous day's backup until the corruption time (remote journal on a remote system.)
We are now facing the following conflict :
One of our programmers is now un-capable of updating an ABAP program, which he previously added in a transport request, which he did not release.
( This was done during the day of the data corruption)
When the programmer is trying to update the ABAP program through the ABAP workbench, he receives the error :
'Request lock on non u2013 existent task / request DEVK921426'
No details for the transport request DEVK921426 exist in either of the two directories :
/usr/sap/trans/data , /usr/sap/trans/cofiles
The way I see to solve this conflict (eliminate this lock) is to delete the different entries related to the un-released transport request from the database tables.
Any clues would be highly appreciated.
Thank you in advance for your cooperation.
Best regards.
Reda Khalifa

Dear Volker,
Thank you very much for your interest.
The transport request of interest did not appear in transaction code SE03
Eliminating the record from table TLOCK indeed did solve the problem.
Thank you again.
Best regards.
Reda Khalifa

Regarding transport request for BEx.

Dear All,
Would you like kindly suggest regarding my case ..
Now in our transport system for BEx, we must create 1 transport request number (RSA1 - Transport Connection - BEx). Then this transport no is used by all modification in query designer / BEx.
But..
I've ever found in one system, that Each modification in every BEx/Query Designer has it own transport request number.
My Question is ..
Do you know to make BEx transport system like this ???
I mean, every modification in query designer/BEx has its own transport request no..
Is it because of updating some patch ??
Or is it because we must configure it in some t-code ? If yes, could you explain me how to do it ??
Really need your guidances.
Best regards,
Niel.

What I can suggest you for this. Do you have any request number in RSA1-> Transport Connect-> BEx.
Then every time you try to change a query(already transported )it says it is not assigned to transport request.
IN the transport connection assign to a request as we do for cubes etc then do the changes
For the new query it will be saved under $tmp. so what ever you want to transport assign it to request no as we do for cubes and then transport
Regards
PV

Transport Request for a Bex query ?

HI all ,
i have a requirement that , i have a query which is in producton first, & not available in development . we need to do some changes on it .
for this we have copied from producton to DEV .
when i am trying to changes it is saying that , "Bex transport request is not availbele or not suitable :
or choose an existing request .
Plz suggest me how to rectify this .
regards ,
Srinivas .

Dear Srinivas,
I wanted to repeat the normal rules for how we must use the BEx transport in BW.
This is a special transport that is always used in development. All query changes get written there - you don't choose your transport in the normal fashion. But this gives a problem - we have no control over what is in that transport. Therefore we never release it.
Instead the process is to create a new transport and include your new query in it. You often find that part of the query is in the BEx transport, and you must delete it from that transport.
It doesn't matter whether you delete just your query, or just delete all the contents of the BEx transport - but do not delete the transport itself, and do not release it either.
Deleting everything in the transport is very fast and simple - if you do it this way. In se01, click on the 'tools' icon (fourth icon). then choose Unlock Objects (Expert Tool). Run it twice, first the task, then the request. Then return to se01 and all the objects in the transport are unlocked and can be deleted in one go.
Thanks-RK

Bex transport request 'BWDK900073' is not available or not suitable

Hi,
i have transported a cube with "data flow after" option and collected in a package zbexquality.
this request was transported to productin and i can see the queries in production too.
now when i go to change any of the queries on this cube, it gives me the following error:
==========
Diagnosis
There are the following possible causes:
No request has been set up as the standard transport request for BEx objects.
The (set up) request 'BWDK900073' (for the package 'ZBEXQUALITY' ) has already been released.
The (set up) request 'BWDK900073' (for the package 'ZBEXQUALITY' ) is not of the type 'transportable change request'.
System response
The request BWDK900073 can not be used to record changes to BEx objects (queries or Excel workbooks). The changes made to objects you are editing will not be logged.
Procedure
If you want to record changes to BEx objects, set up an open transportable change request as the transport request for BEx objects. (If the package 'ZBEXQUALITY' is not empty, set up a request for this package).
Inform your system administrator of your actions, or enter a new, targeted transport request in the Administrator Workbench in the transport connection by using the 'BEx' pushbutton (Create Transport Requests for BEx).
Procedure for System Administration
====================
when i try to change any other queries( transported using different request and different package earlier), it gives me teh same message.
what is the reason? what is wrong?
thank u in advance

hi S B,
as mentioned in your previous thread,
each time you released request for query to be transported for 1st time, you will need to create
BEx request with same package as soon as the request released, otherwise you won't be able to save changes
to the query in that request.
rsa1->transport connection->icon truck and bex,
assign with package ZBEXQUALITY.
hope this helps.
ZBEXQUALITY is not a good naming. some sample
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e
Customer Package Description
ZBW BW Package for Custom Objects
ZACTPAY Accounts Payable - Query-only package
ZACTREC Accounts Receivables - Query-only package
ZCONTROLLING Controlling - Query-only package
ZSALES Sales and Distribution Query-only package
ZFIAA Fixed Assets - Query-only package
ZPROJ_SYS Project Systems Query-only package
ZPURCH Purchasing - Query-only package
ZSP_LEDGER Special Ledger - Query-only package

BEx Transport Requests '' ist not available or not suitable

hi, all,
I want to change a query, that has been transported back from Prod.System into TestSystem. Changes in the query aren't possible - the error message is
" BEx Transport Requests '' ist not available or not suitable ".
Now, there is a Standard BEx Transport Request and, in the RSA1 -> Transport Connection I see the query complete with that Transport Request.
What can the reason be? Any Idea?
Thanks a lot in advance.
neven

Ciao, Paolo,
thank you for the quick responce.
I did exactly as described :
The easiest thing to do is the following:
1) collect your query in transport connection
2) check if it is already assigned to a transport
2a)if assigned to a transport check if this is the standard bex transport. If so go to step 3, If not see if you should just tranport that request (or you can just go to step 3...but i wouldn't advise that)
3) unlock the standard bex request
4) now go back to transport connection and put the collected objects in a new request
5) release and transport your new request
It still doesn't help. I can't change the Query. The error-message is stil the same.
best regards
neven

Bex Transport request is not available

Hi guys
I want to change the Bex query from query designer, when i go for change mode it didnu2019t allow me to change and throws error message "Bex transport request " is not available or not suitable" and in second line it gives "choose an existing request.
Can any one tell me how to change the Bex query with a transport request?
Gaurav

Hi,
You get this message if you have captured the query in a transport request and released or transported the request.
You can somply capture the query in a new request again from transport connection and then you will be able to edit the query.
even after capturing the query in the request is not allowing to edit then you need to try the option as explained by our friend above.
Regds,
Shashank

BEx Transport Request is not available or not sitable

Hi,
When i try to install some queries from Business Content in the BW DEV box, the error was :
<b>BEx Transport Request is not available or not sitable</b>
Please let me know what has to be done in order to get out of this error
Thanks & Regards,
Kishore

Hi Ken,
Thanks for responding to my problem.
You are right. I am installing from business content queries that have never been installed before.
so when i am installing the queries from business content the error was :
BEx transport request is not suitable or not available.
How to proceed now ?
Please give reply ASAP....
Thanks & Regards,
Kishore

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

Transport request trying to import itself into non existing client.

Hi,
We are trying to import one transport request ( Source client of transport request 101 ) but it trying to import itself into the client 135. This 135 client has been deleted long time back.
I checked , there are no references in transport configuration to this client.
Error we got during import:-client 135 does not exist. Choose another client.
Can someone pl. let me know what could be the reason.
Best Regards,
Tushar.

Hi Markus,
We did not give target client while importing. We left it blank. But source client of transport request is 001. But in log
600 ( default login client )------> selection for import
135 -
> Selection for Import.
600 is ok but why this 135 is selected for import. That is the problem.
Best Regards,
Tushar.

Transport Request Number is non-numeric

Hi,
We implemented CTS+ on Solution Manager.
The transport request number of the Portal Transports (SAP EP 7.0) started with EPDK900001 and after EPDK900009 became EPDK90000A.
Can someone please guide me how to change this so that the transport request number proceeds in numberic fashion like EPDK900009, EPDK900010, EPDK900011,...
Thanks in advance; I know this might be really simple for lot of you gurus.
Regards,
Pratik

The main reason to lock the request is to avoid any duplications.
You can also unlock the request if you want using SE03 transaction.
Goto SE03 transaction,select unlock objects and execute.give your
request number and execute.it will be unlocked.

How to collect the deleted query in a transport request.

Hi Friends,
I have created a query and transported it to the Quality, the data content is all ok, except that i have not used the Project Naming conventions. Now i have a defect against my name for this. I have to copy the same query with the correct Naming convention and transport it.
My question is after copying the query with correct name i have to delete the old query (if not there would be 2 versions of the same query). How do i collect the deleted image of the query in a transport and send it to quality?.
I tried deleting a test query from Bex Designer, but this does not ask me for a transport. should i use RSZDELETE?. Not sure if it asks for a transport request when i delete the query.
Can someone pls tell me how to go about this?.
Thanks in advance.
BN

Hi BN,
I do agree that deleting directly in Quality and Prod is not good way and not recommeded.
I have not tried and deleted.But if the system is configured in such a way that if it doesnt ask for a request
then i feel you have no option.
If any object is deleted then you must have the deletion image collected into request at the same point when you are deleting.Because later when we go to transport connection we wont find the object itself.
What i think from your point as you said you have done earlier is you must have any open request regrding this query and when this query is deleted , the deletion image is also included in the same request.
So go to se03 and give your deleted query name and check all the requests.
Check in the requests when the deletion image is captured or not. we might be knowing that this is cpatured.
Regards
vamsi
Edited by: vamsi talluri on Nov 9, 2010 9:14 PM

Bex Non transportable Request

Similar Messages

Maybe you are looking for