Exit by user

hi every body
i have a program that start procedure which will take time,what i want is to enable user
to stop this procedure during it is working
by click in cancel button,just like cancel report button in Report Builder.
null

Hi,
Assuming this is your requirement..
Store the MKPF & MSEG details in a Z table...when the material document is created..
Solution
1)
Create a function module Z_ADD_ZTABLE..Which should be remote enabled..
Give the parameter..
You can select on MKPF and MSEG with the material document number that has been just posted...The values are available in XMKPF-MBLNR..
Example.
SELECT SINGLE * FROM MKPF WHERE MBLNR = XMKPF-MBLNR.
****The return code will be zero..Means the record is available in the database.
2)
IN the BADI MB_DOCUMENT_BADI or in the USER EXIT...
CALL the function module in BACKGROUND TASK..
Example
CALL FUNCTION 'Z_ADD_ZTABLE' IN BACKGROUND TASK
Exporting
Hope this is clear..
Thanks,
Naren

Similar Messages

Diff b/w "Customer exits" and "User-exit"

Hi,
What is the difference b/w customer exits and user-exit and also please explain me what are the various types of customer and user-exits.
Thanks in advance.
Ramana

Hi,
Types of Exits
There are several different types of customer 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 items 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 screens 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 pulldown 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.
User exits:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-code-samples/userexits%20in%20a%20transaction.doc
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
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.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
http://www.easymarketplace.de/userexit.php
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
Check out these links too...
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
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
USER EXITS
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
****Reward points if helpful.
All the best

Can't exit single user mode

I frequently start in single user mode to run fsck -fy on my startup disk
and after running fsck -fy, I exit single user mode typing exit or logout.
Now after running fsck -fy, typing exit or logout the single user mode remains
and returns a line: -sh-2.05b#. I’m not adept enough to use single user mode
other than for running fsck -fy so I am stuck on how to end the single user mode. TIA
Eric

Some stories have happy endings and this is one of them.
After a little head scratching I dig out the Tiger install DVD
and repaired the permissions on the problem HD partition.
Reboot to the problem disk, enter correct network settings, and
now we even have a web to surf. Also we can exit single user mode OK.
Eric

Difference between customer exit and user exit?

hi experts
difference between customer exit and user exit?

These r the main differences between user exits and customer exits
1) user exits r subroutines where as customer exits r function modules
2) user exits r not upgraded where as customer exits r will upgrade
3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
4) customer exits r reusable where as user exits r not reusable.
Also:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
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
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
1. Previously there were only user-exits.
2. Then came the concept of customer-exits.
3. user exits were nothing but subroutines
FORM/PERFORM
called from standard programs.
4. The FORM defintion was placed inside
an empty include file.
5. So It was called EVERYTIME.
and we need to MODIFY/REPAIR the
standard include .
6. Then it came with concept of customer-exit
7. It consists of calling a FUNCTION MODULE,
which is called only if
the user-exit is ACTIVATED (other wise not called)
In this case, the code in put inside
a pre-defined Z include.
8. Functionality of both is same, howerver
we can note the following important differences
a) Customer exit is called only if activated.
(hence, it does not waste resources)
b) in customer exit, REPAIR does not happen
to the standard include.
Exits are basically the hooks whcih SAP has provided to add your own code.
User Exits: These are provided only SD module .
They are Empty subroutines with naming like USEREXIT_.
We need to have Access key to implement them.
Customer Exits: These are enhancement techniques.
There are defined in SMOD and implemented in CMOD.
Types of Customer exits: Function exit, Screen Exit, Menu exit.
User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
Customer Exit,
Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard 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.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
User Exits: allow you to add additional functions to the SAP standard.
Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
reward points if found useful
regards
palak

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 SAPs 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 SAPs 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 items 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 screens 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 companys 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.

Difference between customer exits and user exits

difference between customer exits and user exits

Hi,
USER EXITS->
1. Introduction:
User exits (Function module exits) are exits developed by SAP.
The exit is implementerd as a call to a functionmodule.
The code for the function module is writeen 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>
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
CUSTOMER EXITS-> t-code CMOD.
As of Release 4.6A SAP provides a new enhancement technique, the Business Add-Ins.
Among others, this enhancement technique has the advantage of
being based on a multi-level system landscape (SAP, country versions, IS solutions, partner,
customer, and so on)
instead of a two-level landscape (SAP, customer) as with the customer exits.
You can create definitions and implementations of business add-ins at any level of the system landscape.
To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
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
Regards
Kiran Sure

Difference b/w Customer exits and User Exits

Hi,
Can anybody explain diff b/w user exits and customer exits .
How to find out and Impement the coding ..
Thanks Advance
Rohan.A

Hi Rohan,
Check this matter , this may be helpful to you.
CUSTOMER EXITS
The enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard 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.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
 They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
 They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System.
User exits :
1. Introduction
2. How to find user exits
3. Using Project management of SAP Enhancements
1. Introduction:
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen 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>
Example:
The program for transaction VA01 Create salesorder is SAPMV45A
If you search for CALL CUSTOMER-FUNCTION i program
SAPMV45A you will find ( Among other user exits):
CALL CUSTOMER-FUNCTION '003'
exporting
 xvbak = vbak
 xvbuk = vbuk
 xkomk = tkomk
