Unable to delete the request through process chain

Hi,
We included program in a info package to delete the request based on snapshot date. its working fine when we ran info package manually but its not working when the infopackage is included in the process chain.
Kindly update us how to work on this.
Thanks & regards
Bharathi

Hi Bharathi,
There are two options in delete request process of chain:
one is to use deletion seletion from Infocube .....infopackage settings
and second one is to set new in chain....
you should try first option...
Thanks
Arun Purohit

Similar Messages

Incorrect data after activating the request through Process chain.

Dear SDN chaps.
Today morning. I encountered a strange issue in DSO..
I have DSO which is updating from the AL11(application server) flat file.
While i am loading it to PSA there were no issues and after loading it to the DSO there is no issue and its passing through the routine and the data is populating properly in NEW data Table .But after successful activation of the request through process i am getting the wrong records in active data table.
Then i deleted the request and reran it manually i mean triggered the DTP and ran the manual activation surprisingly accurate records are coming through manual process..
I am just wondering why it is not working through process chain and why it is showing incorrect records through process chain execution and how it is showing accurate records through manual uploading process..'
Could some one please help to come out from this..By the way mine is SAP BI 7 SP20 &SP05 for BW 7.01
Thanks
K M R

Hi Pra
Thanks for your response..
We are doing PSA deletion and then we are uploading the data to PSA as well as DSO.
Now the issue is not in the part of loading we are facing the issue in Actiation of request if i am executing the activation through process chain it is sucess but the values are incorrect. If i am doing the manual activation it sucess with correct data.
Even i tried with a new chain but still i am facing the issue.
Surprise thing is in new data table the data is perfect in both the ways like manual upate and Process chain update only during activation i am getting incorrect record in the active data table..
Appreciate your help on this....
Thanks
K M R
Edited by: K M R on Jul 9, 2010 11:09 AM

Unable to delete PSA data through process chain.

Hi Everyone,
I have got a problem in PSA deletion. We have got few PSA and change log deletion jobs which run at daily or fortnight basis. We planned to add few PSA tables to each daily and fortnight jobs depending on requirement.
We added in development and could see jobs deleting PSAs properly. Now on transporting to testing, we could see that PSA tables are not being deleted and there is no change in data. We have checked the PSA table names properly, in table RSTSODS and confirmed PSA is given properly only.
Anyone faced this problem or have idea about this issue, please let us know and suggest us.
Thanks and regards,
Shashidhar.

Hi Shashidhar
Just check for the PSA requests as below:
Go to PSA in RSA1/ RSA1OLD -
> Select the PSA -
> Settings -> Display selection for PSA tree -> give start date and end date or any other selecetions as per your requirement-> it will show you all the details.
Hope this helps.
Cheers
Chanda

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

Master Data -- unable to delete the request

I loaded master data for 0EMPLOYEE info object, all the records Added but the request is in Read,
I am trying to QM status Green Manually it is giving the message QM action not allowed for DTP requests in master data and Text Tables .
I am unable to delete the request also, when I am trying to delete it is saying
Error:
Data inconsistency; Partition /BIC/B0000959000 not deleted
Message no. RSAR026
Diagnosis
In table RSTSODSPART you selected all the requests of a partition to be deleted logically. Some entries partno = 0 still exist in the partition. Therefore the partition is not deleted.
System Response
The system outputs an error when deleting the partition.
Procedure&
Check the table for data consistency.
Error:
Termination in problem report 'RSS2_DTP_RNR_SUBSEQ_PROC_SET' in row ' 177'
Message no. RSSTATMAN102

Hi,
I have answered to another thread like this one which is still unsolved (I suggested to open the issue in the OSS)
You can try the following OSS note for a start
SAP Note 1048161 P14:Set QM status for yellow requests using funcion module
I've also found a very recent one:
SAP Note 1078527 P16:Request deletion with error RSSTATMAN 102 in row 34
hope this helps...
Olivier.
Message was edited by:
Olivier Cora

Unable to delete the Requests in the data target---Process chain

