ME59N : PR & PO type

Hi all,
I want to use ME59N to create automatically PO from PR.
When I use the PR type NB, ME59N create a PO type NB, there is no problem.
BUT, I want to use new types I have created : PR type RH and PO type ZRV.
If I use ME21N to create manually my PO type ZRV from my PR type RH, it works.
But If I use ME59N, I got an error : SAP wants to creat a PO type NB from my PR type RH, and it is impossible (I've made it impossible in the customizing).
Can I change the PO type for creation in ME59N, or ME59N can only create PO type NB ?
Thanks all for your answer.
Mathieu

Hi,
Have you created the new documwnt tyoes by copying the existing types or did you do it from the scratch?
ME59n will create any type of PO. But in PR you must have used the relevant Doc type. for example if you use Framework FO as doc type in PR, then if u create a PO from ME59n, then the system will create a PO of FO doc type.
If you want to change the doc type of PO to anything other than PR, then system will not allow you to do it.
Please check the document types linking in the SPRO of Purchasing - Document types...
Do not forget to check the Auto PO indicators in Vendor and Material masters..
Reward if helpful..
Regards,
Srib

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.

User Exit or BADI FOR ME59N

Hi All,
   My requirement is in ME59N if Document Type is ZCD or ZSD it should not consider the Rounding Value (MARC-BSTRF) which is coming from Materrial Master (MRP1 View) and Purchase Info Record (EINE-RDPRF) which is coming from Purchase Info Record(ME12 or ME13), Can any one suggest me the right User Exit or BADI for this, Please go through the requirement.
Regards,
Sudhakar .A
Edited by: Sudhakar Allam on Feb 5, 2010 4:31 AM

HI Sudhakar ,
                          These are the list of enhancements and Badi's available for ME59N ,
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
AMPL0001                                User subscreen for additional data on AMPL
MRFLB001                                Control Items for Contract Release Order
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
The list of Badi are
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: 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_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_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Leve
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKK
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
regards.

Automatic Creation of Purchase Orders from Purchase Requisition

Hi,
Requirement: When the Purchase requisitions is converted into Purchase Orders using ME59N, the document type of the PO should be ZCO (Z document type for Call off) and not NB.
Issue:When the Purchase requisitions are converted into PO's using ME59N, noremal PO's(Document type:NB) are getting created.
As per the business requirements, it should be ZCO.
Please guide if I am missing anything.
With regards
Krishna

Hi
Please refer the below thread.
OSS Note 114213
[ME59N - Automatic determination of POdocument type|ME59N - Automatic determination of POdocument type]
Gobinathan G
Edited by: Gobinathan Govindarajan on Nov 26, 2009 11:15 AM

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

Transaction ME59N for different PO document types

Hi,
I am in process of setting up process for converting PRs into POs automatically through transaction ME59N.
I have created various document types per Plant. That means, one PO document type for one plant & other document type for another plant.
Now, my problem is how can I control (or select) the document type while running the program. I want to run the program for MRP generated PRs in various plants with different PO types.
There is no selection possible for PO document type in transaction ME59N.
Is there any way out for the selection of PO document type in transaction ME59N.
Regards,
Prashant Kolhatkar

Hi Prashant,
This area of configuration might help you out:
Materials management -> consumption based planning -> planning -> procurement proposals -> define external procurement then the MRP Group button.
Have a look.
Steph.

Default doc type for ME59n

Hi All,
I want a doc type to come by default in ME59n how to make this setting? I have tried in SPRO>MM>Purchasing>define default values for doc type but its not possible there for ME59n.
Or putting in the other way how does the system takes document type in ME59n.
Thanks in advance
Pavan

Hi,
In Path SPRO > MM > Purchasing > Define default values for doc type
here assign the default PO Document type to ME21 and ME21N. It will pick up the PO Document Type assigned to ME21 during ME59N.
You can not use ME59 or ME59N here.
Check it by creating a new PO in ME59N.

ME59N - 1 PR doc type to 2 PO doc type

Hi,
I trying to use ME59N to covert PR doc type NB (with item category = blank) to PO doc type NB.
And convert PR doc type NB (with item category = K) to PO doc type CB.
How can I do it?
Thanks,
Anson

Hi Andy,
Thanks for the reply.
Documet Type Linkage
PR doc type NB (item cat. = Blank) link to PO doc type NB.
PR doc type NB (item cat. = Blank) link to PO doc type SB.
PR doc type NB (item cat. = K) link to PO doc type CB.
If my linkage relationship between PR & PO document type set as above, when I run ME59N and tick the option of "Per Item Categary". The PR with item category = Blank will convert to which PO document type?
Please advise.
Thanks,
Anson

Multiple STO document types conflict in ME59N

Folks,
I have the following scenario's:
1) PReq NB with item category U -> intercompany STO NB (depends on the supplying and receiving plant) document types gets determined correctly through STO document type customizing (T161W)
2) Preq NB with item category u -> intracompany STO UB, document types gets determined correctly through STO document type customizing (T161W)
3) exception flow where preq ZF gets created through a development. This is also inter- and intracompany traffic. In case it's intercompany it should get ZF1 and in case it's intracompany it should get ZF2.
I've set preq - PO linkage that ZF preq can be linked to ZF1 and ZF2. Now when running ME59N, it seems that system only takes settings of T161W into consideration and wants an NB document type and this is not allowed (preq - PO linkage table).
Any suggestions how to set up scenario 3?
MZ

