Obsolete User Exit's n BADI's

Hi,
Where can I get a list of Obsolete User Exit's n BADI's when I am upgrading a system from 4.7 to ECC6.0
Also, what is the way forward for dealing with the obsolete exit's n badi's. i.e. how can they be changed to make them compatible with ECC6.0 version?
Thanks,
Ajay.
Edited by: ajay singh on Dec 11, 2009 8:16 AM

Hi!
In most of the cases obsolete exits and badis are working correctly, without any additional coding or modification.
However they are marked as obsolete by SAP, because they will stop using they in the far future, and there are much more useful and more modern ways to handle the same problem.
This means, you don't have to modifying all obsolete stuffs in a big haste until the end of the year, but you have to avoid using them in new developments, and you only have to modify them if they cause problems.
Regards
Tamá

Similar Messages

User-Exit OR a BAdi for the Purchase order create.

Hi,
I am looking for a User-Exit or a BAdi which is fired when the Purchase order is being created in the SRM server via Web template. The requirement is as follows:
There is a flag(Check box) at the the item level, Basic Data tab. This flag is called as Unlimited Overdelivery Allowed. It is with the tolerances field. Now I want this flag to be always set for a PO of a material of certain type.
Can anyone tell me which User-Exit OR Badi I should use to always set this flag?
The Technical field name is UNLIMITED.
I tried a lot but could not get any.
Regards,
Deepak.

Hi Deepak,
Did you try doc_change badi? THis badi is available in all the bus objects.
thanks,
Ashwin

User exit or a badi for checking the vendor email id in me22n on me29n

hi all,
can anybody suggest me a user exit or a badi for checking the email id of the vendor in me21n or me22n or me29n.
i.e. a user exit or a BADI which gets hit either at the time of creation or release of a purchase order.
plz suggest me a solution its urgent.
regards,
santosh

Hi Santosh,
Have you looked BADI ME_PROCESS_PO_CUST or user exits EXIT_SAPMM06E_016 / EXIT_SAPMM06E_017?
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Difference between user exit,enhancement and BAdi

hello guys,
what is the difference between user exit,enhancement and BAdi.
Please do let me know..
Thanks in advance.
regards,
praveen.

Pls do search the forum before posting*

User exit of\r badi for co11

Dear Gurus,
i need a user exit or badi for transcation co11 after creation of batch .
tx
raj

Hi Raj,
Following are the user exit for co11:
CONF0001            Enhancements in order confirmation
CONFPI01            Process order conf.: Calculate cust.specific default values
CONFPI02            Process order confirmation: Customer spec. input checks 1
CONFPI03            Process order conf.: Cust. spec. check after op. selection
CONFPI04            Process order conf.: Customer specific input checks 2
CONFPI05            Process order conf.: Cust. spec. enhancements when saving
CONFPI06            Process order confirmation: Actual data transfer
CONFPM01            PM/SM order conf.: Determine cust. specific default values
CONFPM02            PM/SM order confirmation: Customer specific input checks 1
CONFPM03            PM/SM order conf.: Cust. spec. check after op. selection
CONFPM04            PM/SM order conf.: Customer specific input check 2
CONFPM05            PM/SM order conf.: Cust. specific enhancements when saving
CONFPP01            PP order conf.: Determine customer specific default values
CONFPP02            PP order conf.: Customer specific input checks 1
CONFPP03            PP order conf.: Cust. specific check after op. selection
CONFPP04            PP order conf.: Customer specific input checks 2
CONFPP05            PP order conf.: Customer specific enhancements when saving
CONFPP06            PP Order Confirmations: Actual Data Transfer
CONFPP07            Single Screen Entry: Inclusion of User-Defined Subscreens
CONFPS01            PS confirmation: Determine customer specific default values
CONFPS02            PS confirmation: Customer specific input checks 1
CONFPS03            PS confirmation: Customer specific check after op. selection
CONFPS04            PS confirmation: Customer specific input checks 2
CONFPS05            PS confirmation: Customer specific enhancements when saving
Hope this will help you...

CRM - Pricing User Exit in Java - BADI CRM_COND_COM_BADI

Hi All
I have to convert some user-exit from Abap to Java in order to work in CRM Pricing Scenario (I use VMC technology based on Web AS 7.00).
In the manual attached to note 809820 (New userexit concept for pricing)
I find this chapter but I don't understand how to work with BADI CRM_COND_COM_BADI.
My objective is to create Java user-exit using Custom Tables and Fileds.
Passing additional information to pricing
To summarize, if the information used in a requirement is not depending on the current calculation result, then the information can be passed to the pricing engine. This is the best way to avoid e.g. DB or JCo calls from the user exits.
Nearly all application scenarios using the pricing engine provide a way of filling additional attributes.
1. Create a field catalogue entry for the additional attribute
2. Program the filling of that attribute value
The application calling the pricing engine and the way it is allowing customer code to fill or influence attributes is not part of this document. Here is only a short list of documentation to start with (also various notes exist):
Application Description
CRM Online Order Processing
Implement BADI CRM_COND_COM_BADI. Note 850077
Mobile Solutions Implement VBA user exit methods on SPCDOCHANDLER or SPCITEMHANDLER.Note 677314 and Note 934216
Best regards
Davide Ivanov
[email protected]

