Commit in user exit

hi experts
during an idoc process i am trying to do commit after inserting data to a database table in include MV45AFZZ in a user exit. the commit statement causes the idoc process to fail.
how can i do commit in a way that won't fail the idoc process
tahnks
amit
Edited by: amit walden on Jun 18, 2008 8:38 AM

Hi,
commit statement in userexit,You should not do that.
After the user exits code is triggered, the transaction's own commits statements will commit the database anyway.
Regards
Kiran Sure

Similar Messages

How to activate or deactivate a user-exit based a specific condition

hi all,
i want to activate or deactivate(make it trigger) a particular user-exit based in a condition.
can i do that. if yes please tell me how.
can we use COMMIT in user-exits or BADI's.
Thanks & Regards,
Saroja.

Hello Saroja
The solution provided by Rich should be used for testing purposes only in the the reverted sense:
IF ( syst-uname ne '<specific user>' ).
RETURN.
ENDIF.
" Execute user-exit for specific user
However, for serious programming you should use a a better strategy. In principle, user-exits are either ON or OFF and, if they are ON, they are ON for all user which is usually not intended.
The following example shows a (possible) strategy how to execute user-exits based on specific conditions.
The SAP extension CATS0001 contains the component EXIT_SAPLCATS_001 with the following interface:
FUNCTION EXIT_SAPLCATS_001.
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(SAP_TCATS) LIKE TCATS STRUCTURE TCATS
*" VALUE(SAP_PERNR) LIKE CATSFIELDS-PERNR
*" VALUE(SAP_DATELEFT) LIKE CATSFIELDS-DATELEFT
*" VALUE(SAP_DATERIGHT) LIKE CATSFIELDS-DATERIGHT
*" VALUE(SAP_DATEFROM) LIKE CATSFIELDS-DATEFROM OPTIONAL
*" VALUE(SAP_DATETO) LIKE CATSFIELDS-DATETO OPTIONAL
*" TABLES
*" SAP_ICATSW STRUCTURE CATSW
*" SAP_ICATSW_FIX STRUCTURE CATSW OPTIONAL
INCLUDE ZXCATU01.
ENDFUNCTION.
The include ZXCATU01 contains only the following coding:
CALL FUNCTION 'Z_EXIT_SAPLCATS_001'
 EXPORTING
 sap_tcats = sap_tcats
 sap_pernr = sap_pernr
 sap_dateleft = sap_dateleft
 sap_dateright = sap_dateright
 SAP_DATEFROM = SAP_DATEFROM
 SAP_DATETO = SAP_DATETO
 tables
 sap_icatsw = sap_icatsw
 SAP_ICATSW_FIX = SAP_ICATSW_FIX.
This function module is just a copy of the exit function module in the customer namespace.
Let us assume that your condition at which the user-exit should be executed is that the employee (SAP_PERNR) belongs to a specific controlling area. Thus, we make another copy of the original exit function module and call this fm within the "general" customer-specific exit function module:
FUNCTION z_exit_saplcats_001.
*"*"Local Interface:
*" IMPORTING
*" VALUE(SAP_TCATS) LIKE TCATS STRUCTURE TCATS
*" VALUE(SAP_PERNR) LIKE CATSFIELDS-PERNR
*" VALUE(SAP_DATELEFT) LIKE CATSFIELDS-DATELEFT
*" VALUE(SAP_DATERIGHT) LIKE CATSFIELDS-DATERIGHT
*" VALUE(SAP_DATEFROM) LIKE CATSFIELDS-DATEFROM OPTIONAL
*" VALUE(SAP_DATETO) LIKE CATSFIELDS-DATETO OPTIONAL
*" TABLES
*" SAP_ICATSW STRUCTURE CATSW
*" SAP_ICATSW_FIX STRUCTURE CATSW OPTIONAL
" User-Exit specific for employees (SAP_PERNR)
" belonging to controlling area 1000
CALL FUNCTION 'Z_EXIT_SAPLCATS_001_1000'
 EXPORTING
 sap_tcats = sap_tcats
 sap_pernr = sap_pernr
 sap_dateleft = sap_dateleft
 sap_dateright = sap_dateright
 sap_datefrom = sap_datefrom
 sap_dateto = sap_dateto
 TABLES
 sap_icatsw = sap_icatsw
 sap_icatsw_fix = sap_icatsw_fix.
