User Exit RV60AFZZ not Triggered When Processing IDOC

Hi,
I'm writing to seek some advice on why is the user exit RV60AFZZ not getting triggered when I do a vf01 bdc inside my inbouund IDOC function module. But when I try SHDB the user exit is getting triggered normally.
Thanks,
Mawi

Hi,
Yes I'm creating invoice using delivery orders, inside the idoc function module I'm using bdc call transaction vf01 but somehow it does not trigger the user exit.
But when I do manual vf01 in sap, the user exit is getting triggered.
I cant figure out why this is the behavior of sap.
Regards,
Mawi

Similar Messages

User exit which gets triggered when a line item is deleted in va02

Hello all,
I am unable to find a User exit which gets trigerred when i delete a line item from va02.If I use the User Exits for saving data in Include MV45AFZZ the screen field VBAP-POSNR for line item is not getting accessed.All i need to compare the line item texts. Which means if any of these texts change then i need to write my logic. But the screen field name for all the texts is the same.Please guide me.

Hello,
Whever you perform any actions on the line item, we have the user exit in MV45AFZZ, userexitxvbap. Whenever the the item is deleted the UPDKZ value in XVBAP value is set to 'D', else since you are using the transaction VA02, any change is recorded in YVBAP(for old values) and XVBAP(for new values), so using this two internal table you can write any necessary logic.
BR
Sudhakar.

Which user-exit or BAPI triggered when a schedule line is changed

Dear All,
Does anyone know which user-exit, enhancement or BAPI is triggered when we do change on schedule line item?
Let's say, I have two line schedule line item, then I do change for delivery date. After triggered "Item Availability" button, system will accumulate confirmed Qty on first line and second line into first line. And then the second line will remain zero.
I need to know, which enhancement or user exit or any standard FM do this process.
I searched, but not found any user exit or enhancement that will go through.
Best regards,
Dinivian.

Hi,
For MFBF there are sollowing user-exits....
XMRM0001 - Backflushing in Repetitive Manufacturing.
PTRM0001 - For lead column in REM planning Table.
SAPLRMPU - Customer Exit for Article Staging.
Reward points if useful....
Regards
AK

User exit name which triggers when a save button is pressed in CJ20N

Hi, does anyone knows which user exit is called when press the 'SAVE' button in CJ20N transaction.
Thanks

hi,
Below are the list of user exits available
for cs02.
PCSD0001 Applications development R/3 BOMS
PCSD0002 BOMs: Customer fields in item
PCSD0003 BOMs: Customer fields in header
PCSD0004 BOM comparison
PCSD0005 BOMs: component check for material items
PCSD0006 Mass changes user exit
PCSD0007 Check changes in STKO
PCSD0008 WBS BOM: Customer-specific explosion for creating
PCSD0009 Order/WBS BOM, determine URL page
PCSD0010 Order/WBS BOM, determine explosion date
PCSD0011 Knowledge-based order BOM, parallel update
PCSD0012 Customer - Mat. number/mat. number during material change
PCSD0013 Customer-specific processing of an explosion for BOM rowser
Hope this helps !!
Cheers
Alfred

User exit name which triggers when a save button is pressed in cs01

Hi Gurus,
Can anybody tell me what is user exit which will trigger for a save button in tcode
CS02
Regards
Yathish

hi,
Below are the list of user exits available
for cs02.
PCSD0001 Applications development R/3 BOMS
PCSD0002 BOMs: Customer fields in item
PCSD0003 BOMs: Customer fields in header
PCSD0004 BOM comparison
PCSD0005 BOMs: component check for material items
PCSD0006 Mass changes user exit
PCSD0007 Check changes in STKO
PCSD0008 WBS BOM: Customer-specific explosion for creating
PCSD0009 Order/WBS BOM, determine URL page
PCSD0010 Order/WBS BOM, determine explosion date
PCSD0011 Knowledge-based order BOM, parallel update
PCSD0012 Customer - Mat. number/mat. number during material change
PCSD0013 Customer-specific processing of an explosion for BOM rowser
Hope this helps !!
Cheers
Alfred

