Delete imported requests by job

Hi there,
i am looking for way to delete imported requests from import queue by a job.
Thanks in advance,
Jens

you can schedule job as OS level
tp cleanbuffer <SID> pf=<TRANSDIR>/bin/<TPPROFILE>
this will only clear the successfully imported transports from buffer.
cheers,
-Sunil

Similar Messages

Delete import requests

Hello guys,
I need to make some space in my transport directory ( /usr/sap/trans ) because it is running out of space. Inside this directory there are other directories like cofiles, data, buffer, logs, etc, where I have big files.
What procedure should I follow, to make a good clear of this directories, without affecting my transport system? It would be great to maintain the queue log, just delete the data or big files.
Thanks,
Javier.

Hello,
Proceed as under.
This is an extract of sap help file http://help.sap.com/erp2005_ehp_03/helpdata/EN/3d/ad5b674ebc11d182bf0000e829fbfe/frameset.htm
1. To generate a list of all deletable files in these directories, enter the command tp check all. Files are considered deletable if the accompanying request is not marked for import into an SAP System. The list that is generated is stored as the check.log log file in the tmp subdirectory and can be read.
 2. If you want to test the command tp clearold all, enter the command tp testold all. tp testold all simulates the actions performed by tp clearold all and writes the results to the file testold.log. This file is in the subdirectory tmp. The log file contains details of the actions of tp clearold all when cleaning up the transport directory.
 3. To delete files from the subdirectories cofiles, log, and olddata, and to move files from the subdirectory data to the subdirectory olddata, enter the command tp clearold all. (This command works using the list generated in step 1.) The tp clearold all command writes the results to the clearold.log log file. This file is located in the tmp subdirectory.
For more information on the parameters for these commands, see Transport Profile. To get the current values, use the command tp showparams <sapsid>.
You do not need a connection to the database to execute the commands that are mentioned above. The function is independent of the installed SAP release.
Hope this helps.
Pl award suitably.
Regards

How to retrieve the deleted Transport request (Cust)

Hi,
I have deleted the Customizing Transport Request, by mistake. Now, I am trying to get the TR back.
Could you please let me know if there is any way that I can recover my Transport Request.
Thanks for the helpful answers.
PS: I have checked the existing threads for the same. However, I don't see any solution.
Thanks,
Sandeep

Hi Sandeep,
It;s good if you can involve BASIS consultant or you can check below discription;
If you have deleted from SAP level. Then you need to check at the OS level in /usr/sap/trans/log directory else you can check for the SLOG and ALOG folder also.
If total request has been deleted then you can also do the transport manually at OS level.
or
If you have simply deleted the the requests from import queue through "Extras-> Delete imported requests" in transaction STMS_IMPORT and have not deleted the logs at OS level, then you can check in "Goto-> Import History" in the same transaction to view the requests.
Just double click on the request you want and you enter the "Display Object List" screen for the particular request.
Here you can click on the secong "Spectacles" icon to display the transport steps of the request in each of your SAP system.
Just double click on a step, e.g. 'Import', 'Check Version','Export' etc. to display the log for that particular step.
You can also view the logs from operating system in the directory <TRANSDIR>/log. The logs are named in the format:
<Source SID><Step ID><Request no>.<Target SID>, where step ID is a single alphabet denoting a particular transport action.
Or you can check below link also;
How to recover the deleted Request / task...
Regards,
Kamfrk.

Tp import all - import all with NO deletion of imported requests possible?

Hi,
Story:
We use a Solution Manager to import all transport requests from Testsystem to Integration(Quality)system.
At this transport Solution Manager do this with 'tp import all'. The tp command clean all imported requests out of the import queue.
The problem is:
We do not want that the tp command delete our transported requests out of the import queue.
Is there any possibility to configure this 'transport thing' or 'say' to the tp command not to delete the transported requests?
thx for your help. points will be awared.
bye Mike

