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

Similar Messages

Can i know the user exits which should trigger while saving billing docu

hi,
please can u help me to find out user exits which should trigger while saving billing documents.

A couple years ago I downloaded this program, I think from SAPFANS. I don't take any credit for it...Not sure who originally wrote it. Just type in the t-code and hit execute.
*& Report name          : Identify and Drill-Down to SAP User Exits.   *
*& Program name         : ZZ_FIND_USER_EXITS                           *
REPORT ZZ_FIND_USER_EXITS
NO STANDARD PAGE HEADING
LINE-SIZE 132
LINE-COUNT 65
MESSAGE-ID MM.
D A T A   D E F I N I T I O N                                        *
TABLES : TSTC,      " SAP Transaction Codes
         TADIR,     " Directory of Repository Objects
         MODSAPT,   " SAP Enhancements - Short Texts
         MODACT,    " Modifications
         TRDIR,     " System Table TRDIR
         TFDIR,     " Function Module
         ENLFDIR,   " Additional Attributes for Function Modules
         TSTCT.     " Transaction Code Texts
S E L E C T I O N   S C R E E N                                      *
PARAMETERS : P_TCODE LIKE TSTC-TCODE OBLIGATORY.
I N T E R N A L   S T R U C T U R E S   &   T A B L E S              *
DATA : GT_TADIR LIKE TADIR OCCURS 0 WITH HEADER LINE.
V A R I A B L E S                                                    *
DATA :
       GV_FIELD1(30) TYPE C,
       GV_DEVCLASS    LIKE TADIR-DEVCLASS.
C O N S T A N T S                                                    *
CONSTANTS:
           GC_F     LIKE TRDIR-SUBC   VALUE 'F',
           GC_R3TR LIKE TADIR-PGMID VALUE 'R3TR',
           GC_FUGR LIKE TADIR-OBJECT VALUE 'FUGR',
           GC_SMOD LIKE TADIR-OBJECT VALUE 'SMOD',
           GC_PROG LIKE TADIR-OBJECT VALUE 'PROG'.
R A N G E S                                                          *
RANGES:
GR_VKORK      FOR WKBP-VKORG.
E V E N T   P R O C E S S I N G                                      *
INITIALIZATION.
AT SELECTION-SCREEN.
SELECT SINGLE PGMNA
    INTO TSTC-PGMNA
    FROM TSTC
    WHERE TCODE = P_TCODE.
IF SY-SUBRC <> 0.
    MESSAGE E899(MM)
      WITH TEXT-E01    " Input Transaction Code is Invalid.
           TEXT-E02.   " Please Correct !!
ENDIF.
SELECT SINGLE TTEXT
    INTO TSTCT-TTEXT
    FROM TSTCT
    WHERE SPRSL = SY-LANGU
      AND TCODE = P_TCODE.
START-OF-SELECTION.
CLEAR GV_DEVCLASS.
SELECT SINGLE DEVCLASS
    INTO GV_DEVCLASS
    FROM TADIR
    WHERE PGMID = GC_R3TR
      AND OBJECT = GC_PROG
      AND OBJ_NAME = TSTC-PGMNA.
IF SY-SUBRC <> 0.
    SELECT SINGLE SUBC
      INTO TRDIR-SUBC
      FROM TRDIR
      WHERE NAME = TSTC-PGMNA.
    IF TRDIR-SUBC = GC_F.         " Function Group
      SELECT SINGLE FUNCNAME
        INTO TFDIR-FUNCNAME
        FROM TFDIR
        WHERE PNAME = TSTC-PGMNA.
      SELECT SINGLE AREA
        INTO ENLFDIR-AREA
        FROM ENLFDIR
        WHERE FUNCNAME = TFDIR-FUNCNAME.
      CLEAR GV_DEVCLASS.
      SELECT SINGLE DEVCLASS
        INTO GV_DEVCLASS
        FROM TADIR
        WHERE PGMID    = GC_R3TR
          AND OBJECT   = GC_FUGR
          AND OBJ_NAME = ENLFDIR-AREA.
    ENDIF.
ENDIF.
SELECT *
    FROM TADIR
    INTO TABLE GT_TADIR
    WHERE PGMID = GC_R3TR
      AND OBJECT = GC_SMOD
      AND DEVCLASS = GV_DEVCLASS.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
          20(20) P_TCODE,
          45(36) TSTCT-TTEXT.
