User exit: save PM order

Dear all,
I'm looking for an user exit that will be actived during order save. However, it seems most exits just for check, I can not change any data.
The requirement is: if user save certain order, then field function area 'CAUFVD-FUNC_AREA' is filled automatically. This fiels in the order header.
Thanks,
Ben

Hi,
Orders
User Exits     BBPK0001
Description     Exit for determining the external procurement profile
User Exits     CNEX0013
Description     Default item category for component assignment
User Exits     CNEX0026
Description     Customer enhancement for general inspection of material
User Exits     CNEX0027
Description     Customer enhancement: Plant, storage loc. finding for comp.
User Exits     CNEX0037
Description     Check new component
User Exits     COCCA002
Description     Customer Functions for Organizational Authorization Checks (SETTLEMENT)
User Exits     COI20001
Description     Changing of person found
User Exits     COI20002
Description     Alternative procurement of HR availability data
User Exits     COOM0001
Description     Customer Functions for Overhead Percentages
User Exits     COOPA_01
Description     Customer check modules for internal orders
User Exits     COOPA002
Description     Customer function for master data maintenance - internal orders
User Exits     COOPA003
Description     User-Defined Fields in the Order Master
User Exits     COOPA004
Description     Customer function: Print order master data
User Exits     COPCP005 (see: 1, )
Description     Material Costing: User exit for material valuation (strategy U)
User Exits     CY190001
Description     Capacity Planning: Change order operation
User Exits     COZF0001
Description     Change purchase req. for externally processed operation
User Exits     COZF0002
Description     Change purchase req. for externally procured component
User Exits     CYPP0001
Description     Change sequence criteria and sequencing
User Exits     ICSV0001
Description     Display of geographic location data
User Exits     ICSV0002
Description     Automatic task determination for service notifications
User Exits     ICSV0003
Description     Partner selection
User Exits     ICSV0004
Description     Check PM object and display object information
User Exits     ICSV0005
Description     Determining reason for rejection - resource-related billing
User Exits     ICSV0008
Description     Validation of additional partner types
User Exits     IWMI0001
Description     User exits for SM/PM IDOCs
User Exits     IWO10001
Description     Create a PM sub-order
User Exits     IWO10002
Description     Customer check for order release
User Exits     IWO10004
Description     Customer check for order completion
User Exits     IWO10005
Description     Customer specific determination of profit centre
User Exits     IWO10006
Description     FCode exclusion through customer enhancement
User Exits     IWO10007
Description     Customer enhancement - permits in the order
User Exits     IWO10008
Description     Customer enhancement: Determination of tax jurisdiction code
User Exits     IWO10009
Description     Customer Check for 'Save' Event
User Exits     IWO10010
Description     Customer enhancement for determining WBS element
User Exits     IWO10011
Description     Customer enhancement for component selection
User Exits     IWO10012
Description     Priority handling on central header
User Exits     IWO10015
Description     F4 Help for user fields on operation
User Exits     IWO10016
Description     Customer enhancement to check operation user fields
User Exits     IWO10017
Description     Determine external order number by customer logic
User Exits     IWO10018
Description     User fields on order header
User Exits     IWO10020
Description     Automatically include task list
User Exits     IWO10021
Description     Automatic task list transfer when creating order from notification
User Exits     IWO10022
Description     Determine calendar from user exit
User Exits     IWO10023
Description     Service order: Change header data for advance shipment document
User Exits     IWO10024
Description     Service order: Changes to items for advance shipment
User Exits     IWO10025
Description     Finding responsible cost centre
User Exits     IWO10026
Description     User check on setting status 'Do not perform'
User Exits     IWO10027
Description     User exit: Generate user-defined settlement rule
User Exits     IWO10029
Description     Inclusion of bill of material in PM/SM order
User Exits     IWO10030
Description     Predefining the fields for the profitability segment
User Exits     IWO10031
Description     Hide personnel number in PM/SM order
User Exits     IWO10033
Description     Customer-Specific Authorization Check PM/CS Order
User Exits     IWO10034
Description     Operation status based on the status of capacity requirements
User Exits     IWO20001
Description     User exit to pass routing/task list to order
User Exits     IWOC0003
Description     PM/SM authorization check of ref. object and planner group
User Exits     M06B0002
Description     Change communication structure for purchase requisition release
User Exits     MGA00003
Description     Material Master (Industry and Retail): Number Display
User Exits     PPCO0001
Description     Application development: PP orders
User Exits     PPCO0005
Description     Storage location/backflushing when order is created
User Exits     PPCO0023
Description     Checks changes to components
regards,
Venkatesan Anandan

Similar Messages

User Exit at process order release or save

Dear experts,
Can any one help me which user exit will be useful at the time of process order release or save (t code COR1/COR2).
My requirement is to stop the process order release if there is any maintenance order is already released on that date.
Process order should not get released in between the start and finish date of PM order for the same equipment.
I could acheive this for PM side by using a user exit IWO10002, here if any process order is released for an equipment PM order cannot be released for the same equipment in between start n finish date of the process order.
Please help me out in finding the user exit for process order release / save.
Thanks in advence,
Regards,
Praveen.

