PO document types and user exit

Hi freinds
There is a typical issue I have. The Document types required by my client is huge. I want to bring them down. Is there any way it can be done using user exits. If yes how to do the same.
Regards
Eldee

Hi Dev,
To reduce the document types you have to delete those entries from customizing tables you need not have to use user exit for that
Which document types you want to reduce?
BR
Diwakar

Similar Messages

  • Field editable in FB02 for only one document type and user

    Hi:
    I have a question about editing a field and I hope you can help me. I need to make a field editable in FB02, but only for one document type and two users. The field is BSEG-ZFBDT, Baseline payment dte.
    I have tried in ‘Document Change Rules’, make this field editable when line item not cleared, but it works for all document types and users.
    Please, any idea?
    Thanks in advance for your time.
    Best regards.

    Hi,
    You have to write a ABAP code to achieve this.
    Validation is another Option where you can mention that value is allowed in the Baseline Date field only if the User and Document type value satisfies.
    BR
    Amitash

  • Client Copy Error - ERROR: Type 'F' user exit with SYS_ERROR:

    Hello,
    We want to create a client copy from client 001 to clien 715.
    The client copy test runs successfully.
    The following error occurs in normal mode of client copy.
    1 ETA028XClient copy from "03.11.2010" "17:12:43"
    1 ETA029 System ID............................ "IS3"
    1 ETA043 Target client........................ "715"
    1 ETA030 R/3 Release.......................... "701"
    1 ETA354   Basis Support Package..............."SAPKB70107"
    1 ETA031 Host................................. "xxx"
    1 ETA000 Start in background............. ....." "
    1 ETA032 User................................. "SAP*"
    1 ETA033 Parameter
    1 ETA034 Source client........................ "001"
    1 ETA188 Source client user masters............"001"
    1 ETA185 Copier profile:......................."SAP_ALL"
    1 ETA036 Table selection
    1 ETA177 Customizing data ....................."X"
    1 ETA037 With application data................ "X"
    1 ETA155 Initialize and recreate......... "X"
    1 ETA294 Change documents are not copied
    2 ETA367XStart analysis of system "17:12:43"
    3 ETA108 "/GC1/CC_EXIT_CLIENT_DELETION" executed "        0"("        0") entries copied
    4 ETA114 Runtime "             0" seconds
    3 ETA072 Exit program "/GC1/CC_EXIT_CLIENT_DELETION" successfully executed "17:12:53"
    A2EE/SAPAPO/OM 012 "Mandant 715:" "Verbindung nicht oder fehlerhaft gepflegt:" "IS3CLNT001" " "
    2 ETA102 ERROR: Type 'F' user exit with SYS_ERROR: "/SAPAPO/OM_CLNT_COPY_DOWNLOAD"
    2 ETA534 "RCOD:" " 8" "SY-SUBRC:" " 0"
    2 ETA191 Program ended abnormally
    Can you help me?
    thx
    Torsten

    Torsten,
    Are you doing a local client copy in a SCM System. I can see it fails & is looking for SCM specific fn modules & user exits.
    If yes, has a look at this notes there are some steps that needs to be done for the transactional date:
    894490 - Client copy: Transactional data
    And re-post it in the SCM forum: SAP Advanced Planning & Optimization (SAP APO)
    - Regards, Dibya

  • Brief about enhancements and user exits

    hai,
    can any  one tell me what are enhancements and user exits in sap sd,
    their  signifcance & configuration
    regards
    sriram

    hi,
    an example of user exit
    In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the “Target *** Qty required” and the “Target *** Date” for a specific customer who was not sending “*** Qty Received” by him.
    So for that specific customer we used the search term and added the same in the “Data 4” field of the IDOC under segment E1EDK09.
    There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating “*** Issued” and then find out the difference from “Target *** Qty” and get “*** Qty Received” for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
    <b>User exits in SD</b>
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Pl reward if helpful.
    Thanks
    Sadhu Kishore

  • BADI and User exit for MIGO item and header enhancement

    We want to add three extra fields in MIGO screen for specific movement type 101 . Two fields at item level and one filed at header level .
    Item level fields are independent fields it will store in separate z-table and z-field and dont't have any relation with other table .
    but header field has some relation with quantity field in item level . All the item quantity has to add up in header , Is it possible to add up .
    What are the BADI and user exit need to use for this enhacement and etc required details

    Hi Raghavendra,
    Use BAdI MB_MIGO_BADI.
    It has all the methods that cater your requirement.
    Try to have a design such that you can store the values within the document by enhancing the tables using Append Structures, they surely have a link with the document.
    regards,
    Aabhas K Vishnoi

  • What is the difference between customer exits and user exits?

    hello friends,
    what is the difference between customer exits and user exits?

    Hi
    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 SAP’s 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.     *-- Mani
    The following document is about exits in SAP :-
    The R/3 enhancement concept allows you to add your own functionality to SAP’s 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. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    Types of Exits 
    There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
    Menu Exits
    Menu exits add items to the pulldown 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 item’s 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 subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.
    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. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs. 
    These calls have the following syntax: 
    CALL CUSTOMER-FUNCTION ‘001’.
    Field Exits
    Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.  Example: The data element BBBNR identifies a company’s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100. 
    The field exit concept lets you create a special function module that contains this logic. 
    You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number. 
    In 4.6c, you can use "RSMODPRF" program to create field exits.
    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'.
                             SET SCREEN 100.
                             LEAVE SCREEN.
                 ENDCASE.
          ENDCASE.

  • What is the Difference 'VOFM' and 'User-Exit' ?

    What is the Difference 'VOFM' and 'User-Exit' ?

    If you need to implement any of these User exits, you first create a project for the user exit, then assign the user exit(s) to your project. Then you write the coding for the user exit, and finally activate the project.
    For general information about user exits, in the R/3 Library, go to Basis components and look at the Enhancements section. In addition there is detailed information about each user exit that you can access when you assign it to your project (see below).
    Activities
    Start by creating your project.
    1. Enter a name for your project.
    2. Select Modification -> Create.
    3. Enter a short text for your project and select save.
    Next assign the user exit to your project.
    4. Select Components.
    5. Enter the name(s) of the user exits you want to implement.
    6. Select SAP documentation, if you want detailed information on this user exit.
    7. Select save.
    8. Select back.
    Next make your coding modifications.
    9. Select enhancement components.
    10. Select change.
    11. Select the user exit you want to write code for.
    12. Select the include zxpbco01.
    The system will then prompt you to create this include, and you can continue to write your coding in it.
    Next activate your project.
    13. Return to the initial screen and select activate project.
    Routines
    Routines are short sub-programs that carry out various checks during document processing. In the SD module, you can create and process routines for copying requirements, data transfer, requirements and formulas using transaction VOFM. Besides the routines delivered to you with the system, you can create your own individual routines.
    Transaction VOFM allows you to follow a standardized procedure for creating routines. The name ranges are predefined for routines delivered to you with the system and for routines created by the customer. This name convention guarantees that your own routines are not overwritten during a Release upgrade.
    Copying requirements and data transfer
    The routines for coying requirements and data transfer are defined for the document types sales orders, deliveries, billing documents, sales activities, as well as for texts. You specify copying requirements and the data transfers when defining the document flow for each document type. You enter the routines for texts in the access sequences for texts.
    o Copying requirements determine which data is copied during the copying of documents. A copying requirement could define, for example, that the same customer must appear in the document header when you copy an inquiry to a quotation.
    o Routines for data transfer make a detailed control of the copying of fields possible. A data transfer could define, for example, that particular item fields can only be copied in combination with other particular fields and can only be copied into contracts or credit and debit memos.
    Requirements and formulas
    Routines for requirements and formulas are used for functions using the condition technique. You enter these routines in the pricing procedure or the condition types. Requirements are also used for statistics.
    o A requirement in pricing can determine that an access is dependent on a particular precondition. It can carry out a check of the document currency, for example, and, depending on whether it is a foreign or the local currency, allow or deny the access.
    o Formulas are used in pricing to define various factors for pricing. Formulas are defined for scale base value, condition base value, condition amount, group key, and rounding rules. The formula for a rounding rule could define, for example, that all calculated amounts are rounded to two places behind the decimal point during a price change of the condition record. The formula for a condition base value could define, that the header discount is distributed among the order items according to volume an not value of the item, as is the case in the standard SAP R/3 System.
    Creating routines
    There are two methods to create a routine
    1. Creating by overwriting
    When using this method, a note appears as a commentary in the routine to be newly created.
    2. Creating
    When creating a new routine, an ABAP with internal number assignment is created.
    You always have to activate a new routine before using it. Each routine for requirements and formulas, copying requirements and data transfers is stored in a separate program. For each new routine an entry is added in table TFRM and TFRMT. For each routine, a long text can be stored as a text module.
    Most routines must be changed in client 000. Transaction VOFM can be transported as XPRAs, which means that after the import all routines can be activated.
    Name ranges for routines
    The standard routines are to be within the number range 001-599 (for 2 digit formula numbers, 01-49)
    The user routines are to be within the number range 600-999 (for 2 digit formula numbers, 50-99).

  • Diff b/w "Customer exits" and "User-exit"

    Hi,
    What is the difference b/w customer exits and user-exit and also please explain me what are the various types of customer and user-exits.
    Thanks in advance.
    Ramana

    Hi,
    Types of Exits
    There are several different types of customer exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
    Menu Exits
    Menu exits add items to the pulldown 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 item’s 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 subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.
    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 pulldown 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.
    SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs. These calls have the following syntax: CALL CUSTOMER-FUNCTION ‘001’.
    <b>User exits:</b>
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-code-samples/userexits%20in%20a%20transaction.doc
    In order to find out the user exits for any tcode,
    1. get the developement class of the tcode from SE93.
    2. Now goto transaction SMOD and press F4,
    3. give in the Deve class in the dev class and Press ENTER
    this will show u the exits for any tcode.
    or execute this report
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    which gives the list of exits for a tcode
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
    For information on Exits, check these links
    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/abap/a-short-tutorial-on-user-exits.htm
    http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
    http://www.easymarketplace.de/userexit.php
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
    Check out these links too...
    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.planetsap.com/userexit_main_page.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    USER EXITS
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
    ****Reward points if helpful.
    All the best

  • Differences between BADIS and User-exits

    Hi everybody,
    I am new to ABAP and wonder what are the differences between BADIS and User-Exits. I read paper but did not find a SAP documentation yet.
    Does anybody know where to find a sap document which explains both technologies?
    Greetings, AD

    Hi,
    User-Exit is a specific place in a transaction-process where SAP offers
    third parties to include there own business functionality. Actually
    User-Exit is the namespace used for Exits programmed by SAP specifically
    for SD. For the other modules it's called Customer-Exit.=20
    >Business Add-Ins (BADI) =20
    The use of object orientated code within SAP has lead to new method of
    enhancing standard SAP code called Business Add-Ins or BADI's for short.
    Although the implementation concept is based on classes, methods and
    inheritance you do not really have to understand this fully to implement
    a BADI.
    For better understanding visit.
    http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/779183#
    Hope it was useful.
    Thansk,
    Sandeep.

  • Types of USER EXITS user for enhancement

    Can any one please let me know the types of USER EXITS user for enhancement normslly used in SD module.
    Thanks

    Hi,
    here you can find what's enhancement (overview), the steps, and exits in bw ...
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59069d90-0201-0010-fd81-d5e11994d8b5
    and later abap in bw may useful
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4493c4a6-0301-0010-62a2-efd6ded61e04
    for general understanding of enhancement, take a look this 'Changes to the SAP Standard ' doc
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975a043b111d1896f0000e8322d00/frameset.htm
    ... Enhancements represent potential customer requirements that have not been developed in the standard software. Instead, the standard provides for further development of such exits at the customer site, using logic specific to the customer ...
    some threads on data extraction enhancement
    Enhancement
    Re: User exit
    Hareesh

  • Difference between customer exit and user exit?

    hi experts
    difference between customer exit and user exit?

    These r the main differences between user exits and customer exits
    1) user exits r subroutines where as customer exits r function modules
    2) user exits r not upgraded where as customer exits r will upgrade
    3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
    4) customer exits r reusable where as user exits r not reusable.
    Also:
    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
    1. Previously there were only user-exits.
    2. Then came the concept of customer-exits.
    3. user exits were nothing but subroutines
    FORM/PERFORM
    called from standard programs.
    4. The FORM defintion was placed inside
    an empty include file.
    5. So It was called EVERYTIME.
    and we need to MODIFY/REPAIR the
    standard include .
    6. Then it came with concept of customer-exit
    7. It consists of calling a FUNCTION MODULE,
    which is called only if
    the user-exit is ACTIVATED (other wise not called)
    In this case, the code in put inside
    a pre-defined Z include.
    8. Functionality of both is same, howerver
    we can note the following important differences
    a) Customer exit is called only if activated.
    (hence, it does not waste resources)
    b) in customer exit, REPAIR does not happen
    to the standard include.
    Exits are basically the hooks whcih SAP has provided to add your own code.
    User Exits: These are provided only SD module .
    They are Empty subroutines with naming like USEREXIT_.
    We need to have Access key to implement them.
    Customer Exits: These are enhancement techniques.
    There are defined in SMOD and implemented in CMOD.
    Types of Customer exits: Function exit, Screen Exit, Menu exit.
    User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
    Customer Exit,
    Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
    Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
    Customer Exit
    SAP creates customer exits for specific programs, screens, and menus within standard 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.
    If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
    • They do not affect standard SAP source code
    When you add new functionality to your SAP System using SAP’s 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 SAP’s standard software package.
    • They do not affect software updates
    When you add new functionality to your SAP System using SAP’s 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.
    Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    User Exits: allow you to add additional functions to the SAP standard.
    Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
    Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
    Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
    reward points if found useful
    regards
    palak

  • BADI and User Exit...

    Hi Guys,
    From my understanding and trying out tutorials on BADI, what is the difference between BADI and User Exit?
    What is the best way on how to use User Exit? There are so many user exit provided by SAP.
    Thanks and appreciated.
    William Wilstroth.

    Hi
    check this link,hopefully you will get your problem solved.
    Re: User Exit / BADI
    As far as <b>What is the best way on how to use User Exit? There are so many user exit provided by SAP.</b> is concerned. You have to choose an user exit according to your requirement. e.g MM06E005 is used to only for the purpose <b>Customer fields in purchasing document</b>
    Hope this helps
    regards
    Amit
    Message was edited by: Amit Kumar

  • Reading the description of Sales document type and Profit centre from table

    Hi
    I want to print the description of Sales document type and Profit center on output
    I have checked in table TVAK and CEPC  but i am unable to pick description against the code
    Can anyone please suggest from where can i capture the description of sales document type and profit centre
    Thanks and Regards
    Sunil Srinivasan

    Hi
    If you have the sales document number VBELN then pass this VBELN in to table VBAK and you can get the sales document type VBAK-AUART.
    Now pass the same VBELN to VBAP table here you can get the Profit Center VBAP-PRCTR
    For sales Document type description you pass the VBAK-AUART values into table TVAKT  table and get the values for TVAKT-BEZEI is you sales document type description
    For Profit center description goto table CEPCT and enter the profit center you will get the
    KTEXT
    LTEXT
    MCTXT
    regards
    Prashanth
    Edited by: Prashanth@SD on Oct 25, 2010 12:29 PM

  • New Document Types and new Number Ranges

    Hi,
    Plz tell me How to configure New Document Types and new Number Ranges for Services and Asset Purchases.
    How can i maintain Services with or without Master data.
    Plz tell how much services are there and how to configure step by step

    Hi
    New document type can be configured in SPRO - SAP IMG- Material management - Purchasing - Purchase order - Define number rabges / define document types.
    With out service master straightaway you can create the Service PO with account assigment.
    AC03 - Create service master record.
    ML10 - Model service specifications
    Then Service conditions ML33 or ML39 or ML45
    Create the PO and then do the service entry in ML81N
    Regards,
    Raman

  • BBP_BS_GROUP_BE for new document type and number range

    Hi gurus,
    I am working on Classic scenario in SRM and currently have used the above BADI to use a different document type and number range when creating the PO in the backend system. It all works fine. The only thing is I noticed that the BE_DOC_TYPE field in the shopping cart is still reflected as 'EC' even though the PO created in ECC is for example EC1. My question: Is this standard SRM? If so, is it common to leave this field as it is or is it advisable for us to change the document type to EC1 as well? Also, is there any implication in standard SRM reporting and downstream processes that you are aware of?
    Appreciate any advice on the above.
    Cheers!
    Sf

    We have ended up having to populate the document type on a custom field or alternatively replace the existing one.

Maybe you are looking for

  • TS3899 Why can't I get my Gmail account to work after my ipad reset?

    Took my ipad to Apple store due to a software problem which was fixed by doing a reset. I then restored and backed up/sync'd my ipad in ITunes and iCloud. Now I can't get my gmail account to work on my iPad. It won't send or receive emails and I keep

  • Change Name of Window on Projector

    How do you change the name of the projector window from saying "FLASH Player 9" to a name that I define? Any help is much appreciated.

  • Multiple composite primary key in Master Table

    Dears , I am try to find any solution about Multiple composite primary key by search in forum , but i didn't success ... i am try to built master detail , the master structure table built with multiple composite primary key , i know that apex 4.2 sti

  • Yosemite error 150:30. Photoshop CS4

    Hard drive was failing so new hard drive and Yosemite. Now I get an error when trying to launch PS CS4. Error code 150:30 Licensing for this product has stopped working. Any ideas? Don't want to upgrade.

  • Editing file over the web

    I'm not sure whether this is the correct section to post this problem.... anyway.... yesterday one of my friend demo to me a lotus based application for document management system.... it is a web based application. User just invoke any of his/her fav