" User-Exit specific for employees (SAP_PERNR)
" belonging to controlling area 2000
CALL FUNCTION 'Z_EXIT_SAPLCATS_001_2000'
 EXPORTING
 sap_tcats = sap_tcats
 sap_pernr = sap_pernr
 sap_dateleft = sap_dateleft
 sap_dateright = sap_dateright
 sap_datefrom = sap_datefrom
 sap_dateto = sap_dateto
 TABLES
 sap_icatsw = sap_icatsw
 sap_icatsw_fix = sap_icatsw_fix.
ENDFUNCTION.
Finally, within the specific exit function module we define the condition when the exit should be executed:
FUNCTION z_exit_saplcats_001_1000.
*"*"Local Interface:
*" IMPORTING
*" VALUE(SAP_TCATS) LIKE TCATS STRUCTURE TCATS
*" VALUE(SAP_PERNR) LIKE CATSFIELDS-PERNR
*" VALUE(SAP_DATELEFT) LIKE CATSFIELDS-DATELEFT
*" VALUE(SAP_DATERIGHT) LIKE CATSFIELDS-DATERIGHT
*" VALUE(SAP_DATEFROM) LIKE CATSFIELDS-DATEFROM OPTIONAL
*" VALUE(SAP_DATETO) LIKE CATSFIELDS-DATETO OPTIONAL
*" TABLES
*" SAP_ICATSW STRUCTURE CATSW
*" SAP_ICATSW_FIX STRUCTURE CATSW OPTIONAL
IF ( <user BELONGS to CONTROLLING area 1000> ).
 " execute user-exit
ELSE.
 RETURN.
ENDIF.
ENDFUNCTION.
The alternative would be to place the entire coding including the conditions in the include ZXCATU01. However, in this case you can test the user exit only in the context of the transaction in which the user-exit is passed.
Using the strategy I have devised you are able to test the user-exit in general and the specific user-exits independent of the transaction. For example, if you are already working on 6.40 or higher then you could use ABAP Unit Testing for this purpose.
The same logic can be applied for BAdI where we can have only a single active implementation.
Finally, I hope to convince that it makes sense to spend some time into a reasonable strategy for implementing user-exits.
Regards
Uwe

Restriction of BAPI_TRANSACTION_COMMIT in User Exit

Dear Experts,
I am trying to create Sales Order upon saving Purchase Order through user exit EXIT_SAPMM06E_012 using BAPI_SALESORDER_CREATEFROMDAT2.But i got to know that ...we should not use BAPI TRANSACTION COMMIT in user exits as it leads to data inconsistency.....Can any one please let me know the other way other around..
Regards,
Kartheek.

Don't call BAPI_TRANSACTION_COMMIT or COMMIT WORK anywhere in your user exit coding that is all )
Really, SAP will save your sales order when the purchase order will be committed and saved.
It doesn't matter where the COMMIT happens so far it happens within same LUW. Now if you are calling BAPI to create sales order within EXIT_SAPMM06E_012 and don't do a COMMIT in anyway then the purchase order save will automatically commit it.
I think EXIT_SAPMM06E_012 is an ideal place to call the sales order create BAPI as it is just called before the PO is saved. If for some reason PO doesn't save and ROLLBACK occurs then your sales order also won't get created.

User Exit/BADI after database commit in VA01/VA02

Hi All,
Can you tell me an user exit/BADI in VA01/VA02 which I can utilize AFTER the database commit but still utilize the tables/structures like xvbap, xvbkd etc? Thanks.
Best Regards,
Avimanyu

