User Exit in ME23n

hi,
i have to change the po such as that for a particular purchase order type there should be a fixed purchasing org.
how can i do it?

Hi,
U can use this badi-ME_PROCESS_PO_CUST.
In the method:PROCESS_HEADER,
write the foll code:
In this code, zbsart ref to ur specific po doc type & zekorg ref to ur fixed pur.org.
DATA LS_MEPOHEADER TYPE MEPOHEADER.
LS_MEPOHEADER = IM_HEADER->GET_DATA( ).
LS_MEPOHEADER-EKORG = 'ZEKORG'.
IF LS_MEPOHEADER-BSART = 'ZBSART'.
call method im_DATA->set_data
importing
exporting
im_data = ls_mepoHEADER.
ENDIF.

Similar Messages

I want a user exit for ME23N

Hi guys,
               i need a user exit for ME23N transaction,
My requirement is , if user want to add a new line item with reference to a PR, i need to validate whether PR is still Open r closed.

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
M06B0004            Number range and document number
M06B0005            Changes to comm. structure for overall release of requisn.
M06E0004            Changes to communication structure for release purch. doc.
M06E0005            Role determination for release of purchasing documents
ME590001            Grouping of requsitions for PO split in ME59
MEETA001            Define schedule line type (backlog, immed. req., preview)
MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
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
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
{h4}

Me23n user exit dynpro problem

Hello Everybody,
I'm developing a user exit for me23n transaction. I have added a tab in which i have some fields i want to fill, but i'm having the next problem.
when i enter in the me23n transaction, i push the edit button and those fields appear on editable state, but when i modify the values and push save the fields the fields continue in editable state.
I have tried to solve this problem in the catching the MESAVE action in the pai of the me22 and calling leaving to the transaction me23 with the vnew values but it's not working. Any ideas?
Here is the source code ( dynpro 111)
process after input.
field ekpo_ci-zzref_alb.
field ekpo_ci-ZZFECH_DES.
field ekpo_ci-zzeqveh.
field ekpo_ci-zzmatricula.
field ekpo_ci-zzeqtar.
field ekpo_ci-zztarjeta.
field ekpo_ci-ZZCENTRO_SER.
field ekpo_ci-ZZREF_FACT.
field ekpo_ci-ZZCLIENTE.
field ekpo_ci-ZZPAIS.
field ekpo_ci-zzdoc.
module user_command_0111.
module USER_COMMAND_0111 input.
if sy-tcode = 'ME23N' and sy-ucomm = 'METOGG'.
leave to transaction 'ME22N'.
endif.
if sy-tcode = 'ME22N' and sy-ucomm = 'METOGG'.
leave to transaction 'ME23N'.
endif.
if sy-tcode = 'ME22N' and sy-ucomm = 'MESAVE'.
sy-ucomm = 'METOGG'.
leave to transaction 'ME23N'.
endif.
Thanx

Hi,
Check the code below:
CALL FUNCTION 'READ_TEXT'
EXPORTING
id = '0001'
language = sy-langu
name = sname "sales doc is given here
object = 'VBBK'
TABLES
lines = tlines.
if not tlines is initial.
LOOP AT tlines.
CASE sy-tabix.
WHEN 1.
ztable-field1 = tlines-tdline.
WHEN 2.
ztable-field2 = tlines-tdline.
WHEN 3.
ztable-field3 = tlines-tdline.
ENDLOOP.
UPDATE ztable SET field1= ztable-field1
field2= ztable-field2
field3 = ztable-field3
WHERE vbeln = vbak-vbeln.
ENDIF.
endif.
Regards
Kannaiah

User exit in PO confirmataion

Hi gurus,
   I would like to know a user exit for PO confirmation (Save) in ME23n which is also being called when we use an IDOC for PO confirmation.
Thanks in advance,
tkg.

Hi,
    These are the available user exit for me23n.
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
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
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
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
Regards,
Himanshu

What User Exit can I use to add a cust field to PO Item overview in ME23n?

Hi,
I need help!
Does anyone have any examples of adding a new cust field to PO Item Detail screen with a user exit?
In transactions ME21n, ME22n, ME23n I need to add a new field in PO Item overview (screen 1211 of SAPLMEGUI). The new field ZZUNSPSC, has been appended to table EKPO as a 30 char field, which will be enterable/changeable on the ME21n, ME22n screens and display only on ME23n.
Which user exit I can use for the purpose of adding a new input/output field to the PO item overview on SAPLMEGUI screen 1211?
We are on release SAP ERP Central Component 5.0

Hi,
Thank you for the response. I tried this and found Badi ME_PROCESS_PO_CUST. Do you have any examples of adding a new cust field to PO Item overview screen using badi ME_PROCESS_PO_CUST? I have had little experience creating badi's, and would appreciate very much some sample code if possible.
In transactions ME21n, ME22n, ME23n I need to add a new field in PO Item overview (screen 1211 of SAPLMEGUI). The new field ZZUNSPSC, has been appended to table EKPO as a 30 char field, which will be enterable/changeable on the ME21n, ME22n screens and display only on ME23n.
Can you tell me if method FIELDSELECTION_ITEM of badi ME_PROCESS_PO_CUST the correct one to use for the purpose of adding a new input/output field to the PO item overview on SAPLMEGUI screen 1211?
Thank you for help - much appreciated,
Vicki