Hello Gurus!
Can anyone plz help me out knowing this issue...
Let me explain the whole scenario:
Like when monitoring the process chains,one of the process chainhas a sequence of variants like:
load info-package1>ODS1 activation>load infopackage2-->load infopackage3..
due to some problems they scheduing it manually.all the infopackages loads data into one ODS1......suddenly info-package3 failed.
so....when i looked into the datatarget ODS1->manage->requests.
i found that the info-pack1 requests status was RED.
info-pack2 requests status was YELLOW.
info-pack3 requests status was RED.
ALL THE THREE R FULL UPDATES ONLY.
so suddenly one of our cologue deleted the all the three requests by making ino-pack2 requests to red.
when we r loading again the ino-pack1 again its failed.we deleted it onceagain(removing the requests from the ods),when we are trying to load ino-pack2 for some priority ,automatically the info-pack1 requests with red were seemed in the ODS.so how to solve this issue and also how to load these three ino-packs..
i hope that all understand the scenario..plz suggest me how to work on it
Thanks in advance!!!
Dilip

Hi,
Your loads are running on back ground you have to kill this porcess in SM50 or SM51 check which are all jobs are running with your user name and ALEREMOTE if jobs are running with ALEREMOTE you can check wether it is your load or some body else in SM37 so kill your jobs in SM50 or in SM51 and make request into RED of your 3 loads, delete the requests from ODS and repeat the loads it will go with out any issues, as i under stood your question when your colegue deleted the request without killing the process he simply made it to red and delete its wrong he has to kill the process and then make it to red.
Regards
Sankar

Unable to delete the request from ODS

Hi All,
I have loaded a request to ODS from flat file and the load got success, the request is activated and is available for reporting. Now the problem is i want to delete the request, but the request is not deleting.
I tried to delete the request by going in to the cube manage and changed the QM status and the technical status to red and delete, but it is not deleted.
Thanks in advance for your reply

Hi Prem,
If the ods has datamart status & has been used to load data to a cube, then u cant delete the ods request. In this case, first, change the QM status of the request in the cube to red (delete) & then it wud be possible to go with the deletion of ods request.
Also check this thread as well
Request unable to delete from ODS.
Regards,
R.Ravi

Unable to delete the request id in ODS....indicating partially activated

Dear All,
When I tried deleting a request from ODS, am unable to turn the QM status to red, itz indicating that the request is partially activated. When I tried deleting the request without changing the status, the delete icon is popped up, but eventually goes back to the previous status and hence does not get deleted.
Due to the above, the subsequent requests coming into the ODS are not getting activated at all...
I tried running the function module RSBM_GUI_CHANGE_USTATE, to delete the request, but to no success. Similarly, when I tried locating the requests in the four tables RSICCONT, RSMONICDP, RSODSACTUPDTYPE and RSODSACTREQ, could not found the request id to be deleted in any of these 4 tables.
Please suggest some solution as it is of high importance...
Thanks and Regards,
Edited by: sachitp on Feb 27, 2011 12:25 PM

Hi,
You can try the below options,
1. Remove the request data from the active table using the function
to delete data selectively.
You must enter selection criterion to select the data of the
aborted request.
2. Use Transaction SE37 to execute the 'RSAR_ODS_API_DEL' function
module as follows:
I_REQUEST <Name of the activation request>
I_DATE <current date>
3. Use Transaction SE16 to delete all entries for this request and
for this ODS object from the RSICCONT, RSMONICDP, RSODSACTUPDTYPE
and RSODSACTREQ tables.
Thanks,
Vinod

Delete Overlapping Request in Process Chain

Hi,
Im working on Process chain to upload data from four source cubes to one target cube. Process chain has been configured as after the Data Transfer Processs successful execution, system looks for overlapping data requests and deletes them. Chain seems doing the required functionality but the only thing going wrong is when it comes to deletion of overlapping requests, it randomly delete few and leave others. The status of undeleted ones switched to erroneous and this prevents newly generated data requests available for reporting.
Regards,
Shabbar

Hi,
Thanks for your replies. For deletion Im using Same or More Comprehensive option because I just want to delete the corresponding request with the same selection.
There are four requests need to be created with every run and it should delete the corresponding four. But I dont know whats going wrong, why and how it picks up a few out of four for deletion and left the rest with erroneous status.
Hope this would make the problem statement clear, if you require any further information, please let me know.
Regards,
Shabbar

Unable to delete the request Id

When I tried to delete one Request Id, I got the following messages:
Previous request (ID 1924) has status 'red'
Termination in problem report 'RSS2_DTP_RNR_SUBSEQ_PROC_SET' in row '     175'
I just installed SP10, why can I delete this request? And where can I find "Previous rquest (ID 1924)? It's not there.