SKIP.
IF NOT GT_TADIR[] IS INITIAL.
    WRITE:/(95) SY-ULINE.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    WRITE:/1 SY-VLINE,
           2 'Exit Name',
          21 SY-VLINE ,
          24 'Description',
          95 SY-VLINE.
    WRITE:/(95) SY-ULINE.
    SORT GT_TADIR BY OBJ_NAME.
    LOOP AT GT_TADIR.
      SELECT SINGLE MODTEXT
        INTO MODSAPT-MODTEXT
        FROM MODSAPT
        WHERE SPRSL = SY-LANGU
          AND NAME = GT_TADIR-OBJ_NAME.
      FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
      WRITE:/01 SY-VLINE,
             02 GT_TADIR-OBJ_NAME HOTSPOT ON,
             21 SY-VLINE,
             22 MODSAPT-MODTEXT,
             95 SY-VLINE.
    ENDLOOP.
    WRITE:/(95) SY-ULINE.
    DESCRIBE TABLE GT_TADIR.
    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.
AT LINE-SELECTION.
GET CURSOR FIELD GV_FIELD1.
IF GV_FIELD1(8) = 'GT_TADIR'.
    SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).
    CALL TRANSACTION 'SMOD' AND SKIP FIRST   SCREEN.
ELSE.
    MESSAGE I899(MM)
      WITH TEXT-I01    " Click on the Exit Name to Drill-Down
           TEXT-I02.   " to SAP Enhancement Information.
ENDIF.
END-OF-SELECTION.
TOP-OF-PAGE.
S U B R O U T I N E S                                                *
E N D   O F   R E P O R T ****************************************

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

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

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

Find out user exits which should trigger while saving billing doc.(VA01)

Hi All,
please can u help me to find out user exits which should trigger while saving billing documents for VA01 transaction...I have already z report to find the user-exit for any transaction.I have tried in that also.
Reply
Ulhas

Hi
Try these
USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified
in the billing type table and can be changed in this user exit. This
user exit is only called when the billing documents is created.
USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program
RV60AFZZ)
In this user exit additional fields for account determination that
are not provided in the standard system are copied into
communication structure KOMKCV (header fields).
USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that
are not provided in the standard system are copied into
communication structure KOMPCV (item fields).
USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program
RV60AFZC)
Depending on the number range, table TVFKD is used to set the
billing date (country-specific requirments in Italy).
USEREXIT_NUMBER_RANGE is automatically deactivated when this user
exit is being applied.
USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created.
It is used to provide the header and the item of the new billing
document with deviating or additional data.
USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
Printing the item line of a billing document can be supplemented or
changed.
USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Printing the header line of a billing document can be supplemented
or changed.
User exits in program RV60AFZD
Short descriptions of the user exits are contained in the program:
-   USEREXIT_RELI_XVBPAK_AVBPAK
-   USEREXIT_NEWROLE_XVBPAK_AVBPAK
-   USEREXIT_NEWROLE_XVBPAP_AVBPAK
e following user exits are available in report SAPLV60B for transfer
accounting (function group V60B):
EXIT_SAPLV60B_001: Change the header data in the structure acchd
You can use this exit to influence the header information of the
accounting document. For example, you can change the business
transaction, "created on" date and time, the name of the person who
created it or the transaction with which the document was created.
EXIT_SAPLV60B_002: Change the customer line ACCIT
You can use this exit to change the customer line in the accounting
document. This exit is processed once the ACCIT structure is filled
in with data from document header VBRK.
EXIT_SAPLV60B_003: Change the customer line in costing
The customer line is filled in differently for costing. You can use
exit 003 to influence the ACCIT structure.
EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add
information to a GL account item (such as quantity specifications)
with this exit.
EXIT_SAPLV60B_005: User exit for accruals
Once all relevant data for accruals was entered in the GL account
item, you can add to this data with this exit.
EXIT_SAPLV60B_006: Change the control line ACCIT
You can use exit 006 to add information to the control line.
EXIT_SAPLV60B_007: Change the installment plan
You can use exit 007 to add information to the installment plan
parameters in the GL account item.
EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and
ACCHD
After the accounting document is filled in with data, you can use
exit 008 to change the document once again.
EXIT_SAPLV60B_010: Item table for customer lines
You can use exit 10 to influence the contents of customer lines
before they are created.
EXIT_SAPLV60B_0011: Change the parameter for cash account
determination or reconciliation account determination
You can use this exit to change inbound parameters in order to
influence account determination.
>
Thanks
Shiva

Find the user exit while creation and change of sales order

Hi Team
Below mentioned requirement , in which user exit i have to put below logic while creaion and change of sales order?
u2022     The logic for the user exit to explode should consider the following assumptions and validations
o     Customer master to have the entry at KNVV-KVGR1
o     Material master to have the entry at MVKE
o     UoM in the Sales order item (VBAP- VRKME) should be = Pallets PAL or tonnes (TES)
o     Should have more than one line item or number of line items with UoM PAL or tonnes TES should be > 1
for example :-->
Product A with Scales mentioned below
Product A     Quantity / Scale     UoM     Price(£)
     0-10     PAL/TES     20
     11- 20     PAL/TES     10
     21- 30     PAL/TES     5
     31-40     PAL/TES     2.5
     >41     PAL/TES