I get this from the custo documentation:
Configure Transport Strategy
Use
In this IMG activity, you:
Deactivate the quality assurance (QA) approval procedure
Activate the "Single Transports" strategy
In the transport tracks where the software distribution is controlled by Change Request Management, you must deactivate the QA approval procedure in the TMS, since this procedure is incompatible with the approval procedure in Change Request Management. Additionally, you have to activate the "Single transports" strategy. This prevents you from accidentally executing "Import All". All transports within the system landscape of Change Request Management must be processed by project imports.
For more information, see the online documentation about the TMS in transaction STMS by choosing Help -> Application Help.
Activities
Proceed as follows:
1. Call transaction STMS.
2. Choose Overview -> Transport Routes.
3. Double-click each system.
4. The Display System Attributes dialog box appears.
5. In the Transport strategy group box, select Single transports (since only Import Single and Import Project All are used).
6. In the Quality assurance group box, deselect Delivery after confirmation.
(The quality assurance mechanism is used implicitly but not within the TMS context.)
7. Choose Continue.
Note
When you activate "Single transports", manually executed single imports cannot be imported again by using "Import Project". If you want to execute these single imports again by using a subsequent "Import Project", you have to set the corresponding transport option. We recommend that you only use the transport functions of Change Request Management.
I guess if you select single, the tp shoulds stay in the Q?
can you check this config?

Import of maintenance cycle with deleted transport requests in queue

We use Solution manager 7.0 with one maintenance cycle per satelite system landscape.
In this maintenance cycle Regular corrections and Urg. corrections are used.
When a transport request (connected to a correction) is re-imported into the quality assurance system.
The transport request triggers a deletion and "add to buffer" of the same request into the import queue of the production system.
The sequence of the transport in the production queue is correct before the "import all" into production is triggered via the tasklist of the maintenance cycle.
During the "import all" of the maintenance cycle into production the re-imported requests are pushed to the end of the importqueue.
The re-imported transports are imported last in the sequence and left in the importqueue.
The deletion of the request in the import queue causes this problem.
Re-importing a request is sometimes unavoidable (E.g. after a client copy to QAS).
All our satelite systems have a 3-tier landscape with a simple transport routes configuration.
We are looking for a solution to problem, this can be either technical or adjusting procedures.
Kind regards
Gert-jan Meijer

Hi Gert-Jan,
We do the same and we don't face this issue. There is thus a solution.
I never had this case, this might be a parameter in your QAS refresh procedure.
1/ If you empty your production import buffer (meaning you import it all to production) before tacking the production copy you will never have this issue.
2/ If you have some transportd left in the import buffer of production , you have this issue ? I guess this is our case
I will try to reformulate the case.
The refresh of QAS is causing the lost of some customizing that were not yet imported in production but was imported in QAS prior to the refresh of QAS.
When you reimport the "overwritten" transports in QAS after the refresh, this transport is removed from the QAS import buffer and going too the import buffer of production.
A/The same transport is now twice in the import buffer of production ? we don't have this in our landscape (I even think this was not possible)
B/Or in between this transport has been imported in production and thus you are right it falls in the import buffer of production again with another sequence.
Thank you to confirm your case A or B ?.

Problem in deleting a request from ODS

Hi,
i am trying to delete a request (not activated) from ODS, when i checked in SM37 for the status of the job it shows as Cancelled, but when i see for the request in ODS, the requested is deleted, could anyone please let me know why job in SM37 is cancelling when the request is actually deleting,
This is not the case with activated request.
please see the worklog of the cancelled job
 Job started
Step 001 started (program RSDELPART1, variant &0000000005236, user ID KUMARV1)
Delete running: ODS object ZCFORO01, from 512,483 to 512,483
Delete is scheduled; Selection conditions were substituted
Request REQU_45IYZ9A2BQFRW0IUY5EB4MZ9W successfully deleted from ODS object ZCFORO01
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled 

