What is user-exists --- related to cross functionality topic

what is user-exists --- related to cross functionality topic

User Exits are also called as BADI's (Business Aditions)
There are two steps in User Exit creation.
1} Identify the User Exit suitable for the requirement and that is available in the system:
Code SE18 is used to Identify the BADI available.
Look for the string 'CL_EXITHANDLER' in the standard program. This is a class which has a method 'GET_INSTANCE' which is used to trigger BADI's from the Standard Program. The interface parameter for this static method 'EXIT_NAME' is used to pass the BADI to the method.
Open Standard Program and do a global search 'CL_EXITHANDLER'.
SE18 > give the BADI name found through above search.
CUSTOMER_ADD_DATA > which has a method SAVE_DATA.
2} Implement the User Exit identified through above process.
T.Code SE19 is used to Implement BADI.
SE19 > give the implementation name > Give the Definition name as CUSTOMER_ADD_DATA and the Short Text.
Intro.....
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
Check these links for info about badi..
BADI's
http://support.sas.com/rnd/papers/sugi30/SAP.ppt
BADI's
http://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09e10000000a155106/frameset.htm
http://support.sas.com/rnd/papers/sugi30/SAP.ppt
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
http://members.aol.com/_ht_a/skarkada/sap/
http://www.ct-software.com/reportpool_frame.htm
http://www.saphelp.com/SAP_Technical.htm
http://www.kabai.com/abaps/q.htm
http://www.guidancetech.com/people/holland/sap/abap/
http://www.planetsap.com/download_abap_programs.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
/people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series
/people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework
http://www.esnips.com/web/BAdI
http://www.allsaplinks.com/badi.html
New to Badi
check any fo the below links. this will def help u.
http://www.allsaplinks.com/badi.html
And also download this file....
http://www.savefile.com/files.php?fid=8913854
There are other tutorials on this site...
http://sapbrain.com/Tutorials/tuto_download.html
Reward Points if useful.

Similar Messages

Types of user exists arise in sd module

what is user exist and what type of user exists arise in sd module?

Dear Chandu,
Please go through this IMG path to identify the User exits
SPRO>sales and Distribution>Syatem modification-->User Exits
I hope it will help you,
Regards,
Murali.
Please close the completed threads

Says about formatters(currencies, dates...) well, is relate to user locale, ... what this "user" mea

I use Flash Builder 4.0.1 standard, I can follow the FX IN A WK (FX B 4.5), without problems or...exist other in my version FX IN A WK (FX B 4.0)?
in the book ADOBE FX 4 TFS VOL.1, CH.15: USING FORMATTERS AND VALIDATORS,
Says about formatters(currencies, dates...) well, is relate to user locale, ... what this "user" mean? developer configuration, or server locale or visitors locale? developer configuration how done in the FlexGrocer App?
ADOBE FX 4.5 TFS VOL.1, 2 again use FlexGrocer App? Where find this volume: ADOBE FX 4 TFS VOL.2?

Hmm, I'm not able to reproduce your issue.
I created a simple JSP page with the following:
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<f:view locale="en">
<f:loadBundle basename="Resources" var="res"/>
<h:outputText value="#{res.key}"/>
</f:view>
[\code]
I have two properties files with the base name of Resources (Resources_en_US.properties and Resources.properties).
When I issue a request to the JSP page, I get the localized value from the Resources.properties file.
I suppose it could potentially be a JDK issue since the loadBundle tag uses java.util.ResourceBundle. Which JDK are you using?

How to capture the User input value to user exist function module.

Hi,
How can i capture user input value.Here i am using User exist in BPS variable.
Calculating days using user exist functin module and my input is another variable i.e user defined value.
How can i capture user defined vaule into my function module.
This is very urgent can you help me..
Thanks....

Hi!
You can get the instance using the method get_instance of the class cl_sem_variable, and call the method get_value with the return. Check the example:
      CALL METHOD cl_sem_variable=>get_instance
        EXPORTING
          i_area       = (planning area)
          i_variable   = (variable name)
        RECEIVING
          rr_variable = lr_var
        EXCEPTIONS
          not_existing = 1
          OTHERS       = 2.
      CHECK sy-subrc IS INITIAL.
      CALL METHOD lr_var->get_value
        RECEIVING
          rto_value = et_value
        EXCEPTIONS
          error     = 1.