Product B with Scales mentioned below
Product B     Quantity / Scale     UoM     Price(£)
     0-15     PAL/TES     25
     16-20     PAL/TES     20
     21- 30     PAL/TES     15
     31-40     PAL/TES     10
     > 41     PAL/TES     5
u2022     Product A (qty 10PAL) + Product B (qty 15 pal) ordered in a single order with 2 line items.
u2022     The expected results should be
o     Product A qty 10 + B qty 15 added = 25Pal
o     The system user exit should add the total number of pallets on the order line items and point towards the respective scales, so in this example prices against each line item should be the respective price against 25 Pal = 5£ for product A per pal and £15 for product B.
Thanks in Advance.
Puneet.

Hi Team
Below mentioned requirement , in which user exit i have to put below logic while creaion and change of sales order?
u2022 The logic for the user exit to explode should consider the following assumptions and validations
o Customer master to have the entry at KNVV-KVGR1
o Material master to have the entry at MVKE
o UoM in the Sales order item (VBAP- VRKME) should be = Pallets PAL or tonnes (TES)
o Should have more than one line item or number of line items with UoM PAL or tonnes TES should be > 1
for example :-->
Product A with Scales mentioned below
Product A Quantity / Scale UoM Price(£)
0-10 PAL/TES 20
11- 20 PAL/TES 10
21- 30 PAL/TES 5
31-40 PAL/TES 2.5
>41 PAL/TES
Product B with Scales mentioned below
Product B Quantity / Scale UoM Price(£)
0-15 PAL/TES 25
16-20 PAL/TES 20
21- 30 PAL/TES 15
31-40 PAL/TES 10
41 PAL/TES 5
u2022 Product A (qty 10PAL) + Product B (qty 15 pal) ordered in a single order with 2 line items.
u2022 The expected results should be
o Product A qty 10 + B qty 15 added = 25Pal
o The system user exit should add the total number of pallets on the order line items and point towards the respective scales, so in this example prices against each line item should be the respective price against 25 Pal = 5£ for product A per pal and £15 for product B.
Thanks in Advance.
Puneet.

How can we identify what are all user exits are there for sales orders,deli

Dear All,
How can we identify what are all user exits are there for sales orders,deliverys and invoices
thanks
nitchel v

