Are User Exits to be desupported ?

Are User Exits desupported after Forms 9i? Do you know where to find out, and when support ends? We have some legacy Pro*Cobol User Exits, and we will need to plan ahead if User-Exits are desupported.
If you know the answer to the question, I would be very grateful for a reply, but please do not bother if you are just suggesting alternatives to User-Exits.
Thanks
Phil

Hello,
I need for example to check if for a certain material an MRP caracteristic is maintained. Upon checking a Purchase order position, the system should branch to the MARC table of the material and see if the caracteristic is maintained.
If maintained,,the position of the PO should not be ordered (error message for that position).
If not maintained,the material can be ordered so the position should not generate an error or warning message.
I need a check like this, and with more criteria!
Thanks for any reply.
Aart

Similar Messages

What are user exits & enhancements & how to use those .

What are user exits & enhancements & how to use those .

Hi,
BADI , Customer Exit / User Exit , Enhancement all are same.
Customer Exit & User Exit terms were earlier used in case of R/3. Now in ECC 6.0 they are known as
BADI means Business Add-Ins.
BADIs :
Use:
SAP provides multiple implementations of Business Add-Ins (BAdIs), which enhance the functions of the Configuration Control component.
In addition, there are multiple empty BAdIs available for implementing a customer-specific logic for special functions.
Pls. find listed below some important PP Enhancements / BADIs :
Exit name Short text
PPAPO002 Publication of APO Data in Transfer from APO to R/3
PPAPO003 Production Order R/3->APO: Check if Operation is APO-Re
PPAPO004 Planned Order Conversion from APO: New BOM Explosion?
PPAPO005 Enh. of Relationships in Proc. Order during Transfer to
PPAPO006 Influencing Initial Supply of Manufacturing Orders
PPAPO007 Overriding Checkbox Fields for Production Order APO ->
PPAPO008 Override Order Type for Planned Order Conversion
PPAPO009 Customer Exit for Addition of Components and Items
PPAPO010 Filtering Components out of Quantity Propagation
PPAPO011 Performance-Related Adjustment of Remaining Duration
PPCO0001 Application development: PP orders
PPCO0002 Check exit for setting delete mark / deletion indicator
PPCO0003 Check exit for order changes from sales order
PPCO0004 Sort and processing exit: Mass processing orders
PPCO0005 Storage location/backflushing when order is created
PPCO0006 Enhancement to specify defaults for fields in order hea
PPCO0007 Exit when saving production order
PPCO0008 Enhancement in the adding and changing of components
PPCO0009 Enhancement in goods movements for prod. process order
PPCO0010 Enhancement in make-to-order production - Unit of measu
PPCO0012 Production Order: Display/Change Order Header Data
PPCO0013 Change priorities of selection crit. for batch determin
PPCO0014 Select process orders for external relationships
PPCO0015 Additional check for document links from BOMs
PPCO0016 Additional check for document links from master data
PPCO0017 Additional check for online processing of document link
PPCO0018 Check for changes to production order header
PPCO0019 Checks for changes to order operations
PPCO0020 Process order: Display/change order header data
PPCO0021 Release Control for Automatic Batch Determination
PPCO0022 Determination of Production Memo
PPCO0023 Checks Changes to Order Components
PPCP0001 P.Cost Planning: Additional Cost Elements for Person
PPEACT01 Customer Fields at Mode D
PPECMP01 Customer Fields for CMP Node
PPECMP02 Customer Fields: CMP Variants
PPEGEN01 General Engineering Node: Customer Fields
PPEMPA01 MPA Customer Enhancement
PPEMPO01 Customer Enhancement for Material Planning Object
PPEMPO02 Customer Enhancement for Model
PPERES01 Customer Fields at RES Node
Alternately you can find User Exits / BADIs in TCode : SMOD ( SAP Enhancements)
Hope this helps.
Regards,
Tejas

Credit Control Area User exit

What is user exit in credit Management?
What is the use of it?
How to configure it?
Plz let me know?
Bye

