User exits for route

Hi,
For route scheduling, please provide the list of user exits available.
Thanks

Hi Ranjit,
If you need to find user exits in SD. Go to transaction SE81. Click on SD, then click u201Ceditu201D on the menu bar and choose select subtree. Click on u201Cinformation system,u201D Open Environment node, customer exits, and enhancements. Press F8 to get all the user exits for that module. In brief: SE81->SD->Select subtree->Information System->Envir->Exit Techniques->Customers exits->enhancements->Execute.
Pls look at the link ,,,,,,
http://abaplovers.blogspot.com/2008/02/user-exits-in-sap-sd.html
Regards,
Viveks

Similar Messages

User exits for route determination in Sales order & Deliver creation

Hi Gurus,
I need to do some change in the route determination for both sales order & Delivery creation.
Can anyone suggest me which user exit I have to use.
Appropriate answers will be awarded.

Hi,
You can use the following exit for route determination - EXIT_SAPL0VRF_001.
The FM documentation is below. Check the functionality:
"The customer exit can be used for customer-specific route determination or to modify the inbound data for the company's own route determination.
The following data is transferred to support customer-specific route determination:
I_VBAK current order header (for route determination in sales order)
I_VBKD order business data (for route determination in sales order)
I_VBAP current order item (for route determination in sales order)
I_VBPA current sales partner
I_LIKP current delivery header (for route determination in delivery)
The following data can be modified and transferred back to the standard route determination or used for a specific route determination:
C_ALAND Country of departure
C_AZONE Departure zone
C_LLAND Destination country
C_LZONE Receiving zone
C_VSBED Shipping condition
C_TRAGR Transportation group
C_GRULG Weight group
C_FLAG_GEN_VT Flag: Route determination with generic shipping
requirements/transportation group.
C_FLAG_INCR_GRULG Flag: Increase weight group if no route
If you want to use a standard route determination with different parameters, trigger the exception 'CONTINUE_WITH_STANDARD'.
In the log table C_PROT, the log data from the customer-specific route determination can be transferred back. In this case, the log entries always refer to customer-specific messages. To add a message to the log table, the function module SD_ROUTE_DET_LOG can be used (see below).
If a route is determined in the customer-specific route-determination, it can be transferred back in the E_ROUTE field. If no route was found, the exception 'NO_ROUTE_FOUND' is to be triggered."
Thanks.

User exit for route determination in Stock trasnport order

Hi All,
Can somebody help me with a user exit that I can use for route determination in the Stock transport order.
Kind Regards
Chakradhar

Exit to be used is   EXIT_SAPLEBND_002. Enhancement M06E0004.
DATA it_ekpo TYPE LINE OF mmpur_bekpo .
To have controls in system for Standard Cost Estimation under two conditions if SCE is not run then,
1)      System will not allow creating Process Order (COR1).
2)      System will not allow Post Goods Issue (VL02N).
Till date we do not have any control of SCE while creating Stock Transport Order.
Now we have another control for SCE, that is
3)      Henceforth system will not allow creating STO (ME21N).
IF sy-tcode = 'ME21N' OR sy-tcode = 'ME22N'.
IF i_cekko-bsart = 'UB'.
    LOOP AT it_bekpo INTO it_ekpo.
      SELECT SINGLE mtart FROM mara INTO mara-mtart WHERE matnr = it_ekpo-matnr .
      IF mara-mtart = 'IFIG' OR mara-mtart = 'ISFG'.
        SELECT SINGLE * FROM mbew WHERE matnr EQ it_ekpo-matnr
                                            AND bwkey EQ it_ekpo-werks.
        IF mbew-vprsv = 'S'.
          SELECT SINGLE * FROM mbew WHERE matnr EQ it_ekpo-matnr
                                          AND bwkey EQ it_ekpo-werks.
          IF mbew-stprs > '0.00'.
            CONTINUE.
          ELSE.
            MESSAGE e004(zpp) WITH it_ekpo-matnr it_ekpo-werks.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDLOOP.
ENDIF.
Regards,
Mallick

User exit for route determination in VA01

Dear friends,
I need a userexit for route determination whenever required delivery date is changed at the time of sales order creation VA01.
Please reply ASAP.
Thanks,
--Sonal

Hi,
MV45AFZZ should solve the issue.
Check the subroutines userexit_move_field_to_vbap and userexit_save_document_prepare.
Place a break point in all the subroutines and run VA01 and change the date. You can find the exact place where you can code.
Thanks,
Vinod.

User-Exit for Shipment VT01N

