What is "Field known only in Exit " Indicator

Hello friends,
could anyone explain me "Field known only in Exit" option in the Datasource display screen in the source system. This you will see when you double click a DS in RSA6. Adjacent to Hide Feild column.
I have enhanced some fileds in teh extractor structure. Now, will have have to leave this indicator ON as I am populating this filedin CMOD?
Regards,
Simmi

Here comes a little bit of a trick:
If you don't check this flag on, depending on what table the field comes from, you may not have to code any customer exit!
E.g. 0COSTCENTER_ATTR
CSKS table
KOSTL - standard field
ZZXXX  - custom field
If you do not check the "Field only known in exit" flag you don't need any customer exit coding. The standard extractor is written flexibly enough to extract the ZZXXX field, provided that the field name is identical to that used on the source table. This doesn't work for all extractors, but worth a try before starting any coding.

Similar Messages

  • Field only known in Customer Exit

    Hi all,
    I know this topic has been discussed quite number of times before on SDN, but still i am confused with this field indicator.
    Based on previous posts in SDN, what i understand is that if we enhance a datasource by appending a field to
    extract structure we check this field.
    If i am not wrong we write the code to populate this field in CMOD.
    I have a bunch of fields appended to extract structure and i see that
    not all fields are checked for"filed only known in CustExit". But still i get data for these fields
    when i do extraction. All these fields are populated in UserExit.
    when data can be extracted even if "field know in custexit" is not checked. what is the significance of this indicator.
    Thanks
    Silpa

    *If fields are part of a standard extractor i can understand them not being checked. But in my case i have Z custom fields some of which are checked others are not.
    Eg: ZZ1, ZZ2, ZZ3, ZZ4. I have ZZ1, ZZ2 checked and ZZ3, ZZ4 not checked for "field known in customer exit" indicator.
    So you mean to say ZZ3 and ZZ4 will not get any values even though there is code for these two fields in customer exit.*
    What I meant was that irrespective of whether or not "field known in customer exit" is set, if in your customer exit you have coded for populating data to particular fields, those fields will get the data from customer exit.
    eg.
    zz1 and zz2 are set with this indicator
    zz3 and zz4 are not set
    If you code for zz1, zz2, zz3 and zz4, you can populate these values in exit
    If not, these fields will not be automatically populated in standard extractors as it can do so only for the fields which are part of standard extractors.
    Your main question was 'what is the significane of "field know in custexit" indicator'
    Its main significance as I have mentioned is that if a field is set with this indicator and the coding is not done in customer exit, that particular field will not get populated
    Edited by: Rahul K Rai on Jul 13, 2010 7:31 PM

  • What is Field Exit--Step By Step procedure..

    Hi,
    What is Field Exit.
    And How to validate a field on any screen using field exit.
    what is the Procedure.
    Please give me Step by Step Procedure.
    Points will be given for straight answers..
    Regards,
    Kiran

    Please find below the step by step procedure for field exit :-
    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
    Regards
    Kiran

  • P.O change if i change only screen exit field the data is not saving

    Hi ,
    In the purchase order header custom tab i am added a screen exit field .In the purchase order creation mode the screen exit field is saving.But in the change mode if i am changing only the screen exit field then it is showing as 'no data to save' and not saving .But at the same time if i am changing some standard field with the screen exit field then both the field is saving.
    I have to activate any field to save the screen exit field.Please let me know any exit to be activated for saving the data.
    With Regards,
    Ambrose

    Hi
    Pls keep a break-point in the PAI of Screen exit and check, whether it stops in change mode
    Regards
    Madhan D

  • What is it called when a field box only generates when another field box has text entered?

    Hi:
    I am using LiveCycle Designer 8.0 and am in the process of creating a form.  I want to create a field that only will generate if a previous field has text in it.  Kinda like: if this is entered, then this will happen.  Any thoughts?

    Hi,
    There is a lot of potential for creating dynamic forms with LC. The help file in LC and the guides on the Adobe web site give a lot of direction.
    In your first field you can write javascript against an event, in this case the exit event is probably best:
    if (this.rawValue == "" || this.rawValue == null) // this is a test if the first field is empty
         textField2.presence = "invisible";
    else
         textField2.presence = "visible";
    When testing you use double "=="; when assigning values you use a single "=". TextField2 is there, just hidden from the user.
    Good luck,
    Niall

  • Whats blue field indicating in MC02M_0ITM (Extraction Purchasing (Item)

    Hi,
    whats blue field indicating in MC02M_0ITM (Extraction Purchasing (Item),
    is this structure is related with mceeko and mcekpo?
    Best Regards,
    dushyant.

    Hi,
    MC02M_ITM is mainly getting data from EKPO.
    You can see that in Tx LBWE in the maintenance of the extract structure: you'll see MCEKKO and MCEKPO which usually relates to EKKO and EKPO respectively.
    hope this helps...
    Olivier.
    Message was edited by:
            Olivier Cora

  • Can't open new tab by going to file/new tab (or CTRL+T or clicking on the new tab field). Only way is to right click on a link and choose open in new tab.

    Can't open new tab by going to file/new tab (or CTRL+T or clicking on the new tab field). Only way is to right click on a link and choose open in new tab.

    Hello,
    '''Try Firefox Safe Mode''' to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.
    ''(If you're not using it, switch to the Default theme.)''
    * You can open Firefox 4.0+ in Safe Mode by holding the '''Shift''' key when you open the Firefox desktop or Start menu shortcut.
    * Or open the Help menu and click on the '''Restart with Add-ons Disabled...''' menu item while Firefox is running.
    ''Once you get the pop-up, just select "'Start in Safe Mode"''
    '''''If the issue is not present in Firefox Safe Mode''''', your problem is probably caused by an extension, and you need to figure out which one. Please follow the [[Troubleshooting extensions and themes]] article for that.
    ''To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.''
    ''When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.''
    Thank you.

  • How to make fields read only after form is filled in

    I am creating forms to be used within our company.  The customer srv representative (CSR) would fill in the form and send it to the customer for signature and initial.  There are a few issues I can't solve.
    1)  I need to make the rate & services fields read only after the CSR initials the form

    Will the CSR have Acrobat or just Reader, and what type of computer will the CSR be using (Windows/Mac/mobile OS)? If just Reader (Wind/Mac), this is possible by setting the fields to read-only with JavaScript. The problem is this can't be considered secure, even if using a password as discussed here: Password-protect and hide one form field
    With Acrobat you have the ability to flatten certain fields, which makes it a bit more difficult to change the "fields".

  • OA Framework,how to make field Read-Only which is used inside Switch case

    Hi all,
    Using Personalization in OA Framework, when I am trying to make field read only, which is inside Swich statement ,then that field get automatically hidden.but my purpose is to make that field read-only not hide.
    My field name is Proposed Annual Increase Amount .
    The Personalization swtich case lookslike this :-
    Field Name Shown
    Switcher: Proposed Annual Increase Amount Yes
    case_name_HrPRateAnnTotInputSs
    Message Text Input: New Annual Amount Yes
    case_name_HrPRateAnnInputSs
    Message Text Input: Annual Pay Rate Yes
    case_name_HrPRateCurrAnnSalSs
    Message Styled Text: Pay Rate
    Regards,
    Mxj2930

    Can you be a bit clear on your requirement. If you have a switcher to display a field based on some condition, the other fields will not get displayed. I did not get as to what you mean by "my purpose is to make that field read-only not hide.".
    Are you talking about the case, when the "New Annual Amount" (or) "Annual Pay Rate" fields are displayed conditionally, you want them to be read-only and not editable. If this is the case, set the read-only property of these fields to true.

  • What is the use of at-exit in mudule pool

    hi
    what is the use of at-exit in mudule pool. what is the use when we keep the function type as 'E' for a function code

    AT EXIT-COMMAND lets you call a module before the system executes the automatic fields checks.
    Automatic field checks can be avoided through AT EXIT-COMMAND, which works exactly the same way as CANCEL works from standard tool bar.  In the R/3 screen, if your want to quit the processing of that particular screen without entering the mandatory fields then user can click the CANCEL button, same functionality can be incorporated in the user defined transaction by usine AT EXIT-COMMAND.  This module can be called before the system executes the automatic field checks.
    Code for AT EXIT-COMMAND in flow logic and in module pool program can be written as follows.
    In Flow Logic:
    PROCESS AFTER INPUT.
    MODULE EXIT AT EXIT-COMAND.
    In Module Pool Program:
    MODULE EXIT.
    case okcode.
    when 'EXIT'.
    leave to screen 0.
    ENDMODULE.
    To achieve this kind of functinality, the pushbutton or menu item should be assigned a function type 'E' (Exit).  It tells the system to process this particular module before carrying out any field checks.
    Rewards if useful.

  • ML81N Make FM fields display only in account assignment

    Requirement is to make FM fields already derived from PO (derivation working correctly) display only or add an error message. Easy I thought just go to config for SES and click on Additional Fields display only (Cost Center?, WBS element? there was no funds management fields available)...then after some time investigating
    Have debugged the transaction and found some possibilities.
    (1) BADI TR_GET_ACCNT_ASSIGN called in function FM_ACCOUNT_GET_COBL from MS_ACCOUNT_ASSIGNMENT.
    (2) User Exit EXIT_SAPLFMCH_001 called in function FM_CHANGE_AA_SUBST
    (3) Use FMDERIVE to somehow check the PO derivation
    Just wondered if anyone had taken this further before I spend a lot more time understanding the whole process in order to achieve a small bit. Please I am a technical resource not FM specialist.
    If I could understand the process flow, at least it might help me make quickest simplest solution.
    thanks,

    Hi,
    You can customize the field status in tx OME9 for the relevant account assignment category.
    But be aware that this customizing will be valid for all purchasing documents and transactions - not only for ML81N and the services area.         
    During SES postings, inheriting the FM account assignment from the reference PO is the standard and expected behaviour, so you may see that FMDERIVE is not called when the PO reduction is to be posted during ML81N. Instead, the FMAA is read from table FMIOI and fmderive is skipped in those lines (fi transaction keys KBS/WRX, for instance).
    I hope this will help you
    Kind regards
    Mar

  • Quantity field display only in ME52N

    Dear Experts,
    Our requirement is to restrict any change in PR qty through ME52N.
    I have done the changes in field selection group ME52, but still the field is not in display mode.
    Kindly siggest what all field selection groups involved when ME52N transaction is executed.
    As per my understanding;
    I checked AKTV-Optional,ME52-Display and NBB-Mandatory...result should be display but the result is still optional.
    Also as per rule combination of display field with any other mode results display only(except suppressed).
    Is it getting overruled through hard coded standard programs...kindly advise.
    Regards

    SAP-MM wrote:
    Dear Experts,
    > Our requirement is to restrict any change in PR qty through ME52N.
    > I have done the changes in field selection group ME52, but still the field is not in display mode.
    >
    > Kindly siggest what all field selection groups involved when ME52N transaction is executed.
    > As per my understanding;
    > I checked AKTV-Optional,ME52-Display and NBB-Mandatory...result should be display but the result is still optional.
    >
    > Also as per rule combination of display field with any other mode results display only(except suppressed).
    > Is it getting overruled through hard coded standard programs...kindly advise.
    >
    > Regards
    hi,
    please change in me52n not in me51.
    and come to me52n 
    select other purchase requsion
    given your requsion number  and click on change / display option  then it displiedin change mode
    Thanking you.

  • Field Selection Key In Release Indicator For PR

    Hi,
    Can you explain what is the use of Field Selection Key in Release indicator for PR on what basis to select this value.
    regards,
      zafar

    Hi
    Field selection key   directs which  values can be changed after the relevant release indicators have been set
    Eg suppose you want to supress the field for PR after first release indicator has been set you have to assign the relevant field selection key to Release indicator
    you can assign the same to the release indicators in
    spro-mm-Purchasing -PR-Procedure with classification-set up Procedure with classification-release indicators
    you can set the field selection key in
    spro-mm-purchasing -PR- define screen layout at document level
    Regards
    Sandeep

  • What is "other" known for in how much space you have left?

    What is "other" known for in the bar at the bottom where it shows how much space you have left?

    Other is usually around 1 GB...
    A  ' Large Other ' usually indicates Corrupt Data...
    First Try a Restore from Backup... But... if the Large Other Persists, that is an Indicator of Corrupt Data in the Backup... Then a Restore as New is the way to go...
    Details Here  >  http://support.apple.com/kb/HT1414
    More Info about ‘Other’ in this Discussion
    https://discussions.apple.com/message/19958116

  • What is the difference between customer exits and user exits?

    hello friends,
    what is the difference between customer exits and user exits?

    Hi
    User exit - A user exit is a three character code that instructs the system to access a program during system processing.
    SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number.
    UXX: U is for user exits that are defined by the user.  XX represents the 2-digit exit number
    Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.     *-- Mani
    The following document is about exits in SAP :-
    The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. 
    SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    Types of Exits 
    There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
    Menu Exits
    Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
    SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.
    Screen Exits
    Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.
    Function Module Exits 
    Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. 
    When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated. 
    Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs. 
    These calls have the following syntax: 
    CALL CUSTOMER-FUNCTION ‘001’.
    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'.
                             SET SCREEN 100.
                             LEAVE SCREEN.
                 ENDCASE.
          ENDCASE.

Maybe you are looking for