Hi,
user exits are used when u r unable to configure some requirements with standards..for credit management SAP provided number of user exits..mainly 2 will be used.
1.LVKMPTZZ
2.LVKMPTF1
these will be used as per the requirements of the clients..
regards..
yogi..

Are user exits in Pricing for CRM 7.0 implementable in ABAP?

Hi all,
I'm new in CRM. I'm interested in creating some user exits for pricing in CRM 7.0. I know it can be done in Java but I was wandering, since now the web AS is implemented in ABAP, if I could drop Java and use solely ABAP for user exits in pricing.
Thanks

Hi all, I am new to CRM....Can I not create a user-exit condition type in CRM using VOFM ? The reason is that we are comfortable in ABAP but not in Java. Kindly reply with your experience. Thanks

What are User exits?

Hi SAP gurus can u explain me on user exits?

Hi Chandrakanth,
Userexits are system modifications. The requirements of the client which can be met with Standard SAP are done with help of routines or userexits.
Userexits are nothing but a provision given by sap to write your own code/logic in the standard program.
Say for example while processing a sales order you want to check certain criteria weather they are met or not then you can use userxit_save_document_prepare.Here depending on the code you write system checks the if the criteria is fulfilling if not you can set an error or warning message in the code. This userexit is being executed just before saving of document.
one more commonly used exit is adding field in field catalog
In spro check this path Sales and Distribution-System modifications-Userexits.
Read the document provided,you will find all the exits in different processing for SD with program name and their purpose.
User exits are the enhancements provided by SAP
you can use them in transactions. Each transaction will have user exits.
If you want to use your own requirements by making your coding while the transaction is run you can use user exits.
For example if you want to run the MRP in MD02 specific to MRP controller you can user exit.
Please also refer the document below.
USEREXIT
Userxits allow us to add our own functionality to SAP standard program
without modifying it. These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
All Userexits start with the word USEREXIT_...
FORM USEREXIT_..
z..
ENDFORM.
The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary customer code is inserted in the customer include starting with the z. in the form routine.
e.g. USEREXIT_SAVE_DOCUMENT_PREPARE
Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions instead they are using EXITs which come bundled in enhancement packages . Nevertheless existing USEREXITS will be supported by SAP an all the newer versions of SAP.
HOW TO FIND USEREXITS
Userexits can be found in number of ways:
1) To find userexits in SD module , goto object navigator(SE80) and select
development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press enter and you will find all the includes which contain userexits in SD for different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it and start coding.
Some examples of userexits in SD (SALES & DISTRIBUTION) are:
1)ADDING OF NEW FIELDS IN PRICING
In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure. This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields. The fields which are not in either of the two tables KOMK and KOMP cannot be used in pricing .Sometimes a need arises when the pricing is to be based on some other criteria which is not present in the form of fields in either of the two tables. This problem can be solved by using USEREXITS which are provided for pricing in SD. Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done. Hence SAP provides 2 userexits ,one for sales order processing which is
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
In the case of userexit which will be called when invoicing is done ,these
are provided in the include RY60AFZZ which is in the standard SAP program SAPMV45A. The name of the userexits are same. i.e.
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newly created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose includes are provided in each of them .
To create the field in header data (KOMK) the include provided is KOMKAZ
and to create the field in item data (KOMP) the include provided is KOMPAZ.
One possible example for the need of creating new fields can be e.g. Freight to be based upon transportation zone, for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
2) The other method of finding userexit is to find the word USEREXIT in the
associated program of the transaction for which we want to determine userexit using SE38.
3) The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located, this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
Some other examples of userexits in SD are:
USEREXIT_NUMBER_RANGE
This userexit is used to assign a different internal document number to the
sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .
USEREXIT_SAVE_DOCUMENT_PREPARE
This userexit is used to insert the ABAP code which will be called when
the document (sales order VA01) is just about to be saved. This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.
Exits & Enhancements
There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.
These are different from USEREXIT in the way that they are implemented
in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits.
These start from the word EXIT_ followed by the program name and then followed by a three digit number.
e.g. EXIT_SAPMV45A_002
This exit is found in SD in enhancement V45A0002.
TYPES OF EXITS
1) MENU EXITS
2) FUNCTION EXITS
3) TABLE EXITS
4) SCREEN EXITS
5) KEYWORD EXITS
6) FIELD EXITS
We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit, it is required to create the project by using CMOD
selecting the enhancement e.g. V45A0002 and selecting the component
(one which fulfills our need) i.e. the exit which will be implemented in SMOD and after coding has been done the project has to be activated.
An exit can be coded only once.
FUNCTION EXITS
These are used to add functionality through ABAP code. These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any type of exit including function exits.
The function exits are called from the standard SAP program in the form
of ABAP statement
CALL CUSTOMER-FUNCTION 'NNN'
This is in contrast to USEREXITs where PERFORM statement is used to call
the required userexit.
To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its components the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.
e.g.
ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation
To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components. In the components you will see the exit EXIT_SAPMV45A_002. This exit is used for our purpose.
Double clicking on this exit will takes us to function builder (SE37) . This
function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e. if we move the desired customer name to this structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order. This function also contains a customer include ZXVVA04. This include will be used to write our custom code.
Double clicking on this include and it will prompt us that this include does not exists do you want to create this object, select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
e.g. E_KUNNR = 301.
Activate the include and Activate the project. Now when ever the SALES ORDER will be created, sold-to-party field will come up with a predefined customer.
FIELD EXITS
The field exits are managed, created, activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.
The format of field exit is:
FIELD_EXIT_dataelement_A-Z or 0-9
If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.
The function module associated with field exit shows two parameters
INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3, we can write our own code to change the output parameter depending upon our requirements.
Before the field exit can have any effect the system profile parameter
ABAP/FIELDEXIT in all the application servers should be set to YES
ABAP/FIELDEXIT = YES.
User exits in the SD orders. These are program names (SE38):
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 User exits in the SD orders. These are program names (SE38):
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. e 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.
SMOD is the transaction to view user exits assigned to an object.
CMOD is the transaction to change the user exits according to your requirement.
You can find user exits by looking into the phrase USER_EXIT.
Check this program to find out user exits for a transaction
TABLES: tftit,
e071,
e070.
TYPES: BEGIN OF x_tstc,
tcode TYPE tcode,
pgmna TYPE program_id,
END OF x_tstc.
TYPES: BEGIN OF x_tadir,
obj_name TYPE sobj_name,
devclass TYPE devclass,
END OF x_tadir.
TYPES: BEGIN OF x_slog,
obj_name TYPE sobj_name,
END OF x_slog.
TYPES: BEGIN OF x_final,
name TYPE smodname,
member TYPE modmember,
include(15), "Include name
END OF x_final.
DATA: it_tstc TYPE STANDARD TABLE OF x_tstc WITH HEADER LINE.
DATA: it_tadir TYPE STANDARD TABLE OF x_tadir WITH HEADER LINE.
DATA: it_jtab TYPE STANDARD TABLE OF x_slog WITH HEADER LINE.
DATA: it_final TYPE STANDARD TABLE OF x_final WITH HEADER LINE.
SELECTION-SCREEN: BEGIN OF BLOCK blk01 WITH FRAME TITLE text-t01.
PARAMETERS: p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk01.
START-OF-SELECTION.
PERFORM get_tcodes. "Get Tcodes
PERFORM get_objects. "Get Objects
END-OF-SELECTION.
PERFORM display_results. "Display Results
FORM get_tcodes.
SELECT tcode
pgmna
INTO TABLE it_tstc
FROM tstc
WHERE tcode = p_tcode.
IF sy-subrc = 0.
SORT it_tstc BY tcode.
ENDIF.
ENDFORM. " get_tcodes
FORM get_objects.
DATA: l_fname LIKE rs38l-name,
l_group LIKE rs38l-area,
l_include LIKE rs38l-include,
l_namespace LIKE rs38l-namespace,
l_str_area LIKE rs38l-str_area.
DATA: v_include LIKE rodiobj-iobjnm.
DATA: e_t_include TYPE STANDARD TABLE OF abapsource WITH HEADER LINE.
DATA: l_line TYPE string,
l_tabix LIKE sy-tabix.
IF NOT it_tstc[] IS INITIAL.
SELECT obj_name
devclass
INTO TABLE it_tadir
FROM tadir FOR ALL ENTRIES IN it_tstc
WHERE pgmid = 'R3TR' AND
object = 'PROG' AND
obj_name = it_tstc-pgmna.
IF sy-subrc = 0.
SORT it_tadir BY obj_name devclass.
SELECT obj_name
INTO TABLE it_jtab
FROM tadir FOR ALL ENTRIES IN it_tadir
WHERE pgmid = 'R3TR' AND
object = 'SMOD' AND
devclass = it_tadir-devclass.
IF sy-subrc = 0.
SORT it_jtab BY obj_name.
ENDIF.
ENDIF.
ENDIF.
*- Get UserExit names
LOOP AT it_jtab.
SELECT name
member
INTO (it_final-name, it_final-member)
FROM modsap
WHERE name = it_jtab-obj_name AND
typ = 'E'.
APPEND it_final.
CLEAR it_final.
ENDSELECT.
ENDLOOP.
*- Process it_final contents.
LOOP AT it_final.
l_tabix = sy-tabix.
CLEAR: l_fname,
l_group,
l_include,
l_namespace,
l_str_area.
l_fname = it_final-member.
CALL FUNCTION 'FUNCTION_EXISTS'
EXPORTING
funcname = l_fname
IMPORTING
group = l_group
include = l_include
namespace = l_namespace
str_area = l_str_area
EXCEPTIONS
function_not_exist = 1
OTHERS = 2.
IF sy-subrc = 0.
IF NOT l_include IS INITIAL.
*- Get Source code of include.
CLEAR: v_include, e_t_include, e_t_include[].
v_include = l_include.
CALL FUNCTION 'MU_INCLUDE_GET'
EXPORTING
i_include = v_include
TABLES
e_t_include = e_t_include.
IF sy-subrc = 0.
LOOP AT e_t_include.
IF e_t_include-line CS 'INCLUDE'.
CLEAR l_line.
l_line = e_t_include-line.
CONDENSE l_line NO-GAPS.
TRANSLATE l_line USING '. '.
l_line = l_line+7(9).
it_final-include = l_line.
MODIFY it_final INDEX l_tabix TRANSPORTING include.
ENDIF.
ENDLOOP.
ENDIF.
ENDIF.
ENDIF.
ENDLOOP.
ENDFORM. " get_objects
FORM display_results.
FORMAT COLOR COL_HEADING.
WRITE:/1(150) sy-uline.
WRITE:/ sy-vline,
2(23) 'Extension Name',
24 sy-vline,
25(39) 'Exit Name',
64 sy-vline,
65(74) 'Description',
140 sy-vline,
141(9) 'Include',
150 sy-vline.
WRITE:/1(150) sy-uline.
FORMAT RESET.
SORT it_final BY name member.
LOOP AT it_final.
CLEAR tftit.
SELECT SINGLE stext
INTO tftit-stext
FROM tftit
WHERE spras = 'EN' AND
funcname = it_final-member.
WRITE:/ sy-vline,
it_final-name COLOR COL_KEY, 24 sy-vline,
25 it_final-member, 64 sy-vline,
65 tftit-stext, 140 sy-vline,
141 it_final-include, 150 sy-vline.
WRITE:/1(150) sy-uline.
ENDLOOP.
ENDFORM. " display_results
Hope this Clarifies your Doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Are there user exits after Workflow items being created