Hello Everybody,
   Want some help from you as to what is the "Exit" which will help me doing some manipulation after we press Enter after the First Screen . I am not talking about Saving Data or Stuff . Specifically i want to fill the "Forwarding Agent" and "Route" field right after the User selects the "Shipment Type" on the first Screen , for the Transaction VT01N .
    If User-Exits are not there , is there any BADI ??? Please help.
Please keep in mind , i want the Exit which will be hit right after the First Screen in VT01N.
Thanks,
Suddha

Hi Take a look at the following list ( for VT01N) :
MV56AINI            Initialization of transaction control for transportation
V56AFCCH            Shipment processing: Check function code allowed
V56AGTAR            User Exit for Filtering Shipping Unit Calculation
V56ARCHV            Customer-spec. checks for archiving shipments
V56ATKTX            Change the number of lines for text input in shipment
V56BMOD             Transportation processing: Field modification
V56DISTZ            Shipment Processing: Determine Distance
V56FCOPY            Shipment processing: Copy delivery data
V56FSTAT            Shipment processing: Activities when setting a status
V56L0001            Status of Shipments for a Delivery
V56LDELI            Read Delivery Data for Shipment Processing
V56LOCID            Shipment Processing: Determine Location Identification
V56MVT04            Extensions for Collective Processing of Shipments
V56SLDET            Shipment processing: Leg determination
V56TDLIF            Filter Delivery Items for Shipment
V56UCHCH            Shipment processing: Check whether changes were made
V56UCHCO            Check shipments are complete
V56UDLUP            Obsolete as of 4.6C: Delivery Update on Delivery Routines
V56UNUMB            Shipment number allocation
V56USTAT            User-individual definition of transportation planning status
V56USVDO            Update new objects for transport
V56USVDP            Preparation for updating new objects for transport?
Best Regards,
Erwan

User exit for changing Sales order lines.

Hello experts ,
I want to delete the field "ROUTE" from all of the orders lines in sales orders, I have been using "USEREXIT_SAVE_DOCUMENT_PREPARE" but it does not seems to do the job.
What is the name of user exit that i have to use for this task and which structure should be used, is it xvbap ? is it vbap ?
Thanks for the help.
Avi.

Hi,
find the user exit u required.
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
Best regards,
venkatawamy.y

User Exit for Estimation

Dear All,
I am searching for an user exit for estimation of meter readings. Can anyone tel me when this user exit EDMFOLUP is triggered, which tcode or function triggers this user exit.
With Regards
Balaji.J

Hi,
Following are the user exits called in transaction EL30 (Estimate meter reading results):
Exit Name           Description
EDMASSES            IS-U: User-Defined Validation for Overestimation
EDMEL231            IS-U: Meter Reading Result - Incorporation of Subscreen
EDMFOLUP            IS-U: Determine follow-up actions during MR result entry
EDMLELAE            IS-U: User Exit Too Static. Evaluation of Evaluated Data.
EDMLELDE            IS-U: Dependent validations based on user exit
EDMLELSV            IS_U: User Exit After Saving Meter Reading Results
EDMMR002            IS-U: Change to Gas Date During Meter Reading Result Entry
EDMMRRES            IS-U: Change readings during upload (before validation)
EDMMRSTR            IS-U, Display Additional Fields for Street Route Maintenance
EDMSUPBI            IS-U: Automatic Suppression of Billing/Deac. Meter Readings
I hope it is helps you.
Regards,
Pranaya

GL Account User Exit for all FI transactions

Hi Experts,
We have to create a Ztable and it stores GL bank account principal amount.
Ex: 130121 (SCB Bank) - Rs.10,00,000.00
In SAP , for the same GL account closing balances will available in FS10N of each month.
Ex: 130121 (SCB Bank) for Sep'09 - Rs.8,50,000.00
Now, the requirement is..
I want to put an User Exit for this Bank GL Account . It has to perform a check operation whenever this GL accounts comes for posting on any FI transactions, and
it'll check each time to the GL account principal balances(from Ztable) with the posting amounts and give a popup message regarding about the bank limits exceeded, remainaing amounts and then only they can able to post the transactions.
Ex: If they are posting in F-02 (general ledger posting) the amount showing in GL account which go for my user exit calculations everytime and the same will be for all other FI GL transactions.
Hope u understood else pls let me know by your replies.
Pls advise.
thanks & regards
sankar.

Hi..
In the tcode where u want to put the user exit, In the menu select System--> Status and double click on the program.
Then click on search and give the search term as "call-customer function".. and see if there are any available user exits..
Select one, and double click on the 3 number..if '003' ,double click on it,it will take u to the Fm..where u will find an include starting with Z.
Here u can write the code u want.
Regards,
Vishwa.

