How to use Field exit

Hi,
Our consultant wants to use field exit as a way to validate a certain field in a screen for tcode MB1B.
I tried to follow the steps below to create a field exit but it seems that I'm missing a step or two because it doesn't work.
1. Run program RSMODPRF in se38.
2. Enter the data element and the number of field exit
3. create and activate the function module
After this I run tcode MB1B but it seems that it did not pass through the field exit.
Do I need an extra step to make the field exit work? And how do I assign a field exit to a certain screen?
Hope to hear from you guys soon.
Thanks!

Hi Jackie,
1.Enter the tcode SE38
2.In the ABAP Editor enter the program name RSMODPRF
3.Execute
4.Then you will get a screen with Data Element and Number of Field Exit
Here enter the Data Element(for example MATNR for material no.) and
enter 0 to 9 or A to Z in the second field(I am taking 0 in my example)
5. Execute
6.Then you will be navigated to the Function Builder screen(se37) with FM name FIELD_EXIT_MATNR_0
The FM name contains the Data Element(MATNR) and No. of Field Exit (0) (in this case)
7.Then click on CREATE.
8.Give the Fun. Grp name and SAVE
9.It will take youn to the Source code wherein ypu have to write the code asb per your requirement
For Example:
FUNCTION FIELD_EXIT_MATNR.
IF INPUT BETWEEN 125 AND 150.
MESSAGE E000(ZMM) WITH "Material not allowed".
ENDIF.
ENDFUNCTION.
10.Then if you try to enter the values in MM01 for Material no.,this effect comes into picture
If you enter Material no between 125 and 150 you will get "Material not allowed".
Follow the above procedure with your requirements(data element,screen name)
And to assign a screen name and program to a Field Exit:
In the 'Field Exits for Data elements' screen, in the application tool bar you can assign the Program name and Screen no. by clicking Assign Prog. /Screen.
You will get the above screen by
1. goto tcode CMOD
2. Enter PRFB in the command prompt and press ENTER
Another procedure for implementing the Field Exit:
One more way to do this is goto tcode CMOD.
Enter PRFB in the command prompt and press ENTER
In the screen select the menu Field exit --> Create and follow the same procedure as above.
Please see the below links hich might be useful
http://www.****************/Tutorials/ExitsBADIs/MK01/FieldExit.htm
****Reward points if found useful
Regards,
Naresh

