4.6 vs 6.0

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.10.2</st1:chsdate>.2 All functions in logistics invoice verification. (4.7)<o:p></o:p>

Logistic invoice verification contains all functions from conventional invoice verification, as well as many other functions, for example, cross-company-code posting and invoice reduction.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.10.2</st1:chsdate>.3.1 automatic quantity and amount distribution for multiple account assignment: (4.7).<o:p></o:p>

On the screen for multiple account assignment in LIV, you can enter varying amounts and quantities, then system will automatic distribution to the relevant account assignment objects according to the distribution schema.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.10.2</st1:chsdate>.3.2 enhancements to BAPIs in LIV.<o:p></o:p>

 Park from data: BAPI_INCOMINGINVOICE_PARK. Park invoice<o:p></o:p>

 Save from data: BAPI_INCOMMINGVOICE_SAVE. Enter invoice for verification in the background.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.10.2</st1:chsdate>.3.3 Displaying MM and FI document numbers<o:p></o:p>

 When you post an incoming invoice, the system can display invoice document numbers generated in materials management, the document number of the accounting document in financial account, and the number of the invoice reduction document where applicable.<o:p></o:p>

The setting to decide whether the FI document number is also displayed, is made for each user using the parameter IVFIDISPLAY.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.10.2</st1:chsdate>.3.4 Clearing the GR/IR clearing account for external service purchase orders. (New) (4.7)<o:p></o:p>

When you enter invoices for external service purchase orders for which no service-based invoice verification is planned, the GR/IR clearing indicator in the item list controls the postings to the GR/IR clearing account. When you enter invoice, the system sets the GR/IR clearing indicator as a default.<o:p></o:p>

If the GR/IR clearing indicator is set, then when you post the invoice, the GR/IR clearing account is cleared completely, even if you only post a partial invoice. If you post partial invoices and do not want the GR/IR clearing account to be completely cleared when you post, you must deselect the GR/IR clearing indicator. <o:p></o:p>

The final invoice indicator then only controls the commitment reduction. When you enter purchase orders for external services and subsequently enter an invoice, the system does not propose this indicator as set.<o:p></o:p>

If the finial invoice indicator is selected, the commitment is completely reduced. <o:p></o:p>

If the finial invoice indictor is not selected, this means that if you are expecting further invoices for this <st1:place w:st="on">PO</st1:place> item, the commitment is reduced according to the amount in the invoice you enter.<o:p></o:p>

Note: if you enter invoices for purchase orders that are not for external services, or for external service purchase orders that are not planned for service-based invoice verification, then the GR/IR clearing indicator is not displayed in the item list. If you set the final invoice indicator when you enter an invoice for a service-based invoice verification, the system automatically sets the GR/IR clearing indicator. This means that the commitments are completely canceled out and the GR/IR clearing account is completely balanced for the <st1:place w:st="on">PO</st1:place> item affected.<o:p></o:p>

That is if you selected this indicator, then if you post a partial invoice(invoice amount less than service accepted amount), the GR/IR account will be equal service accepted amount,, otherwise will be equal invoice amount, the balance (service accepted amount – invoice amount) will be posted into cost account(Maintained accounting in PO).<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.10.2</st1:chsdate>.4.1 Enhancements to the invoice overview. Please compare the MIR6 Invoice overview to check the difference.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.10.2</st1:chsdate>.4.2 Verifying freight invoices in the background.<o:p></o:p>

     When you enter an incoming invoice for verification in the background(MIRA), You can assign a transportation service provider. If you select this, you can settle freight costs with transportation service providers in LIV for background verification.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.10.3</st1:chsdate>.1 Business Add-Ins in logistics invoice verification (for MIRO, MIRA, MIR7).<o:p></o:p>

MRM_HEADER_DEFAULT to preassign various header fields.<o:p></o:p>

MRM_PAYMENT_TERMS to set terms of payment<o:p></o:p>

MRM_UDC_DISTRIBUTE to distribute unplanned delivery costs, you can distribute unplanned delivery costs according to your own rules, for example under.<o:p></o:p>

MRM_TRANSACT_DEFAULT to preassign various transaction fields.<o:p></o:p>