Hi,
Please read OSS note 114213.
http://www.sapfans.com/forums/viewtopic.php?t=237357&highlight=&sid=a33e51e7989bd52296035460ee048409
Regards,
Csaba

Set different PO type when convert PR to PO using ME59N

Hi SAP,
This process is for third Party Sales Order, PR will be created after Third party Sales order is save, Then i use ME59N to convert the PR into PO. the problem is, The PR order type is "NB", when convert the PR into PO it will carry PR Order type NB for PO order type, how do i change the PO order type from "NB" to others ?

Hi,
Refer OSS note : 1361265
You can use the implementation of the BAdI ME_BSART_DET to adjust document type determination according to your requirements.
The attached sample implementation ensures that the document types that are maintained for EA-DFPS are always found in transactions ME59N and /ISDFPS/PRPLD.
If this sample does not meet your requirements, adjust the source code according to your requirements.
Proceed as follows:
Call transaction SE19 (BAdI Builder: Initial Screen for Implementations).
In the "Create Implementation" section, select "Classic BAdI", enter the BAdI name "ME_BSART_DET", and choose "Create Impl.".
Enter an implementation name, for example, ZISDFPS_ME_BSART_DET.
Confirm the customer namespace information and on the next screen, enter your own short text for the implementation.
Save and activate the BAdI implementation.
The implementing class is also specified on the "Interface" tab page.
Double-click to navigate to this class. Implement the method IF_EX_ME_BSART_DET~BSART_DETERMINE as described in the correction instructions.
Regards,
Ram

Create different doc type with me59n

Hi all!
I have a question. We have 2 types of PO - ZNS - for items with item category L - subcontracting and ZNB for items with standard item category. When we convert NB purchase requisitions with me59n we need to create PO's ZNB or ZNS depending of item category of PR. How can we do it?

With PO customizing in the IMG. But if the source of the PR's is a sales order schedule line, then you can better control the process with a differen type of requisition on the schedule line category.

Output type is not appearing in ME22N

Hi,
I have created some POs through sales order.i.e created a sales order and taken the PR from that.
Using ME59N, I have converted the PR to PO. The PO will have some output types attached (in the unprocesssed status).
The Output types (in the MESSAGES) are visible in ME23N. When I look into the PO in change mode ME22N, the output types are not appearing.... this is not the case with all the POs. Happening only for few POs.
Could you please suggest.
Ramana Malladi.

Hello,
Review your condition record values against the PO's that don't have an output type.
Could be something like purchasing group, material group, etc.
Regards
Waza

Separate Doc.Type for MRP generated PRs

Dear All
We are facing an issue with MRP process where we want to automate the process from MRP run to PO creation.
In source list we will add the existing contracts and make it relevant to MRP so that after MRP run we will get source (vendor defined in the contract) assigned purchase requisitions. After that, we will create a background job for ME59n in order to get the POs automatically after MRP run.
In this process we are facing issue with the auto PO generation through ME59n as funds management (FM) related parameters such as Fund and Fund center need to be enetered manually at the time of PO creation in our system. So in order to avoid this manual entry we want to define FM derivation which automatically populate the fund & fund center in the MRP generated PRs.
Further, we have two options for FM derivation one is valuation class and the second one is Document type. If we define the FM derivation based on the valuation class we cannot only restrict to MRP generated PRs. Second option is separate document type for MRP generated PRs.
Please provide pros and cons regarding the creation of new document type for MRP. Also, please provide your suggestions or any work arounds for the above discussed scenario. Your inputs are highly appreciated.
Thanks in advance.
Prabhas

Hi nagaraj
it makes sense . i will explore and tell you.
what about your source assignment standard program. hope it will assign source of supply if it is a valid unique source of supply else it will assign eprofile to your purcase request. check with technical resource how the satndard program behaves.
i will also explore my side again. check mm forum too on your purchase organisation assignment for your userexists.
one question to you.
when you create a PR for material and go to source of supply .why do we get many fixed vendors like contracts,info record if we have valid fixed vendors as sap ecc standard.but in my PR i may not have Purchase organisation information.
muthu

Default Doc Type for PO

Hi Friends..
I need your help in solving a Puzzle in SAP.
I want to use ME59N automatic po conversion option for creation of PO from PR.Here PR doc type is NB-Standard, I want PO doc type to be my own doc type " CT3 " doc type. I have made below settings,
a.Activated Auto PO in VMR.
b.Activated Auto PO in MMR
c.Linked my CT3 doc type in SPRO.
But, when I tried to do default doc type settings in SPRO, SAP didn't
accept this Tcode (ME59N) & hence not successfull.
SAP is taking default doc type as NB & not tailor made "CT3" doc type.
Pl respond.
Thanks, VK.

Hi,
You hve done settings for Automatic PO, I think those setting are not required for you. Because your scenario is not Automatic PO.
In ME21N transaction you can do personnel settings with this whenever you run the ME21N tcode by default system will pick tht doc type as default doc type. This can be user based setting.
Hve you maintained the combination of PO document type and PR docuement type ? If you are using onli CT3 PO document type, assign this PO document type only.
In SPRO - MM - Purchasing - Define default Doc types maintain the defulat doc type for ME21N transaction.
Hope its clear, still if u hve questions let me know.
reg
Durga
*Assign points if the info is useful

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

ME59N : PR & PO type

Similar Messages

Maybe you are looking for