User exit - for ME21N, 22N, 23N - at line item level

Hi,
I want to add new text field to display the description of the MPM(material) in it.
That filed I want to add to the Account Assignment tab at item level.
How to add that field on the screen, I mean any screen exit for this?
and function module to pass the data to that field.
If anybody worked on such problem then pls. let me know.
Thanks in advance.
-- Umesh

Hi,
These are the user exits for me21n.
AMPL0001
LMEDR001
LMELA002
LMELA010
LMEQR001
M06B0001
M06B0002
M06B0003
M06B0004
M06B0005
M06E0004
M06E0005
ME590001
MEETA001
MEFLD004
MELAB001
MEVME001
MM06E001
MM06E003
MM06E004
MM06E005
MM06E007
MM06E008
MM06E009
MM06E010
MMAL0001
MMAL0002
MMAL0003
MMAL0004
MMDA0001
MMFAB001
Regards
praveen

Similar Messages

Screen exit for ME21N/22N/23N

Hi All.
I have created all the subscreens available for enhancement MM06E005 (sub. scr. 0101, 0111, 0201, 0211, 0301 and 0311) , and have put a text inside each subscreen. All I want so far is to see this text in transactions ME21N/22N/23N, but I can´t find it. Is there any other step I should follow in order to make my subscreens show up in those transactions?
I have followed everything I could find in every topic in this forum, but I still can´t see my subscreen and the texts inside it.
Any help will be much appreciated, and points will be given to helpful answers.
thanks a lot in advance.

did u activated the project for which u assigned the exit.
you can check the exit directly in
SMOD.
give the exit name and press test.
check that u get u r requirement.
regards
santhosh reddy
reward if useful

Screen exit for Service entry sheet at line item level

Hi,
We would like to add some custom fields at service entry sheet at line item.
A new tab to be introduced with custom fields at serive entry line item level.
Any idea which screen exit can be use? or
what is the way to find the screen exit?
Regards,
Sandeep

Hi Sandeep,
You can try to use the user defined fields in table ESLL
ESLL-USERF1_NUM   User-Defined Field
ESLL-USERF2_NUM   User-Defined Field
ESLL-USERF1_TXT   User-Defined Field
ESLL-USERF2_TXT   User-Defined Field
or develop a custom solution with the help of customer enhancement
SRVDET (transactions SMOD, CMOD).
You should use EXIT_SAPLMLSP_030 to transfer values.
Regards,
Edit

User exit for delivery tab of PO line item?

Hi guys,
i want to impose checking on under delivery tolerance field present under delivery tab of PO line items.
Is there any user exit to do this??
Appropriate solution would be rewarded/
Regards,
GURU

Check Enhancement - MM06E005 - Exit EXIT_SAPMM06E_012
OR
Check Business Add-In ME_PROCESS_PO_CUST has method CHECK.
-Alpesh

User Exit for ME21n - Urgent

HI all,
I want to add a function module when a Purchase order is saved(ME21n), i want to know how to find user exit for ME21n & which user exit to be changed.
I want to call a function module when the user saves the purchase order, please help.
Please also let me know the step to find the user exits.
Thanxs in advance.

Hi,
Please check enhancement MM06E005 (SMOD).
Here list of User exit and BADI for ME21N .
Transaction Code - ME21N                    Create Purchase Order
Enhancement/ Business Add-in            Description
USER EXIT
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
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
LMEKO001                                Extend communications structure KOMK for pricing
LMEKO002                                Extend communications structure KOMP for pricing
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
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
M06B0003                                Number range and document number
M06B0002                                Changes to comm. structure for purchase requisition release
Business Add-in - BADI
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: Customer
ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched. Agreemnts with Rel. Docs
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_REQ_POSTED                           Purchase Requisition Posted
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
MM_EDI_DELFOR_OUT                       Enhancements for IDoc Output of SA Releases: Internal
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_EDI_ORDERS_OUT                       Enhancements for IDoc Output of Purchase Order: Internal
SMOD_MRFLB001                           Control Items for Contract Release Order
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
ME_BAPI_PR_CHANGE_01                    BAdI: Enjoy BAPIs for Purchase Requisitions (Method Change)
ME_BAPI_PR_CHANGE_02                    BAdI: Enjoy BAPIs for Purchase Requisitions (Method Change)
ME_BAPI_PR_CREATE_01                    BAdI: Enjoy BAPIs for Purchase Requisitions
ME_BAPI_PR_CREATE_02                    BAdI: Enjoy BAPIs for Purchase Requisitions (Method Create)
ME_BSART_DET                            Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR                         Facilitates Reference Characteristics in Purchasing
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
<b>Reward points</b>
Regards

Badi & User Exit for ME21N & ME22N

Hi,
        My requirement is when a Purchase order is created using ME21n or when a line is added or changed using ME22n, the system should copy the vendors tax jurisdiction to the purchase order line items jurisdiction code. I tried badi (ME_PROCESS_PO_CUST) but could not suceed. Can any one tell me if any badi or user exit available for the same???
