Search user-exit for create purchase order

Hi all,
i'm searching the user-exit (or BADI) for create purchase order.
Thanks for help.

Hi CECG,
GOTO SMOD and press F4
then Click on Information system
and in the Package name give as ME
and press enter.
you will get all user exits for Purchase Orders
Hope this solves your problem.
Please reward points if found helpful.
Thanks and regards,
Rajeshwar.

Similar Messages

User exit for create delivery order

hi! expert.
i have a scenario when user B create delivery order (VL01N) then get DO No. I want to send this DO No. to user A 's mail.
when i look for user exit with this [program|http://wiki.sdn.sap.com/wiki/display/ABAP/FindEXITandBADIfroagivenTransactionCode] . i don't know which one I should use. please suggest me.
V02V0001
V02V0002
V02V0003
V02V0004
V50PSTAT
V50Q0001
V50R0001
V50R0002
V50R0004
V50S0001
V53C0001
V53C0002
V53W0001
VMDE0001
VMDE0002
VMDE0003
VMDE0004
my SAP version is 4.6
best regards,
Kiitisak

Hi,
Any userexit asks the access key for first time.(Not the case with customer exits). So no probelm. Get the access key from your BASIS team and implement the exit. I wonder that MV50AFZ1 is not implemented yet in your system. Is your SAP system new?
This is the most busy exit (Locked by some one at any time) in most of the systems:)
Thanks,
Vinod.

User Exit for PO (Purchase Order) Change

Hi,
I want to know the SAP Standard User Exit that is triggered ONLY during changing / modification of PO(Purchase Order).
Thanks in Advance.
RK

ME_PROCESS_PO_CUST
use above BADI for ME22N/ME21N,often we use method PROCESS_HEADER
PROCESS_ITEM our most of the requirement meet by these methods only,check once if your requirement does meets with these two methods?
if not than you may implement some more method which are in ME_PROCESS_PO_CUST, for more help you may read documentation,there is well enough documentation already there for each method.
and for ME22/ME21 you may use
ME_PURCHDOC_POSTED
and method POSTED.

Need User Exit before the Purchase Order saved!!!

Hai All,
 I am in search for User Exit before the Purchase Order gets saved.This User Exit should capture this generated Purchase Order and post it to the Destination System for further processing.
 Can anyone help me to find this User Exit.
Thanks,
Ugandhar.
Message was edited by: Ugandhar Domathoti

Check out this enchancement in smod MM06E001
in that EXIT_SAPLEINM_001
 EXIT_SAPLEINM_002
may help you ....
regards
vijay

I need output type NEU automaticaly for create purchase order document type

Dear Experts,
I need output type NEU automaticaly for create purchase order document type NB
when transaction code MN04, I am doing the following:
(1) I selected the third option Purchasing Output determination: Document type
(2) I selected the output type NEU.
(3) In condition records in document type , i have chosen NB.
(4) In name its automatically coming as Purchase requisition
Please suggest how Purchase Order NB will come

Hi,
Check & press F4, NB Purchase Order (for catagory F) will be there after entering PO output type NEU & then maintaion the condition record in MN04.
Output type NEU automaticaly defaulted during purchase order creation with document type ,then just fine tune the output (message) type in following path:
SPRO--->MM->Purchasing>Message>Output control->Message types> Define message type for Purchase Order----->Fine-Tuned Control: Purchase Order
Now here select the check box corresponding to your output(message) type NEU to have print output automatically displayed & save.
Now try to creating Purchase Order & you will have default message type NEU.
Regards,
Biju K

User Exit for checking Purchase Requisitioner Field in CJ20N Transaction

Hi,
I want user Exit for checking Purchase Requisitioner field while making PR through CJ20N transaction. I have trie EXIT_SAPLEBND_001 user exit. Problem in this user exit is I am not getting Purchase Requisitioner No & Item No in I_CEBAN
structure.
Please suggest what to do ?
Regard's
Shabbir

Hi,
You can check with this BADI ME_PROCESS_REQ_CUST.
Kindly refer below mentioned link for further details:
Badi ME_REQ_POSTED For CJ20N Transaction
Hope this will help you.
Regards,
Mudita

User Exit for Va01[ Return Order ]

I Have Written User Exit for Va01[ Return Order ] in MV45AFZZ,
I'm Making tax field VBAK-TAXK1 as 0 when making this field as 0 Pricing Condition Tax calculation should not be exit and tax value must be 0.
How to do this process...plz give me a solution.

Hi
For price calculations or modifications, you may have to write the code in SD routines. Check this T.code VOFM.
Reward if it helps!
Krishna

User Exit for third party order processes.Missing in ECC 6.

Hi All,
There is a user exit EXIT_SAPLJ3AM_003 which exist in 4.6C version of SAP for AFS.
This user exit is for Third Party order processes. This is called within the include LJ3AMFD1 of the main program SAPLJ3AM.
But this User exit is missing in ECC version of SAP for AFS.
Could anyone please let me know how I can resolve this issue as I need this User exit for my requirement. Has SAP provided any enhancement spots for this?
I tried to search the enhancement spots and OSS notes but couldnu2019t get any useful information.
Please advice.
Thanks,
Ameesha

changed our requirement

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 Stock transfer order

Hi,
My requirement is : i want to create a Stock transport order in which i have to set an error message based on the Document type and receiving plants country name.
Say for an e.g. if my doc type is STPO and plant is pl10(which belongs to Germany)then no error will come, but if
doc type is STPO and plant is pl11 ( which does not belongs to Germany) In that case error has to occur.
I want to put the logic in the code.
Kindly provide me program name and user exit where i can implement this.
Regards
Utsav