importing
 lvf_subrc = lvf_subrc
tables
 xvbfa = xvbfa
 xvbap = xvbap
 xvbup = xvbup.
The exit calls function module EXIT_SAPMV45A_003
Hope this is helpful.
Reward all the helpful answers.
Regards

Change Confirmed Qty in Sales Order User exit/ATP User exit

HI
We have a requirement to change the ATP Qty for certain meterials & Order Types duing sales Order User exit(FORM USEREXIT_MOVE_FIELD_TO_VBEP.? ) or ATP User exit.( ATP...OUT?).
Is this ok to update the XVBEP in FORM USEREXIT_MOVE_FIELD_TO_VBEP of MV45AFZZ ?
Our requirement will be like this, for one order type ZSAL( and for certain Materials) we need to reserve 4 qty, if any order comes with 10 qty and the confimed qty is only 6( total available stock at present) , then we should only confirm 2 qty for the other order type( For Non ZSAL Order Type), and reserve the 4 QTY for ZSAL Order Type.
If there are multiple schedule lines for an Item, we need to reduce the qty equally( as possible) from all schdule lines.
i.e. date1 qty 4
date2 qty 6,
in this case we should confirm Date1 QTY 2, date2 qty 4, so that the remaining 4 will be reserved for ZSAL Order type.
Whats the Best way to achieve this ?
Edited by: agrud agrud on Sep 8, 2011 4:01 AM

Hi Agrud,
Did you check the possibilities with configuration.If it is not possible with configuration then you can use that exit.Before i used this but only to display not to change any thing.
Regards,
Madhu.

MC93 menu exit or user exit

Hello am wrking for MC93 tcode i need to button or from menu exit i need to call one report when entering values.....i found one
menu exit MCP20003 IN tht i added menuexit function code at run time it is not highlighed.if any one plz help me out.

Hi,
der r total 17 exit.
J_3RSINV
SDVFX001            User exit header line in delivery to accounting
SDVFX002            User exit for A/R line in transfer to accounting
SDVFX003            User exit cash clearing in transfer to accounting
SDVFX004            User exit G/L line in transfer to accounting
SDVFX005            User exit reserves in transfer to accounting
SDVFX006            User exit tax line in transfer to accounting
SDVFX007            User exit: Billing plan during transfer to Accounting
SDVFX008            User exit: Processing of transfer structures SD-FI
SDVFX009            Billing doc. processing KIDONO (payment reference number)
SDVFX010            User exit item table for the customer lines
SDVFX011            Userexit for the komkcv- and kompcv-structures
V05I0001            User exits for billing index
V05N0001            User Exits for Printing Billing Docs. using POR Procedure
V60A0001            Customer functions in the billing document
V60P0001            Data provision for additional fields for display in lists
V61A0001            Customer enhancement: Pricing
Hope it helps.
/sachinkumar.

FB70 Function Exit or user exit

Hello!
I have a requirement in which I need to assign customer invoice smartform in FB70 transaction. When the user will press save button then the data should go to spool request.
Is it possible by using any Function Exit or BADIs. If yes please tell me the Exit or BADIs name.
Your help will be appreciated.
Ashvender
[email protected]

solved

User exit on User entered Variable

Is it possible to run a user exit that will filter for a particular date, based on what the user enters. For example if the user enters the day May 20, 2008. Can instead filter the report for May 18, 2008 (Always Sunday). How do I go about doing this? I have the code to find the Sunday date, just having difficulty getting it to executing after the user has entered a date.

Hi Vendant
You will need 2 variables, the one the user enters the date against and another customer exit variable executed in step 2 that takes the input date and returns it to sunday.
This CMOD code might help, you may need to tweek it to cater to the date format you use
CASE i_step.
WHEN 2.
CASE i_vnam.
WHEN 'Tech name of customer exit var'.
DATA: loc_var_range LIKE rrrangeexit,
l_s_range TYPE rrrangesid.
DATA: i_t_var_rec LIKE LINE OF i_t_var_range.
DATA: l_text(10) Type C.
READ TABLE i_t_var_range INTO loc_var_range
WITH KEY vnam = 'tech name of first date var'.
use your code to find sunday here on the loc_var_range-low, this is the value the user entered.
you will need to assign loc_var_range-low to a variable like l_text as you cant manipulate it directly
l_text = loc_var_range-low.
l_s_range-low = the result of your find sunday code.
l_s_range-high = ''.
l_s_range-sign = 'I'.
l_s_range-opt = 'EQ'.
APPEND l_s_range TO e_t_range.
ENDCASE.
ENDCASE.
Hope this helps
Cheers
Josh

MD11 Screen Exit/BADI/ User Exit For Adding Custom Field

Hi,
I have a requirement wherein i need to add one custom field on MD11 Screen.
I cheked but coudnt find any relevant Exit or BADi for doing this.
Doen Anybody knows how to add Custom Field on MD11 Screen.
Thanks in Advance.
Nitin