Hi davide,
The BADI CRM_COND_COM_BADI is used for filling the pricing communication structure.
If you have added any field at header level of the field catelog that will available in the changing parameter of the method HEADER_COMMUNICATION_STRUCTURE.
If you have added any field at item level of the field catelog that will available in the changing parameter of the method ITEM_COMMUNICATION_STRUCTURE.
Additional fields added at catelog can be filled with the values using this BADI.
Thanks & Regards,
Raghuram. K.R.

User Exit's and BADI's

HI SAP Gurus,
Can anybody please tell me what are user exits and BADI'S, and how are they used.
Thanks in Advance.
Sravanthi

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
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.
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'.
Note that you can write any code that satisfy your needs. ****
But in this case, this was wrote as a sample code for reference sake. ****
And you can test it. ****
SET SCREEN 100.
LEAVE SCREEN.
ENDCASE.
ENDCASE.
BADI: can be used for multiple implementations
that is the difference between user exit and Badi.
which-ever thing you execute that related code will be executed.
see the Badi's doc
Business Add-Ins
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
Courtesy - Kushagra

User Exit migrated to Badi (IE4N)

Hi Expert,
I'm doing upgrade to ECC 6.0 from 4.7 right now and encounter one issue with enhancement CCM00001. We have implemented several screen and user exit in that enhancement in 4.7 system but when we want to open it via SMOD in ECC 6.0, information message popup saying that the enhancement already migrated to Enhancement Badi Definition SMOD_CCM00001 and the status of that enhancement also Migrated.
The funny thing is, there is no Badi definition with name SMOD_CCM00001 and the CCM00001 exit is no longer triggered from IE4N transaction as the way it was in 4.7 system.
Do share your experience if any of you have encountered the same problem before. Thank you.

Hi Abraham,
We had the same issue. According to SAP, the exit CCM00001 was replaced by the following new badis in ECC6.00:
User screen installation IERI_USERSCR_INSTALL
User screen dismantling IERI_USERSCR_REMOVAL
User screen notification dismantling IERI_R_NOTIF_CUST
We have implemented the first two badis and it worked fine.
I hope it can help you.
BR, Otávio.

How to find the user exits and BADIS from SPRO

Hi all,
please let us know how to find the User exits or BADIS for an application from SPRO.
Regards,
Madhavi

