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.

Similar Messages

  • 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

  • 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.

  • 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

  • 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

  • Material Conversion Error

    Hi gurus,
    i have executed a query and i have tried to drill on material then i got an error saying that
    internal system error....BMG135
    which says material conversion settings not found...
    how to solve this error and fix so that i can see the material in my report.
    thanks
    Neel

    Hi,
    take a look
    0MATERIAL conversion exit
    execute report (transaction se38) RSCC_V_TMCNV helps.
    Set the length of 0MATERIAL and change conversion to alpha:
    Re: Error Installing 0MATERIAL from Business Content
    oss note 555675
    Solution
    Make the settings for the material number conversion.
    In BW Release 2.1C, the settings are maintained for the material number conversion via report RSCC_V_TMCNV.
    As of BW Release 3.0A, the settings are maintained for the material number conversion via transaction OMSL.
    Select the same settings as the settings made in the OLTP system.
    Note that you must also perform the setting in client 000 if the error occurred while you were importing a transport request.
    hope this helps.
    Go to transaction OMSL in BW and set the length of material number same as that in transaction OMSL in R/3, should resolve the problem.
    hope it helps
    Regards,
    San!
    Message was edited by: San!

  • Does Alpha Conversion work in new Release(SP14-16)?

    Hi guys,
    we have problem with Alpha conversion:
    we have an InfoObjekt, which includes an alpha conversion, but error occur with data loading in BI, when we have data value like "123", it can not be converted to "000123". Instead that, an error occurs and the data can not be loaded, we have to manuell change this value and then load...
    Is this because of new release (we have this new release since Feburar 2008)?
    Any hint is appriciated.
    Regards,
    Liying

    Yes, it does work still.
    Make sure that in the infosource (transfer rule), that the conversion flag is set for the infoObject.
    matt

  • Alpha Conversion  in node 00000010 for info object 0COSTCENTER

    Hi Masters,
    I am getting the problem in process chain hirachies. Info Object 0COSTCENETER  hier loading the data through process chain sucessfulyy completeed, when saving that hieracies process chain i am getting the error . the  problem is " Alpha conversion in node 00000010 for info object 0COSTCENTER".
    please give me some solutions
    thanks in advance.....
    kk

    kk,
    You can solve by writing an alpha conversion routine in the transfer rules for that infoobject and then load the data.
    DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        INPUT         = TRAN_STRUCTURE-0COSTCENTER
      IMPORTING
       OUTPUT        =  RESULT.
    returncode <> 0 means skip this record
      RETURNCODE = 0.
    abort <> 0 means skip whole data package !!!
      ABORT = 0.

  • Alpha convertion error

    hi,
        when montoring info package i faced some problem  it gives error message
    "Record 6 :InfoObject /BIC/ZA2SRNUM does not contain alpa-conforming value 999 "
    how to solve this problem
    crm field is ZZSERIAL_NO   type char     lengh    20
    bw field is  ZA2SRNUM                char     lengh     20(not alpha converion)(i defined like this)
    can u give me the solution
    thanksjyothi

    Jyothi,
        You have to write an alpha conversion routine in transfer rules for this. it will solve your issue.
    You can use the below code directly in transfer rules i.e ABAP routine at IO level in transfer rules...
    DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        INPUT         = TRAN_STRUCTURE-ZA2SRNUM
    IMPORTING
       OUTPUT        =  RESULT.
    returncode <> 0 means skip this record
      RETURNCODE = 0.
    abort <> 0 means skip whole data package !!!
      ABORT = 0.

  • Alpha conversion in 0customer

    Hi experts,
    In my development system alpha conversion routine is deleted from 0customer.
    Now I am trying to put it again but system given me follwing errors.
    Follwing tables still contains data.
    /BI0/PCUSTOMER
    /BI0/SCUSTOMER
    /BI0/TCUSTOMER
    I also tried to reinstall the 0customer business content but it is not sucessfull.
    Can u please help me on this ... it is very urgent.
    Regards,
    MVS

    Hi,
    this is a BAD recommendation!
    If the system cannot delete this master it is most probably because it is still used in cubes/ods or as attribute of another IObj;
    please check your master data deletion log by calling SLG1 with RSDMD and MD_DEL; you'll see in which IObjs your master data IDs are used; you will have first to delete the data is those objects before being able to delete 0CUSTOMER master data;
    performing an SE14 will create an inconsistency in your system
    hope this helps...
    Olivier.

Maybe you are looking for