RSAU499, error occurred in UPDATE_INFOCUBE for data target 0PUR_C01,0PUR_C04

[Former Member]

Hi all SCNers,

                         I hoep all are doing good in their projects.I have been activating 3.x infocube in MM purchasing and loading the data with 3.x dataflow with 3.x datasources and 3.x infosources.i was initializing data first for 2LIS_02_ITM with 3.x infopackage with immediate updating the data targets(0PUR_C01,0PUR_C04,0PUR_O01).When i initialize and loading data it has been giving this error "DATA RECORDS FOR PACKAGE 1 SELECTED IN PSA-1 ERROR(S)" ......" ERROR OCCURRED IN UPDATE_INFOCUBE FOR DATA TARGET 0PUR_C01" same errors for 0PUR_C04 cube also.you can see the errors in the below screen shot

i have searched SCN for the solutions.I have seen PSA might be having errors and i have checked PSA have errors and i put the check mark for conversion for 0REQUESTER infoobject in transfer structure and tried loading data again.now PSA has no errors but still the above errors came.I have followed the explanation given in the below link by applying note numbers 1610009,1152453,1610259.

http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2012/05/18/update-infocube-with-fail...

the note 1610009 is implemented and the other notes are saying can not be implemented in our system as our system version is BW 7.02,SAPKW70208.But still iam getting the same errors in the above screen even after all the things have been done.i am thinking still something i am missing somewhere.i am not able to pick the correct solution.its been 5days the problem has been arrived,please give me solution if anybody has seen this type of errors in their project.

Thanking you in advanced,

Sri

[former_member182470 · Accepted solution]

Can you delete this red request from Cube and update the corrected request through PSA scheduler to Cube? Please make sure you save the records which are edited in PSA.

[Former Member · Accepted solution]

Thank you for your prompt reply Suman,I have not edited any request in PSA.instead i have checked the check mark for CONVERSION for 0REQUETER infoobject and also maintained characters sets in RSKC.again initialized data after this,now the PSA data is looking fine without any errors.after this also i got the errors and again like you said i have deleted the requests at cube level and scheduled from PSA to CUBE but no success,same errors.

[MGrob · Accepted solution]

Hi

Have a look at the routine which is in your transferrule called r0001_0DELIVERIES and r0001_0CONTR_ITEM

If a return code <> 0 is returned from a routine without a message 
being sent, the system triggers a routine error and sends message RSAU 727 
"Routine &, return code = & without error message see Note 
1530791".
If you want the original behavior "SKIP Value", you can get this by 
initializing the return parameter "RESULT" in the routine.

You need to make the adjustments mentioned in your note

hope that clarifies

Martin

[Former Member · Accepted solution]

Hi Martin,i think you are referring note 1610009.I have implemented that note already but no use.

[MGrob · Accepted solution]

You need to make a change the routine the note won't fix it..

martin

[Former Member · Accepted solution]

Hi Martin my senior said that do not change any code in standard update rules.could you please tell me where should i change the code if in case i want to change routine.im expecting i should comment the RETURNCODE=4 in the below code for one of the update rule NUMBER OF DELIVERIES

PROGRAM UPDATE_ROUTINE.

*$*$ begin of global - insert your declaration only below this line  *-*

* TABLES: ...

* DATA:   ...

*$*$ end of global - insert your declaration only before this line   *-*

FORM compute_data_field

   TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring

   USING    COMM_STRUCTURE LIKE /BIC/CS2LIS_02_ITM

            RECORD_NO LIKE SY-TABIX

            RECORD_ALL LIKE SY-TABIX

            SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS

   CHANGING RESULT LIKE /BI0/V0PUR_C01T-DELIVERIES

            RETURNCODE LIKE SY-SUBRC

            ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update

*

*$*$ begin of routine - insert your code only below this line        *-*

