Error occurred in UPDATE_INFOCUBE for data target

[Former Member]

Hi Experts,

We have upgraded our SAP BW 3.5 system to BW 7.3 SP4.

When we try to load the master data into some InfoObjects, we are getting the error mentioned in the subject.

We tried several solutions mentioned, for example mentioned in this blog http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2012/05/18/update-infocube-with-fail... and several other solutions mentioned on the forum like implementing note 1610259, 1610009, etc. but in vain.

Could someone suggest us if we are missing something...

Thanks in advance,

Kind Regards,

Ashmeel.

[Former Member]

We've tried those things, too, and they didn't work for us, either.  We just logged a customer message to SAP, and I suggest you do the same.

[Former Member]

Thanks Johnson for your reply.

Please keep us updated regarding the reply from SAP.

If we find some solution, we'll update.

Thanks & Regards,

Ashmeel.

[Former Member]

Hi Johnson,

We have solved this issue.

Solution:

TCode RSKC --> Enter ALL_CAPITAL_PLUS_HEX --> Execute.

We debugged the FM RSKC_CHAVL_CHECK and understood that its behaving strangely.  Then We understood that the RSKC settings have to be changed.  We have changed the settings from ALL_CAPITAL to ALL_CAPITAL_PLUS_HEX.

Reason to change:

The source system is sending some hexa-decimal characters which are not accepted in BW.  But when we see these characters in BW and R/3 they are shown as #, which are accepted as we have field routines for these.  Later we understood that this is not a # character but some other character pretending to be #.

Regards,

Ashmeel.

[Former Member]

That is good news.  We tried it in our system, but unfortunately, we still get the UPDATE_INFOCUBE error.  We will inform SAP.

[Former Member]

Hi Johnson,

As mentioned in note 1075403, SAP does not recommend to have ALL_CAPITAL_PLUS_HEX in the RSKC settings.  So we used the FM SCP_REPLACE_STRANGE_CHARS in field routines to convert the strange characters into readable format.  But ALL_CAPITAL_PLUS_HEX helped as a quick-fix for the problem we faced.

Hope this helps.

Regards,

Ashmeel.