User Exit in Contract & SA

Dear Experts ,
Can you please inform me the user exit name associated with Contract and Scheduling Agreement?
Regards,
Santosh

Hi
AMPL0001 -User subscreen for additional AMPL data (manufacturer part number)
LMELA002 -Adoption of batch number from shipping notification at time of posting of a goods receipt
LMELA010 -Incoming shipping notification: adoption of item data from IDoc
LMEQR001- User exit for source determination
M06E0004 -Changes to communication structure for release of purchasing document
M06E0005 - Role determination for release of purchasing documents
MEETA001 -Determination of schedule line type (backlog, immediate requirement, forecast)
MELAB001 -Generation of forecast delivery schedule: realization via creation profile
MEVME001 -Calculation of default GR quantity and over/underdelivery tolerances
MM06E001 -User exits for inbound EDI messages and outbound purchasing documents
MM06E003 -Number range and document number
MM06E005 -Customer fields in purchasing documents
MM06E008 -Monitoring of contract target value in case of release orders
MM06E009 - Relevant texts for "Texts exist" indicator
MM06E010 - Field selection for vendor address
MM06L001 -Exits for determination of ratings in vendor evaluation
MMAL0001-ALE source list distribution: outbound processing
MMAL0002-ALE source list distribution: inbound processing
MMDA0001 -Default values for delivery addresses
MMFAB001 -User exit for generation of releases
MRFLB001-Control items during release creation
LMEXF001 -Conditions in purchasing documents without invoice receipt
LMEKO002-Enhance communication structure KOMP for price determination
These are some enhancements which can be usedf in case of Contracts & Scheduling agreements, Some are applicable to Purchase orders also. Include document category logic in programming to stop affecting PO's
Thansk & Regards
Kishore

Similar Messages

User Exit in Contract -Very Urgent

Dear Experts,
We are using User Exit "M06E0005 - Role determination for release of purchasing documents" for some enhancement of release strategy for purchasing docs.
It is working fine for PO but in case of contract the exit is not firing. We wrote to SAP Service, They told that this user exit is not currently being supported in case of contract. I really have doubt in their comment as SAP documentation for the user exit is telling different things.
Can anybody used/experienced the same exit or any other exit for enhancement of release strategy for contract?
Please dont send the list of MM user exits, I need a specific answere.
Full points will be awarded for explanatory replies.
Regards,
Santosh

Hii..
It is better to use these BADIs to enhance MIGO..
MB_MIGO_BADI
MB_MIGO_ITEM_BADI
Check the Documentation of these BADIs in SE18
Implement the BADI in SE19.
reward if Helpful

User exit for Contracts in MM

Hi,
    what is the user exit or BAdi for contracts in MM.I need to add a screen in the header for ME31k,32k and 33k.
Thanks n Regards,
Avinash.

Here is a utility that will help you find user exits by transaction code. implement this program, execute it, enter your tcode, hit execute.
report z_find_user_exit no standard page heading.
tables: tstc, tadir, modsapt, modact,
        trdir, tfdir, enlfdir, tstct.
