Infoobject Conversion Routine Alpha

Hi All,
At the time of creating infoobjects under General Tab we have option Conversion Routine : Alpha (by default), can anybody put light on that what is that exactly.
Thanks and Regards
Asim.

Hi,
See the following program, and the same logic you can apply in Transfer Rules/Transformations. Take ABAPer help.
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

Similar Messages

  • How to transport InfoObject Conversion Routine

    Hi,
    I am using an existing coversion routine to my InfoObjects, this conversion routine is a custom object which already existed in Dev created by someone and i have just used it for my InfoObjects, now how can i transport this conversion routine to CONS, is it enough if i just transport the INPUT and OUTPUT function module.
    Thanks
    Akila. R

    hi Just go to the transport Connection, select the infoobjet automatically the conversion routines will be associated with it no need of collecting it seperately .
    for example
    ALPHA conversion is used in the BW system for each presetting for character characteristics. The ALPHA conversion routine is registered automatically when a characteristic is created. If you do not want to use this routine, you have to remove it manually.
    The ALPHA conversion routine is used, for example, with account numbers or document numbers.
    For conversions from an internal to an external format (function module CONVERSION_EXIT_ALPHA_OUTPUT) the process is reversed. Blank characters on the left-hand side are omitted from the output.
    CONVERSION_EXIT_ALPHA_OUTPUT ths functional module will be transorted automatically with out your notice
    hope this helps
    santosh
    Edited by: Santhosh Nagaraj on Sep 16, 2009 2:59 PM
    Edited by: Santhosh Nagaraj on Sep 16, 2009 3:00 PM

  • 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

  • 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

  • How to reset Conversion Routine NUMCV in InfoObject

    Dear all,
    In order to test, I deleted the Conversion Routine NUMCV in tab General of an InfoObject. And now I'd like to reset it as NUMCV. A message says: Conversion Routine NUMCV was deleted.
    How can I resolve it?
    Thanks a lot in advance

    Thanks for your answer.
    I've tried to create a new InfoObject, but everytime when I choose "Data type" as NUMC and then choose "Convers. Rout" as "NUMCV", it's said : Conversion Routine NUMCV was deleted.
    Do you have any idea?

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

  • 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

  • Info Object conversion routine

    Hello,
    I have a very simple question.
    I have an infoObject which suppose to save texts. I dont care which kind of text is it. It can be anything.  in the infoObject i removed the conversion routine and didnt put an X in the "lowercase letters" checkbox but still when i load data into the ODS the data cant be activated just because this infoObject have wrong charactaristics.
    Please Advice,
    David

    Hi David,
    allow lowercase letters or check out this one: /people/siegfried.szameitat/blog/2005/07/18/text-infoobjects-part-1
    regards
    Siggi

  • Conversion Routine... plz help

    Dear Gurus,
    There is a text field in R3 called as SGTXT related to some finance table... some of the records in this field directly start with '#' character and then the details.. Well here is the problem.. I m loading to ODS 0FIAR_O04 and it ends up in error due to the above mentioned problem.. the infoobject which carry the data from SGTXT field is 0POSTXT...
    I decided to go for a conversion routive in transfer rule for this field.. but i dont know how to write routines.. can you plz help me with the steps as well as the code to remove '#' from SGTXT.... Thanks.
    For more help i m attaching the conversion routine with is automatically generated by system... only i hv to add code to remove '#' character... kindly go thru it and suggest me where to add and what to add...
    here it is
    PROGRAM CONVERSION_ROUTINE.
    Type pools used by conversion program
    TYPE-POOLS: RS, RSARC, RSARR, SBIWA, RSSM.
    Declaration of transfer structure (selected fields only)
    TYPES: BEGIN OF TRANSFER_STRUCTURE ,
    InfoObject 0POSTXT: CHAR - 000050
    SGTXT(000050) TYPE C,
    END OF TRANSFER_STRUCTURE .
    Global code used by conversion rules
    $$ begin of global - insert your declaration only below this line -
    TABLES: ...
    DATA: ...
    $$ end of global - insert your declaration only before this line -
    FORM COMPUTE_POSTXT
    Compute value of InfoObject 0POSTXT
    in communication structure /BIC/CS0FI_AR_4
    Technical properties:
    field name = POSTXT
    data element = /BI0/OIPOSTXT
    data type = CHAR
    length = 000060
    decimals = 000000
    ABAP type = C
    ABAP length = 000120
    reference field =
    Parameters:
    --> RECORD_NO Record number
    --> TRAN_STRUCTURE Transfer structure
    <-- RESULT Return value of InfoObject
    <-> G_T_ERRORLOG Error log
    <-- RETURNCODE Return code (to skip one record)
    <-- ABORT Abort code (to skip whole data package)
    FORM COMPUTE_POSTXT
    USING RECORD_NO LIKE SY-TABIX
    TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
    G_S_MINFO TYPE RSSM_S_MINFO
    CHANGING RESULT TYPE /BI0/OIPOSTXT
    G_T_ERRORLOG TYPE rssm_t_errorlog_int
    RETURNCODE LIKE SY-SUBRC
    ABORT LIKE SY-SUBRC. "set ABORT 0 to cancel datapackage
    $$ begin of routine - insert your code only below this line -
    DATA: l_s_errorlog TYPE rssm_s_errorlog_int.
    RESULT = .
    returncode 0 means skip this record
    RETURNCODE = 0.
    abort 0 means skip whole data package !!!
    ABORT = 0.
    $$ end of routine - insert your code only before this line -
    ENDFORM.
    FORM INVERT_POSTXT
    Inversion of selection criteria for InfoObject 0POSTXT
    This subroutine needs to be implemented only for SAP RemoteCubes
    (for better performance) and for the Report/Report Interface
    (drill through).
    --> I_RT_CHAVL_CS Ranges table for current InfoObject
    --> I_THX_SELECTION_CS Selection criteria for all other InfoObjects
    <-- C_T_SELECTION Selection criteria for fields of
    transfer structure
    <-- E_EXACT Flag: Inversion was exact
    FORM INVERT_POSTXT
    USING I_RT_CHAVL_CS TYPE RSARC_RT_CHAVL
    I_THX_SELECTION_CS TYPE RSARC_THX_SELCS
    CHANGING C_T_SELECTION TYPE SBIWA_T_SELECT
    E_EXACT TYPE RS_BOOL.
    $$ begin of inverse routine - insert your code only below this line-
    DATA:
    L_S_SELECTION LIKE LINE OF C_T_SELECTION.
    An empty selection means all values
    CLEAR C_T_SELECTION.
    L_S_SELECTION-FIELDNM = 'SGTXT'.
    Selection of all values may be not exact
    E_EXACT = RS_C_FALSE.
    $$ end of inverse routine - insert your code only before this line -
    ENDFORM.

    It has been solved.. thanks everyone for inputs.. points awarded to concerened.. thanks.

  • How to remove conversion routine "ABPSN"

    Dear gurus,
      In my transfer rules, under the tab "DataSource/Trans. Structure", I have a field PSPID whose "Conversion Routine" has the value "ABPSN". This conversion routine converts the external format to the SAP format which, however, is not what I want. I want to remain the original format so I need to remove this "ABPSN" conversion routine. When I double clicked it, it linked to the InfoObject 0PROJECT maintanace screen. On that screen, I removed the conversion routine "PROJ" for 0PROJECT, but still ABPSN remains and the data loaded into the InfoCube have been converted.
       So how can I remove this ABPSN convertion routine?
      Thanks in advance.
      Jin Ming

    Hi Jin Ming,
    Conversion Exit ABSPN is related to WBS element and not project at R/3 side.
    But at BW side this routine internally calls Project routine .
    The Process is,
    1. Delete all transactional data , from related ODS & Cube wherever 0PRoject is used .
    2. Delete master data from 0Project.
    3. Change object 0Project remove the conversion using Tcode RSD1.
    4. Load master data for 0Project.
    5. Load transaction data.
    Hope that helps.
    Regards
    Mr Kapadia

  • How to "Custom conversion routine" in BW

    Hi team,
    The R3 table level field has converion routine which stores the value as "A" .
    When you display this in application (or) using ALV, it shows as "AB". There are custom function modules behind this conversion routine.
    In BW, when we extract until PSA, we are getting "A".
    I see the option at Info object level to write" conversion routine" but how and where to start this conversion routine in BW.
    In BW, we want to show "AB"
    Thanks
    Angelo

    Hi,
    this problem is solved in transformation PSA to InfoObject using formula or routine.
    Regards,
    Conrado
    www.forosap.com
    Spanish SAP Forum Administrator
    Edited by: Conrado Linquet on Mar 29, 2010 5:54 PM

  • Conversion Routine problem

    Hi,
    In one of the info object there is a conversion routine. So, when the query is executed in BeX Query Analyzer the result is comming correct i.e. if in the database the value of info object is 0001234 then at display it is coming as 1234.
    However, in case if its value is "STEP" in database , at output "Not Assigned" is comming. Dont know what is happening. If anybody already encouter this problem please help.

    Hi,
    It is not in the hierarchy.
    I am using alpha routine so as to remove the leading zeros at the time of display.
    There are two info objects, both are same, the only difference between them is one info object is having alpha routine and another one is without it.
    The one info object without any routine is displaying values correctly but the another one with aplha routine is displaying 00123 as 123 but also displaying STEP as Not Assigned.
    Edited by: megamin79 on Feb 9, 2012 7:43 PM

  • What is meant by matn1 conversion routine in info object

    hi,
    Can i know the exact meaning and usage of matn1 (type of conversion routine) in the infoobject level.
    thanks in advance

    Hi Sankar,
    Conversion takes place when converting the contents of a screen field from display format to SAP-internal format and vice versa and when outputting with the ABAP statement WRITE, depending on the data type of the field.
    Check the info here:
    http://help.sap.com/saphelp_nw04/helpdata/en/2b/e9a20d3347b340946c32331c96a64e/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/07/6de91f463a9b47b1fedb5be18699e7/content.htm
    Hope this helps...

  • Conversion routine to remove leading zeros from nonnumeric values.

    Hi,
    Can anybody tell me any conversion routine while can remove leading zeros from a character value.
    Eg : 
    input : asdfe
            output : 0000asdfe and vice versa
    I tried with Alpha conversion routine but that is useful only with numeric values.
    Please help.
    Regards,
    Deepti Jain.

    Hi,
    See the following program, and the same logic you can apply in Transfer Rules/Transformations. Take ABAPer help.
    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

  • PRODU Conversion Routine

    Hi Experts,
    We are loading data from APO to BW. However, the Material length in APO is 40 with PRODU conversion routine. In BW, the Material length is 18 with ALPHA conversion routine.
    During data loading, if the value is '000000000000000000000000000000000001' in APO, it will display as '0000000000000000' in BW. Please advise on how to correct this. Thank you.

    HI
    first check in SPRO.. settings configures. 4.3.Specify Output Format of Product Number
    IMG >  Advanced Planning & Optimization>Master Data>Product> Specify Output Format of Product Number.
    For example: 
    Product Number with Leading Zeros:  000000001234 (zeros up to defined length of product number)
    Product Number without Leading Zeros:  1234 (leading zeros removed from product number)
    Following the menu path or transaction code above:
    u2022     Uncheck the u201Cleading zerosu201D box and save the setting.
    thx
    vijju

