LOG_MMFI_P2P: BF MM, Integration of Materials Management and Financial

Accounting
Use
As of SAP enhancement package 4 for SAP ERP 6.0 (SAP_APPL 604), materials management
provides the following new functions:
o MM_PUR_604_MMFI_ANZA: Entering of Down Payment Data in the
Purchase Order (New)
o MM_IV_604_MMFI_AZVER: Down Payment Clearing (New)
o MM_IV_604_MMFI_EINBE: Posting of Retentions (New)
o MM_IV_604_MMFI_WEDAT: Checking of Goods Receipt Date Against
Delivery Date (New)
o MM_IV_604_MMFI_PARTN: Checking of Partner Roles in the
Incomi ng Invoice (New)
o MM_PUR_604_MMFI_FO: Follow-On Activities for Completed
Purchase Order Items (New)
o MM_PUR_604_MMFI_REPO: Business Add-In for Displaying
Reporting Data
o MM_PUR_604_MMFI_LFPL: Stock Removal of Scheduling Agreement
Releases (New)
o Entering of plant data in the incoming invoice
In the transactions Enter Invoice (MIRO) and Park Invoice (MIR7), on the G/L Account tab
page, you can enter data in the Plant field and call this data when displaying the invoice
document (MIR4).
o New editor for enteri ng texts in purchasing info records
A new editor is available for entering internal info record memos and purchase order texts
in purchasing info records, in which you can enter continuous text with word wrap. The
new editor replaces the previous editor in the transactions ME11, ME12, and ME13 on
the screen SAPMM061.
o Improved Reports for Archiving Purchasing Documents
- Archiving object MM_EKKO
Preprocess (RM06EV47), Write (RM06EW70), Delete (RM06ED70)
- Archiving object MM_EBAN
Preprocess (RM06BV70), Write (RM06BW70), Delete (RM06BD70)
- Archiving object MM_EINA
Write (RM06IW70), Delete (RM06ID70)
LOG_MMFI_P2P: Entering of Down Payment Data in the Purchase Order (New)
Use
As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function MM,
Integration of Materials Management and Financial Accounting (LOG_MMFI_P2P), you can
save down payment data in the purchase order, at both header and item level, which the
system copies to financial accounting as default values. You can specify down payment
categories, down payment amounts, down payment percentages, and due dates in the
purchase order.
In the report Down-Payment Monitoring for PO, (report RM06DPMONITOR), you can display all
the purchase orders with down payment-relevant data whose due dates are within a certain
period. In addition to the due date, you can use further selection criteria to select purchase
orders (for example, vendor, purchasing group, and document date). From the report, you can
display data for purchase orders and branch to the FI applications for creating and changing
down payment requests and down payments. You can change the default down payment data
there.
You can use the Business Add-In Enhancement for Processing the Enjoy Purchase Order
(Customer) (ME_PROCESS_PO_CUST) to define the conditions when down payments are
mandatory, in the methods CHECK, PROCESS_HEADER, and PROCESS_ITEM. For example,
you can define that down payments are required for purchase order values as of a specific
value.
Effects on Existing Data
In the transactions MEPO, ME21N, ME22N, and ME23N, the following changes to the user
interface have been made in program SAPLMEGUI:
o There is a new screen 1238, which contains fields for saving down payment data in the
purchase order header.
o There is a new screen 1317, which provides fields for saving down payment data at item
level.
LOG_MMFI_P2P: Down Payment Clearing (New)
Use
As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function MM,
Integration of Materials Management and Financial Accounting (LOG_MMFI_P2P), you can
perform down payment clearing directly in logistics invoice verification, without having to branch
to the relevant financial accounting transactions. You can use this function for material
settlement and service settlement. When you enter an incoming invoice, you can select down
payments that have been posted for a purchase order for down payment clearing, and post the
down payment clearing document together with the invoice document.
Two Business Add-Ins (BAdIs) enable you to make customer-specific enhancements to down
payment clearing:
o You can use the BAdI BAdI: Default Values for Vendor Down Payment
Clearing (BADI_CALC_DP_VALUES) to define default values for down payment
clearing in logistics invoice verification. BAdI method CALC_PROPOSED_VALUES
contains two new import parameters to help you do this.
o You can use the BAdI Down Payments (MRM_DOWNPAYMENT) to control whether
down payment clearing is possible directly in logistics invoice verification. If you specify
that the system does not output the message "Down payments exist for this purchase
order" (M8 318), the Down Payment Clearing pushbutton is not displayed and the down
payment clearing option is not available.
Note:
You cannot use down payment clearing in connection with prepayments. Furthermore, you can
only use down payment clearing if you have not activated the function for document splitting for
the new general ledger in the leading company code of the invoice in question.
Effects on Existing Data
In the transactions Enter Invoice (MIRO), Park Invoice (MIR7), and Display Invoice Document
(MIR4), the newDown Payment Clearing pushbutton is available at header level.
Effects on Customizing
If you want to define default values for down payment clearing, implement the BAdI Default
Values for Vendor Down Payment Clearing in Customizing for financial accounting, under
Accounts Receivable And Accounts Payable --> Business Transactions --> Down Payment
Made --> Down Payments/Down Payment Requests.
If you do not want down payment clearing to be available in logistics invoice verification,
implement the BAdI Down Payments in Customizing for material management under Logistics
Invoice Verification -->Maintain Customer Exits and Business Add-Ins.
LOG_MMFI_P2P: Posting of Retentions (New)
Use
As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function MM,
Integration of Materials Management and Financial Accounting (LOG_MMFI_P2P), you can
retain parts of the invoice amount until a defined due date, in order to ensure the fulfillment of
the contract when materials are delivered or services performed.
You can define retentions as a percentage of the purchase order value in purchasing. The
system copies the retention data that you define at header and item level in purchase orders to
logistics invoice verification, as default values. When you process the incoming invoice, you can
change retention data and define the due date.
The system transfers the special G/L indicator for H to financial accounting.
The BAPIs BAPI_CONTRACT_CREATE and BAPI_CONTRACT_CHANGE are available for
creating and changing retentions for contracts. You can only display the retention data you
entered with the BAPI BAPI_CONTRACT_GETDETAIL, not in the contract itself.
Note:
o You cannot use retention together with prepayment of an invoice.
o An amount split is not possible for retention.
o If you have activated valuation areas for the material ledger, you cannot define retentions
for purchase order items with these valuation areas.
o You cannot use retention together with installment payment.
o In case of multiple account assignment, no different tax codes are possible.
o Delivery costs are not included when retentions are calculated.
Effects on Existing Data
o In the transactions MEPO, ME21N, ME22N, and ME23N, in program SAPLMEGUI, there
is a new screen 1238, which contains fields for saving retention data in the purchase
order header.
o In transactions MIRO, MIR7, and MIR4, the following fields for entering and displaying
incoming invoices are available:
- At header level in program SAPLMRM_INVOICE_CHANGE, screen 0100, the new
field Retention Due.
- At item level in program SAPLMR1M, screen 6310, the new fields Retent. in Doc.
Crcy, Retention %, Due Date, and Tax Reduction.
Effects on Customizing
To define special features for processing retention, in Customizing for Materials Management
choose Logistics Invoice Verification --> Incoming Invoice --> Retention.
o In the IMG activity Define Default Due Date for Retention, you can define a
validity period for retentions for each material group, which the system uses to determine
the default value for the due date in logistics invoice verification.
o In the IMG activity Define Tax Handling for Retention, you can define country-
specific parameters for tax calculation in the retention document.
o In the IMG activity Define Control Parameters for Retention, you can define
company code-specific settings for retention.
You can use Business Add-In (BAdI) Default Values and Input Parameters for
Retention Amounts to define a customer-specific proposal logic for retention data in
logistics invoice verification, and control the changeability of default values.
LOG_MMFI_P2P: Checking of Goods Receipt Date Against Delivery Date (New)
Use
As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function MM,
Integration of Materials Management and Financial Accounting (LOG_MMFI_P2P), you can
check whether the goods receipt is as agreed or too late, when creating an incoming invoice.
The document date of the goods receipt is checked against the delivery date defined in the
purchase order. In the purchase order, the system checks both the last delivery date that was
agreed at schedule line level and the latest possible goods receipt date entered in the item
details.
If the goods receipt date is after the agreed dates, the system issues a message. You can
define this message as an information message in Customizing.
Effects on Customizing
If you want the system to check the goods receipt date, in IMG activity Define Attributes of
System Messages enter system message M8 778 with message type Information.
LOG_MMFI_P2P: Checking of Partner Roles in the Incomi ng Invoice (New)
Use
As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function MM,
Integration of Materials Management and Financial Accounting (LOG_MMFI_P2P), you can
check whether the invoicing party is allowed as a payee when creating an incoming invoice.
The system checks the following when you create the invoice:
o Whether the entered invoicing party is specified as a partner in the header data of the
referenced purchase order.
o Whether the partner role of the entered invoicing party is defined as an allowed payee
according to your settings in Customizing.
These checks can be set independently of each other as either warning or error messages. If
both checks are active, the system first checks whether the invoicing party is entered as a
partner in the purchase order header. If the result is positive, a second step is performed, in
which the validity of the partner role is verified.
Effects on Customizing
In the IMG activity Define Partner Role as Allowed Payee, you define for each client
which partner roles are allowed as payees.
In the IMG activity Define Attributes of System Messages, you activate the checking
of the business partner by assigning the system messages M8 776 and M8 777 to message
type Warning or Error.
You can use the Business Add-In BAdI: Check Partner Data from Purchase Order
to define customer-specific logic, which the system uses to check the partner data.
LOG_MMFI_P2P: Follow-On Activities for Completed Purchase Order Items
(New)
Use
As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function MM,
Integration of Materials Management and Financial Accounting (LOG_MMFI_P2P), you can
suppress follow-on activities for purchase order items in which the delivery completed indicator
or the final invoice indicator is set.
In the following cases, the system issues a message, which you can define as an error
message in Customizing, to prevent the posting of follow-on documents:
o When you enter an additional partial goods receipt for a purchase order for which delivery
is completed (message M7 433)
o When you enter an additional partial invoice for a purchase order for which invoicing is
completed (messages M8 705 and M8 707)
You can use Business Add-In BAdI: Set Delivery Completed Indicator
(MB_GOODSMOVEMENT_DCI) to implement your own logic determining when the
system sets the delivery completed indicator in a purchase order item.
If you use the example implementation MB_GOODSMOVEMENT_DCI_EXAMPLE, once a
purchase order item has the delivery completed indicator it does not lose this status, even if
further partial goods receipts are posted for the item. This means that budget is released only
for the delivery quantity of the subsequently posted partial goods receipt, not for the whole open
purchase order quantity.
LOG_MMFI_P2P: Busi ness Add-In for Displaying Reporting Data (New)
Use
As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function MM,
Integration of Materials Management and Financial Accounting (LOG_MMFI_P2P), you can use
the new Business Add-In (BAdI) Enrich ALV Output Tables in Reporting
(ME_CHANGE_OUTTAB_CUS).
You can use this BAdI to influence the data displayed from different reporting transactions in the
Purchasing (MM-PUR) andServices (MM-SRV) components. Before you can do this, data must
be displayed using ALV grid control.
Effects on Customizing
To implement the BAdI, in Customizing for Materials Management choose Purchasing -->
Business Add-Ins for Purchasing.
LOG_MMFI_P2P: Stock Removal of Scheduling Agreement Releases (New)
Use
As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function MM,
Integration of Materials Management and Financial Accounting (LOG_MMFI_P2P), you can
remove scheduling agreement releases (forecast delivery schedules and J IT delivery
schedules) from stock, thereby preventing a high number of older releases from adversely
affecting the performance of your application.
In the new transaction Removal/Relocation of Scheduling Agreement Releases (ME83), you
can use various criteria to select forecast delivery schedules and J IT delivery schedules, and
define how many releases should still be available for a scheduling agreement item. By
removing older scheduling agreement releases, you improve the performance of downstream
processes, such as the display and editing of delivery schedule lines, the creation of releases,
and goods receipt. The system stipulates that you cannot remove the five most recent forecast
delivery schedules and J IT delivery schedules.
To remove scheduling agreement releases, on the SAP Easy Access screen choose Logistics --
> Materials Management --> Purchasing --> Outline Agreement --> Scheduling Agreement -->
Administer --> Remove Scheduling Agreement Releases.
Note:
You cannot reverse the removal of scheduling agreement releases. The system writes all
removed releases to the corresponding removal tables (EKEKH, EKEHH, and, if appropriate,
ISAUTOEKLWESH), which you can display only in the Data Browser (transaction SE16).
See al so
For more information, see the Materials Management component under Purchasing --> Outline
Purchase Agreements with Vendors -->Scheduling Agreement --> Administration of Scheduling
Agreements.