Thanks in Advance.

hi,
Enhancement/ Business Add-in            Description
Enhancement
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
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
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
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
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
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
M06B0003                                Number range and document number
Business Add-in
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
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_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001                           Control Items for Contract Release Order
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_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
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
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)
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
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
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
No.of Exits:         35
No.of BADis:         55
Arunima

Error in badi ME_GUI_PO_CUST for ME21n/22n/23n

Dear All,
I want to add 1 tab in ME21n/22n/23n.
In that 2 field in EKKO table using ci_ekkodb include is add
For that I use badi ME_GUI_PO_CUST.
in that
MAP_DYNPRO_FIELDS
TRANSPORT_FROM_MODEL
TRANSPORT_TO_DYNP
TRANSPORT_FROM_DYNP
TRANSPORT_TO_MODEL
these method find error do to field name passing.
method IF_EX_ME_GUI_PO_CUST~MAP_DYNPRO_FIELDS.
FIELD-SYMBOLS: <mapping> LIKE LINE OF ch_mapping.
    LOOP AT ch_mapping ASSIGNING <mapping>.
      CASE <mapping>-fieldname.
        WHEN 'ZZDEPT'.                                            " Field Name
          <mapping>-metafield = mmmfd_cust_03.
        WHEN 'ZZPOGR'.                                            " Field Name
          <mapping>-metafield = mmmfd_cust_04.
      ENDCASE.
    ENDLOOP.
endmethod.
Referening **************** - Step by step guide on adding a new tab in ME21N using a BADI
Replay is appreciable.
Regards,
Pooja

First you go to se18 and read documentation of this badi.
You have to implement BAdI ME_PROCESS_PO_CUST before implementing this BAdI.
Sample code is available here.... goto->sample code->display
In case any doubt u ask..
Regards
Sreekanth

User exit for ME21N (Not functional or customer exit)

Hi Guys,
I want to get a user exit for PO as my requirement is to call custom screen before the PO is getting saved.
I have the functional exits and badi's list which will not fulfill my requirement as because on my custom screen i have cancel button.
On clicking the control needs to come back to the me21n second screen with the data entered with out order getting created.
The screen number for the second screen in ME21N is 14.
if i call screen 14 it will work in a user exit where as in customer exit(functional exit) we have limitations with the exporting and importing as so the screen number will not be recognised.
I am able to do the same calling of cust screen in Sales order creation and is sucessfull, the same should happen with PO also.
Probably if the user exit triggers at the time of syntax check i can achive my requirement rather than at save as the call back to the screen will not harm and database commits will not take place.
I also tried with all most of the enahancement points but the call screen statement is not working at any point of time which worked with Sales order exits. So i tried with making the validation fail but still by that time the PO number is getting generated and so if i try to cancel the PO before save and trying to get PO in edit mode but the sequence number is getting missed by by 1.
Please help.
Regards,
Amar.
Edited by: amar srinivas on Feb 11, 2011 10:16 AM
Edited by: amar srinivas on Feb 14, 2011 4:56 PM

Hi,
You can try it this way.
Check badi ME_PROCESS_PO_CUST , method - CHECK.
This badi/method gets triggered when the "CHeck" button and "SAVE" button is pressed.
It consists of a changing parameter CH_FAILED . Pass X to it when cancel button is hit in your custom screen.
Donot use any commit in this method. Read the documentation before doing it.

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.

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

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

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

BADI/user exit for ME21N - Warning message for "our reference" field

Dear all,
I have a problem.
In ME21N, I need to show a warning message (message w... ) when user enter an already-used-before input in "Our reference' field (EKKO-UNSEZ).
I've tried in two methods.
1. Using fm EXIT_SAPMM06E_004. But it can only works for Error message. My warning message never shows up.
2. Tried to implement classic BADI ME_PROCESS_PO_CUST, using the PROCESS_HEADER method. Got the break-point spot on, but still didn't show the warning message.
Why is my warning message always got override?
Please advise.
Thanks in advance
Ahmad

Hi Ahmad,
Check the below links:
Unable to put Warning messages in ME21N and ME22N in Exit / BAdI in ECC 6.0
Warning message in me22n check user-exit can't process?
Custome warning message in T. code me51n me52n & me21n , me22n
Regards,
Nisha Vengal.

BADI / user-exit for MD02 while creating Schedule Lines

