Update Infocube with failures RSAU499 (UPDATE_INFOCUBE) and RSAU727
Introduction
I have seen recently a lot of problems related to the change of the RETURNCODE behavior in update rules, and I thought, it would be a good idea to give a brief overview of this change, and how this can be handled in different BW systems. Furthermore, I would like to give you some hints, what should be checked to analyze the problem and finally in the last part of this blog entry, I would like to summarize the release specific properties.
Graph 1: Update Rule Failure Message in Monitor
Background
If a routine ends with a non-zero value (returncode <> 0), this will be interpreted as „Skip Value”. In this case, the system sends simultaneously messages to the monitor for the specific record . The endeffect of this phenomenon, that a so called „sorting” mechanism influences the entire data record flow. Until now, the BW systems ignored only those values, which match the condition return code <> 0 without any „ERROR” message in the MONITOR variable within the routine. With the help of note 1610009, the subsequent change to the standard SAP behavior will be undone. The consulting note 1610259 helps you to reach an consistent „reaction” from the system. The above mentioned note delivers the correction for behavior data consistency (with and wihout „ERROR” message).
Graph 2: Performance Assistant Inform Us About Message No. RSAU499
Effects of note 1610009
Release 7.x: set the functionality of returncode <> 0 back to starting point (original behavior).
Release 7.30: you can set the old behavior like in 7.x and the interpretation of returncode will be handeld similar as for routines in transformations. This leads to simplification of migration of the update rules to a transformation.
Hints to analyze the issue
Parameter in RSADMIN:
1.Call transaction ‘SE16’
2.Open up table “Table name: RSADMIN”
3.Object: RSAU_RETURNCODE_OLD or RSAU_RETURNCODE_NEW
Graph 3: The Table RSADMIN In Transaction SE16
Has the update rule already re-generated?
1.Call transaction ‘RSA1’
2.Double click on Update Rule
3.In menu “EXTRAS” choose “Display Activated Program”
4.Under “Date:” you will find the date of re-generation
Graph 4: Header Of Generated Program
Release-dependent solutions
3.x Dataflow, Release 7.x:
Implement note 1610009
Deactivate both entries in table RSADMIN
Execute the program ‘SAP_RSADMIN_MAINTAIN’ in SE38:
Object: RSAU_RETURNCODE_NEW and RSAU_RETURNCODE_OLD
Value: ‘ ‘
Follow instructions of note 1152453 with parameters:
p_prov: <InfoProvider>
p_ic_act: ‘X’
p_pg_gen: ‘X’
This report generates the new programs from the template RSTMPLWIDTP and cleans up the staging table RSUPDINFO. Note 1152453 contains the description and code for the program.
For regeneration of update rules follow the instructions of 1610259:
- Call transaction RSSGPCLA
- Select the program class RSAUTMPLUR (Generated Update Programs)
- Choose “Set Status” (Ctrl+F3).
7.x Dataflow, Release 7.x: no modifications necessary
3.x Dataflow, Release 7.3 and newer:
Implement note 1610009
Activate RSAU_RETURNCODE_OLD entry in table RSADMIN ( in SE16 )
Execute the program ‘SAP_RSADMIN_MAINTAIN’ in SE38:
Object: RSAU_RETURNCODE_OLD
Value: ‘ X’
Follow instructions of note 1152453 with parameters:
p_prov: <InfoProvider>
p_ic_act: ‘X’
p_pg_gen: ‘X’
This report generates the new programs from the template RSTMPLWIDTP and cleans up the staging table RSUPDINFO. Note 1152453 contains the description and code for the program.
For regeneration of update rules follow the instructions of 1610259:
– Call transaction RSSGPCLA
– Select the program class RSAUTMPLUR (Generated Update Programs)
– Choose “Set Status” (Ctrl+F3).
If the issue afterwards still remains, SAP Note #2339662 should be applied to the system. Please be aware that the SAP Note does not resolve the issue but contains corrections to provide more meaningful error messages.
7.x Dataflow, Release 7.3: no modifications necessary
List of referenced notes and documents:
#1530791 – Update rule does not pass on data to process chain
#1610009 – Return code in update rules: Error RSAU 727
#1610259 – Controlling ‘Returncode’ behavior in update rules
#1152453 – Termination generating InfoCube write program
#1657246 – Problems loading data in BW 7.3 SP4&5
#1855275 – Cube writer: Error for 3.x data flow and mass writer
(Remark: RSDD_ENABLE_MASS_CUBE_WRITE should set to ‘X’.
HANA: default (can be set to ‘ ‘)
Oracle: not default (can be set to ‘X’)
If the Cube-Mass-Writer is not enabled via the RSDD_ENABLE_MASS_CUBE_WRITE parameter, then a different method for writing is used.)
Documentation:
http://help.sap.com/saphelp_nw73/helpdata/en/21/894eeee0b911d4b2d90050da4c74dc/frameset.htm
Hi Norbert Putz,
Nice and very useful blog with detailed explanation 🙂
Regards
Renjith
Post authorNamaste Renjith,
Thanks for your comment. I’m glad that you find this blog useful 🙂
Best regards,
Norbert
We face many new kind of issues while loading data to IC, this doc will help us to understand how to get rid of this rsau499 failures.
Kind Regards
Manna Das
Hi Norbert
Very good blog. It describes with details the issue. I worked in many incidents with this issue and suggested your blog 🙂
Jana
Hi Norbert,
Nice and very useful blog to enhance our knowledge…:)
Regards,
Lalit
Hi Norbert,.
I have an accompanying KBA 1887091 which you might add to your “List of referenced notes..” section above?
thanks,
Colum
Namaste Norbert,
This is really a helpful blog. We had same issue with a HANA optimized cube, we check ed all the setting as mentioned in your blog & Data volume is less, but One of the Datapackage was failing with “Write_Ic” error.
Upon implementation of note 2339662, exact error got as “CL_RSDD_CUBE_WRITER->WRITE_UR cl_rsdd_cube_mass_writer Problem during the masswriter activity “. We noticed that RSDD_ENABLE_MASS_CUBE_WRITE was missing in RSADMIN table. Upon enabling it, data load issue resolved.
Wondering what impact RSDD_ENABLE_MASS_CUBE_WRITE has on all other data loads. Will there be any performance degradation, as this setting may enable MASS Processing.
Thanks- Deepak