Similar Messages

  • Using Field Exit for a field in table KNA1

    Hi everyone,
    I am working on a ticket, the problem is we have a field called STRAS in table KNA1 which holds the address of the customer but now we want to increase the length of this field from 35 charachters to 55 due to some business requirement. SO my question is if this can be done using Field Exit and if yes.. can you please tell me how as I have never used Field exits.
    Thanks,
    Rajeev

    Hi,
    Using field exit, you can only validate the data entry for the field (either globally or on a particular screen field)
    This is usually done by implementing the field exit for the data element corresponding to the field(in your case STRAS_GP)
    Hence you cannot increase the length of the field using the concept of the field exits...
    Please note that after SAP R/3 4.6c, SAP has stopped the creation of field exits and there will be no support for any new ones created.
    Regards
    Shiva

  • How to use User Exit for SD...

    Hi there,
    My client's requirement is to block the overall status of the Sales Order header under status tab to be blocked when user r-enters a new scheduled date in the "First Date" column in the SO.
    When they goto VA02, & put a new date it must automatically put a delivery block in the header as well as make the order header status to be blocked.
    I see the “First date” field in the SO is in a Structure “RV45A”, the field name is ETDAT.
    Can you let me know how to use User exit MV45AFZZ?
    When doing it, it must put the Delivery block in table VBAK – LIFSK.
    Rgds,
    Pri

    Hi Debadatta,
    Welcome to SDN.
    Have you looked report program <b>RM07MAAU</b> (Report for Material Document Archiving)?
    Hope this will help.
    Regards,
    Ferry Lianto

  • How to use rri exit IF_EX_SMOD_RSR00004

    Hello Forum,
    we need to use the rri exit to map source fields depending on their values to the fields of the receiving query.
    Unfortunately, we've not found any kind of documentations or examples showing how to use the EXIT_SAPLRSBBS_001 and its parameters I_THX_RECEIVER, I_THX_SENDER, E_THX_MAPPING.
    Has anyone an idea how to use this exit properly?
    Many thanks in advance for any idea.
    Regards,
    Tobias

    Hi,
    you can find a useful document following this link:
    [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/library/business-intelligence/a-c/customer%20enhancements%20and%20userexits%20in%20bw%20-%20sap%20netweaver%20know-how%20network%20webinar.pdf]
    Hope this helps..
    /Pradeep

  • How to findout Field Exit and Menu Exit  ?

    Hi all,
    How to findout Field Exit and Menu Exit  ?If you have any example for both , could you please send it to me ?
    Thanks in advance
    Krishnasri

    To find user exit  check below code exicute with required T code you will get its all exits
    report  zm_user_exit1 no standard page heading.
    *& Enter the transaction code that you want to search through in order
    *& to find which Standard SAP User Exits exists.
    *& Tables
    tables : tstc, "SAP Transaction Codes
    tadir, "Directory of Repository Objects
    modsapt, "SAP Enhancements - Short Texts
    modact, "Modifications
    trdir, "System table TRDIR
    tfdir, "Function Module
    enlfdir, "Additional Attributes for Function Modules
    tstct. "Transaction Code Texts
    *& Variables
    data : jtab like tadir occurs 0 with header line.
    data : field1(30).
    data : v_devclass like tadir-devclass.
    *& Selection Screen Parameters
    selection-screen begin of block a01 with frame title text-001.
    selection-screen skip.
    parameters : p_tcode like tstc-tcode obligatory.
    selection-screen skip.
    selection-screen end of block a01.
    *& Start of main program
    start-of-selection.
    Validate Transaction Code
    select single * from tstc
    where tcode eq p_tcode.
    Find Repository Objects for transaction code
    if sy-subrc eq 0.
    select single * from tadir
    where pgmid = 'R3TR'
    and object = 'PROG'
    and obj_name = tstc-pgmna.
    move : tadir-devclass to v_devclass.
    if sy-subrc ne 0.
    select single * from trdir
    where name = tstc-pgmna.
    if trdir-subc eq 'F'.
    select single * from tfdir
    where pname = tstc-pgmna.
    select single * from enlfdir
    where funcname = tfdir-funcname.
    select single * from tadir
    where pgmid = 'R3TR'
    and object = 'FUGR'
    and obj_name = enlfdir-area.
    move : tadir-devclass to v_devclass.
    endif.
    endif.
    Find SAP Modifactions
    select * from tadir
    into table jtab
    where pgmid = 'R3TR'
    and object = 'SMOD'
    and devclass = v_devclass.
    select single * from tstct
    where sprsl eq sy-langu
    and tcode eq p_tcode.
    format color col_positive intensified off.
    write:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    skip.
    if not jtab[] is initial.
    write:/(95) sy-uline.
    format color col_heading intensified on.
    write:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    write:/(95) sy-uline.
    loop at jtab.
    select single * from modsapt
    where sprsl = sy-langu and
    name = jtab-obj_name.
    format color col_normal intensified off.
    write:/1 sy-vline,
    2 jtab-obj_name hotspot on,
    21 sy-vline ,
    22 modsapt-modtext,
    95 sy-vline.
    endloop.
    write:/(95) sy-uline.
    describe table jtab.
    skip.
    format color col_total intensified on.
    write:/ 'No of Exits:' , sy-tfill.
    else.
    format color col_negative intensified on.
    write:/(95) 'No User Exit exists'.
    endif.
    else.
    format color col_negative intensified on.
    write:/(95) 'Transaction Code Does Not Exist'.
    endif.
    Take the user to SMOD for the Exit that was selected.
    at line-selection.
    get cursor field field1.
    check field1(4) eq 'JTAB'.
    set parameter id 'MON' field sy-lisel+1(10).
    call transaction 'SMOD' and skip first screen.
    Rewards if useful......................
    Minal

  • How to use field symbols

    can anyone tell me how to use field symbols. What effect it has on performance of a program?
    what r its avantages?
    iam working on a report where iam facing a lot of problems in performance issue. can anyone tell how field symbols are useful in this regard?
    thanx to all

    Check the below links
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
    FIELD-SYMBOLS
    Basic form
    FIELD-SYMBOLS <fs>.
    Additions
    1. ... STRUCTURE s DEFAULT wa
    2. ... TYPE t
    3. ... TYPE LINE OF t
    4. ... LIKE s
    5. ... LIKE LINE OF s
    Effect
    This statement declares a symbolic field called <fs>. At runtime, you can assign a concrete field to the field symbol using ASSIGN . All operations performed with the field symbol then directly affect the field assigned to it.
    You can only use one of the additions.
    Example
    Output aircraft type from the table SFLIGHT using a field symbol:
    FIELD-SYMBOLS <PT>.
    TABLES SFLIGHT.
    ASSIGN SFLIGHT-PLANETYPE TO <PT>.
    WRITE <PT>.
    Addition 1
    ... STRUCTURE s DEFAULT wa
    Effect
    Assigns any (internal) field string or structure to the field symbol from the ABAP/4 Dictionary ( s ). All fields of the structure can be addressed by name: <fs>-fieldname . The structured field symbol points initially to the work area wa specified after DEFAULT .
    The work area wa must be at least as long as the structure s . If s contains fields of the type I or F, wa should have the structure s or at least begin in that way, since otherwise alignment problems may occur.
    Example
    Address components of the flight bookings table SBOOK using a field symbol:
    DATA SBOOK_WA LIKE SBOOK.
    FIELD-SYMBOLS <SB> STRUCTURE SBOOK
    DEFAULT SBOOK_WA.
    WRITE: <SB>-BOOKID, <SB>-FLDATE.
    Addition 2
    ... TYPE t
    Addition 3
    ... TYPE LINE OF t
    Addition 4
    ... LIKE s
    Addition 5
    ... LIKE LINE OF s
    Effect
    You can use additions 2 to 5 to type field symbols in the same way as FORM parameters (see also Type assignment of subroutine parameters). ASSIGN performs the same type checks as with USING parameters of FORM s.

  • How to use FIELD-SYMBOLS to declare a table

    How to use FIELD-SYMBOLS to declare a table?

    hi yong,
    this will be very general:
    FIELD-SYMBOLS : <gf_table> TYPE ANY TABLE.
    or
    to do like a specific table from your program
    FIELD-SYMBOLS : <gf_table> TYPE itab.
    itab is of course your internal table from your program.
    ec

  • How to use field symbols in program

    how to use field symbols can any one explain with example please..
    Regards,
    venki...

    Hi
    Field Symbols
    Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
    Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
    Field symbols are similar to dereferenced pointers in C (that is, pointers to which the content operator * is applied). However, the only real equivalent of pointers in ABAP, that is, variables that contain a memory address (reference) and that can be used without the contents operator, are reference variables in ABAP Objects.
    All operations programmed with field symbols are applied to the field assigned to it. For example, a MOVE statement between two field symbols moves the contents of the field assigned to the first field symbol to the field assigned to the second field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before.
    You can create field symbols either without or with type specifications. If you do not specify a type, the field symbol inherits all of the technical attributes of the field assigned to it. If you do specify a type, the system checks the compatibility of the field symbol and the field you are assigning to it during the ASSIGN statement.
    Field symbols provide greater flexibility when you address data objects:
    If you want to process sections of fields, you can specify the offset and length of the field dynamically.
    You can assign one field symbol to another, which allows you to address parts of fields.
    Assignments to field symbols may extend beyond field boundaries. This allows you to address regular sequences of fields in memory efficiently.
    You can also force a field symbol to take different technical attributes from those of the field assigned to it.
    The flexibility of field symbols provides elegant solutions to certain problems. On the other hand, it does mean that errors can easily occur. Since fields are not assigned to field symbols until runtime, the effectiveness of syntax and security checks is very limited for operations involving field symbols. This can lead to runtime errors or incorrect data assignments.
    While runtime errors indicate an obvious problem, incorrect data assignments are dangerous because they can be very difficult to detect. For this reason, you should only use field symbols if you cannot achieve the same result using other ABAP statements.
    For example, you may want to process part of a string where the offset and length depend on the contents of the field. You could use field symbols in this case. However, since the MOVE statement also supports variable offset and length specifications, you should use it instead. The MOVE statement (with your own auxiliary variables if required) is much safer than using field symbols, since it cannot address memory beyond the boundary of a field. However, field symbols may improve performance in some cases.
    check the below links u will get the answers for your questions
    http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
    http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/field_sy.htm
    http://searchsap.techtarget.com/tip/1,289483,sid21_gci920484,00.html
    Syntax Diagram
    FIELD-SYMBOLS
    Basic form
    FIELD-SYMBOLS <fs>.
    Extras:
    1. ... TYPE type
    2. ... TYPE REF TO cif
    3. ... TYPE REF TO DATA
    4. ... TYPE LINE OF type
    5. ... LIKE s
    6. ... LIKE LINE OF s
    7. ... TYPE tabkind
    8. ... STRUCTURE s DEFAULT wa
    The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Untyped Field Symbols ad Cannot Use Field Symbols as Components of Classes.
    Effect
    This statement declares a symbolic field called <fs>. At runtime, you can assign a concrete field to the field symbol using ASSIGN. All operations performed with the field symbol then directly affect the field assigned to it.
    You can only use one of the additions.
    Example
    Output aircraft type from the table SFLIGHT using a field symbol:
    FIELD-SYMBOLS <PT> TYPE ANY.
    DATA SFLIGHT_WA TYPE SFLIGHT.
    ASSIGN SFLIGHT_WA-PLANETYPE TO <PT>.
    WRITE <PT>.
    Addition 1
    ... TYPE type
    Addition 2
    ... TYPE REF TO cif
    Addition 3
    ... TYPE REF TO DATA
    Addition 4
    ... TYPE LINE OF type
    Addition 5
    ... LIKE s
    Addition 6
    ... LIKE LINE OF s
    Addition 7
    ... TYPE tabkind
    Effect
    You can define the type of the field symbol using additions 2 to 7 (just as you can for FORM parameters (compare Defining the Type of Subroutine Parameters). When you use the ASSIGN statement, the system carries out the same type checks as for USING parameters of FORMs.
    This addition is not allowed in an ABAP Objects context. See Cannot Use Obsolete Casting for FIELD SYMBOLS.
    In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. See Defining Types Using STRUCTURE.
    Effect
    Assigns any (internal) field string or structure to the field symbol from the ABAP Dictionary (s). All fields of the structure can be addressed by name: <fs>-fieldname. The structured field symbol points initially to the work area wa specified after DEFAULT.
    The work area wa must be at least as long as the structure s. If s contains fields of the type I or F, wa should have the structure s or at least begin in that way, since otherwise alignment problems may occur.
    Example
    Address components of the flight bookings table SBOOK using a field symbol:
    DATA SBOOK_WA LIKE SBOOK.
    FIELD-SYMBOLS <SB> STRUCTURE SBOOK
    DEFAULT SBOOK_WA.
    WRITE: <SB>-BOOKID, <SB>-FLDATE.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • How to use Field-symbol with dynamic select query

    Can anybody tell me, how to use field-symbols in the dynamic select query.

    FIELD-SYMBOLS <fs> { typing | STRUCTURE struc DEFAULT dobj }.
    1. ... typing
    2. ... STRUCTURE struc DEFAULT dobj
    The FIELD-SYMBOLS statement declares a field symbol <fs>. The name conventions apply to the name fs. The angle brackets of the field symbols indicate the difference to data objects and are obligatory. You can declare field symbols in any procedure and in the global declaration section of an ABAP program, but not in the declaration section of a class or an interface. You can use a field symbol in any operand position in which it is visible and which match the typing defined using typing.
    After its declaration, a field symbol is initial - that is, it does not reference a memory area. You have to assign a memory area to it (normally using the ASSIGN statement) before you can use it as an operand. Otherwise an exception will be triggered.
    eg.
    FIELD-SYMBOLS <fs> TYPE ANY.
    DATA: BEGIN OF line,
            string1(10) VALUE '0123456789',
            string2(10) VALUE 'abcdefghij',
          END OF line.
    WRITE / line-string1+5.
    ASSIGN line-string1+5(*) TO <fs>.
    WRITE / <fs>.
    output:
    56789
    56789
    reward if helpful
    anju

  • How to use User exit for MM_MATBEL

    Hi
    I want to exclude some material documents while archiving a range of material document through archive Object MM_MATBEL.
    Can you please suggest how to use user exit for this to exclude the material document while archiving.
    Please brief me details.
    Thanks,
    Debadatta

    Hi Debadatta,
    Welcome to SDN.
    Have you looked report program <b>RM07MAAU</b> (Report for Material Document Archiving)?
    Hope this will help.
    Regards,
    Ferry Lianto

  • Use Field-Exit in selection-screen

    Hi,
    I have actived the field-exit of data element p_pernr program RCATSC01 screen 1000.
    But the result is the same like before.
    It is possible to use field-exit in screen 1000 (selection screen) of transaction CAPS ?
    Julien.

    Hi
    I believe the field-exit works for screen of module pool only.
    Max

  • How to use user exit macros in demand planning?

    Hi all,
    I am have created an user exit macros? but then can anyone guide me how to use the abp code there in the User exit macros in demand planning.
    Thanks
    Pooja

    Hi Pooja,
    The ABAP code can be written inside the functional module assigned to user exit macro.
    Start Transaction SMOD.Enter APODM005 in the 'Enhancement' field. Select 'Display'.
    Then choose 'Components' or Shift+F11 and double-click the name of the function module.
    Double-click the include contained in the function module to enter the source code.
    For step by step details you can refer to SAP note 418801.
    Let me know if it helps.
    Regards
    Gaurav

  • How  to Creating Field EXIT

    Hi,
      Please tell me the step by step procedure for creating Filed Exit

    Hi Mohan,
    This will be too useful for u...
    Step by step procedure for creating Field Exits
    There are eight steps to creating a field exit:
                Step 1: Determine Data Element
                Step 2: Go To Field Exit Transaction
                Step 3: Create Field Exit
                Step 4: Create Function Module
                Step 5: Code Function Module
                Step 6: Activate Function Module
                Step 7: Assign Program/Screen
                Step 8: Activate Field Exit
    Step 1: Determine Data Element
    - Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
    - An easy way to determine the data element associated to a particular screen field is to:
    Go the appropriate screen.
    Position the cursor in the appropriate field.
    Press ‘F1’ for field-level help.
    Click on the ‘Technical info’ pushbutton (or press ‘F9’) on the help dialog box.
    On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
    Step 2: Go To Field Exit Transaction
    - The transaction to create field exits is CMOD.
    - You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
    - From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
    - After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
    NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
    Step 3: Create Field Exit
    - From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
    - After choosing this menu path, a dialog box will prompt you for the appropriate data element .
    - Enter the data element name and click the ‘Continue’ pushbutton.
    - Now, you will be able to create the function module associated to the data element’s field exit.
    Step 4: Create Function Module
    - You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the ‘Continue’ pushbutton.
    - In the ‘Function module’ field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
    FIELD_EXIT_<data element>
    - You can add an identifier (an underscore followed by a single character ).
    - The first function module for a data element’s field exit must be created without an identifier.
    - To create the function module, click on the ‘Create’ pushbutton, choose menu path Function module -> Create, or press ‘F5’.
    - After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing ‘Enter’, you will be able to go ahead and create the function module.
    - Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
    Step 5: Code Function Module
    - From the function module’s attributes screen, click on the ‘Source code’ pushbutton or choose the Goto -> Function module menu path to the code of the function module.
    - Here you will add your desired functionality for the field exit.
    - Remember that field exit’s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
    - You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
    Step 6: Activate Function Module
    - After coding the function module, you must remember to activate it.
    - Use the Function module -> Activate menu path to activate the function module.
    - At this point, you can return to the field exit transaction.
    - You should be able to 'green arrow' back to this transaction.
    - When you return to the field exit transaction, you will see an entry for the newly created field exit.
    - At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
    - Also, the field exit will not be triggered yet because it is inactive.
    Step 7: Assign Program/Screen
    - This step is only needed if you want to make a field exit local.
    - To make a field exit local, select the field exit and click on the ‘Assign prog./screen’ pushbutton.
    - In the dialog box , indicate the appropriate program name and screen number.
    This information indicates that the field exit is local to the specified screen in the specified program.
    - In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the ‘Fld. Exit’ field.
    - If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
    - If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
    Step 8: Activate Field Exit
    - The field exit must be active for it to be triggered by the system.
    - Activate the field exit by choosing the Field exit -> Activate menu path.
    - After assigning the field exit to a change request, its status will change to ‘Active’ and it will be triggered automatically on the appropriate screen(s).
    NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
    Set the above config in Tcode RZ11

  • How to use field 'HIER_ID' to determine price in S/O?

    I want to use field 'HIER_ID'(hierarchy) to determine price in S/O but I don't know what value I should maintain in pricing master data.
    It should be 'HIER_ID' = 01 or 02 or 10 or else?????
    I don't know.

    HI,
      U have to create a new condition table in the tcone V/03, there u can take the required field . then assign it to ur acess sequence.
    now maintain condition record for that.
    u wl get the price in s/o
    cheers

  • How to use field "responsible Cost center" in Report Painter

    Hi
    I create report painter by using standard LIbrary and want to use field "Responsible Cost Center" as a parameter in order to display report in hierachy.But the standard Library  "6O1"  doesn't provide  this field .
    So I try to create new library by copy the standard  "6O1" and using  the structure "CCSS".But it doesn't show this "Responsible Cost Center" Field as a parameter .
    Please give me an advice step by step the way to get this field as parameter in report painter 
    regards
    Chompleon

    Hi,
    I have a similar requirement. I have followed OSS note 358251 as an example to add the 'Responsible Cost Center', however it doesn't display in the report even after I choose the field for display. The steps I have followed are -
    1) Added the field ZZ_KOSTV in the include structure CI_CC1S.
    2) Using transaction GRCT, table CCSS, I added a characteristic KOSTV with Def field OBJNR, and filler routinue EZZ_FILL_KOSTV.  I then wrote code in this routinue to populate the value KOSTV from AUFK table in the include program FK21REZZ. In debug mode, I can see correct values are populated in this field.
    3) I created a copy of an existing report in the library 6O1, changed it and in the Total line, added the field Responsible Cost Center to the Selected Characteristics. When I save, regenerate and execute the report, the value for  Responsible Cost Center doesn't get displayed though the displayed orders have a value populated in this field and when I debug I can see the value is passed ut correctly form the filler routinue to the field KOSTV.
    Please help and let me know what I need to do to be able to see this field in the output result.
    Regards,
    Neha

Maybe you are looking for