* fill the internal table "MONITOR", to make monitor entries

   if ( COMM_STRUCTURE-PROCESSKEY = '002' or      "WE

      COMM_STRUCTURE-PROCESSKEY = '012' or

      COMM_STRUCTURE-PROCESSKEY = '022' )

    AND COMM_STRUCTURE-BWAPPLNM EQ 'MM'

    AND COMM_STRUCTURE-deliveries <> 0.

* result value of the routine

     RESULT = COMM_STRUCTURE-deliveries.

* if the returncode is not equal zero, the result will not be updated

     RETURNCODE = 0.

   else.

     RETURNCODE = 4.

   endif.

* if abort is not equal zero, the update process will be canceled

   ABORT = 0.

*$*$ end of routine - insert your code only before this line         *-*

*

ENDFORM.

[MGrob · Accepted solution]

what's the routine r0001_0CONTR_ITEM look like?

Martin

[MGrob · Accepted solution]

If you implement 1610259

Execute the program 'SAP_RSADMIN_MAINTAIN'.
In the 'OBJECT' field, enter the value RSAU_RETURNCODE_OLD, and in the 
'VALUE' field, enter the value X.

your problem would be gone.. otherwise you need to initalize the return value.

else.

     RETURNCODE = 4.

RESULT "".

   endif.

those two options should fix it

Martin

[Former Member · Accepted solution]

Martin it is saying Note 1610259 CAN NOT BE IMPLEMENTED in our release.maintained the value X for RSAU_RETURNCODE_OLD but issue is not resolved.you want me to put the RESULT after RETURNCODE=4 statement??

[MGrob · Accepted solution]

the note is also not containing correction instructions.. you only need to set the parameter and also regenerate the updaterule as described in the note!

• You can force a regeneration of all update rules as follows:

• Call transaction RSSGPCLA.

• Select the program class RSAUTMPLUR (Generated Update
  Programs).

• • Choose "Set Status" (Ctrl+F3).

otherwise set the result value after returncode=4

[Former Member · Accepted solution]

if i do this transaction RSSGPCLA and set status for RSAUTMPLUR is there anyway i can revert back?.i exactly do not understand what is this "regeneration of all update rules"

[MGrob · Accepted solution]

regenerating the update rules is just activating the update rule again.. there is nothing to revert back..it just needs to regenerate the program code

[former_member182470 · Accepted solution]

Hope you have already checked this SAP Note : 1530791 and followed all the guide lines of that.

You can just re-install your update rules from the business content. Otherwise try to just activate it.

[Former Member]

Issue has been resolved(BW7.02,SAPKW70208).followed like this in my step

1) Implemented note 1610009

2) set the value 'x' for RSAU_RETURNCODE_OLD and value ' ' for RSAU_RETURNCODE_NEW by executing program SAP_RSADMIN_MAINTAIN in SE38

3)run the program RSDD_RSTMPLWIDTP_GEN_ALL with parameters

P_PROV : ' ' (no value)

P_IC_ACT : 'X'

P_PG_GEN : 'X'

4)T-code RSSGPCLA

selected program class RSAUTMPLUR and choosen "set status (ctrl+f3) "

Thank you Suman,Ramanjaneyulu and Martin for helping me.Martin suggestions have shown exact path to solve this issue,

[former_member219865]

i had this issue and fixed it with this steps, many thanks

[RamanKorrapati]

Hi Sy,

Error itself saying to see the note 1530791. Have you seen that note.

As my guess there is routine which causing this issue.Please check transformations between info cube and source(datasource or dso).

You may have routine at your transformations. have you done sytax check on it.

Thanks

[Former Member]

Hi Ramanjaneyulu,I have read note 1530791 but it cant be implemented for our release (7.02,support package08).i knew one of the routines from two cubes having RETURNCODE<>0 which is the main cause.thats why i have mentioned note numbers 1610009,1152453,1612059 for correcting those errors,nothing is working,im thinking there might be another solution or i am not be following correct sequence.i have applied note 1610009 but notes 1152453,1612059 are cant be implemented for my release.

[RamanKorrapati]

Hi Sy,

Try to check all notes which are applciable as per your bw version. mean while search at oss market palce. if not helped then raist to SAP.

Thanks