Me59n

how to configure automatic purchase order based on purchase requisition can anyone explain step by step.
Failed to search properly. Locked.
Edited by: Csaba Szommer on Apr 22, 2011 7:54 AM

Hi,
For automatic PO creation from PR, follow the below setting.
1) Material Master purchasing view tick automatic PO check box
2) Vendor Master purchasing view tick automatic PO check box.
3) Maintain Source list for Vendor & Material.(ME01)
4) Maintain Purchase Info Record.(ME11)
5) Create a Purchase Requisition.(ME51N)
6) Use T.Code: ME59N & execute for PR for vendor, you will be able to create automatic PO.
Please note that during creation of PR , select check box of Source Determination in the 1st screen of ME51N
For Service Auto- PO, you need to activate Automatic Purchase order creation for Service requisitions in ML91. Create info record based on Material Group as for Automatic PO , info record is mandatory.
For more check SAP note 635511
Regards,
Biju K

Similar Messages

Wrong document type is processed form ME59N - Automatic PO creation Efected

Dear Friends,
Im facing one issue while the PO is created from Purchase requistion(ME59N).
If the purchase requisition document type is - XTB while creation of PO from ME59N the document type is taking as UB
the SPRO setting has been done for supplying plant and receving pant as - XTB but still getting the error as
Doc. type XTBshould be used for suppl. plant XXXX and receiving plant XXXX. 06 - 674 ( Msg class and No)
Could any one please help me on this.
The manual PO creation(ME21N) is perfect .
Regards
Kumar.

Hi Mauro,
Thank you for the very helpful answer, i suggested my team to impliment the OSS note.
Thanks for your help.
One similar kind of issue i am facing, i implimented one enhancement in the BADI "ME_PROCESS_PO_CUST" for checking the supplying plant.
When i processd it through ME21N ( manulaly) it's taking the right plant, But when i processed it through ME59 ( Autoamtion of PO) the Enhancement is not triggered.
ME59N is not supporting as there is no support pack ( OSS notes need to be implimented).
Coluld you please provide any helpful answer for me
Thanks for your support and Help.
Regards
Ravi.

Error during automatic po creation ME59N

Dear All,
Following errors has been shown after automatic po creation by ME59N:-
Message text Message Class Message Number
PO could not be created
PO header data still faulty MEPO 2
Enter Validity End ME 83
Enter Latest GR Date ME 83
Can delivery date be met? ME 40
Requisition could not be converted
Please suggest how to solve above .
with regards,
Pradeep Bhardwaj

Hi
From the messages it seems that system is expecting a Validity end date at PO header & Latest GR date at item level.
Do you have these two fields as required in the PO??
If these are required fields then you need to have process to populate them automatically (Programatically) to resolve the error.
Thanx
Prasad

ME59N Automatic PO creation

When i try to create PR into PO with Tcode ME59N....
error it is showing Requisition could not be converted
I checked in Both Material master and vendor master also i have selected Automatic PO check box..
Pls guide me....

Hi,
Please follow the below steps to create automatic PO using ME59N transaction
1. In material master Automatic PO check box to be checked (Already done in our case)
2. In vendor Master under purchasing view check the box Automatic Purchase order (Already done in our case)
3. Maintain the list of sources available for the given material with plant combination
4. Maintain the Purchase Info record for all the vendors which are maintained in the above Source list with the material combination
5. While creating the PR under source of supply tab click on Assign source (We are doing this as we have multiple sources for our material) . Save the PR
6. Execute the transaction ME59N and provide the source (vendor number) and plant . System will automatically create a Purchase order for the vendor.
Do follow the above steps and let us know if you are able to create a PO
Regards
Pavan

Error during automatic PO creation by PR (ME59N)

Dear All,
Following errors has been shown after automatic po creation by ME59N:-
Message text     Message Class Message Number
PO could not be created
PO header data still faulty        MEPO               2
Enter Validity End        ME              83
Enter Latest GR Date        ME              83
Can delivery date be met?        ME              40
Requisition could not be converted
Please suggest how to solve above .
with regards,
Pradeep Bhardwaj