hi
Please discuss with ur technical consultant and given ur functional need in Functional spec form for user exit .
In that u have to mention eaxactly what u need i.e ur requirement regarding the user exit for STO process.
So it can be done with ABAPer with you as functional consultant.
Thanks
SAP_MM

Program for Creating Purchase Order with reference to purchase requisition

Hi ,
I need to Create purchase Order with reference to Purchase requisition,
in my case i need to automize the Process which is happening in MD04,
Can you please suggest me ?
Thanks ,
Murali

Hi,
Plz check this link. It will be helpful to you.
Purchase order creation with reference to PR
We can also create the PO Using the BAPI_PO_CREATE1 function module.
In this function module fill up the all necessary Details.
With details in Item Table we haveto give the Fields PREQ_NO and PREQ_ITEM for each item .
then it will creates the PO with PREQ.
Thanks & Regards,
Sarita Singh Rathour
Edited by: Sarita Rathour on Aug 3, 2009 7:01 AM

LOGIC FOR CREATING Purchase Order FOR repective Purchase Requisiton URGENT

hi all,
guys i have got all the purchase requisition for the materials from EBAN table.
now i have to create the PURCHASE ORDER for these PURCHASE REQUISITIONS.
so how should i proceed.
what logic i should use to create the PO for These PR.
if anyone of u have any code regd this requirement then plz share it with me.
its very urgent, i have to deliver it by today evening.
plz help me .
i will award ur efforts.
Thanks
Sanjeev

hi,
Automatic Conversion of PR to PO
You created purchase requisition for various material. During creation of purchase order you used the following path:
Purchase Requisition
.......Follow on function
.........Create Purchase Order
............automatic via purReq.
When you mentioned required purchase requisition number and execute, system give error that purchase requisition does not contain any suitable item.
Is there any setting in customization where you can monitor and use that function.
In an effort for you to successfully use the Transaction Code ME59 to automatically convert the current PR into PO, then the following criteria should be met:
1) In the Purchasing View of the material master data, the "Autom. PO" field must be clicked;
2) In the Purchasing View of the Vendor Master Data, the "Automatic Purchase Order" field must be clicked;
3) The Outline Agreement or Purchasing Info Record shall be maintained which will allow the automatic copying of unit price and other conditions into PO;
4) The Source List shall be maintained for the nominated vendor which was shown in either the Outline Agreement or Purchasing Info Record.
or
it might be PR subject to release strategy and not yet released
or
If you're not using a source list or automatic creation of PO, you may need to assign the requisition to a purchase information record using transaction ME56. Then it should appear in ME58.
reward points to helpful answers.
rgds

User Exit for getting Purchase Requisition Release Strategy

Hi Experts,
When a user creates a PR I need to know the user exit I need to implement so that the First Approver (Processor) text in the Release Strategy is populated from a custom table. I have seen that the field is MEREL_S_GRID1-STEXT. I also need to know if I can implement a user exit so that it pulls the release strategy for a PR for assets (Acct Category A) since it is pulling for Acct Category K (Cost Centre) and the Release Strategy tab is appearing in this case.
Kind Regards,
Darlington

Hi Meenakshi,
Thanks for the very useful answer. It has given clues on how to resolve this issue. I have resolved this issue for the Asset item category using the following thread: user exit for requisition release strategy, and also SAP Note 365604.
However, I have another issue, the release strategy for Stock Items, (item category blank) is not pulling through. I need to use the same method above but would like to know how it determines the funds centre for a specific stock item. I couldn't find where that is implemented in the material master and I need info on how to determine the account assignment for stock items based on the funds centre.
Regards and Thanks.

User Exit to Create Production Order when creating of Purchase Order

Hi Guru's,
I want to create the Production Order when creating the Purchase Order. i want to know is there any user exit exists for that??
My scenario is as follows.
we are converting the Purchase Requisition to the Purchase Order , while doing this we want to create the Production Order.. Is this possible??
If possible how can we do that???Please suggest me the possible solution.
Thanks in advance.
Thank you,
Adi.

Teja,
My Scenario is as follows.
P1- Manufacturing Plant
P2 - WareHouse Plant (Procures Material from P1 using STO)
When we run the MRP in P2, it creates a Purchase Requisition, that Purc.Req is going to be convert as STO (Stock Transport Order) in P1 Plant.
When converting the Purchase Req to STO, we need to create a Production Order in P1 Plant.
we know that system will creae the Purchase Order only, is there any possibility that,For creating the Production Order is there any user Exit/BADI or any other procedure while creating the Purchase Order????
Thanks,
Adi.

User exit to change purchase order quantity

Hi all,
when we create production order based on that service purchase requisition is created. based on that in me21n service purchase order is created and now if we do any change will be changing the production order qty after creating the order that is reflecting in service purchase requisiton but not reflectiing in me21n purchase order number so can u suggest me which enhancement to use and which user exit should be used to acheive this functionality i have tried using ppco0012 enhancement by keeping break point but when running the scenario it is not going to debug mode.
Regards,
Naveen
Moderator Message: Previous warnings from Moderator ignored. Account sent for deletion.
Edited by: kishan P on Dec 1, 2010 9:47 AM

Hi,
You may use USEREXIT_MOVE_FIELD_TO_ME_REQ.
You can find this in include MV45AFZB.
<REMOVED BY MODERATOR>
Regards,
Sharad
Edited by: Alvaro Tejada Galindo on Jul 21, 2008 12:37 PM

Search user-exit for create purchase order

Similar Messages

Maybe you are looking for