User Exits for Purchase order & requistion to control Material description

Dear Experts,
I am creating a Purchasing requisition & Purchase order for certain Material Type. Currently user can change material description at item level without anu check. Now I have different material type like PACKING(ZPAC), Raw material(ZROH) Etc.
My requirement is like such that i want to allow change of material description of packing material(ZPAC) but system should not allow for Raw material type(ZROH). so from where i can control this?
Can any one give me EXIT name or enhancement point for Purchase order & requisition.
Thanks in advance.
Regards,
Piyush

Dear,
You can achieve this by Field selection in SPRO > MM > Purchasing > Purchase Requisition > Define Document Types > Here get the Field Selection Key for PR Doc Type
SPRO > MM > Purchasing > Purchase Requisition > Define Screen Layout at Document Level > Here for that Field Selection Key, for Selection group "Basic data, item", make field "Short text" as display.
Similarly do for PO also SPRO > MM > Purchasing > Purchase Order > Define Document Types > Here get the Field Selection Key for PO Doc Type
SPRO > MM > Purchasing > Purchase Order > Define Screen Layout at Document Level > Here for that Field Selection Key, for Selection group "Basic data, item", make field "Short text" as display.
Note: - But in case of text Purchases, you need to create a new PR and PO Document Type. So that this config. will not have any impact on Text Purchases.
Regards,
R.Brahmankar

Similar Messages

User Exit for Purchase Order Release Strategy

Hi,
I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
Thanks in advance.
Mick

Hi
Check the following Exits and BADI for Pur Requisition
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
Business Add-in
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_PURCHDOC_POSTED Purchasing Document Posted
SMOD_MRFLB001 Control Items for Contract Release Order
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_REQ_POSTED Purchase Requisition Posted
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_BSART_DET Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN Commitment for return item
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CHECK_OA Check BAdI for Contracts
Reward points if useful
Rgds,
Naren

User Exit for Purchase Order Line Items.

I have been trying to search for a User Exit for Purchase Order Line Items and have been unable to do find anything. I need to overwrite the Net Price and Pricing Condition on a certain type of material based upon the Pricing Condition for that Line Item which is on the Sales Document. Any direction you can point me into would be greatly appreciated. Thanks.

Thanks for pointing me in the right direction. I was able to create my first BADI using the PROCESS_ITEM method. The following link was also very helpful: Re: BADI ME_PROCESS_PO_CUST Method:PROCESS_ITEM

BADI / User exit for Purchase order(ME21N) after saving the document

Hi expert,
I need the BADI / User exit for Purchase order(ME21N) after saving the document
This is for email sending after create the purchase order so PO document number will be the import parameter
pls help me
point will be reward
Regards,
Ganesh

Hi Ganesh,
Could you please share your solution?
Thanks.
Hoops
Edited by: Hoops on Jun 13, 2011 10:51 PM

User exit for Purchase order to change RESB-SOBKZ

Hai,
The requirment is to change the purchase order's RESB-SOBKZ.
The purchase orders will be created in r/3 from APO & the same PO would be published back to APO.
I have to change the above metioned field at the time of PO save in R/3.
The RESB-SOBKZ actually changes the purchase orders Individual & collective indicator based on its value.
Can any one know what is the user exit for this?
I have checked 'EXIT_SAPLCPUR_001' but it dosn't have the RESB related structure.
Thanks,
Bhaskar

Hi,
I know this is very late reply to your query but i think this is the correct answer for which you are looking for.
you were searching in a right direction...just try to see the User Exit EXIT_SAPLMEPI_006 on R/3 side in which you will find the RESB-SOBKZ field in CP_POSITION parameter in Changing Tab,Assoicated Type = MEPI_PO in which SOBKZ field is there on 16th position.
Regards,
Saurabh

User Exits for Purchase order Header Text Validation

Hi Experts,
I need user exit for validate a Long text in Purchase order header data for a Particular Doc type.
We are using 4.6 B so badi is not available .
So pls tell me user exit for the same or any other method as i was unable to find user exit for this scenario.
Note : This valiadation should trigger whhile creating PO.
Warm Regards
Santosh Kumar
Edited by: Santosh L on Mar 19, 2010 9:58 AM

i have used concept of global memory through call stack

CIF User Exit for Purchase Order CIFPUR01

Hi All,
I had couple of questions related to the way CIF user Exit CIFPUR01 is called whenever there is a change in txn data related to Purchase Orders on R/3 side.
I could see that the User Exit is called only when I completely deactivate the Integration Model using CFM3, and then reactivate the same using CFM3. If I generate a new model using CFM1 and then activate the newest version using CFM3 (without deactivating the earlier version), the system doesn't call the User Exit and this is an issue because the custom code for some calculation logic that we have defined is never called !
Additionally, whenever the change in Purchase Order is done (say to the Quantity, Delivery date etc.), the User Exit is not called when change is done via ME22N and given that Integration Model is active.
Is this the correct behavior?
Any thoughts on the above behavior would be highly appreciated.
Thanks in advance,
Regards,
Prashant