data : jtab like tadir occurs 0 with header line.
data : hotspot(30).
parameters : p_tcode like tstc-tcode obligatory.
at line-selection.
get cursor field hotspot.
check hotspot(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
call transaction 'SMOD' and skip first screen.
start-of-selection.
perform get_data.
perform write_list.
*       FORM get_data                                                 *
form get_data.
select single * from tstc
              where tcode eq p_tcode.
check sy-subrc eq 0.
select single * from tadir
            where pgmid = 'R3TR'
              and object = 'PROG'
              and obj_name = tstc-pgmna.
if sy-subrc ne 0.
    select single * from trdir
             where name = tstc-pgmna.
    if trdir-subc eq 'F'.
      select single * from tfdir
                     where pname = tstc-pgmna.
      select single * from enlfdir
                     where funcname = tfdir-funcname.
      select single * from tadir
                     where pgmid = 'R3TR'
                       and object = 'FUGR'
                       and obj_name eq enlfdir-area.
    endif.
endif.
select * from tadir into table jtab
             where pgmid = 'R3TR'
               and object = 'SMOD'
               and devclass = tadir-devclass.
select single * from tstct
          where sprsl eq sy-langu
            and tcode eq p_tcode.
endform.
*       FORM write_list                                               *
form write_list.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
    write:/(95) sy-uline.
    format color col_heading intensified on.
    write:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    write:/(95) sy-uline.
    loop at jtab.
      select single * from modsapt
      where sprsl = sy-langu and
      name = jtab-obj_name.
      format color col_normal intensified off.
      write:/1 sy-vline,
      2 jtab-obj_name hotspot on,
      21 sy-vline ,
      22 modsapt-modtext,
      95 sy-vline.
    endloop.
    write:/(95) sy-uline.
    describe table jtab.
    skip.
    format color col_total intensified on.
    write:/ 'No of Exits:' , sy-tfill.
else.
    format color col_negative intensified on.
    write:/(95) 'No User Exit exists'.
endif.
endform.
Regards,
Rich Heilman

User exit for contract start date in sales order change mode.

24.10.2008
Hi Gurus,
I need to disable the 'contract start date' (VEDA-VBEGDAT) field in Contract data tab at header and item level. Can someone suggest a user exit for the same ???
Regards,
Udaynath

Dear Udyanath,
Please check these User exits with the help of ABAPer
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document
processing are listed below.
USEREXIT_FIELD_MODIFICATION
     This user exit can be used to modify the attributes of the screen
     fields.
     To do this, the screen fields are allocated to so-called
     modification groups 1 - 4 and can be edited together during a
     modification in ABAP. If a field has no field name, it cannot be
     allocated to a group.
     The usage of the field groups (modification group 1-4) is as
     follows:
-   Modification group 1:   Automatic modification with transaction
         MFAW
-   Modification group 2:   It contains 'LOO' for step loop fields
-   Modification group 3:   For modifications which depend on check tables or on other fixed information.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document
header level. It is described in the section "Transfer of the
customer master fields into the sales document".
The user exit is called up at the end of the FORM routine
VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document
item level. It is described in the section "Copy customer master
fields into the sales document".
The user exit is called up at the end of the FORM routine
VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of
the sales document schedule lines.
The user exit is called up at the end of the FORM routine
VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer
master fields into sales document".
The user exit is called up at the end of the FORM routine
VBKD_FUELLEN.
I hope this will help you,
Regards,
Murali.

User exit for contract release order.......

Hi All,
I have a question...
when we create a sales order and type the sold-to party the system dispalys(pop-up screen) the open contracts against the customer. It is up to us wheather we can copy any one of the contacts into the sales order and create a release order or we can just cancel the pop-up screen and create a new sales order with out reference to a sales order.
HERE my requirement is as follows.
1) When a customer has open contacts and validity period we should make user to copy any one of the the existing contracts in the pop-up screen.
2) At the same time if the customer has got no contracts against him he should be allowed to cerate a plain sales order.
I have tried with user exit Change document & User exit Save document in include MV45AFZZ but our code (user exit) should fire before or at the time of pop-up screen(containing the open contracts against the customer) which is just not happening.
Has any one of you came across of any solution for this kind of scenario...
One last option i have got is to disable the close push button taking the access key and changing the standard code........but this will effect the other places where this close button is used.
Please let me know how to go about it.
Thanks in advance......for your valuable time & precious knowledge.
With regards,
Pavan

Have you tried applying code to EXIT_SAPLV46H_001 - Customer Function When Creating Item?
Or EXIT_SAPLV46H_002 - Customer Function for Partner Changes?

User exit for contracts

Hi All,
our requirement is as follows:
Whenever the price conditions in a contract is created or changed(me31k or me32k),the info record,schedule agreements and PO's should be updated with these conditions.
I would like to know which user exit or BADI can be used for this requirement.
Thanks for your time in advance.
ASA.

Hi ASA
check this LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt

Brief about enhancements and user exits

hai,
can any one tell me what are enhancements and user exits in sap sd,
their signifcance & configuration
regards
sriram

hi,
an example of user exit
In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the Target *** Qty required and the Target *** Date for a specific customer who was not sending *** Qty Received by him.
So for that specific customer we used the search term and added the same in the Data 4 field of the IDOC under segment E1EDK09.
There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating *** Issued and then find out the difference from Target *** Qty and get *** Qty Received for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
User exits in SD
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Pl reward if helpful.
Thanks
Sadhu Kishore

Access to Profitability seg data in contract through user exit

Dear All ,
I have a critical issue in my current project.
I have to post/create a contract in R/3 using custom Idoc type which is enhanced version of the standard Idoc type with two new fields for profitability segment data(TS product and Offering) for contract item.
The Idoc is calling BAPI_CONTRACT_CREATEFROMDATA and which in turn calls SD_SALESDOCUMENT_CREATE and I checked it is passing through MV45AFZZ,MV45AFZA,MV45ZB INCLUDES also.
Can anybody suggest me which user exit to be used to pass the idoc fields for profitability segment to the required work area(I dont know where,which table it gets saved) so that it gets saved in the line item.I tried COBL work area but those fields are not there.
Your help is appreciated.
Thanks
Soujash