Can you please check the code in SE37 for this function module ..with the OSS note corrections...
I have pasted the corrections of OSS note
FUNCTION RSS2_DTP_RNR_SUBSEQ_PROC_SET
Delta 001Context Block
function rss2_dtp_rnr_subseq_proc_set.
""Lokale Schnittstelle:
*" IMPORTING
*"     REFERENCE(I_SID) TYPE RSSID
*"     REFERENCE(I_TSTATE) TYPE RSBKTSTATE
*"     REFERENCE(I_S_MSG) TYPE RSPC_S_MSG OPTIONAL
Delete Block
data: l_r_dtp_rnr type ref to cl_rsbk_request.
data: l_tstate    type rsbktstate.
data: l_ustate    type rsbktstate.
data l_r_error    type ref to cx_rs_static_check.
Insert Block
*" EXPORTING
*"     REFERENCE(E_T_MSG) TYPE RS_T_MSG
*" EXCEPTIONS
*"      ERROR
data: l_r_dtp_rnr type ref to cl_rsbk_request.
data: l_tstate    type rsbktstate.
data: l_ustate    type rsbktstate.
data: l_r_error   type ref to cx_rs_static_check.
data: l_s_msg     type rs_s_msg.
data: l_line      type i.
refresh e_t_msg.
do 1 times.
Delta 002Context Block
      call method cl_rsbk_request=>create_from_db
        exporting
          i_requid    = i_sid
        receiving
          r_r_request = l_r_dtp_rnr.
    catch cx_rs_not_found into l_r_error.
Delete Block
      message l_r_error type 'S'.
      message x000.
Insert Block
       message l_r_error type 'S'.
       message x000.
        l_line = 34.
        exit.
Delta 003Context Block
              call method l_r_dtp_rnr->if_rsbk_request~set_ustate_red
                exporting
                  i_no_commit = rs_c_true.
            catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
              message l_r_error type 'X'.
Insert Block
               message l_r_error type 'X'.
                l_line = 69.
                exit.
Delta 004Context Block
              call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                exporting
                  i_tstate    = rsbc_c_tstate-further
                  i_no_commit = rs_c_true
                  i_s_msg     = i_s_msg.
            catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
              message l_r_error type 'X'.
Insert Block
                  message l_r_error type 'X'.
                l_line = 85.
                exit.
Delta 005Context Block
            call method l_r_dtp_rnr->if_rsbk_request~set_tstate
              exporting
                i_tstate    = rsbc_c_tstate-deleting
                i_no_commit = rs_c_true.
          catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
            message l_r_error type 'X'.
Insert Block
                message l_r_error type 'X'.
              l_line = 99.
              exit.
Delta 006Context Block
              call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                exporting
                  i_tstate    = rsbc_c_tstate-further
                  i_no_commit = rs_c_true
                  i_s_msg     = i_s_msg.
            catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
              message l_r_error type 'X'.
Insert Block
                  message l_r_error type 'X'.
                l_line = 130.
                exit.
Delta 007Context Block
              call method l_r_dtp_rnr->if_rsbk_request~set_ustate_red
                exporting
                  i_no_commit = rs_c_true.
            catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
              message l_r_error type 'X'.
Insert Block
                  message l_r_error type 'X'.
                l_line = 146.
                exit.
Delta 008Context Block
              call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                exporting
                  i_tstate    = rsbc_c_tstate-deleting
                  i_no_commit = rs_c_true.
            catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
              message l_r_error type 'X'.
Insert Block
                  message l_r_error type 'X'.
                l_line = 161.
                exit.
Delta 009Context Block
            call method l_r_dtp_rnr->if_rsbk_request~set_tstate
              exporting
                i_tstate    = rsbc_c_tstate-deleted
                i_no_commit = rs_c_true.
          catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
            message l_r_error type 'X'.
Insert Block
                message l_r_error type 'X'.
              l_line = 175.
              exit.
Delta 010Context Block
            call method l_r_dtp_rnr->if_rsbk_request~set_tstate
              exporting
                i_tstate    = rsbc_c_tstate-further_start
                i_no_commit = rs_c_true.
          catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
            message l_r_error type 'X'.
Insert Block
                message l_r_error type 'X'.
              l_line = 197.
              exit.
