ALPHA conversion error in Crystal and MDXTEST

Hello Experts,
I've a BW query which is running fine without errors But when a cross tab report is created in Crystal, we get the below error upon execution:
"Characteristic value xxx of Characteristic ZXX is not ALPHA converted"
The same error when run in MDXTEST.
The InfoObject ZPRFTCTR and all its nav attribs has got ALPHA conversion enabled. Also, I am doing alpha conv in my expert routine of this infoobject.
RSRV checks show no errors.
No error while accessing data from cubes in BW.
This error is only in Q and P not in D.
I've re-activated Infoobject and transformation and transported to Q then reloaded the master data but still the same error.
Have you guys faced this issue before? What could be causing this error. Please help.

Hi,
as this error also shows up in transaction MDXTEST it clearly indicates that the issue is already happening in the BW stack without the involvement from the SAP BusinessObjects tools.
I would suggest you post your question into the SAP BW Forum.
regards
Ingo Hilgefort

Similar Messages

Alpha conversion error

Hi experts,
We have an error coming for the field as 0ref_doc_no as alpha conversion error. We are in BI 7 .Transformations we are using.
How to rectify this error ?
Regards,
Bhadri M.

Hi,
Maintain select the alpha conversion ... We need to find a cause and need to rectify in the source, ...
First of all, the BI system throws the error for special characters
Go through the below links
http://help.sap.com/saphelp_nw04/helpdata/en/9b/f9c18f5a07f0459127e9676ae22a54/frameset.htm
http://sathya-sapbw.blogspot.com/2007/10/faq-alpha-conversion.html
http://fuller.mit.edu/SAPDocs/conversion_exits_in.htm
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/7108a690-0201-0010-4cbc-9bca94f9ad9c
Regards,
Marasa.

Alpha Conversion

Hi All,
When scheduling loads in one of the Info objects in Quality, i am getting this error:
InfoObject /BIC/ZITM does not contain alpha-conforming value 90952
I get this error for some other records of the same IO. I checked in our development system in the Transfer structure for'Alpha-Conversion routine' check box of the same Info object. It is unchecked. But, we didn't face any errors while scheduling loads in development.
In the info object's definiton, entry 'Alpha' appears in the conversion routine field in both Dev. and Quality.
What is the reaon for the error durimg loads in Quality?
Thanks.

Hi Roberto,
The Info object ZITM is an attribute of 0Customer.ZITM is not checked for Alpha Conversion in the transfer structure of '0Customer_Attr' in the Development system. There is no problem when loading Customer.
In Quality, though the Transfer structure appears the same, i do get 'Alpha Conversion' error for ZITM when scheduling loads into Customer.
Thanks.

Why does alpha conversion not work?

Hi guys,
I have an alpha conversion in an infoObjekt, and this infoObjekt is used in one inforsource, and I have set the check box "conversion" in the transfer rule, but the alpha conversion didn't work.
But when I call 'CONVERSION_EXIT_ALPHA_INPUT' in this field routine, it works...
I can not figur out the reason, please help me.
Any hint is apprreciated.
Regards

hi,
Did you mention conversion Rout as Alpha in the INfoobject.
RSD1 - General - Conversion Rout as Alpha
or you Use the following code at transfer routine to convert using ALPHA.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = trans_structure-<Source field>
IMPORTING
OUTPUT = RESULT.

Error in ALPHA conversion while loading hierarchies

Hi,
I got the following error while loading hierarchies:
<i>Error in ALPHA conversion in NodeId00000088 for InfoObject 0PROFIT_CTR
Message no. RH224
Diagnosis
The technical node name for node id 00000088 is not consistent for conversion exit ALPHA, which is stored with InfoObject 0PROFIT_CTR.
Possible reasons for the error:
The original consistent value returned by the DataSource was changed by a conversion routine to a non-consistent conversion exit value.
The DataSource returns a value that is not consistent in the conversion exit.
System response
Loading the hierarchy was terminated.
Procedure
Check whether the correct conversion exit was entered for the InfoObject. If necessary, change the conversion exit, conversion routine or the data to be extracted.
A further option is to activate automatic conversion in the transfer rules. Here, the system executes the conversion exit, making sure that the data is in the correct format.</i>
If it is not hierarchies, we fix this error by prefixing the zeros (as we are working on Qbox we wont change the transfer rules to select the conversion routine) but here there is no PSA, the data is coming from ALE. Based on this please suggest me to how to fix this error?
Points will be given for any helpful suggestion

Ganesh,
Can you please check out the Alpha Conversion Routine and also nodeid for that infoobject..
There might be some inconsistencies in the code..
Hope it helps
Gattu

Error in ALPHA conversion

Hi experts,
I am loading a hierarchy for a infoobject. When I execute the infopackage, the monitor show me the next error: Error in ALPHA conversion in NodeId00000009 for Infoobjetc 0CUSTOMER. Can anybody hepl me?

Hi,
Go to the transfer rules and check the Conversion checkbox for the info-object 0CUSTOMER. Retry the load. Hopefully it should go through.
Bye
Dinesh

