User exit for save data in T.code PA40 ABAP-HR

Hi Expart,
what is the user exit which is trigger when we save the data through pa40 transaction which check the latest update in the database.
Kindly give me exit name .

Hi Vikash ,
Please refer to below Exits :
HRPBAS01            User Exit for HR Master Data
HRPC0001            HR: PC download authorization
HRRPAI01            User exit for FB HR_ENTRY_DATE and HR_LEAVING_DATE
PARA0001            Enhancement for Determining the Number of Periods
PARA0002            Enhancement for Calculating Annual Salary; IT0008,14,15
PBAS0001            PA: Pers.Admin./Recruitment: Default values and checks
PBAS0002            PA: Enhancements for Personnel Administration - Menu
PBASRP01            PA: User exit distributed reporting
Hope this will help you.
Regards,
Nikhil

Similar Messages

User exit for save button in transaction code CBIH82

HI All.
i have got an issue with finding of user exit for transaction code cbih82.
my functional consultant want me to go for exit CBIH_LB39_UE_POST_COMMIT (se37) but i cont find any user exit in this function module as it is triggering when i click on save at cbih82 in debugging.
but i cont find any user exit in this CBIH_LB39_UE_POST_COMMIT.
so could any one help me in this issue for finding user exit which should trigger when i click on save at cbih82 tcode.
will be waiitng for a good answer.
bye.
regards.
seetaram.

check in smod
user exits for CBIH82
Exit Name           -- Description
EHSIAHM1           -- EH&S: Menu Exit 1 for Incident/Accident Log Header
EHSIAHM2           --- EH&S: Menu Exit 2 for Incident/Accident Log Header
EHSIAPM1           --- EH&S: Menu Exit 1 for Incident/Accident Log Person
EHSIAPM2           -- EH&S: Menu Exit 2 for Incident/Accident Log Person
EHSMPHM1        --   EHS: Menu Exit 1 for Measurement Project Header Data
EHSMPHM2         -- EHS: Menu Exit 2 for Measurement Project Header Data
EHSMPJM1          -- EHS: Menu Exit 1 for Measurement Project Measurements
EHSMPJM2          -- EHS: Menu Exit 2 for Measurement Project Measurements
EHSSARA            -- EHS: Check/Edit Lines in SARA List Before Printout
Salil...
Edited by: salil chavan on Nov 19, 2008 8:23 AM
Edited by: salil chavan on Nov 19, 2008 8:25 AM

User exit for component data in ME21n/ME22n

Hello,
I have a requirement to issue an error message if a component quantity is not evenly divisible by the end item quantity. The component data (BOM) is entered after clicking the components button on ME21n/ME22n at the item level detail. I need to evaluate the data after a user clicks save, but I cannot find a user exit where the data is passed into, or where it is defined as global data where I can reference it in a user exit. The data is stored on the screen in structure MDPM and stored in the database in table RESB.
I appreciate any help,
David

Thanks for pointing me in the right direction.
I was able to put my code in EXIT_SAPMM06E_012 and retrieve the component data through (SAPLEINK)XMDPM[]
Below is the code I used to assign the data to be able to evaluate it.
FIELD-SYMBOLS: <z_mdpm_x> TYPE ANY.
DATA: i_mdpm_x TYPE STANDARD TABLE OF MDPM_X.
Fetching Component data
ASSIGN ('(SAPLEINK)XMDPM[]') to <z_mdpm_x>.
CHECK sy-subrc = 0.
Assigning data into an internal table
i_mdpm_x[] = <z_mdpm_x>.
CHECK i_mdpm_x[] IS NOT INITIAL.
David
Edited by: David Herrema on Oct 20, 2010 3:03 PM

User Exit for KP90 to add Company Code

Hi Experts,
I need to add company code to the selection criteria of the KP90 transaction
and thereby clear plan data by company code.
Please let me know the User Exit for the same or the way i should search for one.
Or shall i instead create a Z program to meet the above requirement.
Please help.

Go to SE80 - choose program - SAPMV45A - Screen number 8309 - this is the screen exit to add fields in Additional data b
You can write your own code for this screen and Try to use other user exits in SAPMV45A program and make sure you use transaction type or Sy-Tcode as the same program is used for quote and sales orders tooo
Good luck

User Exit for Validity Date for VA41 Tcode

Hi,
I am giving order type in VA41 Tcode and then Clicking on 'Create with Reference' .Then a Pop Up is getting generated. In this i am giving Contract created with validity date lessthan today's date(in Contract Tab).For Example i created a Contract xxxxxx with 'valid to' 9.12.2008. When I am giving this contract and clicking on 'Copy' button a Warning message is getting generated 'The sales document is only valid until 09.12.2008'. Now i have to change this into Error message instead of Warning Message.
i used User Exits mv45afzz,MV45AFZA,MV45AFZB. But the debugger is getting started only after Warning message got generated.Is there any User Exit for which debugger gets started when i give the Contract and then Click on 'Copy' button. Please Suggest.
Thanks and Regards
K Srinivas