Delta 011Context Block
              call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                exporting
                  i_tstate    = rsbc_c_tstate-further_start
                  i_no_commit = rs_c_true.
            catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
             data l_x.
             while l_x is initial.
             endwhile.
              message l_r_error type 'X'.
Insert Block
                  data l_x.
                  while l_x is initial.
                  endwhile.
                  message l_r_error type 'X'.
                l_line = 223.
                exit.
Delta 012Context Block
            call method l_r_dtp_rnr->if_rsbk_request~set_tstate
              exporting
                i_tstate    = rsbc_c_tstate-further
                i_no_commit = rs_c_true
                i_s_msg     = i_s_msg.
          catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
           data l_x1.
           while l_x1 is initial.
           endwhile.
            message l_r_error type 'X'.
Insert Block
                data l_x1.
                while l_x1 is initial.
                endwhile.
                message l_r_error type 'X'.
              l_line = 241.
              exit.
Delta 013Context Block
              call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                exporting
                  i_tstate    = rsbc_c_tstate-further_start
                  i_no_commit = rs_c_true.
            catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
              message l_r_error type 'X'.
Insert Block
                  message l_r_error type 'X'.
                l_line = 264.
                exit.
Delta 014Context Block
            call method l_r_dtp_rnr->if_rsbk_request~set_tstate
              exporting
                i_tstate    = rsbc_c_tstate-further_error
                i_no_commit = rs_c_true
                i_s_msg     = i_s_msg.
          catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
Delete Block
            message l_r_error type 'X'.
Insert Block
                message l_r_error type 'X'.
              l_line = 279.
              exit.
Delta 015Context Block
      endif.
    when others.
      message x000.
endcase.
Delete Block
Insert Block
    exit.
enddo.
if l_r_error is bound.
    call function 'RS_EXCEPTION_TO_MESSAGE'
      exporting
        i_r_exception = l_r_error
      changing
        c_t_msg       = e_t_msg.
    l_s_msg-msgid = 'RSSTATMAN'.
    l_s_msg-msgno = 102.
    l_s_msg-msgty = 'E'.
    l_s_msg-msgv1 = 'RSS2_DTP_RNR_SUBSEQ_PROC_SET'.
    data: l_char(10) type c.
    l_char = l_line.
    l_s_msg-msgv2 = l_char.
    append l_s_msg to e_t_msg.
    data: l_on type sy-batch.
    call function 'RSSM_RFC_IS_GUI_ON'
      importing
        on = l_on.
    if l_on = 'Y'.
      call function 'RSDC_SHOW_MESSAGES_POPUP'
        exporting
          i_t_msg                 = e_t_msg
          i_txt                   = text-012
        I_WITH_S_ON_EMPTY       = RS_C_TRUE
        I_ONE_MSG_DIRECT        = RS_C_TRUE
        I_ONE_MSG_TYPE_S        = RS_C_TRUE
      IMPORTING
        E_S_EXIT_COMMAND        =
    endif.
    raise error.
    exit.
endif.

Unable to see the new transported Process Chain

Hi all,
I just made change to one of existing Process Chain in Dev, and also created a new one. I transported from Dev to Q successfully, but couldn't find it anywhere in RSPC. For the Existing Process Chain, I saw the changes in Q, but the chain's name has not been changed. Do you know why?
Thanks!

If your transport system is not set up to activate the process chain automatically after importing, then your new process chain may have "New:" in the beginning of the description. And since the process chains are organized within each Application Componenet by description, it may not be in the place where you think it should.
You should also check your transport in Dev to insure you collected the new chain.

Delete PSA Through Process Chain

