Alpha Conv Routine - IMP

Hi all
I am creating a custom ODS in which i had to use many standard infoobjects
like 0vendor , 0deliv_num etc . for each of these , i get a 'non alpha conforming' value
error during data load . for now ,i have introduced the following code (**) in the transfer rules for
each of these infoobjects . I understand that this will convert a vendor value of '7788' to '0000007788'.
We are fetching the data from a new R/3 custom table . Just wanted to know , if it is a good idea
to populate the table with '0000007788' rather than'7788' in the first place ( rather than
using the code in BW transfer rules ) .
Since this is my first implementation , i am not sure how people usually handle this .
Also , Is it always a good idea to have a conversion routine in all Custom/Z InfoObjects
that we create ??
Pls suggest !
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = RESULT
IMPORTING
OUTPUT = RESULT

Hi,
Yes it is the good practice to use this ALPHA conversion routine.
1.  It will help to avoid non alpha conforming value' error. Data in source system may not be consistent. So it is better to use routine.
2. Routines add leading zeroes (according to field length) to the value. It avoids duplication of the values.  Source system may have values like 07788 , 007788 and 7788.
Hope it helps.
Regards,
Aditya

Similar Messages

  • 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

  • Removing Alpha conversion routine

    Hi All,
    We have an object which was created with alpha conversion routine and master data is alredy loaded to the same.
    Will there be an impact if we remove the alpha routine from the object now. Will this cause any data inconsistency?
    Thanks
    Jeevitha

    Hi,
    Check with the following programand implement it in TransferRules/Transformations.
    REPORT  ZALPHA_INPUT.
    DATA: ZI(18) TYPE C,
          ZO(12) TYPE C.
    DATA: ZS(12) TYPE C,
          ZR(18) TYPE C.
          ZI = '000000099999889925'.
          ZS = '099999889925'.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
        EXPORTING
          INPUT         = ZI
       IMPORTING
         OUTPUT        = ZO.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
        EXPORTING
          INPUT         = ZS
       IMPORTING
         OUTPUT        =  ZR  .
    Write:/   ZI.
    Write:/   ZO.
    Write:/   ZS.
    Write:/   ZR.
    Thanks
    Reddy

  • Conv Routin in DataSource

    Gurus,
    This is the generic DataSource created in R/3, and replicated into BW.  In RSA1, I double-click on the DataSource. In the Field tab, I can see the list of fields used by this DataSource. However, I noticed that the Conversion Routine exist for the field PROID in this DataSource, under Column SS Conv. Rout. In the F1, it says:
    Conversion Routine in Source System (Outside of BW)
    Why the conversion routing is assigned to this field? What does this mean? How can I remove this?
    Please help.

    not answer

  • Alpha-convers. in BW but no leading zeros from source system

    Hello all,
    I want to load customer data via XML. The data are delivered via XI every night in a delta-queue in BW. From the delta-queue the data gets loaded into an ODS.
    From the source system I get the customer number with 6 characters, but in BW I have a alpha conves.Routine in the InfoObject 0SOLD_TO and 0CUSTOMER.
    How can I fill in leading zeros to the values? Do I have to do this in the InfoSource setting or in the update rule?
    Any ideas would be great.
    Thanks upfront and Best regards,
    Stefanos from Munich/Germany

    Hi,
    Try checking the option in the transfer rules. Aganist the Info Object 0Customer you'll have to scroll to right then you can see the check box called conversion . Check that & try loading the data.
    Other than this you'll have to go with the routine.
    Regards,
    SB

  • InfoObject not appearing in Formula Builder

    <b><i>I have an active set of ODS update rules, and am trying to use formula builder to "RIGHT 8" the values of one of the source fields. For example, my field is packed with 00000000CUSTNAME, and I want to trim right 8 to CUSTNAME.
    However, when I look at the available fields in the left-hand selection table, all I can see are system fields, and nothing from my transfer structure. How can I actually manipulate my source field if I can't input it into the expression? How do I get the source fields to appear as candidates for manipulation in the formula builder expression? I can find nothing on this issue from help.sap.com itself. Thanks, Doug</i></b>

    Hi Doug,
    Was the update rule created based on the Infosource then you should be able to find it in the formula section. Also if you want your Cust name to appear without the trailing zeroes then you dont need the formula as SAP would take care of it if you have the alpha conv routine checked for custname.
    Bye
    Dinesh

  • Leading zeros in report.

    Hi,
    I have got a char Tracking number of type numc . I have loaded the data using alpha conv routine. So when i look at cube content my char is showing leading zeroes for the values. but in reports I am not able to see leading zeroes. what setting needs to be done and wher should I do it to obtain values with leading zeroes in report??
    thanks in advance.

    Interesting Issue...
    Jst in case are you looking at the same data/same selections ?
    Any Coding/VBA used to suppress zeroes ?

  • Issue activating and object with ALPHA routine

    Hi Experts,
    yesterday we had a problem with the infoobject 0CUSTOMER. Accidentally, we deleted the ALPHA routine conversion and now the object can't be activated with the ALPHA routine conversion again because the object is in use in some infoproviders.
    We cannot delete infoprovider's data, and we need to activate again the ALPHA routine.
    We are using BW 3.5
    Can somebody help us please?
    Thanks in advance,
    Muhammad

    Hi Muhammad,
    I dont think you will be able to add the alpha conversion routine back in the master data object without deleting data from all infoproviders where 0CUSTOMER object is used.
    Addition of any attribute to master data object doesnot cause any issue however deletion of any attribute or conversion routine, where master data has been already loaded and used in other infoproviders (remember referential integrity) requires one to delete the data from all infoproviders where it is used.
    As rightly suggested by Vikram you can try to achieve what the alpha conversion routine does by writing a transfer routine.
    Best Regards,
    Sameer

  • Give me details about  conversion  routine like alpha

    give me details about  conversion  routine like alpha  and how many conversion routines are ther and their uses  give detail

    Hi Deba,
    There are many Conversion routines...
    ALPHA Conversion Routine
    BUCAT Conversion Routine
    EAN11 Conversion Routine
    GJAHR Conversion Routine
    ISOLA Conversion Routine
    MATN1 Conversion Routine
    NUMCV Conversion Routine
    PERI5 Conversion Routine
    PERI6 Conversion Routine
    PERI7 Conversion Routine
    POSID Conversion Routine
    PROJ Conversion Routine
    REQID Conversion Routine
    IDATE Conversion Routine
    Conversion Routine RSDAT
    SDATE Conversion Routine
    WBSEL Conversion Routine
    Check this link for conversion routines and its types...
    http://help.sap.com/saphelp_nw04s/helpdata/en/2b/e9a20d3347b340946c32331c96a64e/frameset.htm
    Hope this helps u...
    Regards,
    KK.

  • What are the commonly used conversion routines apart from alpha conversion?

    hi all,
    Can any one let me know the commonly used conversion routines apart from alpha conversion routines ?
    thanxs ina dvance
    hari

    Hari
    There are lot of conversion routines, like
    BUCAT Conversion Routine. eg. The BUCAT conversion routine converts the internal presentation of the budget type
    (0BUD_CAT) into the external presentation (0BUD_CAT_EX), using the active entries in the
    master data table for the budget type InfoObject (0BUD_CAT).
    see the link below for all the routines.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b9119290-0201-0010-69af-96fe3bf00243
    assign points if helpful
    Kalyan

  • 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

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

  • Error: InfoObject does not contain alpha-conforming value 20030729

    Hi everyone,
    I got this problem, that i tried to fix yesterday, but all i did was that i got realy frustrated...
    I created an infoobject which is copy of 0DOC_NUMBER and has alpha coversion routine.
    Mapping field in DataSource is also type character 10(VBELN) as my infoobject.
    But there are some values in this field that i am trying to load, less then 10 characters long (20030729,20051116...) and shouldn't be there, because the values are dates and not document numbers.
    But anyway on R/3 side this values are in field which is defined as character 10 (VBELN), and when I am trying to load Infopackage(17500 records) I get 52 errors: InfoObject does not contain alpha-conforming value 20030729.
    I don't get it, since both fields are type character 10 and the values are only digits, why do I get this error message and how can I fix it?
    PS:One solution is to remove alpha conversion routine from infoobject, but i don't want that.
    Regards,
    Uroš

    hi,
    sorry... correction, it's 'Exclusive attributes' that cannot be used for navigational attribute, you can set lower case to differentiate ... check the impact of lower case setting here ...
    http://help.sap.com/saphelp_bw33/helpdata/en/b7/f470375fbf307ee10000009b38f8cf/frameset.htm
    Lowercase letters allowed / not allowed
    If this indicator is set, the system differentiates between lowercase letters and capital letters when you use a screen template to input values. If this indicator is not set, the system converts all the letters into capital letters when you use a screen template to input values.
    If you choose to allow the use of lowercase letters, you must be aware of what happens when you input variables:
    If you want to use the characteristic in variables, the system is only able to find the values for the characteristic if the lowercase letters and the capital letters are typed in accurately on the input screen for variables. If, on the other hand, you do not allow the use of lowercase letters, any characters that you type onto the input screen, are converted automatically into capital letters.
    Exclusive attributes:
    If you select Exclusively Attributes, the created characteristic can be used only as a display attribute for another characteristic, and not as a dedicated characteristic in the InfoCube. Furthermore, you then cannot transfer the characteristic into InfoCubes. However, you can use it in ODS objects or InfoSets.

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

  • 0material alpha conversion in BEx query

    Folks,
    I want to ALPHA convert the material number during BEx query execution.  Once the query is executed, I should see the ALPHA converted number.  Please advise. 
    Thanks.

    Hi,
    can you please give an example of what you want to achieve? 0MATERIAL has already MATN1 as conversion exit....
    Achieving this in BEx during query runtime could be quite tricky...
    Alternatives would be
    - adding a nav attribute to 0MATERIAL like ZMAT_ALPHA and load it with the ALPHA conv exit
    - virtual charateristic
    - changing the displayed values in VisualBasic or in the WebTemplate
    hope this helps....
    Olivier.

Maybe you are looking for