Hi all:
Here is my situation, I want to create a change document object on table SWWWIHEAD, which is the table of workflow items. Whenever a workitem is created, I want to send the information of this item to an webservice outside of ECC.
The first thing come to my thought is the change document, and use the change document to link with an event. But we need to find the place to insert the code of call the function *WRITE_DOCUMENT generated by change document. Are there any one know if there are user exits that I can insert the code after a work item being created or updated?
Regrads
Wayne

look at MM06E005 in SMOD

Sample code ale/idoc n user exits

Hi
could any one post me two objects each for ALE/IDOCs and Enhancements with explanation about business scenarios ,complete code plz....

I do not see any FM idoc_input_deladv1 ,but i see FM IDOC_INPUT_DELVRY
There are user exits related to FM IDOC_INPUT_DELVRY
Check the enhancement : V55K0001
FM : EXIT_SAPLV55K_001
Check the enhancement : V55K0002
EXIT_SAPLV55K_002
Check the enhancement : V55K0003
EXIT_SAPLV55K_003
Thanks
Seshu

Search cluster PCL4 user-exit or BADI, enhancement

Hi,
i need to add some code when the system has finished to record the PCL4 cluster (HR), but i don't find user-exit or BADI's.
Thanks for your help.

I don't think there is a user exit or BADI for PCL4.
What do you want to do?
Usually there are user exits for reports or transactions and not for tables.

