User Exit which triggers after creation of purchasing group

Hi all.
We are creating purchasing group by using the FOLLWOING PATH
SPRO->MATERIAL MANAGEMENT->PURCHASING->CREATING PURCHASING GROUP.
Our issue is whenever new purchasing group is created I need to track this and send this new purchasing group details only to other system. Can we have some user exit we can call one RFC.
Pls let me know. Thanks in advance.
cheers,
sami.

Hi,
You can check which BADi is getting initiated on creating new purchase order and do your coding there..
You can search a BADi with SQl trace..
Go through this thread
Exit for Purchase Order ME21N
Regards
Mudit
Edited by: Mudit Batra on Jan 22, 2009 6:22 AM

Similar Messages

Exit which triggers after SO Save

Dear Experts,
I have a requirement to send auto mail to user on customer credit status when user create Sales Order and save.
I did all the necessary code in the form routine USEREXIT_SAVE_DOCUMENT of include program MV45AFZZ.
USEREXIT_SAVE_DOCUMENT will trigger before the document save but I need the condition value for that SO and that will be available only after the Order saved therefore my requirement will be completely fulfil if there is any exit which triggers after Order saved, please let me know if there is any exit triggers after SO saved.
Thanks in advance...
Regards
Venkat

Hi Venkat,
I think you can achieve through output. You can create an output condition similar to KRML (in which the credit data is send to credit rep) and modify the same as per your need.
How ever the desired credit data that you are looking for can be called from sales summary(t code-VC/2): Info block 018 Credit info.
Hope this will help you.
Please revert to forum if have further doubts
Cheers
Atul

User Exit which runs after pressing SAVE button at VF01 Screen.

Dear all,
I need user Exit which runs after pressing SAVE button at VF01 Screen.
Kind Regards,

If you search the forum, you can find plenty of threads on this, for example Re: Badi or user exit for VF01 while save Can you let the forum know what exactly you want to achieve using user exit during saving of a billing document?
Regards,

User-exit for ME59 - Automatic creation of Purchase Order from Requisitions

Hi,
In ME59, is there a way to prevent PO of being saved, but instead created with the « hold » option?

Hi,
I tried this for ME59N and struggled.
I think EXIT_SAPMM06E_013 cannot change EKKO (it only imports it as the exit is for posting customer data) and BAdi ME_PROCESS_PO_CUST cannot change MEMORY because method SET_DATA uses mepoheader (and later mepoheaderx).
Check the two structures in SE11, in our ECC5 system mepoheaderx doesn't have field "memory" so the BAdi can work out its been changed (via method SET_DATA).
Even though lots of people have asked this question and the same exits/BAdi get highlighted I cannot see anyone confirming that they have managed to do it.
If anyone has then please share the details.
Thanks, Matt

BADI or User Exit for VL09 after Reversing

Hi Experts,
I have a requirement that updating certain values in Custom Table after Reversing a Delivery. Is there any BADI or User Exit which trigger After Reversing a Delivery in VL09.
Thanks in Advance.

1) Goto se24 (Display class cl_exithandler)
2) Double click on the method GET_INSTANCE.
3) Put a break point at Line no.25 (CASE sy-subrc).
Now
4) Execute your SAP standard transaction
5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
7) This way you will find all the BADIs called on click of any button in any transaction

User Exit that triggers for Change operation

Hi All..
I want a user exit which triggers when I enter into an infotype(2001) from tcode PA30.
My actual requirement is to show the field REFNR in display mode.
By using the exit PBAS0001 exit0001 I can make the field REFNR in displaymode for create operation.
But in change operation of the infotype the exit is not getting triggered.
Regards,
Anji.

chk these
Transaction Code - PA30                     Maintain HR Master Data
Enhancement/ Business Add-in            Description
Enhancement
PBASRP01                                PA: User exit distributed reporting
PBAS0002                                PA: Enhancements for Personnel Administration - Menu
PBAS0001                                PA: Pers.Admin./Recruitment: Default values and checks
PARA0002                                Enhancement for Calculating Annual Salary; IT0008,14,15
PARA0001                                Enhancement for Determining the Number of Periods
HRRPAI01                                User exit for FB HR_ENTRY_DATE and HR_LEAVING_DATE
HRPC0001                                HR: PC download authorization
HRPBAS01                                User Exit for HR Master Data
Business Add-in
HRPAD00_PREM                            Definition of User Exit for Collective Search Help PREM
HRPADUS_PBAS_0001                       Customer Exit for Message handling
HRPAD_SUBTY_CHECK
HR_F4_GET_SUBTYPE                       HR: Entry help for subtypes
HR_FAST_ACTION_CHECK                    Check fields on the fast entry screen
HR_INDVAL                               HR: Indirect wage type valuation
HR_SET_PKGAB
HRPAD00_RECOG_SCREEN                    Employee - Recognition Screen
HRPAYXX_DELETE_PERNR                    BAdI for Reports Deleting Personnel Numbers
HRPAD00_PAPM                            Definition of User Exit for Collective Search Help PAPM
HRPAD00_GET_AF_0008                     Additional Fields for Basic Pay Infotype (0008)
HRPAD00_ENTRY_LEAVE                     HR_ENTRY_DATE and HR_LEAVING_DATE
HRPAD00_ADRS                            HR: Address formatting
HRPAD00MGEACTIVATION                    Activation Action BAdI for Global Employees
HRPAD00INFTY                            Update / Infotype maintenance
HRPAD00AUTH_TIME                        Time Logic in the PA Authorization Check
HRPAD00AUTH_RECORD                      Spanish Data Privacy Law: Exit for Recording
HRPAD00AUTH_CHECK                       HR: Authorization Check
HRIV_REDUCE_AMOUNT                      Reduction within Indirect Valuation

