Skip to Content
avatar image
Former Member

user exits in sd area

Hai gurus

there are so many user exits in sd area and we can find that in spro itself with specific to the module in system modifications. I wanted to know as an we find an user exit which is appropriate with the requirement how we should activate it. can any one explain me the step by step process after finding an appropriate user exit.

do we have to intract with the abaper for it or what?

elobrate answer will be highly rewarded

sree

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

7 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 07, 2007 at 04:16 AM

    hi

    can also find the list thru...

    CMOD -> Utilities -> SAP Enhancements -> F8 Execute)

    List of User Exits

    http://www.planetsap.com/Userexit_List.htm

    finding-the-user-exit

    http://www.saptechnical.com/Tutorials/ExitsBADIs/ExitsMain.htm

    yeh u have to interact with abaper as he is the right person to hadle those exits..

    as a functional consultant u are not permitted to use user exits.. for reference purpose u can find the available user exits from the above mentioned links and other member rplys.. infact knowing whta user exits are available in the sap system is very much gud for the functional consultant as it can help a fucn conslnt in interacting withe abaper in various issues and in preparation of requirement documents..

    it is always an gud idea to have idea and knowledge of technical aspects in sap as it can improve a functional consultnts performance while preparing business specifications. specially user exits, idocs, etc. so that u can directly suggest the technical person of wht can be used instead of searching for required ones by the tech guy,,.

    Reward if USeful

    Thanx & regards

    Naren..

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 07, 2007 at 04:03 AM

    Hi

    Refer below

    All" target="_blank">http://www.easymarketplace.de/userexit.php">All SAP User Exits (SMOD/CMOD) on one view

    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 bundeled in enhancement packages . Neverthiless 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 newely

    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. Frieght 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 tupe 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 compnents 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.

    <b>Finding user exits</b>

    Need to find user exits module-wise? Suppose we want to see the available sales module user exits. Go to transaction SE81. Click on SD, then click "edit" on the menu bar and choose select subtree. Click on "information system," Open Environment node, customer exits, and enhancements. Press F8 to get all the user exits for that module. In brief: SE81->SD->Select subtree->Information System->Envir->Exit Techniques->Customers exits->enhancements->Execute(F8)

    MV45AFZZhttp://fuller.mit.edu/user_exits/validating_sales_docs.htm">MV45AFZZ>

    Supressing" target="_blank">http://www.sap-img.com/sap-sd/supressing-fields-in-sale-order.htm">Supressing Fields in Sale Order

    [url=http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/content.htm]User Exits In Sales Document Processing[/url]

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 06, 2007 at 02:37 PM

    SDVFX007 User exit: Billing plan during transfer to Accounting

    SDVFX008 User exit: Processing of transfer structures SD-FI

    SDVFX009 Billing doc. processing KIDONO (payment reference number)

    SDVFX010 User exit item table for the customer lines

    SDVFX011 Userexit for the komkcv- and kompcv-structures

    V05I0001 User exits for billing index

    V05N0001 User Exits for Printing Billing Docs. using POR Procedure

    V60A0001 Customer functions in the billing document

    V60P0001 Data provision for additional fields for display in lists

    V61A0001 Customer enhancement: Pricing

    use SMOD to find out the detail

    List of user exits related to VL01N

    V02V0001 - Sales area determination for stock transport order

    V02V0002 - User exit for storage location determination

    V02V0003 - User exit for gate + matl staging area determination

    V02V0004 - User Exit for Staging Area Determination (Item)

    V50PSTAT - Delivery: Item Status Calculation

    V50Q0001 - Delivery Monitor: User Exits for Filling Display Fields

    V50R0001 - Collective processing for delivery creation

    V50R0002 - Collective processing for delivery creation

    V50R0004 - Calculation of Stock for POs for Shipping Due Date List

    V50S0001 - User Exits for Delivery Processing

    V53C0001 - Rough workload calculation in time per item

    V53C0002 - W&S: RWE enhancement - shipping material type/time slot

    V53W0001 - User exits for creating picking waves

    VMDE0001 - Shipping Interface: Error Handling - Inbound IDoc

    VMDE0002 - Shipping Interface: Message PICKSD (Picking, Outbound)

    VMDE0003 - Shipping Interface: Message SDPICK (Picking, Inbound)

    VMDE0004 - Shipping Interface: Message SDPACK (Packing, Inbound)

    V56DISTZ - Transportation processing: Field modification

    MV56AINI - Initialization of transaction control for transportation

    V56AFCCH -Shipment processing: Check function code allowed

    V56LOCID Shipment Processing: Determine Location Identification

    V56SLDET Shipment processing: Leg determination

    V56TDLIF Filter Delivery Items for Shipment

    V56UCHCO Check shipments are complete

    rewards if it helps

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 06, 2007 at 02:46 PM

    Sales realated exits

    SDTRM001 Reschedule schedule lines without a new ATP check

    V45A0001 Determine alternative materials for product selection

    V45A0002 Predefine sold-to party in sales document

    V45A0003 Collector for customer function modulpool MV45A

    V45A0004 Copy packing proposal

    V45E0001 Update the purchase order from the sales order

    V45E0002 Data transfer in procurement elements (PRreq., assembly)

    V45L0001 SD component supplier processing (customer enhancements)

    V45P0001 SD customer function for cross-company code sales

    V45S0001 Update sales document from configuration

    V45S0003 MRP-relevance for incomplete configuration

    V45S0004 Effectivity type in sales order

    V45W0001 SD Service Management: Forward Contract Data to Item

    V46H0001 SD Customer functions for resource-related billing

    V60F0001 SD Billing plan (customer enhancement) diff. to billing plan

    Billing Related exits

    SDVFX007 User exit: Billing plan during transfer to Accounting

    SDVFX008 User exit: Processing of transfer structures SD-FI

    SDVFX009 Billing doc. processing KIDONO (payment reference number)

    SDVFX010 User exit item table for the customer lines

    SDVFX011 Userexit for the komkcv- and kompcv-structures

    V05I0001 User exits for billing index

    V05N0001 User Exits for Printing Billing Docs. using POR Procedure

    V60A0001 Customer functions in the billing document

    V60P0001 Data provision for additional fields for display in lists

    V61A0001 Customer enhancement: Pricing

    Hope these helps ..

    Cheers

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 07, 2007 at 06:41 AM

    Hi Sree,

    Please find below the user exits which are available for VL02N.

    V50PSTAT - Delivery: Item Status Calculation

    V50Q0001 - Delivery Monitor: User Exits for Filling Display Fields

    V50R0001 - Collective processing for delivery creation

    V50R0002 - Collective processing for delivery creation

    V50R0004 - Calculation of Stock for POs for Shipping Due Date List

    V50S0001 - User Exits for Delivery Processing

    V53C0001 - Rough workload calculation in time per item

    V53C0002 - W&S: RWE enhancement - shipping material type/time slot

    V53W0001 - User exits for creating picking waves

    VMDE0001 - Shipping Interface: Error Handling - Inbound IDoc

    VMDE0002 - Shipping Interface: Message PICKSD (Picking, Outbound)

    VMDE0003 - Shipping Interface: Message SDPICK (Picking, Inbound)

    VMDE0004 - Shipping Interface: Message SDPACK (Packing, Inbound)

    V02V0001 - Sales area determination for stock transport order

    V02V0002 - User exit for storage location determination

    V02V0003 - User exit for gate + matl staging area determination (headr)

    V02V0004 - User Exit for Staging Area Determination (Item)

    If you need see the further exits and BADI's related to VA01/VA02

    Enhancement

    V60F0001 SD Billing plan (customer enhancement) diff. to billing plan

    V46H0001 SD Customer functions for resource-related billing

    V45W0001 SD Service Management: Forward Contract Data to Item

    V45S0004 Effectivity type in sales order

    V45S0003 MRP-relevance for incomplete configuration

    V45S0001 Update sales document from configuration

    V45P0001 SD customer function for cross-company code sales

    V45L0001 SD component supplier processing (customer enhancements)

    V45E0002 Data transfer in procurement elements (PRreq., assembly)

    V45E0001 Update the purchase order from the sales order

    V45A0004 Copy packing proposal

    V45A0003 Collector for customer function modulpool MV45A

    V45A0002 Predefine sold-to party in sales document

    V45A0001 Determine alternative materials for product selection

    SDTRM001 Reschedule schedule lines without a new ATP check

    SDAPO001 Activating Sourcing Subitem Quantity Propagation

    User Exits For Price Determination

    • USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ)

    This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document.

    This user exit is described in detail in the "New fields in pricing" section.

    • USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)

    This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing.

    This user exit is described in detail in the "New fields in pricing" section.

    • USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)

    You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals.

    This user exit is also used in order processing.

    • USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB)

    You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.

    This user exit is also used in order processing.

    • USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB)

    You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.

    This user exit is also used in order processing.

    • USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB)

    You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.

    This user exit is also used in order processing.

    • USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA)

    You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).

    • USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA)

    In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.

    • USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA)

    You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.

    • USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB)

    This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.

    • USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB)

    Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.

    • USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB)

    In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).

    • USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB)

    You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.

    • USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB)

    This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.

    • USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB)

    This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.

    • USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA)

    You can change the KONV fields for copied price components.

    User Exits for Partner Determination

    Partner determination contains the following user exits for your use:

    • EXIT_SAPLV09A_001

    You can use this user exit to control whether an address that was entered manually and has already been used in other documents (referenced), should be referenced again if it changes or whether a new address shold be created (duplicated).

    • EXIT_SAPLV09A_002

    Call up this user exit if a customer has not been maintained in the current sales area.

    • EXIT_SAPLV09A_003

    Use this user exit to control the origin of partners in the partner determination procedure (origin X, Y or Z). If X, Y, or Z has been entered in the Origin field, this user exit is automatically called up during partner determination.

    • EXIT_SAPLV09A_004

    Use this user exit to integrate your own check in a program, that runs before the partner is saved in the document.

    For more detailed information, see the program documentation for each ofthe user exits.

    User Exits For Credit Checks And Risk Management

    Credit Check

    If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:

    • LVKMPTZZ

    • LVKMPFZ1: USER_CREDIT_CHECK1

    • LVKMPFZ2: USER_CREDIT_CHECK2

    • LVKMPFZ3: USER_CREDIT_CHECK3

    User exit for availability check

    User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.

    This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.

    Risk Management for Receivables

    • RVKMPUS2

    Using this user exit, you can define new forms of payment guarantee.

    Reward points pls.

    Regards,

    Govind.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 07, 2007 at 10:13 AM

    THANKS YOU FRIENDS

    SREE

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 07, 2007 at 10:19 AM

    hi

    refer to the link below..

    user exits in sd area

    Swapna...

    Message was edited by:

    Swapna Latha

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      hi

      swapna.. i guess u r new to the forum.. the link u have pasted is of the same post.. whn working with multiple windows.. watch out for the window ur in..

      just an info.. dont take it other way..

      its nice to c ur interet in helping out people..

      ALL THE BEST !... WELCOME TO THE FORUM..

      Thanx.. Naren..