User Exit For Transaction F150 (Dunning)

Hi All,
Can any one help me in finding a User Exit for Transaction F150 (Dunning).

Hello,
Try this one
F150D001
Bye
gabriel

User-Exit for the Me22n

Hi,
I am Mohan. I faced on Problem with the User Exit. I write the user exit for the ME21n for PO Creation. While Creation of the PO the Purchase Requition is mandatory. it is working for the ME21n. But PO creation is another two ways is there. Those are ME22N (Purchase order---> Create) and ME23N
(Purchase order---> Create) for this case also my condition applicable but it is not working for this case. How to write the Code for this. by using Sy-ucomm also. but it is not working.
Please help me.
Regards,
Mohan

Following the user exit's related to ME22N transaction.
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
Regards.

User Exit for saving Invoice

Hi Experts,
My req, is I have to check billing date with order date/ delivery date while creating the invoice in VF01.
For that I have done codig in user exit RV60AFZZ, so it gives error ,but the billing date field get disable.
& this invoice no. alsp get created.
So can anybody plz tell me in which user exit i have to put my code ???
I have tried with RV60AFZC.But it is not working.
My code is
FORM userexit_pricing_prepare_tkomp.
* TKOMP-zzfield = xxxx-zzfield2.
* structure for vbak
TYPES:BEGIN OF ty_vbak,
 vbeln TYPE vbak-vbeln,
 audat TYPE vbak-audat,
 END OF ty_vbak.
*likp structure
TYPES:BEGIN OF ty_likp,
 vbeln TYPE likp-vbeln,
 lfdat TYPE likp-lfdat,
 END OF ty_likp.
*vbrp structure
TYPES:BEGIN OF ty_vbrp,
 vgbel TYPE vbrp-vgbel,
 vgpos TYPE vbrp-vgpos,
 aubel TYPE vbrp-aubel,
 aupos TYPE vbrp-aupos,
 END OF ty_vbrp.
DATA:it_vbak TYPE STANDARD TABLE OF ty_vbak,
 it_likp TYPE STANDARD TABLE OF ty_likp,
 it_vbrp TYPE STANDARD TABLE OF ty_vbrp.
DATA:wa_vbak TYPE ty_vbak,
 wa_likp TYPE ty_likp,
 wa_vbrp TYPE ty_vbrp.
***** take reference document no & delivery no. *****
LOOP AT xvbrp.
wa_vbrp-vgbel = xvbrp-vgbel.
wa_vbrp-vgpos = xvbrp-vgpos.
wa_vbrp-aubel = xvbrp-aubel.
wa_vbrp-aupos = xvbrp-aupos.
APPEND wa_vbrp TO it_vbrp.
ENDLOOP.
IF it_vbrp IS NOT INITIAL.
SELECT vbeln audat FROM vbak
 INTO TABLE it_vbak
 FOR ALL ENTRIES IN it_vbrp
 WHERE vbeln = it_vbrp-aubel.
SELECT vbeln lfdat from likp
 INTO TABLE it_likp
 FOR ALL ENTRIES IN it_vbrp
 WHERE vbeln = it_vbrp-vgbel.
ENDIF.
**** check for invoice date with order date *****
LOOP AT it_vbak INTO wa_vbak.
IF xvbrk-fkdat IS NOT INITIAL AND xvbrk-fkdat < wa_vbak-audat.
 MESSAGE 'Invoice Date is less than Order Date' TYPE 'E'.
ENDIF.
ENDLOOP.
**** check for invoice date with delievery date *****
LOOP AT it_likp INTO wa_likp.
IF xvbrk-fkdat IS NOT INITIAL AND xvbrk-fkdat < wa_likp-lfdat.
 MESSAGE 'Invoice Date is less than Delivery Date' TYPE 'E'.
ENDIF.
ENDLOOP.
ENDFORM. "USEREXIT_PRICING_PREPARE_TKOMP
Thanks & Regards,
Anagha Deshmukh

Hello,
These are the user exits for the tcode.
J_3RSINV Export sales
SDVFX007 User exit: Billing plan during transfer to Accounting
SDVFX008 User exit: Processing of transfer structures SD-FI
SDVFX009 Billing doc. processing KIDONO (payment reference number)
SDVFX010 User exit item table for the customer lines
SDVFX011 Userexit for the komkcv- and kompcv-structures
V05I0001 User exits for billing index
V05N0001 User Exits for Printing Billing Docs. using POR Procedure
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lists
V61A0001 Customer enhancement: Pricing
Keep the break point and try in the debugging in each and every exit and see which user exit is triggred.

HOW TO CREATE A USER-EXIT FOR MB31 GOODS RECEIPT