Maybe you are looking for

  • JavaDoc documentation for new BC4J UI classes

    Hi All I could not find JavaDoc documentation for new UI packages ( oracle.jbo.uicli.*** ) in JDeveloper 9i RC. Does anybody have an idea where can I find them? Regards, Shota

  • Hi I'm new to java

    Hi, When i tried to run the Servlet it is showing the following warning: "serializable class ProfileServlet doesn't declare a static final serialversionUID field of type long" ProfileServlet.java package flowers; import java.io.IOException; import ja

  • Vista 64- Ipod touch won't sync

    downloaded the 64 bit itunes off of IEx64 and it still won't work. The Apple mobile service is there, I tried stopping/starting it and it still won't sync. When i plug it in now it reads it as "Digital Still Camera" what do i do?

  • Mac Pro Suggish

    Hi I have a Mac Pro and a Mac Book. The Mac Pro is 5 months old. The Mac Book is about 3 months old. The Mac Pro is crashing constantly and the Mac Book is perfect. Issues with the Mac Pro: 1. Firefox can't hack it any more.Keeps 'unexpectedly quitti

  • N73ME FW 4.0736.3.2.1 thread removed from here...

    OH YEAH!!! n73ME FW 4.0736.3.2.1 thread removed What reason? what basis? why? Honestly, it makes me wonder.. Right now all I can say is "inappropriate language"!!!!! ALot of inappropriate langauge.. All the colors and letter cases and everyeverything