Skip to Content
author's profile photo Former Member
Former Member

Field exit


I have one 3 field exit implemented for MB1C field, that is materia, batch and quantity. it will select a data form a table and populates to screen. is working fine, but the question here is, it wont work for certain user screen. example are, the number of lines that i will be populating is 16lines, and in user screen, it has only 12 lines, the fields exit can only populates 12 lines of data and another 4 lines wont be there. is there anyway i can code in the way that it can page down and populates another 4 lines of data so that we have complete set of population? it vary from one screen resolution to another. Please help


Hooi Fung

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Sep 20, 2007 at 03:12 AM


    Transaction Code - MB1C Other Goods Receipts

    Exit Name Description

    MBCF0002 Customer function exit: Segment text in material doc. item

    MBCF0005 Material document item for goods receipt/issue slip

    MBCF0006 Customer function for WBS element

    MBCF0007 Customer function exit: Updating a reservation

    MBCF0009 Filling the storage location field

    MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1

    MBCF0011 Read from RESB and RKPF for print list in MB26

    MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc.

    No of Exits: 8

    USER EXIT,295199,sid63_gci982756,00.html

    Rewards if useful...................


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 20, 2007 at 03:19 AM


    The below given info is not relevant to your question but thought it could be of some help.Check it.

    OSS NOTES: 29377


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


    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.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.