Hi Nitchel
There are many ways to find out the user exits..
For example for VA01.
Goto Transaction ie VA01:
goto System-- Status
doubleclick on the program name ie SAPMV45A
SE38 -> Enter the program name and in the program( SAPMV45A) goto -- attributes
get the package name from here ie VA
note the package(VA) and get back to main screen
goto SMOD tcode and click on find button in the package spec giv the package name ie VA and execute it
you will find list of exits available
check out the exit that suits ur requirement
goto cmod and create a new project and implement in that user exit.
You will get the following exits in SMOD..
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly
V45L0001 SD component supplier processing (customer enhancements
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing
For Delivery you will get .. here the package name will be VL.
V02V0001 Sales area determination for stock transport order
V02V0002 User exit for storage location determination
V02V0003 User exit for gate + matl staging area determination (h
V02V0004 User Exit for Staging Area Determination (Item)
V50PSTAT Delivery: Item Status Calculation
V50Q0001 Delivery Monitor: User Exits for Filling Display Fields
V50R0001 Collective processing for delivery creation
V50R0002 Collective processing for delivery creation
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V50S0001 User Exits for Delivery Processing
V53C0001 Rough workload calculation in time per item
V53C0002 W&S: RWE enhancement - shipping material type/time slot
V53W0001 User exits for creating picking waves
VMDE0001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)
For Billing VF01..Package is VF..
SDVFX007 User exit: Billing plan during transfer to Accounting
SDVFX008 User exit: Processing of transfer structures SD-FI
SDVFX009 Billing doc. processing KIDONO (payment reference numbe
SDVFX010 User exit item table for the customer lines
SDVFX011 Userexit for the komkcv- and kompcv-structures
V05I0001 User exits for billing index
V05N0001 User Exits for Printing Billing Docs. using POR Procedu
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lis
V61A0001 Customer enhancement: Pricing
Or another way is ..
- Get the program name for that T-Code
- Go to that program
- In that program, search for word 'EXIT' or 'CUSTOMER-FUNCTION' by using where-used list which will give u the list of user exits for that program
And also you can check in the tables in SE16 for user exits..
MODSAP - Stores SAP Enhancements
MODSAPT - Stores SAP Enhancements - Short Texts
MODACT - Stores Modifications
And there are other ways as well , pls check the forum for this ,
Regards,
Vvieks
Note : If you have any specific requirement then pls let us know , we will guide you

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)

What are the user defind functions

hi all,
what are the user defind functions.
Regards,
priya

Hi Priya,
Generally we will complete our mapping things with the help of Standard Functions itself those are available in Graphical Mapping.
UDF are used when the mappings are unable to complete with these standard functions then we need to write small piece of Java code and can achieve that functionality.
Steps to UDF
Activities
1. To create a new user-defined function, in the data-flow editor, choose Create New Function (This
graphic is explained in the accompanying text), which is located on the lower left-hand side of the
screen. In the menu, choose Simple Function or Advanced Function.
2. In the window that appears, specify the attributes of the new function:
Name
Technical name of the function. The name is displayed in the function chooser and on the data-flow
object.
Description
Description of how the function is used.
Cache
Function type (see above)
Argument Count
In this table, you specify the number of input values the function can process, and name them. All
functions are of type String.
3. In the window that appears, you can create Java source code:
a. You can import Java packages to your methods from the Imports input field, by specifying them
separated by a comma or semi-colon:
You do not need to import the packages java.lang., java.util., java.io., and java.lang.reflect. since
all message mappings require these packages and therefore import them. You should be able to
access standard JDK and J2EE packages of the SAP Web Application Server by simply specifying the
package under Import. In other words, you do not have to import it as an archive into the Integration
Repository. You can also access classes of the SAP XML Toolkit, the SAP Java Connector, and the
SAP Logging Service (see also: Runtime Environment (Java-Mappings)).
In addition to the standard packages, you can also specify Java packages that you have imported as
archives and that are located in the same, or in an underlying software component version as the
message mapping.
b. Create your Java source text in the editor window or copy source text from another editor.
4. Confirm with Save and Close.
5. User-defined functions are limited to the message mapping in which you created the function. To
save the new function, save the message mapping.
6. To test the function, use the test environment.
The new function is now visible in the User-Defined function category. When you select this category,
a corresponding button is displayed in the function chooser pushbutton bar. To edit, delete, or add the
function to the data-flow editor, choose the arrow next to the button and select from the list box
displayed.
REgards
Seshagiri

What are the consequences of Compiling a trigger in peaktime in a Database.

What are the consequences of Compiling a trigger in peaktime in a Database.

Compiling a (table) trigger, would temporarily require a lock on the involved table.
So, no open transactions that involve the table can exist.
Since a trigger is a top-level object (dba_dependencies - wise), compiling it will not invalidate other objects.
Having said this: I would not advise doing this during peaktime...

What is the user exit triggering at this time of saving delivery document

Hi All,
What is the user exit triggering at this time of saving delivery document
regards
Deekshitha.

For the Delivery process following project are used, you can list out all exit
V02V0001
V02V0002
V02V0003
V02V0004
V50PSTAT
V50Q0001
V50R0001
V50R0002
V50R0004
V50S0001
V53C0001
V53C0002
V53W0001
VMDE0001
VMDE0002
VMDE0003
VMDE0004

I have a Win7Pro SP1 PC locked down with a Group Policy as it is a public facing PC. PDF fillable forms cannot be completed when logged on as the restricted user. The forms work as a normal user. What are the user requirements/permissions needed to fill f

I have a Win7Pro SP1 PC locked down with a Group Policy as it is a public facing PC. PDF fillable forms cannot be completed when logged on as the restricted user. The forms work as a normal user. What are the user requirements/permissions needed to fill forms?

Well, try this (I was able to fix my with these steps):
Go Utilities > Disk Utility
Select your Startup Disk, e.g. Macintosh HD
Then, under the First Aid Tab, click Verify Disk Permissions.
If there are errors, then click repair Disk Permissions.
After it is done, restart the computer and see if your problem is resolved.
I hope this help.
Zeke
www.ZekeYuen.com/blog/

Any report to see what are the users assigned to an org-unit ?

Hi All,
Is there any standard report available to see what are the users assigned to a particular org-unit?
I'm looking for complete list of users assigned to a particular org-unit both directly and indirectly/
Thank you so much in advance !!
Cheers,
Gyan.

Hi,
None of them actually helped.
Trx PC00 is not available in 4.0 sytem. And from the table mentioned i don't see the org-unit value. Could you please elaborate on this.
Thanks,
Gyan.

WHAT ARE THE FORMS (SCRIPTS) WHICH ARE NOT PROVIDED BY STANDARD SAP?

WHAT ARE THE FORMS (SCRIPTS) WHICH ARE NOT PROVIDED BY STANDARD SAP?

Hi Pravin
For a beginner in CRM - Sales would be a right choice to understand how CRM behaves when integrated with backend R/3.
Still as far as CRM goes, most of the components are not exposed to their fullest potential and that is why its not outshining the competitors in market.

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

Similar Messages

Maybe you are looking for