I have used some user exits to replace fields on the profitability segment during order entry. The same process might work for your scenario.
You will have to add restrictions so it is only called during your IDOC processing and not for every SD transaction.
I used USEREXIT_CHECK_VBKD in MV45AFZB.
The current PA segment was read with function module RKE_GET_CHARS_FOR_PAOBJNR.
If it was different than what I needed, I replaced fields on VBAP and re-triggered PA processing with
PERFORM VBAP_PRUEFEN_ENDE(SAPFV45P).

User exit for condition records in purchasing contracts

I am looking for a user exit to track changes to condition records made in ME31K and ME32K (purchasing contracts) transaction. Any useful tips are welcome.
Thanks,
Shareen

Hello ,
Please check the below BADI defintion
ME_DEFINE_CALCTYPE
Method : DEFINE_CALCTYPE :Determine pricing type after changes to EKKO or EKPO
Hope it is helpfull .
Regards,

User exit or BADI for ME31K for create Contract

Hi,
I want that in Tcode ME31K when i create a contract, for a particular vendor and particular material only one contract should be allowed to create.
If i try to create a second contract with the same vendor and material it should not allow me to do that.
please let me know is any user exit or BADI is there to solve my problem.
and what should be my code for this?

hi,
try this BADI...
SMOD_MRFLB001 Control Items for Contract Release Order
Prabhudas

VA42 user exit to update contract start and end dates at Item level

Hi Experts,
                  I need to update contract start and end dates at Item level in 'VA42' transaction, for this i am using user-exit 'USEREXIT_FIELD_MODIFICATION' in the include 'MV45AFZZ'. i am able to display the data into item level through my coding but the data is not getting updated into 'VEDA'
Note: No need to change contract start date and end date in header level. Only at item level i want to change dates.
Thanks,
Sateesh.

Thanks For your reply Vikram,
      i tried with 'USEREXIT_MOVE_FIELD_TO_VBAP' user-exit earlier it self its not working. Can you suggest me any another way how we can achieve this functionality. modification of Contract start date and end date in only item level.
'USEREXIT_MOVE_FIELD_TO_VBAP':
FORM USEREXIT_MOVE_FIELD_TO_VBAP.
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(3) Form USEREXIT_MOVE_FIELD_TO_VBAP, Start                                                                                                           A
*$*$-Start: (3)---------------------------------------------------------------------------------$*$*
ENHANCEMENT 1 ZSD_CONT_DATE.    "active version
DATA : lv_var TYPE CHAR10.
lv_var = '0040000219'.
if sy-tcode = 'VA42'.
IF VBAK-VBELN EQ lv_var.
VEDA-VBEGDAT = '20140502'.
XVEDA-UPDKZ = 'X'.
VEDA-VENDDAT = '20140602'.
XVEDA-UPDKZ = 'X'.
ENDIF.
ENDIF.
ENDENHANCEMENT.

VA42 user exit to update contract start and end dates at header

Hi.
My requirement : In VA42, if a user changes a contract end date at item level, I want the change to be reflected at header level automatically.
I have looked in MV45AFZZ, USEREXIT_SAVE_DOCUMENT and USEREXIT_SAVE_DOCUMENT_PREPARE. I am unable to affect the contract end date in those user exits, whatever I put in VEDA-VENDDAT or XVEDA-VENDDAT or whateverVEDA-VENDDAT, does not have any effect on the actual contract dates.
Can anyone help?
Please note that we are running 46C.
Thank you.

Thanks For your reply Vikram,
      i tried with 'USEREXIT_MOVE_FIELD_TO_VBAP' user-exit earlier it self its not working. Can you suggest me any another way how we can achieve this functionality. modification of Contract start date and end date in only item level.
'USEREXIT_MOVE_FIELD_TO_VBAP':
FORM USEREXIT_MOVE_FIELD_TO_VBAP.
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(3) Form USEREXIT_MOVE_FIELD_TO_VBAP, Start                                                                                                           A
*$*$-Start: (3)---------------------------------------------------------------------------------$*$*
ENHANCEMENT 1 ZSD_CONT_DATE.    "active version
DATA : lv_var TYPE CHAR10.
lv_var = '0040000219'.
if sy-tcode = 'VA42'.
IF VBAK-VBELN EQ lv_var.
VEDA-VBEGDAT = '20140502'.
XVEDA-UPDKZ = 'X'.
VEDA-VENDDAT = '20140602'.
XVEDA-UPDKZ = 'X'.
ENDIF.
ENDIF.
ENDENHANCEMENT.

