Sie sind auf Seite 1von 4

Business Function Procure-to-Pay for Commodities –

Constraints in Enhancement Package 6


Regarding the business function Procure-to-Pay for Commodities, there exist several
constraints for the delivery of enhancement package 6 (Suite 7i2011). This document
describes the constraints.

Constraints for Purchasing (MM-PUR)


The following restrictions apply for purchasing, purchase orders and PO items
relating to differential invoicing:

You can define the items of a purchase order (PO) as relevant for differential
invoicing. When starting the purchasing process by means of a purchasing
contract or a purchase requisition, it is not possible to define an item of the
purchasing contract or purchase requisition as being relevant for
differential invoicing. Nevertheless, when you create a PO with reference to a
purchase requisition or as a call-off from a purchasing contract, the resulting
PO items can be defined as relevant for differential invoicing.

Scheduling agreements are not supported in combination with differential


invoicing; i.e. it is not possible to set an item as being relevant for differential
invoicing.

When creating a PO for differential invoicing, the item categories below are
not supported. Currently only item category Standard is supported.

Limit
Consignment
Subcontracting
Third-party
Stock transfer
Note that for intra-company stock transfers (internal item category 7) an
invoice receipt is only possible for planned delivery costs and therefore this
type of PO item is not relevant for differential invoicing.
For cross-company stock transfers (internal item category 0) differential
invoicing is supported.
Services
Material unknown
Material group
Text

© 2011 SAP AG Title: Business Function Procure to Pay for Page 1 of 4


Commodities – Constraints in EHP 6
Dietmar-Hopp-Allee 16
D-69190 Walldorf Date: April 2011
In general, PO items with account assignments are supported, i.e. all the
existing account assignment categories can be used. However, because of
issues in Logistics Invoice Verification, account assignment category “Asset” is
not supported.

If a goods receipt is intended and it is not to be valuated, a PO item cannot be


set as relevant for differential invoicing if in customizing for the specific
account assignment category the indicator for changing account assignment at
time of invoice receipt is set.

The following additional constraints for PO items also apply:

If an invoicing plan exists, the PO item cannot be set as relevant for differential
invoicing. Moreover, if a PO item has been set as relevant for differential
invoicing, it is not possible to create an invoicing plan.
If a PO item is marked to be subject to Evaluated Receipt Settlement (ERS), it
cannot be set as relevant for differential invoicing.
If a PO item is defined as returns item, it cannot be set as relevant for
differential invoicing.
If an invoice receipt it not intended for a PO item, it cannot be set as relevant
for differential invoicing.
If the final account assignment indicator is set, the PO item cannot be set as
relevant for differential invoicing.

Finally, when changing a PO, it is not possible to change the relevancy of a PO item
with regard to differential invoicing if one or more of the following conditions apply:

The invoice has already been posted for the PO item.


A goods receipt has already been posted to unrestricted-use stock (movement
type 101) for the PO item.
A goods receipt has been posted to blocked stock (movement type 103 and
107) for the PO item.
A goods issue (WAMNG) has been posted for the PO item.
An invoice has been parked or parked as complete for the PO item.
An invoice has been held for the PO item.
An invoice has been saved as erroneous from background or EDI processing
for the PO item.

© 2011 SAP AG Title: Business Function Procure to Pay for Page 2 of 4


Commodities – Constraints in EHP 6
Dietmar-Hopp-Allee 16
D-69190 Walldorf Date: April 2011
Constraints for Inventory Management (MM-IM)
Customers often use GR-based invoice verification when purchasing commodities. In
this case, a goods receipt is required before posting an invoice.

The following restrictions apply for price determination in inventory management:

When using transaction MIGO it is possible to create two material document


items with reference to the same PO item. For each material document item
the batch classification can be maintained differently, i.e. the delivered quantity
is of different quality. Pricing team defined this use case as restriction

The following restrictions apply for the handling of batches in inventory


management:

For the cancellation of a goods receipt, a restriction has been introduced. If a


provisional, differential or final invoice has already been posted, a message is
issued for the cancellation of the corresponding goods receipt. The message
category (error or warning) is customizable.

After posting an initial goods receipt, it is possible to create a subsequent


delivery with reference to the initial goods receipt. In this case, the batch that
was used for the initial goods receipt is copied to the subsequent delivery.
Moreover this default batch cannot be changed and a user is therefore not
able to post a subsequent delivery with a different batch than the
corresponding initial goods receipt.

Constraints for Logistics Invoice Verification (MM-IV)


After posting a goods receipt, a customer is able to post provisional, differential and
final invoices by means of transactions from MM-IV. For differential invoicing, the
following transactions are not supported:

Evaluated Receipt Settlement (ERS – transaction MRRL) and Automatic


Delivery Cost Settlement (transaction MRDC) are not supported, because, as
already mentioned in the restrictions for Purchasing, a PO item with the ERS-
flag cannot be set as relevant for differential invoicing.
Consignment and Pipeline Settlement (transaction MRKO) is not supported,
because it does not have a PO reference.
Invoicing Plan Settlement (transaction MRIS) is not supported because, as
already mentioned in the restrictions for Purchasing, a PO item with an
invoicing plan cannot be set as relevant for differential invoicing.

© 2011 SAP AG Title: Business Function Procure to Pay for Page 3 of 4


Commodities – Constraints in EHP 6
Dietmar-Hopp-Allee 16
D-69190 Walldorf Date: April 2011
Revaluation (transaction MRNB) can be used if a final invoice has been
posted. Otherwise an error message is raised and the usage is not allowed.
IDOC INVOIC for incoming invoices cannot be used for differential invoicing.

The following BAPI-function modules are not supported in MM-IV:

BAPI_INCOMINGINVOICE_CREATE
BAPI_INCOMINGINVOICE_CREATE1
BAPI_INCOMINGINVOICE_CHANGE
BAPI_INCOMINGINVOICE_PARK
BAPI_INCOMINGINVOICE_POST

In addition to the above-mentioned transactions, the following MM-IV functionalities


are not supported for differential invoicing:

Invoice reduction
Retention
Subsequent (end-of-period rebate) settlement
Subsequent debit/credit indicator is not available on item level.
Planned delivery costs can be included in a provisional, differential or final
invoice, but the differential invoicing process cannot actually be applied to
these costs.
The following example shows the behavior (system EBS, 003, PO
4500002469):
The PO contains a freight condition which is calculated as 10% of the material
value. For the PO item, re-pricing at goods receipt has been set.
When posting the goods receipt, re-pricing took place and freight cost has
been posted. A Provisional Invoice has been posted. For the Differential
Invoice, the freight cost shall be considered. Because of the actual batch
classification, the net value for the material has been calculated with
15.619,72 USD. The condition details for the material item show the correct
calculation of the net value. Moreover, the calculation for freight cost is shown
correctly with 1.561,97 USD (10% of 15.619,72 USD).
If freight costs are included in the Differential Invoice, the amount is calculated
using the existing standard logic, i.e. the condition value for the freight
condition is taken from the price determination at time of goods receipt. The
amount for the freight condition is proposed with 943,46 USD. This amount
differs from the value that has been calculated and shown in the condition
details for the material. There is no connection between the proposal of the
amount for freight condition and the value that has been calculated during
price determination for the material item.

© 2011 SAP AG Title: Business Function Procure to Pay for Page 4 of 4


Commodities – Constraints in EHP 6
Dietmar-Hopp-Allee 16
D-69190 Walldorf Date: April 2011

Das könnte Ihnen auch gefallen