User exit / BADI for me23n

Dear friends,
In a purchase order, in the item detail there is "invoice" tab. for the item category B "Invoicing plan" push button appears in the invoice tab. my requirement is if we click on this button the GR non-valuated check box in the "Delivery" tab of item detailsl should be checked. Is there any user exit/badi exists to accomplish? Please advise.

Hi
you can use this BAdI
The Business Add-In (BAdI) ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order on an individual basis.
You can thus influence the dialog transactions ME21N, ME22N, ME23N, and ME29N, and the BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE.
Typical applications for this BAdI include:
Processing of own objects
Processing of additional data on standard objects
Implementation of additional checks and derivations
Change of data in standard fields
Change in field selection
Use the method for the PROCESS_ITEM, this method enables you to change the item data and check it for correctness.
Thanks & Regards
Kishore

User-exit for pass user value to item of po during creating me23n

does anyone know user-exit for change data field of item level of PO when creating ME23N?
I tried EXIT_SAPMM06E_012, but did not save with my value.

Check include
LV69AFZZ
Check this BADI
ME_PROCESS_PO
ME_PROCESS_PO_CUST
Thanks
Arghadip

User-Exit for the Me22n

Hi,
I am Mohan. I faced on Problem with the User Exit. I write the user exit for the ME21n for PO Creation. While Creation of the PO the Purchase Requition is mandatory. it is working for the ME21n. But PO creation is another two ways is there. Those are ME22N (Purchase order---> Create) and ME23N
(Purchase order---> Create) for this case also my condition applicable but it is not working for this case. How to write the Code for this. by using Sy-ucomm also. but it is not working.
Please help me.
Regards,
Mohan

Following the user exit's related to ME22N transaction.
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
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
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
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
Regards.

User exit/BADI for Return PO item delivery Address

Hi Guyz,
We have a requirement where in when a PO item is marked as return PO item(In ME21n/ME22n/ME23n We have check box at item level) and click on enter/Check/Save, In delivery address of item details we have to populate Vendor address. By default SAP populates Plant address. If we manually give Vendor number in item details=>Delivery address tab then it populates vendor address. We want to automate this functionality.
Is there any Exit/BADI which serve this purpose.
Note: We need this functionality for few doc types(i.e PO doc type should also be available in the exit).
Any ideas could be really helpfull.
Thanks,
Vinod.

Hi,
there are some user-exit & enhancements....
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
Some BADI s:
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

User exit/ BADI ME*N

Hello,
first the situation and then my question.
I have to implement a search help exit on knttp. I know the search help and have implemented the exit.
Know i need proccesing data in the exit of the purchase.
For example:
I start ME22N,
then i push F4 on KNTTP in position screen.
Then i have to check the field BSART in header screen to decrease the result of search help with a condition on BSART.
my opinion for a good solution is to find a user exit or badi in the process of displaying the purchase and set a static attribute of a new implemented Z class. To get this parameter in searchhelpexit create an instance of this class and get this attribute.
The release is 4.6C so i can't implement an enhancement point.
At time of Badi processing ME_PROCESS_PO_CUST - subscribe there are no purchase data in access.
I need the information of the purchase header at the time of showing this purchaseorder, and when you change the purchase order.
This changes have to be implemented in the enjoy transactions ME21N,ME22N, ME23n, ME51N,ME52N, ME53N.
Thank you in advance.
Best regards,
Dennis
Edited by: Dennis Goerke on Dec 8, 2008 3:33 PM

My Problem, was i have no information about the purchase order in the searchhelp exit so i can't process a check on the field BSART.
But i have found two badis for my problems.
ME_PROCESS_REQ_CUST
and
ME_PROCESS_PO_CUST
There is the Method OPEN, which is execude at opening the purchase or requisision.
There i can cast the header data and write a static attribute.
Then i can create an object in search help exit to access the attribute, so i can do a check on BSART in this search help now.
Thanks for your answer.
best regards, Dennis

User exit for check/save/hold in Purchase order

>The client requirement is like this :-
>The client has development a Order Approval Form process and want the user to create all the purchase orders having value all inclusive value of Purchase order above Rs. 300000/-.
>The user should not be able to save/hold/modify any purchase order above Rs. 300000/- in normal SAP through tcodes ME21N, ME22N, ME23N.
>For this we need to use a user exit and flash an error message that PO value is above Rs. 300000/-, hence please process the purchase order in OAF.
>Can any one please provide details of which user exit to use for the above scenario.
>Thanks in advance
>AJ

BADi:ME_PROCESS_PO
Method: PROCESS_HEADER
PROCESS_ITEM
Or
BADi:ME_PROCESS_PO_CUST
Method: PROCESS_HEADER
PROCESS_ITEM
Call your ABAPer to do the same.

User exit function module include how to write the code