User Exit regarding Sale Order

Hi All,
While creating a sale order, in the header details and in conditions tab. All the condition types are displayed. Customer requirment is i need to make some changes for some particular condition type in tht sale order like. Can any one pls tell me which user exit i can use for it? to be more clear they have condition type ZFRT for Freight charges. I need to make some calculation ther and display the freight price value ther in tht condition type when the sale order is created. Since its a standrad prog we can do it by user exit only. If anyone done such requirment can let me know which user exit can be used for this.
Thanks
Sathish

Go to SE80 - choose program enter SAPMV45A - Double click on the program and go to include MV45AFZA - There are user exits related to price. Put break point and execute VA01. Change field content of XKOMV (i think) and see the result in sales order application.
They are the user exits to modify the pricing conditions.
If you want to do that in pricing routines - find out the routine or requirement or formula for the same and go to tcode VOFM - write your code. Contact SD pricing guy for the same.

Urgent ( Case about USER EXIT)

I need to place a Botton in CN20J (Project Builder).
How can I proceed,
Can there are User Exit for this ,
If It is there Plz Try to Add a button to aopen an URL,
I got aprocedure for URL.
I need to place a button............
If possible Plz send the Code to write it. or Steps to Proceed.....

There are enhancements CNEX0006 PS customer specific fields project definition and CNEX0007 for WBS, these enhancement contain sub-screens for specific/customer fields.
You could use this enhancement to
- Put the button in sub-screen to display your URL
or
- Intercept the function-key "+CUD" to display your URL, then you have to "by-pass" the subscreen (or best, display the url in the sub-screen)
Regards

