SAP MM ME59N 自动创建PO时候，系统如何自动确定PO的document type？

1>这个跟你的系统配置有关。请查看下PO的Document type就知道，哪种类型的PR对应哪种类型的PO。

IMG：Material Management -> Purchasing -> Purchase order -> Define Document types

2>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 purchase 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 simplest 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.