Hi,
One idea. Go to VTAA (copy between sales docs) and create a new VOFM where you manage the copy control. Set a warning/error message in the new VOFM (in your range number), and try it.
Regards,
Eduardo
Edited by: Eduardo Hinojosa on Dec 10, 2008 3:58 PM

User exit for additional data B for sale order item .

Hi., all
my client requirement is
( This business requirement will make the Last Price for a given item be visible during order entry. )
u2022Retrieve & display during order entry, the most recent unit price given to a customer for a specific item, from the Billing data.
. Display the Last Price under Additional Data B Screen
add new field (last extended price) in additional data b screen.
after that 1.     Using the Sales Order Material Number (VBAP-MATNR), Sales Order Sales Organization (VBAK-VKORG), Sales Order Distribution Channel (VBAK-VTWEG), Sales Order Division (VBAK-SPART), Sales Order Sold-to Number (VBPA-KUNNR for VBPA-PARVW=u2019AGu2019) to access the Billing Items By Material Index Table (VRPMA) and specify a billing date (VRPMA-FKDAT) of less than 60 days from current Sales Order requested delivery date (if specified at header VBAK-VDATU or at the schedule line level (VBEP-EDATU). This will result in all the billing documents where the Sold-to bought the item but isnu2019t completely refined as of yet. Retain the billing document (VRPMA-VBELN), item (VBPMA-POSNR), and billing date (VRPMA-FKDAT) in a temporary table to pass to number 2 as the input.
2.     Use the billing document (VRPMA-VBELN) and item (VRPMA-POSNR) to read the Sales Document Partners Table (VBPA) where the partner function (VBPA-PARVW = u201CSHu201D) and the Sales Order Ship-To (VBPA-KUNNR for VBPA-PARVW=u2019WEu2019) to select ONLY billing documents that are for that given ship-to location. This filters out only billing documents relevant for that ship-to location.
3.     From the resulting list of billing documents, select the most recent date (VRPMA-FKDAT) which will refine the search for the last Billing Document (VRPMA-VBELN) and item (VRPMA-POSNR).
4.     Using the most recent Billing Document (VBPA-VBELN), access the Billing Document Item Table (VBRP). To result in the Last Extended Price as VBRP-KZWI1.
5.     This price will be an extended price which needs to be calculated as a u2018unit priceu2019. For this billing item, select the sales unit (VBRP-VRKME) to determine if the sales unit is in cases or eaches.
a.     If the unit of measure is in cases, then simple math is required to divide the Last Extended Price (VBRP-KZWI1) by the billing quantity (VBRP-FKIMG). Standard rounding should apply when .005 results in a .01.
how to achive this ?

Hi Chakravarthy,
use the Exits provided in SAPMV45A -includes MV45*ZZ and screen exits as well 8309 8310 8459, 8460. Just be sure to
use zznnnnnn include in the SAP provided forms instead of coding directly in the forms.
You can check below user exits:
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.
Reddy

User Exit for reading data from a hierarchy in BW-BPS

Hello Forum,
How can i fetch all the records from a particular node in a Hierarchy using a user exit in a variable in BW-BPS,
Plz Help,
Regards,
KK

Hi,
This is a sample code that may help you.
DATA: BEGIN OF wa_val,
        from TYPE rsleaffrom,
        to   TYPE rsleafto,
      END OF wa_val,
      tb_val LIKE wa_val OCCURS 0 WITH HEADER LINE,
      tb_grpval_ce LIKE wa_val OCCURS 0 WITH HEADER LINE,
        tb_ce_val   TYPE rshi_t_hienode,
        tb_ce_intervl TYPE rshi_t_interval,
        wa_hiedirkey TYPE rshi_s_rshiedirkey,
        tb_node_val TYPE rshi_t_hienode,
        tb_interval TYPE rshi_th_interval,
        wa_interval TYPE rshi_s_interval,
SELECT SINGLE hieid objvers FROM /bi0/haccount
                INTO wa_hiedirkey
                WHERE nodename = group-name.
CALL FUNCTION 'RSSH_HIERARCHY_READ'
    EXPORTING
      i_rshiedirkey     = wa_hiedirkey
      i_date            = sy-datum
    IMPORTING
      e_t_rsnodes       = tb_node_val
      e_th_rsinterval   = tb_interval
    EXCEPTIONS
      invalid_hierarchy = 1
      name_error        = 2
      iobj_not_found    = 3
      OTHERS            = 4.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
thanks
pratyush

User exit for actual dates in CJ20N

I have a req, When i start any activity i enter date in user field in actual dates as displayed in below pic
Now when i enter date in user field it should be copied to actual start date field in dates tab as shown in below pic
Kindly suggest the user exit needed for it
Best Regards,
Nitesh H Panchal

Hi Nilesh,
Try this with Substitution & Validation rule.
You want AFVGD-ISDD should have same detail as of AFVGD-USR08.
However with the help ABAPer you can achieve this easily.
Regards,
Pranav

User exit for updating date field in msc2n while doing a goods rcpt in cor6

is ther anyexit to update the Date1 field(MCHA-FVDT1) in MSC2n( Batch) while doing a Good receipt for an order
Thanks in advance

Hi,
to find the user exits & Badi's for the T-code..
go to table TSTC>enter T-code and execute> get the Program for the t-code..
and go to-se38-->get the package attached to the t-code..
next go to t-code Se15>expand the enhacement tab>enter package under userexit and
                                                     execute you will get the list of exits
                                                     available...
                                                  -->enter package under Badi's tab and
                                                     execute you will get the list of Badi's
                                                     available...
All the User exits are stored in Table MODSAP..
Prabhudas

User Exit for VA01 and VA02 transaction codes

Hi,
I am writing a userexit for PO number checking for VA01 and VA02 transaction codes.The PO number should be unique in the table (vbkd-bstkd).Duplicate PO number entries can be checked with Sold-to Party.If anybody written something like this....please advice me...
Thanks in advance.
fractal

Hi Fractel,
Why are you looking for a user exit to do this duplicate PO check?
This can be achieved through configuration of your sales order document type and message control. Follow the path below for configuration of the document type.
Implementation Guide for R/3 Customizing (IMG)
-->Sales and Distribution
   -->Sales
      -->Sales Documents
         -->Sales Document Header
            -->Define Sales Document Types
Once you execute this node, you will see all the available document types. Select the one you are interested in and click the details icon. In the subsequent screen, under "General Control" section, there is a field "Check purch.order no". Pick the value 'A' from the drop-down list.
Once you do this, system will check for duplicate PO numbers whenever you are creating or changing the sales order with that document type. If duplicate, it issues a message.

User Exit for delivery Date Update in ME41

Hi,
I want to Create one User Exit which will Update the Delivery Date of All Line Items ,same as of Item one.
Detail : When creating RFQ using tcode ME41, create with Reference to PR, add your collective Number and copy few line items from your PR, say 5 items selected, now when come to RFQ it asks to change item details if require,
now here i want to change Delivery date of item one and when putting new delivery date, and press enter then it should update all (remaining 4 ) items delivery date same as of item one. so that user do not need to update all items delivery date one by one.
is there any user exit/Enhancement Spot available which get triggered after pressing enter when changing the items?
Thanks in advance.
Regards,
Sujeet

Hi,
Check these enhancements:
ME590001
MEETA001
MEFLD004
MELAB001
Jitendra

User exit for budget profile per comapny code

Hi Gurus,
We are having around 100 company codes in our system. They all using same internal order type for creation of internal order for capital projects.Now for one of the company code I want to have a budget profile by using same order type.
Can anybody help mke with a functional module which I can use to maintain budget profile per company code using existing internal order type.
Thank You

Hi,
Budget profile is maitained on the level of order type. You have to define it there. Are these companies maintained under one controlling area?
Regards,
Eli

User exit for pricing date determination

Hi Friends
I want to have a custom validation at pricing date determination at billing document creation. Please anybody can help me which exit available at VF01 for this purpose.
Regards,
Ramindu

Hello,
Check for the below link:
http://help.sap.com/saphelp_46c/helpdata/en/18/f62c7dd435d1118b3f0060b03ca329/content.htm
Prase

Regarding the User Exit for Goods Receipt (MIGO) Transaction code

Hi,
I have a requirement where I want to capture the Goods Receipt Document number when its got saved (Created).
I have find out Exits available for the MIGO.
MB_CF001
MBCF0002
MBCF0005
MBCF0006
MBCF0007
MBCF0009
MBCF0010
MBCF0011
I want to know which is the right one to serve my purpose (Exit Name).

Hi Nikhil.
I'm not sure which one is the best (there are several exits in SAP).
But what i usually do is:
- i have a dummy project in DEVELOPMENT SYSTEM, where i include the enhancements i suspect that solve my problems.
- then i set the project active, break point ... that's it.
Hope this helped.
Reward helpfull ideas.
Best regards.
Valter Oliveira.

What are the User Exits for Sales Order creation process?

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

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

User exit for save data in T.code PA40 ABAP-HR

Similar Messages

Maybe you are looking for