Hi,
The following enhancements are available for process order management:
For order maintenance:
o   PPCO0006 to predefine entries for order header fields when creating
    an order
o   PPCO0001 to provide information at the time of saving (for
    production orders and process orders)
o   PPCO0007 to check or change header data when saving
o   PPCO0002 to add additional checks that are to take place when
    setting the deletion flag or deletion indicator
o   PPCO0003 to prevent changes in sales order items that would cause
    changes in the process order for static assembly processing
o   STATTEXT to format the status line
o   PPCO0008 to check components that have been changed or added
o   PPCO0005 to change the storage location and the 'backflush'
    indicator in the reservation
o   PPCO0013 to change the priority of the selection criteria for batch
    determination in production orders or process orders
o   PPCO0014 to restrict the selection of process orders that are
    offered when creating external relationships
o   PPCO0020 to display additional information for another tab page in
    the process order header
Regards,
Dhaval

User exit in planned Orders

Hello all.
I have been search for a user exit in planned orders that allow me to define some code in it to triger some changes. this user exit should be at time of planned order is saved.
I have already search in this forum and I found out how to find the user exits by transaction. I have tried for transaction MD12 but did not found any suitable user exit.
Does any one know any user exit that could make my life easiser
thanks
Manuel Antonio

You can try the following BAdIs:
You can use the Business Add-In (BAdI) MD_PLDORD_CHANGE to change, before posting, data from planned orders, which have been created, changed, or deleted as a result of planning a material or manual processing.
The Business Add-In allows you to fill and change fields from planned orders in the PLAF table. It also supports filling of customer-specific fields in the customer include CI_PLAFDB.
You can execute the Business Add-In in the planning run in the following areas:
Material requirements planning
Master production planning
Long-term planning
You can also carry out the Business Add-In in all applications, which execute manual planned order changes. Examples of this kind of application are:
The dialog transactions for creating and changing planned orders (MD11, MD12, MS11, MS12)
The Business Application Programming Interfaces (BAPI) for creating and changing planned orders
all applications that explicitly or implicitly create or change planned orders, for example the planning table of repetitive manufacturing, repetitive manufacturing confirmation, capacity planning, assembly order processing and so on.
Requirements
When planning a material or manually processing a planned order, you must change individual fields in the planned order or provide entries for customer-specific enhancements of the planned order structure.
Standard settings
The Business Add-In is not active in the standard.
The Business Add-In cannot be used multiple times.
The Business Add-In is not filter dependent.
Activities
To activate the Business Add-In, you must create an active implementation. To do this, choose the following path in the SAP Menu: Tools -> ABAP Workbench -> Utilities -> Business Add-Ins -> Implementation
For more information about this procedure, see the SAP Library under
Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.
Further notes
Documentation on the BAdI method CHANGE_BEFORE_SAVE_MRP
Documentation on the BAdI method CHANGE_BEFORE_SAVE_MAN
You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:
1. Choose the tab page Interface.
2. Double-click on the relevant method.
3. Click on the right mouse button and choose Component documentation.
Update Planned Orders (MD_PLDORD_POST)
Use
Application components: PP-MRP, PP-MP-MPS, PP-MP-LTP, PP-REM
Function group: M61P, M61U
You can use the Business Add-In (BAdI) MD_PLDORD_POST to further process data from planned orders, which have been created, changed or deleted through the planning of a material or as a result of manual processing.
The Business Add-In allows you to publish the created and changed data from planned orders and can be used to update customer-specific tables or to connect to information systems and workflows.
You cannot use the methods of the Business Add-In to change the planned orders themselves. The planned orders are always posted in the communicated form.
You can execute the Business Add-In in the planning run of the following areas:
Material requirements planning (PP-MRP)
Master production planning (PP-MP-MPS)
Long-term planning (PP-MP-LTP)
You can also execute the Business Add-In in all applications, which carry out manual planned order changes, for example:
The dialog transactions for creating and changing planned orders (MD11, MD12, MS11, MS12)
The Business Application Programming Interfaces (BAPI) for creating and changing planned orders ( PlannedOrder Create, PlannedOrder Change)
All applications that explicitly or implicitly create and change planned orders, for example the planning table of repetitive manufacturing, repetitive manufacturing confirmation, capacity planning, assembly order processing, and so on.
Standard settings
The Business Add-In is not active in the standard.
The Business Add-In can be used multiple times.
The Business Add-In is not filter dependent.
Activities
To activate the Business Add-In, you must create an active implementation. To do this, choose the following path in the SAP Menu: Tools -> ABAP Workbench -> Utilities -> Business Add-Ins -> Implementation
For more information about this procedure, see the SAP Library under
Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing Business Add-Ins.
Note that the Business Add-In can be used multiple times and therefore all active implementations are called and run through.
Example
The following is a possible use for the methods of this Business Add-In:
When planning a material or manually processing planned orders, you want to log the changes made to the planned orders or the triggered subsequent functions.
The subsequent processing of certain planned orders or individual data from the planned orders occurs in an external planning system. In this case, you can log the corresponding changes to these planned orders in a user-defined table during planning. Using a separate report, you can select the data from the log table and process it further.
Further notes
Methods
Update Planned Orders: Requirements Planning - POST_AFTER_SAVE_MRP
Update Planned Orders: Manual Processing - POST_AFTER_SAVE_MAN
You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:
1. Choose the tab page Interface.
2. Double-click on the relevant method.
3. Click on the right mouse button and choose Component documentation.
Regards
Ram

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 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: Put internal order number to GL item when settlement