After this, read the first line of the table et_value (it should be the value that the user choose on the screen).
seeya!
Robson

"user exists" function

Hi
I was wondering if it's possible to modify the user exists
code so that instead of being redirected to another page if the
user already exists, the user will be notified of the error on the
same page?
I can get an error message to appear without the redirect,
but the already existing user login ID is still inserted into the
database.
Here is the original code for the user exists funcion, I
would be grateful if anyone can suggest what I should change in
order to get the effect I want. Thanks

HI
You can check using the BAPI,
BAPI_USER_EXISTENCE_CHECK
where you can enter the users name and it returns with the message whether the user exists or not.
Do reward if useful
Thanks
Swarna

Hi guru's i am learning ,i am learning user exists plz help me

hi guru's i am learning ,i am learning user exists , i don't know anything about that plz help me lie realtime oriented

Hi
USER EXIT
EXIT s are nothing but the R/3 Enhancements which allows you to add your own functionality to SAPs standard business applications without having to modify the original applications.
Purpose
To introduce the techniques of enhancement in standard SAP system. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
Use
They do not affect standard SAP source code.
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
They do not affect software updates.
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Challenges
Customer exits are not available for all programs and screens found in the SAP System.
Modifications
Any change made to an SAP object in a customer system is called a modification. Customers usually modify their systems for one of two reasons. Either they make changes to the SAP standard in order to adjust the R/3 System to their specific business needs (actual modifications), or they alter individual SAP objects in order to correct an error (as recommended in an SAP error note).
You should only modify the SAP standard if the modifications you want to make are absolutely necessary for optimizing work flow in your company. Be aware that good background knowledge of application structure and flow are important prerequisites for deciding what kind of modifications to make and how these modifications should be designed.
need
ABAP DICTIONARY
Table Enhancements: There are two ways that you can add additional fields to tables without modifying your system.
Append Structures:
Append structures allow you to enhance tables by adding fields to them that are not part of the standard. With append structures, customers can add their own fields to any table or structure they want.
Append structures are created for use with a specific table. However, a table can have multiple append structures assigned to it.
Customizing Includes:
If customers know in advance that one of the tables or structures delivered to them by SAP needs to have customer-specific fields added to it, an SAP application developer can include these fields in the table using a Customizing include statement.
The same Customizing include can be used in multiple tables or structures. This provides for consistency in these tables and structures whenever the itself include is altered.
Append structures allow you to attach fields to a table without actually having to modify the table itself.
Append structures may only be assigned to a single table. A table may, however, have several append structures attached to it. Whenever a table is activated, the system searches for all active append structures for that table and attaches them to the table. If an append structure is created or changed and then activated, the table it is assigned to is also activated, and all of the changes made to the append structure take effect in the table as well.
You can use append structures in ABAP programs just as you would any other structure.
Note: When you copy tables that have append structures attached to them, the fields that were found in the append structure of the original table become part of the actual body of the target table.
Some of the tables and structures delivered with the R/3 standard contain special include statements calling Customizing includes. These are often inserted in those standard tables that need to have customer-specific fields added to them.
In contrast to append structures, Customizing includes can be inserted into more than one table. This provides for data consistency throughout the tables and structures affected whenever the include is altered.
Customizing include programs are part of the customer namespace: all of their names begin with 'CI_'. This naming convention guarantees that nonexistent Customizing includes do not lead to errors. No code for Customizing includes is delivered with the R/3 standard.
You create Customizing includes using special Customizing transactions. Some are already part of SAP enhancements and can be created by using project management (see the unit on 'Enhancements using Customer Exits').
The Customizing include field names must lie in the customer namespace just like field names in append structures. These names must all begin with either 'YY' or 'ZZ'.
When adding the fields of a Customizing include to your database, adhere to same rules you would with append structures.
ABAP DICTIONARY
Field Exits:
Field exits take you from a screen field with a data element reference to a function module. Field exits can be either global or local.
Field exit function modules adhere to the following naming convention:
prefix: FIELD_EXIT_
name: <data element name>_
suffix (optional): 0 to 9, A to Z
Text Enhancements:
Possible text enhancements include customer keywords and customer documentation of data elements.
Text enhancements differ from other application enhancements in that they take effect globally in all related SAP applications after activation (global enhancements).
Customer Exits
Function Module Exits
Menu Exits
Screen Exits
Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated. Function module exits also control the data flow between standard programs and screen exit fields.
Menu Exits
Menu exits add items to the pull down menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special sub screen areas on a standard R/3 screen and calling a customer sub screen from the standard screens flow logic.
Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html

