RSDDS_AGGR_MOD_CLOSE

Hi all,
Can any body please give the information about these two
RSDDS_AGGR_MOD_STATE_GET, RSDDS_AGGR_MOD_CLOSE function modules. How to use this function modules and what will these function modules do.
thanks in advance.
thanks,
reddy

Hi Dinesh,
I appreciate for your help. Rellay i am happy with your answer,you are 100% correct.I need further more information.
LIke function module" RSDDS_AGGR_MOD_STATE_GET "
(confirm the field E_MOD_IN_PROGRESS should have no value, E_CNSID should be 0.
If no values found start "change run ").
If the field E_MOD_IN_PROGRESS has a value,the
SE37-->function module " RSDDS_AGGR_MOD_CLOSE " This deletes the flag for an "active" changerun .
I checked this function module RSDDS_AGGR_MOD_STATE_GET
and the fields had values so I ran the RSDDS_AGGR_MOD_CLOSE function module to set the flag,and i continued changerun later successfully. here my problem is "is there any harm to the aggrigates data", if i run this function module is it going to replace any values in the aggrigates.Could you please give information regarding this.And if you send any documents or links abt this that is very much helpfull to me.I will give full points to your next reply.
Thanks a lot,
Reddy.

Similar Messages

Error in Setting lock for Master Data Load

Hi Team,
I encounter the following error while uploading the Masterdata
"Lock NOT set for: Loading master data attributes
Attributes of characteristic 0BPARTNER are locked by terminated change run 465451241"
I Performed the following steps
1) Checked if any active jobs (change run jobs) running in the system. But no jobs running.
2) RSATTR->infoobject list-> no infoobject found
3)Tried after sometime ,but load continue to fail
Could anyone help to solve the problem
thanks
Bala

Hi Bala,
Check in SM12 if there are any locks exist with the change run number?
First check if there are any Master data loads running related to it?
Check in the Attribute change run screen if there are any change run steps are running?
Once after checking the above if no locks exist and no master data is running then check the below steps
1. Run RSA1 transaction
2. Tools -> Apply Hierarchy/Attibutes Change(or direct transaction RSATTR)... menu option
3. Click at "Monitor and Start terminated Change Runs" button (at the bottom of the screen)
4. Click "Reset Status" button at Run ID 465451241
NOTE: this is not recommended, to unlock the locks better to wait till the locks get relased.
If still the error message persists then we can use a FM in se37 in serious cases which was not recommended by SAP...
Use RSDDS_AGGR_MOD_CLOSE in se37 and execute--->there give ur failed change run no(465451241) beside I_CNSID and execute...
It releases all the locks by that change run....and continue with your further work/jobs...
Regards
KP

Lock NOT set for: Loading master data attributes error

Hi experts,
We were encountering this error before when trying to load master data. When we checked the system we could not find any locks at the time, and activation or kicking off the attribute change run failed again. We finally solved the problem running FM RSDDS_AGGR_MOD_CLOSE which sets the close flag to 'X' in table RSDDAGGRMODSTATE. I have read that it is possible this lock error happens when two change runs happen at the same time.
My question are:
1. is it possible to find out what process exactly "caused" the lock? the table RSDDAGGRMODSTATE does not have a reference to any object or job. I am curious as we are trying to find ways to avoid this in the future...
2. in our case, when we could not find any locks, is running this fm the only work around? is this a best practice?
mark
Message was edited by:
Mark Siongco
Message was edited by:
Mark Siongco

Hello Catherine
I have had this problem in the past (3.0B) --> the reason is that our system was too slow and could not crunch the data fast enough, therefore packets where loacking each other.
The fix: load the data into the PSA only, and then send it in background from the PSA to the info object. By doing this, only a background process will run, therefore locks cannot happen.
Fix#2: by a faster server (by faster, I mean more CPU power)
Now, maybe you have another issue with NW2004s, this was only my 2 cents quick thought
Good luck!
Ioan

Attribute ChangeRun issue

Hi All
I can not able to run Attribute Change run because it is locked with 1 Infoobject and save button got vanished from past few days it is got dump message In the monitor is showing change run was terminated and characterstics to be activated. This is major impact in my project since we can not able to load any data to this Master data object ofcourse we can able to activate data for other Infoobjects using Right click on Infoobject and activate.
Why this is happend I have tried to load data into this after few records got red and showing message like Infoobject is locked.
I can not able to do anything with this Object. I have checked in SM12 we dont have any locks.
Can anyone have the solution please help me.
Thanks
Vani

Hi,
You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
Attribute change run Infoobjects locked
Refer OSS notes 903886
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=903886
1) Some times the infoobjects are not released from the previous change run.
So go to the FM RSDDS_AGGR_MOD_CLOSE and run it it will release all the locks on the infoobjects by the ACR.
Now re run the ACR.
OR
If your last change run was unsuccessful then, Go to table RSDDAGGRMODSTATE. Failed change run might have left a record in this table with field CLOSEDFL = ' ' (false).
Change this field CLOSEDFL to 'X' and the infoobjects will got unlocked.
This should be used only as as last resort and is not advicable to use frequently.
Also there are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over.Most of the times we have problem with the Attribute Change Run(ACR) running because ACR and the Roll Up's for Aggregates cannot run in parallel.
And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and need to deactivate that aggregate.
But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
This may not be the exact issue you are facing.
thanks,
JituK