Documents remain in GenWWW status and conversion error message says success

Hi,
I have instaled UCM 11.1.1.4 and the situation is that documents remains in GenWWW status, the
conversion error message says success . In Ibr logs says everything went perfect, in UCM logs isn't recorded any error.
Anyone have a clue to solve this problem?
Update:
When runnig IdcAnalyse appears the following error:
./IdcAnalyze -filesystem
FileSystemFileStore:1.0.0.0 started.
Content Management System Server. Version 11gR1-11.1.1.4.0-idcprod1-101229T001824
Copyright (C) 1996-2011, Oracle and/or its affiliates. All rights reserved.
Analyzing filesystem...
.....................Error checking filesystem: Unable to locate extension for rendition flag 'L'.
Is this error related with the documents remain in GenWWW?
Thanks
Edited by: carlos.pereira on Jul 26, 2011 4:58 PM
Edited by: carlos.pereira on Jul 26, 2011 5:00 PM

Usually this issue is seen when the IBR's cannot keep up with the load and after a defined amount of time, the refineryjobs entries are cleared while the IBR's might still hold this content item.
If you do what Srinath proposes the refinery jobs is cleared as well as the queues on the IBR. This will not fix the issue with the documents in GenWWW, but it will make the way clear for (new) documents to be (Re-)submitted for conversion. IdcAnalyze should then be able to create a IdcCommand file with resubmit_for_conversion calls for all the documents in GenWWW state. Running this IdcCommand file should then convert all the documents that were "stuck" in GenWWW.

Unable to convert pdf to any other format. Tried cloud as well as acrobat reader. Reader error message "unable to contact service" and Cloud message "conversion error". I tried multiple pdf documents and checked security settings on all of them. Help Plea

nable to convert pdf to any other format. Tried cloud as well as acrobat reader. Reader error message "unable to contact service" and Cloud message "conversion error". I tried multiple pdf documents and checked security settings on all of them. Help Please!

Hi skydivingsnowman,
I'm sorry you're having such trouble using the ExportPDF service. What browser are you using?
Please try clearing your browser cache, or using a different browser (here's a list of supported browsers: http://www.adobe.com/acom/systemreqs/.
Please let me know if that works.
Best,
Sara

JHS and JSF Validation Conversion Error Customizations

Hello
Have JHS done any work about JSF validation or conversion error customizations?
I mean the error messages such as "lablename:"value mus be entered etc.
What can i do if i want to globally customize and localize this error messages.
I have copied the key such as "javax.faces.component.UIInput.REQUIRED" in my appdeff resource bundle but JHS (or maybe ADF) gives own message yet.
I Apologize if my problem don't depend on JHS. I wonder that JHS overrided JSF default messages.
Thank You

JHeadstart does not use any JSF standard message.
JHeadstart uses ADF Faces which comes with its own bundle of error messages.
Please use the JDeveloper forum for instructions on modifying ADF Faces error messages.
Steven Davelaar,
JHeadstart Team.

Casting and radio select : conversion error

I'd like to display radio options differently, regarding of their type.
For example I have an OpenOption class which extends Option. So when I display it I'd like to add an input text box if the user select an open option :
                         <h:selectOneRadio value="#{q.answer}">
                             <s:selectItems value="#{q.target.options}" var="opt" label="#{opt.text}" />
                             <a:support event="onchange" reRender="pnlOpenText"/>
                         </h:selectOneRadio>
                         <a:outputPanel id="pnlOpenText">
                                 <h:panelGroup id="innerPnlOpenText" rendered="#{q.answer.class.simpleName eq 'OpenOption'}">
                                   <h:outputText value="#{q.answer.freeTextLabel}"/> 
                                   <h:inputText value="#{q.freeText}" size="50"/>                                   </h:panelGroup>
                         </a:outputPanel>I use the following EL expression to test the type of the selected option :
#{q.answer.class.simpleName eq 'OpenOption'}It works well BUT if I select the open option and refresh the page, the RadioRenderer fail when trying to convert ALL the options into OpenOption :
Cannot convert Option[ id=null, text=Q1, rank=0 ] of type class Option to class OpenOptionFor the time being I see only one solution : put a type attribute in my Option class ... I believe this is not the best design.
Is there any other workaround ?
Would it be possible to have a renderer which doesnt infer the options type from the selected option but individually for each option ? I don't know anything about the spec ...
Thanks,
Bruno

Java is case sensitive language after all , plus beans getters and setters naming rules :)
SetConfirmClaim
must be
setConfirmClaim
It raises a question though whether more exact error reporting is achievable , not just "Conversion error has occured".

Language conversion error

Dear all,
We have imported data from SAP R/3 to BW. The problem we are getting is language. In R/3 they(key users) have mentioned customer name in both English,special characters and chinese. When I use ALPHA conversion routine, its giving error. What I should do to solve this issue?
thanks in advance.
Nagesh Aswartha