Hi Arun,
Yes the system raises an exception and saying that there is an error in ABAP code, could you please let me know what is the error, i have tried this deletion with 3-4 different ODS and to different systems i.e. in Q, P system
Abap code as specified by Exception in ST22 transaction
The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in
"RSSM_PROCESS_REQUDEL_ODSO".
The main program was "RSDELPART1 ".
The termination occurred in line 114 of the source code of the (Include)
program "LRSSM_PROCESSU19"
of the source code of program "LRSSM_PROCESSU19" (when calling the editor
1140).
The program "SAPLRSSM_PROCESS" was started as a background job.
Source code extract
000840 endif.
000850 append l_s_rnr_del to l_t_rnr_del.
000860 endif.
000870 delete l_t_rnr_del where
000880 rnr = ''.
000890 loop at l_t_rnr_del into l_s_rnr_del.
000900 l_idx = sy-tabix.
000910 if l_s_rnr_del-sid is initial.
000920 call function 'RRSI_VAL_SID_SINGLE_CONVERT'
000930 exporting
000940 i_iobjnm = '0REQUID'
000950 i_chavl = l_s_rnr_del-rnr
000960 importing
000970 e_sid = l_s_rnr_del-sid.
000980 endif.
000990 if l_s_rnr_del-odssid is initial and
001000 not l_s_rnr_del-odsrnr is initial.
001010 call function 'RRSI_VAL_SID_SINGLE_CONVERT'
001020 exporting
001030 i_iobjnm = '0REQUID'
001040 i_chavl = l_s_rnr_del-odsrnr
001050 importing
001060 e_sid = l_s_rnr_del-odssid.
001070 endif.
001080 modify l_t_rnr_del from l_s_rnr_del index l_idx.
001090 if l_min_sid > l_s_rnr_del-odssid.
001100 l_min_sid = l_s_rnr_del-odssid.
001110 endif.
001120 endloop.
001130 if sy-subrc <> 0.
 > message x000.
001150 endif.

How to Export/Import a batch job

Hi there,
I am wondering if there is/are transaction that can export/import a background job(s). Because, one of our production background jobs got deleted somehow and we have same job that sits in QA system, so we want to export that background jobs and import to Production system, since it has around 70+ steps
Thanks
Kumar

I'm not sure
but if these jobs can be put in a request and.. then transport..
U can try..

Delete Overlapping requests question

Hi ,
How would a Delete overlapping requests (DOR)type work in a PC to a Cube that gets a full load every day with selections for rolling 12 months?
Say there is a scenario to load data into an AR line items cube to update open to closed items history and the loads are configured for a 12 month rolling. eg yesterdays full would be for 03/23/09 to 03/23/10
today's 03/24/09 to 03/24/10
Now how can we utilize DOR instead in a PC that would delete the doubling behaviour of data for dates 03/24/09 to 03/23/10?
All thoughts appreciated.
Thanks

Hi,
in The selection criteria of the info package u can have the following code which takes the selection criteria as the first day to last day of the month based on previous days date(SY-DATUM - 1.)
data: l_idx like sy-tabix,
        dDATE1 LIKE SY-DATUM,
        dDATE LIKE SY-DATUM,
        L_LOW LIKE RSSDLRANGE-LOW,
        L_HIGH LIKE RSSDLRANGE-HIGH.
read table l_t_range with key
       fieldname = 'END_SHIFTDATE'.
l_idx = sy-tabix.
dDATE1 = SY-DATUM - 1.
CALL FUNCTION 'ZFNC_FIRSTDAY_MONTH'
    EXPORTING
      DDATE      = dDATE1
    IMPORTING
      DLAST_DATE = dDATE.
L_LOW         = dDATE.
L_T_RANGE-LOW = L_LOW.
L_T_RANGE-SIGN   = 'I'.
L_T_RANGE-OPTION = 'BT'.
CLEAR dDATE.
CALL FUNCTION 'ZFNC_LASTDAY_MONTH'
    EXPORTING
      DDATE      = dDATE1
    IMPORTING
      DLAST_DATE = dDATE.