Hi,
Check....
Exit Name               Description
LMDR2001               User exits restr. profiles of opt. pur.ord.-based load bldg
LMDZU001               User exits in additional planning
reward points if useful....
Regards
AK

Field Exit or User Exit for Maintenance Order field.

Dear All,
we need an field exit or an user exit for order(AUFNR)field in PM module.
The Client wants that the value of this field should be validated and for certaion condition an error message should be given while saving an invoice for this order.
Kindly provide the user exit ..
Its urgent.
Thansk in advance ..
regards
Ajay.

Implement Field Exit within program
For this example I am using dta element 'EBELN' from table EKKO.
Step 1: Execute program 'RSMODPRF', entering the data element of the field
Step 2:Create function module when prompted, and add you code to the source section using the parameter 'INPUT' as the field value you are checking
Step 3:      Save and activate Function and execute transaction 'CMOD'.
Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
Step 3:      Save and activate Function and execute transaction 'CMOD'.
Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
Step 5:      Enter data element
Step 6:      Save and activate
Step 7: Execute program 'RSMODPRF' again but this time leave data element field blank. Step 8: Select the checkbox for the data element you have just created and choose option: Field exit->Activate This will now be active for all instances of this data element, but you can assign specific program and screen combinations by pressing the 'Assign prog./screen' button. You can also change the code you entered in the field exit function module by pressing the 'Edit FM' button.
regards
vinod

User exit for user status

Hi,
Please let me know if there is any user exit that triggers upon updating the user status in the status tab of the sales order.
I had used the exit 'Move_field_to_vbep' and 'USEREXIT_SAVE_DOCUMENT'
but they are not getting triggered on saving the sales order.
Regards,
Srirupa.

You can check with include RV45PFZA and USEREXIT_SET_STATUS_VBUK and USEREXIT_SET_STATUS_VBUP .
Hope it helps.
Reward if it is useful.
Thanks,
Srinivas

Search help exit while user double click

Hi,
As it was done earlier but while test facing some issue,Double clicked value from the output is not returned to input screen whatever thevalues only last value is returning to the screen
please ooverview some of my code,
IF callcontrol-step = 'DISP' or
    callcontrol-step = 'SELECT' or "or "AND
   callcontrol-step = 'RETURN'.
* EXIT.
   SELECT *
   from /ain/dm_loct
   into table lt_loct.
   IF sy-subrc eq 0.
     READ TABLE shlp-INTERFACE into ls_interface INDEX 1.
     if ls_interface-shlpfield = lc_gln. "'GLN'.
       lv_cp_gln = ls_interface-value.
     ENDIF.
     loop at lt_loct INTO ls_loct.
       CALL FUNCTION '/AIN/UI_MAPPED_LOC_ID_GET'
         EXPORTING
           IV_LOC_GUID = ls_loct-loc_guid
           IV_ID_TYPE = lc_fmcg "'FMCG'
         IMPORTING
           ET_VALUE    = lt_value.
*         ET_RETURN   =
       READ TABLE lt_value into ls_value with key element = lc_gln.
*    'GLN'.
       if sy-subrc = 0.
         ls_loc_gln-GLN     = ls_value-element_value.
         ls_loc_gln-locdesc = ls_loct-locdesc.
         APPEND ls_loc_gln to lt_valuex.
       endif.
       REFRESH lt_value.
     ENDLOOP.
     endif.
*-- Mape output data
if callcontrol-step = 'DISP' OR
    callcontrol-step = 'SELECT'.
       IF lv_cp_gln = '' AND lt_valuex IS NOT INITIAL.
         CALL FUNCTION 'F4UT_RESULTS_MAP'
           EXPORTING
*           SOURCE_STRUCTURE   =
             apply_restrictions = gc_true "'X'
           TABLES
             shlp_tab           = shlp_tab
             record_tab         = record_tab
             source_tab         = lt_valuex
           CHANGING
             shlp               = shlp
             callcontrol        = callcontrol
           EXCEPTIONS
             illegal_structure = 1
             OTHERS             = 2.
*      endif.
*        exit.
       Else.
         refresh: record_tab[],lt_final.
         LOOP at lt_valuex into ls_loc_gln where gln cp lv_cp_gln.
           ls_loc_glnx-GLN =    ls_loc_gln-gln.
           ls_loc_glnx-locdesc = ls_loc_gln-locdesc.
           APPEND ls_loc_glnx to lt_final.
         ENDLOOP.
         IF sy-subrc eq 0 and lt_final is NOT INITIAL.
           CALL FUNCTION 'F4UT_RESULTS_MAP'
             EXPORTING
*             SOURCE_STRUCTURE   =
               apply_restrictions = gc_true "'X'
             TABLES
               shlp_tab           = shlp_tab
               record_tab         = record_tab
               source_tab         = lt_final
             CHANGING
               shlp               = shlp
               callcontrol        = callcontrol
             EXCEPTIONS
               illegal_structure = 1
               OTHERS             = 2.
         else.
         ENDIF.
         IF record_tab[] is INITIAL.
           message 'No values Exist' type 'S'.
         ENDIF.
       endif.

sorry only first value is going to input screen

Exit by user

Similar Messages

Maybe you are looking for