Deletion of requests by setting it to red

Hello,
There are certain confusions in my mind.
1. Why we make request to red while deleting the request?
2. Consider I am extracting data from R/3 system. Consider DSO A and B. I have extracted data to B. But if there are some erraneous record.
a) What happens when I changed the status frm green to red in DSO B for delta update?
b) What happens when I changed the status frm green to red in DSO B for full update?
c) What happens when I changed the status frm green to red in DSO A for delta update?
d) What happens when I changed the status frm green to red in DSO A for full update?
e) What happens when I changed the status frm green to red in Infopackage for delta update?
f) What happens when I changed the status frm green to red in InfoPackage for full update?
Please explain in detail.
Thanks,
Sonu

Hi Sonu,
1. Why we make request to red while deleting the request?
This means system considers previous load was not completed successfully.
2. Consider I am extracting data from R/3 system. Consider DSO A and B. I have extracted data to B. But if there are some erraneous record.
a) What happens when I changed the status frm green to red in DSO B for delta update?
If changed the status to green, the previous delta was not completed, you have delete the data mart status of the request in DSO A.
b) What happens when I changed the status frm green to red in DSO B for full update?
This is also same thing, the previous load was not completed, you can recall the load.
c) What happens when I changed the status frm green to red in DSO A for delta update?
once you make the request to red and delete the request from DSO A, in the source system last delta will be reset in RSA7.
d) What happens when I changed the status frm green to red in DSO A for full update?
Source system considers the previous load was not complete, we can recall the load.
e) What happens when I changed the status frm green to red in Infopackage for delta update?
We do not have any option to change the status from green to red at infopackage level, we can do it at monitor screen.
f) What happens when I changed the status frm green to red in InfoPackage for full update?
answer is same as question e.
Hope this helps.
Veerendra

Similar Messages

Job in Source system terminated - Request is set to red

Hi
I ran a process chain on the weekend which loaded several info packages into a cube. They all ran successfully except for one.
The error message said "Job in source system terminated - Request is set to red".
I've looked on Monitor and no records were extracted.
How can I find out more information as to why this failed ?
Sandra
thanks in advance

Hi sandra,
Suppose if the job in the source system is terminated then no extraction is possible.In order to see the job in the source system->in the process monitor tab->go to environment menu-->job overview>in the source system.so by following the above steps u can see the job in active r cancelled like that.by clicking on the job log u can see all the steps involved in that job.based on that u can take action.
what my suggestion to this issue is force the qmstatus to red and delete that incorrect request and perform again repeat.it will goes through successfully unless it is not a functional error.
assign points if it is useful...
regards,
sri

An infopackage does not delete privious requests though its set to

Hi experts.
An infopackage is set to delete repeating requests, but it does not work when it in a process chain. If i run infopackage itself it does, but in chain it does not delete requsts. Why?
Regards Tigr_Z

Hi,
I think that If you want to use this option while loading the data through process chains, you would need to Add a Process Variant u201CDelete Overlapping Request From InfoCubeu201D to the process chain, position of this variant will be after the data load (Execute InfoPackage). For more detailed procedure refer to this document ::
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0431c48-5ba4-2c10-eab6-fc91a5fc2719?QuickLink=index&overridelayout=true
Regards,
APK

How to delete a request with 1millions records in InfoCube

Hi All,
Our extraction from ODS to InfoCube lead to an error (time-out). The total data transfer is more than 1million records. We tried to delete the request but not to avail. Its still there.
Is there other safer way to remove this request, so that we can reconstruct back the data. No errors in data.
Any helps will be rewarded with points.
Thank you.
Regards,
Azlan.

Hi All,
Thanks for the reply. Points rewarded for everyone. The scenario was; there was a time-out during the loading from ODS to InfoCube and the job was terminated. Short dump also was generated. Time-out was set to 7 hrs. We will further investigate what was the cause of the error. So the immediate resolution was;
1) Delete the error RequestID (mark with red icon)
2) Wait until finish
3) Refresh, the request still there. Select and delete again
4) Wait again. Refresh and now its gone.
5) Go back to ODS, reload back the appropriate request to InfoCube
6) Second time round, everything OK.
Hope this will help others.
Thanks everyone.

How to delete the requests in DTP?

hi all,
here i am unable to delete the requests in DTP...
when i am going to delete the request in DTP it simply showing the error:
*cannot lock request DTPR_488BDVJVHQPUUTT3R383DJ55Q OF TABLE 0MATERIAL for deletion*
could you plz help me on this.....

Hi Kiran,
Please go through this thread. Here the same problem has been discussed it detail.
/message/4419400#4419400 [original link is broken]
Following are the steps mentioned in this thread
1. RSA1 -->Info provider >0Material>Right Click-->Display
2. One screen will come , Select the monitor icon to view that (not the one when you go with Manage of 0Material_attr).
3. In the monitor screen you will see Refresh icon , Refresh that
screen , Now the status will change , after 2 -3 refreshes you
will see the request turning to red.
4. Now go back to the manage tab of the 0Material attribute , You
can delete now.
Regards,
Praveen

Unable to delete bad request in ODS DATA TARGET

Hi Experts,
I have got an abend in load and need to rerun from POF manually .So i need to delete bad request in ODS .But I am unable to delete bad request in ODS.
Please tell me how to delete request in red.

Hi,
Try to do the following:-
1. Note that bad request number
2. Go to SE16
3. Open table RSODSACTREQ.: Filter the contents by that request number . There will be one entry for that request . Delete that entry
4. Open table RSICCONT. There will be one entry for that request . Delete that entry
5. Open Table RSMONICDP. Filter the contents by that request number . There will be 3-4 entries for that request depending on number of data packages in that request .Delete all those entries
Once these entries are deleted , the bad request will be automatically deleted from the ODS.
Regards,
Satya