Hi experts,
I have a problem with implementation that I'm designing.
Current situation:
While MRP run (MD02 or background) new Schedule Lines are being created in reference to MM Scheduling Agreement.
Example:
04.08.2014
SchLne
5500000415/00010
200
04.08.2014
IndReq
VSFB
200-
05.08.2014
SchLne
5500000415/00010
300
05.08.2014
IndReq
VSFB
300-
2 Schedule Lines where created - for wuantity 200 and 300.
Target:
There is a need to create more than one Schedule Line per day during MRP run. According to example there should be for example 2 Schedule Lines in 04/08 and 3 Schedule Lines in 05/08 all for quantity = 100. There is possibility to change Schedule Lines in ME38, but there is a need to make a change during creatin while MRP run.
04.08.2014
IndReq
VSFB
200-
04.08.2014
SchLne
5500000415/00010 *
100
04.08.2014
SchLne
5500000415/00010 *
100
05.08.2014
IndReq
VSFB
300-
06.08.2014
SchLne
5500000415/00010 *
100
06.08.2014
SchLne
5500000415/00010 *
100
06.08.2014
SchLne
5500000415/00010 *
100
So instead of creating only 2 Schedule Lines, MRP should create 5.
I'm looking for a BADI/user-exit to edit Schedule Lines which are to be created by MRP and change it tn reference to the needs.
I found only one BADI:
BADI: MD_CHANGE_MRP_DATA
method: CHANGE_MDPSX_MDBS
The priblem is that this method is only being executed when there are Schedule Lines which already exist.
Maybe some of you have done some extension similar to mine? Please give me advice where I should put extension.
Thanks in advance!

Dear Saravaran,
Thanks for the reply.
This will not suits to us. The provided BADI will works upto Posting the material document in transaction MIGO and it will not considered for the FI level entries.
Hope you could have understand mine requirement.
The requirement of mine is:
While doing the GR with ref to PO the material documnet will be posted and subsequently FI documnet will be generated in Background. While generating the FI document i need to manipulate the values for the G/L. So that the manipulated values will be flow into BKPF and BSEG tables.
Thanks.
Regards
Swamy

User exit for ME21N for displaying the tax code from custom table

Hi,
I have a requirement, in our system, the inforecord is not maintain for all the material and vendor combination, we have a custom table in which we have maintain the
Compnay code, Pur. Org., Vendor code Tax code, juridiction code
now we want that when a Po is created with ME21 or ME21N the tax code and jurisdiction code should be come from this table and if entry not found in this table then it should search as per the regular process like from last Po or info record. then which user exit we can use for this.
regards,
zafar

CLOSE

User-exit for ME21N: Check if outline agreement is valid (for date)

Hopefully someone has seen this before..
When creating a PO with ME21N, it is possible to create the PO with reference to an agreement that is not valid any more (Validity end field in ME33K is before todays date). No warning or error message is presented to the user.
I have a list of 38 user-exits available for ME21N, but none of them seems to focus on this problem.
I have to have EKKO-KDATE available in the exit, I think...
Exit Name (for ME21N)
AMPL0001
LMEDR001
LMELA002
LMELA010
LMEQR001
LMEXF001
LWSUS001
M06B0001
M06B0002
M06B0003
M06B0004
M06B0005
M06E0004
M06E0005
ME590001
MEETA001
MEFLD004
MELAB001
MEVME001
MM06E001
MM06E003
MM06E004
MM06E005
MM06E007
MM06E008
MM06E009
MM06E010
MMAL0001
MMAL0002
MMAL0003
MMAL0004
MMDA0001
MMFAB001
MRFLB001
LMEKO001
LMEKO002
MM06E011
MEQUERY1

Hello Helge,
Did u try using EXIT_SAPMM06E_004. This is in the enhancement MM06E004. Use the code in the exit.
tables: ekko.
data: v_date like ekko-kdate,
      ebeln like ekko-ebeln.
data: prog(30) value '(SAPLMEPO)ekko'.
field-symbols: <fs1> type any.
assign (prog) to <fs1>.
ekko = <fs1>.
*ekko-ebeln = <fs1>-ebeln.
select single kdate into v_date from ekko
             where ebeln = ekko-konnr.
if v_date < sy-datum.
   message e000(zhb).
endif.
Try this.

VA01 user-exit to modify net price of line item...

Hello Experts,
Is there a user-exit to modify the net price value of a line item upon 'ENTERING' in
VA01 transaction?
Hope you can help me guys. Thank you and take care!

Hi,
The user exits and badis for va01 tcode:
Enhancement/ Business Add-in Description
Enhancement
V45L0001
SD component supplier processing (customer enhancements)
V45E0002
Data transfer in procurement elements (PRreq., assembly)
V45E0001
Update the purchase order from the sales order
V45A0004
Copy packing proposal
V45A0003
Collector for customer function modulpool MV45A
V45A0002
Predefine sold-to party in sales document
V45A0001
Determine alternative articles for product selection
SDTRM001
Reschedule schedule lines without a new ATP check
V60F0001
SD Billing plan (customer enhancement) diff. to billing plan
V46H0001
SD Customer functions for resource-related billing
V45W0001
SD Service Management: Forward Contract Data to Item
V45S0004
Effectivity type in sales order
V45S0003
RP-relevance for incomplete configuration
V45S0001
Update sales document from configuration
V45P0001
SD customer function for cross-company code sales
Business Add-in
BADI_SD_SCH_GETWAGFZ
Scheduling Agreement: Read WAGFZ from S073
BADI_SD_V46H0001
SD Customer functions for resource-related billing
Pls. reward if useful...

User exit - for ME21N, 22N, 23N - at line item level

Similar Messages

Maybe you are looking for