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

Similar Messages

  • Why do we need a disabled AD object prior to migrating user from one domain to another.

    Say i am migrating a user 'Mr.A' mailbox from abc.com to xyz.com in exchange 2010 environemnt, why do i need a disabled AD object for Mr. A in xyz.com prior to migrating  ? please suggest.
    Aditya Mediratta

    Hi ,
    To be frank i am not aware of quest but i can suggest you in ADMT and also in exchange cross forest migration.
    I hope you are doing the cross forest migration from exchange forest to exchange forest , so on such case by using the prepare-moverequest.ps1  we can have
    only have the disabled MEU on the target exchange forest until the remaining attributes of the user object was migrated from ADMT.
    While running the prepare-moverequest.ps1  it will not completely move all the active directory user attributes from the source forest to the target forest
    but it will move all the exchange attributes to the target forest and finally it will make the MEU object in the disabled state. Since
    all the exchange attributes are already migrated to the target forest ,so prior to use ADMT user account migration we need to exclude the exchange attributes
    by running the script on the ADMT server .After doing so exchange attributes will not be migrated but the required user attributes will be migrated to make the MEU to the enabled state.
    Reference Link for types of exchange migration between the forest :
    http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
    Thanks & Regards S.Nithyanandham

  • USE OF CONVERSION ROUTINES WHILE CREATING DOMAIN

    Hi,
    Could anyone tell me the use of conversion routines under output characteristics tab while creating a domain ??
    Thanks & Regards,
    Mounica J

    Coversion Routines are used to convert field values into internal or external format.
    Once you specify the Conversion routines at domain level,it ensures that data conversion into external and internal format is handled automatically .
    Please close the post if the question is answered.
    Thanks,
    Faiz

  • How to get object level security in Universe?

    Hi,
    I need to get the object level security for an Universe. I'm able to get the list of objects and its security access level (Public / Controlled / Restricted / Confidential / Private / )  from the (.Unv) file using the Designer SDK.
    But I need to get the list of users who has the object level security in the universe. In the CMC, by clicking the Universe and click on the Object Level Security tab, we can see the list of users there.
    I need to get the same using BOE SDK.
    I have used the following query to get the universe from the repository,
    "select * from ci_appobjects where si_kind='universe' "
    But I'm not able to get the list of users having obj. level security for that universe.
    Kindly help me to proceed.
    Thanks.

    The access security level is encapsulated in the SI_KIND='Overload' object. 
    Look for those types of objects, and the doc for the Overload class.
    An Overload references the Universe to which it's associated, and User/UserGroup objects are associated with the Overload via SecurityInfo.
    Sincerely,
    Ted Ueda

  • Regarding  Transfer Routine at InfoObject Level(in Maiantance Screen Of In

    hai
    i have some bad characters from the oracle source system .
    So im writing the following Transfer Routine in the transfer rule for all infoobjects .
    RESULT = TRAN_STRUCTURE-PRENBT.
    call function 'ZTHW_REMOVE_BAD_CHARACTERS'
    changing
    string = RESULT.
    translate RESULT to upper case.
    But i want to write this code at InfoObject Level in the Maintanence Screen (Create Transfer Routine)
    So how can i write this code in Maintanence Screen of each InfoObject instead of writitng in the transfer rules.
    Pls give the ABAP CODE at InfoObject Levele
    pls tell me
    i ll assing the points
    rizwan

    hi rizwan
    there is a result value for the conversion routine at iobj level also .Please see below :
    PROGRAM CONVERSION_ROUTINE.
    Type pools used by conversion program
    TYPE-POOLS: RSD, RSARC, RSARR.
    TYPES: DE_YA_M_IND(000006) TYPE C.
    Conversion rule for InfoObject YA_M_IND
        Data type       = CHAR
        ABAP type       = C
        ABAP length     = 000006
    FORM CONVERT_YA_M_IND
      USING    RECORD_NO LIKE SY-TABIX
               SOURCE_SYSTEM TYPE RSA_LOGSYS
               IOBJ_NAME TYPE RSIOBJNM
      CHANGING RESULT TYPE DE_YA_M_IND " InfoObject value
               RETURNCODE LIKE SY-SUBRC.
    $$ begin of routine - insert your code only below this line        -
      <b>RESULT = .
      RETURNCODE = 0.</b>$$ end of routine - insert your code only before this line         -
    ENDFORM.

  • Why do we need to take a lock before invoking wait()/notify() on an Object?

    Hi,
    Why do we need to take a lock before invoking wait()/notify() on an Object? i know that we shud take otherwise illegalstateexception is thrown.
    what is the reason to take a lock bfefore invoking the above methods. why does jvm expects from the programmer?

    Please do not crosspost..

  • 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

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

  • Time Conversion Routine- Help

    I have a requirement where Iam haivng the Value as Input in CSV File for Time Feild as 12:00:00 A or 10:15:00 PM.
    As per BW Standard Time feild object allows HH:MM:SS format .Hence, I need to know if there is any Solution to convert the Input Data into required BW Timefield Format as my Job is failing to upload through CSV File into BW.
    Would appreciate your help in advance
    Thanks
    Ashley

    Hey why are you asking the same question again ???
    Time Conversion Routine- Help

  • ORA-03120: two-task conversion routine: integer overflow

    Hello DB Gurus!!
    Need your comments and help once again...
    I am trying to import a DUMP file into My Local Database ie. Oracle Database 10g Enterprise Edition Release 10.2.0.4.0
    The file exported was by different user on different Dabase of Oracle 10g i.e. Oracle Database 10g Enterprise Edition Release 10.2.0.3.0
    but while I am trying to import, I getting the following error..
    Please help.. and suggest the alternate..
    Warning: the objects were exported by XYZABC , not by you
    import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
    import server uses WE8ISO8859P1 character set (possible charset conversion)
    IMP-00008: unrecognized statement in the export file:
    . importing NEXOS_ADMIN_OLTP_API's objects into SHRICHANDRA_ABC123
    IMP-00003: ORACLE error 3120 encountered
    ORA-03120: two-task conversion routine: integer overflow
    . importing NEXOS_ADMIN_OLTP_TAB's objects into SHRICHANDRA_XYZ123
    IMP-00003: ORACLE error 3120 encountered
    ORA-03120: two-task conversion routine: integer overflow
    Thanks in advance..

    Thank Rajneesh,
    I suspect the same issue as you did, But unfortunately I don't have much option available, as other side all are production DB so All I can do is pull from there that is export and import to my local where I am stuck!!!
    Thanks..

  • 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 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 delimit leading zero in vendor number in OO ABAP ALV without using conversion routine

    Hi,
    How to delimit leading zero in OO ABAP ALV without using conversion routine, because I have many fields like vendor, customer, material number etc..
    How to address this leading zero.
    I appreciate your quick response.
    Regards,
    Nalini S.

    Hi Nalini,
    Delimiting leading zeros in fields has to be done via conversion routines, as suggested by Vadamalai you need to pass on the conversion routine name in you field catalog variable.
    Now as to which object oriented approach are you using to have your table contents display in ALV as it matters  -
    Using FACTORY method of CL_SALV_TABLE class, or
    Using SET_TABLE_FOR_FIRST_DISPLAY method of CL_GUI_ALV_GRID class.
    Using FACTORY method of CL_SALV_TABLE will do your own work, no need to apply any conversion routines or set long/medium/short text for columns as we do in field catalogs!
    Cheers,
    Varun

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

  • 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

Maybe you are looking for