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?

Similar Messages

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;

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

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

Form Exits when compiling with database link

Dear All,
I am using forms 6i and Oracle 10 G .I am using a databaselink in the form.When I compile the form , it exits from the form Builder.
I am able to use the databaselink from SQL.
Kindly help
Thanks
Elsy
Kuwait
Edited by: Elsy on Dec 5, 2011 12:53 PM

In forms 10g. Tnsname is picked from application server from <oracle_home>\Product\OraMidTier10gR2\NETWORK\ADMIN
As you have forms6i , I expect your client machine should have tns enrty for the SID what you are using in creating databaselink.
~Lokanath

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.

User exit in MV45AFZB include

Hi experts,
I got a requirement like this .
To develop user exit to check if the sales order item is within warranty or not,
And then display a message for user action.
Background information and requirement:
When a lift is installed, the Warranty Period is stored in the material master characteristic. If there is a replacement, then the SAP Notification will trigger a Sales Order where the user will create the sale item. During this item creation, a user exit is required to check whether this new replacement should be covered by an existing sales order item warranty (i.e whether the same part has been replaced before and within the warranty period), and the search is by the sales code (ie. The sale order item eg.DEIN material), equipment number ( as represented by the Equipment number in the technical object section in the Sales order header) and subcode (as defined in the characteristic of the item) combination. If an existing item is found and the warranty is still valid (ie.Today - Sales Order itemss Service Rendered Date(that is manually entered by user)< Warranty Period), Then the system should display a message indicating that the sales order item should be crated in service order instead. Otherwise, prompt a message indicating that the user can continue to create the sales order item.
Basic Logic:
User Exit 1:
USEREXIT_MOVE_FIELD_TO _VBKD
1. Develop this user exit to get the Equipment Number from the Notification. The Notification number is retrieved from the Sales Order document flow.
2. Assign the Equipment number to the Sales Order Items Technical Information Equipment number field.
User Exit 2: USEREXIT_CHECK_ABAP
After user enters Sales Order Item, It triggers the user exit USEREXIT_CHECK_ABAP that the performs the following actions.
1. Get the current characteristic, Subcode, value, possibly using USEREXIT_GET_FIELD_FROM _SDCOM.
2. Using the same material number, retrieve the characteristic Warranty Period in the material master classification.
3. Using current sales order item material number and Equipment Number, get all sales order tiem in VBAP and VERIS02 where VBAP-MATNR = material number (which will retrieve the historical sales with same sales code) and EQUINO = Equipment Number.
4. Sort list found by Sales order items Service Rendered Date in descending order.
5. Repeat through this list of items until same Sub code is found.
· Get item characteristic Subcode.
· If Subcode = current Subcode and Today <(Service Rendered Date + Warranty Period)
o part is within warranty. Sales order: NNNNNN. Please create this item in Service Order as non-chargeable.
I got these USEREXITS in MV45AFZB and MV45AFZZ includes.
Can any one tell me what is the purpose of USEREXIT_MOVE_FIELD_TO_VBKD in MV45AFZB include
and USEREXIT_CHECK_VBAP in MV45AFZZ include? .
If i write code in above includes is it work out? OR is there any other way to achieve above requirement?
Can any one tell me Step by step process to achieve this.
Iam new to USEREXITs.
Points guaranteed
cheers
kaki

1. You have to get a key from SAP to modify the two includes in which the user exits are present.
2. You have to enter statement 'INCLUDE z**. ' in both user exits in the MV45* includes. Then save and activate the MV45** includes.
3. You have to figure out the code that carries out the functionality described in your specifications.
3. Write the code in includes Z** .
4. Now the code written by you will be executed when you run the relevant SD transaction
Message was edited by: Sudhir Bhate

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)

Closing Browser on Forms Exit

Can anyone tell me how to close the browser(IE or Netscape) when exiting a Forms 9i Application?
I call EXIT_FORM to exit the last form in the App but then have to manually close the browser.

In your Post-Form trigger you can use Web.SHOW_DOCUMENT('javascript:window.close()');
[Check the exact syntac of the Javascript command that's off the top of my head.
Note that the browser will pop up a dialog asking you if you want to close the browser unless the Browser window was opened using JavaScript in the first place.

Adobe Form Exit Button does not work

When I select a PCR from the Portal and review the Adobe Form - when I click on the exit button - it does nothing.
How can I fix that problem?

Hi
are you using standard MSS and Homepage frame work for PCR form or created your own iview in portal?
what is ther version of Software using?
thanks
Gopal

Close IE on Forms Exit

hi,
I have made a form with just one button on it with the following code
exit_form;
And then on the post-forms trigger I have included
web.show_document('javascript:window.close()','_self');
But still the Form gets closed off without closing the internet explorer, and what remains back is dark gray area.
Can someone sugguest a solution for this. I read on the forum that writing this code as above will for sure solve the issue. so then why doesnt it work in my case. Is there some specific setting I am missing. btw, I am running the forms on windows XP using Internet Explorer 6
Hamim

You need to put the javascript in a web page (onload event, <body> tag) and open that page with web.show_document.

MV45AFZB User Exit; FORM userexit_check_vbap

Hi experts,
I have implemented a user exit in MV45AFZB, the requirement is that when I change the sales order quantity of a line item for example previous quantity is 2000 kg and I change it to current quantity 1000kg, during debug mode i need to know the previous quantity 2000kg of that particular sales order item I changed. I looked at YVBAP but it is empty. Any inputs is appreciated.
Thanks.

Hi Mawi,
For this function : you have enhancement spots. click on spiral icon, goto edit enhancement- show implesit enhancements
then cursor will take you some enhancement spots, here you can find for vbap_old and vbap_new structures.
if it is useful, points please.
Thank you
srinu

VA01-VA02 : Error message in a user exit / MV45AFZB

I everyone,
i want to add an error message in the exit "USEREXIT_CHECK_VBEP" (MV45AFZB) but when i do so it displays the following abend message :
"Incorrect index structure for table XMVERF_POS
/0000000222 /000030 " (V1322).
just after mine.
do you have any idea ?
Xavier.
PS : I use SAP ECC5

Hi Xavier,
Here is the explanation when you get this type of error:
Short Text
Incorrect index structure for table &
Diagnosis
Internal error.
Procedure
Repeat the transaction.
If the error occurs and you have a CRM System connected to your ERP System, the document may have been archived in the CRM System.
If the error occurs again, inform your system administrator. If the error cannot be corrected, call the SAP Hotline directly. Describe which steps preceeded the error.
This is the long text description of that error message, so please let me know what next i mean whether you checked this and took the necessary action as explained above.
let me know if your problem still persists, else kindly close the thread.
Regards,
Yugandhar

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 exit in MV45AFZB.

Similar Messages

Maybe you are looking for