Hi,
I am working in NW04s. I have few questions related to the subject line. Few are for knowledge enhancement and other are task oriented.
Background: InfoPackages are created to load data (master and transaction, both full & delta) for InfoObjects and DOS/Cubes. All the 4 options (PSA and then InfoObject, PSA and infoobject in parallel, only InfoObject and only PSA) are used in production.
Questions:
Q1 (general): Why should we have a process in Process Chain after data load to delete PSA, if we are using PSA and then InfoObject?
Q2 (specific questions): How to include the PSA name in "Delete PSA Request" of a Process Chain when infoPacakge processing is only PSA.
Q3 (specific question): When Data target is not defined in InfoPacakge (but only Data Source and Source System is defiled, and process is "PSA and then InfoObject', then in such case which infoprovider is to be put into "Delete PSA Request" in process chain.
Thank you for reading my questions, and helping me.
Sincerely,
S

Q1 (general): Why should we have a process in Process Chain after data load to delete PSA, if we are using PSA and then InfoObject?
Requests in PSA are deleted periodically so as to prevent getting the PSA table bigger and bigger occupying more DB space.
Q2 (specific questions): How to include the PSA name in "Delete PSA Request" of a Process Chain when infoPacakge processing is only PSA.
You can specify the PSA table name, it need not load further targets as it is deleting requests from PSA itself . Loading PSA is good enough for the Delete Request in PSA process type to work.
Q3 (specific question): When Data target is not defined in InfoPacakge (but only Data Source and Source System is defiled, and process is "PSA and then InfoObject', then in such case which infoprovider is to be put into "Delete PSA Request" in process chain.
You can specify the PSA table name, why do you want to Infoprovider name I guess you cannot even do that for this process type.

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 PSA request

Hello,
I am unable to delete the request in PSA the status of the request is Yellow(Undecided)
But I would like to delete this one.
Thanks,

Hello Ram,
Is it giving any error. If so what is that?
Right Click the PSA and select Delete
or you can use the function module RSATREE_PSA_DELETE_BATCH to clear all the PSA.
Thanks
Chandran

Broadcasting through process chains

How to broadcast reports to indivdual mailboxs in the company through process chains. say current data should be broadcasted into individual email account every time a new sales order or purchase order is created or by the end of the day , it should automatically trigger the mail with the report. can anyone help on this.

Hi,
Here see the blog details.
The goal of information broadcasting is to distribute the right information, in the appropriate format, to the right people, through different channels, at the right time.
With the BEx Broadcaster, you can precalculate queries, query views, Web templates, reports and workbooks and broadcast them by e-mail or to the portal. In addition to the precalculated documents in various formats (HTML, MHTML, ZIP and so on) that contain historical data, you can also generate online links.
Accessing the Broadcaster
The broadcaster can also be accessed via the Portal through the delivered BI Role.
You can determine the Scheduling for Information Broadcaster
Based on a data change event triggered by a process chain.
Based on a pre-defined time point.
Freely definable scheduling.
Steps to Schedule Information Broadcaster based on a data change event triggered by a process chain
Create the Query in the Query Designer.
Execute the report in the BEx Web Analyzer.
Click on u201CSendu201D to create the settings for broadcasting.
The Broadcast Wizard takes you through a series of prompts where you supply the key information required to develop a broadcast. At any time you can leave the Wizard and use the standard settings dialogs which offer more settings.
Then schedule the broadcast. If you start the Broadcaster for a query (or template or workbook) that gets data from an InfoProvider that will be selected in the process chain, you can select the InfoProvider for Scheduling.
Create the process chain and include the event data change, include process type "Trigger Event Data Change (for Broadcaster), itu2019s available under "Load Process and Post -Processing".
The Process Chain is created including the process types: (1) Start (2) Execute InfoPackage (3) Delta Data Transfer Process (4) Activate DSO (5) Trigger Event data Change.
When you create the Variant for the Event Data Change, using checkbox we can indicate when the Broadcast should trigger.
As soon as that InfoProvider is affected by a Process Chain, the Broadcasting is triggered.
After successful activation you can now schedule your chain. Press button u201CScheduleu201D or menu u201CExecution -> scheduleu201D. The chain will be scheduled as background job. You can see it in SM37. You will find a job named u201CBI_PROCESS_TRIGGERu201D. Unfortunately every process chain is scheduled with a job with this name. In the job variant you will find which process chain will be executed. During execution the steps defined in RSPCPROCESSCHAIN will be executed one after each other. The execution of the next event is triggered by events defined in the table. You can watch SM37 for new executed jobs starting with u201CBI_u201D or look at the protocol view of the chain.
You can monitor the Broadcaster from the SOST transaction.
Note:
Depending on authorizations, end-users can schedule their Broadcasting Settings.
Only for those queries which are checked "Execution with Data Change in the Infoprovider" while you schedule, will be triggered by process chain event.
You may wish to refer the Note on Settings for Information Broadcasting- 760775
Hope this help you
Regards,
Rakesh

Unable to delete the request through process chain

Similar Messages

Maybe you are looking for