Hi Vikas,
Thanks for your suggestion.
I had already tried that by putting the break points in the include of the User Exit and the control of the program didn't enter the User Exit code when I generated and activated new version of the Integration model (CFM1 followed by CFM3).
The control enters the User Exit code only when I completely deactivate the existing Integration model and then reactivate.
Below are the scenarios which explain my point.
Scenario 1:
1. Completely deactivate the existing Integration model using CFM3.
2. Put the break point on the user exit code.
3. Generate the new version of Integration model through CFM1.
4. Activate the new version through CFM3. In this case, the control goes to the user exit code and does the calculation specified by us. This is correct and works as expected.
Scenario 2:
1. The Integration model is already activated and I put the break points in the User exit code.
2. I regenerate the new version of Integration model via CFM1.
3. I activate the new version through CFM3. In this case, the control DOES NOT go to the User exit code. This is not the expected behavior.
Scenario 3:
1. The Integration model is already activated and I put the break points in the User exit code.
2. I change the PO qty for existing Purchase order.
3. The change is immediately transferred to APO as expected. The control doesn't get transferred to user exit code. Thus the custom calculation in the INCLUDE of the user exit is not done and hence custom qty is not updated in APO.
Please let me know if you would need more clarifications.
Thanks,
Prashant

User exit for Purchase order

Hi,
We are creating a PO with 2 Purchase requisitions each having 5000/-INR. while creating the purchase order we changed the qty then net value becomes 12000/-INR for both PR's, so the difference is 2000/- which is 10% greater than actual net value that is 10000/-.
while saving the purchase order we need to rise one error message why means the difference value 2000/- is greater that 10%.
For that we need User Exit and any example code.
Thanks.

Hi Deepak,
Use this Badi. THis will be called at the time of saving PO. U can validate according to your requirement.
Sample coding:
METHOD if_ex_me_purchdoc_posted~posted .
      LOOP AT im_ekpo INTO lv_ekpo WHERE LOEKZ NE 'X'.
        SELECT * FROM qinf INTO lv_qinf WHERE matnr     = lv_ekpo-matnr
                                          AND lieferant = im_ekko-lifnr
                                          AND werk      = lv_ekpo-werks.
          IF sy-subrc = 0.
            IF im_ekko-bedat > lv_qinf-frei_dat.
              MESSAGE e000(zamq) WITH 'Vendor is not released by quality for material ' lv_ekpo-matnr.
            ENDIF.
          ENDIF.
        ENDSELECT.
      ENDLOOP.
ENDMETHOD.
Regards,
Sudhakar.

User Exit for Purchase Order Release.

Hi Friends,
I am searching for a user exit which should trigger at the time of Purchase Order release in ME29n transaction.
If anyone can help me for the same....!!!
I need the exact exit which triggers at the release of PO....
Points will be rewarded for the needful replies.
Regards,
Mandeep.

hai Mandeep Singh,
I am Genaralising This For U.
It Is ver EASY Procees.
Just Go To SE84
Give The PRogram Name Or PAckage name In Which ME29n is present.
Then Click On Display.
Then Click On Enhancements.
Then U will Get USer Exits Aswell As BADI 's
IF Found helpful Reward.
Regards
Eshwar

User exit for Purchase order & Purchase requisition.

Hi,
I need the user exits/BADIs/BTE in the following events.
       1) Just before saving Purchase requisitions and After saving purchase req ( Create and Change)
      2) Just before saving Purchase Order and After saving purchase Order   ( Create and Change)
Regards,
Ganesh Nama.

Hi Experts,
I want to change delivery date in PR while creating purchase requisition ME51n.
Means need to add 7 days in delivry date field when ever it is todays date (sy-datum).
Please suggest suitable badi or EXIT.
I tried in BADI..ME_PROCESS_REQ_CUST... in PROCESS_ITEM methode
data : preqdata type mereq_item,
          v_lfdat    type sy-datum.
          prereq_x   type   mereq_itemx.
    preqdata = im_item->get_data( ).
if preqdata-lfdat = sy-datum.
prereq_x-lfdat = 'X'.
call function 'CALCULATE_DATE'
   exporting
     days              = '7'
     months            = '0'
     start_date        = sy-datum
   importing
     result_date       = v_lfdat            .