L_HIGH         = dDATE.
L_T_RANGE-HIGH = L_HIGH.
modify l_t_range index l_idx.
and DOR deletes the previous day's request as the selection criteria is same. on first day of the next month it has a request with selection criteria as first to last date of the previous month. and this request is not deleted since on 2nd of the month it has different selection criteria(Start daay and end day of that month)
Hope its clear
Thanks,
Sandeep

How to delete the request in Direct Update DSO

Dear Gurus,
I have a situation where I have an invalid characteristic loaded into the Direct update DSO. This is related to Spend Performance Management. This DSO is loaded through a data source with the option Without Archive. So, I cant see any request in this DSO. This DSO will then supply data to another DSO which is standard DSO.
The data Activation job in the standard DSO is failing.
My question is I have to delete the request from the Direct Update DSO and then load it to Standard DSO. I have already repaired the data in PSA.
Your Kind help is greatly appreciated.
-Mohan Kumar

You must be using some fill or delete APIs to fill the data in Direct update DSO.You can't create transformation to fill the data in DIrect Update DSO as you do in Standard DSO.You will not see request number under the manage tab for direct update dso for any load.
Whenever you will fill the Direct update DSO next time,previous data gets deleted automatcally. For Direct update DSO there can only be a Full Update.So just load the data using API's and previous data will get deleted automatically
Edited by: shyam agarwal on Mar 2, 2012 7:48 AM

How to delete the Request Number

Hi all,
How to delete the Requset Number in Development Client.Already i transported this Req. Number to Tesing Client.

For what purpose, deleting the request number won't restore your dev system. You can remove the request from the import queues via transaction STMS to insure it will not be accidentally imported.
You can usually only destroy a request in source system if it has not been released and all objects are unlocked, but this is risky in some cases and may cause a loss of information or coherence.
Regards

BW: Error during Delete Overalpping requests from a cube

Hello, I am getting the following error in a process chain for the last few days when trying to do Delete Overlapping requests from a cube. If I do a "repeat" the chain completes successfully.
The error I am getting is:
Error when deleting requests for comparison request REQU_4MNC5NXH00MJI1LRHAFV3I3BH
Deletion of request REQU_4MQ0NT0ISDRZA444OQRDBGC3X from data target ZZCCA_C11 failed
Any suggestions on how to fix this problem?
Thanks.

Hi Sam,
The job might be failing because the request might me compressed. Take the request id from the error message(for instance
REQU_4MQ0NT0ISDRZA444OQRDBGC3X here) and check whether this request is compressed in the target ZZCCA_C11 or not.
If it is compressed then the data target deletion step will fail obviously.
If this is the case then change the setting of the compression step in the PC to compress the requests loaded 15 days back or whichever you feel comfortable.
If this is not the case then please check the job log once why the deletion is failing.
Hope this helps.
Regards,
Vijay.

Problem in deleting the request from ODS......

Hi,
I am not able to delete one INIT request from the ODS. This request was taking long time and eventually it turned to RED. Data was there in PSA but I deleted the request and thought of doing the fresh load .
Problem is that although I have deleted the request from the ODS , it is again coming back to ODS . I have started the fresh load. AS the previous also coming to this ODS its taking long time to load the data.
Can some body let me know how to STOP/DELETE the old request?? I have already turned everything to RED QM status , overall status etc. but still its not getting stoped.
Thanks Jeetu

Hi Jeetu,
Even though u find the job and cancel it or delete it the data load will not stop untill it loads the entire data!
Hope there will be large volume of data !
Until the data load is complete wait and then delete the request and then delete the init and start the fresh load!
I too faced the same issue but i am helpless i could not stop the data load inthe middle!
If you found any solution for this let me also know
Thanks
Ram

Proc Chain - Delete Overlapping Requests fails with aggregates

