Invalid character error during load to cube

I have char length 30 and i trying to populate the cube field zpacreanm with values
"barrier" in transformation, please help me should i reduce the length of char to 10
or what should be th solution of error below.
Error
Value 'barrier' (hex. '004E0065007700410063007100750069007300690074006900') of characteristic ZPACREANM contains invalid Character
Please help me asap to resolve will really appreciate
Thanks
Soniya

Hi,
U can do in this way also.......
actually there are no special charectors in ur text, the problem is u r trying to input lower case letters, u either change the lower case letters to upper case or
select the check box 'lower case letters' in info object change/create screen for the particular/ relevant info object.
assign points if useful
Gan

Similar Messages

Invalid character error while activating DSO - Please help

Hi experts,
I'm getting invalid hex character error when loading a text infoobject in my DSO. Repairing data records in the PSA is not an option. Changing the data in the source system is also not an option. I've tried many of the methods suggested in other threads, but am unable to get it working (ABAP code, "ALL_CAPITAL" etc). We are on an unicode system.
Can someone provide some clean code to eliminate the illegal hex characters (00-1f) in my transfer rule routine. Basically, replace the illegal hex characters with space or an acceptable character.
Many thanks,
Anita S.

Hi,
I have used the below code for removing all unwanted chars from 0MATERIAL, that worked fine. You can modify it for ur need.
CONSTANTS:
       G_ALLOWED_CHAR(58) TYPE C VALUE
         ' !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ'.
    data : E_ALLOWED_CHAR(58).
RESULT = SOURCE_FIELDS-MATNR.
    SHIFT RESULT RIGHT DELETING TRAILING SPACE.
    SHIFT RESULT LEFT DELETING LEADING SPACE.
    TRANSLATE RESULT TO upper case.
*RESULT = comm_structure-/BIC/ZCONTRTD.
    while RESULT ca '#'.
      RESULT+sy-fdpos(1) = ' '.
    endwhile.
    if RESULT(1) = '!'.
      RESULT(1) = ' '.
    endif.
    do.
      if not RESULT co g_allowed_char.
        shift RESULT+sy-fdpos left.
      else.
        exit.
      endif.
    enddo.
Thanks
dipika

XML Publisher Report ends with Warning -- Invalid Character Error in XML

Hi,
I have migrated the standard report 'Invoice Print Selected Invoices' from Reports 6i to XML Publisher. It has to print a Euro(€) in the report. It does not even generate the XML File fully. It gives the below error in the XML File. When i remove the special character, it works fine.
Please let me know the settings to ensure that XML file also accepts the special characters. How do i get the Euro symbol printed in XML File with out giving Invalid Character Error?
===========================================================The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again
later.
An invalid character was found in text content. Error processing resource 'http://dfw1svdevapp03.ora.rackspace.com:8040/OA_...
<C_INV_CURRENCY_SYMBOL>
N class="m">>
<LINE_UOM />
<LINE_UNIT_SELLING_PRICE />
===========================================================
The XML File even does not show which character set it uses. The output file starts with:
===========================================================
<?xml version="1.0" ?>
- 
===========================================================

Hi Tim,
Thanks for your adhoc response.
I have gone thru the Document 222663.1 and it says that the Developer 6.0.8.23 is required to handle this problem. We are using almost the updated Developer version i.e., Developer 6.0.8.25. So, this should be handled automatically, but it still errors out. Please suggest.
Thanks,
Kesava

LPX-00217 invalid character error - Using reference characters in XML file