Hi Sengupta,
Usually there are no user-exits after COMMIT.
What you need to do is register a call which will be executed after COMMIT, from one of the available user-exits.
To do this, SAP provides 2 methods:
1. PERFORM xxx ON COMMIT
2. Function Module with attribute "Update Module"
Check ABAP keyword help for more information for PERFORM xxx ON COMMIT.
<a href="http://help.sap.com/saphelp_46c/helpdata/en/34/8e72cc6df74873e10000009b38f9b8/frameset.htm">http://help.sap.com/saphelp_46c/helpdata/en/34/8e72cc6df74873e10000009b38f9b8/frameset.htm</a>
Hope this helps.
Regards,
Sumant.
PS: Reward points if this is helpful.

User Exit after the credit release by VKM1/VKM3 (database commit)

Hi All,
We have a requirement where once the credit manager releases the order from block through transaction VKM1 or VKM3, an e-mail should be triggered stating that the order has been released.
I tried putting the code in EXIT_SAPFV45K_001(include ZXVVAU03 ) which checks the status in vbuk-cmgst for value 'D' and send the mail.But there are 2 problems with this appproach.
1) The database table VBUK is not getting updated at this stage.So the CMGST value doesnt change. Even the last change value in VBAK( VBAK-CMFRE) is not getting updated.
I tried Implementing this solution as well.
"Perform f0001_download_data on commit"
but even then the tables are not getting updated at this point.
2) This user exit is called in transaction VA02 as well.so the mail is getting triggered whenever someone saves anything in VA02. Chances are thetre might be other transacyions using this exit like va01.
Can anyone help me with this scenario? Is there any other user exit which can be used or any other way this can be done ??
Thanks
Shwet
Edited by: Shwet Priy Anand on Jun 29, 2010 7:16 PM

Output determination requires both config and development and it's the standard method for triggering document-related communications (printing, faxing, emailing, etc.). When you block or release a sales order for credit check, you are changing that order and thus you can use output determination to trigger any type of communication related to the change. There is a standard output type and standard requirements for credit holds; you can create your own for credit releases. You can find thousands of posts on this site related to output determination and emailing and there is an abundance of documentation in the IMG (SD -> Basic functions -> Output control) and in the help files.
Don't put emails in user exits unless it's a last resort - there's no error handling and logging available.

User Exit / Badi after (inbound idoc) database commit

Hello Folks,
I want to know the User Exit/Badi that can be used after inbound idoc gets posted, as i want to use perform on commit statement.
Thanks & Regards,
Nishanth Kumar

Hi Sengupta,
Usually there are no user-exits after COMMIT.
What you need to do is register a call which will be executed after COMMIT, from one of the available user-exits.
To do this, SAP provides 2 methods:
1. PERFORM xxx ON COMMIT
2. Function Module with attribute "Update Module"
Check ABAP keyword help for more information for PERFORM xxx ON COMMIT.
<a href="http://help.sap.com/saphelp_46c/helpdata/en/34/8e72cc6df74873e10000009b38f9b8/frameset.htm">http://help.sap.com/saphelp_46c/helpdata/en/34/8e72cc6df74873e10000009b38f9b8/frameset.htm</a>
Hope this helps.
Regards,
Sumant.
PS: Reward points if this is helpful.

Commit statement in user exit

Hi All,
We found that while doing PGI , it takes some time to COMMIT the table VBUK. Due to which we are getting old values of VBUK-KOSTK field while executing select query at later point of time in the flow.
My question --
Can I use COMMIT WORK statement in user exit MV50AFZ1 --> FORM USEREXIT_SAVE_DOCUMENT so that all the related tables
get committed immediately.
Thanks
Saurabh