BW Forum,
Our weekly/daily load process chain loads several full (not delta) transaction infopackages. Those infopackages are intended to replace prior full loads and are then rolled up into aggregates on the cubes.
The problem is the process chains fail to delete the overlapping requests. I manually have to remove the aggregates, remove the infopackages, then rebuild the aggregates. It seems that the delete overlapping request fails due to the aggregates or a missing index on the aggregates, but I'm not certain. The lengthy job log contains many references to the aggregate prior to it failing with the below messages.
11/06/2004 13:47:53 SQL-END: 11/06/2004 13:47:53 00:00:00                                                 DBMAN        99
11/06/2004 13:47:53     SQL-ERROR: 1,418 ORA-01418: specified index does not exist                        DBMAN        99
11/06/2004 13:47:59 ABAP/4 processor: RAISE_EXCEPTION                                                       00        671
11/06/2004 13:47:59 Job cancelled                                                                           00        518
The raise_exception is a short dump with Exception condition "OBJECT_NOT_FOUND" raised.
The termination occurred in the ABAP program "SAPLRRBA " in
"RRBA_NUMBER_GET_BW".
The main program was "RSPROCESS ".
I've looked for OSS notes. I've tried to find a process to delete aggregates prior to loading/deletion of overlapping requests. In the end, I've had to manually intervene each time we execute the process chain, so I've got to resolve the issue.
Do others have this problem? Are the aggregates supposed to be deleted prior to loading full packages which will require deletion of overlapping requests? I presume not since there doesn't seem to be a process for this. Am I missing something?
We're using BW 3.3 SP 15 on Oracle 9.2.0.3.
Thanks for your time and consideration!
Doug Maltby

Are the aggregates compressed after the rollup? If you compress the aggregate completely, the Request you are trying to delete is no longer identifiable once it is in the compressed E fact table (since it throws away the Request ID).
So you need to change the aggregate so that it the most recent Requests remain in the uncompressed the F fact table. Then the Request deletion should work.
I thought what was supposed to happen if the aggregate was fully compressed and then you wanted to delete a Request, the system would recognize that the Request was unavailable due to compression and that it would automatically refill the aggregate - but I'm not sure where I read that. Maybe it was a Note, maybe that doesn't happen in a Process Chain, just not sure.
The better solution when you regularly backout a Request is just not the fully compress the aggregate, letting it follow the compression of the base cube, which I'm assuming you have set to compress Requests older than XX days.

Delete Overlapping Requests - by Filename via ABAP Routine

