186272645 Down Payment in Miro

LOG_MMFI_P2P: BF MM, Integration of Materials Management and FinancialAccounting

Use

As of SAP enhancement package 4 for SAP ERP 6.0 (SAP_APPL 604), materials managementprovides the following new functions:

o MM_PUR_604_MMFI_ANZA: Entering of Down Payment Data in thePurchase 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

Incoming 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 Datao 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 tabpage, you can enter data in the Plant field and call this data when displaying the invoicedocument (MIR4).

o New editor for entering texts in purchasing info recordsA new editor is available for entering internal info record memos and purchase order textsin purchasing info records, in which you can enter continuous text with word wrap. Thenew editor replaces the previous editor in the transactions ME11, ME12, and ME13 onthe screen SAPMM061.

o Improved Reports for Archiving Purchasing Documents

- Archiving object MM_EKKOPreprocess (RM06EV47), Write (RM06EW70), Delete (RM06ED70)

- Archiving object MM_EBANPreprocess (RM06BV70), Write (RM06BW70), Delete (RM06BD70)

- Archiving object MM_EINAWrite (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 cansave down payment data in the purchase order, at both header and item level, which thesystem copies to financial accounting as default values. You can specify down paymentcategories, down payment amounts, down payment percentages, and due dates in thepurchase order.

In the report Down-Payment Monitoring for PO, (report RM06DPMONITOR), you can display allthe purchase orders with down payment-relevant data whose due dates are within a certainperiod. In addition to the due date, you can use further selection criteria to select purchaseorders (for example, vendor, purchasing group, and document date). From the report, you candisplay data for purchase orders and branch to the FI applications for creating and changingdown payment requests and down payments. You can change the default down payment datathere.

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 aremandatory, 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 specificvalue.

Effects on Existing Data

In the transactions MEPO, ME21N, ME22N, and ME23N, the following changes to the userinterface have been made in program SAPLMEGUI:

o There is a new screen 1238, which contains fields for saving down payment data in thepurchase order header.

o There is a new screen 1317, which provides fields for saving down payment data at itemlevel.

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 canperform down payment clearing directly in logistics invoice verification, without having to branchto the relevant financial accounting transactions. You can use this function for materialsettlement and service settlement. When you enter an incoming invoice, you can select downpayments that have been posted for a purchase order for down payment clearing, and post thedown payment clearing document together with the invoice document.

Two Business Add-Ins (BAdIs) enable you to make customer-specific enhancements to downpayment clearing:

o You can use the BAdI BAdI: Default Values for Vendor Down PaymentClearing (BADI_CALC_DP_VALUES) to define default values for down paymentclearing in logistics invoice verification. BAdI method CALC_PROPOSED_VALUEScontains two new import parameters to help you do this.

o You can use the BAdI Down Payments (MRM_DOWNPAYMENT) to control whetherdown payment clearing is possible directly in logistics invoice verification. If you specifythat the system does not output the message "Down payments exist for this purchaseorder" (M8 318), the Down Payment Clearing pushbutton is not displayed and the downpayment clearing option is not available.

Note:

You cannot use down payment clearing in connection with prepayments. Furthermore, you canonly use down payment clearing if you have not activated the function for document splitting forthe new general ledger in the leading company code of the invoice in question.


In the transactions Enter Invoice (MIRO), Park Invoice (MIR7), and Display Invoice Document(MIR4), the new Down 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 DefaultValues for Vendor Down Payment Clearing in Customizing for financial accounting, underAccounts Receivable And Accounts Payable --> Business Transactions --> Down PaymentMade --> 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 LogisticsInvoice Verification --> Maintain Customer Exits and Business Add-Ins.

sudarshan.yewaleHighlight

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 canretain parts of the invoice amount until a defined due date, in order to ensure the fulfillment ofthe contract when materials are delivered or services performed.

You can define retentions as a percentage of the purchase order value in purchasing. Thesystem copies the retention data that you define at header and item level in purchase orders tologistics invoice verification, as default values. When you process the incoming invoice, you canchange 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 forcreating and changing retentions for contracts. You can only display the retention data youentered 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 retentionsfor 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.


o In the transactions MEPO, ME21N, ME22N, and ME23N, in program SAPLMEGUI, thereis a new screen 1238, which contains fields for saving retention data in the purchaseorder header.

o In transactions MIRO, MIR7, and MIR4, the following fields for entering and displayingincoming invoices are available:

- At header level in program SAPLMRM_INVOICE_CHANGE, screen 0100, the newfield Retention Due.

- At item level in program SAPLMR1M, screen 6310, the new fields Retent. in Doc.Crcy, Retention %, Due Date, and Tax Reduction.


To define special features for processing retention, in Customizing for Materials Managementchoose Logistics Invoice Verification --> Incoming Invoice --> Retention.

o In the IMG activity Define Default Due Date for Retention, you can define avalidity period for retentions for each material group, which the system uses to determinethe 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 definecompany 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 inlogistics 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 cancheck 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 thepurchase order. In the purchase order, the system checks both the last delivery date that wasagreed at schedule line level and the latest possible goods receipt date entered in the itemdetails.

If the goods receipt date is after the agreed dates, the system issues a message. You candefine this message as an information message in Customizing.


If you want the system to check the goods receipt date, in IMG activity Define Attributes ofSystem Messages enter system message M8 778 with message type Information.

LOG_MMFI_P2P: Checking of Partner Roles in the Incoming 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 cancheck 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 thereferenced purchase order.

o Whether the partner role of the entered invoicing party is defined as an allowed payeeaccording to your settings in Customizing.

These checks can be set independently of each other as either warning or error messages. Ifboth checks are active, the system first checks whether the invoicing party is entered as apartner in the purchase order header. If the result is positive, a second step is performed, inwhich the validity of the partner role is verified.


In the IMG activity Define Partner Role as Allowed Payee, you define for each clientwhich partner roles are allowed as payees.

In the IMG activity Define Attributes of System Messages, you activate the checkingof the business partner by assigning the system messages M8 776 and M8 777 to messagetype Warning or Error.

You can use the Business Add-In BAdI: Check Partner Data from Purchase Orderto 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 cansuppress follow-on activities for purchase order items in which the delivery completed indicatoror the final invoice indicator is set.

In the following cases, the system issues a message, which you can define as an errormessage 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 deliveryis completed (message M7 433)

o When you enter an additional partial invoice for a purchase order for which invoicing iscompleted (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 thesystem sets the delivery completed indicator in a purchase order item.

If you use the example implementation MB_GOODSMOVEMENT_DCI_EXAMPLE, once apurchase order item has the delivery completed indicator it does not lose this status, even iffurther partial goods receipts are posted for the item. This means that budget is released onlyfor the delivery quantity of the subsequently posted partial goods receipt, not for the whole openpurchase order quantity.

LOG_MMFI_P2P: Business 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 usethe 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 thePurchasing (MM-PUR) and Services (MM-SRV) components. Before you can do this, data mustbe displayed using ALV grid control.


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 canremove scheduling agreement releases (forecast delivery schedules and JIT deliveryschedules) from stock, thereby preventing a high number of older releases from adverselyaffecting the performance of your application.

In the new transaction Removal/Relocation of Scheduling Agreement Releases (ME83), youcan use various criteria to select forecast delivery schedules and JIT delivery schedules, anddefine how many releases should still be available for a scheduling agreement item. Byremoving older scheduling agreement releases, you improve the performance of downstreamprocesses, 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 forecastdelivery schedules and JIT 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 allremoved releases to the corresponding removal tables (EKEKH, EKEHH, and, if appropriate,ISAUTOEKLWESH), which you can display only in the Data Browser (transaction SE16).

See also

For more information, see the Materials Management component under Purchasing --> OutlinePurchase Agreements with Vendors -->Scheduling Agreement --> Administration of SchedulingAgreements.

186272645 Down Payment in Miro

Documents

Transcript of 186272645 Down Payment in Miro