Alpha Conversion Issue

Hi Experts,
where we can place the ALPHA conversion of "Customer Operational Contract" instead of on InfoObject level ?
Please suggest me the other way to put alpha conversion.....

In 7.0 data source, In Convesion Routines column you can input ALPHA and in Format column, you will need to select external.
This should run the alpha converion while loading data from that data source.
But what think is that it would just convert the way data is stored in the system (same with using FM) but in the query, we will have to input the data with appropriate zeros for value selection for that characteristic.
Regards,
Gaurav

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

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

  • Alpha conversion for 0Material

    In 0Material, we had 'ALPHA'  conversion routine. When we run the queries all the leading zeros are truncated .
    We have a issue if a material no in R/3 is like <b>01123</b>. In the query this material is shown as 1123. Users want to see it as 01123.
    If we remove ALPHA conversion routine it shows all the leading Zeros and also in the selection we need to give all the leading Zeros(18 Char).
    Please do advise.
    Thank you,
    PVK

    Dear PVK,
    <b>I tried creating material with number "01123" but system truncates leading zero and gives only 1123 as material code.</b>
    And internally at sap R/3 side there is conversion routine which converts  "1123" into "000000000000001123".
    So i would say that you should keep on the alpha conversion routine at BW side.
    Regards
    Kapadia

  • Enable alpha conversion on infoobject, deletion of data no option

    Hi SDN forum users
    I have this issue where I need to enable / activate alpha conversion on an existing infoobject. The problem is that this infoobject is used in several DSO's and cubes, so many, that deletion of data and reload is not an option (It does not contain Master Data only used as transaction data). Therefore I need to find a solution, that makes activation of alpha conversion possible even though data exits. I have heard about the transaction RMSDEXITON for this, but since we are using version 7.0 this option has been removed.
    So how do you guys see the possiblities for me to enable alpha conversion?

    Hi.....
    U can add the conversion routine for this Infoobject in three ways...
    In the BW side...in the Datasource Level
      In the datasource >> Go to fields tab >> there search the R/3 field which is mapped to that Infoobject in the Transformation >> Then in the Conv.Routine column select the Alpha Conversion Routine and In the Format column select External....
    In the Transformation
    Write a field level routine for that particular field abd call the Alpha conversion routine there...
    In the R/3 side
    In the Customer exit ....Go to SE37 >> EXIT_SAPLRSAP_001 >> Double click on ZXRSAU01 >> search the datasource......write the code there....
    Regards,
    Debjani....

  • Customer Alpha Conversion

    Hi All,
    I have customer ID's being used from sales data(DataSource ), GL data (Attribute of 0PROJECT), Cost for Controlling (Routine which picks the same table of 0PROJECT).
    I have checked this table /bi0/PProject here I see the customers having values such as 00000R1010, 00000R4000 when these should be R1010, and R4000.
    0CUSTOMER is a CHAR 10 Field with ALPHA.
    Customer numbers with just numeric values are correct while customer numbers starting with charecter i.e. (R) is having the problem.
    All suggestions are appreciated.
    Kind Regards
    James

    hi,
    The Alpha conversion will only work for Numeric values, for Alpha numeric values it does not do anything.
    The data in IO 0PROJECT is being loaded from the R/3 system and the values itself are coming with appended zeros in the beginning. You can write the ABAP code in the transformation to 0PROJECT to delete the leading zeros while loading customer values in 0PROJECT.
    SHIFT CUSTOMER LEFT DELETING LEADING '0' .
    This will delete leading zeros and store values in 0PROJECT as R4000
    regards,
    Arvind.
    Edited by: Arvind Tekra on May 4, 2011 7:46 AM

  • Conversion issue in encoding in PI

    Hi,
      I am having a problem in conversion issue for encoding. Let's have a detailed look into the scenario first.
    Scenario: SNC->PI (through Proxy)->MQ (through Receiver JMS adapter)->SeeBeyond (It's a middleware system).
                   Here from SNC, data are coming into PI as in UTF-8 encoding, whereas all the systems shown in the above flow are of ISO 8859_1 format. Hence UTF-8 needs to be converted into ISO 8859_1. PI does this conversion in Receiver JMS adapter. CCSID has been set to 00819 which is for ISO 8859_1 encoding. But the beginning of the xml, it remains still UTF-8, like below:-
      <?xml version="1.0" encoding="utf-8" ?>
    Whereas the content of the xml has already been converted into ISO 8859_1 by Receiver JMS adapter. Now let's see the problem now.
    Problem: After the data been passed in SeeBeyond, the mapping fails in SeeBeyond, since SeeBeyond tries to look at the XML tag from the beginning and it found it's in UTF-8 as per he tag above. Then it tries to map it in UTF-8 format whereas the content is in ISO 8859_1, so mapping fails in SeeBeyond. Please note, here allthe systems except SeeBeyond are just bypassing the data, no mapping been introduced in anywhere in the systems except SeeBeyond.
    Workaround: Is there any other chance where we can change the tag header from UTF-8 to ISO 8859_1 in Receiver JMS adapter itself in PI like this:-
    <?xml version="1.0" encoding="iso 8859_1" ?>
    This might resolve our problem I think. Any suggestions would be appreciated.
    Thanks and Regards
    Soumya

    Hi Stefan,
                Thanks for your reply. I have gone through the link you have specified. Ya, that's the other way to resolve that issue in that case. But here we have asked the receiver system (SeeBeyond) to change the encoding part in their mapping. Because changing the coding part in SeeBeyond is less time consuming than adding a new Bean in JMS adapter. Our problem got resolved by changing the mapping in Receiver end. Thanks anyway for your valuable reply.
    Thanks
    Soumya

  • Umlaut Conversion issue in Sender communication channel SAP PI

    Hi Gurus,
    We are facing issue while conversion.
    umlaut Conversion issue in Sender communication channel that is reason channel not able to pic the file from the path.
    Sender CC error:
    Value of incoming field is too large. Segment:'IMD', Field:'7008', MaxLength:'35', value:'Plssvvkbecher Lübzer 0,4 (1280Stk p' DESCRIPTION: The length of the field value is too big !
    Actually field contains 35 Chars only the value is  : 'Plssvvkbecher Lübzer 0,4 (1280Stk p'
    We tried with “ISO-8859-1” if the field value is less than 35 characters it is able to converting.
    Please help me out from this issue.
    Thank you.
    Regards,
    Jittu.

    Hi Jittu,
    Have you tried using the codepageconversion bean in the modules under the sender?  It would be like:
    AF_Modules/TextCodepageConversionBean with a parameter of Conversion.charset and a value of utf-8.
    Regards,
    Ryan Crosby

  • Language conversion issue in PI7.1

    Hi,
    My sceanrio is file to Idoc. Am facing language conversion issues.
    For example one of the field in the source file is having the value "Différence sur net". And in the IDOC field the value is appearing as "Différence sur net".
    With the same data I have done file to file scenario with and without content conversion and the output is coming correctly as "Différence sur net".
    I have enabled Unicode check box in RFC destination also in XI server. But still its coming "Différence sur net" . Please advice how can I get the target field value same as that of the source field vale.
    Can anyone help me to sort out this issue?
    Thanks.
    Dinesh

    Hi,
    In Channel try with using the File type: text and encoding : UTF-8.
    I think this will solve your issue.
    Thank you,
    Siva

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

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

  • Substitute of alpha conversion routine

    Hi,
    Is there any routine as a substitute for the alpha conversion routine. I am getting problem in alpha conversion and the info object is filled by routine to infocube.
    I cannot overcome the problem by checking in the transfer rule.
    Please provide some input to resolve the problem.
    Thanks and regards,
    V.Satyanathan

    Write your code in start routine to convert it to upper case.
    Thanks
    Nilesh

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

  • 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

Maybe you are looking for