hi all,
i am creating user exit for ME22N using this enhance MM06E005 .
in this i created subscreen and set some fields .
that data has to be stoe in EKPO.
inside the include i have to write the logic plz guide me how to follow .
once i enter it will store on wish internal table and wish internal table to shall i move to EKPO .
If Tcode is ME23N how to display data in disable mode.
Regards,
Hari.

This is the code inside the function module .
once i enter data in custom field the below wish table it will store.
FUNCTION EXIT_SAPMM06E_016.
""Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(I_EKPO) LIKE EKPO STRUCTURE EKPO
*"     VALUE(I_AKTYP)
*"     VALUE(I_CI_EKPO) LIKE EKPO_CI STRUCTURE EKPO_CI
*"     VALUE(I_BSTYP) LIKE EKKO-BSTYP
*"     VALUE(I_NO_SCREEN)
*"     VALUE(I_LFA1) LIKE LFA1 STRUCTURE LFA1
*"     VALUE(I_LFM1) LIKE LFM1 STRUCTURE LFM1
*"     VALUE(I_EKKO) LIKE EKKO STRUCTURE EKKO
*"     VALUE(I_REKPO) LIKE EKPO STRUCTURE EKPO OPTIONAL
*"     VALUE(I_KEKPO) LIKE EKPO STRUCTURE EKPO OPTIONAL
*"     VALUE(I_AEKPO) LIKE EKPO STRUCTURE EKPO OPTIONAL
*"     VALUE(I_REBAN) LIKE EBAN STRUCTURE EBAN OPTIONAL
*"     VALUE(I_MT06E) LIKE MT06E STRUCTURE MT06E OPTIONAL
*"     VALUE(I_EINA) LIKE EINA STRUCTURE EINA OPTIONAL
*"     VALUE(I_EINE) LIKE EINE STRUCTURE EINE OPTIONAL
*"     VALUE(I_EKPO_OLD) LIKE EKPO STRUCTURE EKPO OPTIONAL
*"     VALUE(I_KOMP) LIKE KOMP STRUCTURE KOMP OPTIONAL
*"     VALUE(I_ENJ_CALL) OPTIONAL
*" TABLES
*"      TEKPO STRUCTURE BEKPO OPTIONAL
*"      TEKET STRUCTURE BEKET OPTIONAL
*"      TEKKN STRUCTURE EKKNU OPTIONAL
*"      TKOMV STRUCTURE KOMV OPTIONAL
INCLUDE ZXM06U41 .
ENDFUNCTION.
inside the INCLUDE ZXM06U41 . i writen this code
*& Include           ZXM06U41
DATA :
      FS_EKPO TYPE EKPO_CI.
IF ( SY-TCODE EQ 'ME22N' OR SY-TCODE EQ 'ME23N'
      OR SY-TCODE EQ 'ME22' OR SY-TCODE EQ 'ME23' ) .
LOOP AT TEKPO.
   IF ( TEKPO-EBELN EQ i_EKPO-EBELN
        AND TEKPO-EBELP EQ i_EKPO-EBELP ) .
    EKPO_CI-ZMATERIAL = TEKPO-ZMATERIAL.
    EKPO_CI-ZQUANTITY = TEKPO-ZQUANTITY.
    EKPO_CI-ZUNIT     = TEKPO-ZUNIT.
    EKPO_CI-ZPRICE    = TEKPO-ZPRICE.
    EKPO_CI-ZCURRENCY = TEKPO-ZCURRENCY.
   ENDIF.
ENDLOOP.
ENDIF.
Regards,
Hari.

BADI or User exit for PO

Hi Gurus,
I am looking for BADI's or User exits for transaction ME23n.
Exactly I am looking for BADI or user exit for the release strategy for the PO and then mailing it to th e apporover.
regards
kanishka

dear ,
check out these two badi it may be useful for your requiremrnt
ME_RELEASE_CREATE
SMOD_MRFLB001
Cheers
fareed

User exit for Po text

Hi Gurus,
My requiremnt was to write the Material data in item ( delivery date, requiremt quantity) in the text tab ( info record PO text)
When we display( Me23n) the PO.
I need the user exit or BADI so that I can put the code to dispaly the data in the text tab.
Rgerads
Dhanoo

Hi Paul,
Try BADi 'ME_PURCHDOC_POSTED'. This will trigger before saving the PO document.
Pranav

User exit or BADI while saving purchase order

Hello,
I want to use an user exit or BADI while saving of purchase order. The objective is to check the material group of the line item while saving. We don´t want to allow to save purchase orders for one material group.
Can you please guide me.
Thanks
Srinivasan

Hi
The Business Add-In (BAdI) ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order on an individual basis.
You can thus influence the dialog transactions ME21N, ME22N, ME23N, and ME29N, and the BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE.
Typical applications for this BAdI include:
Processing of own objects
Processing of additional data on standard objects
Implementation of additional checks and derivationsChange of data in standard fields
Change in field selection
you can use this BADI for checking the material group
Thanks & Regards
Kishore

User Exit in ME23n

Similar Messages

Maybe you are looking for