Unable to Delete the request in ODS

HI Friends,
      I am facing the problem with deleting request in ODS.
          I deleted the request in cube (PPV Analysis cube). But I unable to delete the request in ODS.
    it is showing the message request is already activated;no further QM action possible.
       My system is upgraded by BI 7.0 one week before only. Please give me solution .
I am waiting for your reply.
Thanks & Regards,
Guna.

Hi,
Are there other activated requests on top of this requests?
In that case it wont let you delete this request unless those requests are also deleted.
Try to change the status to red and delete.
Else try this.
Delete requests manually from the ODS tables.
1. tcode se16.
2. delete the request in these tables : RSICCONT (delete activated requests OR
Make the selective deletion of the contents of that request), RSMONICDP, RSODSACTREQ (give the name of the ODS and the
request ID and delete all the entries pertaining to this selection in that table.), RSODSACTUPDTYPE.
The request will be removed from your ODS.
Note 947481 - P32:ODS: Deleting partially active non-condensed requests
Hope this helps.
Thanks,
JituK

Delta Update in data Target Must be Deactivated Before deleting the request

Hi Experts,
I got an error while deleting a request from an ODS target. In breaf Let me explain..
Today one data load got failed. The data source 0CRM_SALES_CONT_I ( CRM Sales Contract : Item ) is updating data to 4 ( Four ) ODS targets.
So I forcefully made the request red to delete the request from the targets. But I unfortunately deleted another request without making it RED, I reconstructed it. Everything is looking fine.
   But the thing is , when I tried to Delete the ERROR request from the other two related Data Targets ( 0CRM_CN2P and   0CRM_CNT1) , I fount these warnings..
                --> Request 140522 already retrieved by Data Target BWPCLNT600
                --> Delta update in Data Target BWPCLNT600 must be DEACT. before deleting the request.
                --> Do you want to DEACTIVATE the Delta Update in the Data Target BWPCLNT600   ?
   I clicked on YES.
I am having doubt, will it make any problem in future ? Or How Can I Resolve this problem   ?
Thanks,
Utpal.

Hi shanthi bhaskar ,
Thank you. But the client no which I have mentioned is not our. That is different, I have given for the example. Bur the DS and ODS name are as it is.
   and Shanthi, Won't be any problem as I got the warning as mentioned above.. ?
Thanks,
Utpal

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 a request from Dso

Hi Experts,
I have loaded the request into DSO, after activation, i have changed the QM status to red and try to delete it from the manage screen. But it is not getting deleted from DSO.
I have used following tables :
RSREQDONE
RSICCONNT
RSODSACTREQ
For deletion purpose, but i'm not provided with authorization ..
And also i have used FM to delete the request from DSO , but it also failed ..
Can you please help me out in this regard..
Thanks
PT

Hi,
Please check if your DSO is locked by any other process. You can check the lock status from SM12. If your DSO is locked by some other process, you will have to wait till that process finishes or kill the process if it is not required so that your DSO will be unlocked. Once your DSO is unlocked you can retry activation. If this doesn't work, please check if you have the authorization to delete data. after trying to delete the DSO you can run the transaction SU53 to see if there is any authorization failure.
Hope this helps you.
Thanks,
Nithin Reddy.

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 in Cube

Dear all,
I need delete the requests uploaded in the previous day when transferring new request into Cube,and the system is BW 7.0,but I use 3.5 data source and infoSource.
The issue is that when I

Tianli,
You can delete the overlapping request in the infocube.
In the infopackage -
> Data Targets -
> Automatic loading of similar/identical requests
You can set the parameter for deleting the overlapping request here.
If you are using process chains, there is a process type available
Load process and post processing-----> Delete overlapping request from infocube.
Can you post your question again as I see it is incomplete..
Sasi

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 from InfoCube" in a Process Chain

Dear all,
I encountered a problem when I building the process chain in BW 3.0.
In a process chain, I schedule daily an InfoPackage to load data to an InfoCube and then delete the previously loaded data by the same InfoPacckage from the InfoCube.
For example, I have 2 InfoPacakge, A and B, and schedule to load data to InfoCube C. In the process chain, I scheduled daily the following tasks in sequence:
- Delete index in InfoCube C
- Load data through InfoPackage A to InfoCube C
- Delete duplicated request previously loaded through InfoPackage A in InfoCube C
- Load data through InfoPackage B to InfoCube C
- Delete duplicated request previously loaded through InfoPackage B in InfoCube C
- Create index in InfoCube C
However, when I activate the process chain, a warning message is prompted: No type "Delete Overlapping Requests from InfoCube" process allowed infront of process "Execute InfoPackage" variable ZPAK_4GMFI
Would anyone tell me why such warning message is prompted?
Many thanks!
Best regards,
Marcus

Hi all,
Re Ranjan:
I previously config the process chain like that:
(1)   Delete index in InfoCube C
(2)   Load data through InfoPackage A to InfoCube C
(3a) Delete duplicated request previously loaded through InfoPackage A in InfoCube C
(3b) Load data through InfoPackage B to InfoCube C
(4)   Delete duplicated request previously loaded through InfoPackage B in InfoCube C
(5)   Create index in InfoCube C
where (3a) and (3b) is executed simultaneously.
However, (3b) often reports error. I guess it may be due to the parallel run of (3a) and (3b). So that's why I set the process chain to be executed in serial.
Re Jacob:
I found that the process chain can be run even a warning message is prompted when activating the process chain!.
Thanks you all for your kind support!!
Best regards,
Marcus

Deletion of requests by setting it to red

Similar Messages

Maybe you are looking for