Hi Experts,
I have a requirement to develop user-exit for internal order settlement. The current status in in standard SAP function as below:
When we settle an internal order then corresponding FI documents is generated at the same time. In the FI document there have two itmes, the first item is for GL account, and the field of bseg-aufnr is space. The second item is for ERG account, and the internal order number will fill into bsge-aufnr on this item.
Now our requirement is below,
I would like to fill the internal order number to first item also. Do we have the user-exit/enhancement/modifucation to meet this requirement?? Please kindly point me a direction. Thanks very much.

Only one exit for it check
Transaction Code - KO88 Actual Settlement: Order
Exit Name Description
COOM0003 Customer function for automatic creation of settlement rules
No of Exits: 1
Rewards if useful.....................
Minal

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 Service order release ( needed operation details as import )

Hi All,
   I need a user-exit while service order release( tcode : IW31 ) activity . I find some of the exits, but none of those not having "Operation" details , all are having only header details. Please suggest if any user-exit is available for this or BADI . I tried with badi "ALM_ME_001_ORDER" , its not triggering at all while creation of service order.
   Is there any way we can get from operation data from buffer, please suggest me the same.
Thanks in advance,
Pavan.

Hi Thomas,
   Thanks for reply. I saw the function exit which you mentioned , but it didn't have the operation details in import.
Regards,
Pavan

User exit during planned order to production order conversion

Hi,
Let me know if there is any user exit during planned order to production order production.
Regards,
Yogesh

Dear
You can try the following :
1.PPCO0001 /PPCO0007 /PPCO0012
2.BADI workorder_update
3.Check in SMOD or CMOD and enter PPC* -you will find all the related user exit
Hope this helps
Regards
JH
Edited by: Jiaul Haque on Oct 21, 2010 10:55 AM

Suggest the user exit when process order released then save

Need to update batch value from component's batch field to FG batch field. Need at the time of process order released and saved. Can you please tell me which user exit to use?

Hi,
The following enhancements are available for process order management:
For order maintenance:
o   PPCO0006 to predefine entries for order header fields when creating
    an order
o   PPCO0001 to provide information at the time of saving (for
    production orders and process orders)
o   PPCO0007 to check or change header data when saving
o   PPCO0002 to add additional checks that are to take place when
    setting the deletion flag or deletion indicator
o   PPCO0003 to prevent changes in sales order items that would cause
    changes in the process order for static assembly processing
o   STATTEXT to format the status line
o   PPCO0008 to check components that have been changed or added
o   PPCO0005 to change the storage location and the 'backflush'
    indicator in the reservation
o   PPCO0013 to change the priority of the selection criteria for batch
    determination in production orders or process orders
o   PPCO0014 to restrict the selection of process orders that are
    offered when creating external relationships
o   PPCO0020 to display additional information for another tab page in
    the process order header
Regards,
Dhaval

User exits for sales order

Dear all SAP experts,
How to find out the user exits for sales document type? Especially the user exits which are called when we save the sales order.
With best regards,
Allabaqsh G. Patil

Hi,
Also there is user exit to refresh data
USEREXIT_REFRESH_DOCUMENT
       It is always necessary to refresh user-specific data before   *
      the next document will be processed.                          *
      This can be done in this userexit.                            *
      This userexit can be used to refresh user-specific data       *
      when the processing of a sales document is finished           *
      - after the document is saved                                 *
      - when you leave the document processing with F3 or F15       *
      It may be necessary to refresh user-specific data before      *
      the next document will be processed.                          *

BADI / User Exit for APO Order transaction /SAPAPO/SNPTLB

Hi Experts,
We have a proxy interface and currently we are using FUNCTION EXIT_SAPMSNPUSER_006 for the APO Order transaction: /SAPAPO/SNPTLB.
This exist is triggering before the Order is being saved in APO and at times it is throwing an error 'Order key already exists in live cache' in the APO system.
Is there any other BADI or User exit available to Save the order in APO before the interface gets processed?, if so, plese guide me.
Thanks & Regards,
Vijaya

Hello Lakshmi,
I am having the same issue with the message "Order key already exists in live cache" in our system.
We are using the user-exit EXIT_SAPMSNPUSER_005 for UoM conversion. But we are not making any explicit proxy calls
to /SAPAPO/SNPTLB. Does the system automatically call this transaction with this user-exit?
Did you get a resolution for the issue. I would really appreciate if you can let me know how you have addressed this.
Thanks,
Ratnam

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 exit: save PM order

Similar Messages

Maybe you are looking for