Attribute change run error in daily job (BI 7.0 SP 23)

Hi All,
We are facing an Attribute Change Run error in one of our daily batch job.we donnot see any locks in SM12.and a dump occurs in ST22.we also donnot have any master data load running at that time .We executed the the FM RSDDS_AGGR_MOD_CLOSE,but the Change run error occurs frequently .How to get the root cause of this issue as we donnot have any master data load running at that time.
regards,
maria

If you are sure that your master data is 0MATERIAL then GOTO-RSA1>Tools in Top>Select Attribute Hiearchy Change Run>Select Info Object List>Select 0MATERIAL>Execute.Then message "Attribute/Hierarchy change run scheduled" will appear in the Tab on your User ID.Once its finished your masterdata is activated.
For Activate Master Data we can do another method like "Right click on the particular Infoobject which need to activate and click "Activate Master Data".
The above steps is for manual activation of master data changes..
If you want to automaize the above steps "Need to add Attribute/Hierarchy Change Run" in the process chain.When execution of Processchain it will activate all the master data in the list one by one and also realign the Aggregates which using the master data objects.

Objects Locked by Failed Process Chain

HI,
I cannot update certain infopackages as they are locked by a failed Process Chain update, however I have checked sm12 and there are no locked items showing, also I have gone into RSA1 --> tools Attrib Change Run and into the InfoObject List and ther are no objects so i cant run the Atrrib change run from their either.
So if there is no locked items in Sm12 well then how do i unlock them?
Do i need to mark the failed Process chain as complete or something?
Thanks.

Is this in the Source Code tab? Sorry i do not see where i should input the Timestamp or where i actually run the RSDDS_AGGR_MOD_CLOSE function module?
This is the code i see when i Run SE37 with RSDDS_AGGR_MOD_CLOSE
FUNCTION RSDDS_AGGR_MOD_CLOSE.
""Lokale Schnittstelle:
*" IMPORTING
*"     REFERENCE(I_CNSID) TYPE RSSID
*" EXCEPTIONS
*"      X_MESSAGE
DATA: l_timestmp type rs_timestmp.
get time stamp field l_timestmp.
UPDATE RSDDAGGRMODSTATE set   closedfl     = rs_c_true
                                TIMESTMP_END = l_timestmp
                          where cnsid = i_cnsid.
IF SY-SUBRC NE 0.
    perform x_message using 'RSDDS_AGGR_MOD_CLOSE-1-'.
ENDIF.
ENDFUNCTION.

Monitor error

Hi BW experts,
when i try to load to master data .attribute of charcterstic 0person are locked by terminated change run. iam getting this error can any one give the solution. i will award the points.
regards
RK

Hi,
Attribute change run Infoobjects locked
Transaction RSATTR will schedule/display attribute change run.
OSS notes 903886 https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=903886
Some times the infoobjects are not released from the previous change run.
So go to the FM RSDDS_AGGR_MOD_CLOSE and run it it will release all the locks on the infoobjects by the ACR.
Now re run the ACR.
OR
If your last change run was unsuccessful then, Go to table RSDDAGGRMODSTATE. Failed change run might have left a record in this table with field CLOSEDFL = ' ' (false).
Change this field CLOSEDFL to 'X' and the infoobjects will got unlocked.
But both of this are only the last resort and not recommended by SAP.
Refer
Re: Urgent:Attribute change run in HOLD state due to ARFC Reason
Cancellation of Attribute change run after Hold ARFC.
thanks,
JituK

Attribute Change run failure

Hi All,
First time when ACR is run, the job terminated and when I checked in Change run Monitor there were some other change run which has got terminated already under some user.
In Job log the error was "Error when deleting the data record /BIC/XZInfoobject"
We also get the message u2018Attributes of characteristic ZXXXX locked by the terminated run XXXXXXXu2019 when we activate master data.
We tried to re-execute the run in the change run monitor even then it got terminated and the error message was the same as above.
In order to release the lock we tried in SM12 but could not any locks and found a Function module RSDDS_AGGR_MOD_CLOSE to finish the last change run and we used the same to release the lock which worked fine.
We then used the program RSDDS_AGGREGATES_MAINTAIN to manually run the ACR giving the Info object name.
The job also finished successfully but still we find records of version u2018Mu2019 under the Infoobject P table. There are 11 records having M version with Insertion flag u2018Iu2019. These are the modified records after the load, which will be inserted upon activation.
Please let me know if there are any solutions to activate the modified records to P table because we are not finding the Infoobject in ACR queue even after manually changing master data or running loads.
Thanks,
Dinesh

Anything related to WD here ??
Please put your question in relevant forum for a speedy response.
Regards
Manas Dua

Attribute Change Run terminating - repeated several times - not locked