User Exit which is triggered when we do the posting to accounting

Dear Guru,
Can any one provide list of User Exits which are triggred while Posting in accounting happens via MM transaction?
Regards,
Sandeep

Hello
Go through the link
http://www.easymarketplace.de/userexit.php
Regards

User Exit EXIT_SAPMQEVA_003 Not Triggered

Dear All,
i am using EXIT_SAPMQEVA_003 to change Next inspection Date but this is not trigered in any Transaction of QM.
Pl kindly give solution ASAP.
Thanks and Regards,
Navin

Hi,
This EXIT is triggered only for 09 type of inspection lot (recuring inspection).
In Form WIEDERKEHRENDE_PRUEFUNG , is line with check qals-herkunft eq hk_wiederkehr.
qals-herkunft -> insp. lot origin
hk_wiederkehr is declaration with initial value 09
HK_WIEDERKEHR
LIKE QALS-HERKUNFT
VALUE '09',
For other insp. lot origin, You have to use other EXITS.
Hope this helps...

Variable user exit EXIT_SAPLRRS0_001 not called when I execute my query

Hi *,
I have created a variable in my query. Corresponding to that, I have written an exit in EXIT_SAPLRRS0_001. Wanted to debug this exit but unsuccessful.
I put a breakpoint in "IF i_step = 2." and started running the query. I thought that the point of execution will be hated at my breakpoint so that I can check my logic.
But the query simply directly executes. Where is the fault ? What needs to be checked ? Is the exit being called? My debugging technique is right ?
Will assign points for suggestible remedies.
Regards,
Srinivas

Hi !
Case 1.
your cmod project may not be activated.
a. Go to the cmod "editior" go to change mode and activate your code....
b. press back button once ...
c. continue to press activate button at every step till you come to cmod initial screen ...
At last when you are at cmod initial screen ... press activate again ....
This is very important as our cmod code (project) should be activated at every level ...
Case 2.
If it still does not work ... try using a break point just before the code segment ( case statement or if statement i.e. case 'i_vnam' etc .... ) and try to debug....
Hope it helps ....
Regards
Anshul

For a PO with item catagory S user exit was not triggering

HI SDN,
I wrote a code for invoicing plan in EXIT_SAPLMRMP_001 for block the payment with INVOICE VERIFICATION block .
it is working fine for a PO with item catagory Blank
and not working for item catagory S.
please suggest me is there any solution for this?

y

User-exit EXIT_SAPLSPOR_001 not executed (filter spool requests)

Hi,
The default SAP functionality provided to control the output controller functions via auth. objects S_SPO_DEV, S_SPO_ACT & S_ADMI_FCD does not do what we would like to do.
There's a user-exit available to implement some additional code: SPOOAUTH / EXIT_SAPLSPOR_001.
I've activated SPOOAUTH via CMOD and added a record in table TSPOPTIONS (AUTHORITY, value CUSTOM) which was mentioned in the documentation of the function module.
No other changes were made.
However, this user-exit is not called when I start trx. SP01.In the selection screen I choose to show all spool request from all users for a specific time period. According to the documentation this should trigger the user-exit.
Now the funpart begins:
I've debugged SP01 and found that FM RSPO_CHECK_JOB_PERMISSION contains:
       IF INIT IS INITIAL.
         data: v like tspoptions-value.
         call function 'RSPO_OPTION_GET'
           exporting
             name                = SPOPT_AUTH
           IMPORTING
             VALUE               = v.
         if not v is initial.
return value of v should be CUSTOM. However it is empty -> skips the user-exit.
The check in FM RSPO_OPTION_GET contains:
ALL 'RSPO_CACHE_CONTROL' ID 'AREA' FIELD 'OPTION'           ID 'OP'
FIELD 'GET'
                         ID 'NAME'
FIELD NAME
                         ID 'VALUE'
FIELD V.
if sy-subrc ne 0.
   perform write_trace1 using 'RSPO_OPTION_GET %s failed\n' name. "#EC NOTEXT
   select single value from tspoptions into v where spoption = name.
