Field Exit is not working in ecc6.0

hi all,
i have upgraded my system from 4.7 to ecc6.0, there was a field exit 'FIELD_EXIT_QLGO_VM04_A' in 4.7 for QA32, but problem is that it was working in 4.7 but not working in ECC6.0 while codes are the same. can anyone help me that what shud i do?
Regards saurabh.
Edited by: saurabh srivastava on Dec 6, 2008 11:45 AM
Edited by: saurabh srivastava on Dec 6, 2008 11:57 AM

Hi
U can ran the report to manage the field-exit (now I don't remember the name) by SE38 and check if your field-exit is still active and if it's active u can check the system parameter abap/fieldexit by trx RZ10: it has to be set to YES.
Anyway u should consider the field-exit are not supported by SAP from release 4.70.
Max

Similar Messages

Field Exits are not working in ECC6

Hi Friends,
We upgraded our 4.6C system to ECC6 but after upgradation field exits are not working. What could be the reason.
We are using GUI version-7.1 and SP-10,Release-6.
Rewarded,
Steve

Hi there,
Try this link ... it could help you.
[http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm|http://www.sap-img.com/abap/field-exits-smod-cmod-questions-and-answers.htm]
If not, give an example.
I did the same upgrade without problems.
Best regards.
Valter Oliveira.

Field Exit is not working in QA but working in Development Server....

Hi friends,
                     I have created Field Exit for data element EPOS_LGORT (Storage Location) .Which is using in ME21N transaction of MM. This Field Exit is proper
working in Development Server but after transport in QA it is not working. I have checked code , it is same as well as exist in development Server.
              Abap/fieldexit parameter already has been set as Yes. But still it is not working.
Following values has been set for Parameter abap/fieldexit for QA .
Dflt value                no
ProfileVal               YES
Current value          YES
SAP Release         4.71
                     Any other setting required for parameter's . Please suggest me.
Thanks.

Hi Chandrasekhar,
                       Thanks . Default value of parameter abap/fieldexit is 'yes or no' . Basis person told me that abap/fieldexit either can be set yes or no , so where we have to set 'X' value for abap/fieldexit parameter.
After execution of Program RSPARAM , following values found for QA Server.
1.1 R/3 C kernel               no
2.1 file                             no
3.1 file                             YES
3.2 program parameters    YES
3.3 Replace $$ and $(..)    YES
3.4 Generate file name      YES
4.4 Value in SharedMemory      YES
      Any other setting's we needed ?

Field exit is not working for a user

Hi,
We have implemented a field exit in ME12 to change the purchase info record short description. It is working fine for most of the users except for some users. I just wanted to know is there any way we can restrict the field exits based on Authorization
Did any one faced this kind of issues
Bhanu

Hi,
Reason could be that users are logged on different servers : check that profile parameter abap/fieldexit is set equally in all application servers.
If it's okay, then you'll find the reason only by tracing 2 users, one which is okay, the other not, doing exactly the same thing. To do that, use SE30 with a variant with "no aggregation", as Olga explains in her blog ([SDN blog: ABAP Runtime Analysis (SE30) - How to analyze ABAP program flow|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4847/17050 [original link is broken] [original link is broken] [original link is broken] ]). Then you compare the 2 traces to see from which point execution differs. You can use SAT transaction, available from 7.0, to compare 2 traces far more quickly.
BR
Sandra

Field exits is not working in the COPA

Dear All,
I had create the field exits for profit center and it is working well in all the screen except the COPA. My profit center field exits will automatically change the profit center value if user key in the valid profit center department in the profit center field.
However, it is not working in the COPA screen. Please kindly advise.
thank you very much

Thank u for your answer.
Yes, of course .. i�ve already apply the unique key validator for the entity.. so that custom error message is the error im trying to get in the application.
Other issue is when im trying to edit that error message: when im going to edit the message the previous error im entered is not there. Is it normal?

Cancel and Exit button not working

Dear Experts,
<u>Cancel and Exit button not working</u>
I am calling a screen from inside a report program
using SET SCREEN 9000.
2 of the date fields(start date end date)
on this screen are Mandatory.
I am not able to Come out of this screen 9000 using
CANCEL or EXIT button
without giving a date entry in both of
Mandatory fields (start date end date).
Can someone help me with a solution?
Appreciate your valuable help;
Points assured
Thanks,
Aby Jacob

Hi..
To avoid this problem you have to use AT EXIT-COMMAND Module.
1. In the GUI Status for both EXIT and CANCEL buttons assign the Function type E (Exit Command)
2. In the PAI of the Screen Call this module.
   MODULE EXIT_SCREEN AT EXIT COMMAND.
3. Now check the OK_CODE or Sy-ucomm in this module to Leave the Screen
   MODULE EXIT_SCREEN INPUT.
       CASE OK_CODE.
      WHEN 'EXIT' .
            LEAVE TO SCREEN 0.
      WHEN 'CANCEL'.
      ENDCASE.
   ENDMODULE.
This will surely work.
<b>reward if Helpful.</b>

Exit button not working can u say how to do that?

Exit button not working can u say how to do that?

Which version are you using, please the exact number? Exit depends also on the browser, not only on Captivate.

Publishing HTML(Page content) field required field validation is not working

The required field validation is not working on Site Column of type "Full HTML content with formatting and constraints for publishing". I found a link i.e.
https://social.msdn.microsoft.com/Forums/office/en-US/7b544aae-2562-4b8e-8e5b-36a1d47a4d14/publishing-htmlpage-content-field-required-field-validation-is-not-working?forum=sharepointdevelopment
which tells this is a hot fix in July 2014 CU . Can anyone help me with what all Fixes are there in July 2014 CU. So that I can update only if it required!
Or any other alternative where I can use the required field validator on "Full HTML content with formatting and constraints for publishing" column type?

You could add a scripteditor webpart on the newform.aspx page and add client side validation using jQuery.
$(document).ready(function()
var fname = document.getElementById('fname').val();
var lname = document.getElementById('lname').val();
var age = document.getElementById('age').val();
/*Do not know how to get element by class and that too, two different type. Have to check if user chose anything or not*/
$("#submit").click(function()
if(fname.length === 0)
alert("Please input a first name");
else if(lname.length === 0)
alert("Please input a last name");
else if(age.length === 0)
alert("Please input an age");

Formatted Search for Delivery Date field in SO not working

Hi All
Can anyone help me as to why my formatted search is not working?
I am currently using SAP B1A SP01 Patch 19.
I have created a user query as follows:
SELECT $ [$10.0.DATE] + 5
When I add this to the delivery field within the Sales Order and bring through the saved query which I set to auto refresh when the Posting Date field changes and to Display Saved Values it doesn't work.
Any ideas?
Thanks and best wishes
Gail

HI Gail,
If I am not mistaken you want to add days to the posting date...if that is so then try this out:
SELECT $[ORDR.DocDate.DATE]+5 From ORDR T0 For Browse
Set The indicator to Auto Refresh when the fields change
Nagesh

Exit button not working in MS Explorer

Hi. The exit button in our Captivate courses are not working
all of a sudden. They work in FireFox but in MS IE. We are using
Capivate 2.0. IE version is 6.0.

Hi Apparo,
In onAction method of the Exit button, a call is made to the TargetExitApplication as follows:
fpm.navigate(wdThis
.wdGetFcNavigationInterface()
.getNavigationTargetExitApplication());
Also, the Exit button does work in the Address Overview/Edit/Review Page, but not in W-4 Tax and Benefits Enrollment.
Any help on this problem !!!
Regards,
Adren

Exit Button not working in ESS

Hi All,
We have configured ESS in our landscape. When I go to any Overview/Edit/Review Page (in W-4 Tax, Add/Change dependents etc..), the Exit button which is present is not working. When I click the Exit button, it doesn't exit the current view, but instead stays at the current location.
Can anyone tell me the reason for this strange behaviour? Also, where should I make the code level changes for the Exit button work.
Any kind of help would be greatly appreciated.
Regards,
Adren

Hi Apparo,
In onAction method of the Exit button, a call is made to the TargetExitApplication as follows:
fpm.navigate(wdThis
.wdGetFcNavigationInterface()
.getNavigationTargetExitApplication());
Also, the Exit button does work in the Address Overview/Edit/Review Page, but not in W-4 Tax and Benefits Enrollment.
Any help on this problem !!!
Regards,
Adren

Setting form fields to required not working in Adobe Acrobat XI Pro

This should be a simple matter. However, I'm stuck in a rut with it, and cannot seem to get out.
I have created a form. All I need is for users to be prompted that they have to complete the form field when they try to tab or click out of that particular field where there needs to be information input. I have tried the following "on blur" java script code:
if (!event.value) {
    app.alert("This field is required. Please enter a value.");
    event.target.setFocus();
What continues to happen is when the user clicks out of that field, the error message comes up asking them to click "okay." The problem is that the error message does not go away after the user clicks it.
What I've learned is that if you right click on a field and click "set as required field," it doesn't work in the way I need it to. In fact, it hasn't been working at all for me.
Does anyone have a simple suggestion? I more than willing to try anything at this point.

OK, so the custom calculate script for field B could be something like:
(function () {
    // Get field values as strings
    var sA = getField("A").valueAsString;
    var sC = getField("C").valueAsString;
    var sD = getField("D").valueAsString;
    // Only perform the calculation if all fields are filled
    if (sA && sC && sD) {
        var sum = +sC + sD;
        event.value = sum;
        // Alert the user if the sum is more than A
        if (sum > +sA) {
            app.alert("Error message goes here");
    } else {
        // Blank this field if all fields are not filled in
        event.value = "";
Instead of (or in addition to) an app.alert popup, you could place this message in a read-only form field, and clear it if there is no error condition.

Exit button not working in Captivate 7 published output

Hi. I am using Capivate v7 and am experiecing this problem with published output:
I am using an Exit button that runs the standard javascript code
javascript:window.close()
so that the user can exit the presentation. The button works fine when I test out the presentation using Internet Explorer 8, but when I generate an output and try running the .swf file, the button does not work.
How do I get an Exit button to work for the .swf output?
Thanks,
- Michael Fekete

Yes, the close X does work 100% of the time. That's because the browser itself is just a window in the operating system. And you are commanding the window to close.
And you might find yourself asking why that would work while the Exit button fails. And it would be that it's a security issue. Security prevents the window from closing because if a web site was nefarious, it could actually trap you by making changes and quickly closing the window and preventing you from browsing elsewhere.
It's simple to turn off the Exit button. Just click Project > Skin Editor and clear the Close checkbox.
Cheers... Rick

Exit button not working on Personal Information DC

Hi,
The exit button in Personal Information ( Home Address & Phone ) DC is not working. The issue is when I click on Exit button the screen is getting refresh, but no action is taken place.
Is the issue related to SPRO Configuration? Because the respective method is calling from FPM -fpm.navigate(wdThis.wdGetFcNavigationInterface().getNavigationTargetExitApplication());
So I tried by writing following method, but when I click on Exit button from Edit & Review views, the page is opening in a new window instead of opening in a content area where as Overview page is opening in Content Area.
WDPortalNavigation.navigateAbsolute
                          ("ROLES://portal_content/abc/hr/ess/iviews/com.abc.hr.ess.iview.area_personal_information",
                 WDPortalNavigationMode.SHOW_INPLACE,
                 WDPortalNavigationHistoryMode.NO_HISTORY,
                 null);
Also I would like to know what are the configurations we need to do in SPRO with respect to ESS & MSS.
Thanks in advance to resolve the issue.
cheers
dev

Create an alert with name close_alert write message of you choice give lable to button1 and button2 Yes and No respectively.
On your exit button write below code
declare
     al number;
begin
     al:=show_alert('al_close');
     if al=alert_button1 then
          exit_form(no_validate);
     end if;
     end;Edited by: XeM on Apr 6, 2013 2:39 AM

Exit Plug not working in Portal

Hi experts,
I have a web dynpro application (WDP A) which fire an exit plug to another web dynpro application (WDP B). It works fine in normal web dynpro runtime. The architecture of the application is shown [here|http://img232.imageshack.us/img232/7172/exitplug.png].
Now i have created an iView in the EP for WDP A. When the button which fires the exit plug is clicked, i get this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
Seems exit plug is not working in portal run time. Any one has an idea on how to solve this?? Use portal navigation?? What is that?? any guideline and documentation on that??
Thanks in advance.
Best Regards,
kityein
Edited by: kityein lai on Aug 5, 2009 10:04 AM

Hi,
Now that your WD apps are running in a Portal they should be more "Portal aware".
What I mean is that now they are part of a larger framework and you cannot just call the other WD app.
To do this properly (as the error message says) you should use the portal navigation.
Portal navigation consists of many variants: Normal, Dynamic, Quicklinks etc etc.
I personally advice to use Quicklinks if you want to navigate between 2 applciations running in the portal but are not native-portal apps. Altough this might not fit your requrements in this scenario, I cannot say....
In addtions here are some help resources:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/38/5dc53e5ae84d3be10000000a11405a/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/97/b0ef8b24a64ae884f0ab246e54cae5/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/00c110606a5277e10000000a1553f7/frameset.htm
Hope this helps you a bit...
Benjamin Houttuin

Field Exit is not working in ecc6.0

Similar Messages

Maybe you are looking for