Need conversion rule for field PACKNR

Hi all
I am trying to insert PACKNR field from flat file to Data Base Table KONDP. I am getting the PACKNR field as 75 from flat file in order to upload it to data base table i need to Convert it in internal format IVPHv6g}0MZX08002hqR8m.
How can i encode PACKNR 75 as  IVPHv6g}0MZX08002hqR8m?
Regards,
Aboli.

Domain of PACKNR has a converion routine.
Double click in table on dataelement of PACKNR and next double click on domain of this dataelement.
Now you see exit routine, double click on this and you will get two routines:
CONVERSION_EXIT_VHUPI_INPUT
CONVERSION_EXIT_VHUPI_OUTPUT
Edited by: Micky Oestreich on Jun 18, 2009 1:10 PM

Similar Messages

  • ALE : conversion rule for field value to become null

    Dear experts,
    I need to pass a material from one system to another with ALE. The problem is that the field marc-prctr (profit center) of this material is populated in the first system, but it does not exist in the second, so I assume transaction bd79 should be used to convert somehow the value of prctr to initial.
    How can I do that??? I have already tried defining a conversion rule and assigning it to message type MATMAS, segment E1MARCM, but it did not work.
    Please help.

    Did you check this?<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/d3/06f6679aaf0e44b67ca6d6b58d91df/content.htm">http://help.sap.com/saphelp_erp2005/helpdata/en/d3/06f6679aaf0e44b67ca6d6b58d91df/content.htm</a>

  • Errors with the global conversion rule for the field 0SOURSYSTEM.

    Hello Gurus,
        We are implementing CRM Activities. I enhanced the data source and when I add new info objects to 0SAL_DS01 DSO and trying to activate I'm getting there errors. Can some one please help me out in this problem?
    Error in global conversion rule for InfoObject 0SOURSYSTEM
    Message no. RSAR263
    Diagnosis
    Errors with the global conversion rule for the field 0SOURSYSTEM.
    System Response
    The function module delivers the following error message:
    Field "" is unknown. It is neither in one of t
    Procedure
    Check the definition of the global conversion rule for an InfoObject
    What does this error mean? We are using BI 7.
    Thanks
    RKR

    I have around 9 source systems, do I have to maintain data for all of them for 0SOURCESYSTEM?
    I set data for CRM system and then tried to activate.. but still I'm getting same error.
    I;m getting this warning too...
    InfoObject 0FISCVARNT needs to be in key for DataStore object C_0SAL_D
    Message no. RSDODSO123
    Diagnosis
    Characteristic 0FISCVARNT is included in the data part of ODS object C_0SAL_D.
    System Response
    The fiscal year variant cannot be used in the update rules for calculating business hour characteristics.
    Does this matter???
    Thanks
    RKR
    Message was edited by:
            RKR M

  • Error in global conversion rule for InfoObject 0PERSLANGU when activating

    Dear Experts
    We are working on HR in BI7.0 with Ehp1.
    I am trying to Activate the Transfer Rules of 0HR_PA_PA_1 DataSource which has the BID (BW Development) as the Source System to itself in order to load 0PAPA_C02 (Headcount) InfoCube.
    When trying to Activate, it gives the following error message:
    Error in global conversion rule for InfoObject 0PERSLANGU
    Message no. RSAR263
    Diagnosis
    Errors with the global conversion rule for the field 0PERSLANGU.
    System Response
    The function module delivers the following error message:
    Incorrect statament: Expression missing Operand mi
    Procedure
    Check the definition of the global conversion rule for an InfoObject.
    In fact, we are Re-implementing 3.0b BW System in new BI7.0 Ehp1 System. I have checked the Config of InfoObject 0PERSLANGU to the one available in existing BWP (3.0b Production) system and it's all the same.
    Has anyone come across similar error message and how did you resolve. Any help is very much appreciated.
    Many Thanks,
    Chandu

    HI Chandu ,
    It is a bug in the system , can you take a look at the SAP note
    Note 1070702 - RSAR 263: Error in global conversion rule for InfoObject
    Hope it helps ,
    Regards,'
    Sathya

  • Error in global conversion rule for InfoObject when Activating 2LIS_11_V_IT

    Hello,
    I am facing several issues while activating the Content. For 2LIS_11_V_ITM I get the following message:
    Error in global conversion rule for InfoObject 0INCOTERMS2
    Message no. RSAR263
    Diagnosis
    Errors with the global conversion rule for the field 0INCOTERMS2.
    System Response
    The function module delivers the following error message:
    Incorrect statament: Expression missing Operand mi
    Procedure
    Check the definition of the global conversion rule for an InfoObject.
    Any suggestion?
    thanks,

    Hi Mohan,
    seems this message is common when activating BI_CONT.
    I believe what i did was:
    - go to the InfoObject
    - verified Object Routine (check) (then was ok).
    - Removed Object form DS
    - Activated DS  (w/o info object was giving problems)
    - Placed InfoObject back to the DS
    - Activated DS but now including Info Object
    Believe that worked for me.
    Let me know how it goes.

  • Error in global conversion rule for InfoObject 0INCOTERMS2

    When I activate BI content 2LIS_12_VCITM with transfer rule, The transfer rule was error with the message " Error in global conversion rule for InfoObject 0INCOTERMS2" and Mgs No. 263.
    The transfer rule cannot be activated.
    I checked the 0INCOTERMS2 infoObject . The global conversion rule is no error.
    The global conversion is in below.
    ============================================================
    PROGRAM CONVERSION_ROUTINE.
    Type pools used by conversion program
    TYPE-POOLS: RSD, RSARC, RSARR.
    TYPES: DE_0INCOTERMS2(000028) TYPE C.
    Conversion rule for InfoObject 0INCOTERMS2
        Data type       = CHAR
        ABAP type       = C
        ABAP length     = 000028
    FORM CONVERT_0INCOTERMS2
      USING    RECORD_NO LIKE SY-TABIX
               SOURCE_SYSTEM TYPE RSA_LOGSYS
               IOBJ_NAME TYPE RSIOBJNM
      CHANGING RESULT TYPE DE_0INCOTERMS2 " InfoObject value
               RETURNCODE LIKE SY-SUBRC.
    $$ begin of routine - insert your code only below this line        -
      TRANSLATE RESULT TO UPPER CASE.
    $$ end of routine - insert your code only before this line         -
    ENDFORM.
    =================================================================
    If you have any idea or face the similar problem, please suggest solution.
    Thank you.

    Good afternoon,
    If you have not done so already can you apply the SAP note  1387854 in your system and it should prevent the problem from happening again. If you also reactivate the infoobject  0INCOTERMS2 in RSD1 then it should be possible to manually activate the  transfer rule.
    Best Regards,
    Des

  • Error in global conversion rule for 0DOC_CATEG

    Hi Friends,
    My transfer rules are inactive for 2LIS_11_VAITM. When i tried to get activate i am getting the below error message...
    Error in global conversion rule for 0DOC_CATEG
    How i can activate the transfer rules.
    is there any global routine for this infoobject.
    Please suggest a solution.
    Thanks & Regards,
    Anand

    Hi Reddy,
    Goto Change mode of the info object 0DOC_CATEG. Just edit the description of 0DOC_CATEG by adding a "." and activate it.
    Again change the description by removing the "." and activate the info object.
    After doing this, activate the transfer rules. It'll work fine.
    -- Selva

  • Need a document for field exit....urgent

    Can any one please send a document for field exit or have a simple document on how to work on a field exit with screen shots. pls send it ...its urgent
    Thanks and regards
    Nandha kumar R

    Hi,
    A field exit is a type of user exit.
    A user exit is a hook where you can inject your own add-on functionality or behavior to SAP’s standard business applications without having to modify the original applications.
    Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.
    Field Exits
    Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.  Example: The data element BBBNR identifies a company’s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100. 
    The field exit concept lets you create a special function module that contains this logic. 
    You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number. 
    In 4.6c, you can use "RSMODPRF" program to create field exits.
    An example of a user exits :-
    MODULE user_exit_0001 INPUT 
        CASE okcode.
            WHEN 'BACK OR EXIT'.
                CASE sy-dynnr.
                        WHEN '100'.
                             SET SCREEN 0.
                             LEAVE SCREEN.
                        WHEN '200'.
    Note that you can write any code that satisfy your needs.                                                     ****
    But in this case, this was wrote as a sample code for reference sake.                                    ****
    And you can test it.                                                                                ****
                             SET SCREEN 100.
                             LEAVE SCREEN.
                 ENDCASE.
          ENDCASE. 
    Field exits (SMOD/CMOD) Questions and Answers
    1. Field exit was created with CMOD, but is not processed when calling the screen.
    -  Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
    -  Set profile parameter abap/fieldexit to YES and restart the system.
    -  After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.
    - Do not work on different application servers since there may be some delay before the field exit is activated.
    - The profile parameter must be set on all or none of the application servers.
    - If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen
          number (take care with subscreens).
    - Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit use the name of the data element and not the field name.
    - After transport, field exits are marked as active but will not be processed. 
       Tip: First try deactivating the field exit once more and then afterwards, activate it again.
    2. How is performance affected by setting abap/fieldexit?
    - If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an
    update. The user should not notice any difference because screen generation is very fast.
    3. Can you read the contents of other screen fields in the field exit?
    - In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them
    available to other field exits. Note here that field exits are always called and not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
    4. How does the field exit behave on step loop fields ?
    - After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system
    variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
    5. Can field exits be debugged ?
    - No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variable to the file system using TRANSFER... . These can then be analysed there.
    6. What can you do if the field contents are no longer transported to to ABAP/4.
    - Check whether a value is assigned to the field OUTPUT.
    7. When is the field exit called if a conversion exit is attached to the
       data element ?
    - The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the
    ABAP/4 program also receives it.
    8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@)
    - This is an error in the kernel which no longer occurs as of 3.0C.  As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
    9. Field exit is not visible in CMOD, although created.
    - If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_. This
    function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix,
    the data element is not displayed in CMOD.
    10. Field exit is not executed although it is active.
    -  Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an
    extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the         application by LOOP AT SCREEN.
    This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is
    invisible.
    - Field exits can only be executed for fields that are directly related tothe dictionary. If the relation is indirect, i.e. via an       ABAP declaration (  LIKE ), no field exit can be executed.
    11. Field exits on check buttons do not work
    -  Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on
    them.
    12. Field exits do not work on selection screens
    SAP Field Exits
    From 4.6c onwards, Field exits will no more be supported by SAP.  They removed the function of field exit but they had given lot of flexibility through userexit.
    However, if you still required it, here is how to activate it :-
    First called up transaction  CMOD.
    Then called up transaction PRFB.
    or
    Activation of the field exits and assignment of the dynpros can also be carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank).  If required, new field exits can be created using program RSMODPRF (see the program documentation).
    REFER THIS LINK ALSO.
    defining screen fields using FIELD-SYMBOL
    Thanks,
    Shankar

  • Steps to create substitution rule for field BSEG-RECID

    MIRO generates FI document. FI document has BSEG-RECID field. I need to apply substitution for BSEG-RECID depending on the value of the RSEG-GEBER field in MIRO. The substitution must be activated only if account to be booked is PL account in FI and derived MM document based on ZNPP PO type.
    Field values are as follows:
    RSEG-GEBER     BSEG-RECID
    No value                          No value
    N                              N
    D                              D
    A                              A
    Could anyone please let me know the steps to create the above substitution rule for the FI document
    Thank You

    Hi,
    You can do it as below:
    Prerequisite : Select the document type for which you want check, here you have to select the BKPF-BLART = " " (Give the document type for the MIRO)
    Substitution: Use the User exit with the logic as you said.
    If you want you can use the user exit in both PREREQ & SUBSTITUTION. It will be applicable in your case
    VVR

  • Jakarta Beanutils - Conversion rules for null

    Hi all,
    I am using the BeanUtils.copyProperties(target, source) method to copy my Struts ActionForm String-only fields into my Business JavaBean's typed fields (String, Boolean and Integer fields).
    The thing I am having trouble understanding is if there is no request variable sent for a particular value, this value is null in the Struts action form - but the copyProperties method uses this null String to populate an Integer field on my business bean as new Integer(0) - and not simply populating this value with null.
    This doesn't seem intuitive to me - if the HTML form had no value for a certain field, I expect both ActionForm and Business bean to also have a null value - the the form have the value "0", then I would expect this to get mapped through to new Integer(0) in the back end.
    Is there any documentation that explain the default BeanUtils conversion rules, or ways or adjusting these rules programatically ?
    I have browsed the jakarta site for a while, but not seem anything of immediate use, and google isn't helping at all !
    Many thanks for you help,
    Ben

    It certainly seems that all null Strings get mapped to the "default primitive value" for the wrapper class - 0 for Integer, false for Boolean etc...
    I think the problem here is I was looking for the copyProperties method to be a bijection (1 to 1 mapping) between String and Integer, e.g."1" maps to new Integer(1), and Integer(1) maps to "1"
    "0" maps to new Integer(0), and Integer(0) maps to "0"
    null String maps to null Integer, and null Integer maps to null StringBut it seems null String maps to new Integer(0), and new Integer(0) maps back to "0" - which is not my original value.
    Anyone know how to force this behvaiour or explain why the library doesn't follow what is, AFAICT, a more logical conversion scheme ?

  • Error in Global Conversion rule for InfoObject

    Hi Gurus,
                  I am working on SAP NetWeaver 2004s BW 7.0, I have extracted the SD cube 0SD_C03(sales overview) content from the business content and noticed the infoobject's transfer rules are not active and when i tried to active them i am getting the following error "Error in global conversion rule fro infoObkect 0DOC_CATEG"
    "NO PSA exits for the infoObject 0DOC_CATEG"
    Please help me to resolve the problem.
    Thanking you
    Mrudul.

    Hi,
    This solution of dummy change in routine worked for me.
    Thanks!!!
    Regards,
    Rohit
    Edited by: Rohit Chhaparwal on Feb 23, 2010 12:18 PM

  • Data Conversion rules for EDI processing (same client IDOC processing)

    Hi,
    I am trying to post IDOCS in same client.Its a PO->SO process.
    ie. there will be 1 outbound and inbound idoc in same client using EDI processing.
    I am using Data Conversion using Rulesfor converting sender fields.
    The LIFNR and PAORG od segment E1EDKA1 has to be converted.
    For ALE processing, the Data conversion is been done correctly.
    But no conversion is done for EDI.
    Can anybody help me with this problem ?
    Thanks in advance.
    Regards
    Megha

    Issue solved

  • Need conversion mechanism for converting 24 bit image to 16 bit

    In my java project I need to convert 24 bit image to 16 bit image. I don't have any clue. Please provide me the option to implement it.
    Thanks,
    jai

    That doesn't tell me much, and I know what you're talking about. I doubt that it tells the OP anything useful whatsoever.Sorry EJP, it was a mouthful I know. Maybe this will help instead, a ColorConversionOps class to work on *32 bit > 16 bit > 32 bit colors*. To help clarify where the 16 bit color input and output goes, some of the methods return or require parameters of type short. Also take notice the bitmask for variables of type short vs the bitmasks for int. AND pay particular attention to the unsigned right bit-shifting of the most-significant-digit.
    public class ColorConversionOps
      public static short convert32_16(int rgb) {
        int a = ((rgb & 0xF0000000) >>> 16);
        int r = ((rgb & 0x00F00000) >>  12);
        int g = ((rgb & 0x0000F000) >>   8);
        int b = ((rgb & 0x000000F0) >>   4);
        return (short)( a | r | g | b);
      public static int convert16_32(short rgb) {
        int a = ((rgb & 0xF000) << 16);
        int r = ((rgb & 0x0F00) << 12);
        int g = ((rgb & 0x00F0) <<  8);
        int b = ((rgb & 0x000F) <<  4);
        return (a | r | g | b);
      public static void printRGB_32(int rgb) {
        System.out.println("a="+((rgb & 0xFF000000) >>> 24));
        System.out.println("r="+((rgb & 0x00FF0000) >>  16));
        System.out.println("g="+((rgb & 0x0000FF00) >>  8));
        System.out.println("b="+ (rgb & 0x000000FF));
        System.out.println();
      public static void printRGB_16(short rgb) {
        System.out.println("a="+((rgb & 0xF000) >>> 12));
        System.out.println("r="+((rgb & 0x0F00) >>  8));
        System.out.println("g="+((rgb & 0x00F0) >>  4));
        System.out.println("b="+ (rgb & 0x000F));
        System.out.println();
    }Now to make the conversion from 32 bit color to 16 bit color and back. NOTICE there willl be a loss of precision -- just like someone else has already said.
    public class Test
      public static void main(String[] args)
        int rgb = 0xFFFFFFFF;
        ColorConversionOps.printRGB_32(rgb);
        //a=255
        //r=255
        //g=255
        //b=255
        rgb = ColorConversionOps.convert32_16(rgb);
        ColorConversionOps.printRGB_16((short)rgb);
        //a=15
        //r=15
        //g=15
        //b=15
        rgb = ColorConversionOps.convert16_32((short)rgb);
        ColorConversionOps.printRGB_32(rgb);
        //a=240
        //r=240
        //g=240
        //b=240
    }And now we see, the reason 16bit color is so unpopular to the rest of the world, but not for us here!

  • Help needed with 'Conditions' for field with read only on demand

    Hy guys,
    I really need your help now, i have two items named P22_LOGIN_TYPE (..wich can be 'Default' or 'Special') and P22_PASSWORD, i need to turn to 'read only' the second item when the first item is 'Default', i'v tryied the conditional option but with no success, i know is managed from there but it's not working for me, it seems that i don't know exactly how to do it. By the way, i have APEX 2.2.
    I need an exact guide (explanation) on how to do it, thank you very much.
    Best regards,
    Victor

    Firstly you could set your First item to be a select list with submit. Make the branch go to the same page.
    Secondly, on the read-only conditions for your second item, use the condition when item in expression 1 = value in expression 2, and set that to 'Default' in expression 2.
    Essentially this will re-submit your page when you make a selection either 'Default' or 'Special'. If 'Default' is selected, then the PASSWORD item will be rendered as read-only. If you don't want to display the PASSWORD item at all, you can put the above condition for the read-only, into the conditions section of the item.
    Hope this helps and is not too confusing. It reads a lot worse than it actually is ;)
    Cj

  • Need conversion logic for the xml sending from legacy system ...!!!

    Hi Experts ,
    we have one requirement where in the legacy system ( Sender system) is sending .xml  file and PI needs to pick the file and send it to ECC Via IDOC AAE Receiver Adapter  to R/3  (SAP ECC) System .
    The problem is the  .xml file which PI receives is in a different format  which is shown below
    </tns:Header>
        <tns:Body>
            <esa:Payload>
                <esa:Header>
                    <PayloadName></PayloadName>
                    <PayloadVersion>1.0</PayloadVersion>
                    <PayloadCreated>2014-01-07T02:39:55.793Z</PayloadCreated>
                    <PayloadSize units="Bytes">432</PayloadSize>
                </esa:Header>
                <esa:Data>
                    <zcs:HUM xmlns:zcs="com.">
                        <Hum_Number>00393155965135748871</Hum_Number>
                        <Source_Storage_Location>9000</Source_Storage_Location>
                        <Destination_Storage_Location>0100</Destination_Storage_Location>
                        <Material_Number>000000000000004123</Material_Number>
                        <Batch_Number>321940071 </Batch_Number>
                        <Quantity>0000000096000</Quantity>
                        <Production_Version>A100</Production_Version>
                        <Hostname>POSPI000003</Hostname>
                    </zcs:HUM>
                </esa:Data>
            </esa:Payload>
        </tns:Body>
    </tns:Envelope>|]
    need help to  convert this  .xml into PI Standard xml  format ( i mean without esa,zcs, ..So that at PI the message gets passed  successfully without throwing  xml parser issue or xml well not formed error .)  .
    do i need to write any java code for this ?
    Please experts needs your suggestions here .
    regards,
    khan ,

    Hi Aziz,
    please make sure your pasted xml has  start and end tags
    <tns:Body> </tns:Body>.
    i don't think you need to change the external definition. make sure that you use xslt mapping first then message mapping.
    Regards,
    Muni.

Maybe you are looking for