Dear Aswartha,
I guess, you should know about Unicode for this scenario.
chk:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b8d163a7-0301-0010-d9b0-98f692ea3c60
http://www.idi.ntnu.no/~jag/Publications/emrps99.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ee7407a0-0501-0010-81ae-e329029b1074
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5411d290-0201-0010-b49b-a6145fb16d15
Thanks,
Raj

Dont want ALPHA conversion

Hi All,
According to our requiremetn we dont want Alpha conversion. So i have removed check box in the info object definition. And also i did not use any conversion logic(usning Exit_conversion_alpha_input) in the transfer rules.
But while loading i am getting an error <<info object>> does not contain alpha confirming value 028.
and if i use alpha conversion there is no error but the value would 0000028, in which our customer is not interested. How to avoid this error??
Is there any other way to solve this problem with out using conversion exit.
Regards,
Ravi

Hi....
The ALPHA routine converts purely numeric user input like '4711' into '004711' (assuming that the characteristic value is 6 characters long). If a value is not purely numeric like '4711A' it is left unchanged............
I think values are found that do not have the correct internal format........
Due to this you are facing this issue.....Check the field length of the value for which you are facing this issue.......
Regards,
Debjani.......

InfoObject - Alpha Conversion

We have a custom InfoObject INNUM (Invoice Number) in BW 3.0B. It is defined as CHAR 10. Many of our customers send invoice numbers with leading zeros. We need to store and retrieve these invoice numbers as sent.
Unique invoice numbers are as follows:
123
00123
0000123
I have tried 2 options:
With Alpha Conversion the numbers are padded with leading zeros to length 10. They can then be retrieved and displayed as 123, without any leading zeros.
Without Alpha Conversion the numbers are padded with leading zeros to length 10 but can only be retrieved by searching with all leading zeros in the search string (0000000123).
Is the Alpha Conversion functioning as advertised? Is there a way to store, retrieve, and report on the invoice numbers as sent by our suppliers without adding leading zeros?
Best regards,
Mike

It depends on the realeases: in fact to Upgrade to 3.x it was NECESSARY to carry out a massive ALPHA Conversion (so as to remore previous conversion errors). A BW installation born in 3.x (not Upgraded from 2.x) could still have some APLHA problem.
With Aplha it seems to work right (from what you say), without NO! Without Alpha if you store the follwing values:
123
00123
0000123
each of them sholud be retrieved ONLY with the necessary leading zeros (so 123, 00123, 0000123) ... You say that "can only be retrieved by searching with all leading zeros in the search string (0000000123)": this is unusual. In fact if you store 123 on a CHAR 10 InfoObject you will see in S Table /BIC/SINNUM the same value "123" and NOT "0000000123". When attempting with NO Alpha Conversion did you deleted the InfoObjects value?
Hop it helps
GFV

Alpha conversions in BW7

Hello all,
I found out that transaction for alpha conversion became obsolete in BW 7.0. You can observe this while you try to run TA RSMDCNVEXIT or RSMDEXITON in BW 7.0 SP10+ system is raising following error:
Data conversion functions are no longer supported Message no. RSMD001
Since I briefly searched on OSS and I'm not successful to find any relevant note I would like to ask here how Data conversion are handled in BW7. Somebody has any clue?
PS. Note that I'm running on Unicode system.
Thanks
m./

Hi Martin,
Since some objects of the new data flow in BI 7.0, for example BIA, are not covered by RSMDCNVEXIT it has been set to obsolete. You should not use it anymore.
As an alternative to solve your problem, if you would like to switch on a certain customer exit, you have to delete the data, switch on the customer data, and reload the data.
For further information regarding to Customer exit please check the below links:
Customer Exits
   http://help.sap.com/erp2005_ehp_04/helpdata/EN/f1/0a56f5e09411d2acb90000e829fbfe/frameset.htm
Creating Free Characteristics and Characteristic Values
   http://help.sap.com/erp2005_ehp_04/helpdata/EN/cd/6a5378051a11d2a5700000e8407c05/frameset.htm
Selecting Characteristics and Storing Characteristic Values
   http://help.sap.com/erp2005_ehp_04/helpdata/EN/c1/376a58449a11d188fe0000e8322f96/frameset.htm
Rgds,
Colum
Edited by: Colum Cronin on Jul 7, 2009 4:01 PM

ALPHA Conversion Exit Problem

Hi,
I have an InfoObject ZPRODUCT1 with ALPHA Conversion Exit in RSD1 definition.In the Infosource and in the DataSource/Trans. Structure TAB when i check for the corresponding field it has some other Conversion exit called 'PRID1' and i couldn't change it.
When i load the data i get the error at the PSA level itself and the message is,
InfoObject /BIC/ZPRODUCT1 does not contain alpa-conforming value 80001909.
How to fix this problem?
Thank you
arun

Thanks,
I already did that and it worked properly.
Can you explain how come the conversion exit in Data source transfer structure and the InfoObject can be different?How did this worked?
Will i be able to modify the Conversion exit assignment in the infoobject or Data Source/Trans. Structure TAB? How do i do this, it looks display only in RSD1?
Thank you
arun

ALPHA conversion error in Crystal and MDXTEST

Similar Messages

Maybe you are looking for