Hy,
HOW TO CREATE A USER-EXIT FOR MB31
TO COMPARE ORDER QTY CONFIRMED AND GOODS RECEIPT QTY
( IF GR QTY GREATER THAN CONFIRMED QTY ERROR MESSAGE SHOULD COME AND NOT ALLOW TRANSCATION TO PROCEED).
POINTS CONFIRMED.
REGARDS,
KARTIKEY.

Hi Rawat,
 You Don't need to create User Exits,but you need to find user Exits.Below are list of user Exits for MB31.
Use proper exit as per your requirement.
Exit Name Description
MBCF0002 Customer function exit: Segment text in material doc. item
MBCF0005 Material document item for goods receipt/issue slip
MBCF0006 Customer function for WBS element
MBCF0007 Customer function exit: Updating a reservation
MBCF0009 Filling the storage location field
MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0011 Read from RESB and RKPF for print list in MB26
MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc.
award points if ans is useful.
Regards,
Albert

How to find the exact user exit for our requirement?

Dear Mr. keerthi,
can you please explain me how to find the exact user exit for our requirement?

Hi sandip
There is more than one method in which you can check for user-exits.The following method is used very often.
How to find the exact user-exit for your requirement.
1. You can check the user exists using transaction SE85.
2. Repository Information System -> Enhancements -> Customer exits
3. You can search the user-exits by package name.
4. Double click on each exit name to check the function module exits.
The procedure to find the package name.
Execute transaction SE93
Enter the tcode of the transaction for which you want to check the user exit.
Example: if you want to find the user-exit for purchase orders while changing, enter ME22n and press display.
You will get to see the package name
But you need to confirm that the user exit will get triggered at the appropriate event.
( example: you might want some validations to be done ON SAVE of a purchase order)
Checking if the user-exit is getting triggered or not.
1. Open the user exit function module (that you have got in step 4) in Tcode SE37.
2. Click on where used button. In the pop up that immediately appears choose only programs .
3. You will get a list of programs. Double click on the program name.
4. You will get the list of location where this function module user exit is used.
5. Place session break points at each of these location ( at each CALL FUNCTION statement)
6. Now go to your transaction ( say change purchase order tcode:Me22n) and check if the user exit is getting triggered on appropriate event.
regards,
Prasad

How to find the appropriate user exit for invoic02 idoc in idoc_output_invo

Hi all,
I am new to this community p
i have issue regarding the How to find the appropriate user exit for invoic02 idoc in idoc_output_invoic function module.........
thanks,

Hi ,
welcome to SDN.
You can select the appropriate Customer exit accrding to the available parameters .
The list of exits available are
EXIT_SAPLVEDF_001
EXIT_SAPLVEDF_002
EXIT_SAPLVEDF_003
EXIT_SAPLVEDF_004
For Example , if you want to modify the Idoc data(EDIDD) you have to use the EXIT_SAPLVEDF_002. accodingly you can select the user exit according to the avaialable parametres.Use Table MODSAP fto get the Enhancement name.
Hope this Helps
Rgds
Sree
Edited by: Sree on Jul 23, 2010 12:11 PM

REG:USER EXIT FOR DATA SOURCE 0HR_LSO_1

Hi ,
I have to write the enhancement ABAP code for data source 0HR_LSO_1 which is related to module " training and event management "(also known as LMS or LSO) in ECC 6.0 .
So how can I find out appropriate user exit for the same .I have to concentrate on the field "kostl (cost centre)" in that data source .
Please provide some suggestions .
Thanking You ,
Tarun Brijwani .

Hi Tarun...
I this might help you.
In the HR System:
1) T-CODE: CMOD
2) Choose an existing project (vg: Z12345)
3) Modify
4) Press Components button
5) Look for the enhance: RSAP0001 (the BW extracting enhancement)
6) The you have one of the following option:
a- If the Data Source is "transaction data": The exit is "EXIT_SAPLRSAP_001"
b- If the Data Source is "master data": The exit is "EXIT_SAPLRSAP_002"
7) double-click in the appropriate one
8) You'll see an INCLUDE sentence. Could be this ZXRSAU01 or this ZXRSAU02 (depending on the previous step). Double-click and you'll be redirected to the SE38
9) some code:
CASE i_datasource
WHEN '0HR_LSO_1'.
    LOOP i_t_data INTO my_struct
       my_struct-KOSTL           "Here you'll must have your Cost Center
       ...etc...etc...etc
    ENDLOOP.
WHEN OTHERS.
ENDCASE
Hope it helps.
gdmon

User exits for route

Similar Messages

Maybe you are looking for