User Exits in FM IDOC_INPUT_SALESORDER_CREATEFR

Hi
Please help me in providing exit in FM IDOC_INPUT_SALESORDER_CREATEFR for the below functionality.
In this exit I ve to write code to check custom segment field and update the Item category field in Line items of sales order.
Your help appreciated.
Thanks In Advance.

I do not see any FM idoc_input_deladv1 ,but i see FM IDOC_INPUT_DELVRY
There are user exits related to FM IDOC_INPUT_DELVRY
Check the enhancement : V55K0001
FM : EXIT_SAPLV55K_001
Check the enhancement : V55K0002
EXIT_SAPLV55K_002
Check the enhancement : V55K0003
EXIT_SAPLV55K_003
Thanks
Seshu

User Exit for Material Master

Hi everybody,
I'm looking for a BAdi or an userexit for material master data (TA MM01/MM02). This BAdi should be used every time a user press the save button. I could not find any BAdi in the SAP help.
Do anybody of you know if there is a BAdi implementation or userexit exists?
Regards
Berthold

Hi Berthold,
Here are user exits and BADI available for MM01/MM02.
User Exits:
MGA00001
MGA00002
MGA00003
BADIs:
MG_MASS_NEWSEG
MATGRP_SKU_UPD
CDT_CHECK_MATERIAL
BADI_MM_MATNR
BADI_MAT_F_SPEC_SEL
BADI_MATNR_CHECK_PVS
BADI_MATERIAL_REF
BADI_MATERIAL_OD
BADI_MATERIAL_CHECK
BADI_GTIN_VARIANT
BADI_EAN_SYSTEMATIC
Regards,
Ferry Lianto