MRM_WT_SPLIT_UPDATE to change the withholding tax data and the data for a vendor split.<o:p></o:p>

MRM_TOLERANCE_GROUP to set vendor-specific tolerance groups.<o:p></o:p>

MRM_RELEASE_CHECK for additional checks before invoices are released, in other words, you can restrict the list of invoices to be released by defining your own criteria.<o:p></o:p>

MRM_MRIS_HDAT_MODIFY to change header data for invoicing plan settlement.<o:p></o:p>

MRM_MRIS_IDAT_MODIFY to change item data for invoicing plan settlement.<o:p></o:p>

MRM_MRKO_HDAT_MODIFY to change the document header data for consignment settlement.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899"><st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.2.2</st1:chsdate> P</st1:chsdate>ick-up list: batch where-used list display in MB56(Changed)(2004).<o:p></o:p>

Until now, the top-down and bottom-up analysis in the function pick up list for batch where-used list(MB<st1:chmetcnv w:st="on" tcsc="0" numbertype="1" negative="False" hasspace="False" sourcevalue="5" unitname="C">5C</st1:chmetcnv>) Where only displayed in the form of simple output lists. As of ECC5.0, The function pick-up list for batch where-used list is displayed, in the initial screen. You can use all the setting that are available in the batch where-used list, for example, expand transfer posting or display vendor batch. However it is not possible to limit the selection to valid plants in the initial screen of the pick-up list.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.2.3</st1:chsdate>.1 BAPIs in inventory management (new)(2004).<o:p></o:p>

BAPI_RESERVATION_GETITEMS1 BAPI to read reservation items.<o:p></o:p>

BAPI_RESERVATION_CHANGE   BAPI to change individual reservations.<o:p></o:p>

BAPI_RESERVATION_CREATE1 BAPI to create individual reservations.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.2.4</st1:chsdate>.1 Functional enhancements for transaction MIGO (Changed).(5.0)<o:p></o:p>

For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), you can specify the ordering plant as additional selection criterion directly next to the purchase order number and the item number. As standard, the field for the plant is hidden, to show this field, you must set the plant field to ready for input in IMG.<o:p></o:p>

New default value: copy account assignment fields. When entering other goods receipts, you can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, you set the copy account assignment fields indicator in the default values. You change the default values in the menu settings--> default values.<o:p></o:p>

Goods movements with reference to a material document. When entering the following goods movements, it is possible to specify a matrial document as the reference document: goods receipt/ goods issue/ transfer posting/ remove from storage.<o:p></o:p>

Note that these material documents must be documents that have arisen from a goods movement without reference(“other”) and that are not reversal documents.<o:p></o:p>

Non-inventory managed documentary batches<o:p></o:p>

You can now post goods movement documentary batches and therefore use for these batches the previous batch functions. Documentary batches are not inventory-managed batches with a batch where-used list. All relevant data for a documentary batch appears in MIGO on separate tab pages.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.3.1</st1:chsdate>.1 New report: Display list of invoice documents(New)(2004)<o:p></o:p>

LIV offers you a new report display list of invoice documents(RMMR1MDI), Which you can use to display a list of invoice document. The T-CODE is MIR5.<o:p></o:p>

13.4 Customizing transactions OX01 and OX17 replaced by views.(2005)<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.6.5</st1:chsdate> Buyer Role(New)(2005)<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.6.15</st1:chsdate>.2 New BAPIs in purchasing(New)(2005)<o:p></o:p>

Creation of a scheduling agreement(BAPI_SAG_CREATE).<o:p></o:p>

Changing of a scheduling agreement(BAPI_SAG_CHANGE)<o:p></o:p>

Displaying of details of a purchase scheduling agreement( BAPI_SAG_GETDETAIL).<o:p></o:p>

Maintenance of scheduling agreement delivery schedule lines. (BAPI_SCHEDULE_MAINTAIN).<o:p></o:p>

Creation of a purchase contract (BAPI_CONTRACT_CREATE).<o:p></o:p>

Changing of a purchase contract (BAPI_CONTRACT_CHANGE).<o:p></o:p>

