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

Similar Messages

  • Info object transfer routine

    Hi,
    i had infoobject ZEBAY01 and need to write global transfer routine for this infoobject. Now the infoobject value is comming 0000999999 but the business wants the output value as 009999. They want to see output value as 6digit like (009999).can someone help me how to write code here
    ROGRAM CONVERSION_ROUTINE.
    Type pools used by conversion program
    TYPE-POOLS: RSD, RSARC, RSARR.
    TYPES: DE_ZEBAY01(000015) TYPE C.
    Conversion rule for InfoObject ZEBAY01
    Data type = CHAR
    ABAP type = C
    ABAP length = 000015
    FORM CONVERT_ZEBAY01
    USING RECORD_NO LIKE SY-TABIX
    SOURCE_SYSTEM TYPE RSA_LOGSYS
    IOBJ_NAME TYPE RSIOBJNM
    CHANGING RESULT TYPE DE_ZEBAY01 " InfoObject value
    RETURNCODE LIKE SY-SUBRC.
    $$ begin of routine - insert your code only below this line

    Hi Laxmi
    Use the below code.
    RESULT = RESULT+2(8).
      RESULT = RESULT(6).
      RETURNCODE = 0.
    First Result will take from 8 characters starting from first position. So you get rid of first two leading zeroes.
    Then take first 6 character from the result of above operation from the first character. You get rid off last 2 digits.
    Regards
    Anindya

  • Info object Global routine

    Hi,
    i had infoobject ZEBAY01 and need to write global transfer routine for this infoobject. Now the infoobject value is comming 0000999999 but the business wants the output value as 009999. They want to see output value as 6digit like (009999).can someone help me how to write code here
    ROGRAM CONVERSION_ROUTINE.
    Type pools used by conversion program
    TYPE-POOLS: RSD, RSARC, RSARR.
    TYPES: DE_ZEBAY01(000015) TYPE C.
    Conversion rule for InfoObject ZEBAY01
        Data type       = CHAR
        ABAP type       = C
        ABAP length     = 000015
    FORM CONVERT_ZEBAY01
      USING    RECORD_NO LIKE SY-TABIX
               SOURCE_SYSTEM TYPE RSA_LOGSYS
               IOBJ_NAME TYPE RSIOBJNM
      CHANGING RESULT TYPE DE_ZEBAY01 " InfoObject value
               RETURNCODE LIKE SY-SUBRC.
    $$ begin of routine - insert your code only below this line

    Hi Sri,
    This would be helpful to you.
    Data: de_zebay(15) type c value '000099999911223', " here i have given default value as 15 digits: 000099999911223
             de_zebay1(15),
             de_zebay(15).
    de_zebay1 = de_zebay3(6). "This will read 6 characters from 4th char onwards and place it to de_zebay1+
    de_zebay2 = de_zebay12(3). "This will read 3 characters from 13th char onwards and place it to de_zebay2+
    concatenate de_zebay1 de_zebay2 into de_zebay.
    result = de_zebay.
    Output: 099999223

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

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

  • BI end routine at transformation to populate info object by vlookup attribu

    Hi ,
    I am APO consultant working in Bi routines and I have the follwoing situation and need some guidance in ABAP code (routine) .
    We sales info from markets as flat filea snd lod them into cubes. One of the filed is file is External sales Group: ZEXSGRP. This is an attribute or Sales Group info object ZSLSGRP.
    We get external sales group populated in file when we upload the file into cube -  I  want to use end routine to vlook up the  info infoobject table ZSLSGRP - all the external sales groups and use the matching value to write Sales Group (ZSLSGRP).Example  if ZSLSGRP  is NAM and it attribute is  ZEXSGRP  and has value N0000032. The file gets value N0000032 so the end routine should look all attribute of all infoobject ZSLSGRP and match the value and populate in example above it populates NAM.
    Hope i am clear - can any help with this.
    thaks
    Varma

    Replace your select statement ,
    SELECT *
    FROM /BIC/PZF31SALOFF
    INTO CORRESPONDING FIELDS OF TABLE it_tab4.
    instead of selecting all the fields , pick only the fields which are required.(one good performance improvement)
    SELECT    /BIC/PZF31SALOFF  comp_code
    FROM /BIC/PZF31SALOFF
    INTO CORRESPONDING FIELDS OF TABLE it_tab4.
    Remove the line below , this is not required
    MODIFY it_tab4 FROM wa_tab4.

  • Why do u need conversion routine at object level?

    hi friends,
    what scenerio we use conversion routine at object level, while creating my character , there is option conversion routine, when we use, please give me 1 scenerio with sample code?
    regards
    ss

    Suneel,
    You can make transformation to the data for specific InfoObjects in the Transfer Rules and / or Update Rules.
    Now, when you do that, it will only affect that InfoObject in that particular set of rules.
    If you want to process o transform the data for this InfoObject ANYWHERE it is used, without the need of repeating it over and over in the Transfer or Update Rules where it is present, you just do it once, at the Object level.
    That's the main purpose.
    Sorry, I don't have a sample code.
    Regards,
    Luis

  • List of Routines where info object is used

    Hi all,
    I would like to list all routines where a info object is used. Can anybody tell me how do I do it in BW.
    Regards
    NPR

    RSTSRULES & RSTRANROUTMAP in SE16

  • Strange behaviour of Removal of Alpha for Info object in Quality system

    Strange behaviour of Removal of Alpha for Info object in Quality system as compared to Development system.
    Hi,
    The data for an info object Key in the DSO was 00000000000000000000000000123. I removed Alpha for the info object and data was corrected to 123 in the DSO in development system.
    Now, when i transported the info object without alpha to quality and loaded data into DSO, the data is still the same with leading zeros.
    I dont want to write routine to remove leading zeros, as I have values as 0. If i write routine, all zeros will be removed and this will be blank.
    Both development and quality have same patches applied and are on same level.
    Why is this strange behaviour in quality system...
    Any inputs?? please suggest.
    Thanks.
    Lavanya

    Hi,
      Did you drop and reload the data after changing the conversion?
    Regards,
    Raghavendra.

  • Conversion routine for time key figure

    Hi,
    i have a filed in datasource which has length 5 ( of numeric char ).it may be coz time can be represented as "hh:mm" which has of course of length 5.
    this particular field is mapped to a key figure of type time ( which is only 4 numc ).
    because of this mismatches transfer rules are not getting activated.
    what i need to do now? is it neccessary to write a conversion routine again?if yes, can any body write here the code required for it?
    thanks,
    Ravi

    Hi Ravi,
    Assuming time comes in 'HH:MM' , colon placed explicitly , Code should look like ...
    bwtime(2) = r3time+1(2) .
    bwtime2(2) = r3time3(2).
    Where BW_Time stands for info object.
              R3time stands for transfer structure field.
    Normally time field is of type  numc lenght 6 ( HHMMSS) and inthat case should not be any issue when used in BW system.
    Hope that helps.
    Regards
    Mr Kapadia
    ***Assigning points is the way to say thanks in SDN.***

  • 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

  • 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

  • BW Info Object update problem

    Hi All,
    We are implementing BW. The Vendor and Document date info objects are not mapped directly to SAP R/3. Hence the data is not updating directly fromR/3 for these info objects. So I have written a small transfer routine to update the info object. But it is not getting updated with this routine. I am not sure where the problem is. Any ideas why?
    The following is the code of transfer routine. There are two infosources: communicaoin structure and Transfer structure. I wrote the routine in transfer structure. This routine is written for the info object Vendor. 
    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 SL_ACTIV: CHAR - 000004
      ACTIV(000004) TYPE C,
      InfoObject SL_AWORG: CHAR - 000010
      AWORG(000010) TYPE C,
      InfoObject SL_AWTYP: CHAR - 000005
      AWTYP(000005) TYPE C,
      InfoObject 0ACDOC_NO_F: CHAR - 000010
      BELNR(000010) TYPE C,
      InfoObject 0PSTNG_DATE: DATS - 000008
      BUDAT(000008) TYPE D,
      InfoObject 0ITEM_NUM: NUMC - 000003
      BUZEI(000003) TYPE N,
      InfoObject 0CHRT_ACCTS: CHAR - 000004
      CHARTACCTS(000004) TYPE C,
      InfoObject 0CREATEDON: DATS - 000008
      CPUDT(000008) TYPE D,
      InfoObject SL_CPUTM: TIMS - 000006
      CPUTM(000006) TYPE T,
      InfoObject 0CREDIT: CURR - 000017
      CREDIT(000009) TYPE P,
      InfoObject 0CURRENCY: CUKY - 000005
      CURRUNIT(000005) TYPE C,
      InfoObject 0CURTYPE: CHAR - 000002
      CURTYPE(000002) TYPE C,
      InfoObject 0DEBIT: CURR - 000017
      DEBIT(000009) TYPE P,
      InfoObject SL_DOCCT: CHAR - 000001
      DOCCT(000001) TYPE C,
      InfoObject SL_DOCLN: CHAR - 000006
      DOCLN(000006) TYPE C,
      InfoObject SL_DOCNR: CHAR - 000010
      DOCNR(000010) TYPE C,
      InfoObject SL_DOCTY: CHAR - 000002
      DOCTY(000002) TYPE C,
      InfoObject 0FISCPER: NUMC - 000007
      FISCPER(000007) TYPE N,
      InfoObject 0FISCVARNT: CHAR - 000002
      FISCVAR(000002) TYPE C,
      InfoObject SL_LINET: CHAR - 000005
      LINETYPE(000005) TYPE C,
      InfoObject SL_LOGSYS: CHAR - 000010
      LOGSYS(000010) TYPE C,
      InfoObject SL_POPER: NUMC - 000003
      POPER(000003) TYPE N,
      InfoObject 0QUANTITY: QUAN - 000015
      QUANTITY(000008) TYPE P,
      InfoObject 0UNIT: UNIT - 000003
      QUANUNIT(000003) TYPE C,
      InfoObject 0GL_ACCOUNT: CHAR - 000010
      RACCT(000010) TYPE C,
      InfoObject 0COMP_CODE: CHAR - 000004
      RBUKRS(000004) TYPE C,
      InfoObject 0COSTCENTER: CHAR - 000010
      RCNTR(000010) TYPE C,
      InfoObject SL_REFACT: CHAR - 000004
      REFACTIV(000004) TYPE C,
      InfoObject SL_RFDCCT: CHAR - 000001
      REFDOCCT(000001) TYPE C,
      InfoObject SL_RFDCLN: NUMC - 000006
      REFDOCLN(000006) TYPE N,
      InfoObject SL_RFDCNR: CHAR - 000010
        REFDOCNR(000010) TYPE C,
      InfoObject SL_REFRYR: NUMC - 000004
      REFRYEAR(000004) TYPE N,
      InfoObject SPL_CUR1: CUKY - 000005
      RTCUR(000005) TYPE C,
      InfoObject 0VERSION: CHAR - 000003
      RVERS(000003) TYPE C,
      InfoObject SPL_CUR2: CUKY - 000005
      RWCUR(000005) TYPE C,
      InfoObject 0FISCYEAR: NUMC - 000004
      RYEAR(000004) TYPE N,
      InfoObject 0CO_AREA: CHAR - 000004
      RZZKOKRS(000004) TYPE C,
      InfoObject 0PROFIT_CTR: CHAR - 000010
      RZZPRCTR(000010) TYPE C,
      InfoObject 0PACCOUNT: CHAR - 000010
      SACCT(000010) TYPE C,
      InfoObject 0PCOMP_CODE: CHAR - 000004
      SBUKRS(000004) TYPE C,
      InfoObject 0PART_CCTR: CHAR - 000010
      SCNTR(000010) TYPE C,
      InfoObject 0POSTXT: CHAR - 000050
      SGTXT(000050) TYPE C,
      InfoObject SL_PPRCTR: CHAR - 000010
      SZZPRCTR(000010) TYPE C,
      InfoObject SL_TMSTMP: DEC - 000015
      TIMESTAMP(000008) TYPE P,
      InfoObject 0SALES: CURR - 000017
      TURNOVER(000009) TYPE P,
      InfoObject 0RECORDMODE: CHAR - 000001
      UPMOD(000001) TYPE C,
      InfoObject 0USER_NAME: CHAR - 000012
      USNAM(000012) TYPE C,
      InfoObject 0VTYPE: NUMC - 000003
      VALUETYPE(000003) TYPE N,
      InfoObject 0VALUATION: NUMC - 000001
      VALUTYP(000001) TYPE N,
      InfoObject SL_WSDAT: DATS - 000008
      WSDAT(000008) TYPE D,
      InfoObject SL_SPLTMD: CHAR - 000001
      XSPLITMOD(000001) TYPE C,
      InfoObject 0ASSET_MAIN: CHAR - 000012
      ZZANLN1(000012) TYPE C,
      InfoObject 0ASSET: CHAR - 000004
      ZZANLN2(000004) TYPE C,
      InfoObject 0DEBITOR: CHAR - 000010
      ZZKUNNR(000010) TYPE C,
      InfoObject SL_ZZLFNR: CHAR - 000010
      ZZLIFNR(000010) TYPE C,
      InfoObject SL_ZRPRCR: CHAR - 000010
      ZZREPPRCTR(000010) TYPE C,
      InfoObject SL_ZTCDE: CHAR - 000020
      ZZTCODE(000020) TYPE C,
      InfoObject 0REF_DOC_NO: CHAR - 000016
      ZZXBLNR(000016) 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_CREDITOR
    Compute value of InfoObject 0CREDITOR
    in communication structure /BIC/CSSPL_LINE
    Technical properties:
        field name      = CREDITOR
        data element    = /BI0/OICREDITOR
        data type       = CHAR
        length          = 000010
        decimals        = 000000
        ABAP type       = C
        ABAP length     = 000010
        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_CREDITOR
      USING    RECORD_NO LIKE SY-TABIX
               TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
               G_S_MINFO TYPE RSSM_S_MINFO
      CHANGING RESULT TYPE /BI0/OICREDITOR
               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.
      SELECT SINGLE CREDITOR FROM /BIC/AAPOSLVEN00
                    INTO RESULT
                    WHERE /BIC/SL_RFDCNR = TRAN_STRUCTURE-REFDOCNR.
       IF SY-SUBRC NE 0.
           CLEAR RESULT.
        ENDIF.
    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_CREDITOR
          Inversion of selection criteria for InfoObject 0CREDITOR
          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_CREDITOR
      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 = 'REFDOCNR'.
    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.
    Thanks for the great help,
    Sobhan.

    Hi manoj,
    Welcome to SDN!!
    Check this blog:
    /people/sap.user72/blog/2005/09/05/sap-bw-and-business-content-datasources-in-pursuit-of-the-origins
    Bye
    Dinesh

  • Conversion routine PROJ in case master data doesn't exist

    Hi gurus!
    I have a problem with info-object 0PROJECT. It has a conversion routine PROJ, which converts the values nicely from external format to internal only if the master data for such project exists. If I use a interval variable in bex query the query user needs to give the upper value in internal value (for example Y3000 instead of Y-3000) in case he or she doesn't know if the value exists in database or not. That is understandable because of the logic of conversion routine PROJ (uses attribute project_ex).
    But what explains the fact that query variable input value Y3000 doesn't give data of Y-3000, but only one smaller (Y-2999). To get data of project Y-3000 one has to give upper variable value Y3001.
    Has anyone better understanding of this query/conversion behaviour?
    Sari

    Check the example here
    http://help.sap.com/saphelp_nw04s/helpdata/en/dd/f470375fbf307ee10000009b38f8cf/frameset.htm
    In master data updates, you can either load time-dependent and time-constant data individually, or together.
    Hope it Helps
    Chetan
    @CP..

Maybe you are looking for

  • RH9 - Can I restore layouts in "Single Source Layouts" pod from .ssl files?

    RH 9 (latest) Windows 7 x64 Due to some corruption somewhere in our main help project that prevented me from generating layouts using the RoboHelp command line (rhcl.exe), I deleted my .xpj file and .cpd file, and then recreated the .xpj project file

  • Lock for changes in GR and GI & production order change

    Hi all,      We have MTO scenario. We do delivery after GR and then make invoice. My client's requirement is whenever the delivery is made, system should restrict the changes in production order and should not allow to change GR/GI documents. How we

  • Can't install doomsday from AUR

    Hello. I want to install doomsday to play doom, doom2 and so on I type yaourt -S doomsday and installation works correctly, but then this appears: -- Build files have been written to: /tmp/yaourt-tmp-ignacio/aur-doomsday/src/deng-1.9.0-beta6.9/doomsd

  • Network ready for Cisco wireless ?

    I know for IPT their is lots of network readiness guides. Is their anything like that for Cisco wireless (with central controler)? We looking at putting in Dell swithcs and not cisco. Anybody have any switch level feture I should be looking out for?

  • Package com.ms.wfc.app

    How 2 use this one in Applet? 10x Megi