API User Hook for Restricting Category Creation in a sepcific catalog

Q: API User Hook for Restricting Category Creation in a sepcific catalog by a specific responsibility. I want to capture GO button process event?
Hi All,
Can anyone help me if anyone have used user hook for OLM? My requirement is to restrict course creation for the specific category... when we select category and select course and click on go button which process is calling? How can we identify the BP Package and Procedure name of that GO button?
urgent reply shall be a great help.
thank you.
Regards,
AD

OK, I just tried to insert an element entry from the API and it works perfectly
The problem seems to be coming from the form. Is the form not using an API?
If this is the case, should I do a personalization and run a PL/SQL procedure each time a change is made?

Similar Messages

  • Creating API User Hooks for Saudi HRMS

    Dear All,
    I want to create API User hooks for Person Extra Information Type,Any one could help me.
    Thanks and regards,

    If you want to learn how a user hook works, you can check the metalink note 73170.1. Or you can visit the following link.This guy has given the whole content in his blog.
    http://shrigupta.blogspot.com/2010/06/understanding-and-using-api-user-hooks.html
    Hope this helps.

  • HR API User Hooks - Can I use to change a value in the table the API for?

    I am trying to initialize a descriptive flexfield on per_all_people_f. I originally tried doing the initialization using a “before row insert” database trigger directly on the table per_all_people_f. Seems to work great in the People form (PERWSHRG), but does not seem to work consistently when a new employee is entered through a template like Enter Employees (PERWSQHM).
    Does anyone know if you can use an API User Hook to initialize a value on one o the tables the API is inserting? For example, could I put a "Before Process" user hook on the "Create_ Employee" API to change the value of a descriptive flexfield?
    Any other good ideas?
    Currently I have a concurrent request that runs once every 30 minutes to default the descriptive flexfield. The delay is causing issues.

    In such cases you should write the code to default the values in the front end PUIs. As one person pointed out, User hooks are provided either to validate the already entered values, or to insert/update data in some custom tables but not for updating values in the same table where data is being inserted/updated.
    BTW for your information:-
    Person form (People Enter and Maintain) does not use APIs so anything written inside the user hook would be ignored by the application when this form is used. (The reason is this is one of the oldest form in HRMS, was created even before the concept of user hook came).
    Template form PERWSQHM uses APIs, so user hook is called when this form is used to create/update the data.
    Hope this is useful.

  • USER Hook for Changer Manager function

    Dear All,
    I need to know that is there any user hook for Manager Self Service -- Change Manager function for employee.
    If yes then please give me the module name/id for the user hook.
    If no then how can I set custom validations on this page.
    Regards.

    You should look for the update assignment api.
    select * from hr_api_modules
    where module_name like '%UPDATE%ASG%'
    Depending on the legislation, you will have different modules/packages/procedures.

  • What are the User Exits for Sales Order creation process?

    Hi,
    what are the User Exits for Sales Order creation process? how can I find them?
    thanks in advance,
    will reward,
    Mindaugas

    Please check this info:
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    Regards
    Eswar

  • User Exit for ME21 PO Creation at the time of saving--Urgent

    Hi,
    Can some one help me out in finding the user exit for PO creation at the time of saving.
    The Requirement is:
    I need to create a custom field in EKKO table.
    After appending the structure with the field to the EKKO table, i need to create a PO.
    Now i need to update the field which has been created at the time of pressing the SAVE button.
    I need to update the EKKO table it self.
    I could find the user exits but none of them have the EKKO table either in Changing or in Tables.
    Thanks,

    Hi,
              You may want to check this user exits.
    EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
    EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
    Here is the list of available user exits for ME21.
    EXIT_SAPMM06E_001 - Other Number Range or Own Document Number
    EXIT_SAPMM06E_004 - User Exit for Cust.-Specific Control of Import Data Screens in Purchasing
    EXIT_SAPMM06E_005 - Field Selection Control: Vendor Address Screen
    EXIT_SAPMM06E_006 - Export Data to Customer Subscreen for Purchasing Document Header (PBO)
    EXIT_SAPMM06E_007 - Export Data to Customer Subscreen for Purchasing Document Header (PAI)
    EXIT_SAPMM06E_008 - Import Data from Customer Subscreen for Purchasing Document Header
    EXIT_SAPMM06E_009 - Reset Customer Data at Beginning of New Document (Without Dialog)
    EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
    EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
    EXIT_SAPMM06E_014 - Read Customer-Specific Data when Importing Purchasing Document
    EXIT_SAPMM06E_016 - Export Data to Customer Subscreen for Purchasing Document Item (PBO)
    EXIT_SAPMM06E_017 - Export Data to Customer Subscreen for Purchasing Document Item (PAI)
    EXIT_SAPMM06E_018 - Import Data from Customer Subscreen for Purchasing Document Item
    EXIT_SAPMM06E_020 - User Exit: Change Document for Requisitions (Conversion into PO)
    EXIT_SAPMM06E_021 - Fulfillment of Target Value: Release Orders Against a Contract
    <b>Reward points</b>
    Regards

  • Need to find user exit for Auto TO creation

    Dear SAP WM experts
    I need to filter the TR getting converted into TO automatically
    I can see, in configuration, that an exit is suggested for the same:
    This configuration refers to OMKZ transaction, package LVSC
    When I search using the same in SMOD, I do not get any entries
    Any help would be appreciated!
    Thanks
    Yogesh.

    Hi Yogesh!
    For "Automatic TO creation (background processing)", the following user exits are available:
    MWMTOAU1 Selection of requirements for automatic creation of orders.
    MWMTOAU2 Reference number assignment.
    MWMTOAU3 Selection of posting change notices for automatic creation of transfer orders.
    See Develop User Exits for Warehouse Management - Warehouse Management - SAP Library
    My guess is, that the MWMTOAU1 user exit is the one you are looking for.
    The SAP documentation says:
    "With this user exit, you can select transfer requirements for the
    automatic TO creation according to your own criteria by means of report
    RLAUTA10."
    Best Regards!
    Tim Lutz

  • User Exit for New Field Creation & Updation at Sales Order Level

    Hi All,
    I want to create one new field in Additional Data B Tab of Sales Order.
    Also when the sales order is created with reference to a Contract, that Contract number to be updated in that field.
    Which user exit need to be used for this field Creation & Updation at the time of order creation? Is it MV45AFZZ?
    Pls suggest.
    Rgds,
    Senni.B

    Hi
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Regards
    Madhu

  • User exit for Credit Memo creation

    I want to create an IDOC when the credit memo will be created.
    What is the name of the user exit  where I can write the IDOC generation code ?
    Edited by: Alvaro Tejada Galindo on Feb 18, 2008 9:47 AM

    IDoc Inbound User Exits
    1. ACC_BILLING
    Accounting: Post invoice (OAG: LOAD RECEIVABLE)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    2. ACC_EMPLOYEE_EXP
    FI/CO: HR posting GL (AcctngEmplyeeExenses)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    3. ACC_EMPLOYEE_PAY
    FI/CO: HR posting AP (AcctngEmplyeePaybles)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    4. ACC_EMPLOYEE_REC
    FI/CO: HR posting AR (AcctngEmplyeeRcvbles)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    5. ACC_GL_POSTING
    Accounting: General G/L account posting
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    6. ACC_GOODS_MOVEMENT
    Accounting: Post goods movement (OAG: POST JOURNAL)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    7. ACC_INVOICE_RECEIPT
    Accounting: Post invoice receipt (OAG: LOAD PAYABLE)
    - ACBAPI01 EXIT_SAPLACC4_001 Accounting: Customer enhancement to BAPI interfaces
    8. ACLPAY Accounting: Inbound invoice
    - ACCID001 EXIT_SAPLACC1_031 IDoc ACLPAY: Userexit for creditor in accounting document
    - ACCID001 EXIT_SAPLACC1_032 IDoc ACLPAY: Userexit for GL posting in accounting document
    - ACCID001 EXIT_SAPLACC1_033 IDoc ACLPAY: Userexit for taxes in accounting document
    9. ACLREC
    Accounting: Billing document
    - ACCID001 EXIT_SAPLACC1_011 IDoc ACLREC: Userexit for debitor in accounting document
    - ACCID001 EXIT_SAPLACC1_012 IDoc ACLREC: Userexit for GL posting in accounting document
    - ACCID001 EXIT_SAPLACC1_013 IDoc ACLREC: Userexit for taxes
    10. ACPJMM
    Posting in accounting from materials management
    - ACCID001 EXIT_SAPLACC1_021 IDoc ACPJOU: Userexit for GL posting in accounting document
    11. ARTMAS
    Create and change of material master (Retail)
    - MGV00003 EXIT_SAPL1001_003 Enhancement for article master: IDoc inbound
    12. BLAOCH
    Purchasing contract change
    - MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
    - MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
    - MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
    13. BLAORD
    Purchasing contracts
    - MM06E002 EXIT_SAPLEINN_001 Customer enhancements for Idocs: contracts
    - MM06E002 EXIT_SAPLEINN_002 Customer enhancements for Idocs: contracts
    - MM06E002 EXIT_SAPLEINN_003 Customer enhancements for Idocs: contracts
    14. BLAREL
    Release order documentation for distributed contracts
    - MM06E001 EXIT_SAPLEINM_004 Customer enhancements for release documentation inbound
    15. COND_A
    Conditions: master data for price determination
    - VKOI0001 EXIT_SAPLVKOI_001 Interchange of Conditions: Inbound Processing Modifications E1KOMG Segment
    - VKOI0001 EXIT_SAPLVKOI_002 Interchange of Conditions: Inbound Processing Customer Segments
    16. CREMAS
    Distribute vendor master
    - VSV00001 EXIT_SAPLKD02_001 Inbound: Read and process vendor segments
    17. DEBMAS
    Customer master
    - VSV00001 EXIT_SAPLVV02_001 Inbound: Read and update additional customer master segments
    18. DELINS
    Delivery schedule/JIT schedule
    - VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
    - VED40001 EXIT_SAPLVED4_002 Copying Data to Screens for Incoming EDI Docs
    - VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
    - VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
    19. DESADV
    Delivery: Shipping notification
    - LMELA010 EXIT_SAPLEINM_010 Customer enhancement shipping notification inbound: line item
    - MM06E001 EXIT_SAPLEINM_006 Customer enhancements for shipping notification inbound
    - V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
    - V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
    - V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
    - V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
    - V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
    - V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
    20. DOCMAS
    Master document
    - CVDS0001 EXIT_SAPLCVALE_001 Userexit for ALEDVS (DOCMAS inbound)
    21. DOLMAS
    Document-object links
    - CVDS0001 EXIT_SAPLCVALE_003 Userexit for ALEDVS (DOLMAS inbound)
    22. EDLNOT
    EDL delivery notes
    - VED40001 EXIT_SAPLVED4_001 Modify Warnings in Table XVBFS
    - VED40001 EXIT_SAPLVED4_002 Copying Data to screens for Incoming EDI Docs
    - VED40001 EXIT_SAPLVED4_003 Customer-Specific Changes in the Workflow Parameters
    - VED40001 EXIT_SAPLVED4_004 Determination of mail receiver during inbound processing
    23. FIDCC1
    Send entire FI documents (user exit 003/4)
    - F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    - F050S002 EXIT_SAPLF050_004 FIDCC1 IDoc inbound: Change IDoc / do not process
    - F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
    - F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
    24. FIDCC2
    Send entire FI documents (user exit 005/6)
    - F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    - F050S003 EXIT_SAPLF050_006 FIDCC2 IDoc inbound: Change IDoc / do not process
    - F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
    - F050S005 EXIT_SAPLF050_009 IDoc inbound: change fields in parked documents
    25. FIDCMT
    Sending single items for FI-GL
    - F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    - F050S005 EXIT_SAPLF050_008 IDoc inbound: change fields in ACC structures (FI document)
    26. FINSTA
    Bank Statement
    - FEDI0005 EXIT_SAPLIEDP_201 FI-EDI: inbound - bank statement/ Lockbox - Final processing
    - FEDI0005 EXIT_SAPLIEDP_202 FI-EDI: inbound - bank statement/ Lockbox - Processing of segments
    27. FIROLL
    General ledger rollup for FI-GL (delta f. line items FIDCMT)
    - F050S001 EXIT_SAPLF050_002 IDoc inbound: read user-defined IDoc segment
    28. GSVERF
    Cred. memo procedure
    - VED50001 EXIT_SAPLVED5_001 User Exit for Condition Value Tolerances in the Self- Billing Procedure
    - VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
    - VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
    29. HRMD_A
    HR: Master data and organizational data (appl. system)
    - RHALE001 EXIT_SAPLRHA0_002 HR-CA: ALE inbound processing: Export parameter
    - RHALE001 EXIT_SAPLRHAL_002 HR-CA: ALE inbound processing: Change info type data
    - RHALE001 EXIT_SAPLRHAL_004 HR-CA: ALE inbound processing: conversion segment/ info type
    30. INFREC
    Purchasing info record
    - MMAL0004 EXIT_SAPLMEAI_004 ALE source list distribution: inbound processing userdefined data
    - MMAL0004 EXIT_SAPLMEAI_003 ALE purchasing info record distribution: inbound processing segments
    31. INVOIC
    Invoice / Billing document
    - FEDI0001 EXIT_SAPLIEDI_001 FI-EDI: Invoice receipt - Determine G/L account per invoice line
    - FEDI0001 EXIT_SAPLIEDI_002 FI-EDI: Invoice receipt - Determine add. acct assignm. per line item
    - FEDI0001 EXIT_SAPLIEDI_003 FI-EDI: Invoice receipt - Fill the screen field 'Allocation'
    - FEDI0001 EXIT_SAPLIEDI_004 FI-EDI: Invoice receipt - Determine the segment text
    - FEDI0001 EXIT_SAPLIEDI_005 FI-EDI: Invoice receipt - Determine the name of the BDC session
    - FEDI0001 EXIT_SAPLIEDI_011 MM-EDI: Invoice receipt - Determine purchase order item
    - FEDI0001 EXIT_SAPLIEDI_101 FI-EDI: Invoice receipt INVOIC01 - additional assignment
    - FEDI0001 EXIT_SAPLIEDI_102 FI-EDI: Invoice receipt INVOIC01 - add data
    - FEDI0001 EXIT_SAPLIEDI_111 MM-EDI: Invoice receipt INVOIC01 - additional assignment
    - FEDI0001 EXIT_SAPLIEDI_112 MM-EDI: Invoice receipt INVOIC01 - add data
    - MRMH0002 EXIT_SAPLMRMH_011 Logistics Invoice Verification:inboud EDI message, company code
    - MRMH0002 EXIT_SAPLMRMH_012 Logistics Invoice Verification:inboud EDI message, control flags
    - MRMH0002 EXIT_SAPLMRMH_013 Logistics Invoice Verification:inboud EDI message, assignment
    - MRMH0002 EXIT_SAPLMRMH_014 Logistics Invoice Verification:inboud EDI message, segments
    - MRMH0002 EXIT_SAPLMRMH_015 Logistics Invoice Verification:inbound EDI message, before posting
    32. LIKOND
    Listing conditions
    - WSOR0001 EXIT_SAPLWSOI_001 Enhancement for assortments: inbound IDoc
    33. MATMAS
    Material Master
    - MGV00001 EXIT_SAPLMV02_002 Enhancement for material master IDoc: Update
    34. MRESCR
    Create reservation
    - SAPLMEWB EXIT_SAPLMEWB_001 Customer exit for processing of reservations via BAPIs
    35. ORDCHG
    Purchase order/order change
    - MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
    - MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
    - VEDB0001 EXIT_SAPLVEDB_001 SD EDI incoming change orders: read additional data from IDoc
    - VEDB0001 EXIT_SAPLVEDB_002 SD EDI incoming change orders: additional data for dynpros
    - VEDB0001 EXIT_SAPLVEDB_003 SD EDI incoming change orders: further activities after calling
    - VEDB0001 EXIT_SAPLVEDB_004 SD EDI incoming change orders: closing activities per
    - VEDB0001 EXIT_SAPLVEDB_005 SD EDI incoming change orders: closing activities by order block
    - VEDB0001 EXIT_SAPLVEDB_006 SD EDI incoming change orders: setting order type
    - VEDB0001 EXIT_SAPLVEDB_007 SD EDI incoming change orders: additional checks of IDoc
    - VEDB0001 EXIT_SAPLVEDB_008 SD EDI incoming change orders: error handling
    - VEDB0001 EXIT_SAPLVEDB_009 SD EDI incoming change orders: additional checks of IDoc segments
    - VEDB0001 EXIT_SAPLVEDB_010 SD EDI incoming change orders: manipulation of status ecords
    - VEDB0001 EXIT_SAPLVEDB_012 SD EDI incoming change orders: change internal table
    36. ORDERS
    Purchase order / order
    - MCP20008 EXIT_SAPLMCP2_008 User exit: Processing of purchase order header
    - MCP20008 EXIT_SAPLMCP2_009 User exit: Processing of purchase order item
    37. ORDERS
    Purchase order / order
    - MM06E001 EXIT_SAPLEINM_012 MM EDI ORDERS/ ORDCHG: enhancement configuration
    - MM06E001 EXIT_SAPLEINM_013 MM EDI ORDERS/ ORDCHG: enhancement configuration
    - VEDA0001 EXIT_SAPLVEDA_001 SD EDI incoming orders: read additional data from IDoc
    - VEDA0001 EXIT_SAPLVEDA_002 SD EDI incoming orders: additional data for dynpros
    - VEDA0001 EXIT_SAPLVEDA_003 SD EDI incoming orders: further activities after calling
    - VEDA0001 EXIT_SAPLVEDA_004 SD EDI incoming orders: closing activities per order
    - VEDA0001 EXIT_SAPLVEDA_005 SD EDI incoming orders: closing activities by order block
    - VEDA0001 EXIT_SAPLVEDA_006 SD EDI incoming orders: setting order type
    - VEDA0001 EXIT_SAPLVEDA_007 SD EDI incoming orders: number of ordering party
    - VEDA0001 EXIT_SAPLVEDA_008 SD EDI incoming orders: error handling
    - VEDA0001 EXIT_SAPLVEDA_009 SD EDI incoming orders: additional checks of IDoc segments
    - VEDA0001 EXIT_SAPLVEDA_010 SD EDI incoming orders: manipulation of status records
    - VEDA0001 EXIT_SAPLVEDA_011 SD EDI incoming orders: change internal table
    - WVFB0001 EXIT_SAPLWVFB_002 Customer exists for store order PO confirmationdata seg.
    38. ORDRSP
    Purchase order / order confirmation
    - MM06E001 EXIT_SAPLEINM_005 Customer enhancements for order confirmation inbound
    - MM06E001 EXIT_SAPLEINM_007 Customer enhancements inbound confirmation: reading
    - MM06E001 EXIT_SAPLEINM_008 Customer enhancements inbound confirmation: final
    - WVMI0001 EXIT_SAPLWVMI_003 ORDRSP VMI inbound, modification before creating purchase order
    39. PORDCR
    Create purchase order
    - SAPLMEWP EXIT_SAPLMEWP_002 Customer exit for processing of purchase orders via BAPIs
    40. PREQCR
    Create purchase requisition
    - SAPLMEWQ EXIT_SAPLMEWQ_001 Customer exit for processing of requisitions via BAPIs
    41. PROACT
    Stock and sales data
    - WVMI0001 EXIT_SAPLWVMI_002 IDoc PROACT inbound: prior to processing
    42. REMADV
    Payment advice
    - FEDI0002 EXIT_SAPLIEDP_101 FI-EDI: Incoming pmnt advice - Extended allocatn of IDOC -> applicatn data
    - FEDI0002 EXIT_SAPLIEDP_102 FI-EDI: Incoming pmnt adivce - Closing allocatn of IDOC -> applicatn data
    43. REQOTE
    Inquiry
    - VEDQ0001 EXIT_SAPLVEDQ_001 SD EDI inbound inquiry: read additional data from IDoc
    - VEDQ0001 EXIT_SAPLVEDQ_002 SD EDI inbound inquiry: additional data for dynpros
    - VEDQ0001 EXIT_SAPLVEDQ_003 SD EDI inbound inquiry: further activities after calling
    - VEDQ0001 EXIT_SAPLVEDQ_004 SD EDI inbound inquiry: closing activities per inquiry
    - VEDQ0001 EXIT_SAPLVEDQ_005 SD EDI inbound inquiry: closing activities by inquiry block
    - VEDQ0001 EXIT_SAPLVEDQ_006 SD EDI inbound inquiry: setting inquiry type
    - VEDQ0001 EXIT_SAPLVEDQ_007 SD EDI inbound inquiry: number of sold-to party
    - VEDQ0001 EXIT_SAPLVEDQ_008 SD EDI inbound inquiry: error handling
    - VEDQ0001 EXIT_SAPLVEDQ_009 SD EDI inbound inquiry: additional checks of IDoc segments
    - VEDQ0001 EXIT_SAPLVEDQ_010 SD EDI inbound inquiry: manipulation of status records
    - VEDQ0001 EXIT_SAPLVEDQ_011 SD EDI inbound inquiry: change internal table
    44. SBINV
    Credit memo procedure with invoice creation
    - VED50001 EXIT_SAPLVED5_002 User Exit for messages in the Self-Billing Procedure SBINV
    - VED50001 EXIT_SAPLVED5_003 User Exit for Tolerances in the Self- Billing Procedure SBINV
    - VED50001 EXIT_SAPLVED5_004 Customer-Function for changing invoice data SBINV
    - VED50001 EXIT_SAPLVED5_005 Customer-Specific Changes in Workflow Parameters
    - VED50001 EXIT_SAPLVED5_006 Copying Data to Screens for Incoming EDI Docs
    45. SDPACK
    Packing confirmation
    - VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
    - VMDE0004 EXIT_SAPLVMDE_004 Shipping Interface: Message SDPACK (Packing, Inbound)
    46. SDPICK
    Picking confirmation
    - VMDE0001 EXIT_SAPLVMDE_001 Shipping Interface: Error Handling - Inbound IDoc
    - VMDE0003 EXIT_SAPLVMDE_003 Shipping Interface: Message SDPICK (Picking, Receipt)
    47. SHP_IBDLV_CONFIRM_DECENTRAL
    Confirmation (Inbound Delivery)
    - V50B0001 EXIT_SAPLV50I_002 User exit for BAPI Verification of Inbound Deliveries
    48. SHP_IBDLV_SAVE_REPLICA
    BAPI Function Module for Duplication of Outbound Deliveries
    - V50B0001 EXIT_SAPLV50I_001 User exit for BAPI Duplication of Inbound Deliveries
    49. SHP_OBDLV_CONFIRM_DECENTRAL
    Confirmation (Customer Delivery)
    - V50B0001 EXIT_SAPLV50I_004 User exit for BAPI Verification of Outbound Deliveries
    50. SHP_OBDLV_SAVE_REPLICA
    BAPI Function Module for Duplication of Outbound Deliveries
    - V50B0001 EXIT_SAPLV50I_003 User exit for BAPI Duplication of Outbound Deliveries
    51. SHPCON
    Delivery: Shipping confirmation
    - V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
    - V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
    - V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
    - V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
    - V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
    - V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
    52. SHPMNT
    Shipping outbound
    - V55K0020 EXIT_SAPLV55K_020 IDoc SHPMNT: Modification Control/ Data before processing
    - V55K0021 EXIT_SAPLV55K_021 Processing of segments IDoc SHPMNT
    - V55K0022 EXIT_SAPLV55K_022 Update of user defined tables for inbound IDoc SHPMNT
    53. SRCLST
    Source List
    - MMAL0002 EXIT_SAPLMEAI_001 ALE source list distribution: inbound processing segments
    - MMAL0002 EXIT_SAPLMEAI_002 ALE source list distribution: inbound processing user defined data
    54. SRVMAS
    Master data service master
    - BASI0001 EXIT_SAPLBASI_001 Userexit IDoc inbound service master: segment
    - BASI0001 EXIT_SAPLBASI_002 Userexit IDoc inbound service master: database
    55. TPSSHT
    Shipping planning system: Transfer planned shipments
    - V56I0010 EXIT_SAPLV56I_010 IDoc TPSSHT01: Input of planned shipments: Modification of IDoc segments
    - V56I0010 EXIT_SAPLV56I_011 IDoc TPSSHT01: Input of planned shipments: modification of transport tab, processing
    - V56I0010 EXIT_SAPLV56I_012 IDoc TPSSHT01: Input of planned shipments: update of own tables
    56. WHSCON
    Delivery: Stock confirmation
    - V55K0001 EXIT_SAPLV55K_001 Delivery (inbound): Take data
    - V55K0002 EXIT_SAPLV55K_002 Delivery (inbound): Prepare processing
    - V55K0003 EXIT_SAPLV55K_003 Delivery (inbound): Evaluate result
    - V55K0011 EXIT_SAPLV55K_011 Shipping notification (inbound): Take data
    - V55K0012 EXIT_SAPLV55K_012 Shipping notification (inbound): Prepare processing
    - V55K0013 EXIT_SAPLV55K_013 Shipping notification (inbound): Evaluate result
    57. WMBBIN
    Block Storage Bins
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI04 EXIT_SAPLLIDI_004 Customer enhancement for IDoc WMBBID01
    58. WMCATO
    Reversal/Reversal request for transfer order
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI03 EXIT_SAPLLIDI_003 Customer enhancement for IDoc WMCAI01
    59. WMINVE
    Inventory count input
    - MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDO09 EXIT_SAPLLMDE_003 Customer enhancement for message WMINVE
    - MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
    60. WMMBXY
    IDoc Report goods movements in IM
    - MWMIDO08 EXIT_SAPLLMDE_002 Customer enhancement for message WMMBXY (goods movement) inbound
    61. WMSUMO
    Move storage unit
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI06 EXIT_SAPLLIDI_006 Customer enhancement for IDoc WMSUID01
    62. WMTOCO
    Transfer order
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI02 EXIT_SAPLLIDI_002 Customer enhancement for IDoc WMTCID01
    63. WMTORD
    Transfer order
    - MWMIDO07 EXIT_SAPLLMDE_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDO10 EXIT_SAPLLMDE_004 Customer enhancement for message WMTORD (Create TO) inbound
    - MWMIDO11 EXIT_SAPLLMDE_005 Customer enhancement for message WMTORD (Create TO) inbound
    64. WMTREQ
    Create/Cancel transfer order
    - MWMIDI01 EXIT_SAPLLIDI_001 Customer enhancement for error handling of inbound IDoc
    - MWMIDI05 EXIT_SAPLLIDI_005 Customer enhancement for IDoc WMTRID01
    65. WPUBON
    POS interface: Upload sales documents (compressed)
    - WPUE0002 EXIT_SAPLWPUE_104 IDoc WPUBON01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_105 Check, whether transaction of IDoc WPUBON01 is compressable
    - WPUE0002 EXIT_SAPLWPUE_106 IDoc WPUBON01: processing user segment
    - WPUE0002 EXIT_SAPLWPUE_109 IDoc WPUBON01: after to inbound processing
    66. WPUFIB
    POS interface: Upload Fin.Acc. interface SRS/POS
    - WPUE0002 EXIT_SAPLWPUE_130 IDoc WPUFIB01: prior to update
    - WPUE0002 EXIT_SAPLWPUE_131 IDoc WPUFIB01: processing user
    67. WPUFIB
    POS interface: Upload Fin.Acc. interface SRS/POS
    - WPUE0002 EXIT_SAPLWPUE_132 IDoc WPUFIB01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_139 IDoc WPUFIB01: after to inbound processing
    68. WPUKSR
    POS upload cashier data
    - WPUE0002 EXIT_SAPLWPUE_120 IDoc WPUKSR01: prior to update
    - WPUE0002 EXIT_SAPLWPUE_122 IDoc WPUKSR01: processing user segment
    - WPUE0002 EXIT_SAPLWPUE_123 IDoc WPUKSR01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_129 IDoc WPUKSR01: after to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_152 IDoc WPUTAB01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_159 IDoc WPUTAB01: after to inbound processing
    69. WPUUMS
    POS interface: Upload sales data (compressed)
    - WPUE0002 EXIT_SAPLWPUE_110 IDoc WPUUMS01: prior to update
    - WPUE0002 EXIT_SAPLWPUE_112 IDoc WPUUMS01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_113 IDoc WPUUMS01: processing user segment
    - WPUE0002 EXIT_SAPLWPUE_119 IDoc WPUUMS01: after to inbound processing
    70. WPUWBW
    POS interface: Upload goods movements
    - WPUE0002 EXIT_SAPLWPUE_140 IDoc WPUWBW01: prior to update
    - WPUE0002 EXIT_SAPLWPUE_141 IDoc WPUWBW01: processing user segment
    - WPUE0002 EXIT_SAPLWPUE_142 IDoc WPUWBW01: prior to inbound processing
    - WPUE0002 EXIT_SAPLWPUE_149 IDoc WPUWBW01: after to inbound processing
    71. WVINVE
    Store physical inventory / sales price revaluation
    - WVFI0001 EXIT_SAPLWVFI_001 Inbound IDoc store phys. inv.: override Customizing
    - WVFI0002 EXIT_SAPLWVFI_002 Inbound IDoc store phys. inv.: process customer segment

  • User exit for XD01 (Customer Creation)

    Hi All Gurus,
    I need to extract some data (kunnr, name1, name2, telephone, mobile etc from KNA1, KNVV, KNBK tables) when user is creating a new customer. I have used the user exit SAPMF02D - EXIT_SAPMF02D_001 for the requirement.
    I am getting all the required data except KUNNR. It is always blank, and according to my guessing it is because yet the KUNNR is not created.
    Is there any other alternative or user exit for this scenario?
    Thank you all in advance,

    This was a very useful post Marcin!
    For those who need detailed steps for BTE regarding customer master data:
    Transaction FIBF
    Environment -> Infosystem P/S
    Find event code using google (debitors are 00001320)
    Click "Sample Function Module" and copy it to your FM (e.g. Z_CUSTOMER_UPDATED)
    Back in FIBF choose menu Settings -> Products -> ...of a customer and create one (check "Active"). Go back to FIBF
    Settings -> P/S Modules -> of a customer and assign your event + product + FM
    Now you can implement your FM
    You can use this FM to track changes to customer master data and e.g. feed the information into interfacing systems.

  • User Exit for Vendor Master creation

    Hi SAP Gurus,
    We need to stop to create vendor using MK01 if there is no general data exist for it. I don't see any standard way for it.
    Does any one knows any user exit for it ?
    Thanks for your help.
    Regards,
    Manoj

    Hi Manoj, that's a very simple question. Before you save data, that record will not even exist in LFA1 table. so, you just need to check that table for the record. In case it doesn't exit, just give an error message.
    inclue some code in the user exit. something like
    if sy-tcode eq 'MK01'.
    select single from lfa1 where lifnr eq ???-lifnr. "check field name in exit
        if not sy-subrc eq 0.    "record doesn't exist
           message E 'Record ..........'
        endif.
    endif.
    if you want to use authorization, just include a mandatory field in a field group, like name1 (vendor name, you can create a vendor without a name) and that will only be open for maintenance for those who have the corresponding authorization value. Therefore, those who have authorization to create a vendor can create it using XK01/MK01/FK01, but those who can only maintain purchasing data cannot create a new vendor record.

  • User Exits for Item Category Determination based on Item Category Usage

    Hi Gurus,
    If I need to create a new item category usage code and perform item category determination using the new item category usage code, is there a user exit or function module which is able to perform this?
    Thanks & Regards

    Hi Lawrence Tam,
             If you are going to create a new item category usage to determine an item category, you need to add a new line in transaction VOV4 for the new combination of sales document type + Item Cat. group + usage + high leve item cat. to determine the item category.
    Thanks in advance,
    Mariano.

  • Internet user role for BP category type "Organisation"

    Dear All,
    We have some BPs which is created under the BP category of "Organization" with role sold-to-party. Now the client wants to extend this BPs to Internet user role. Where as in Standard internet user role will be assigned to only person category.
    Please advise me on the same.
    Regards
    Ashwini

    Hi Ashwini,
    you need to modify the logon routine and then in the user management (isauseradmin application) to do this. Then there are likely changes to the catalog identification, and very likely to most processes in the shop. I really wouldn't advise doing so. As accounts usually have contact persons: Why does your client insist in providing a login for the organization and not for a person?
    To achieve something that looks almost like the desired solution you, e.g., could model a dummy contact person for each account that shall get a logon, that then does the job. The contact person could be named like the company and then you are back to plain standard.
    Rgds
    Thomas

  • User Manual for SRM organisation creation.

    Hi
    Can any one send user manual with screen shot to my business ID for creation of
    SRM organisation.
    Regards
    G.Ganesh Kumar

    Hi
    This thread is closed
    Regards
    G.ganesh Kumar

  • BADI/User Exit for WBS element creation (CRM to R/3)

    In CRM 4.0 once a Campaign or Trade Promotion is created, a WBS is also automatically in R/3 (tcode CJ20N)
    I have a requirement to fill out the 'user fields' at the WBS element level when the campaign/TPM status is set to Release.
    I also need to fill out the 'company code' at the Project Definition level.
    Could you let me know if there's a badi or user exit that i can use in order to achieve these requirements?
    Your help will be much appreciated.
    Thanks
    Elynor

    Hi Tomasz,
    Thanks for your reply. Could you give me a hint on how to use these Badis since the passing parameters cannot be changed?
    A sample code would be helpful
    Many Thanks.

Maybe you are looking for

  • How do you set an array of combo boxes to a specific value?

    I have an array of combo boxes that I would like to set to a specific value. When I tell my program to set them it only sets the combo box that I most recently changed and none of the others.  I've attached a small vi that demonstates the problem.  T

  • Linked Object

    Hai, i can create a linked object & assign through the datasource to salesperson screen but its a problem when the sales person selected through the orrange arrow help Screen but this value should not reflect in my screen when i return to the origina

  • Printer menu

    The PRINT selection has disappeared from the list of prompts on the printer screen.  I have un and re installed the software on my computer to no avail.

  • HP Support Assistant not installing updates

    I downloaded my updates via the Support Assistant but when i see the history it shows that it is not yet completed installing. Many times I have postponed the restart by the Support Assistant. Here is how it shows me. Please Help Me out. Viraj dv7-61

  • Deleteing entries in tRFC

    We have entries in the tRFC that we need to delete (not execute; there is a valid reason for this). When I try to delete the entry, I am informed that only the user whos name the entry is created in can delete it. The problem is, that user is a syste