Clear Form & Exit Form

Hi All,
I have developed a new form.In my form i have some mandatory columns,without entering the madatory columns my form is not able to clear the data.
but it has to clear all the data in my form.Is there any solution to slove this
bit urget plss any body
Even if i say Exit form also itis not closing the Form.
Regards
Siva

Inside the block ABC where you have mandatory columns, I believe you may have cursored or entered one of the fields and did not place a mandatory value in the field. Then when you try and close the form, the form is complaining that you did not enter the mandatory value. Am I correct?
If this is what is happening, then you created an incomplete record. Try to use the set_item_property built-in to tell form the record for block ABC is new. You can do this in the same trigger that you are using to close the form. Maybe something like this:
go_block('ABC');
set_record_property(currect_record, 'ABC', STATUS, NEW_STATUS);
then
clear_form(no_validate) or exit_form(no_validate)

Similar Messages

FORM EXITS Vs FUNCTION EXITS

Hi folks
I am a little confused on FORM EXITS& FUNCTION EXITS...can anyone provide me what exactly is the differnce between these two. How we go about using these two in various scenarioes.
Thanks in advance.
Regards
Ram

Hi
There are 4 types of exits
like FUNCTIOn MODULE, MENU,FIELD and SCREEN exits
What is this form exits?
see the doc
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
To find a Exit.
Goto Transaction -- Find The Package
SMOD >f4>Use the Package here to Find the Exits In the Package.
Else if you Want to search by Application Area wise ,
There is one more tab to find the Exits in the Respective Application Area.
Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
Now Run ur Transaction to Check if it Triggers.
Thats it..
Suppose you need to find out all the user exits related to a tcode.
1. Execute the Tcode.
2. Open the SAP program.
3. Get the Development Class.
4. Execute Tcode SE84.
5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
6. Enter the Development class and execute.
Check out this thread..
The specified item was not found.
1. Type the transaction : system->status-> <PROG. NAME>
2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
3. Open CMOD utilities->SAP enhancements
EDIT->All selections
4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
5. The displayed list contains the enhancements names for the transaction You were looking for.
6. Create a project in CMOD and the code in default include->activate.
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.planetsap.com/userexit_main_page.htm
User-Exits
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/ab038.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.sap-basis-abap.com/sapab013.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
These links will help you to learn more on user exits.
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.allsaplinks.com/user_exit.html
www.sap-img.com/abap/what-is-user-exits.htm
Also please check these threads for more details about user exits.
Re: Screen exit
user exit and customer exit
user exit
1. Document on UserExits in FI/CO
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
2. Finding User Exits...
http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
3. List of all User Exits...
http://www.planetsap.com/userexit_main_page.htm
How to implement screen exit for a SAP standard transaction HOT
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
Reward points for useful Answers
Regards
Anji

Exiting form after being in query mode

Hi guys,
Having an issue with some forms after migrating from forms version 6i to 10g. Learning as I go along.
Forms which startup in query-mode seem to have an issue when closing - all have two blocks - one block is utilised through user query and the other (like a child) displays the query results and can be updated from here. If the user does not enter a query they can cancel it using exit_form which works fine.
After a query has been completed the system mode returns to 'normal' mode (which I can see through debugging by entering messages/pauses throughout the code). However when exiting the application breaks with error FRM-92100. I have had this problem before with regards to exiting forms but I got round this by having an open window (acting as a parent or root window) in the background which is not closable. Been tweaking the form all afternoon including using exit_form(no_validate) and other changes. By commenting out enter_query and execute_query commands the form closes as normal without issue which means it is related to query mode or something along these lines.
If anyone has any ideas or pointers on how to move forward with this it would be much appreciated.
Cheers,
Robin

