Deleting Variable in production system vis Transport request

Hello,
I need to delete a variable in production system via Transport request how can we do this?
Thanks,

Hi,
Open the query in BEx in Development system, delete the variable form the query. The pop-up will arise for a new transport request. Capture the query in new request and then transport the same to Production.
Regards,
Yogesh.

Similar Messages

Locationg source system object transport request number in target system .

Hi,
After the object is pushed from source system to target using SCC1 for cross clients but same systems or STMS for cross-systems, if we want to see the object's source system's transport request number in the target system, how can we see that ?
Regards,
Rajesh.

Hi Rajesh
If my understanding is correct you want to know the source server in the target system( i.e where we have transported).
For cross-system objects, as you know we use STMS to transport them...
In the target system:
1. SE10
2. Click on Transports button.
3. Select the required request and expand the node.
4. You will have the first one which has log only for Export.
The node with only Export log is the source system...
Hope this helps...
Kind Regards
Eswar

Deleting Queries in Production system

Hello,
I transports few queries into production system but I would like to delete those queries
Can i just delete in production or is there any procedure?
These queries are just brand new queries.
Thanks,

What is the difference between "Create Transport Requests for BEx " and "Transport object"
When do we use "Create Transport Requests for BEx "?
When do we use "Transport object"?
Correct answer = points
Thanks,
Edited by: Moderator on Jan 30, 2008 3:41 PM
*Everyone on the forum knows that points will be assigned for correct and useful replies. There is really no need to keep mentioning this on each post you create. Thanks!

Delete all inactive objects in a Transport Request

Hi,
I want to delete all the inactive objects in a transport Request . How can i do this ? I have many inactive objects in a request so i want to delete them first and then transport it . How can i do this . Please help..

Hi,
go to transaction se10 click on display individually enter teh request and click display and then you would get the list of all objects in that request so you can check which one are inactive and delete.
Or you can also go to se80 in the repository browser you can choose inactive objects so it would show all inactive objects for a user from there also you can delete objects.
Regards,
Himanshu

Target System in transport request is blank

Hi
I set the transport system in a scenario DEV, QAS and PRD.
When I create an order request, the field target system is blank.
Where should I set it for me automatically display the system QAS as a system target ?
Thanks,
Enrique

Hi,
just adding my solution for future references..
I had similar problem but when I checked our transport package it was showing wrong transport layer..
Make sure your present transport package transport layer attribute is correct or not by using se21 or se80.
we have entered correct transport layer under our package and all working fine.

No able to open hierarchy variable in production system

Hi,
I've have a strange issue in my BEX analyzer 3.5, i have kept product center hierarchy as one of the selection variable for my query, when i click the "Input help" button on my product hierarchy variable, its not opening the window were we can select values, instead of that it keeps on processing for a very long time until we click cancel button and i also checked for other variables by clicking the "input help" button others working fine, wheni try this same query in my testing system it is working fine, Plz resolve my issue
Thanks
Satish

<div class="jive-quote">Hi,
I've have a strange issue in my BEX analyzer 3.5, i have kept product center hierarchy as one of the selection variable for my query, when i click the "Input help" button on my product hierarchy variable, its not opening the window were we can select values, instead of that it keeps on processing for a very long time until we click cancel button and i also checked for other variables by clicking the "input help" button others working fine, wheni try this same query in my testing system it is working fine,</div>
I am not pretty much sure about this issue, but what i understand is that, when you try to open input help, the system is trying to display all the possible product hierarchy values, which i suppose the system is unable to display, as your hierarchy may have many nodes.
Just give a try, you said your testing system has no issue regarding this, just have a view on hierarchy attribute settings in maintain hierarchy option of product center hierarchy, compare the node level drill down at initial in both the systems. I think in testing system node level drill down may be less, and in ur current system it might be more.
Hope this may help you somewhere towards finding the solution.
Regards
Jeeth
Edited by: Jeeth_P on Feb 18, 2012 9:12 PM

How to delete infoobject by transport request?

Hi experts,
I want to delete infoobject from productive system by transport request without deleting this infoobject from development system.
Is it possible? How can I do this?
Thanks!

Hi Denis,
Take an approval to open the production system. While you delete the infoobject , it will ask for transport request to save under.
Regards,
KANTH

How to Create Transport Request For custom table

Hello All,
I have and requirement to create transport request automatically when and record inserted in to the custom table.
Actually FI whe people create or delete some bank account from DEV client the transport request creates automatically and they transport that request to Quality and Production system to delete or create that account from all the systems. but when they delete the account all the informations related to that bank accounts get deleted from all the standered customize tables . to keep the track of that deleted account I have created one z table which is of type customize table. this table is filled automatically when any account get deleted from DEV system. now I want to pass that record to Quality and Production systems using transport request.
how can i create transport request when record get inserted into my ztable automatically.
Thanks in advance.
Vinod

