Message type EINK "Mail to Purchasing" is being replaced by the
message type MLPP for Logistics Invoice Verification: In Release
3.x, the type EINK was used for both conventional Invoice
Verification (MR01) and Logistics Invoice Verification (MR1M). This
led to conflicts when both Invoice Verification components were
used. As of Release 4.0a, type EINK will only be used for
conventional Invoice Verification. The type MLPP will be used for
Logistics Invoice Verification. The two types have identical
functionality. The following activities are only necessary if,
prior to Release 4.0a, you used the message type EINK in connection
with Logistics Invoice Verification:
If you changed the type EINK so that it differs from the
standard, you may have to make the same changes for MLPP. This
applies in particular to the mail text.
Unlike EINK, MLPP does not access condition table B046 "Company
code/blocking reason price", but table B049 "Company code". If you
have already made entries in B046, you can copy these to B049. You
can also change the access sequence and have the type MLPLP access
B046. If you do so, no further changes are necessary.
Condition table B047 "Company code/blocking reason(qty)" has
been deleted. On installation of Release 4.0, B047 and all its
entries will be deleted. B047 was not contained in any access
sequences in the standard system. If you did not change message
determination in Invoice Verification or if you did make changes
but did not add B047 to an access sequence, the deletion of B047
will have no repercussions. Only if you added B047 to an access
sequence are the following activities necessary:
Check if you can use condition table B049 "Company code". This
is new in Release 4.0a and has company code as its key. If you can
use this table, you have to maintain B049 after Release 4.0a is
installed. Otherwise, in customer name space create a new condition
table similar to B047 and - before you install Release 4.0 - copy
over the entries or enter them new.
Convert the access sequences contained in B047. You may have to
change the requirements used for message schemas and message types
The following functions are linked to message
Evaluated Receipt Settlement (ERS)
When goods receipts are settled, a
statement is generated via SAPscript.
When withdrawals from the pipeline or
consignment stores are settled, a letter of consignment is
generated via SAPscript.
When an invoice is reduced, a letter
of complaint is generated via SAPscript.