me59 自動產生PO時，PO type如何決定

Aiking

Roger.

nylgzxf

一个是PR type 可以定义对应相应的PO type， 另外可以通过mrp组定义 物料对应的pr type。

sofy124

原帖由 stcao 于 2008-7-21 13:18 发表
解答参见SAP Note 114213 - ME59: Determining the order document type

Symptom

The determination of the order document type during the automatic generation of purchase orders is unclear, in particular, whether you can define a special document type as a default value.


Other terms

ME59, RM06BB10, RM06BB20, T160, T161A, OMH5, OMEC



Solution

You want to convert a group of purchase requisitions into a purchase order. The document type of the purchase order is derived from the document type of the first purchase requisition of this group according to the following algorithm:
If an order document type exists which is identical to the purchase requisition document type and is allowed according to Customizing (table T161A or Customizing Transaction OMEC) this one has the highest priority. If there is only one allowed document type, the system generates this one. For several allowed document types, the one which is entered as a default document type for Transaction ME21 is prior to the others (table T160 or Customizing Transaction OMH5). If nothing is entered here or the default document type is not allowed, the system takes the first allowed document type.
Special cases are stock transport orders and the purchse order split for each item category:
For stock transport orders the document type is derived from the combination issuing plant/receiving plant (table T161W or Customizing Transaction OMGN).
If the purchase order split is active for each item category, the item category is also used during the document type determination:
If there is one order document type which is identical with the purchase requisition document type and the same item category is allowed as the one in the purchase requisition (according to table T161A), the system uses this combination. If there are several possibilities, the system takes the first document type for which the same item category is allowed as for the purchase requisition. If this does not succeed (as in the general case), the same document type (if available) is chosen (but with a different item category) or the default document type for Transaction ME21 or the first allowed one.

There is no possibility to define a special document type (via the proposal mechanism of table T160) for the automatic generation of purchase orders. Since this is required by several customers, a simple modification solution is stated in the attachment. A general solution in the standard system (together with a user exit) is planned for a later release.

The modification solution uses table T160. You can add an entry via table maintenance (Transaction SM31 or SE16) for Transaction ME59 and define a default document type (unfortunately not via Customizing Transaction OMH5) since they are restricted to the transactions, where the default document type is applied in the standard system. To be able to use the default value in Transaction ME59, implement the program change in report RM06BB10 listed in the attachment. The modification is only possible for the simpliest case (no stock transport order, no split according to item category) and gives highest priority to the default document type if it is allowed according to Customizing.

果然是前辈。。。

qualmy

可是，系统提示不存在实物 omgn

luzfeng

看英语好累啊

seaman1978

我试过,只能设置一种default PO type.如果用ME57操作时,要根据不同的PR Type 自动带出不同的PO type要如何操作？

soror

学习学习……

jiliguan

并不是只可以转成NB类型的PO，是与后台配置PR type可以转为哪些PO type相关的。PR转PO也是可以使用ME21N的，而且更加方便，在ITEM中输入要转的PRnumber即可。使用ME59的是针对已经分配了vendor的PR，如果没有分配的话需要使用ME57 ME58为PR分配vendor后才可以转。

ys_yansh

学习一下!

seaman1978

Note 114213 - ME59: Determining the order document type
Note Language: English Version: 8 Validity: Valid from 26.03.2003
Summary
Symptom
The determination of the order document type during the automatic
generation of purchase orders is unclear, in particular, whether you can
define a special document type as a default value.
More Terms
ME59, RM06BB10, RM06BB20, T160, T161A, OMH5, OMEC
Cause and Prerequisites
Solution
You want to convert a group of purchase requisitions into a purchase order.
The document type of the purchase order is derived from the document type
of the first purchase requisition of this group according to the following
algorithm:
If an order document type exists which is identical to the purchase
requisition document type and is allowed according to Customizing (table
T161A or Customizing Transaction OMEC) this one has the highest priority.
If there is only one allowed document type, the system generates this one.
For several allowed document types, the one which is entered as a default
document type for Transaction ME21 is prior to the others (table T160 or
Customizing Transaction OMH5). If nothing is entered here or the default
document type is not allowed, the system takes the first allowed document
type.
Special cases are stock transport orders and the purchse order split for
each item category:
For stock transport orders the document type is derived from the
combination issuing plant/receiving plant (table T161W or Customizing
Transaction OMGN).
If the purchase order split is active for each item category, the item
category is also used during the document type determination:
If there is one order document type which is identical with the purchase
requisition document type and the same item category is allowed as the one
in the purchase requisition (according to table T161A), the system uses
this combination. If there are several possibilities, the system takes the
first document type for which the same item category is allowed as for the
purchase requisition. If this does not succeed (as in the general case),
the same document type (if available) is chosen (but with a different item
category) or the default document type for Transaction ME21 or the first
allowed one.
There is no possibility to define a special document type (via the proposal
mechanism of table T160) for the automatic generation of purchase orders.
Since this is required by several customers, a simple modification solution
is stated in the attachment. A general solution in the standard system
(together with a user exit) is planned for a later release.
The modification solution uses table T160. You can add an entry via table
maintenance (Transaction SM31 or SE16) for Transaction ME59 and define a
default document type (unfortunately not via Customizing Transaction OMH5)
since they are restricted to the transactions, where the default document
type is applied in the standard system. To be able to use the default value
in Transaction ME59, implement the program change in report RM06BB10 listed
in the attachment. The modification is only possible for the simpliest case
(no stock transport order, no split according to item category) and gives
highest priority to the default document type if it is allowed according to
Customizing.
Header Data
Release Status: Released for Customer
Released on: 21.02.2008 08:23:23
Priority: Recommendations/additional info
Category: Consulting
Main Component MM-PUR Purchasing
Valid Releases
Software Component Release From
Release
To Release and Following
SAP_APPL 30 30A 31I X
SAP_APPL 40 40A 40B X
SAP_APPL 45 45A 45B X
SAP_APPL 46 46A 46B X
SAP_APPL 46C 46C 46C X
SAP_APPL 470 470 470 X
SAP_APPL 500 500 500
SAP_APPL 600 600 600
SAP_APPL 602 602 602
SAP_APPL 603 603 603
SAP_APPL 604 604 604
Related Notes
Number Short Text
491211 FAQ: Purchase order (general)
Correction Instructions
Correction
Instructio
ns
Valid
from
Valid
to
Software
Component
Typ
e
*)
Reference
Correction
Last
Changed
30A 46C SAP_APPL C 28.02.2000 13:23:10
535430 470 604 SAP_APPL C 20.02.2008 06:43:41
*) C Correction, B Pre-Implementation, A Post-Implementation, M Undetermined