Which user exit is triggered on Save of CV01N/CV02N

I have some requirement to be triggered on the Save of a document using CV01N/CV02N.
I found three exits in the transaction EXIT_SAPLCV110_001, EXIT_SAPLCV110_002, EXIT_SAPLCV110_003 but none of them get triggered on Save even though I have activated the enhancement.
If someone knows which user exit gets triggered on Save of CV01N/CV02N please let me know.

You can use BADIs.
You can use DOCUMENT_MAIN01.
Go to SE18. Display 'DOCUMENT_MAIN01.
On the menu bar, Click on Implementation > Create.
Give your own implementation name starting with Y or Z.
There's a method called BEFORE_SAVE in this.
It has all the data DRAW, DRAD, DRAZ etc as Changing Parameters.
So you will be able to manipulate that data in that method.
Activate the implementation And you are good to go.
Reward if helpful.

User exit which gets triggered when a line item is deleted in va02

Hello all,
I am unable to find a User exit which gets trigerred when i delete a line item from va02.If I use the User Exits for saving data in Include MV45AFZZ the screen field VBAP-POSNR for line item is not getting accessed.All i need to compare the line item texts. Which means if any of these texts change then i need to write my logic. But the screen field name for all the texts is the same.Please guide me.

Hello,
Whever you perform any actions on the line item, we have the user exit in MV45AFZZ, userexitxvbap. Whenever the the item is deleted the UPDKZ value in XVBAP value is set to 'D', else since you are using the transaction VA02, any change is recorded in YVBAP(for old values) and XVBAP(for new values), so using this two internal table you can write any necessary logic.
BR
Sudhakar.

User Exit which is triggered when we do the posting to accounting

Dear Guru,
Can any one provide list of User Exits which are triggred while Posting in accounting happens via MM transaction?
Regards,
Sandeep

Hello
Go through the link
http://www.easymarketplace.de/userexit.php
Regards

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

Need User Exit which wll allow to display a error message

Hello All,
i need a User Exit in Tx ME21N .
When user try to drag multiple PR for PO at that instant only there should be an User Exit which will restrict the user to doing so with a error message.

ME_CHECK_ALL_ITEMS
ME_CCP_ACTIVE_CHECK
MD_EXT_SUP
ME_DEFINE_CALCTYPE
MD_STOCK_TRANSFER
ME_PROCESS_PO_CUST
These are the BADIs gettting triggered while dragging the PR's to PO creation.
You can check any of these as per your requirement.
Check if the BADI 'ME_PROCESS_PO_CUST' is useful.

User exit which changes po (item level) delievery date (eket-eindt)

Hi,
Can you please suggest EXIT which triggers while changing delivery date (LIKP-LFDAT) of outbound delivery through TCODE VL02N should reflect in its corresponding purchase order delivery date ( ME22N at item level field (EKET-EINDT)..
I tried in USEREXIT_SAVE_DOCUMENT_PREPARE include MV50AFZ1. but changes are not reflected in PO.
code:
XEKET-EINDT= LIKP-LFDAT.
but it is not working .there is no field as update indicator (updkz) in table xeket..Please let me know if I am doing something wrong.
Thanks in advance.

Have you checked the BADI 'ME_PROCESS_PO_CUST' ? This has a method PROCESS_ITEM, this may solve your problem.

User exit for MIRO after pressing ENTER

Hello,
Is there a user exit in MIRO after entering PO, Invoice date and Reference and pressing ENTER?
I want to popup a message that relates to vendor data that does not appear in the screen
Thanks,
Moshe

Hi,
BADI
class_name                     CL_EX_PPA_CUST_BADI
exit_name                      PPA_CUST_BADI
class_name                     CL_EX_FAGL_PERIOD_CHECK
exit_name                      FAGL_PERIOD_CHECK
class_name                     CL_EX_MRM_VARIANCE_TYPE
exit_name                      MRM_VARIANCE_TYPE
class_name                     CL_EX_MRM_HEADER_CHECK
exit_name                      MRM_HEADER_CHECK
Check which one is best.
Regards,
Clemens

User exit at the time of saving purchase order

Hi experts
There are some plants for which we need to auto GR. Is there any user exit available which will check these plants in PO at the time of saving PO document and do auto GR.
Regards

Enhancement
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
MM06E011                                Activate PReq Block
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
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
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
User exit for me21n

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

User Exit which triggers after creation of purchasing group

Similar Messages

Maybe you are looking for