SELECTs in user exists (P/S modules)

Hi,
I am implementing user exist triggered when an accounting document is posted ... P/S event no. 00001030. The problem is, that I need to read some records from BSID table ... this event is triggered right before a commit is executed, therefore I suppose that all database changes are already made, but not commited yet. Anyway, I've tried to read these database rows (in the same database transaction), but SELECT does not fetch any row! I know how database servers works, what are database sessions and database transactions ... I thought SAP system works in the same way ...
Can anybody explain me why ABAP does not see uncommited rows inserted by the same database session/transaction? Is there a way how to read these rows? I already tried to call my function by PERFORM ON COMMIT, ... same results ... also by CALL FUNCTION IN UPDATE TASK ... same results ...
Is there any sensible way how to read desired uncommited records?

Hi,
Check while debugging where BSID table have those values or not.If yes then BSID table should declare in Table fields.If not then you need to dynamically assign the value of table to your workarea.
Below is the code which might help you:
Get the Name field enetered on Fb01 screen
ASSIGN ('(SAPMF05A)BSEC') TO <fs>.
wa_bsec = <fs>.
I hope it would help you.
Regards,
Swati

User Exists & Bar Code Q's

HI,
User Exists
If we know User Exists name, for example MV45AFZZ.
How to find related Transaction code or Program name from that?
What are the Transaction code aval for User Exists.
Any Sample BLOGS on this?
BarCode
I know we can print BarCode in Scripts and SmartForms.
Where else we can implement BarCode in ABAP Programs.
Any Sample BLOGS on this?

Hai Jen
Go to se93 and give the tcode to find the main program associated to it.
Go to se38 and give the main program.
Find the package associated to it.Go to->Object Directory Entry.
Go to smod transaction.
Press f4.
Press Information System Button.
Give the Project(Dev Class).
Press enter.
Find the enhancements associated
For Script/Smaft form print barcode
First Download it to your PC and then Upload it again with Different name.
For Download you need to use the Class CL_SSF_XSF_UTILITIES
in this class you have to call the method GET_BDS_GRAPHIC_AS_BMP
to get the image in xstring format .
now download that to PC using GUI_DOWNLOAD and then upload it with Different name.
Regards
Sreeni

Adding code in std. user exist

Hi,
I want to add some code in USER EXIST,
the include program : RV60BFZA , is a include program which is use in Function Pool program SAPLV60B
now in RV60BFZA there are many usereixt and in user exist
FORM userexit_fill_xkomk1.
ENDFORM.                    "USEREXIT_FILL_XKOMK1
I want to add code                           rule_new_cancel = 'A'.
will you please giude how to add this code in the user exist, I have never work on uer exist.
regards,
zafar
Moderator Message: These are NOT training forums. Nor are they an alternative for proper classroom trianing.
Edited by: kishan P on Dec 6, 2010 1:52 PM

Hi Ashok,
    Thanks for your reply,
I follow the stpes given by you when I click on create enhancement it is giving a pop up box for selection of DECLARATION or Code then I click on code then again it is displaying on epop for the selection of enhancement implementation and Pack, now there are many pack in this, so what to select and proceed, what is effect of this.
regards,
   zafar

User exist CCUX0008 does not take effective

Dear Expects,
    I implement user exist CCUX0008 with very simple code NO_EXPL_EXT_PROCUREMENT = 'X' . in ZXCUCU15 include file.
    After I active it I found the external procured components still explore their children materials in T-code cu51/cu52/cskb/csk1/csk2/csk3.
     I am very puzzled what's happened? and could somebody tell me what the CCUX0008 do indeed and what is the logic of it?
Thanks
Jason