Displaying of detail of a purchase contract (BAPI_CONTRACT_GETDETAIL).<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.6.15</st1:chsdate>.3.2 Mass maintenance of outline agreements(New) (2005).<o:p></o:p>

As of ECC6.0, You can use the mass maintenance functions for outline agreements(contracts and scheduling agreements) in purchasing.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.7.3</st1:chsdate> Service-based commitments in purchasing(NEW)(2005).<o:p></o:p>

As of ECC6.0, service-based commitments are possible in purchasing. The system updates <st1:place w:st="on">PO</st1:place> and requisition commitments per service line. You can display the commitment documents belonging to a purchase order under environment-à AC commitment documents.<o:p></o:p>

Note: if you use service-based commitments for a purchase order, the system must update the <st1:place w:st="on">PO</st1:place> history per service line. The system therefore sets the indicator for service-based invoice verification automatically in the purchase order, you cannot unset the indicator.<o:p></o:p>

Commitment offsetting after <st1:place w:st="on">PO</st1:place> release is not supported for service-based commitments in purchase requisitions. The commitment in the purchase requisition is offset(reduced, cancelled out) when the purchase order is saved.<o:p></o:p>

To able to use this function, you must activate the enterprise extension Public sector. You must have set the Service-based commitment indicator in the follow-on processing for external service items area of customizing for materials management under External services management-àsource determination and default values-àdefine for the clinet.<o:p></o:p>

    <st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.8.6</st1:chsdate>.3 New movement types in inventory management(New)(2005),<o:p></o:p>

The following new movement types are available in inventory management:<o:p></o:p>

107: Goods receipt to valuated GR block stock.<o:p></o:p>

109: Goods receipt from valuated GR block stock.<o:p></o:p>

You can use these two new movement types for an acceptance at origin(origin acceptance), there is a check box in <st1:place w:st="on">PO</st1:place> item delivery view.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.9.2</st1:chsdate> Variance type as sort criterion for invoice items (New).<o:p></o:p>

As of SAP ECC6.0, Invoice processing at the invoice item level has been enhanced by the addition of the variance type field.<o:p></o:p>

The system uses the variance type field to flag possible quantity or price differences in the invoice item in the background. Differences between the goods receipt and purchase order quantities can represent one possible error type. The system is supplied with this preset error type. Further error types can be implemented on a customer-specific basis using BADIs.<o:p></o:p>

You can have the system help you find possible errors in invoice items(in your role as invoice verification clerk, for example) more quickly by sorting faulty items on the basis of the variance type field. The variance type can serve as the starting point for the work of the invoice verification clerk.<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899"><st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.9.3</st1:chsdate> p</st1:chsdate>repayment of invoices(New)(2005)<o:p></o:p>

As of SAP ECC6.0, you can trigger prepayment of vendor invoices in logistics invoice verification. You use the prepayment function for vendors with whom you have a good, long-standing relationship. The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes , and cash discounts in financial accounting in advance. The system execute the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.<o:p></o:p>

Most logistics invoice verification standard functions are not affected by the prepayment function. When the system posts invoices, it continues to execute the standard checks, if the system has already posted the prepayment document. You can only make restricted changes to the header fields of the invoice. To ensure adequate and orderly FI postings, a prepayment clearing account has been added to SAP 6.0, upon prepayment, the system debits this account and then settles the account again after executing the check.<o:p></o:p>

To run this function, must two steps. At first ,must activate by company code for IMG in material management under LIV. Second you must assign a value in vendor master under payment transaction( prepayment)<o:p></o:p>

<st1:chsdate w:st="on" isrocdate="False" islunardate="False" day="30" month="12" year="1899">13.9.6</st1:chsdate>.2 New Business ADD-Ins in logistics invoice verification( New).<o:p></o:p>

 As of SAP ECC6.0, The following new business ADD-ins are available in logistic invoice verification.<o:p></o:p>

MRM_ERS_HDAT_MODIFY BADI to change document header data in evaluated receipt settlement(ERS):<o:p></o:p>

MRM_ERS_IDAT_MODIFY  BADI to change document lines in ERS:<o:p></o:p>

MRM_ITEM_CUSTFIELDS  BADI to change customers’ own fields.<o:p></o:p>