Hi Saurabh ,
Normally , you shoud not specify COMMIT stmt in any user exit , badi etc..
SAP has its own COMMIT statement while execuiting the standard transactions .
Addition of a COMMIT might lead to problems elsewhere .
Thanks
Supriya

MIGO BAdI or User-Exit - After Database Commit

Hello,
I'm looking for a BAdI or user-exit after database commit for MIGO posting. I want to create a FI document after MIGO posting.
I already tried MB_MIGO_BADI BAdI but system gives a short dump. So I have to find a exit or BAdI after database commit.
Thanks for helping in advance.
Regards,
Burak

Hello,
This issue solved.
I used MB_DOCUMENT_BADI / MB_DOCUMENT_UPDATE and it solved my problem.
FYI.
Regards,
Burak

Can it be used commit statement in user-exits?

Can it be used commit statement in user-exits?
How to badi is different from other enhancement?
What are the two default components systems automatically creates when we create a new badi?
What is the business object for purchase order?

Hi,
1) commit statement in userexit:
You should not do that.
After the user exits code is triggered, the transaction's own commits statements will commit the database anyway
2)You could say: BAdI = enhancement using interfaces
It is just the most up-to-date version of SAP's enhancement concept.
go thru this.
http://www.esnips.com/web/BAdI
http://www.allsaplinks.com/badi.html
New to Badi
Regards
Kiran Sure

COMMIT WORK within an user exit

Hi every one,
I got a lill question here, can i use COMMIT WORK (AND WAIT ) within a user
exit FM, if yes is do i need any thing extra. Please help.
Thanks in advance
Jahan.

Hi Jahan,
although your question has been answered, just a few words on COMMIT WORK.
During a LUW (logical unit of work, i.e. transaction) all changes of database records are done within a so-called rollback segment of the database. That means they are visible within the current LUW but invisible to other users.
This makes it easy to do all necessary changes to all tables step by step. And if any step fails, all changes can be thrown away. Thats what we call a rollback - A rollback will just dump the rollback segment.
The reason you should not COMMIT WORK in a user exit is simply you have no idea what other database changes have already been done and what other database changes may follow after the user exit. If in one of the following steps a severe error is detected, all prior changes cannot be rolled back. COMMIT WORK means that all changes still in the rollback segment of the database will be applied and finalized to the database. The rollback segment will also be dumped that there is no chance to find out details about the changes.
An Error message (Type E or A) will automatically finish the LUW without commiting the data in the rollback segment - implicit rollback.
The end of a report not caused by any error will commit the rollback segment to the database - implicit commit.
All function modules called IN UPDATE TASK will be executed in their own update process after COMMIT or DUMPED after rollback.
All form routines called as PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK will be executed only after explicit COMMIT WORK or ROLLBACK WORK.
The addition 'AND WAIT' just means that the next program statement is not executed before all update processes started with COMMIT WORK have finished.
The general rule derived from this can be:
Never do a commit or rollback in a process which is called by another process. The only place for COMMIT or ROLLBACK is at the end of reports and transactions using CALL ... IN UPDATE TASK or PERFORM ... ON COMMIT - if you call any functions you should be aware that function modules may initiate update calls and/or form calls ...ON COMMIT/ROLLBACK. An explicit COMMIT WORK at the end of a process (or ROLLBACK WORK in case of error) will be OK.
Regards,
Clemens

User exit to find sy-comm when user select a tab at item level data in VA02

Hi Gurus,
is there any user exit in VA02 in which we can find the command button pressed in the sale order line item data where we find sales A sales B .....and condition tab in the screen.
rewards for sure.
thanks