User Exit EXIT_SAPLV01Z_004 in Batch Management

Hi All
I am trying to use EXIT_SAPLV01Z_004 in checking of externally created Batch number.The exit is working fine for ROH materials in MIGO.It is not getting triggred at all in MB31 or MSC1N.Can any one guide me.
S Anil

Here are user exits for tcode PR04:
Exit Name           Description
FITR0001            User exit: Delete/Reorganize trip statistics
FITR0002            User exit: Create/Change trip statistics
FITR0003            User exit: Save trip (PR01, PR04, PR05)
FITR0005            User Exit: Save Trip (PR01, PR04, PR05)
RPRCST01         Customer Exit for Travel Expenses

User Exit in PD

Hello All-
Can you please let me know if there is a userexit that I can enhance when maintaining any Org. Management objects mainly when maintaining Infotype 1005.
Thanks-
Chakri.

Hi,
Following are User Exit & BAdi for TCode PP01.
Enhancement
RHGB0001       Function Group RHGB Customer-specific field (list)
RHIV0001         OrgManagement: Customer-specific number assignment
Business Add-in
ARC_BC_HROBJ_CHECK-Archiving Object BC_HROBJ: Archivability Checks
ARC_BC_HROBJ_WRITE Archiving Object BC_HROBJ: Additional Table Entries
HRBAS00INFTY                Update By
HRBAS00_GET_PROFL    Determine user profile from table T77PR
HRBAS00_RELAT             HR: Exit for Relationships
HRBAS00_RHBAUS00      Business Add-In for RHBAUS00
HRBAS00_SEARCH          HR: Object Search
HRBAS00_STRUAUTH       Business Add-In for Structural Authorization
HRBAS00_T77S0               HR: Switch Attributes
regards,
Dharitree

User exits, Bapi , badi ?

Hi Gurus,
What are user exits, BAPI and BADI ?
Short and sweet answers would be appreciated.
Thanks in advance.

BAPI
BAPI stands for Business API(Application Program Interface).
A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
User Exits
User exits are a type of system enhancement that were originally developed for the R/3 SD.
The SAP developer creates a special include in a module pool. These includes contain one or more subroutines that satisfy the naming convention userexit_<name>. The calls for these subroutines have already been implemented in the R/3 program. Refer Conventional SD User exits Slides
A user exit is considered a modification, since technically objects in the SAP namespace are being modified.
After delivering them, SAP never alters includes created in this manner; if new user exits must be delivered in a new release, they are placed in a new include program.
Customer Exits
Customer exits are hooks provided by SAP within many standard programs, screens and menus on which customers may hang custom functionality to meet business requirements
BADI
DEFINING THE BADI
1) execute Tcode SE18.
2) Specify a definition Name : ZBADI_SPFLI
3) Press create
4) Choose the attribute tab. Specify short desc for badi.. and specify the type :
multiple use.
5) Choose the interface tab
6) Specify interface name: ZIF_EX_BADI_SPFLI and save.
7) Dbl clk on interface name to start class builder . specify a method name (name,
level, desc).
Method level desc
Linese;ection instance methos some desc
8) place the cursor on the method name desc its parameters to define the interface.
Parameter type refe field desc
I_carrid import spfli-carrid some
I_connid import spefi-connid some
9) save , check and activateadapter class proposed by system is
ZCL_IM_IM_LINESEL is genereated.
IMPLEMENTATION OF BADI DEFINITION
1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.
2) Specify aname for implementation ZIM_LINESEL
3) Specify short desc.
4) Choose interface tab. System proposes a name fo the implementation class.
ZCL_IM_IMLINESEL which is already generarted.
5) Specify short desc for method
6) Dbl clk on method to insert code..(check the code in AAA).
7) Save , check and activate the code.
Some useful URL
http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
Reward Points if useful.

Are User Exits to be desupported ?

Similar Messages

Maybe you are looking for