I had a failure in my master data chain tonight. The attribute change run that ran yesterday ran for 11k seconds and was cancelled (it says manually). When the chain ran tonight, the process failed again. I checked the log and it says "UNCAUGHT_EXCEPTION" and it created a short dump. I tried repeating to see if it did anything and it gave me the same message.
I went into the change run monitor and reset the status and manually tried to run the change run again. Same result "UNCAUGHT_EXCEPTION".
I then checked table RSDDAGGRMODSTATE and there was no blank CNSID entries, but there was a blank "completed flag" entry. I don't have change access to the table in prod so I cannot manually change it to X (meaning closed). I reset the status again in the chagne run monitor and the record with the blank "completed flag" disappeared. I repeated the change run and it failed again and a new record with the "completed flag" being blank appeared in the RSDDAGGRMODSTATE table.
I checked SM12 and there are no locks there. I'm on 7.0 so I can't manually right click on 0CUSTOMER and activate the master data either.
As a last resort I did run the function module RSDDS_AGGR_MOD_CLOSE but that short dumped too.
Any ideas? Please? This will fail my other chains that have 0CUSTOMER in the aggregates. Thanks.

HI,
Firstly try this FM RSDDS_AGGREGATES_MAINTAIN
if not possible
Try doing it manually
Uncaught exception may come due to many reasons
IN RSA1 go to tools and select attribute change run
Check the blog it shows you how to manually do attribute change run step by Step (for BI7.0 also)
/people/debjani.das/blog/2009/03/30/attribute-change-run-acr
Regards,
MADhu.
Edited by: MadhuMarupudi on Aug 21, 2009 5:49 AM

Failed change run in CHANGERUNMONI

Hi all,
How to change the status of a failed change run in CHANGERUNMONI, actually one of our change run failed so we are trying to restart it using CHANGERUNMONI, and trying to restart the status forcefully, but it's giving us short dump.
Please give some advice, its urgent.
Regards,
Partha

nformation on where terminated
   Termination occurred in the ABAP program "RSDDS_CHANGERUN_MONITOR" - in
    "ROLLBACK_CHANGERUN".
   The main program was "RSDDS_CHANGERUN_MONITOR ".
In the source code you have the termination point in line 152
   of the (Include) program "DS_CHANGERUN_MONITOR_F02".
   The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
   procedure "ROLLBACK_CHANGERUN" "(METHOD)", but it was neither handled locally
    nor declared
   in the RAISING clause of its signature.
The procedure is in program "RSDDS_CHANGERUN_MONITOR "; its source code begins
    in line
   126 of the (Include program "DS_CHANGERUN_MONITOR_F02 ".
The ABAP code is
Source Code Extract
Line SourceCde
122     aggregatesdeactivate( l_th_node ).
123
124   ENDMETHOD.
125
126   method rollback_changerun.
127     data: l_TS_STATE_CR TYPE RSDDS_TS_STATE_CR,
128           l_s_state     type rsdds_s_state_cr,
129           l_t_chngprot type standard table of rsddchngprot
130                              with non-unique key TABLE_LINE,
131           l_s_chngprot type rsddchngprot.
132
133 *   check that the changerun is not running
134     CALL FUNCTION 'RSDDS_AGGR_MOD_STATE_GET'
135       IMPORTING E_TS_STATE_CR = l_TS_STATE_CR.
136     read table l_ts_state_cr into l_s_state
137          with table KEY CNSID = i_cnsid.
138     check sy-subrc = 0
139       and l_s_state-running = rs_c_false.
140
141 *   copy selected characteristics and hierarchies
142 *   in protocol table
143     select * from rsddchngprot
144              into table l_t_chngprot
145              where cnsid = i_cnsid
146                and ( chabasnm <> space
147                    or hieid <> space ).
148     l_s_chngprot-cnsid = 0.
149     modify l_t_chngprot from l_s_chngprot
150            TRANSPORTING cnsid
           TRANSPORTING cnsid
           where cnsid = i_cnsid.
    insert rsddchngprot from table l_t_chngprot.
    CALL FUNCTION 'RSDDS_AGGR_MOD_CLOSE'
      EXPORTING i_cnsid = i_cnsid.
    call function 'DB_COMMIT'.
endmethod.
METHOD getcr_objects.
    DATA: l_s_chabasnm_cr TYPE rsdds_s_chabasnm_cr,
          l_s_chabasnm    TYPE rsdds_s_range_chabasnm,
          l_s_hier_cr     TYPE rsdds_s_hier_cr,
          l_s_hieid       TYPE rsdds_s_range_hieid.
    READ TABLE p_ts_state_cr INTO e_s_state
               WITH TABLE KEY cnsid = i_cnsid.
    IF sy-subrc NE 0.
      MESSAGE x299(brain) WITH 'RSDDS_CHANGERUN_MONITOR' '_GET_CR_OBJECTS' .
    ENDIF.
    l_s_chabasnm-sign    = rs_c_range_sign-including.
    l_s_chabasnm-option = rs_c_range_opt-equal.
    LOOP AT p_ts_chabasnm_cr INTO l_s_chabasnm_cr
            WHERE cnsid = i_cnsid.

RSDDS_AGGR_MOD_CLOSE

Similar Messages

Maybe you are looking for