Hello,
to check the errors issued I suggest to try to create the PO converting the PR from transaction ME21N.
I guess that some fields, mandatory for the PO creation, were not filled in the Purchase Request and could not be determined in any different way. If you can't maintain them on the PR you should set them as optional, if possible, in the customizing for Screen lay-out of transaction ME59N, under "Materials Management --> Purchasing --> Purchase Order --> Define Screen Layout at Document Level".
Hope to be useful.
Best regards,
Andrea

Automatic PO creation from PR ME59N

HI,
We are creating PO's after the PR is duly approved as per the relaese strategy.
Can we use automatic creation functionality to reduce the manula inputs and errors.
regards,
ab

Hi,
Yes you can create Automatic PO from PR Via ME59N.
but for this you have to check Automatic PO in both purchasing View of Material Master and Vender master .
also maintian Purchse Info Record with T code ME11 for value and tax code and
source of Supply in ME01 and assign source of Suppy in PR and release PR and
go to ME59N to create automatic PO with that PR.
But remember that you can not put additional Conditions in PO for E.g. ur fright charges and Packaging and forwarding charges via automatic PO.
Regards,
Pardeep Malik

ME59N as background job

Hi Gurus,
We want to have certain pruchase reqs automatically converted to POs via ME59N and we want to set it up as a background job. I will have filled certain fields on ME59N. How can this be acheived?
Thanks
Anusha

Create and schedule a background job in SM36 for program RM06BB30 (ME59N) with a variant of ME59N that selects the requisitions you wish to convert to orders. You can schedule this job to run once or periodically depending on your requirements.
Regards.

How to change the document type while creating a PO by ME59N

Hi,
I have 2 groups of PR's, for group one the document type is picked as NB and PO is created and for the group 2 it should pick as XYZ and PO should be created using ME59N tcode.
How to change the document type for group 2 in ME59N? Which user exists to use to change the document type while creating PO in ME59N?
Can any one suggest me.

Hi,
There a config area, where you can define default PO doc types for a particular Pr doc type. If you maintain the settings properly there, then your requirement can be fulfilled.
SPRO->IMG->MM->Purchasing->Purchase requisation->Define doc types.
This will serve your purpose.
Thanks,
Srinu

ME59N - Conversion of Purchase Req to Purchase Order

Hi Gurus,
I am trying to convert PR to PO through ME59N tcode.
The vendor as cource of suppply is ERS vendor.
When I do the conversion, I am getting an error " Tax code must be maintained for ERS vendor' . How can I interfere in this automatic conversion.
Can anyone throw smoe idea , how to skip this error and convert the PR to PO by ME59N
Regards
Raj

Hi,
Add Tax code for material plant vendor cobination in Info record in ME12 t.code
Regards,
JS

Tax code not flowing while ME59N in case of conversion of service PR to PO

Hello,
I am trying to create automatic PO using ME59N for Service PR. But system is showing an error Tax code is not found. In my case I cannot create Contract. I have to maintain Service conditions in ML33 from which the Service amount will flow. Everything else is working fine, except that I cannot bring the tax code. My vendor is ERS vendor. So the tax code is manadatory and I don't want to remove the check.
Please suggest how to bring the tax code automatically? I have tried creating inforecord using the material group of the service. But it has not worked.
Please help. Useful suggestions will be awarded.

I have found a solution in standard itself

Badi or User Exit to close PR in ME59n

Dear All,
I have implemented a enhancement for ME59n(EXIT_SAPLME59_001). Here we club the PR which has same material, vendor, date..... And add the quantity to first PR quantity and create a single PO against all the PR.
PR No              Material                vendor                     date                Quantity
1                      ABC                   XYZ                     26.05.2011           100
2                     ABC                    XYZ                     26.05.2011           200
3                    ABC                     XYZ                     26.05.2011           300
Assume the above example and here it will sum up the quantity i.e. 600 total and put against PR 1 and will remove the PR 2 and 3 from the internal table. Now PO will create for PR 1 with 600 as quantity and standard SAP will mark the PR 1 as closed.
Now we have removed PR 2 and 3 from the internal table during run time after adding the Quantity. But I need to mark PR 2 and 3 as closed.
Please let me know if there is any right Exit or Badi to achieve it or other way.
Thanks in advance.
Arun Kumaram.