Hello All,
This is a FAQ and has been answered many times before in the forum.
1. Maintain delivery class 'C' it will start asking for a TR: False. Delivery class has got nothing to do with the TR prompt. It determines how the data is to be transported. A delivery class 'C' will prompt for a customizing request, whereas a delivery 'A' will prompt for a workbench request.
2. For the system to automatically prompt for a TR you have to select the "Standard Recording Routine" in the table maintenance generator. This will prompt you for a TR every time you try to create / modify a record & save it to the DB.
Hope i am clear in my explanation.
If your table is filled automatically through some coding you have to add the entry to the TR programmatically. Check this link for details: [http://wiki.sdn.sap.com/wiki/display/ABAP/TransportingTableEntriesinABAPprogrammatically|http://wiki.sdn.sap.com/wiki/display/ABAP/TransportingTableEntriesinABAPprogrammatically]
BR,
Suhas
Edited by: Suhas Saha on Mar 31, 2010 11:22 AM

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

Modify request in productive system

Hi expert,
Users want to modify requests in productive system. These request are been created in development and transported in production.
And, in fact, I would like to retransport request modified in production to development.
No problemes for authorization but I would like to know, what configuration to do in productive system (order BEx, parameters in rsa1/ transport connection).
I tried to create :
- a transport request for BEx
- object changeability : everithing changeable for query element
But changes are not registered in the BEx transport request.
Thanks in advance for your help.
Daniel

Hi Daniel,
In your systems you have something called a Transport Route. This is a route that it says to a request where it would be transported. I think your productive system may be closed for modifications from transaction SCC1, but you allowed BEx modifications from the object changeability customizing, but this won't collect your modifications in a request, because of SCC1 customizing (and that´s correct). That's how SAP works.
So, if you want to transport from PRD to DEV, you may need to create a new transport route from PRD to DEV, but that's not a good option, and i think basis people wouldn't be neither. Then, you should manually copy BEx modifications from PRD to DEV, and to leave the system consistent, then transport it to PRD in a request. If you want to have always the systems consistent, then you should disable object changeability to BEx objects, and always make modifications in DEV and transport them to PRD.
Hope it helps.
Regards,
Diego Lombardini

Error in collecting transfer Rules in transport request after system copy

Hello,
Recently we had a system copy from Production to Test system.
We are trying to collect all the transfer rules from production in the transport request with the procedure which is given in the below link.
Re: Q: Transfer Rules after system copy
When we are trying to transport such objects, system first prompt for transportable workbench request, after specifying request once, it prompts for it again and after providing transport request number system results with message u201CSpecify a requestu201D.
Please suggest how to overcome this issue.

thats scary that you are copying your transfer rules from production to test system well if you guy sare doing it good luck..
a part from that make sure your prd is open so it allows items to be able to transport an dthere is a conenction between prd to test for transports to go through
if you have already copied all te data source to TEST, replicate them IN BWQ( your test system) then send over tranfer fules .
hope that helps.

How can i delete a transport request?

Hello:
I only speak a little english. I wait that you can understand me.
I have a transport request that is released. I make bad this request and i need delete it. But, when i go to se10 and I try to delete I recive this messagge:
Request/task ____ already releaded (not modificable).
How can I delete this request?
Thank you very much.
Report RDDIT076 is internal and should not be executed by customers.
- Reported by Jason ORiordan
Message was edited by: Suhas Saha

Hi,
It is easilly possible to delete the cofile and the datafile of the released transport request but why would you need to do that ?
It is also possible to delete a transport request in the transport tables but it is a very bad idea and could even be seen as a temptative to hide a forbidden action in the system.
It will be seen by a security audit as this would create a hole in the request order numbering.
You would need to use direct database access to delete a released transport request.
As I told you before, I would NOT do it as it is hasardous et may generate security audit problems.
You can also destroy your transport system.
Transport requests are stored in table E070.
We only modify the e070 table after system copy by database refresh to reset the next transport request number. It is done by inserting a line in the table. We never delete inside this table.
Use at your own risk !
Regards,
Raj.

How to delete a transport request once it is been realised.

Hi Gurus,
I need to delete the object from the existing transport request which is already been released and create a new transport request to transport. Is this options possible.
With Regards,
Shakthi.

- You cannot delete a released transport request, but you (or Basis team) can remove it from the import queue in the following systems (starting with quality) (STMS)
- Then you could also via transport tools add the objects of the released request in a new request, there remove the (no longer wanted) object of the new request and release/transport this new request.. (SE03 - Look for "Merge Object Lists")
Ref : [Working with the Transport Organizer|http://help.sap.com/saphelp_nw04/helpdata/EN/57/38e14e4eb711d182bf0000e829fbfe/frameset.htm]
Regards,
Raymond

How to delete the entries from the transport request

i need to delete the entries programatically from the transport request for all the entries which is exists in the package for the tables e070 and e071.

Hi,
I think you need to have authorization for that thru auth group SA.
One more thing is where ever its created like source client only you can do if u have authorization.
Regds
Sivaparvathi
Please reward points if helpful...

PERNR deletion in Production System

Is it possible to delete PERNR in production system after Posting is done and bank transfers are also made.

Dear Samrudhi,
Before trying to delete the personnel number please ensure you have completed the following steps.
1. Identify the posting run number in which the payroll result for this employee is posted to accounting.
2 .Reverse this posting run from PCP0 transaction.
3. Delete the payroll result using the transaction PU01.
4. Clear the fields in infotype 0003 using PU03 transaction.
5. Use PU00 to delete the personnel number, if any time evaluation results are there for this employee choose B2 cluster first in PU00 transaction then deleting the personnel number.
Please let us know if you still have problem with this. Also do not forget to remove this personnel number from the DME file generated and repost the reversed posting run which include other employees result.
Regards
Raviiiiiiiiiiii

Deleting Variable in production system vis Transport request

Similar Messages

Maybe you are looking for