Dear,
Delete import parameter NO_EXPL_EXT_PROCUREMENT by using Transaction SE37 for function NO_EXPL_EXT_PROCUREMENT.
Create a new export parameter for this function module:
Parameter name:    NO_EXPL_EXT_PROCUREMENT
Type. spec.:       TYPE
Reference type:    C
Short text:        No explosion of components procured externally
Save it and test again.
Regards,
R.Brahmankar

Difference between user exists&badi's

difference between user exists&badi's

Hi, this may help you.
Check this link to learn more about differences between user-exits and badis:
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
Difference Between BADI and User Exits
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.
As with customer exits two different views are available:
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.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
Ex:- 'Development server'>'Quality server'-> 'Production server'......
Reward If Helpful.
Regards Madhu.

Difference between user exists customer exists

difference between user exists customer exists

Hi,
User exits are basically modifications done to the std. pgm
for whic u need to have access code,this is not reccomended
in sap as during upgradation none of the mod. will come thru.
   In contrast customer exits are enhancements done to the
std pgm in the space provided by sap so that during
upgrading versions this also will be available.
    Customer exits types
     Function exits, Field exits(absolete), screen exits.
There isn't much difference between the two. CMOD user exits allow greater control, and have a manageable, trackable framework - it's easy to see what's in use and what isn't. A customer exit is a type of user exit. A user exit is a handle that SAP put into their code, allowing a customer to add their own routines.
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
Customer exit - 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 customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
Reward if helpful..
Regards,
Ramya

What is User Exits ? what are Enhancements

What is User Exits ? what are Enhancements ?

You can find information in the SAP help, e.g. under http://help.sap.com/saphelp_nw04/helpdata/en/c8/1978b543b111d1896f0000e8322d00/frameset.htm.
User exits can be realized through BADI's or customer exits.
In SAP Standard Transactions, if you need to do some customization via programming then SAP has identified the milestones in the behavior of the transactions where these customized effects may be needed.
This customization to standard transactions is done by some special function modules wherein one can write the customized code with the given SAP import/export parameters. These function modules relate to user exits. Transaction for user exit & its usage in any project are CMOD/SMOD.
Create a project in CMOD and implement that project in SMOD
PS If the answer solves your query, plz do reward points to everyone responding.

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

What is Customer Exist?

Dear All,
What is Customer Exist?
What is Different Between User Exist & Customer Exist?
Regards,
Dharmesh

Hi ,
Customer Exits :
 Pre-planned enhancement to the standard SAP system.
SAP anticipates potential customer requests not already implemented in the standard system by predefining them as 'empty modification modules'. Customers fill these modules with their own logic according to their own requirements.
SAP creates customer exits with transaction SMOD. From these customer exits, customers then use transaction CMOD to choose the enhancements they want to process, assign them to enhancement projects, edit the components, and activate the relevant projects.
Using customer exits guarantees upwards compatibility. This is because jumps to exits are predefined in the standard software and the validity of the call interface are both retained, even in future release upgrades.
Difference Between User-exits and Customer-exits
1. USER EXITS are FORMS and are called by SAP standard programs using PERFORM.
 CUSTOMER EXITS are FUNCTIONS so they are called using CALL FUNCTION (or more exactly CALL CUSTOMER FUNCTION).
2. Inside the form (user exit) you can read and change almost any global data from host program.
 Inside a function (customer exit) you can only acces your import/export/changing/tables parameters.
3.User exits are more flexible because you have more information to use in your code but on the other hand , it is very easy to manipulate erroneously global data and lead the standard program to a dump or even to make database inconsistent.
 Customer exits are more restrictive but you are sure any change you can make to any parameters will never lead to inconsistency.
4.User-exit doesnt have any classification.
 In customer-exit we have function-module exit , screen exit , menu exit.
5.User Exits are Basically designed For SD module.
 Customer Exits are available for MM,SD,FI,HR..Basically designed for all modules.
6. User-exits can be written only using access-key.
 No need of access key to write a customer exit.
7.With user-exits the code , the developer has written will not be there for next version unless modification assistance tool is used.
 Customer-exits are not wiped during upgradation.
thanks and regards,
kunal.

What is user-exists --- related to cross functionality topic

Similar Messages

Maybe you are looking for