Here are the user exits you can look to http://www.sap-img.com/ab038.htm to and
AMPL0001            Subscreen usu.p.dat.adicionales p.lista piezas fabr.autoriz.
LMEDR001            Ampliaciones programa de impresión
LMEKO001            Ampliar estructura comunicación KOMK para determinar precios
LMEKO002            Ampliar estructura comunicación KOMP para determinar precios
LMELA002            Transfer.núm.lote de aviso entrega al contabilizar una EM
LMELA010            Entrada aviso de entrega: toma de datos posición de IDOC
LMEQR001            Exit de usuario p.determinación fuente aprovision.
LMEXF001            Condiciones en documentos de compra sin recepción d.factura
LWSUS001            Determinación fuente aprov.específica cliente en el comercio
M06B0001            Determinación de funciones p.liberación solicitud de pedido
M06B0002            Modific.estructura de comunicación p.liberación solic.pedido
M06B0003            rango de números y número de documento
M06B0004            rango de números y número de documento
M06B0005            Modif.estruct.comunicación p.liberación general solic.pedido
M06E0004            Modif.estructura comunicación p.liberación docs.compras
M06E0005            Determinación funciones p.liberación doc.compras
ME590001            Agrupación solicitudes de ped.p.partición de pedidos en ME59
MEETA001            Determinar clase de reparto (atrasos, nec.inmed., previsión)
MEFLD004            Determ.fe.entrega más temprana p.verif.seg.EM (sólo pedido)
MELAB001            Crear orden entrega p.suministro: Realiz.plan de transmisión
MEQUERY1            Ampliación para resumen de documentos ME21N/ME51N
MEVME001            Cálculo ctd.prop.entr.mercanc.y tolerancia exc./faltas sum.
MM06E001            Exit de usuario para EDI: entrada/salida documentos ventas
MM06E003            rango de números y número de documento
MM06E004            Control pantallas datos import. en el pedido
MM06E005            Campos cliente en documento compras
MM06E007            Doc.modif.p.solicitudes pedido durante conversión a pedido
MM06E008            Control del valor previsto p.pedidos p.orden de entrega
MM06E009            Textos relevantes p.indicador "Existen textos"
MM06E010            Selección de campos para la dirección del proveedor
MM06E011            Activación bloqueo de solicitud pedido
MMAL0001            ALE distribución libro de pedidos: tratamiento salidas
MMAL0002            ALE distribución libro de pedidos: tratamiento entradas
MMAL0003            ALE distribución registro info compras: tratamiento salidas
MMAL0004            ALE distribución registro info compras: tratamiento entradas
MMDA0001            Propuesta de direcciones suministro
MMFAB001            Exit usuario para creación orden entrega
MRFLB001            Controlar posiciones p.creación orden entrega

SO is getting updated from PO thru ME59N

Hi All,
We have an issue here , our client is creating automatic PO from ME59N , but to the surprise he found that a new line item has been inserted into the corresponding sales order for which the PO was created.
The sales order had only 1 line item initially -- with some Purchase req no
Later after running ME59N, a new line item got inserted in the Sales order
But PO got created with single line item which was initially present in SO.
Can any one help me, why the SO is getting updated with the new line item?
or where can i see this issue.
Moreover this is issue is coming in the producion server , so i cant debug the issue as well.
Edited by: kishan P on Sep 17, 2010 11:39 AM

Hi,
I have a feeling there is some configuration which controls if (and any) changes should get copied back to related documents - you might like to discuss this with your functional consultant.
Failing that, run a SQL trace and see if the update is occurring as a result of a customer enhancement - if it's the sales order being updated then look out for the VB* table updates in the trace.
Regards, Andy

Automatic PO from PR through ME59N

Dear All,
While converting the PR automatically to PO with ME59N, I am getting message "No suitable PR found". Where as the PR contains the open items and the same PR can be converted in to PO thourgh ME57 (manually). Please suggest me what could be the problem and how to resolve it.
Regards
sachin

Hi ,
1. Maintain Auto PO in Material master Purchasing view
2. Select Automatic purchase order in Vendor master- Purchase data
3. Maintain info-record with tax-codes
4. Create a PR through ME51
5. Assign the same in ME57
6. Execute in background using Tcode ME59.
PO will be created automatically.
Hope this helps you.
Regards,
Archit

ME59N - Customize it to change POs? User Exit?

