error occur ODS to IC

[Former Member]

Hi experts,

i am having an issue that i am getting invalid char from ods to IC

now i need to insert option that at processing step 1.psa & then data target.

for this i am unable to choose that because its in disable

i cant find that package in INFOSOURCE &not even find out that DS in SOURCE system under MODELING & mone thing that is of 8zgl_01 infosource where can i find that............

PLZ help it out

Regard's

venkat

Edited by: venkatesh.ravilla on Jun 28, 2011 7:49 AM

[former_member186445 · Accepted solution]

not sure what you mean...but a here is a guess:

when you load from dso to cube there is NO psa. the psa is only used when loading from an actual datasource.

you can find the datasource (as a dso) under the datasources tree of your bi system.

concerning your actual problem, invalid char: the fact that you only have this problem when loading to the cube and not to dso is because you have no sid generation in the dso.

your solution is to figure out which char is invalid. delete the load from cube and dso. adapt the data in psa. reload the dso and further upload to the cube

M.

[Former Member · Accepted solution]

Hi Tibollo,

my problem is exactlly wht u think but i cant delete it in ods y because that my last 4months delta around 9500000 when i reloaded it again it showing short dump.

so main soultion is can i put PSA option in b/w ODS & IC then it can be easy i think. tell the require steps and is there any way rather than deletion.

Regard's

venkat

[Former Member · Accepted solution]

You can use the transaction RSKC to 'Pemitted extra characters" in you system. So you need to identify the erroneous characters. Even .,'' may be counted as invalid

[former_member186445 · Accepted solution]

as far as i know you don't have the possibility to have a psa between dso and cube. if you can't delete the data from the dso, the best option is to handle this in update rule/transformation.

figure out which infoobject is giving the problem (and why), and create a routine for this object in the transformation to delete the invalid char (or maybe you just need to translate to uppercase).

then transport the modifications to production and load again from dso to cube. the problem should then be solved.

afterwards you can leave the modification or you can put the transformation back to the original state.

M.

[Former Member · Accepted solution]

YES wht your saying right previouslly i did the same at that time..... my field elemenate that particular invalid value.

at that time i got another field invalid char so i deleted req.

for some reasons we deleted req in ods also then Intialization faild. so now we did instalation and reconstruted the that req now i am having code we wrote at that time but now it showing same invalid char in same record

Regard's

venkat

[srikanthbwbw · Accepted solution]

Hi,

Can you please tell us on which objects the error is pointing to. If its invalid then you can just maintain your char into RSKC or write a routine to disregard invalid char.

thanks

srikanth

[Former Member · Accepted solution]

Hi srikanth,

i am having 02-Ã

 LCD101118122 of special char in between A & A they press enter not an space or just gap so that we can't write a program for this can u help me out of this.

Regard's

venkat

Edited by: venkatesh.ravilla on Jun 28, 2011 1:51 PM

[Former Member · Accepted solution]

Hi Venkat,

i think you need to do the mapping between the valid and invalid characters like Ã.

Read mapping table between invalid and valid chars

read the table /bic/pcvalc WHERE objvers = 'A' AND /bic/cvalc NE ' '.

regards,

adlin

[Former Member · Accepted solution]

Dear all,

for this error we wrote a code error finesh up but i get new error that

i am having 2 delta request one is 200000 & 2nd is 9500000. but when i updated these to IC i am getting only 8700000.

can u any one tell me y it happen.

all post ill be revarded

Regard's

venkat

[former_member186445 · Accepted solution]

i suppose the 200000 & 2nd is 9500000 is the number of records in the delta infopackage to the dso. that's what you see in the manage tab and this will be the number of records in the new data table of the dso. however when loading from dso to ic it's not the new data table that's used but the change log table. this table reflects the delta of the new data and the already active data. hence it's normal that you don't have the same number of records in the delta load towards the dso.

M.

[Former Member]

Thank's for your contrebution friend.

[Former Member]

Dear All,

Here is a try and kindly find the below suggestions i have.

1) to find the erroneous records use the tables

RSERRORLOG to check error records RSERRORHEAD to check PSA records

2) kindly try to load small chunks of data to DSO so tat error rectification can be fast and u can avoid short dump.

Thanks and Kind Regards,

Sandeep

[Former Member]

Hello Venkatesh,

Please check whether Update rules are active version between DSO and Cube , if not make the update rules as active. After making Update rules active then u create a new infopackage as per ur requirement and load the data.

Regards,

Krishna.