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

Similar Messages

User exit for Internal Order SaveReplica or ALE/IDOC

Hi,
We're currently copying back internal orders from our PRD environment into QAS using the class method InternalOrder SaveReplica via the distribution model in BD64.
We've extended table AUFK to include some custom fields and are populating it nicely via the user exit provided. However, we want to include these values when we replicate the data back in our QAS environment.
The BAPI for method CREATE contains the "EXTENSIONIN" table so I think I know what to do there, but we are using SAVEREPLICA which doesn't offer any extra fields.
What is the best way to copy this data back into QAS?
Would it make sense to put a user exit RFC call in the QAS system to populate the values after reading them from the PRD system at the time of saving?
I can't find any user exits. We are doing this based off of change pointers.
Would you recommend using basic ALE, doing an extension to idoc type internalorders01 or something?
Thanks for any suggestions.

Hi,
usage of specific combinations of internal orders + cost elements:
Create FI-validation rule (T-code OB28 or GGB1) using BSEG-HKONT, BSEG-AUFNR for call-up point 2. Assigne this rule to the comp. code(s) needed.
Best regards, Christian

User Exit for Internal Order

Good day,
What is the transaction code to search for user exit?
Also, what possible solution we can use in order to limit the use of order to specific cost element only, meaning 1:1 ratio of cost element against Internal Order, that during transaction such as FI posting (F-02) or MM transaction during PR creation, warning or error message will be prompted when incorrect IO or GL account has been used.
Appreciate any feedback.
Thanks,
Rod

Hi,
usage of specific combinations of internal orders + cost elements:
Create FI-validation rule (T-code OB28 or GGB1) using BSEG-HKONT, BSEG-AUFNR for call-up point 2. Assigne this rule to the comp. code(s) needed.
Best regards, Christian

Screen/ User Exit for Internal Order Master Data

Hi,
I would like to one more field in Internal Order Master Data in TC KO01. I know the Table AUFK and i know there is one Include Structure (CI_AUFK). but i dont know how to add the field in that.
if you go to Screen Exit COOPA003. There is a Structure like CI_AUFK Structure there is no Calling screen in SMOD.
Can anybody please let me know how to do that?
It's really really very urgent.
your help would really appriciate.
Thanks,
Dhaval Shah.

Hi Chandra,
Thanks for the reply, can you please let me know from which TC i have to do. and i will be really appreciate your help if you write down the whole process.
Because i am aFunctional Person and i am using this Screen Exit for the first time so i'll be really thank ful to you.
Thanks,
Dhaval Shah.

User Exit during Sales Order Creation - New Line Item needed

I have a situation during the process of sales order creation. If a Material in a line item has say 27 EA and the Base Unit is EA. But the Sales Unit is CSE. Then whenever the user enters 27 EA and presses enter he should get two line items.
The first line item needs to convert to maximum number of CSE posible and the rest will be the second line item with the remaining EA. The order isn't important but that is what is needed. Question is how do I approach this problem and code my user exit accordingly and where do I code it.
I was looking at SAPMV45A and saw the program MV45AIZZ which is meant as a user exit for any PAI event handling. If anybody has encountered this kind of requirement can you please share your view on this.
I will definitely reward points for useful answers.
Clark

Hello Mahendra
The requirement is as follows :
PART 1:
Sales Order Enter:
1. When a line item is entered on a sales order (VA01 or VA02), at enter, check the sales unit of measure (VBAP-VRKME).
 Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
 Do not check items where VRKME <> EA
2. If VRKME = EA, go to MARM for MATNR.
3. Go to record where alternate unit of measure (MEINH) = CSE, get the value from the numerator field (UMREZ).
4. Divide the order quantity (VBEP-WMENG) by UMREZ.
5. If the result is greater than 1.0, the customer has ordered more than one case and a new line item needs to be added to the sales order for the case quantity.
6. Add a new line to VBAP for the same material with the case quantity. If not a whole value, the remainder of eaches (bottles) should update the qty on the first item on VBAP.
 Part 1 is relevant for order types ZCA, ZOR, ZSO, RE, ZSM
PART 2:
Batch Job to run prior to the Delivery Due List:
1. Read VBUK for Delivery Status (LFSTK) = A (delivery not processed). Get all of the document numbers (VBELN).
2. Go to VBEP for those document numbers to get the goods issue date for the order. There will be many records in VBEP for the same sales order. Look at all orders with a goods issue date (WADAT) of next day.
3. Go to VBAK for those document numbers to see if there are multiple sales orders for the same Sold To party (KUNNR).
4. For customers who have more than one order in VBAK, search all line items (for all orders). If there are no duplicate materials across sales orders, do nothing.
 Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
 Do not check line items where reason for rejection (VBAP-ABGRU) is not blank
