Problem with Field exits

Hi Gurus
i have a problem, in MM01/MM02(Basic data1) there is field called Prod.hierarchy(dataelement is prodh_d), for this data element how to create and change Field Exits and how to assign to MM01/MM02 Tcode.
the code part i have to write is
1. To validate MARA-PRDHA field length (field exit can handle this). the field length should be 18 char.
2.Copy the value of MARA-PRDHA to MVKE-PRODH (the code of the field exit above, you can do field-symbol technique to transfer value from mara-prhda to mvke-prodh).
plz. do the needfull information with all the steps with codeASAP.
I am using Ecc 6.0 Version.
Thanks & Regards,
Sudheer.

Hello,
If you want to create a user exit execute report RSMODPRF with out parameters and create the FM to the field you need, and active it.
But before doing that, check if there is a user exit or badi implementation availavle, it will be a better solution.
Check for instance, the following:
USER EXIT
MGA00001                                Material Master (Industry): Checks and Enhancements
MGA00002                                Material Master (Industry): Number Assignment
MGA00003                                Material Master (Industry and Retail): Number Display
Business Add-in
BADI_EAN_SYSTEMATIC                     BAdI for Internal Control of EAN Logic
WRF_DISCONT_PARAMS_I                    BAdI: Parameters in Fashion Discontinuation
WRF_DISCONT_FACT_E                      BAdI: Follow-Up Actions in Discontinuation
WRF_DISCONT_CHECKS_I                    BAdI: Scope of Check in Material Reorganization
MG_MASS_NEWSEG                          User-Specific Fields & Segments in Mass Maintenance
MATGRP_SKU_UPD                          BAdI for Article Hierarchy Connection
CDT_CHECK_MATERIAL                      Checks for Existence of a Material in a CDT
BADI_MM_MATNR                           Modification-Free Archiving Enhancement of MM_MATNR
BADI_MAT_F_SPEC_SEL                     BAdI for Material Special Field Selection
BADI_MATNR_CHECK_PVS                    Check Material for Use in iPPE
BADI_MATERIAL_REF                       Addition of customer-defined default data for material
BADI_MATERIAL_OD                        Integration of New Objects in Material or Article Master
BADI_MATERIAL_CHECK                     Enhanced Checks for Material Master Tables
BADI_GTIN_VARIANT                       User Exit for Customer-Specific GTIN Variant Check
Hope this helps,
Dont forget to reward.