Field NAME = AUTHORITY
Field V    = empty
Return = 0 -> skips user-exit.
Have I overlooked something?
Any help would be welcome.
Kind regards,
Mark

Hi Mark,
Could be that the option value is being picked from cache/buffer (old value). You can restart the system and verify.
Also, after putting a break-point in FM RSPO_OPTION_GET, you can edit the value of 'v' in debugger and set it to CUSTOM, just to check whether the user-exit gets executed in this case.

ChaRM: Mail not triggered when current user = mail receiver?

Dearl all:
     Ive noticed that mails are not triggered when the user who is processing a document is the same who will receive it. Is there any way to deactivate this functionality?
Thank you very much,
Federico.

Hi Miguel, how are you?
      I think it is a nice feature not sending a mail when the user who is changing the status in the one who would receive the mail in that next status. But Im in the testing pahse of implementing SOLMAN and I would like to know if this is a real feature or a flaw, and besides I would like to turn off this possible feature, just for the testing phase. This is not a big deal anyway.
    By the way, I also notice that if there is a partner assigned multiple times to a document, it doesnt trigger the mails as expected.
Best regards,
Federico.

LT09 - Transfer Order User Exit is not getting trigerred though its active

Hi,
I am trying to assign the enhancement : MWMTO001
( Enhancements for end of transfer order generation )
which contains the user exit component : EXIT_SAPLL03T_001
I have created a project in CMOD and assigned the enhancement.
When I execute the TCode LT09 for transfer order, I noticed that this exit is not getting trigerred ...
I need to call a smartform whenever we save the data in the T-code LT09.
Am i using a wrong Exit ? Please help me to find out why this exit is not getting triggered though its activated ....
Thanking you in advance..
Nagasubramanyam.

Hi
Thank you for reply.
According to 1st scenario prgm is activated & also activated enhancement in CMOD.
According to 2nd scenario, can u suggest how to find out the correct exit...
Actually I written a print prgm in include of EXIT_SAPLL03T_001 & designed SMARTFORM for that...
if I do process thru LT09 transaction & save that SMARTFORM should be triggered which is not happening...I put break points & tried but the exit is not triggering.
pls suggest how to find out the correct exit of LT09 .
Thanks&Regards
NagaSubramanyam.

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
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
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
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.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Workflow not triggered when i have changed the PO

Hi,
We have custom fields (Price) in PO Header as well as in item. when we update in header the price should get distributed to items.
we have custom workflow evernt (changed) to update the items if user change in header. But the issue is if user changes the items and save the po, it is not updating immediatly. after we come back to Purcahse Order and save the purcahse order again then it updates the table.
Is there any reason why the event is not triggered when the PO was changed initially.

Hello,
"We have custom fields (Price) in PO Header as well as in item. when we update in header the price should get distributed to items. "
If you update a price in the header, how/why would that be distributed to the items? Is this a total price of the whole PO? Why not just have it in the header?
"we have custom workflow evernt (changed) to update the items if user change in header."
OK. Strange, but OK.
"But the issue is if user changes the items and save the po, it is not updating immediatly"
I thought it was supposed to happen when the users changed the header, not the items.
If you really have a workflow to update the items when the header is changed, then maybe it's not succeeding if the PO items are locked, eg by having them on your screen. Did the worklow actually start? Any error messages?
rgards
Rick Bakker
hanabi technology

User exit that gets triggered at the press of 'Enter' in IW42

Hi,
Is there any user exits that gets triggered at the press of Enter key in PM order confirmation IW42 transaction. Basically the requirement is to give a customized message at the order confirmation screen when the enter key is pressed.
Regards,
Prabaharan.G

Hi,
You may try the following enhancement points and exit respectively.
CMFU0001 E EXIT_SAPLCMFU_001
CMFU0002 E EXIT_SAPLCMFU_002
Pls reward points if useful.
Regards,
Renjith Michael.
Edited by: Renjith Michael on Jan 12, 2008 12:57 PM

User Exit RV60AFZZ not Triggered When Processing IDOC

Similar Messages

Maybe you are looking for