preqdata-lfdat = v_lfdat.
call method im_item->set_datax( prereq_x ).
call method im_item->set_data( preqdata ).
endif.
But systems is ignoring thi change and again coming in same badi ..so in loop.
Please tel any other way to make change is delivery date field.
Thank you.....!!!!
Nilesh.

Problem with User exit for Purchase Order creation/change

Hi Everyone,
I have a requirement where I have to implement an enhancement for the standard transaction(ME21N/ME22N). I need to modify a particular field of the item table (EKPO) based on a few comparisons from the header values (After save of PO). I am using the enhancement MM06E005 and its corresponding exit EXIT_SAPMM06E_013. While debugging I notice that the value is getting changed; but as soon as the control comes out of the FM, the change is not being reflected. Hoping to find a solution for this.
Thanks & Regards,
Indudhar P.G

Hi Guys,
Now I am using the BADI "ME_PROCESS_PO_CUST". But the control is not stopping at the method even though I set a breakpoint. It just saves the PO after I click save. Is this because my document type of PO is Stock Transfer Order. Can I use this BADI for STO's? and moreover how do I process each item line in this method. Does "ls_mepoitem = im_item->get_data( ).
" fetch all the item lines?
Thanks and Regards,
Indudhar P.G

Sales order number user exit in Purchase order

hi,
There is a sales order number in Purchase order(item level/account assignment/sales order no)
Now, i have to populate the SO no in orders 05.
Can any one say the user exit for populating the sales order number in PO.

Hi
Check the below exits related to purchasing in which the table EKKN is referenced
EKKN will have VBELN (sales order No) and POSNR (item of sales order)
M06B0001
Role determination for release of requisitions
M06B0001
Changes to communication structure for release of requisitions
M06B0003
Number range and document number
M06B0004
Number range and document number
M06B0005
Changes to communication structure for overall release of purchase requisitions
M06E0004
Changes to communication structure for release of purchasing document
M06E0005
Role determination for release of purchasing documents
ME590001
Grouping of requisitions for PO split in transaction ME59
MEETA001
Determination of schedule line type (backlog, immediate requirement, forecast)
MEFLD004
Determination of earliest delivery date for checking at time of goods receipt (PO only)
MELAB001
Generation of forecast delivery schedule: realization via creation profile
MEQUERY1
Enhancement for document overview ME21N / ME51N
MEVME001
Calculation of default GR quantity and over/underdelivery tolerances
MM06E001
User exits for inbound EDI messages and outbound purchasing documents
MM06E003
Number range and document number
MM06E004
Control of import data screens in purchase orders
MM06E005
Customer fields in purchasing documents
MEREQ001
Customer's own data in purchase requisitions
MM06E007
Change document for requisitions when converting into POs
MM06E008
Monitoring of contract target value in case of release orders
MM06E009
Relevant texts for "Texts exist" indicator
MM06E010
Field selection for vendor address
MM06E011
Activation of requisition block
MM06L001
Exits for determination of ratings in vendor evaluation
MMAL0001
ALE source list distribution: outbound processing
MMAL0002
ALE source list distribution: inbound processing
MMAL0003
ALE purchasing info record distribution: outbound processing
MMAL0004
ALE purchasing info record distribution: inbound processing
MMDA0001
Default values for delivery addresses
MMFAB001
User exit for generation of releases
MRFLB001
Control items during release creation
LWBON001
Enhancement of LIS update through extension of the communication structure MCKONA (business volumes and rebate income)
LWBON003
Change settlement data for end-of-period rebate settlement before creation of settlement documents
LWSUS001
Customer-specific source determination in Retail
LMEXF001
Conditions in purchasing documents without invoice receipt
LMEKO002
Enhance communication structure KOMP for price determination
<b>Reward points for useful Answers</b>
Regards
Anji

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 Production Order status

Hi all ,
Pl tell me about the : user exit for Production Order status
( i want CLSD status after settlement of the Production order .)
regards,

Hi,
for production order you have exits PPCO0001 - PPCO0023. In transaction SMOD you can see the documentation for all this exits. Actually I think exit PPCO0007 could be a possiblity for you. This exit is called by saving the order.
But maybe it would be better for you to use a special status profile? A user status is set if settlement status is set.
Also BADI WORKORDER_UPDATE could be interessting for you.
Regards,
Sabine

USER EXIT FOR CHANGING POSTING DATE IN THE MATERIAL DOCUMENT

Hi,
Pls advise any USER EXIT FOR CHANGING POSTING DATE IN THE MATERIAL DOCUMENT.
Regards,

Hi,
There is another user exit for updating material document data Upon posting is MB_CF001
I hope this will fullfill you.
Prem

User Exits for Purchase order & requistion to control Material description

Similar Messages

Maybe you are looking for