Dear Mandy,
How to find user exits:
Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT
If you know the Exit name, go to transaction CMOD.
Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.
You will now come to a screen that shows the function module exits for the exit.
3. Using Project management of SAP Enhancements, we want to create a project to enahance trasnaction VA01 .
- Go to transaction CMOD
- Create a project called ZVA01
- Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document.
Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed
Press Save
Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = '2155'.
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and craete a salesorder.
Finding the user-exits of a SAP transaction code
* Finding the user-exits of a SAP transaction code
* Enter the transaction code in which you are looking for the user-exit
* and it will list you the list of user-exits in the transaction code.
* Also a drill down is possible which will help you to branch to SMOD.
report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
 tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
 select single * from tadir where pgmid = 'R3TR'
 and object = 'PROG'
 and obj_name = tstc-pgmna.
 move : tadir-devclass to v_devclass.
 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.
 move : tadir-devclass to v_devclass.
 endif.
 endif.
 select * from tadir into table jtab
 where pgmid = 'R3TR'
 and object = 'SMOD'
 and devclass = v_devclass.
 select single * from tstct where sprsl eq sy-langu and
 tcode eq p_tcode.
 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.
 else.
 format color col_negative intensified on.
 write:/(95) 'Transaction Code Does Not Exist'.
 endif.
at line-selection.
 get cursor field field1.
 check field1(4) eq 'JTAB'.
 set parameter id 'MON' field sy-lisel+1(10).
 call transaction 'SMOD' and skip first screen.
*---End of Program
Best Regards,
Rajesh
Please award points if found helpful.

User exit/BADI AFTER the database commit in va01 va02

Hi All
I need an user exit/BADI AFTER the database tables are updated when save button is pressed on VA01/VA02, both these user exits are fired before that.
Regards
Badari

Check out all these exits
 SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
SDAPO001 Activating Sourcing Subitem Quantity Propagation

Packing data at delivery user exit or BADI time

I create a delivery and enter associated packing data (handling units HU), then save the delivery. At user exit time, the delivery header is available via XLIKP and the delivery items are available via XLIPS tables, but the packing data is not!
Now, program SAPMV50A has a table called CVEKP, whose structure is VEKPVB, the handling unit header, but this table is always empty.
I thought I had a solution: instead of putting my custom logic in user exit MV50AFZ1, I tested putting my logic in the "Delivery Publish" BADI. Supposedly, this one is executed after the commit work, and so I could then read table VEKP directly and get the handling units. No such luck! Unfortunately, at the time the BADI is executed, the VEKP table may or may not be updated. Even adding the WAIT option wasn't 100% effective.
But these attempted workarounds still leaves the big question unanswered: "Where are the handling units data stored during execution of transaction VL01 or VL02"?
Anybody know?

which BADI u have seen ?
what abt ur requirement ?
Regards
Prabhu

User-Exit for the Me22n

Hi,
I am Mohan. I faced on Problem with the User Exit. I write the user exit for the ME21n for PO Creation. While Creation of the PO the Purchase Requition is mandatory. it is working for the ME21n. But PO creation is another two ways is there. Those are ME22N (Purchase order---> Create) and ME23N
(Purchase order---> Create) for this case also my condition applicable but it is not working for this case. How to write the Code for this. by using Sy-ucomm also. but it is not working.
Please help me.
Regards,
Mohan

Following the user exit's related to ME22N transaction.
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
Regards.

User exit while saving Service Purchase Order

i want to update one z table from the Service PO, after saving. Hence i require , an user exit, which will give the details of the service tab , of the PO. I am not able to get any exit, where the details of the Service tab, of the transaction me22n.
Below is the screen of the Service tab of the purchase Order Screen :
 Line DeService numbShort text Quantity Uni Gross priceCr
 10 3000001 Sub-Con Recruitment Commissio91 DAY1,249.00 IN
 20 3000001 Sub-Con Recruitment Commissio91 DAY1,249.00 IN

hi,
check this out .
Transaction Code - ME21 Create Purchase Order
Exit Name Description
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
LMEKO001 Extend communications structure KOMK for pricing
LMEKO002 Extend communications structure KOMP for pricing
MM06E011 Activation of PReq Lock
No of Exits: 38
Kishi.

Commit in user exit

Similar Messages

Maybe you are looking for