Hi SDN Community
Do you know if it is possible to set the delete overlapping request parameters to recoginse the file name, and remove it via the derivation of the file name via an ABAP Routine.
I am using an ABAP routine to derive the flat flat file upon loading, but do not know the syntax, or if it is possible to set this equivalent code into the delete overlapping request Routine area
(The code basically derives the first day of the calendar week, for previous weeks in the Do n times Loop
Thank you.
Simon
DATA: ld_CWEEK         TYPE scal-week,
      ld_DATE          TYPE SY-DATUM,
      ld_DATE1         TYPE SY-DATUM,
      lc_DIRECTORY(30) TYPE c,
      ln_YYYY(4)       TYPE n,
      ln_WW(2)         TYPE n.
*Derive week from sy-datum
ld_date = SY-DATUM.
Determine the calendar week from the entered calendar date
CALL FUNCTION 'DATE_GET_WEEK'
    EXPORTING
      date           = ld_date
    IMPORTING
      week          = ld_cweek
    EXCEPTIONS
      date_invalid = 1
      OTHERS        = 2.
Get the First day of the week
        CALL FUNCTION 'WEEK_GET_FIRST_DAY'
          EXPORTING
            week         = ld_CWEEK
          IMPORTING
            date         = ld_DATE1
          EXCEPTIONS
            week_invalid = 1
            OTHERS       = 2.
Need to find the previous calendar week and reconvert to the first
day in order to accomodate weeks less than 7 days
Get the last day of the current calendar week - 2
    DO 2 TIMES.
        ld_DATE1 = ld_DATE1 - 1.
Determine the calendar week from the last day of the previous week
        CALL FUNCTION 'DATE_GET_WEEK'
          EXPORTING
            date         = ld_DATE1
          IMPORTING
            week         = ld_CWEEK
          EXCEPTIONS
            date_invalid = 1
            OTHERS       = 2.
Get the First day of the week
          CALL FUNCTION 'WEEK_GET_FIRST_DAY'
            EXPORTING
              week         = ld_CWEEK
            IMPORTING
              date         = ld_DATE1
            EXCEPTIONS
              week_invalid = 1
              OTHERS       = 2.
    ENDDO.
*ln_YYYY = ld_CWEEK(4).
ln_YYYY = ld_DATE1(4).
ln_WW = ld_CWEEK+4(2).
*DIRECTORY represnts path where file is stored .
lc_DIRECTORY = '/interfaces/EDW/data/CSM/'.
CONCATENATE lc_DIRECTORY
ld_date '_WEEK' ln_WW '_c1_pri_' ln_YYYY '.csv' into p_filename.
'MIC_NT_' ld_date1 '_' ln_YYYY '.csv' into p_filename.

Thank you for your response Debanshu
However, i could not find this process type in the process chain area.
Is this where you meant, can you please give me more detailed steps including long syntax of names of process types
We are on BW 3.50
i assumed the filename had to be constructed via abap according to some of the sdn replies i've searched through.
Thank you.
Simon

Delete overlapping requests runs for 5+ hours ...This is too long

We are on BW 3.5 and have a process chain that loads 3 years of data from a cube on the APO Server and AOP data from the BW server into a cube on the BW server. Each load is in its own infopackage. This loads happens every week. We want to delete the loads that occurred the week before using the delete overlapping requests. It is set up as follows:
1.Drop index of Cube
2.Load Current Year data into Cube via Infopackage #1. Loads approximately 32 million records. Selections on calweek: 200701 200752. Infosource: InfoSource for APO-DP Cube from APO(ZAPODP_I11). Datasource: APO-DP Backup Cube(8ZAPODPC73). Source System: APP Client 200(APPCLNT200). The Data targets tab is set up as follows: Automatic Loading of similar/identical requests from the cube wherein Delete Existing Requests Conditions: Infosources are the same. Selections are overlapping.
3.Load Current Year + 1 data into Cube via Infopackage #2. Loads approximately 32 million recordsSelections on calweek: 200801 200852. Rest is same as above #2.
4.Load Current Year +2 data into Cube via Infopackage #3. Loads approximately 32 million recordsSelections on calweek: 200901 200952. . Rest is same as above #2.
5.Load AOP data into Cube via Infopackage #4. Loads approximately 135,000 records. Infosource: AOP Plan(8ZAOPC01). Datasource: AOP Plan(8ZAOPC01). Source System: BW Production(BWPCLNT100). The Data targets tab is set up as follows: Automatic Loading of similar/identical requests from the cube wherein Delete Existing Requests Conditions: Infosources are the same. Selections are overlapping
6.Create index on cube
7.Delete overlapping requests from cube. The process chain step is set up to Use Delete Selections for Infocubes from the Infopackages
The issue is that step #7 runs for more than 5 hours. That is way too long. When we manually delete the requests, it takes 5 minutes. How can I fine tune this processing? Thanks in advance!


What is your dbms? Does it support partitioning? If it does then deleting requests merely drops the corresponding partitions, which should be very fast.
If it does not support partitioning then you're running SQL delete statements to delete the data, which could take a long time if you're deleting tens of million of records. BTW how long does it take to load the same data?
P.S. Just saw your last point about manually deleting the requests taking only 5 minutes. Did you delete one request at a time or multiple request at once? The previous poster wanted to know whether you had background processes to run the deletion job. i.e. Did the deletion really took 5 hours, or did it wait a few hours to start the job?
Message was edited by:
Rick Chau

Delete imported requests by job

Similar Messages

Maybe you are looking for