Hi, I hope you will help me to understand and to fix the error I get during insert of an XML file into a table with XML Type field.
I used Oracle documentation for this:
1. Create table
CREATE TABLE XMLDOC
( XMLCOLUMN xmltype);
2. Create external directory
CREATE OR REPLACE DIRECTORY FILESDIR AS 'E:\ora_xml_test\';
3. Create function
CREATE OR REPLACE function DSS.getClobDocument(
filename in varchar2,
charset in varchar2 default NULL)
return CLOB deterministic
is
file bfile := bfilename('FILESDIR',filename);
charContent CLOB := ' ';
targetFile bfile;
lang_ctx number := DBMS_LOB.default_lang_ctx;
charset_id number := 0;
src_offset number := 1 ;
dst_offset number := 1 ;
warning number;
begin
if charset is not null then
charset_id := NLS_CHARSET_ID(charset);
end if;
targetFile := file;
DBMS_LOB.fileopen(targetFile, DBMS_LOB.file_readonly);
DBMS_LOB.LOADCLOBFROMFILE(charContent, targetFile,
DBMS_LOB.getLength(targetFile), src_offset, dst_offset,
charset_id, lang_ctx,warning);
DBMS_LOB.fileclose(targetFile);
return charContent;
end;
And now appears the problem when I use different character references - one of them are parsed by the XML parser and another -are not:
test1.xml - Contains a charachter from Latin language -ă (&#x103)
<?xml version="1.0" encoding="UTF-8"?>
<ROWSET>
<ROW
<IDNO>1</IDNO>
<NAME>aaa (&#x103)</NAME>
</ROW>
</ROWSET>
--a semicolumn must be added after 103
SQL> insert into XMLDOC values(xmltype(getClobDocument('test1.xml','UTF8')));
1 row created.
test2.xml - Contains a charachter from Cyrillic language -ш (&#x404)
<?xml version="1.0" encoding="UTF-8"?>
<ROWSET>
<ROW>
<IDNO>1</IDNO>
<NAME>aaa (&#x404)</NAME>
</ROW>
</ROWSET>
--a semicolumn must be added after 404
SQL> insert into XMLDOC values(xmltype(getClobDocument('test2.xml','UTF8')));
insert into XMLDOC values(xmltype(getClobDocument('test2.xml','UTF8')))
ERROR at line 1:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00217: invalid character 1028 (\u0404)
Error at line 5
ORA-06512: at "SYS.XMLTYPE", line 0
ORA-06512: at line 1
I am not familiar to Unicode and encoding maybe I ' missing something.
Please help!!!

Which database version are you using and what is the characterset used during its creation...?
There is a lot on this forum which has been already answered / addressed but the database must support it, in other words the characterset must support it. Among others, see Re: XML-Document with special characters for instance.
Conversion like you are doing (&#x103) is not needed.

Error during loading of transaction data: An RFC call-up triggered the ...

Dear Sirs,
during loading of master data from a 4.6C SAP system to BI 7.0 SP9 I get the following error during processing (data packet).
<i>"An RFC call-up triggered the exception (ID: RSAR NO: 503) "</i>
The strange thing with this error is that it emerged today, after successfully loading master data and a subset of transaction data yesterday from same source system.
Has anyone else come across this error, and can tell us where we should look for a possible solution? (or a better error explaination).
The RFC connections works fine when testing in SM59, and was functioning yesterday. No relevant dumps in either system.

Hi folks,
I am also interested in this error.
Thanks.

How can we handle an invalid character while doing loading in bi7 ?

means procedure and details
     issues:
             i have taken an invalid character in my flatfile
              and i want to solve this so that i can see these invalid characters in report correctly
Please search the forum before posting a thread
Edited by: Pravender on Feb 4, 2012 11:06 AM

Hi Nihararanjan,
This issue has been discussed many times, please search in SDN for more threads.
You go to t.code RSKC and maintain the Invalid or Special characters and then you can load.
Check the below doc for the same:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0cdc928-5e2d-2e10-e1bb-ec77bcb5cbfd?QuickLink=index&overridelayout=true
Regards,
Raghu

Errors during Loading TD from Flat file to PSA

Hi Guys,
I got some errors while loading the flat file transaction data into PSA using infopackage.
Could you guys can help me to solve the below errors. It would be more appreciated if you guys could send some material which tells about these types of errors more detailly.
Points will be awarded.
Field /BIC/ZIO_PRIC ( Position 4 ): External length specification will be ignored
Message no. RSDS101
Diagnosis
The value 23 is specified as output length in Field /BIC/ZIO_PRIC ( Position 4 ). It is also specified that the data is shipped in internal format.
System Response
The length specification for output length is ignored. If the data in the source actually have the specified lengths, this results in conversion errors.
Procedure
Select the external format if required.
Field /BIC/ZIO_PRIC ( Position 4 ): Amount field in internal format; check settings
Message no. RSDS099
Diagnosis
Setting made for Field /BIC/ZIO_PRIC ( Position 4 ) states that the data from the source is available in the internal format.
This is not usually the case for this source system type.
System Response
If you do not change this setting, the data has to be available in the internal SAP format.
Example:
For the Japanese Yen this means: 1000 JPY has to be delivered from the source as 10.00 JPY.
Procedure
Check the data format of the source and where necessary, change the setting to External.
Field /BIC/ZIO_PRIC ( Position 4 ): Missing reference to currency field/unit field
Message no. RSDS151
Diagnosis
If an amount or quantity field is not delivered with values in internal format, an associated currency field or unit field must be specified so that the currency or units can be converted during data import.
System Response
The DataSource can not be activated.
Procedure
Specify a reference field if the data is delivered in external format.
Specify a reference field even if the currency or unit is constant. Fields with fixed values are not part of the data source; they are filled by the system when loaded.

Hi JUergen.
The order of the fields are same as datasource. I didn't make any field for amount in a flat file as it is defined as fixed currency usd when i created a key figure. i don't think so we have to create a field unless we take 0currency is a unit for price instead of fixed currency.
Though we got the above error, it still allows activates the datasource but the 10.00 usd shows as 1000 usd.
Cheers,
Shrinu

Error During Load Infocube from ODS

Hi guys i hae an infocube and an ODS i load data to the ODS directly from SAP and its OK but i have an error when i try to load data from ODS to infocube, i`ve created an update rule from ODS to infocube theres an error in the load request "Load Request is invalid" i try to load to infocube from ODS in many ways Full, Init Delta but i have the same error in all of them.....i need to do something before or i need to change in any way the data targets.....
I hope somebody could help me with this.......

HI,
Activate the data in ur ODS. Then right click on ur ODS n choose "create export datasource". Now right click ur ODS and go to "Manage" and make sure that the QM status is green and the Datamart status is checked with a green mark. Now carry on the load from ODS to infocube.
Hope this helps...Let me know
Regards,
R.Ravi

Getting ORA-00911: invalid character error in the func ?

CREATE OR REPLACE FUNCTION f_get_oibt_value(argin_rollent IN VARCHAR2,
argin_rollsubent IN VARCHAR2,
argin_legalORdervied IN CHAR,
argin_year IN VARCHAR2,
argin_currmtd IN VARCHAR2)
RETURN NUMBER AS
ln_oibt_value NUMBER;
ln_oibt_l_value NUMBER;
ls_acct_id VARCHAR2(10);
sql_stmt VARCHAR2(2999);
BEGIN
-- dbms_output.enable(9999);
IF UPPER(argin_legalOrdervied) = 'L' THEN
ls_acct_id := 'OIBT-L';
ELSE
ls_acct_id := 'OIBT-D';
END IF;
sql_stmt := 'SELECT SUM (NVL (DECODE (yr, ''' || argin_year || ''', avg_ytd_' || argin_currmtd || ', 0), 0)) ';
sql_stmt := sql_stmt || 'FROM ma_temp_local ';
sql_stmt := sql_stmt || 'WHERE roll_ent = :argin_rollent '; --(Input argument)
sql_stmt := sql_stmt || 'AND roll_sub_ent = :argin_rollsubent '; --(Input argument)
sql_stmt := sql_stmt || 'AND ent NOT IN (''817'', ''PSP'') ';
sql_stmt := sql_stmt || 'AND acct_id = ''legal'' '; --Fixed
sql_stmt := sql_stmt || 'AND acct = :ls_acct_id '; --Fixed
sql_stmt := sql_stmt || 'AND rel_type = '' '' '; --Fixed
sql_stmt := sql_stmt || 'AND acct_lvl <= ''0'' '; --Fixed
sql_stmt := sql_stmt || 'AND yr = :argin_year '; --(Input argument)
sql_stmt := sql_stmt || 'AND rec_type = ''A'' '; -- Fixed
sql_stmt := sql_stmt || 'AND product_code = ''ALL'' '; -- Fixed
sql_stmt := sql_stmt || 'AND segment_code = ''ALL'' '; -- Fixed
sql_stmt := sql_stmt || 'GROUP BY roll_ent, roll_sub_ent;';
--dbms_output.put_line(sql_stmt);
EXECUTE IMMEDIATE sql_stmt
INTO ln_oibt_l_value
USING argin_rollent, argin_rollsubent, ls_acct_id, argin_year;
RETURN ln_oibt_value;
END f_get_oibt_value;
getting below errors..
ORA-00911: invalid character
ORA-06512: at "F_GET_OIBT_VALUE", line 36
ORA-06512: at line 3

Are You Getting the error while creating the function or while excuting it
SQL>CREATE OR REPLACE FUNCTION f_get_oibt_value(argin_rollent IN VARCHAR2,
2 argin_rollsubent IN VARCHAR2,
3 argin_legalORdervied IN CHAR,
4 argin_year IN VARCHAR2,
5 argin_currmtd IN VARCHAR2)
6 RETURN NUMBER AS
7
8 ln_oibt_value NUMBER;
9
10 ln_oibt_l_value NUMBER;
11 ls_acct_id VARCHAR2(10);
12 sql_stmt VARCHAR2(2999);
13
14 BEGIN
15 -- dbms_output.enable(9999);
16 IF UPPER(argin_legalOrdervied) = 'L' THEN
17 ls_acct_id := 'OIBT-L';
18 ELSE
19 ls_acct_id := 'OIBT-D';
20 END IF;
21
22 sql_stmt := 'SELECT SUM (NVL (DECODE (yr, ''' || argin_year || ''', avg_ytd_' || argin_currmtd || ', 0), 0)) ';
23 sql_stmt := sql_stmt || 'FROM ma_temp_local ';
24 sql_stmt := sql_stmt || 'WHERE roll_ent = :argin_rollent '; --(Input argument)
25 sql_stmt := sql_stmt || 'AND roll_sub_ent = :argin_rollsubent '; --(Input argument)
26 sql_stmt := sql_stmt || 'AND ent NOT IN (''817'', ''PSP'') ';
27 sql_stmt := sql_stmt || 'AND acct_id = ''legal'' '; --Fixed
28 sql_stmt := sql_stmt || 'AND acct = :ls_acct_id '; --Fixed
29 sql_stmt := sql_stmt || 'AND rel_type = '' '' '; --Fixed
30 sql_stmt := sql_stmt || 'AND acct_lvl <= ''0'' '; --Fixed
31 sql_stmt := sql_stmt || 'AND yr = :argin_year '; --(Input argument)
32 sql_stmt := sql_stmt || 'AND rec_type = ''A'' '; -- Fixed
33 sql_stmt := sql_stmt || 'AND product_code = ''ALL'' '; -- Fixed
34 sql_stmt := sql_stmt || 'AND segment_code = ''ALL'' '; -- Fixed
35 sql_stmt := sql_stmt || 'GROUP BY roll_ent, roll_sub_ent;';
36 --dbms_output.put_line(sql_stmt);
37 EXECUTE IMMEDIATE sql_stmt
38 INTO ln_oibt_l_value
39 USING argin_rollent, argin_rollsubent, ls_acct_id, argin_year;
40
41
42 RETURN ln_oibt_value;
43
44 END f_get_oibt_value;
45 /
Function created.
SQL>drop function f_get_oibt_value;
Function dropped.
SQL>

'Invalid Dim' error during dynamic dim building

Hi Folks,
I am trying to update an outline using my own dim rules file and data .txt file, but i get an error in the dimbuild log file saying "\\Column 7 - Invalid Dimension" What could be the reason for this? The outline already contains 5 standard dims (i.e. Customer, Period, Account, Scenario and Year) and 2 more attribute dims. My goal is to add some new members to the existing Account dim. My data file looks like this:
Account,Metrics,,O,~
Metrics, Avg_Wolverines_Juggled, Average Wolverines Juggled, S,~
Metrics, Avg_Dropped_Wolverines, Average Dropped Wolverines, S,~
Metrics,Headcount,,S,~
In the data-prep editor I have created a .rul file that has 6 columns (fields). The first field I created by mistake, so I have set it to 'ignore field..' under 'dim build properties'. The next 5 fields map correctly to the way I have arranged my data file, i.e Parent0, Account Child0, Account Alias0, Account Property0, Account Property0, Account
This .rul file validates correctly, but when I try to update the outline, I get the "\\Column 7 - Invalid Dimension" error log message. The log msg says that the data file contains an error, but may have partially loaded data. However, I don't see a SINGLE new member added to the outline..
In terms of settings, everything under 'Dim Build Properties' seems fine. i.e. for each field the correct dim type (e.g. Parent, Child, Alias, or Property) and dim name (i.e. Account) is selected. However, under 'Dim Build Settings', when i try to choose 'Account' as the dim name, it reverts back to the name of the first dim in the outline (i.e. Customer) whenever I close/reopen 'Dim Build Settings' This happens even though I do a double-click and make sure 'Account' is shown in Blue before closing out of 'Dim Build Settings' Could this have something to do with the error I am getting? I have also made sure that the 'Build Method' is correct (i.e. Parent/Child references) for the two main dim fields. As per my understanding, for alias and properties fields, the Build Method doesn't matter.
I apologize for the long question, but would really appreciate some help.
thanks,
Akshay

Ah good old wolvering Juggling. The problem is they will bite you if you are not careful. (It's a nice metaphor for essbase). learning from Edwards book I see.
your file looks like it only has five columns and you say you created a sixth column that you set to ignore. The message indicates there is a 7th column. Open your load rule and your data file and see if in fact there is a trailing column. Also, make sure you set the dimension build properties for the account dimension to be parent/child

"Invalid Character" error when executing a 13KB query with ADO

Hello
I want to execute a query using an ADO Recordset using the Open method. When calling this method, an ORA-911 "Invalid Character" raises. I can say that the SQL runs fine, because using the SQL*Plus utility it works.
I have a 11g client installed, and the target database is in a 9i server; my PC uses WinXP SP2.
What could be wrong?
Thanks a lot.

Well there's a 32K limit in Oracle. (But it can be overcome using dynamic sql).
You basically end up putting the text in an associative_array which has to be sequential.
There should be info on askom.oracle.com as I initially posted the question there.
13KB of characters is a lot of query text, and it could easily be the provider.
Try the microsoft ADO provider and see if you get the same problem.
There was another company which had a provider (which you had to pay for) , can't remember its name , but it seemed to be the best.
I would seriously question why you need to pass a 13KB string to oracle though.

Invalid character error while activating data in DSO.

Hi Experts,
We are facing an issue with presence of invalid characters in data from source. This throws SID generation error while activating data in DSO. Long text of error shows like this:
"Value " ĠĠĠĠĠĠĠĠĠĠĠĠĠĠĠ" (HEX 000D0120012001200120012001200120012001200120012001) of characteristic contains an error at position 1"
Also we've tried adding the character " Ġ " in TCode RSKC, but it then shows as a rectangle box which I'm not able to copy manually(looks like a blank space or something of that sort).
We've tried implementing routine to remove special characters while loading data, but still it fails. Due to huge amounts of data, its practically unfeasible to check each record manually.
Any useful suggestions will be acknowledged.
regards,
anoop

Hi,
We are using following code for the same purpose. U can use it at infoobject level mapping. This code will check value of each character in the data coming, whether it is in RSKC, if it is a allowed one then it will be passed as it is. Otherwise it will replace that character by space.
    data: l_d_length like sy-index,
             l_d_char type c,
             l_d_index type sy-index,
          l oopx like sy-tabix.
    data : xinfobj(30) type c value 'RABC'.    -> this is ur infoobject name
    clear : result.
    call function 'CONVERSION_EXIT_ALPHA_INPUT'
      exporting
        input = tran_strucutre-XYZ     -> object name in ur structure
      importing
        output = result.
    l_d_length = strlen( result ).
    do l_d_length times.
      l_d_index = sy-index - 1.
      l_d_char = result+l_d_index(1).
      call function 'RSKC_CHAVL_OF_IOBJ_CHECK'
        exporting
          i_chavl                 = l_d_char
          i_iobjnm                = xinfobj
    I_S_COB_PRO             =
    I_T_COB_PRO_CMP         =
       exceptions
         chavl_not_allowed       = 1
         others                  = 2
      if sy-subrc <> 0.
        result+l_d_index(1) = ' '.
      endif.
    enddo.
Regards;
Jitendra

Error during loading and deletion of write-optimized DSO

Hey guys,
I am using a write optimized DSO ZMYDSO to store data from several sources (two datasources and one DSO).
I have disabled the check of uniqueness in the DSO, but I defined a semantic key for the fields ZCLIENT, ZGUID, ZSOURCE, ZPOSID which are used in a non-unique index.
In the given case, I want to delete existing rows in the DSO. I execute these steps in the endroutine. Here the abstract coding:
LOOP AT RESULT_PACKAGE ASSINING <RESULT_FIELDS>.
u201Csome other logic [u2026]
DELETE /BIC/AZMYDSO00
WHERE /BIC/ZCLIENT = RESULT_FIELDS-/BIC/ZCLIENT
     AND /BIC/ZGUID = RESULT_FIELDS-/BIC/ZGUID
AND /BIC/ZSOURCE = RESULT_FIELDS-/BIC/ZSOURCE
AND /BIC/ZPOSID = RESULT_FIELDS-/BIC/ ZPOSID.
ENDLOOP.
COMMIT WORK AND WAIT.
During the Loading (after the transformation step in the updating step), I get the messages (not every time):
1.     Error while writing the data. (RSAODS131)
2.     Could not Save DataPackage xy in DataStore ZMYDSO (RSODSO_UPDATE027).
Diagnosis: DataPackage XY could not be saved. Reasons therefore could be violation of key uniqueness (duplicate data) or general database error.
3.     Error in the substep of updating DataStore.
I have checked the system log (SM21) and the system dumps (ST22) but I could not find an exact error description.
I guess, I am creating some inconsistencies or locks (I also checked the SM12) so that the load process interrupts. But I also tried a serial updating within the DTP (I reduced the number of batch processes to 1). No success.
Perhaps the loading of one specific package could take a longer time so that the following package would overtake the predecessor. Could that be a problem? Do you generally advise against the deletion of rows within the endroutine?
Regards,
Philipp

Hi,
is ZMYDSO the name of the DSO?
And is this the end routine of the transformation while loading the same DSO?
if so we never do such a thing.
you are comparing the DSO with the data that is flowing in and then deleting the data from the DSO...
Which doesnt actually make any sense... because when loading the data to a DSO (or a cube or any table) the DSO (or cube) will be locked exclusively for any modifications of data. You can only read data from it.
If your requirement is that existing duplicate records need not arrive in the DSO then you can delete the data from the SOURCE_PACKAGE in the start routine like below
SELECT FIELDS FROM /BIC/AZMYDSO00 INTO INTERNAL_TABLE WHERE <CONDITION>.
LOOP AT INTERNAL_TABLE.
   DELETE SOURCE_PACKAGE
WHERE SOURCE_PACKAGE-/BIC/ZCLIENT = INTERNAL_TABLE-/BIC/ZCLIENT
     AND SOURCE_PACKAGE-/BIC/ZGUID = INTERNAL_TABLE-/BIC/ZGUID
AND SOURCE_PACKAGE-/BIC/ZSOURCE = INTERNAL_TABLE-/BIC/ZSOURCE
AND SOURCE_PACKAGE-/BIC/ZPOSID = INTERNAL_TABLE-/BIC/ ZPOSID.
ENDLOOP.
or if your requirement is that you need to delete the old data from the DSO for the same key which is arriving newly in order to load the new data into the DSO in that case, you could do something like this in the start routine
SELECT FIELDS FROM /BIC/AZMYDSO00 INTO INTERNAL_TABLE FOR ALL ENTRIES IN SOURCE_PACKAGE
WHERE /BIC/ZCLIENT = SOURCE_PACKAGE-/BIC/ZCLIENT
     AND /BIC/ZGUID = SOURCE_PACKAGE-/BIC/ZGUID
AND /BIC/ZSOURCE = SOURCE_PACKAGE-/BIC/ZSOURCE
AND /BIC/ZPOSID = SOURCE_PACKAGE-/BIC/ ZPOSID.
* now update the new values you want to write in the loop
LOOP AT INTERNAL_TABLE INTO WORK_AREA.
"CODE FOR MANIPULATION of WORK_AREA
*write a modify statement to update the RESULT_PACKAGE.
MODIFY RESULT_PACKAGE FROM WORK_AREA TRANSPORTING FIELDS.
ENDLOOP.
hope it helps,
Regards,
Joe

ERROR DURING LOADING DATA FROM PSA TO DSO IN "PRUEFMBKT"

Respected all
I am trying to load data through an r/3 field( pruefmbkt, char-40length) to infoobject. the data is coming correctly to psa but when i am loading it in to dso or infocube request is turning red giving following error message--
Value '010/12.05-112.15/hold on not operate' (hex.
'3031302F31322E30352D3131322E31352F686F6C64206F6E20') of characteristic
PRU_LSIL contains invalid characters
Message no. BRAIN060
Diagnosis
    Only the following standard characters are valid in characteristic
    values by default:
    !"%&''()*,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.+
    Furthermore, characteristic values that only consist of the character #
    or that begin with ! are not valid.
    You are trying to load the invalid characteristic value 1. (hexidecimal
    representation 3031302F31322E30352D3131322E31352F686F6C64206F6E20).
Procedure for System Administration
    Try to change the invalid characters to valid characters.
    If you want values that contain invalid characters to be admitted into
    the system, make the appropriate setting in BW Customizing. Refer to the
    documentation describing the requirements for special characters and the
    possible consequences.
    For more information on the problems involved with valid and invalid
    characters, click here.
kindly give me the solution how to deal with this problem.
thanks
abhay

HI Abhay,
please check if the infoobject corresponding to field PRU_LSIL in BW system has lower case checkbox enabled in the infoobject properties, as the value '010/12.05-112.15/hold on not operate' coming from R/3 has lower case alphabets.
Hope this helps.
Regards,
Umesh.

Error while loading a Cube in BW - "Waiting for Semaphore"

Hello Experts:
I seem to be having a frequent problem while doing a Delta load from BW (3.5) cube to exactly similar cube in BI 7.0.
The load is done daily via a Process Chain. Before doing the Delta load, I also have a step to DELET Index from the
cube in BI. The Delta loads have been successful but frequently they take about 7 or 8 hours to load. The number of
records are not many 80,000 to 140,000 records range. There have been successful loads for similar range withing
7 or 8 minutes. However, when it gets hung up it takes 7 or 8 hours.
Looks like it is a Lock happening in 3.5 BW system. Tcode SM12 shows that it is locked and then in T. Code SM66, it
shows that it is hun for resources..... The message inicated is "Waiting for Semaphore". After about 7 hours, the load
automatically happens.
This is causing issues becuase the upward data loads don't happen and Users can not access the data until late afternoon
for their planning in BPC.
Is there a way this error or Waiting for Semaphore be avoided or time is reduced....? How can I achieve this? Any
fne tuning tricks anyone can suggest please......!!
Thanks a lot in advance.

Thanks to both of you.... ppreciate the feedback. I guess, I will have to wait for the situation to arise again as today's delta went normally. I will see if this happens again. I am not sure whether the Semaphore number is same as the "Work Process Number" in SM66 (which was 3 in my case) or is it the Process ID (which is 22872082 in my case).
If I go to SM50, I shoudl find either the Process ID then.
Would I be searching for the OSS notes corresponding to Process ID (in this case 22872082...? or would it for sempahore number (if it is different .... as I mentioned 3 in my case..?
Could you please clarify which is Semaphore number and if it is same as the process ID I am talking about so that I can search for the right OSS notes.
Also, finding all this will only tell me why it hung.... but is there a way we can make it kick off and not get stuck or I have to wait it out until the resources get released.....? Which in my case then would stil be a wait for 6/7 hours!!
Apreciate your feedback.
Best..... Lee

Invalid character error during load to cube

Similar Messages

Maybe you are looking for