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

Similar Messages

  • Urgent!... What is the USER EXIT for Inbound ORDERS

    Hi all,
    Which is the user exit used for <b>Inbound ORDERS</b>?
    The exact requirement is for an <b>incoming Idoc which is a PO</b>, we have to map certain fields in the segments E1EDK01, E1EDK14, E1EDKA1, E1EDP01, E1EDP19 AND E1EDP20 for <b>ORDERS</b> message type. After the mapping is done, <b>an Idoc is generated and then a SO is created</b>.
    Exact requirement :
    <b>Message Type : ORDERS
    Basic Type:           ORDERS05
    Direction :              Inbound.
    USER EXIT :          ????</b>
    Please help me..quite urgent.
    Regards,
    Anishur

    Hi
    I had worked on a similar requirement. We had used enhancement points for the same. Search for the function module you are going to use. Then either search for enhancement point in the same. Or search for the call statement in the code. Enhancement point can be searched by clicking the spiral button on the toolbar and then navigate to edit -> enhancement operations -> show enhancement options.
    Anyways you can find the same with the following program.
    Find the available exits with the following program:::
    *& Report  ZFINDUSEREXIT
    report  zfinduserexit.
    tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
    tables : tstct.
    data : jtab like tadir occurs 0 with header line.
    data : field1(30).
    data : v_devclass like tadir-devclass.
    parameters : p_tcode like tstc-tcode obligatory.
    select single * from tstc where tcode eq p_tcode.
    if sy-subrc eq 0.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'PROG'
    and obj_name = tstc-pgmna.
    move : tadir-devclass to v_devclass.
    if sy-subrc ne 0.
    select single * from trdir where name = tstc-pgmna.
    if trdir-subc eq 'F'.
    select single * from tfdir where pname = tstc-pgmna.
    select single * from enlfdir where funcname =
    tfdir-funcname.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'FUGR'
    and obj_name eq enlfdir-area.
    move : tadir-devclass to v_devclass.
    endif.
    endif.
    select * from tadir into table jtab
    where pgmid = 'R3TR'
    and object = 'SMOD'
    and devclass = v_devclass.
    select single * from tstct where sprsl eq sy-langu and
    tcode eq p_tcode.
    format color col_positive intensified off.
    write:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    skip.
    if not jtab[] is initial.
    write:/(95) sy-uline.
    format color col_heading intensified on.
    write:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    write:/(95) sy-uline.
    loop at jtab.
    select single * from modsapt
    where sprsl = sy-langu and
    name = jtab-obj_name.
    format color col_normal intensified off.
    write:/1 sy-vline,
    2 jtab-obj_name hotspot on,
    21 sy-vline ,
    22 modsapt-modtext,
    95 sy-vline.
    endloop.
    write:/(95) sy-uline.
    describe table jtab.
    skip.
    format color col_total intensified on.
    write:/ 'No of Exits:' , sy-tfill.
    else.
    format color col_negative intensified on.
    write:/(95) 'No User Exit exists'.
    endif.
    else.
    format color col_negative intensified on.
    write:/(95) 'Transaction Code Does Not Exist'.
    endif.
    at line-selection.
    get cursor field field1.
    check field1(4) eq 'JTAB'.
    set parameter id 'MON' field sy-lisel+1(10).
    execute it, enter the transaction for which enhancement is needed and then execute.
    Please do reward if useful
    Regards
    Dinesh

  • User exit for sales order creation VA01.

    Hi friends,
    While creating Sales order, before saving the document, I need to check the Customer (Sold to pary?) details in KNEX table. KNEX-KUNNR  KNEX-TDOCO KNEX-DHRCO. if condition fails, I need to display an error message V1525,
    which should contain
    1)customer(sold-to -party?KNEX-KUNNR)
    2)partner function PARVW  (VBPA-PARVW?)
    3)country LNDEX KNEX-LNDEX
    Functional spec says, 1)V45A0002
                                  2)V45A0003
                                  3)V45S0001
                                  4)V50EPROP User exits can be levaraged.
    1)triggers before we enter customer (sold-to-party) in VA01. so may not be used.
    remaining i tried, but I am not able to get the proper PARVW, LNDEX from function module parameters / structures like VBAP/VBPA etc.
    Please help me the way.
    i) the above user exits can be used?if not, help me with user exit name.
    ii)if yes, how to fetch PARVW  , LNDEX, KUNNR...as all the primary keys must be used in the selection query.
    Please help me ASAP.

    Hi,
    Use this enhancement V45A0002.
    Reward points if it helps,
    Satish

  • User exits for sales order

    Dear all SAP experts,
    How to find out the user exits for sales document type? Especially the user exits which are called when we save the sales order.
    With best regards,
    Allabaqsh G. Patil

    Hi,
    Also there is user exit to refresh data
    USEREXIT_REFRESH_DOCUMENT
           It is always necessary to refresh user-specific data before   *
          the next document will be processed.                          *
          This can be done in this userexit.                            *
          This userexit can be used to refresh user-specific data       *
          when the processing of a sales document is finished           *
          - after the document is saved                                 *
          - when you leave the document processing with F3 or F15       *
          It may be necessary to refresh user-specific data before      *
          the next document will be processed.                          *

  • What are the user exits available related to Credit Management?

    What are the user exits available related to Credit Management?
    <b>I have blocked users from releasing SO through Tciode VKM3 , now I want to block
    the same (releasing of SO through VKM4) ,I want VKM4 to be used only for releasing delivery orders. Can anyone help me in configuring the same?.</b>
    Thanx in advance,
    Regrds,
    Binayak

    Hi,
    User Exits For Credit Checks And Risk Management
    Credit Check
    If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:
    LVKMPTZZ
    LVKMPFZ1: USER_CREDIT_CHECK1
    LVKMPFZ2: USER_CREDIT_CHECK2
    LVKMPFZ3: USER_CREDIT_CHECK3
    User exit for availability check
    User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.
    This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.
    Risk Management for Receivables
    RVKMPUS2
    Using this user exit, you can define new forms of payment guarantee.
    Regards,
    Amrish Purohit

  • User exits for Sales Order Data

    Hi,
    May i ask if there's any user exit that will get data from Sales order like ex. the order qty and the net price and pass to SHP_OBDLV_SAVE_REPLICA like ex in the segment  E1BPOBDLVITEMRFO of delivery note.
    or get the commodity code (STAWN) from MatMas and pass also to SHP_OBDLV_SAVE_REPLiCA
    Thanks in advance..
    aileen

    These are the user exits for VA01
    V45E0001 Update the purchase order from the sales order
    V45S0001 Update sales document from configuration
    V45S0004 Effectivity type in sales order
    V45W0001 SD Service Management: Forward Contract Data to Item
    V45A0001 Determine alternative materials for product selection
    V45A0002 Predefine sold-to party in sales document
    V45A0003 Collector for customer function modulpool MV45A
    V45A0004 Copy packing proposal
    V45E0002 Data transfer in procurement elements (PRreq., assembly)
    V45L0001 SD component supplier processing (customer enhancements)
    Use this also USEREXIT_SAVE_DOCUMENT
    Regards,
    Shamma

  • What are the User Exit Available after saving a Billing Documents

    Hi,
    What are the User Exit Available after saving a Billing Documents
    Regrds,
    Binayak

    Hi
    Check the following Exits for VF01 Tcode
    V61A0001                                Customer enhancement: Pricing
    V60P0001                                Data provision for additional fields for display in lists
    V60A0001                                Customer functions in the billing document
    V05N0001                                User Exits for Printing Billing Docs. using POR Procedure
    V05I0001                                User exits for billing index
    SDVFX011                                Userexit for the komkcv- and kompcv-structures
    SDVFX010                                User exit item table for the customer lines
    SDVFX009                                Billing doc. processing KIDONO (payment reference number)
    SDVFX008                                User exit: Processing of transfer structures SD-FI
    SDVFX007                                User exit: Billing plan during transfer to Accounting
    SDVFX006                                User exit tax line in transfer to accounting
    SDVFX005                                User exit reserves in transfer to accounting
    SDVFX004                                User exit G/L line in transfer to accounting
    SDVFX003                                User exit cash clearing in transfer to accounting
    SDVFX002                                User exit for A/R line in transfer to accounting
    SDVFX001                                User exit header line in delivery to accounting
    Business Add-in
    SD_CIN_LV60AU02                         BADI for billing
    VOR_WA_FAKTURA                          Billing before Goods Issue
    Reward points if useful
    Regards
    Anji

  • What is the user exit for automatic account determination in PO

    Hi Experts
       I ned to know  what is the user exit for automatic account determination in PO
    my client needs the document type to defines Account Assignment Category.
    choosen a document type Account Assignment Category is defined automatically.  you can't choose
    a wrong  Account Assignment Category from the drop down list.
    thanks form you help.

    If this is the case than why don't you use the Transaction variant
    SHD0: http://www.mortenhjorthnielsen.dk/Security/transactionvariants.htm
    If you have knowledge of Transaction variant then you can use SHD0 tcode and generate the transaction using default type and give that transaction to user instead of ME21N so they will not have the issue.
    The exact solution for your problem is as follows
    Go to Tcode SHD0 and enter the transaction variant
    In T code field enter ME21N and then enter the ZXXXX or the name you want to keep in transaction variant field and hit create button
    This will take you to ME21N transaction and here you just enter the data but make sure you enter the A/c which you want to default.
    Once you finish system will save this one as a variant
    Every time you hit or enter the pop up screen comes here you just hit enter and whichever data you want to default that you have to select in the Popup by checking the Box
    W content and output only for your case the field XXXXXXXX should be selected for W content and output only
    Make sure you have value 1 in contents field
    If not then restart the variant again and on the ME21Nscreen reselect the invoice field
    Later exit and save (save in the object which you can transport)
    Then from SHD0 transaction select GOTO create variant transaction and here you careate the tcode and use that tcode for ME21N (e.g ZTRAN - For specifix sto)

  • User exit for  Sales order

    hi,
       i need to eliminate leading zeros for PO number which comes in SO created trough ALE.i found the enhancement for the FM idoc_input_orders.in that enahancement we have 12 FM's.my Leading zeros are comming for field belnr which comes in e1edk01 segment of idoc orders05.now i had coded my part of coding in FM exit_saplved.._oo1 and i had activated that.but it is not working for me.than i tought of going to other FM exit_sapl..._009.in which i'm not able go into the include either.plz help me out.thank you.

    Hi, Krishna!
    With IDOC_INPUT_ORDERS during IDoc interpretation PO number is assigned to XVBAK-BSTKD field which is later used for sales order creation with reference to PO.
    So all you need is to use some customer exit with changing parameters containing XVBAK after IDoc interpretation is completed. For example you can use EXIT_SAPLVEDA_009 which is called at the end of IDoc check after interpretation.
    Regards,
    Maxim.

  • What are the user-exits which will trigger on saving Sales Order

    Hello Experts!!!
    I am working on Sales Order VA01. The requirement is I need to pre populate Sold-to-Party field. I find out user-exit (V45A0002  Predefine sold-to party in sales document  ). So it is working fine.
    Now second requirement is I need to capture all the date once user saves Sales Order. Also the time or Sales Order creation I have to make u2018GRAYu2019 some of the fields so user cannot change the value. Can anybody tell me which user-exits should I use to retrieve the entire information user entered and lock fields in Sales Order screen?
    Thanks a lot on advance.

    Hi
    U can't find it there,because it's a include, not enanchement.
    So u need to use the trx SE38, not CMOD.
    For sales ored there aren't the enanchements, but only some FORMs defined in particular includes.
    U need to get the access key by OSS in order to change them.
    These are the rest of the includes where u can find other exits:
           INCLUDE MV45ATZZ.            " Data definitions in MV45ATOP
             INCLUDE MV45AOZZ.             " User-modules PBO
             INCLUDE MV45AIZZ.             " User-modules PAI
             INCLUDE MV45AFZA.             " User-forms < 3.0
             INCLUDE MV45AFZB.             " User-forms
             INCLUDE MV45AFZC.             " User-forms < 3.0D
             INCLUDE MV45AFZD.             " User-forms   3.0E
             INCLUDE MV45AFZF.             " User-forms   3.0F
           include mv45afzg.             " User-forms   3.1G
             INCLUDE MV45AFZH.             " User-forms   4.6B
             INCLUDE MV45AFZZ.             " User-forms
             INCLUDE MV45AFZ4.             " User-forms   4.0
    Anyway u can find some information about these exit in customizing (trx SPRO):
    Sales and Distributions->System modifications->User exits
    Max

  • User exit for sale order material serial number change

    I am looking for User exit for changing the serial number for the saleorder material va01.

    Hey,
      Check the include program : MV45AFZZ. it will trigger at the of saving the sale order.
    IF SY-TCODE EQ 'VA02' OR SY-TCODE EQ 'VA01'.
    Endif.
    Note : Write your coding inside the IF clause to avoid affecting the other transaction codes.
    Regards,
    Saravanan M

  • User exit for sale order

    Hi Friends,
    I am now working on Sale order User exit.
    I need to find out wheather the batch management indicator (XCHEF) is checked ('X') if BSTEL(shipping point) changes.
    Can anyone help in which include the the batch management indicator comes and how to find the same.
    Thanks & regards,

    Hi Sumitha,
      Please provide more details on the scenario you are working.Like how the Sales order creation / change is triggered?.
    Thnx!
    Harry

  • What are the tables corresponding to sales order - parners

    Hi Folks,
    Can u pls let me know what are the corresponding tables n fileds for the va02->parners i.e sold to party, ship to party etc, buyer , bill to party and contact details , adress of these parners wil store.
    Thanks in advance.
    Regards
    Rajesh

    hii i am sending u the full code thta i had designed for my sales order confirmation using sap script
    TABLES: VBAK,
            ADRC,
            VBPA,
            VBAP,
            SPELL.
    DATA: BEGIN OF  TVBAK OCCURS 0,
          VBELN LIKE VBAK-VBELN,
          AUDAT LIKE VBAK-AUDAT,
          KUNNR LIKE VBAK-KUNNR,
          VKORG like VBAK-VKORG,
          END OF TVBAK.
    DATA: BEGIN OF TADRC OCCURS 0,
          ADDRNUMBER LIKE ADRC-ADDRNUMBER,
          NAME1 LIKE ADRC-NAME1,
          NAME2 LIKE ADRC-NAME2,
          CITY1 LIKE ADRC-CITY1,
          POST_CODE1 LIKE ADRC-POST_CODE1,
          COUNTRY LIKE ADRC-COUNTRY,
          KUNNR LIKE VBPA-KUNNR,
          VBELN LIKE VBPA-VBELN,
          END OF TADRC.
    DATA:BEGIN OF TVBPA OCCURS 0,
         ADRNR LIKE VBPA-ADRNR,
         KUNNR LIKE VBPA-KUNNR,
         VBELN LIKE VBPA-VBELN,
         END OF TVBPA.
    DATA: BEGIN OF TVBAP OCCURS 0,
          POSNR LIKE VBAP-POSNR,
          VBELN LIKE VBAP-VBELN,
          MATNR LIKE VBAP-MATNR,
          ARKTX LIKE VBAP-ARKTX,
          KWMENG LIKE VBAP-KWMENG,
          VRKME LIKE VBAP-VRKME,
          NETWR LIKE VBAP-NETWR,
          WAERK LIKE VBAP-WAERK,
          END OF TVBAP.
    DATA :W_VBELN LIKE VBAK-VBELN,
          s_amount like vbap-netwr ,
          amount_word LIKE SPELL.
    selection-screen: begin of block b1.
    select-options: s_vbeln for vbpa-vbeln no intervals no-extension.
    selection-screen: end of block b1.
    *AT SELECTION-SCREEN.
      SELECT VBELN INTO W_VBELN FROM VBAK
          WHERE VBELN IN S_VBELN.
    *ENDSELECT.
    START-OF-SELECTION.
    SELECT VBELN AUDAT KUNNR VKORG FROM VBAK INTO CORRESPONDING
    FIELDS OF
    TABLE TVBAK WHERE VBELN IN
    S_VBELN.
       IF SY-SUBRC <> 0.
         MESSAGE I398(00) WITH 'NO DATA'.
       ENDIF.
    SELECT NAME1 NAME2 CITY1 POST_CODE1 COUNTRY FROM ADRC INTO
    CORRESPONDING
    FIELDS OF
    TABLE TADRC.
       IF SY-SUBRC <> 0.
         MESSAGE I398(00) WITH 'NO DATA1'.
       ENDIF.
    SELECT ADRNR KUNNR VBELN  FROM VBPA INTO CORRESPONDING
    FIELDS OF
    TABLE TVBPA WHERE PARVW = 'WE'.
       IF SY-SUBRC <> 0.
         MESSAGE I398(00) WITH 'NO DATA2'.
       ENDIF.
    SELECT VBELN POSNR MATNR ARKTX KWMENG VRKME NETWR WAERK FROM VBAP INTO
    CORRESPONDING
    FIELDS OF TABLE TVBAP WHERE VBELN IN
    S_VBELN.
      IF SY-SUBRC <> 0.
       MESSAGE I398(00) WITH 'NO DATA3'.
       ENDIF.
    LOOP AT TADRC.
       READ TABLE TVBPA WITH KEY ADRNR = TADRC-ADDRNUMBER.
          IF SY-SUBRC = 0.
           MOVE TVBPA-KUNNR TO TADRC-KUNNR.
           MOVE TVBPA-VBELN TO TADRC-VBELN.
           MODIFY TADRC.
          ENDIF.
    ENDLOOP.
    ****reward if helpfull ******

  • How to get header text in user exit for sales order

    Hello all,
    My requirement is that I get and modify the header text in user exit when creating a sales order. In the user exit I'll do some validation and put the error code into header text. But I can't use function 'READ_TEXT' to get header text since the text has not been updated into database.
    Can anybody help me? point will be rewarded. Thanks in advance.
    regards,
    --Alex

    Use the following internal tables. These internal tables are declared in include <b>THEADDAT</b>. THEADDAT is an include of  <b>MV45ATOP</b>.
    THEAD,                
    TLINE.                       
    TVCOM,                      
    TTXID,        
    TTXIT,
    TTXOB,              
    TTXOT          
    I hope it helps.

  • User exit for sales order-Urgent

    How  Developed a User Exit, which will be triggered when a Sales Order is changed manually. This user exit will check the requested delivery date and update VBKD-BSARK field.
    Pls help me how to do it....
    Pts will be rewarded.....

    Hi,
    The following exits trigger during VA01 creation:
    EXIT_SAPMV45A_002 and
    EXIT_SAPMV45A_003
    Check this include MV45AFZZ also.
    Regards,
    Satish

Maybe you are looking for


HashFlare