Similar Messages

  • Problem with Field Exit

    I have created an field exit through a program RSMODPRF. The requirement is that I have to change the type of screen field from CHAR to NUMC. That I have already done, but how to validate the felid if the user enters the character values or how to prevent user not to use character values.

    I don't understand your problem. I'm in 4.7 and made small test:
    REPORT ztest.
    TABLES wlk1.
    PARAMETERS p_lfdnr like wlk1-lfdnr.
    I even can't type in any characters - that's already handled by GUI!
    Field-exits (even with RSMODPRF) will not be available in future release - if possible (and necessary) make your checks in a user-exit.
    Regards,
    Christian

  • IMPORT to memory id with field exit

    hi everyone, i need your help, i'm import to memory/export with field exit, I must capture a data of ik11, from table IMRG... this is the code:
    FUNCTION FIELD_EXIT_IMRC_MDOCM.
       DATA: V_MDOC LIKE IMRG-MDOCM.
    EXPORT V_MDOC TO MEMORY ID 'DOC'.
    ENDFUNCTION.
    And the field exit where capture the data and import to memory:
    FUNCTION FIELD_EXIT_IMRC_CNTRC.
        GET PARAMETER ID 'IPT' FIELD V_POINT.
          IMPORT V_MDOC FROM MEMORY ID 'DOC'.
        MESSAGE E001(ZEXITS_PRUEBAS) WITH V_MDOC.
    ENDFUNCTION.
    I proof with message, 'cause i can't use a break, really?!!!!
    Please help me!
    Thanks.!

    Hi Jimena,
    I remember a field exit being connected to a data element and program screen (dynpro). The field exit is processed when the screen field is processed by dynpro processor. But I do not see the screen field's value being exported to memory.
    The reason you can't put brekpoints is that actually the code is triggered by dynpro processor not abap runtime environment.
    If you want to proove thecode beeing executed, you can write info to file.
    SAP does not actively support field exits since a couple of releases. Are you sure this still works?
    You could try to find a BADI: Use the method I found at SDN some time ago:
    Follow the below steps to find out what all BADI's are called when you press any button in any transaction.
    1) Goto se24 (Display class cl_exithandler)
    2) Double click on the method GET_INSTANCE.
    3) Put a break point at Line no.25 (CASE sy-subrc).
    Now
    4) Execute SAP standard transaction
    5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
    6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
    7) This way you will find all the BADIs called on click of any button in any transaction.
    Regards,
    Clemens

  • Very urgent : Problem with field attributes in Datasource

    Hi
    I am getting a problem with field attributes in the datasource.
    The issue came up after i modified the extract structure-i modified one field and
    added one field to the structure.Now those two fields are not visible in BW.
    When i checked with transaction rsa2, i could find that for those two fields , the
    field attribute is <b>'A'</b> which is <b>'Field in OLTP and BW Hidden by SAP'</b>.
    I tried to modify the field attribute to make it visible.Now the issue is that it is not getting reflected after transport in the Q system.What can be the issue.In the Q system its still the old value 'A' ,which makes the fields invisible.
    Please let me know what can be the issue.
    Regards
    Leon

    Hi,
    did you change this attribute via RSA2?
    you need to change your datasource via postprocessing (RSA6); then transport your DS to your Q source system.
    Replicate your datasources in your BW.
    Finally modifiy your Transfer Structure by editing your TRules ( tab Datasource/Tran structure), move your new fields from the right frame to the left frame)
    Maintain your TRules
    Activate
    hope this helps...
    Olivier.

  • Problem with field GL Account is that it shows concatenated Chart of Accoun

    Hello . Please help me. We have sap BI olap universe . problem with field GL Account is that it shows concatenated Chart of Accounts. But user want to trim the chart of account and show only account in list of values in webi report.
    So What code I can put in Universe to remove this " 9000/" WHICH IS Chart of acct from GL Account
    example List of values shows
    9000/99030
    9000/99070
    I want to show as below
    99030
    99070
    I tried replace function in universe it does not work. Pls help.
    Thanks
    soniya

    Hi,
    You can do it in Web Intelligence using the function Right().
    Depending on the SAP BW version you have it is possible to build such calculated expression in universe on uniquename or name:
    <EXPRESSION>RIGHT[0CALMONTH].currentmember.uniquename,5)</EXPRESSION>
    OR
    <EXPRESSION>RIGHT([0CALMONTH].currentmember.name,5)</EXPRESSION>
    You have to replace 0CALMONTH by the unique definition of GL Accounts and you also need to use the object referencing GL Accounts in your query in addtion to the calculated expression.
    Regatds
    Didier

  • Problem with field label

    Hello All,
    I am having a strange problem with field label? I have created a table with three fields one is MANDT and and the remaining fields as PATID and PATNA.
    I am maintaining the field label for these fields, but still i am not getting the names of the fields while i am calling the structure in my alv tree.
    I d'nt know what is the problem here?
    can any one tell me how can i solve this issue?
    Regards,
    Lisa

    Hi lisa,
    This is not the problem with Data Dictionary,
    While declaring the fieldcatalogue for thr GRID.
    CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
    EXPORTING
      I_BUFFER_ACTIVE              =
       I_STRUCTURE_NAME             = 'ZTABLE'
      I_CLIENT_NEVER_DISPLAY       = 'X'
      I_BYPASSING_BUFFER           =
      CHANGING
        ct_fieldcat                  = gt_fieldcat
    EXCEPTIONS
      INCONSISTENT_INTERFACE       = 1
      PROGRAM_ERROR                = 2
      OTHERS                       = 3
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    If gt_fieldcat-fieldname = 'PATID'.
    gs_fieldcat-ref_field = 'ZTABLE'.
    modify gt_fieldcat from gs_fieldcat.
    clear gs_fieldcat.
    endif.
    Because while calling the FM it is populatinh the fieldname
    so you need to modify the fieldcatalogue with fieldname then it will pick the field labels from the Dictionary.
    Hope this  will solve your problem.
    Regards,

  • Problem with field  KONWA-Rate Unit(Currency or Percentage) of table KONP

    Hi Gurus,
    I m facing problem with field 'KONWA -Rate Unit (Currency or Percentage)' of table KONP. This field is showing ‘Currency’ and '%' both in table KONP. For some materials its showing currency value and for some its showing '%'. Due to which its creating load problems. My question is how this '%' is coming (means is there any calculation behind that or something else) in table KONP and how can I identify this.
    I am sure u will have the answer for this question so Thanks in advance.
    Message was edited by:
            Amit Rajput
    Message was edited by:
            Amit Rajput
    null

    Hi,
    take the following example: you sell liquor to customers; in your country, when you sell liquor your company is entitled to pay customs and excise fees to governamental authorities.
    These excises and duties are a percentage of the retail price. You'll then create such a condition record with this rate so that you calculation schema will post the correct value during the processing of billing documents...
    hope this shed light
    Olivier.
    Message was edited by:
            Olivier Cora

  • Can any one tell me how to work with field exit????

    Hi
    Can any one tell me how to work with field exit I know how to create them. I want to know how it works. Actually I want to create a field exit for T-CODE MIRO. Where I want to put the value ebeln of the PO Reference tab into the Assignment of details tab and make Assignment field disable.
    Thanks in advance

    Hi,
    Follow the Steps,
    1. Go to CMOD transaction
    2. From the menu "GOTO->TEXT ENHANCEMENTS->DATA ELEMENTS-   ->NEW DE CUST DOCU".
    3. In the displayed box specify the data element and
       press either "CHANGE" or " Ref to screen" button
    4. CHANGE button is for defining the documentation
    5. "Ref. to screen" if for assigning the screen in which
       a field has the this type data element.
       Note: You should have used this data element for a   
             field in that screen.
    6. Now it will ask for Function Module name, specify the
       FM name and double click it. It will go to the editor.
    7. Now using the Import parameters code accordingly
    8. Activate and go back
    9. Now "Assign the created program ( that is FM) to the
       screen by specifying the Program name and Screen
       number.
    10. Now save and activate.
    Note: No need to create a separate project for creating field exit through transaction CMOD.
    I hope this is suffice.
    Regs,
    Venkat Ramanan

  • Problem with field-length in sql-loader

    Hello,
    (sorry I see it's the wrong forum -> SQL-Developer, I searched for SQL-Loader, is there a possibility to change the forum ?)
    I can't find an answer for my question at google, so I hope there is someone in this forum who can help me.
    I have a dat-File that contains 12 500 000 records and want to laod it via sql-loader. The first field contains the ID and there were numbers from 1 to 12 500 000 stored.
    When I run the sql-loader, the ID run up to 9 999 999 and then, for the last 2 500 001 records, ist starts at 1 again.
    I noticed a few things :
    1. Numbers < 10 000 000 don't make Problems
    2. Numbers >= 10 000 000 make Problems, the first digit ( in this example "1") is cut, so the number "10 000 001" ist stored as "1". It comes to double entries (IDs 1 to 2 500 000).
    3. The same field-definition, I have for the third field of the record -> there is no Problem. THERE I can store any number.
    4. I tried to store a number > 100 000 000 -> the first digit was cut too, but ONLY the first digit.
    5. I'm able to store any number manually in the Database.
    So, I have a problem with the first field. If the number is greater then 10 000 000, the first Number is cut. It doesn't make any differance, if the number is 10 000 000 or 999 999 999, just the first digit, in the first field, is cut.
    Any idea ??????????
    Here some infos :
    Database :
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    SQL-PLUS :
    SQL*Plus: Release 10.2.0.4.0 - Production
    Script sqlldr :
    sqlplus ${schema}/$2 <<EOF >>LOAD.LOG
    set timing on
    set echo on
    set heading off
    set heading on
    !sqlldr userid=${schema}/$2 control=surface_geometry.ctl log=surface_geometry.log
    exit
    EOF
    ctl-File :
    LOAD DATA
    INFILE imp_surface_geometry_test2
    TRUNCATE
    CONTINUEIF NEXT(1:1) = '#'
    INTO TABLE SURFACE_GEOMETRY
    FIELDS TERMINATED BY '|'
    TRAILING NULLCOLS (
    ID INTEGER EXTERNAL ,
    GMLID,
    GMLID_CODESPACE,
    PARENT_ID NULLIF PARENT_ID = BLANKS,
    ROOT_ID NULLIF ROOT_ID = BLANKS,
    IS_SOLID,
    IS_COMPOSITE,
    IS_TRIANGULATED,
    IS_XLINK,
    IS_REVERSE,
    GEB_ID,
    GEOMETRY COLUMN OBJECT
    SDO_GTYPE INTEGER EXTERNAL,
    SDO_SRID CONSTANT 31468,
    SDO_ELEM_INFO VARRAY TERMINATED BY '|/'
    (X FLOAT EXTERNAL),
    SDO_ORDINATES VARRAY TERMINATED BY '|/'
    (X FLOAT EXTERNAL)
    Table-Definition (sql-File) :
    CREATE TABLE SURFACE_GEOMETRY (
    ID NUMBER,
    GMLID VARCHAR2(256),
    GMLID_CODESPACE VARCHAR2(1000),
    PARENT_ID NUMBER,
    ROOT_ID NUMBER,
    IS_SOLID NUMBER(1,0),
    IS_COMPOSITE NUMBER(1,0),
    IS_TRIANGULATED NUMBER(1,0),
    IS_XLINK NUMBER(1,0),
    IS_REVERSE NUMBER(1,0),
    GEB_ID CHAR(7),
    GEOMETRY MDSYS.SDO_GEOMETRY,
    CONSTRAINT c_unique_id UNIQUE (ID))
    storage (initial 1M next 1M maxextents 1024) ;
    Some Entries in the dat-File :
    12556067| |XXX|12556066|12556066|0|0|0|0|0| |
    #3003|1|1003|1|/
    #4479400.000000|5333360.000000| 526.870000|4479380.000000|5333360.000000| 526.720000|4479400.000000|5333340.000000| 526.980000|4479400.000000|5333360.000000| 526.870000|/
    12556068| |XXX| |12556068|0|0|1|0|0| |
    #||/
    #|/
    12556069| |XXX|12556068|12556068|0|0|0|0|0| |
    #3003|1|1003|1|/
    #4479380.000000|5333380.000000| 526.600000|4479380.000000|5333360.000000| 526.720000|4479400.000000|5333360.000000| 526.870000|4479380.000000|5333380.000000| 526.600000|/
    log-File : (100 records for the test)
    SQL*Loader: Release 10.2.0.4.0 - Production on Fr Mai 28 15:16:43 2010
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    Kontrolldatei: surface_geometry.ctl
    Datendatei: imp_surface_geometry_test.dat
    Fehlerdatei: imp_surface_geometry_test.bad
    Datei für zurückgewiesene Sätze: nichts spezifiziert
    (alle Discards zulassen)
    Zu ladende Anzahl: ALL
    Zu überspringende Anzahl: 0
    Zulässige Fehler: 50
    Bind-Array: 64 Zeilen, maximal 256000 Bytes
    Fortsetzung: 1:1 = 0X23(Zeichen '#'), im nächsten physischen Satz
    Benutzer Pfad: Konventionell
    Tabelle SURFACE_GEOMETRY, geladen von jedem logischen Satz.
    Insert-Option in Kraft für diese Tabelle: TRUNCATE
    Option TRAILING NULLCOLS ist wirksam
    Spaltenname Position Läng Term Eing Datentyp
    ID FIRST * | CHARACTER
    GMLID NEXT * | CHARACTER
    GMLID_CODESPACE NEXT * | CHARACTER
    PARENT_ID NEXT * | CHARACTER
    NULL wenn PARENT_ID = BLANKS
    ROOT_ID NEXT * | CHARACTER
    NULL wenn ROOT_ID = BLANKS
    IS_SOLID NEXT * | CHARACTER
    IS_COMPOSITE NEXT * | CHARACTER
    IS_TRIANGULATED NEXT * | CHARACTER
    IS_XLINK NEXT * | CHARACTER
    IS_REVERSE NEXT * | CHARACTER
    GEB_ID NEXT * | CHARACTER
    GEOMETRY DERIVED * COLUMN OBJECT
    *** Felder in GEOMETRY
    SDO_GTYPE NEXT * | CHARACTER
    SDO_SRID CONSTANT
    Wert ist '31468'
    SDO_ELEM_INFO DERIVED * VARRAY
    Abschlusszeichenfolge : '|/'
    *** Felder in GEOMETRY.SDO_ELEM_INFO
    X FIRST * | CHARACTER
    *** Feldende in GEOMETRY.SDO_ELEM_INFO
    SDO_ORDINATES DERIVED * VARRAY
    Abschlusszeichenfolge : '|/'
    *** Felder in GEOMETRY.SDO_ORDINATES
    X FIRST * | CHARACTER
    *** Feldende in GEOMETRY.SDO_ORDINATES
    *** Feldende in GEOMETRY
    Tabelle SURFACE_GEOMETRY:
    100 Zeilen erfolgreich geladen.
    0 Zeilen aufgrund von Datenfehlern nicht geladen.
    0 Zeilen nicht geladen, da alle WHEN-Klauseln fehlerhaft waren.
    0 Zeilen nicht geladen, da alle Felder NULL waren.
    Zugewiesener Bereich für Bind-Array: 232576 Bytes (64 Zeilen)
    Byte in Lese-Puffer: 1048576
    Gesamtzahl der übersprungenen logischen Datensätze: 0
    Gesamtzahl der gelesenen logischen Datensätze: 100
    Gesamtzahl der abgelehnten logischen Datensätze: 0
    Gesamtzahl der zurückgewiesenen logischen Datensätze: 0
    Lauf begonnen am Fr Mai 28 15:16:43 2010
    Lauf beendet am Fr Mai 28 15:16:43 2010
    Abgelaufene Zeit: 00:00:00.19
    CPU-Zeit: 00:00:00.01
    Edited by: user9338988 on 28.05.2010 06:21

    sorry, wrong forum. I opened the thread in forum "Export/Import/SQL-Loader & External Tables"

  • Is it possible to work with Field Exits in R/3 Enterp. Basis 6.20???

    How could I work with them?

    Yes you can.
    SE 38 --> Prog RSMODPRF
    http://www.sapdevelopment.co.uk/enhance/fexits.htm
    But Have a look at OSS note 29377 as well:
    Symptom
    Problems and questions concerning field exits
    Other terms
    FAQ, Q+A, SMOD/CMOD, field exits
    Reason and Prerequisites
    Note
    Field exits are frozen on the 4.6C maintenance level and are not further developed. This means that the existing functionality is kept with all restrictions (see also the last item below). Existing exits can be further used and are called at runtime as usual.
    Existing exits can be maintained using program RSMODPRF (run the
    program using transaction SE38). 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).
    Solution
    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).
    Generate the screen on which the exit should be active using SE51. It is possible that it was not correctly generated. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with SE38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
    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 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, 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 variables 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 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 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 can lead to an ABAP dump error when function module FIELD_EXIT_<data element name> is called.
    This is an error in the kernel which no longer occurs as of Release 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.
    Due to performance reasons, the active/inactive indicator is stored in the screenload. This can cause inconsistencies between Source and Load. Generate the affected screen with se51. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with se38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
    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_<data_element>. 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 to the dictionary. If the relation is indirect, i.e. via an ABAP declaration (<fieldname> LIKE <dictionary element>), no field exit can be executed.
    11. Field exits do not work on selection screens.
    Results from the previous item since ABAP-internal fields and never the original Dictionary fields are used on selection screens.
    12. Field exists do not work on check buttons.
    Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on them.
    13. How can all screens that use a data element be generated?
    If you want to be sure that all screens that use a specific data element are regenerated, you can transfer Report rsmodfdg from the correction instructions into a customer report (e.g. zsmodfdg). The Report regenerates all screens. In this way, you can ensure that active field exits refer to screens and that inactive exits cannot be called on any screen. The Report uses the affected data element as the input parameter. The affected data element is in the name of the exit: FIELD_EXIT_<data element name>.
    14. Restriction of usage
    Field exit technology was developed for input fields on dynpros and cannot be used for other/new dynpro elements. This means that this technology does not offer support for the new ScreenPainter elements such as graphical elements (e.g. checkbuttons, radiobuttons, dropdown listboxes), controls (except for table controls which are supported like a step loop), or selection screens.
    Erwan

  • Problem activating field exit

    Dear Friends,
    When i try to activate my field exit using program RSMODPRF, the following message appears.....
    System is not configured for field exits (see long text)
    Message no. ENHANCEMENT032
    Diagnosis
    The system is configured wrong. Field exit maintenance will have no effect.
    System Response
    The profile parameter abap/fieldexit is set to YES during screen generation. A screen load is generated that allows you to branch to field exits.
    This parameter may only be set in the customer system.
    Note: If the parameter has been set, you must check that, for each field, the system branches to the correct corresponding function module during screen generation. For performance reasons, you should not set this parameter during generation unless field exits have actually been created for your system.
    Procedure
    Set the abap/fieldexit parameter to YES in the system profile and restart your SAP system.
    How to solve this problem....
    Thanks & Regards,
    Sudheer

    Hi,
             go thourgh the documentation of the program RSMODPRF..
    Short text
    Field Exits for Data Elements
    Description
    Maintenance transaction for creating and activating field exits
    As part of the extension concept, SAP allows you to install a field exit for each screen field. Similar to the conversion exit, the system branches at the field exit at DCI (DATA COMMUNICATIONS INPUT) to a function module, if the field is an input field and a function code was triggered. The function module must adhere to the following naming convention:
    Prefix: FIELD_EXIT_
    Infix:  <Data element name>
    Suffix: _0 to _9 (optional), _A to _Z
    The interface is automatically generated during the creation of the function module, and has 2 parameters:
    Import parameter:  INPUT
    Export parameter:  OUTPUT
    After a function code has been triggered the contents of the field are made available to the FB via the "INPUT" import parameter. You can edit this and, when changed, make it available to the ABAP/4 processor in "OUTPUT". The input field contents are usually passed on: you can simply write OUTPUT = INPUT.
    If, e.g., you have activated the field exit for the data element 'PROGRAM', then the fields of all the screens, which refer to the data element 'PROGRAM', branch to the function module FIELD_EXIT_PROGRAM. This includes the field 'Program' of the initial screen SAPMS38M0100 in transaction SE38, for example.
    If you do not want the function module to be accessed from all screens, assign particular screens to the data element PROGRAM. By allocating an exit number, it is also possible to branch to other function modules with the corresponding suffix _0 ... _Z.
    Example: You have assigned screen SAPMS38M0100 and exit number 5 to data element 'PROGRAM'. The corresponding field on SAPMS38M0100 branches to FIELD_EXIT_PROGRAMM_5.
    As soon as you activate an exit, the corresponding screens are invalidated.
    Note: Field exits are only taken into account during screen generation if the parameter  abap/fieldexit = 'YES' is set in the system profile.
    Requirements
    Set the profile parameter  abap/fieldexit = 'YES' before system start.
    Limitations
    The following ABAP statements are not allowed in the function modules of field exits:
         BREAK-POINT,
         CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT,
         COMMIT WORK, ROLLBACK WORK,
         COMMUNICATION RECEIVE,
         EXIT FROM STEP-LOOP,
         MESSAGE I, MESSAGE W.
    Note:
    Field exits cannot be edited with the debugger.
    You should not use any external Performs in field exits. The ABAP processor shares the table work areas of externally called programs with those of the first caller. This could lead to errors at field exits that can hardly be analyzed, as field exits are sometimes slipped into the flow of the program at unforeseen events.
    Questions and answers on field exits
    1. A field exit was created with the CMOD and activated, but it does not get executed when the screen is called.
    Since the field exit is not executed until DCI, some action must occur in the screen (e.g. press Return, saving....).
    Set the abap/fieldexit profile parameter to YES and start the system again.
    After the FIELD_EXIT... function module has been activated and the field exit has been activated, the transaction in whose screen the field exit is to be executed must be terminated. The screen is not generated until it is called.
    Do not work on different application servers, otherwise there may be a delay before the field exit becomes active.
    The profile parameter must be set either on all application servers or on none.
    If the field exit is to be active in certain screens only, then you should check whether you have selected the correct program and the correct screen number (Careful with SUBSCREENS Do not rely on the F1 information for the field!
    2. How does setting abap/fieldexit affect the performance?
    If a screen is generated and the profile parameter is set, then the system checks in 2 tables (TDDIR, TDDIRS) to see whether a field exit has to be generated for the field. In practice the screen load after a Put is not generated until the screen is called. The user will not experience a noticeable delay, since screen generation is extremely fast.
    3. Can the contents of other screen fields be read in a field exit?
    In principle all fields can be copied to global variables in the TOP or the function group. However, since the order in which the field exits are called is not guaranteed, this possibility should not be used.
    4. How does the field exit work in step-loop fields?
    After data input to DCI the field exit will be called as many times as fields are visible on the step-loop. The SY-STEPL system variable is incremented each time. If a new value is assigned to be field, then it will be visible in the module between LOOP. ENDLOOP. This module will also be called as many times as there are visible step-loop lines.
    5. Can field exits be debugged?
    No. Field exits have to be tested in isolation in the development environment. To analyze problems that occur only in the screen environment, the relevant variables can be written to the file system using TRANSFER... and can be analyzed there.
    6. What should one do if the field contents are not getting transported to ABAP/4?
    Check whether you have assigned a value to the OUTPUT field.
    7. When does the field exit get called in the case that there is a conversion exit attached to the data element?
    The field exit will be called after the conversion exit. This means that the INPUT field contains the data in the same form as that in which the ABAP/4 program also gets them.
    rEGARDS

  • Problem with field catalog after upgrade from 4.0

    Hi experts,
    We have recently upgraded from CRM 4.0 to 5.2.
    I am now experiencing a problem with generation of a transport request for field catalog in transaction CTFC_CRM. I can generate the field catalog without errors.
    The problem is that when I want to create the transport request in our dev system a pop up appears saying "Create object directory entry". Here I have to enter a package for some of the fields in the field catalog. The special thing is that the fields are not custom fields but rather SAP standard fields (using standard data elements). For example field BZIRK.
    These are SAP standard fields but they are not standard in the field catalog. In 4.0 I did not get this prompt but this has apparently changed from 5.0.
    What do I do? I guess if I need to create the objects I will need to use an SAP standard package. But how do I know what package to use?
    Any comments or suggestions will be highly appreciated.
    Best regards,
    Anders

    Hi,
    If you did just install database, then you use Embed PL/SQL Gateway.
    See this guide
    Upgrading Oracle Application Express in Oracle Database Express Edition
    I think you have not run step 5 script apxldimg.sql
    Regards,
    Jari

  • Problem with field symbols in ecc 6.0

    i have the following  code  written in 4.6 version   now i am executing the old report   in 6.0  but  i am facing with some unicode error.
      FIELD-SYMBOLS:
        <line_of_bs_table> LIKE tbl1024,
       READ TABLE bs_table INDEX row_bst ASSIGNING  <line_of_bs_table> .
        buffer_bsbuffer_ptr(aux) =  <line_of_bs_table> >col_bst.
    tb1024 is standard sap structure  for storing buffer contents
    i have the following error in ecc 6.0
    structure type   '<line_of_bs_table> >+col_bst'  does not start with a charecter type  field in unicode programs in such cases
    offset/ length declarations are not allowed.
    can any one tell how can a field symbol  structure is changed  to charecter  type.

    Hi elinuk,
    you have already posted this thread in the ABAP general forum under problem in field symbols in ecc6.0 and I think that this forum is more related to this issue than the DMS forum. So please close this thread and investigate this issue further in the ABAP general forum.
    Best regards,
    Christoph

  • Problem with field type STRING in table

    Hi Experts,
             I am new to ABAP. I have created a new transparent table which hold error info. One of the field has to store data of size about 1500 char.
    Since CHAR type is not acceptable for this field So I gave STRING type. Now when I try to create a TABLE parameter in a RFC enabled functional module using "LIKE YERROR" Then I get a error:
    "YERROR must be a flat structure. You cannot use internal tables, strings, references, or structure as component" 
    Why is this error? How to resolve it? Is it because I have used a field of type STRING in the table? If this is the problem then what other type can I use?
    What are other know problems with using STRING type?
    Please help!
    Thanks
    Gopal

    Hi,
    Try to declare it as type LCHR , it can hold up to 32000 chars.
    Regards
    vijay

  • Problem with field-symbols in UNICODE conversion

    Hi all.
    I'm in a UNICODE conversion project and I have a problem with a program that uses field-symbols.
    DATA: BEGIN OF wa_data_aux,
            mandt LIKE zindices-mandt,
            kschl LIKE zindices-kschl,
            datab LIKE zindices-datab,
            valor LIKE zindices-valor,
            descripcion LIKE zindices-descripcion,
            ernam LIKE zindices-ernam,
            erdat LIKE zindices-erdat,
            waers LIKE zindices-waers,
          END OF wa_data_aux.
    FIELD-SYMBOLS:
                   <fs2>  TYPE ANY,
                   <fs3>  LIKE wa_data_aux.
              <fs2> = <fs3>.
    This assignment results in a DUMP.
    Can anybody help me to solve this problem?
    Thanks!!

    TYPES: BEGIN OF wa_data_aux,
              mandt TYPE mandt,
              kschl TYPE kschl,
              erdat TYPE d,
              waers TYPE waers,
          END OF wa_data_aux.
    DATA: w_aux TYPE wa_data_aux.
    FIELD-SYMBOLS:
    <fs2> TYPE ANY,
    <fs3> TYPE wa_data_aux.
    w_aux-mandt = '300'.
    ASSIGN w_aux TO <fs3>.
    ASSIGN <fs3> TO <fs2>.
    WRITE : / <fs2>.
    GBY.

Maybe you are looking for

  • I just updated my iPad to the iOS 6. My iPad will no longer connect to the Internet.

    Help! My wifi says its connecting and then immediately goes off.

  • AS3 Image Map Linking Issue - No compiler errors

    Hello, I've made an image map in Flash using AS3, however it does not seem to be working properly. The links only work in a strange succession. In order to click all the links you must first click the last link followed by the first link, then the se

  • Wireless IP clients connecting to 7800 call manager

    Can a windows mobile 5 802 PDA with SIP capability be connected to a cisco call manager to use its voip ability like a soft phone? Is there a client program like skype that is needed that cisco provides to allow it to connect as a phone to the 7800 c

  • JList implementing Set interface

    It seems that the JList's DefaultListModel implement a Vector as it's underlying data structure. Any ideas on how to have the JList implement a TreeSet as it's underlying data structure - I don't want duplicates and also would like to have it in sort

  • Image Window Problem

    Please advise why my image windows fly to the left of the screen when I select 'float in window' or float all in windows in the work space tab.   If I drag the window back to where I want it, it flies back to the left of the screen.   I'm using Windo