Hi all,
We are using the automatic PO creation program (ME59N) to convert approved requisitions with a fixed source of supply to purchase orders.
We have scenarios at our company where, after the PO is created and sent to the vendor, a change is to be made, which is usually a new line item that is required. Our process dictates that every new request must go through a requisition and approval process before it can be converted into a PO or added onto an existing PO. In this scenario, the user will create a new requisition or add a line item to an existing requisition, and upon approval, will manually drag the new requisition line into an existing PO (we do not want to issue multiple POs to the vendor, we would like to issue a change order instead when it makes sense to).
Since me59n runs a couple times a day, the user may sometimes not have time to manually drag the requisition into the existing PO, and when this happens, the system creates a brand new PO and sends it off to the vendor. This is obviously confusing as the new line item really belongs on an existing PO that was issued to the vendor.
We were wondering if it was possible, to update the me59n program, to check if the requisition should be included on an existing PO, rather than creating a new PO (we would have the user enter the existing PO# in the requisition in the requirement tracking number field). If the program found a reference to a PO on the requisition line item, it would then find the relevant PO and add the requisition line as a new line item in the existing PO (i.e. change the PO), rather than create a fresh new PO.
Obviously this is not standard in ME59n, as ME59n would create a new PO with the requisition. Is this at all possible via a user exit or badi? Has anyone came across this requirement and have a solution? Or at least a recommendation on which user exit/badi that may be used to implement this?
Cheers,

Hi Anupama,
Try to write the code like this..
loop at itab_covp.
    select single dlinr belnr from ad01dli INTO AD01DLI-dlinr AD01DLI-belnr
    where belnr = itab_covp-belnr .
    if sy-subrc <> 0.     "if record doesn't exist
      DELETE t_covp.
    else.                     "If record exist
      SELECT single * from AD01DLIEF into AD01DLIEF
       where DLINR = AD01DLI-dlinr and belnr = itab_covp-belnr and dopen <> ''.
       if sy-subrc <> 0. "if record doesn't exist
         DELETE t_covp.
       endif.
    endif.
endloop.
This will be the correct logic for your requirement.
Thanks,
Sreenivas Reddy Maddi

Unable to convert PO using ME59N

Hi,
I unable to create PO using ME59N,it show"No suitable purchase requisition found"
Below is the information:
PR type :NB,acc.assignment K,item category D
Source of supply is contract
PR and Contract already released
Vendor master - purchasing data - "Automatic PO" is ticked
It working fine for PR with acc assignment K and is there any special setting need to be done with item category D?
Thank you

Is the #Automatic order allowed# indicator set with the purchase requisition for services in Customizing on client level and on the #Purchasing organization# level?
if you have problems with automatic PO creation, then see OSS Note 786303 - Analysis report RM06ME59 PReq check
It has a report ZRM06ME59 attached that helps you to find the problem

Auto PO creation from service PR(ME59N)

Hi All,
We have service PR's and need to convert to PO's automatically via ME59N.
I have followed below steps but unable to convert to Po's getting message no Pr's found while executeting ME59N
checked VMR and Automatic PO check box selected.
Step1: Creating PR for services
Step2: and assigned source to this PR through t.code: ME56 (contract existed for this vendor)
Step3:Run the ME59Nby giving PR Number, but PO is not created
what could be the reason..is any idea about auto PO creation for Service PR's
Incase of material i can successfully converts PR's PO's but services i can't.
Thanks in Advance,
Warm regards,
Venkat
MM/SRM Consultant

Hi venkat
it should create a PO if the contract is valid..
Note 733045 - Wrong Interface values passed to Services for ME59N
When transaction ME59N is used to convert service purchase requisition
(PR) to purchase order (PO),the program within the ME59N transaction
calls the service package with the wrong interface values.
The following example illustrates one such case :
A Service PR is created and an Outline agreement is assigned as a source of supply to the PR.
when the transation ME59N is executed using the PR's the system performs a mandatory check against the Tax code and tax code has to be entered against each service line to complete the transaction even though the tax code is maintained as a condition.
In the above situation,system behaves in a correct manner for the
transaction ME59 but fails for the transaction ME59N.
Other terms
MS_SERVICE_PACKAGE , ME59N , ME59 , WITHOUT_SCREEN , COPY_SERVICES
Reason and Prerequisites
The calling program of the transaction ME59N calls the function
MS_SERVICE_PACKAGE of services with the wrong interface values.
is it applicable for you?

Me59n

Similar Messages

Maybe you are looking for