Need a user exit to modify the quantity schedules in a sales contract

Hi,
I am using ECC 6.0 with IS OIL. Need a user-exit to update the quantity schedule(table OIA05) in the sales contract VA42.
I have a new field called timestamp in the table OIA05 which needs to be updated with the timestamp value.
I tried the user exit MV45AFZZ in USEREXIT_SAVE_DOCUMENT_PREPARE and USEREXIT_SAVE_DOCUMENT to update the values. But the new values are not being reflected. Can you please help me in this regard.
Thanks,
Best regards,
Ajith

that will allow me to append an initial line with <accit> pointing to the line. Therefore I just have to modify <accit> and the new line will then have my changes?
Yep, that is exactly it. So after the APPEND statement, simply fill the fields of the <accit>.
append initial line to im_document-item ASSIGNING <accit>.
<accit>-field1 = 'Blah'.
<accit>-field2 = 'Blah'.
Regards,
Rich Heilman

User-exit/BADI to change Purchase Contract item field ??

Hello,
I need to update the Order acknowledgement field(EKPO-KZABS) for the Purchase contract via transaction ME32K.
I need to know if there is any user exit or BADI for the Purchase contracts (Outline agreement), so that this field KZABS can be updated while saving. I did not find any user exit so far in which line item is a export parameter. There is one BADI definition ME_PROCESS_PO_CUST but it is called only in case of Purchase Orders and not in the contracts. Please let me know if you have some idea how to do this.

check these exits....
EXIT_SAPMM06E_012
EXIT_SAPMM06E_013
EXIT_SAPMM06E_014
EXIT_SAPMM06E_006
EXIT_SAPMM06E_007
EXIT_SAPMM06E_018
EXIT_SAPMM06E_016
EXIT_SAPMM06E_017
vijay

Custom error message in user exit is giving Short dump

Hi All,
We have a scenario where in if any user try to create/Change/Delete particular types of contract in SAP system we have to issue error message
saying ZIN/ZIR contract creation/Change/Deletion is blocked in SAP. This has to be done from the web application. So we are putting below code
in user exit MV45AFZZ in the form USEREXIT_SAVE_DOCUMENT_PREPARE.
CONSTANTS: lc_vbcpic01 TYPE sy-uname VALUE u2018VBCPIC01u2019, u201CWeb application user ID
         lc_zin           TYPE vbak-auart VALUE u2018ZINu2019,
                     lc_zir            TYPE vbak-auart VALUE u2018ZIRu2019,
                     lc_text(32)    TYPE c VALUE u2018Check long text for more detailsu2019.
DATA: l_uname TYPE sy-uname.
CLEAR: l_uname.
MOVE sy-uname TO l_uname.
*If user ID is not the Web application ID then block the creation/Change/Deletion
IF   l_uname NE lc_vbcpic01
AND ( vbak-auart EQ lc_zin
OR    vbak-auart EQ lc_zir ).
MESSAGE e830(zv) WITH lc_text.
ENDIF.
This code is working fine while creating/Changing the contract i.e. Giving us error message so that user wonu2019t be able to create/change the contract.
But when we delete the contract from VA42, Control is coming to this message statement and is giving Short dump. Below is the error analysis of the dump.
Error Analysis:
During "Exit Command" processing, the program tried to send a " " message.
This is not allowed at this point in processing.
The program had to be terminated.
Screen name.............. "SAPMV45A"
Screen number............ 4001
If any one has come across such scenario/any work around for this problem please let me know your inputs. Your inputs are highly appreciated.
I am working on 4.6C version of SAP.
Note: When i issue information/Warning message contract is getting deleted after displaying the message.
Thanks,
Vinod.

I exactly replicated the same in DELETE_DOCUMENT also
I am getting the Dump. I tried with exit also , but it continued and deleted. To avoid deletion we have to use Leave program or LEAVE TO CURRENT TRANSACTION.
Delete Function is Defined as EXIT command. so it is not possible to give error message. To convice you i just copied demo program and raised the error message.
it is also giving the dump.
copy the demo program DEMO_DYNPRO_AT_EXIT_COMMAND and make this change , information to error .
MODULE cancel INPUT.
MESSAGE e888(sabapdocu) WITH text-001 ok_code input1 input2.
IF ok_code = 'CANCEL'.
    CLEAR ok_code.
    LEAVE PROGRAM.
ENDIF.
ENDMODULE.
and see...

User Exit in Contract & SA

Similar Messages

Maybe you are looking for