5. If there are duplicate materials, go through the same logic as in part 1. If the quantity across the sales orders adds up to greater than one case, add the appropriate quantity to a new line item on the first sales order. If there is a remainder qty, update the line item on the first sales order with this qty. In this case, the quantities on the second sales order needs to be closed out with a reason for rejection code of 50, Line Item Consolidation. If there is no remainder, update the qty on this item directly.
 Part 2 is relevant for order types ZOR, ZCA, ZSM
 This batch job will have to be run manually for Day Pick orders. The end of this program should automatically kick off the delivery due list for Day Pick orders, shipping condition 02.
Business Justification:
The business requires that like order line items be consolidated to one line item prior to the order going to the warehouse for picking. This will aid in picking at the warehouse as well as result in the customer invoice not reflecting more than one line item for the same material. In the case where the customer has truly ordered more than a case, i.e;, 1 case, 2 bottles, the documents in SAP will still reflect 2 lines.

Required a user Exit After Transfer Order Number is genarated?

hi
guys
I need a userexit when ever the Transfer order is generated i need to call the form .can any one help me on these
Thanks in advance
Moderator Message: First help yourself by doing some R&D. If you do not stop asking such lazy questions, then we will have to delete your User ID.
Edited by: kishan P on Dec 8, 2010 11:14 PM

Hi,
Check the enhancement PPCO0007:Exit when saving production order.
Exit is EXIT_SAPLCOZV_001
Thanks,
Ramakrishna

User exit in sales order to add new item condition

Hi,
Our business requirement is to add new item conditions in an order (VA01/VA02) using ABAP coding. Has anyone done this before?
I'm thinking of using USEREXIT_NEW_PRICING_VBAP in MV45AFZB ?
Thanks.
Edited by: William Lawlor on Jul 8, 2008 12:19 PM

Hi,
This exit USEREXIT_NEW_PRICING_VBAP in MV45AFZB is used only to determine or not a new price calculation according to a modification of specific field (ex : if shipping condition is changed, then new price determination).
To add new condition type, you can used requirement in pricing procedure (V/08) with condition formula.
What is the condition to add this new condition type ?
Regards,
Lionel

User-exit to copy collective number from sales order to purchase order

Hi,
Can any one help me which user-exit/BADI is used to copy collective number from sales order to purchase order? please help me.
Thanks,
Alka

hi
copy control would be the better option to choose.. but still u can a give a search in list below and opt for the right one..Refer to the link below..
http://www.planetsap.com/Userexit_List.htm
User exits for Sales order
1USEREXIT_DELETE_DOCUMENT
2USEREXIT_FIELD_MODIFICATION
3.USEREXIT_MOVE_FIELD_TO_VBAK
4.USEREXIT_NUMBER_RANGE
5.USEREXIT_SAVE_DOCUMENT
User exits for billing
1.USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
2.USEREXIT_ACCOUNT_PREP_KOMPCV
3USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
4USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Reward if Useful
Thanx & Regards..
Naren..

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
Reward points for useful Answers
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 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: 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

User exit in sales order

Hi All,
I want to know if there is a way (user exit) that could look at the Sales Order Type , particular Item Pricing Condition and Ship-to party State and set the materialu2019s tax classification (VBAP/TAXM1) to u201C0u201D (Exempt) ?
Thanks in Advance!
Sonali.

Hi GSL,
I have put the code in the user exit, and I am able to set the tax classification indicator but I have a problem... Before setting the indicator I need to check for the Usage code of the line item (This code I am using instead of checking the Pricing condition) . I am able to read all the values of line item in VBAP structure in the user exit except for the first time this user exit is hit as soon as a line item is entered it is not picking up the Usage code. That field is blank.
But if add another line item and go into the user exit I can see the previous line item Usage code in XVBPA table.
Do you have any idea why usage code is missing in VBAP structure in the user exit or is there any other table or structure where I can get the usage code?
Please let me know if any one have any ideas.
Thanks in Advance!
Sonali.

Settlement rule for several assets but one internal order number

Hi,
I have a question regarding the settlement rule for an internal order. I have issued an internal order number to capture costs for a construction project. When the project is completed how do I update the settlement rule for the internal order to several assets all for different amounts?
For example an internal order number has collected costs of 150,000.00 for the completion of a building. When the building is complete and I want to do a final settlement of the internal order. I have one asset for land improvements for 43,000, another asset for the HVAC system for 33,000 and building costs of 74,000. When updating the settlement rule I know to create the assets and update the settlement rule with these asset numbers, but I am unclear on how to assign multiple assets with differnt amounts.

Hi ,
In the settlement rule , you need to select the Receiver as FXA and then enter the Asset number and then you will have to put the % that you want to settle to .
Like if you have 100/- Rs. total cost and you want to settle it to 2 assets in 60/- Rs. and 40/- Rs.
Then you will have to enter 2 line items in settlement rule with diffrent asset numbers and in proportion you will have to say 40 % and 60% , based on which the final settlement would happen .
So make the proportion changes in the settlement rule accordingly .
Regards ,
Dewang T

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

Similar Messages

Maybe you are looking for