Guys,
Thanks for the replies.
The form currently uses exit_form twice in order to close the query mode and I receive a message "query cancelled" to confirm this.
I have also tried - and retried for the benefit of confirming this - the code you have mentioned u3 - using it in the when-window-closed trigger. I chose <option> to be no_validate.
The main app is opened from a webpage. Forms are opened from a menu which is attached to all forms. The code that opens the forms is open_form (i.e. not call_form or new_form) for modal reasons.
The application is disconnected straight after exit_form is used - its as if coming out of query-mode to normal causes this as I said before closes gracefully when I remove the enter_query command.
As for the error message itself here is a fuller picture:
FRM-92100: Your connection to the server was interrupted. This may be the result of a network error, or a failure on the Server. You will need to reestablish your session.
Details...
java.lang.NullPointerException
at oracle.forms.handler.TextComponentItem.selectionChanged(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextComponent._fireSelectionChanged(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextComponent.select(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextField._selectAll(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextField.processFocusEvent(Unknown Source)
...AND SO ON!
Hope this gives a better picture of what's going on :)
Robin
update - There is a 'dirty' workaround to this problem - if i minimize the window (change its state in any way) after the mode is back from query-mode to normal THEN close the window it closes gracefully.
Edited by: Robin84 on Sep 10, 2008 10:03 AM

Form Builder (Forms 6i) exit without message when compiling a form module

Hi all,
i can't resolve problem with Form Builder since 2 weeks.
i have Forms 6i which always exit when i compile form module connecting
to a remote database (oracle 817). There is 2 remote database server 817 in our LAN.
However this happen only for one remote server, while the same form module connecting to another remote database (oracle 817) is well compile and work fine.
I configure a service name with Net8 Easy Config locate on <Oracle for Windows 95>, but the problem is the same. Can anyone suggest, what could be the reason for the problem.
Best regards.

Hi Experts,
We are getting the same issue. Our form builder crashes once we open our custom form
in form builder.
Server shows:-
Forms 6.0 (Forms Runtime) Version 6.0.8.28.0 (Production)
Form Builder shows:-
Forms [32 Bit] Version 6.0.8.11.3 (Production)
How to upgrade the form builder version?

URGENT -- Forms exit problem

Hi,
I am working with APS9i. I have forms in APS9i. I face problem when i call form b from form a. when i call for the first time form b opens and when i exit form b it comes back to form a but some times when i exit form b it closes all the previous forms.
kindly help

Thank you, Very much Sir. I also think that updating it to the latest patch will solve the problem. But were do i get the patch, I dont have any support contract with Oracle, nor any ID of metalink, If possible could u kindly send me the Patch in my following E-mail Id : [email protected] or [email protected]
Thanking u again
regards,
vinod kumar

Force exit form when I am in query mode.

I have created one button just launch Exit_Form built_in. Ok my forms exit, but when I stay in query mode, I need to click at button twice, first to abort query, the second time to exit form. How can I configure that to close my form automatically?
I have tried Abort_Query folling Exit_Form, but does not work as well.
Thanks all.

In the trigger that contains the EXIT_FORM check for if you are in ENTER_QUERY mode. If you are issue two EXIT_FORM otherwise one.

Exiting Form From Web

Hello,
I have deployed the form in web using OAS 4.0. I have created an html file to call the form.fmx from the server. My problem is that I am unable to come to this Html page after I exit the form.
Can Any one help me.
Thanks in advance

Add a Post-Form trigger to the form triggers with the following code:
Web.Show_Document('file:\<virtual dir>\Page.htm', '_self');
where the first argument is the URL for the web page you want to display and the second, '_self', says to display the page in the same browser instance. Look at the online doc for Web.Show_Document for alternatives.
One thing: if your web page automatically runs the form and you don't want that to happen on form exit, then you need to have a second, seemingly identical web page that doesn't automatically run the form and call that one in Show_Document.

Form exits when calling another form

I have a form that passes parameters to another form. When creating new records and then calling the other form, it works fine. However, when coming from a post query and then passes parameters to a new form, the form exits upon calling of the other form. What causes this? Thanks for your help. I am using Forms Developer 6.0
Edited by: user6656248 on Apr 14, 2009 8:30 PM

My form is intermittent, when creating new records, sometimes the other form is called and parameters are passed but sometimes nothing happens and there are no errors. But from post query, calling another form and passing parameters exits the calling form and the called form does not show up. This form calls another form and passes some parameters without problems but when I tried to call another one, those scenarios happen. I am confused because the codes on both my When-Button-Pressed trigger are 100% similar. I dont know why this happens on this one and NEVER on the other. I hope you understand my query. Thanks a lot for responding. Please help.
Here is my code:
DECLARE
form_id      FormModule;
pl_id      paramlist;
pl_name      varchar2(1000);
it_id      Item;
BEGIN
pl_name := 'temp';
pl_id      := get_parameter_list(pl_name);
     IF NOT ID_NULL(pl_id) THEN
     destroy_parameter_list(pl_id);
     END IF;
pl_id := create_parameter_list(pl_name);
add_parameter(pl_id,'L_OUT_DATE',TEXT_PARAMETER,TO_CHAR(:DAILY_OUTS.OUT_DATE,'DD-MON-RRRR HH24:MI:SS'));
add_parameter(pl_id,'L_DATE_IN',TEXT_PARAMETER,TO_CHAR(:DAILY_OUTS.DATE_IN,'DD-MON-RRRR HH24:MI:SS'));
     add_parameter(pl_id,'L_SUBSTATION_CODE',TEXT_PARAMETER,:DAILY_OUTS.SUBSTATION_CODE);
     add_parameter(pl_id,'L_BREAKER_CODE',TEXT_PARAMETER,:DAILY_OUTS.BREAKER_CODE);
     add_parameter(pl_id,'L_CIRCUIT_CODE',TEXT_PARAMETER,:DAILY_OUTS.CIRCUIT_CODE);
     add_parameter(pl_id,'L_REMARKS',TEXT_PARAMETER,:DAILY_OUTS.REMARKS);
     add_parameter(pl_id,'L_FREQUENCY',TEXT_PARAMETER,:DAILY_OUTS.FREQUENCY);
     add_parameter(pl_id,'L_OUTAGE_CODE',TEXT_PARAMETER,:DAILY_OUTS.OUTAGE_CODE);
     add_parameter(pl_id,'L_OUTAGE_SUBCODE',TEXT_PARAMETER,:DAILY_OUTS.OUTAGE_SUBCODE);
     add_parameter(pl_id,'L_WEEK_NO',TEXT_PARAMETER,:DAILY_OUTS.WEEK_NO);
     add_parameter(pl_id,'L_RADIO_GRP',TEXT_PARAMETER,:DAILY_OUTS.NEW_OUTAGE_GRP);
     add_parameter(pl_id,'L_RELAYS_ACT',TEXT_PARAMETER,:DAILY_OUTS.RELAYS_ACT);
     add_parameter(pl_id,'L_TRIP_CAUSED_BY',TEXT_PARAMETER,:DAILY_OUTS.TRIP_CAUSED_BY);
     add_parameterr(pl_id,'L_SCODE_TRIP_CAUSED_BY',TEXT_PARAMETER,:DAILY_OUTS.SC_CAUSED_BY);
     add_parameter(pl_id,'L_ACTION_TAKEN',TEXT_PARAMETER,:DAILY_OUTS.MEASURE);
:GLOBAL.BC := 1;
IF :daily_outs.out_date > sysdate +1 then
     MESSAGE('DATE/TIME-OUT IS GREATER THAN SYSTEM DATE. PLEASE CHECK AND ENTER NEW
DATE/TIME-OUT VALUE.', acknowledge);
     MESSAGE('DATE/TIME-OUT IS GREATER THAN SYSTEM DATE. PLEASE CHECK AND ENTER NEW
DATE/TIME-OUT VALUE.', acknowledge);
     RAISE Form_Trigger_Failure;
END IF;
IF :daily_outs.date_in IS NOT NULL AND :daily_outs.out_date IS NOT NULL THEN
     IF (:daily_outs.date_in - :daily_outs.out_date) <= 0 then
MESSAGE('DATE/TIME-IN IS LESS THAN OR EQUAL TO DATE/TIME-OUT. PLEASE ENTER NEW
DATE/TIME-IN VALUE.', acknowledge);
RAISE Form_Trigger_Failure;
END IF;
END IF;
OPEN_FORM('FRMSPM_DAILY_BRKRS_PARAM', ACTIVATE, NO_SESSION, SHARE_LIBRARY_DATA, pl_id);
END;

When ever using table of an different database forms exits

Hello
i am using FORMS6i,oracle 8i
i have two database A and B
i have created a forms in A database which is accessing
some table of database B.but when ever i open the form
in form builder and try to compile it exits.So every time
i have to create a local table in A which actually belong to
database B to compile the form.is their any easy process
to follow the above
Regards

It's definately worth applying a newer patch, say patch 17, then trying this again.
You get them from metalink.
Let us know what happens.

After query clear ADF search form

I have a adf search form with a date picker. When I push the search button I go to my view object class to change the query
String criteria3 = (String)vcr.getAttribute("Datenaiss");
if (attrs.getName()=="Datenaiss"){
if (criteria3 != null) {
criteria3="> '"+criteria3+"'";
vcr.setAttribute("Datenaiss", criteria3 );
The I receive the result on my jsp but in the field of my date I see now e.g. > '1992-01-17'
can you help me ?

If have found a solution to clear the search form
protected void executeQueryForCollection(Object object, Object[] object1, int i) {
// set the inputfields to uppercase
switchStringsViewCriteriaToUpper();
// execute the query
super.executeQueryForCollection(object, object1, i);
// clear the parameters
super.clearViewCriterias();
}

Want to close internet explorer window on exit form (10g)

i am using oracle 10g forms, want to close internet explorer window when exit form automatically.
Have alread tried calling html page at exit form and using closing window script for this, but didn't work.
Please help and describe in detail how to debuge and test every thing is ok
Aslam

Hi Aslam
Try following the instructions here
https://metalink.oracle.com/metalink/plsql/f?p=130:14:3767372347328447221::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,201481.1,1,0,1,helvetica
Worked a treat for me.
paul

Exit form and browser at one click

hello
can anybody here pls tell me how can i make a push button in oracle 9i form that will exit the form as well as the browser when it is pressed.
im using exit_form; trigger to exit the form. but in this way i need to exit the browser explicitly. is there any way to exit form and browser at once?
thanks in advance.

Exit form and browser at one click

When i'm in the music player function, and i turn my ipod to lanscape view, i start to roll the albums and then the ipod exit form the musicplaying suddenly -_- why? please help me

When i'm in the music player function, and i turn my ipod to lanscape view, i start to roll the albums and then the ipod exit form the musicplaying suddenly -_- why? please help me

Did you try to reset the device by holding the sleep and home button until the Apple logo comes back again?

Form exit in MV45AFZB.

Hi,
My requirement is the users need to validate documents created in the SD module to ensure that the correct CO object is used before the document is transferred to FI i.e. for particular company code if my G/L account number is starting with 4 then I should not pass the WBS element to G/L account and pop up a error msg, the error msg will be created in se91.
Now in which form exit I can use for this? or if i need to write my own form exit then where can i write my code?
This form exit which i should modify or create will be then assigned to a validation rule through tcode OB28
can any one help me with this?
null

hello,
i was just wondering what if i write a form exit in MV45AFZZ and then can use it in OB28 ? will do any harm?

Close IE when exit form

Hi how can i close IE when i click on the exit button on my form. At the moment i'm using 'EXIT_FORM;'.

Hi Jagadish,
If Francois' simpler solution isn't working for you, and you want to try the close.htm route, then you need to make sure that htm file is somewhere that the browser can get to it. Because I have a few other supporting files for my app - htm pages, images etc. - I created a new dedicated folder to store them, and mapped a virtual directory by editing <ORACLE_HOME>/forms/server/forms.conf.
If you look in that file, you'll see the syntax for other virtual directories already in place, but basically you add something like:
AliasMatch ^/forms/my_new_directory/(..*) "<ORACLE_HOME>/forms/my_new_directory/$1"
... replacing the <ORACLE_HOME> with the explicit path of your apps server home.
Drop your .htm file into the new directory; ignoring Forms for a moment, make sure you can access it directly using a URL like:
http://your_server.your_company.com:7781/forms/my_new_directory/close.htm
(If you access it successfully, of course, the browser will immediately shut down!)
Then use Web.Show_Document('my_new_directory/close.htm','_self'); - hopefully that should find it.
Incidentally, I'm working in separateFrame=false. And I had thought that calling Javascript directly from Web.Show_Document() was to be avoided - see e.g. Hide adress bar for security issue On the other hand, Francois is a man who usually knows what he's talking about!
James

Clear Form & Exit Form

Similar Messages

Maybe you are looking for