Hi Varisetty,
Finding user exits and BAdis from SPRO can be cumbsersome. In most instances you know the standard SAP program and want to check (find) an exit called in the flow of the transaction. You can do this as follows:
For User Exit:
Put "/h" in the command box (to start debugging)
Execute your transaction
When you enter debugging - put a breakpoint at statement
CALL CUSTOMER-FUNCTION
the control will stop at all calls to User Exits
For BAdi (it's simpler)
Go to class CL_EXITHANDLER in SE24
Enter method GET_INSTANCE
Put a breakpoint in this method
Run your standard transaction - control will stop at all BAdis called within the flow since this method is used to check BAdi implementations before invoking them
Also, if you want to find enhancements by package - go to SE80, enter the package and check function groups starting with X - those contain function exits (conventional user exits). For BAdis in a package, there is normally a separate tree node (under the package) for Enhancements hence clearly identifiable.
Cheers,
Adi

Help needed in BAdi and user-exits

Hi ,
 Can any one send me the procedure how to find out user-exits and about BAdi's.
Thanks in advance
Uday

hi Uday,
Welcome to SDN
here is the sample program to find the user exits
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.
Written by : SAP Basis, ABAP Programming and Other IMG Stuff
 http://www.sap-img.com/*
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
To find the function exit
REPORT ZV_FIND_EXIT 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.
or
1. in se11, goto table MODSAP
View table contents
2. in Type field, enter 'E' (for function exit)
3. For that tcode, u should know the program name.
eg. SAPLLMOB
4. then type SAPLLMOB and execute
or
REPORT z34331_user_exit .
TABLES : tstc, "SAP Transaction Codes
tadir, "Directory of Repository Objects
modsapt, "SAP Enhancements - Short Texts
modact, "Modifications
trdir, "System table TRDIR
tfdir, "Function Module
enlfdir, "Additional Attributes for Function Modules
tstct. "Transaction Code Texts
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
START-OF-SELECTION.
Validate Transaction Code
SELECT SINGLE * FROM tstc
WHERE tcode EQ p_tcode.
Find Repository Objects for transaction code
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 = enlfdir-area.
MOVE : tadir-devclass TO v_devclass.
ENDIF.
ENDIF.
Find SAP Modifactions
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.
Take the user to SMOD for the Exit that was selected.
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.
if u find it useful plz markt the points
Regards,
Naveen

User Exit or BADI for Operation tab of IW32 Transaction

Hi All,
Currently I am working on the transaction IW32. I am looking for a user exit or BADI which can trace the item level changed data for operations.
Thanks in advance.
Regards,
Rajesh

hi,
User Exit IWO10012.
BADi's
IWO1_ORDER_BADI
IWO1_PREQ_BADI
IWO1_SCREEN_MODIFY
Hope this helps
Regards,
Shashank

BaDi or User-Exit for a new column in COGI

Hi everybody,
is there a User-Exit or a BaDi to add a new column in the TA COGI?
Maybe anyone have an idea!
Best regards,
Markus

Before Posting Pls try to Search from the Forum...definitely will be find ur Answer
Pls Check the Exits Associated to COGI
Exit name Short text
CONF0001 Enhancements in order confirmation
CONFPI01 Process order conf.: Calculate cust.specific default values
CONFPI02 Process order confirmation: Customer spec. input checks 1
CONFPI03 Process order conf.: Cust. spec. check after op. selection
CONFPI04 Process order conf.: Customer specific input checks 2
CONFPI05 Process order conf.: Cust. spec. enhancements when saving
CONFPI06 Process order confirmation: Actual data transfer
CONFPM01 PM/SM order conf.: Determine cust. specific default values
CONFPM02 PM/SM order confirmation: Customer specific input checks 1
CONFPM03 PM/SM order conf.: Cust. spec. check after op. selection
CONFPM04 PM/SM order conf.: Customer specific input check 2
CONFPM05 PM/SM order conf.: Cust. specific enhancements when saving
CONFPP01 PP order conf.: Determine customer specific default values
CONFPP02 PP order conf.: Customer specific input checks 1
CONFPP03 PP order conf.: Cust. specific check after op. selection
CONFPP04 PP order conf.: Customer specific input checks 2
CONFPP05 PP order conf.: Customer specific enhancements when saving
CONFPP06 PP Order Confirmations: Actual Data Transfer
CONFPP07 Single Screen Entry: Inclusion of User-Defined Subscreens
CONFPS01 PS confirmation: Determine customer specific default values
CONFPS02 PS confirmation: Customer specific input checks 1
CONFPS03 PS confirmation: Customer specific check after op. selection
CONFPS04 PS confirmation: Customer specific input checks 2
CONFPS05 PS confirmation: Customer specific enhancements when saving
BADI Used for COGI
VIM_AE_BADI
Try to Implement Ur Code in Suitable User Exit or BADI.
Reagrds,
SD

USER-EXIT / ENHANCEMENT / BADI -- Material Valuation Class (MBEW-BKLAS)

Hi,
I m looking for any user-exit, enhancement or BADI which is triggered while executing MIGO!!!! .
For example, for good movement 101related to a purchase order.
If MIGO item (material) have batch management we have to inform the batch number (mandatory). When material document is posted system updates material master data with a new valuation type (MBEW-BWTAR) with the same name of the batch number.
We need to inform the valuation class (MBEW-BKLAS) related to this valuation type (MBEW-BWTAR) but we don´t know where it´s possible.
Thanks and sorry for my english!!

Hi Orion,
You can refer to the following user exits for MIGO:
Exit Name           Description
MBCF0002            Customer function exit: Segment text in material doc. item
MBCF0005            Material document item for goods receipt/issue slip
MBCF0006            Customer function for WBS element
MBCF0007            Customer function exit: Updating a reservation
MBCF0009            Filling the storage location field
MBCF0010            Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0011            Read from RESB and RKPF for print list in MB26
MB_CF001            Customer Function Exit in the Case of Updating a Mat. Doc.
Hope this will help you...

User Exit or BADI for the Bank validation in BP transaction

Hi All,
My requirement goes like this, my customer wants to validate the bank keys whether the deletion flag is marked or not and if marked then throw the error message, in BP transaction. But when i was searching for the user exit or a BADI during "save" in BP transaction i was not able to get the appropriate user exit or a badi to do the validation. So can anyone help me finding the user exit or a BADI in the BP transaction
Thanks and Regards,
Praveenkumar T

Hi Praveen,
I don't think there is any Standard FM to validate the bank keys.
You need to make a custom FM for the above requirement and call the FM during the save event of the BP.
Go to Transaction Code-BUS7 and look for event-DSAVC
Under the event DSAVC, assign the custom FM and place the X flag for calling the same.
Hope it clarifies.
Thanks,
Amlan

User Exit/BADI for Purchase Order and Purchase Requisitions

HI,
I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
Is there a User Exit or Badi that i can use where this information is availaible.
also i have to check that release strategy is assigned to every purchase order where the version has been completed.
Is there a User Exit or Badi where Information of EREV table is availaible.
Regards,
Tarun Bahal

For Purchachase requisition , the BADIs and USER EXITS are
ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
try with the above BADI's
MEREQ001 Customers' Own Data in Purchase Requisition
for Purchase order , the BADIs and USER EXITS are
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_BAPI_PO_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PR_CREATE_02
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_COMMITMENT_RETURN Commitment for return item
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
SMOD_MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
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., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
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 P
MM06E008 Monitoring of contr. target value in case of release or
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 proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Regards,
Anirban

Obsolete User Exit's n BADI's

Similar Messages

Maybe you are looking for