EHP4 Release Note
Release Notes Procurement and Logistics Execution SAP enhancement package 4 for SAP ERP 6.0 Copyright � Copyright 20
Views 273 Downloads 1 File size 322KB
Recommend stories
Citation preview
Release Notes Procurement and Logistics Execution SAP enhancement package 4 for SAP ERP 6.0
Copyright � Copyright 2008 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C�, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Inventory and Warehouse Management ..........................................................4 Business Function Integration Ext. Warehouse Management, Enterprise Services ........................................................................................................4 LOG_ESOA_OPS_3:Integration Ext Whse Mgmt, Ent Services (New) ............................ 4
Business Function EWM Integration with Manufacturing ..............................5 LOG_PP_EWM_MAN: Business Function EWM Integration into Manufacturing.............. 5 LOG_PP_EWM: EWM Integration in the Area of Production and Process Orders (New) . 7 LOG_PP_EWM: EWM Integration in the Area of Repetitive Manufacturing ................... 10 LOG_PP_EWM: EWM Integration with Kanban (New) .................................................. 13
Procurement ..................................................................................................15 Business Function Functional Improvements in MM for EM and ExD.........15 /BEV1/NE_ENH: Functional Improvements in MM for EM and ExD (New)..................... 15
Business Function MM, Multiple Account Assignment ................................16 LOG_MM_MAA_1: Business Function Multiple Account Assignment (New) .................. 16 LOG_MM_MAA_1: Functions for Multiple Account Assignment (New) .......................... 17 LOG_MM_MAA_1: Valuated Goods Receipt and Multiple Account Assignment (New) .. 18 LOG_MM_MAA_1: Account Assignment and Valuated Goods Receipt for Services (New) .................................................................................................................................... 20 LOG_MM_MAA_1: BAPIs for Purchase Requisitions for Services (New) ...................... 21
Business Function Procurement - SRM Integration ....................................22 LOG_MM_P2PSE_1: Procurement - SAP SRM Integration (New)....................... 22 LOG_MM_P2PSE_1: Enhanced BAPIs for Purchase Requisitions (New) ..................... 23 LOG_MM_P2PSE_1: Integration into Embedded Search (new) .................................... 24 LOG_MM_P2PSE_1: Central Contract Management (New).......................................... 25 LOG_MM_P2PSE_1: Manual Sourcing (New) .............................................................. 30 LOG_MM_P2PSE_1: Service Procurement Enhancements .......................................... 31 LOG_MM_P2PSE_1: Business Package for Buyer 1.4 (new) ....................................... 34 LOG_MM_P2PSE_1: Procurement Business Package for ERP and SRM (new) ........... 35 LOG_MM_P2PSE_1: Enhanced BAPIs for Purchase Requisitions (New) ..................... 36
Business Function Serial Numbers in Purchasing ......................................37 LOG_MM_SERNO: Serial Numbers in Purchasing (New) ............................................. 37
Business Function MM, Integration of Materials Management and Financial Accounting ..................................................................................................39 LOG_MMFI_P2P: BF MM, Integration of Materials Management and Financial Accounting ................................................................................................................... 39 LOG_MMFI_P2P: Entering of Down Payment Data in the Purchase Order (New) ......... 40 LOG_MMFI_P2P: Down Payment Clearing (New) ........................................................ 41 LOG_MMFI_P2P: Posting of Retentions (New)............................................................. 42 LOG_MMFI_P2P: Checking of Goods Receipt Date Against Delivery Date (New)......... 44 LOG_MMFI_P2P: Checking of Partner Roles in the Incoming Invoice (New)................. 45 LOG_MMFI_P2P: Follow-On Activities for Completed Purchase Order Items (New)...... 46 LOG_MMFI_P2P: Business Add-In for Displaying Reporting Data (New) ...................... 47 LOG_MMFI_P2P: Stock Removal of Scheduling Agreement Releases (New) ............... 48
Inventory and Warehouse Management Business Function Integration Ext. Warehouse Management, Enterprise Services LOG_ESOA_OPS_3:Integration Ext Whse Mgmt, Ent Services (New) Use As of SAP ECC 6.0, enhancement package 4, Business Function Retail, Integration Ext. Warehouse Management, Enterprise Services (LOG_ESOA_OPS_3), you can enable the use of SAP ERP 6.0 for integrated logistics processes with an external, decentralized warehouse management system (either SAP or non-SAP based). This business function and its associated enterprise service bundle enable the exchange of logistics-relevant information, such as inbound deliveries, outbound deliveries and data related to the movement of goods within a tracking system. They offer replication of product, customer, and supplier master data from SAP ERP to the external warehouse management system. This results in enhanced support of the customer supply and warehouse replenishment processes, triggering recent stock updates in the ERP system. In addition, the accuracy and consistency of stock data streamlines internal processes by: o
Reducing error processing
o
Reducing handling of unexpected goods receipts
o
Avoiding pick denials in outbound processing because of stock inconsistencies between systems
Business Function EWM Integration with Manufacturing LOG_PP_EWM_MAN: Business Function EWM Integration into Manufacturing Use As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), the business function EWM Integration into Manufacturing (LOG_PP_EWM_MAN) is available. This business function enables you to use an SAP Extended Warehouse Management System in conjunction with the ERP system to manage the storage and material staging of components and finished products. With the integration of EWM into the processes of production planning and control, you have the benefit of powerful EWM functions that enable you to optimize the flexibility and transparency of your warehouse. In the integration of EWM with PP, the delivery is used as the document that transfers the information from ERP to EWM. These deliveries are created in the ERP system and distributed to the EWM system. o
o
o
Production and Process Orders In the area of production and process orders, the following functions have been enhanced for the EWM integration: -
Pull list (material staging list) (MF60)
-
Confirmation transactions for production and process orders
-
Cancellation of confirmations
-
Postprocessing of goods movements (COGI)
Repetitive Manufacturing In repetitive manufacturing, the following processes and functions have been enhanced for the EWM integration: -
Final confirmation
-
Reporting point confirmation
-
Decoupled confirmation
-
Document-neutral cancellation
-
Document-related cancellation
-
Pull list (material staging list) (MF60)
Kanban In the Kanban area, the following functions have been enhanced for the EWM integration: You can use EWM-managed storage locations for your kanban processes. All replenishment strategies (in-house production, stock transfer, and external procurement) are supported.
For more information, see the following Release Notes: EWM Integration in the Area of Production and Process Orders EWM Integration in the Area of Repetitive Manufacturing EWM Integration in the Area of Kanban
Effects on Customizing o
To be able to use the ERP system in conjunction with an SAP EWM system, you must make the settings for the basic configuration of the EWM connection in Customizing for the Component Logistics Execution under Extended Warehouse Management Integration. See also: Basic Settings for Integration with Other Components.
o
In the IMG activity Process EWM-Specific Parameters, you must choose the setting ERP with EWM (Extended Warehouse Management) for the warehouse numbers to which you have assigned the storage locations that are to be managed with EWM. As a result of this, all storage locations assigned to the warehouse numbers become EWM-managed storage locations.
o
You make the settings for EWM Integration into Production Planning and Control in Customizing for the component Logistics Execution under Extended Warehouse Management Integration --> Production Planning and Control -->Define Determination of Delivery Type.
See also For more information, refer to the SAP Library under Business Function Sets and Business Functions --> Enterprise Business Functions --> Logistics --> Prduction Planning and Control --> EWM Integration into Manufacturing and under Logistics --> Logistics Execution (LE) --> Integration of Extended Warehouse Management.
LOG_PP_EWM: EWM Integration in the Area of Production and Process Orders (New) Use As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), Business Function EWM Integration into Manufacturing (LOG_PP_EWM_MAN), you can use an SAP EWM system in conjunction with production and process orders. You can manage both your finished products and assemblies as well as the components in EWM-managed storage locations. Processes The most important processes that can be executed with EWM are: o
Material staging If you use EWM for material staging, the system generally generates production supply deliveries as replenishment elements. The storage location you have assigned to the production supply area can be EWM- or MM-IM-managed. You can carry out the material staging using the following transactions: -
Staging of pick parts for certain production or process orders (transactions CO02 and COR2).
-
Staging of release order parts and pick parts for certain planned orders, production and process orders (transaction MF60).
o
Confirmation of production and process orders In conjunction with EWM, you can use all confirmation transactions at the level of the order header and the operations. When you save the confirmation, the system generates a delivery for the confirmed materials. This delivery is automatically replicated in the EWM system. The goods receipt for the confirmed materials is posted for this delivery in the EWM system. This information is automatically transferred to ERP. The ERP system generates a material document and posts the goods movements. The goods issue posting for the components is carried out automatically.
o
Cancellation of confirmation with reference to confirmation document (CO13/CORS) When you cancel a confirmation, the ERP system automatically cancels the delivery that was previously generated at the time of confirmation. You now only need to cancel the goods receipt in the EWM system. The goods issue posting for the components, which is carried out automatically after a confirmation, is automatically reversed when the confirmation is cancelled.
o
Postprocessing of faulty goods issue postings (COGI)
o
UI Enhancements
Confirmation In the Display Confirmation transaction (CO14/CORT), the delivery number that the system created at the time of the confirmation is displayed. On the Goods Movements screen, the Overview of Goods Movements has been enhanced through the addition of the Delivery column. By double-clicking on the delivery number, you can display the delivery. As soon as the goods receipt of the confirmed materials has been posted in the EWM system, you can display the number of the material document that ERP generated for this. In transaction CO14, you can display all documents for the goods movements carried out in EWM and ERP. To gain an overview of all material documents, starting from the Display Confirmation for Production
Order: Actual Data screen, choose the menu option Goto --> Administration and then the Material Documents pushbutton. In this way you can check the status of the confirmation across systems. The functions Goods Movements with Errors and Intended Goods Movements are also available for the EWM-managed materials. o
Control cycle for material staging To facilitate material staging with EWM, the control cycle for production supply has been enhanced. You must now not only enter a destination but also a source in the control cycle. -
Destination The system automatically determines the storage location and warehouse number for the destination from the production supply area for which you are creating the control cycle. You only have to specify the Material Provision indicator. This specifies whether a pick part or a release order part is involved.
Source You must specify the issuing storage location. The issuing plant is preset by the system because it must be the same as the plant of the destination storage location. The source storage location must be EWM-managed. All processing and display transactions for control cycles have been adjusted to enable you to process and display EWM control cycles. In the list of control cycles (transaction LS41), the Control Cycle Status column has been extended to include the following control cycle categories: -
o
-
E: Control Cycle for EWM This control cycle category indicates that the source and destination that you specify in the control cycle are EWM-managed.
-
B: Control Cycle EWM-IM This control cycle category indicates that the source is EWM-managed and the destination is MM-IM-managed
Pull list (material staging list) (MF60) The initial screen of the pull list has been enhanced through the addition of the following fields: -
EWM Release Order Parts
-
EWM Pick Parts
In the table of replenishiment elements, there are two new categories for replenishment elements: -
EWMKOM for pick parts
-
EWMABR for release order parts In the background a delivery is generated for both, which is created after saving.
In addition, two new views have been added to enhance the menu in the material staging list: -
If you choose View --> Other View --> EWM Pick or EWM Release Order, the system displays only the missing quantity situation and the replenishment elements of the selected category.
Restrictions o
The technical completion of a production order is not possible until there are no open consumption deliveries for that order.
Effects on Customizing You make the Customizing settings for these functions in Customizing under Define Determination of Delivery Type. In this new IMG activity, you define the delivery types and movement types for the above-mentioned processes. See also For more information, refer to the central Release Note for the business function LOG_PP_EWM_MAN: EWM Integration into Manufacturing.
LOG_PP_EWM: EWM Integration in the Area of Repetitive Manufacturing Use As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604) , Business Function EWM Integration into Manufacturing (LOG_PP_EWM_MAN), you can use an SAP EWM system in conjunction with repetitive manufacturing. You can manage the finished product (assembly) with EWM. The components must all be managed with the component MM-IM or LE-WM.
-
Processes
The following repetitive manufacturing processes are supported in conjunction with EWM: o
Final confirmation In conjunction with SAP EWM, the processing steps that the system runs through in the case of final confirmation change. See also: Process of Final
Confirmation with EWM The document log information (transaction MF12) has been enhanced for final confirmation with EWM by the following: -
After the confirmation, the delivery and item numbers that the system has created for the confirmed finished products are displayed. You can display the delivery by double-clicking on the delivery number. To be able to display this new data in the document log information, you must change the layout of the latter. In the standard system, the Delivery and Item fields are hidden.
-
After the goods receipt posting in the SCM system, the ERP system has created a material document for the goods receipt. In the document log information, a new line is displayed for this material document. The number of this document is displayed together with the new indicator Processing Type L (Confirmation for EWM Delivery). You can display the material document by double-clicking on the material document number.
o
Decoupled confirmation In the case of a decoupled confirmation, the system posts only the goods receipt at the time of the confirmation, and reduces capacities. Depending on the setting in the process control profile, all other functions are earmarked in a worklist. When you perform the decoupled confirmation with EWM, this process changes. In conjunction with EWM, at the time of confirmation, the system generates an inbound delivery for the confirmed finished products. The inbound delivery is automatically replicated in the EWM system. In the EWM system, you can specify whether or not a goods receipt is to be posted automatically for the delivery. In the standard system, immediate GR posting is preset. In this case, EWM immediately posts the goods receipt for the finished product. In the ERP system, you then manually post the goods issue for the components plus the production activities.
o
Document-neutral cancellation The processing steps that the system performs in the case of a documentneutral cancellation also change if an EWM system is used: Document-neutral cancellation is the reversal of the final confirmation process. Here, all goods movements are reversed. In this case, the ERP system generates a correction delivery (outbound delivery) for the confirmed finished product. On the basis of this correction delivery, all quantities and activities are posted back. However, the ERP system cannot update the planned orders after
cancellation. o
o
Document-related cancellation In transaction MF41 (Repetitive Manufacturing --> Data Entry --> Cancel) or MF12 (Repetitive Manufacturing -> Data Entry -> Evaluations -> Data Entry Documents), you can choose and cancel a material document for a finished product. The ERP system then generates a cancellation document for the finished product. The system determines the quantity to be cancelled from the material document. At the same time, the ERP system generates a correction delivery (outbound delivery) for the finished product. This correction delivery is automatically replicated in EWM and the goods issue posted. This posting triggers the following in the ERP system: -
Goods issue posting for the finished product
-
Goods receipt posting for components For this, ERP adopts the quantities from the material document.
-
The production activities are reset.
-
The LIS is reset.
-
The planned orders are updated.
-
Finally, the ERP system generates a document log containing all current documents.
Material staging The following changes result with regard to the master data for material staging in connection with an EWM system: -
Production supply area (PSA) The storage location you assign to the PSA must be MM-IM-managed.
-
Control cycle The control cycle is enhanced inasmuch as you must now specify the destination and source of the components. Destination: The system automatically determines the storage location and the warehouse number for the destination from the PSA for which you are creating the control cycle. You only have to specify the material provision indicator. This stipulates whether a pick part or a release order part is involved. Source: You must specify the issuing plant and the issuing storage location. The plant must be the same as the plant of the destination storage location. This storage location must be EWM-managed.
There are the following enhancements to the pull list (material staging list) (MF60): -
The initial screen has been enhanced by the addition of the following fields:
EWM Release Order Parts EWM Pick Parts -
In the table of replenishment elements, there are two new categories of replenishment elements: EWMKOM for pick parts EWMABR for release order parts In the background a delivery is created for both categories.
-
New views: In the pull list, you can switch the view by choosing the following menu options: View --> Other View --> EWM Pick or EWM Release Order
For more information on material staging in conjunction with an SAP EWM system, refer to the SAP Library under Repetitive Manufacturing --> Pull List --> Execution of Material Staging --> Trigger Replenishment --> Trigger Replenishment via EWM.
-
Restrictions
In the case of confirmations of planned orders in repetitive manufacturing, only the finished product can be stored in an EWM-managed storage location. The components must be withdrawn from an MM-IM- or WM-managed storage location.
Effects on Customizing You make the Customizing settings for these functions in Customizing under Define Determination of Delivery Type. In this new IMG activity, you define the delivery types and movement types for the above-mentioned repetitive manufacturing processes. See also For more information, refer to the central Release Note for the business function EWM
Integration into Manufacturing.
LOG_PP_EWM: EWM Integration with Kanban (New) Use As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604) , Business Function EWM Integration into Manufacturing (LOG_PP_EWM_MAN) , you can use an SAP EWM System in conjunction with Kanban. Kanban in conjunction with EWM generates a delivery as replenishment element. The storage locations assigned to a production supply area can be EWM- or MM-IMmanaged. The source from which the replenishment is withdrawn must be EWMmanaged.
o
o
Processes
The following kanban processes with EWM are available: -
Process with single-step stock transfer
-
Process with 2-step stock transfer
-
Processes with external procurement
-
Processes with in-house production
Goods Issue from Kanban for Cost Center -
New Stock Transfer Strategy
For the process with stock transfer, the new stock transfer strategy 0007 Stock Transfer with Delivery (EWM) is supplied. To be able to use Kanban with stock transfers, you must make the following settings on the Stock Transfer tab page in the controly cycle: o
Stock transfer strategy: 0007
o
Storage location (source) The source storage location must be EWM managed.
With this stock transfer strategy, information on the delivery is shown on the kanban board(transaction PK13N): If you set a kanban to Empty on the kanban board, the system automatically generates a new replenishment element. In this case, this is an outbound delivery. In the kanban information, the number of the outbound delivery is shown in the Delivery field. You can use the Display Replenishment function key to access the overview of this outbound delivery. Restrictions: o
Scenarios with MM-IM- or WM-managed storage locations as the source of the replenishment together with a PSA whose storage location is EWM- managed are not supported.
o
In the case of the in-house production strategies for Kanban with planned orders or cost collectors, you must note that only the finished product can be stored at EWM-managed storage locations. The components can only be withdrawn from MM-IM-managed storage locations.
o
In the case of the external procurement strategies, you cannot use processing with scheduling agreement delivery schedule lines and processing the summarized JIT call.
Effects on Customizing You make the Customizing settings for this function in Customizing at the following points: o
Define Determination of Delivery Type In this new IMG activity, you define the delivery types and movement types for the following kanban processes: Single-step stock transfer Two-step stock transfer, goods receipt from stock in transit Two-step stock transfer, goods issue to stock in transit Goods issue from kanban for cost center
o
Define Stock Transfer Strategies In EHP4, there is the new stock transfer strategy: 0007 Stock Transfer with Delivery (EWM) This stock transfer strategy is supplied in the standard system. In the standard stock transfer strategy, only the control type is preset: Delivery from an EWMControlled Storage Location. The customer can make the setting 311 (stock transfer in plant) in the Movement Type field for single-step stock transfer. If you do not enter anything, the system automatically uses 311 and carries out a single-step stock transfer. See: Kanban Process with One-Step Stock Transfer. However, you can also specify the movement type 313 (UL Rem.fm Storage to SLoc). You use this movement type in the case of a two-step stock transfer. The 2-step stock transfer always makes sense if the warehouse and production are spatially separated.
See also For more information, refer to the central Release Note for the business function LOG_PP_EWM_MAN: EWM Integration into Manufacturing.
Procurement Business Function Functional Improvements in MM for EM and ExD /BEV1/NE_ENH: Functional Improvements in MM for EM and ExD (New) Use As of SAP ECC 6.0, Enterprise Extension CP, Enhancement Package 4 (EA-CP 604), business function Functional Improvements in MM for EM and ExD (/BEV1/NE_ENH), you can use Empties Management and Excise Duty with an optimized range of functions specially for customers in the beverage industry. Empties Management Up to now, it was not possible in Empties Management in Purchasing to manage and display empties movements and empties balances for each vendor (empties account per vendor). The following functional improvements are now available: o
Improved tracking of the value-based and quantity-based empties movements that take place between a customer and vendor.
o
Improved tracking of the corresponding empties balances within a freelydefinable time period. You could previously only do this in Sales and Distribution, but it is now also possible in Purchasing.
o
Archiving of the empties information in Purchasing.
Excise Duty Up to now, you could only use the the standard transactions to process the excise duty data for each material in the material master (Create, Change, Display Material; MM01/MM02/MM03). There are now lists provided for processing this data for multiple materials at a time. Existing transactions have been repositioned as follows in the SAP Easy Access menu under Logistics -> Materials Management -> Excise Duty o
List of Materials (/BEV2/EDL1) -> Functions -> Overview -> List of Materials
o
Client (/BEV2/EDM1) -> Master Data-> Material -> Client
o
Company Code (/BEV2/EDM2) -> Master Data-> Material -> Company Code
o
Plant (/BEV2/EDM3) -> Master Data-> Material -> Plant
Effects on Existing Data The following user interface elements are new:
Transaction
Program/Screen
UI Element
/BEV1/NE_LISTBALPO
/BEV1/NE_LISTBALPO
Selection screen
and display of the selected data
Business Function MM, Multiple Account Assignment LOG_MM_MAA_1: Business Function Multiple Account Assignment (New) Use As of SAP enhancement package 4 for SAP ERP 6.0 (SAP_APPL 604), materials management provides new functions for multiple account assignment. These new functions include the following options: distribution of document items by amount, multiple account assignment for planned delivery costs, and the use of multiple account assignment together with valuated goods receipt. In addition, you can use multiple account assignment for service items as well as material items. For more information, see the following release notes: o
MM_604_MAA1_NEWFUNC: Functions for Multiple Account Assignment (New)
o
MM_PUR_604_MAA1_BEWE: Valuated Goods Receipt and Multiple Account Assignment (New)
o
MM_SRV_604_MAA1_BEWE: Account Assignment and Valuated Goods Receipt for Services (New)
o
MM_SRV_604_MAA1_BAPI: BAPIs for Purchase Requisitions for Services (New)
LOG_MM_MAA_1: Functions for Multiple Account Assignment (New) Use As of SAP enhancement package 4 for SAP ERP 6.0 (SAP_APPL 604) business function MM, Multiple Account Assignment (LOG_MM_MAA_1), the following new functions for multiple account assignment are available: o
Amount-based distribution even for very small amounts In addition to percentage and quantity-based distribution, you can now also use amount-based distribution, and thereby distribute the total value of a purchase requisition item or purchase order item to the individual account assignments. The system also includes very low values that have been assigned to an account assignment. You can use amount-based distribution for the procurement of materials and services.
o
Distribution of delivery costs to multiple account assignments Previously, it was not possible to use multiple account assignment for planned delivery costs for the material items. Provided that you create or change purchase orders with transactions ME21N and ME22N, the system also distributes planned delivery costs to the account assignments on a quantity, percentage, or amount basis, exactly as defined by the distribution key of the item. It is not possible to distribute delivery costs in a different way to the associated material item. You can display the distribution of delivery costs in the item detail data. In the commitment interface, the system distributes the delivery costs to the same account assignment items as the associated material costs. You can use both quantity-based and value-based commitment management. Note: For delivery costs with multiple account assignment, you cannot run goods-receipt-based invoice verification.
o
Multiple account assignment and valuated goods receipt Previously, you could only use non-valuated goods receipt when creating items that you wanted to distribute to different account assignments in purchase requisitions and purchase orders. Now you can also use multiple account assignment for those purchase requisition items and purchase order items where you expect a valuated goods receipt.
Constraint You cannot use multiple account assignment in stock transport orders.
Effects on Existing Data The following changes have been made to the user interface: When creating, changing, and displaying purchase requisitions (transactions ME51N, ME52N, and ME53N) and purchase orders (transactions ME21N, ME22N, and ME23N), the Account Assignment tab page in the item detail data contains the new entry Amount-Based Distribution in the Distribution selection field (program SAPLMEACCTVI, screen 1000).
LOG_MM_MAA_1: Valuated Goods Receipt and Multiple Account Assignment (New) Use Previously, you could only use non-valuated goods receipt when creating items that you wanted to distribute to different account assignments in purchase requisitions and purchase orders. As of SAP enhancement package 4 for SAP ERP 6.0 (SAP_APPL 604), business function MM, Multiple Account Assignment (LOG_MM_MAA_1), you can also use multiple account assignment for purchase requisition items and purchase order items where you expect a valuated goods receipt. The system then distributes the value of the goods receipt item to the individual account assignments, and posts the value for each account assignment item to the GR/IR clearing account. o
When posting a valuated goods receipt for a purchase order (transaction MIGO or MB01, movement type 101), the system distributes it to the account assignments that you defined in the purchase order. You can change this distribution with the Business Add-In BAdI: Multiple Account
Assignment � Redistribution in Goods Receipt (MB_ACCOUNTING_DISTRIBUTE), but you cannot change the selected account assignment category or the account assignments. o
The valuation of the goods receipt and the distribution to the account assignments depends on the portion of the ordered quantity for which you have already entered invoices. Depending on this, the goods receipt quantity is valuated with the net price of the purchase order or the invoice price.
o
When you create the purchase order, you can use the partial invoice indicator to define whether the value of the goods receipt items in partial goods receipts is distributed to the individual account assignments proportionally or on a progressive fill-up basis.
o
In the case of overdeliveries, the system first distributes the purchase order quantity to the account assignment items before distributing the overdelivered quantity proportionally according to your specifications in the purchase order.
o
In the case of return deliveries and returns, the system always distributes the value proportionally on the basis of the partial goods receipts posted so far. You can use the BAdI MB_ACCOUNTING_DISTRIBUTE to change this distribution. In the case of reversals, the system distributes the value according to the specifications in the material document to be reversed.
o
The commitment update takes place at the time of goods receipt with the distribution to account assignments defined there.
o
When you enter the invoice (transaction MIRO or MIR7), the system determines default values (quantity and amount) from the data of the purchase order (purchase order quantity and purchase order price) and the purchase order history (goods receipt quantity and invoice quantity) for the document items and account assignment items. You can use the BAdI BAdI: Get Default Values (MRM_PROPOSAL_DETERMINE) to implement customer-specific logic for determining the default values.
o
The system automatically distributes the invoice quantity or amount to the account assignments, and displays quantities and amounts for the individual account assignment on the multiple account assignment screen. You can use the BAdI BAdI: Distribution of Total Quantity and Amount to Multiple Account Assgmts (MRM_DISTRIBUTION_MAAS) to replace this distribution with customer-specific distribution logic.
o
You can use multiple account assignment and valuated goods receipt when creating purchase requisitions and purchase orders for items of item category: Standard and Service. With items of category Standard, you can order materials with or without a material number, which you can describe in more detail in a purchase order text. For more information about valuated goods receipts for service items, see the release note Account Assignment and Valuated Goods Receipt for Services (New).
Constraints o
Valuated goods receipts with multiple account assignments are not supported in the subcontracting process.
o
Valuated goods receipts with multiple account assignments are not supported into blocked stock (movement type 107) or from blocked stock (movement type 109).
Effects on Existing Data In transaction MIGO, you can use the Account Assignment tab page of the item details to display the distribution of the item values for a material document to the account assignments.
See also For more information about valuated goods receipts with multiple account assignment, see the Inventory Management (MM) component of SAP Library, under Inventory Management and Physical Inventory (MM-IM) --> Goods Receipt --> Goods Receipts for Purchase Orders --> Entering a Goods Receipt with Multiple Account Assignment.
LOG_MM_MAA_1: Account Assignment and Valuated Goods Receipt for Services (New) Use Previously, with multiple account assignment for service items you could only choose distribution by quantity or distribution on a percentage basis. If you changed the item quantity, the account assignment quantity had to be adjusted manually. As of SAP enhancement package 4 for SAP ERP 6.0 (SAP_APPL 604), business function MM, Multiple Account Assignment (LOG_MM_MAA_1), multiple account assignment with amount-based distribution to account assignments is available for service items. Now you can use amount-based distribution in service items, to distribute the total amount exactly to the individual account assignments. For each service item in a purchase order, the system provides a service entry sheet and an invoice with all the related account assignments for the service item. The system displays the distribution of the total amount and the quantity among the individual account assignments. You can change the distribution of the total amount. If you change the amounts or quantities of the document items in the service entry sheet or purchase order/purchase requisition, the system automatically adjusts the relevant account assignments proportionally. If the automatic reallocation of the changed amounts leads to rounding differences, the system also automatically allocates the rounding differences to the account assignment with the highest amount. If several account assignments have the same highest amount, the first account assignment item has the rounding difference added to it. In addition, you can post an invoice for a purchase order that is assigned to multiple accounts, for which a valuated goods receipt has taken place. For more information about valuated goods receipts with multiple account assignment, see release notes Valuated Goods Receipt and Multiple Account Assignment (New) and Functions for Multiple Account Assignment (New). Effects on Existing Data In the transactions for creating, changing, and displaying purchase orders (ME21N, ME22N, and ME23N) and purchase requisitions (ME51N, ME52N, and ME53N), and when entering service entry sheets (ML81N), program SAPLMLSK (multiple account assignment screen 200) provides the following new fields for amount-based distribution: Net Value of Item, Currency Key, and Distribution Indicator.
LOG_MM_MAA_1: BAPIs for Purchase Requisitions for Services (New) Use As of SAP enhancement package 4 for SAP ERP 6.0 (SAP_APPL 604), business function MM, Multiple Account Assignment (LOG_MM_MAA_1), you can also use the BAPIs BAPI_PR_CREATE and BAPI_PR_CHANGE to create and change purchase requisitions for services. The BAPIs use the functionality of the Enjoy purchase requisition (transaction ME51N/ME52N). For both BAPIs, you can use the following customer exits of enhancement MEREQ001 and the following Business Add-Ins (BAdIs): o
Enhancements for Processing Enjoy Purchase Requisitions
o
BAdI: Adopt Header Text When Copying Purchase Requisitions
o
BAdI: Define Follow-On Processing for Purchase Requisitions
o
BAdI: Activate Requisition Commitment Update from Other Applications
o
BAdI: Check for Commitment Relevance of Purchase Requisitions
o
BAdI: Customer BAdI for Purchase Requisition BAPIs
When the BAPIs are called, the following authorization objects are used: o
M_BANF_BSA Document type in purchase requisition
o
M_BANF_EKG Purchasing group in purchase requisition
o
M_BANF_EKO Purchasing organization in purchase requisition
o
M_BANF_WRK Plant in purchase requisition
o
M_BANF_LGO Storage location in purchase requisition
Business Function Procurement - SRM Integration -
LOG_MM_P2PSE_1: Procurement - SAP SRM Integration (New)
Use As of SAP ECC 6.0, enhancement package 4 (SAP_APPL 604), you can use the business function Procurement - SAP SRM Integration (LOG_MM_P2PSE_1). This business function enables you to structure procurement processes in SAP ERP and SAP SRM more efficiently. The following functions are available in this business function: o
Integration in the embedded search You can use the embedded search to search for several purchasing documents (for example, purchase order or scheduling agreement). See LOG_MM_P2PSE_1: Integration into Embedded Search
(New) o
Central contract from SAP SRM as a source of supply The buyer enters and edits the contract data in SAP SRM. On saving, the data is transferred from there to SAP ERP, and is then available for sourcing in both systems. See LOG_MM_P2PSE_1: Central Contract Management (New)
o
Enhancements in external service procurement Buyers can now send purchase requisitions with hierarchical service lines to SAP SRM for sourcing. See LOG_MM_P2PSE_1: Service Procurement Enhancements
(New) oManual sourcing Buyers can now use different types of manual sourcing in combination with SAP SRM. Various processes for sourcing optimize vendor selection. See LOG_MM_P2PSE_1: Manual Sourcing (New) oEnhancements to the roles Buyer, Operational Buyer, and Strategic Buyer These roles have been adjusted in SAP NetWeaver Portal (Business Package for Buyer 1.4 and Procurement Business Package for SAP ERP & SAP SRM 7.0). See LOG_MM_P2PSE_1: Business Package for Buyer 1.4 (New) and LOG_MM_P2PSE_1: Procurement Business Package for
ERP and SRM (New) oBAPIs for purchase requisitions You can now also process bills of material and service items. See LOG_MM_P2PSE_1: Enhanced BAPIs for Purchase
Requisitions (New) See also For more information, see SAP Library for on SAP Help Portal at http://help.sap.com under Business Function Sets und Business Functions -> Enterprise Business Function -> Logistics.
LOG_MM_P2PSE_1: Enhanced BAPIs for Purchase Requisitions (New) Use As of SAP enhancement package 4 for SAP ERP 6.0, business function Purchasing - SAP SRM Integration (LOG_MM_P2PSE_1), you can use the following BAPIs to process bills of material and service items: o
BAPI_PR_CREATE
o
BAPI_PR_CHANGE
o
BAPI_PR_GETDETAIL
You can use the following enhancement objects for BAPIs BAPI_PR_CREATE and BAPI_PR_CHANGE: o
SAP enhancement MEREQ001
o
Business Add-Ins -
ME_PROCESS_REQ_CUST � Enhancements for processing Enjoy purchase requisitions
-
ME_REQ_HEADER_TEXT � Copy header text of Enjoy purchase requisition
-
ME_REQ_POSTED � Purchase requisition posted
-
ME_REQ_OI_EXT � Commitment update for external purchase requisitions
-
ME_COMMTMNT_REQ_RE_C � Check commitment relevance of purchase requisitions
-
ME_BAPI_PR_CUST � BAPIs for Enjoy purchase requisitions
When the BAPIs are called, the following authorization objects are used: o
M_BANF_BSA Document type in purchase requisition
o
M_BANF_EKG Purchasing group in purchase requisition
o
M_BANF_EKO Purchasing organization in purchase requisition
o
M_BANF_WRK Plant in purchase requisition
o
M_BANF_LGO Storage location in purchase requisition
See also For more information, see the central release note for the business function Materials Management Purchasing (LOG_MM_CI_2).
LOG_MM_P2PSE_1: Integration into Embedded Search (new) Use As of SAP ECC 6.0, enhancement package 4, business function Procurement - SRM Integration (LOG_MM_P2PSE_1), you can use Embedded Search to search for the following purchasing documents: oPurchase orders oPurchase requisitions o
Contracts
o
Goods receipts
o
Service entry sheets
o
Request for quotations
o
Scheduling agreements
In order to be able use Embedded Search with the above business objects, the business function Embedded Search in SAP ERP (ERP_ENTERPRISESEARCH) must be activated; you must also have activated the relevant business objects in the Enterprise Search Cockpit. You can do this by choosing Tools -> Administration -> Monitor -> Search Engine -> Enterprise Search Cockpit.
Effects on Customizing You make the Customizing settings for this function in Customizing for Purchasing: o
You can index purchase requistions that were created from MRPs run into Embedded Search in Customizing activity Integrate Purchase Requisitions into Embedded Search.
o
The Business Add-In (BAdI) Integration of Embedded Search into POWL is available. It allows you to enhance the integration of Embedded Search into the POWL feeder classes of the portal role Buyer version 1.4. The following POWL feeder classes support Embedded Search: -
CL_MMPUR_UI_FEEDER_PR
-
CL_MMPUR_UI_FEEDER_PO
-
CL_MMPUR_UI_FEEDER_OA
-
CL_MM_POWL_IM_PROCESS
-
CL_MM_POWL_IM_RECEIVE
-
CL_MM_POWL_SRV_SES
-
CL_MM_POWL_SES_RECEIVE
See also For more information, see the main release note for business function Procurement - SRM Integration (LOG_MM_P2PSE_1).
LOG_MM_P2PSE_1: Central Contract Management (New) Use As of SAP enhancement package 4 for SAP ERP 6.0, (SAP_APPL 604), business function Purchasing - SAP SRM Integration (LOG_MM_P2PSE_1), you can use an SRM central contract as the source of supply for materials and services in the ERP system. You have the following options with this function: o
SRM central contract as source of supply in SAP ERP The SRM central contract is distributed to the relevant ERP purchasing organizations and can be used in SAP ERP as a source of supply. When the contract is replicated in SAP ERP, hierarchy information, release value, and customer fields are included. The central contract is taken into account in the following situations: -
Manually in purchase requisitions or purchase orders In a purchase order, you can have several items with ERP and SRM sources of supply, for example info record and SRM central contract. For purchase requisitions that refer to a central contract, you must use the following transactions: Create (ME51N), Change (ME52N), and Display (ME53N). For purchase orders that refer to a central contract, you must use the following transactions: Create (ME21N), Change (ME22N), and Display (ME23N).
-
When assigning sources of supply to purchase requisitions
-
Automatically when processing and assigning sources of supply for purchase requisitions
-
In the source list
-
In the MRP planning run Sourcing for the planning run takes central contracts into account when creating purchase requisitions.
-
In the planned order
o
Customer-specific input help for central contracts When manually assigning central contracts as a source of supply, you can select the central contract from the input help or enter it directly.
o
Current prices and conditions from SAP SRM When you create purchase orders with reference to a central contract, the current prices and conditions are determined from SAP SRM. Since SRM pricing is executed, ERP pricing is not required.
o
Display of contract data You can display the data of the SRM contract in transaction ME33K. The contract cannot be changed in the transaction for changing contracts (ME32K). In purchasing documents, you can navigate to the data of the central contract, starting from the ERP or SRM contract number.
o
Release documentation in SAP SRM When you save or release purchase orders in SAP ERP, the release data is transferred to SAP SRM and the release documentation of the SRM central contract is updated.
o
Archiving The replicated central contract is archived in SAP ERP.
The role of the buyer has been extended by the addition of the central contract
functions in Business Package for Buyer 1.4. In addition, there is a new, harmonized Procurement Business Package for SAP ERP & SAP SRM 7.0. For more information, see the release note for the Business Package for Buyer 1.4. For more information, see the release note Procurement Business Package for SAP ERP & SAP SRM on the SAP Service Marketplace under http://service.sap.com/support under Release and Upgrade-Info -> Release Notes -> SAP Solutions -> SAP Supplier Relationship Management (SAP SRM) -> Release Notes SAP SRM 7.0.
Effects on Existing Data Note the following changes to the user interface:
Transaction
Program/Screen
UI Element
ME21N, ME22N, ME23N
SAPLMEGUI / 1212
New fields:
(Grid structure MEPO1211GRID) SRM_CONTRACT_ID, SRM_CONTRACT_ITM ME21N, ME22N, ME23N
Function group V69A/Screen 6201
New
pushbutton: CCM info ME51N, ME52N, ME53N
SAPLMEGUI/3212
New fields:
(Grid structure MEREQ3211GRID) SRM_CONTRACT_ID, SRM_CONTRACT_ITM ME51N, ME52N, ME53N, and ME56/ME57 (ALV)
SAPLMEGUI/3326 (Grid structure MEREQ3326)
New fields: VALID_FROM VALID_TO
HIERARCHY_EXISTS
THRESHOLD_EXISTS DESCRIPTION RELEASE_DATE
PAYMENT_TERMS CREATION_DATE REL_VALUE TARGET_VALUE REL_QUANTITY
TARGET_QUANTITY
SRM_CONTRACT_ID
SRM_CONTRACT_ITM ME51N, ME52N, ME53N, and ME56/ME57 (ALV)
SAPLMEGUI/3322
New fields:
SRM_CONTRACT_ID
SRM_CONTRACT_ITM DESCRIPTION
HIERARCHY_EXISTS New UI to display:
SAPLMEGUI/1250
New structure
CC1250 Central contract data (in
Changed fields:
transaction ME33K or by
CC1250-NAME1
double-click on ERP or SRM
CC1250-
CREATE_DATE contract number in requisition and PO) New UI to display central contract data
SAPLMEGUI/1410
New structure
CC1410 Fields with changed texts: CC1410-EBELP, CC1410-EBELP ME01, ME03
SAPLMEOR/205
New fields:
SRM_CONTRACT_ID
SRM_CONTRACT_ITM ME01, ME03
SAPLMEOR/202
New fields:
SRM_CONTRACT_ID
SRM_CONTRACT_ITM ME05
SAPLMEOR/ALV list (Grid structure MERE_OUTTAB_ME05) New fields:
SRM_CONTRACT_ID
SRM_CONTRACT_ITM ME11, ME12, ME13
SAPLMEOR/230
New fields:
SRM_CONTRACT_ID
SRM_CONTRACT_ITM ME01, ME03
SAPLMEOR/502
New fields:
(Switched version of SRM_CONTRACT_ID screen 501, menu: Change -> SRM_CONTRACT_ITM Selections -> Flag Selection) Screen is called from function module
SAPLMEQR/500
New fields: ME_SEARCH_SOURCE_OF_SUPPLY SRM_CONTRACT_ID (for example, in transaction MD14) SRM_CONTRACT_ITM MD02; MD03
SAPMM61X/820
(In simulation mode, can be
SRM_CONTRACT_ID
New fields:
changed in detail data of MRP element SRM_CONTRACT_ITM purchase requisition.) MD02; MD03
SAPMM61X/815
(In simulation mode, can be SRM_CONTRACT_ID changed in detail data of MRP element SRM_CONTRACT_ITM
New fields:
planned order.) MD11, MD12, MD13
SAPML61O/713
New fields:
SRM_CONTRACT_ID
SRM_CONTRACT_ITM MD14
SAPLM61H/210
New fields:
SRM_CONTRACT_ID
SRM_CONTRACT_ITM
Effects on System Administration As of SAP SRM 7.0, you can use the central contract and distribute to SAP ERP. This new contract type in SAP SRM covers and replaces the local contract and the global outline agreement. If you have distributed global outline agreements from SAP SRM to SAP ERP in older releases (earlier than SAP SRM 7.0 and SAP ECC6.0, EHP 4), then you must migrate the corresponding contracts in SAP ERP and SAP SRM. For more information, see the documentation of the migration report MMBSI_CONTRACT_MIGRATION. Effects on Customizing Define the following settings in Customizing: o
Assign the ERP condition types to the SRM condition types in Customizing for Integration with Other SAP Components under Supplier Relationship Management -> Central Contract -> Assignment of Conditions.
o
For purchase order items with reference to a central contract, in Customizing for Integration with Other SAP Components under Supplier Relationship Management -> Central Contract -> Pricing, define the point in time when the current prices in SAP SRM are queried.
o
If ERP and SRM number ranges for contracts are identical, you can use BAdI BADI_MMBSI_SELECT_CTR_ID to define which contract is to be used.
See also For more information, see the release notes Procurement Basics and Harmonization of Global Outline Agreement (GOA) and Local SAP SRM on the SAP Service Marketplace under http://service.sap.com/support under Release and UpgradeInfo -> Release Notes -> SAP Solutions -> SAP Supplier Relationship Management (SAP SRM) -> Release Notes SAP SRM 7.0.
LOG_MM_P2PSE_1: Manual Sourcing (New) Use As of SAP enhancement package 4 for SAP ERP 6.0, business function Purchasing SAP SRM Integration (LOG_MM_P2PSE_1), you can use different types of manual sourcing in combination with SAP SRM. Purchasers can use this function to control the procurement process better for purchasing. Various processes for sourcing optimize vendor selection: o
Creation of a bid invitation from the ERP purchase requisition With this option, you can bundle purchase requisitions and then directly create a bid invitation for sourcing in SAP SRM and send it to several vendors.
o
Central sourcing processing With this option, you can control sourcing in your purchasing processes centrally. In the Collectively Process Purchase Requisitions Web application, you can bundle purchase requisitions from different areas and forward them from there to central sourcing in SRM.
The direct connection between the purchase requisition and the central follow-on documents ensures greater transparency in the purchase process. For example, you can track the current status of your request for quotation and make any necessary changes, such as changes to quantities or the deletion of an item. Effects on Existing Data There are no significant effects on the dataset. Effects on Customizing You can implement the functions for sourcing by using BAdI Activate Sending of
Purchase Requisition to External Procurement System (ME_REQ_SOURCING_CUST). This BAdI is available as an IMG activity under the following path: Materials Management -> Purchasing -> Portal -> Business Add-Ins for the Purchasing Portal.
LOG_MM_P2PSE_1: Service Procurement Enhancements Use As of SAP ECC 6.0, Enhancement Package 4, Business Function Procurement - SRM Integration (LOG_MM_P2PSE_1), you can use an enhanced purchasing process in SAP ERP that enables purchase requisitions with a hierarchical service line structure to be transferred to SAP SRM for sourcing. This allows the purchaser to take advantage of hierarchies when using advanced sourcing functions such as sourcing rules and RFx, increasing the efficiency of the procurement process. The integration of Materials Management in SAP ERP and SAP Supplier Self-Services (SUS) in SAP SRM has also been enhanced to support services with hierarchical structures.
Effects on Data Transfer A series of enterprise services are provided to integrate Materials Management in SAP ERP with SAP SRM: o
Request Sourcing
o
Request RFQ
o
Request Purchase Order
o
Maintain Purchase Order_V1
o
Maintain Purchasing Contract_V1
o
Confirm Purchase Order
o
Confirm Purchasing Contract
o
Change Purchase Request Based on Purchase Request ERP Sourcing Confirmation
o
Change Purchase Request Based on RFQ Request SUITE Confirmation
o
Notify of Service Acknowledgement Cancellation
o
Notify of Service Acknowledgement Confirmation
o
Create Service Acknowledgement Based on Acknowledgement Create Request
See also For more information on hierarchies in the enhanced purchasing process, see the release note Hierarchies (Enhanced) on SAP Service Marketplace at http://service.sap.com/support under Release and Upgrade Info -> Release Notes -> SAP Solutions -> SAP Supplier Relationship Management (SAP SRM) -> Release Notes SAP SRM 7.0. For more information on using sourcing rules and RFx, see the release note SAP Bidding Engine (Enhanced) on SAP Service Marketplace at http://service.sap.com/support under Release and Upgrade Info -> Release Notes -> SAP Solutions -> SAP Supplier Relationship Management (SAP SRM) -> Release Notes SAP SRM 7.0. For more information on the integration of Materials Management in SAP ERP and SAP Supplier Self-Services, see the release note Materials Management and Supplier Self-Services Integration (Enhanced) on SAP Service Marketplace at
http://service.sap.com/support under Release and Upgrade Info -> Release Notes -> SAP Solutions -> SAP Supplier Relationship Management (SAP SRM) -> Release Notes SAP SRM 7.0.
MISSING RELN �1_4
LOG_MM_P2PSE_1: Business Package for Buyer 1.4 (new) Use If you activate the business function Procurement - SRM Integration and want to use the portal content for procurement activities, you have to install Business Package for Buyer 1.4. For more information, see the business package release note in SAP Library under SAP ERP Central Component -> Roles -> Business Packages (Portal Content) -> Business Package for Buyer 1.4.
LOG_MM_P2PSE_1: Procurement Business Package for ERP and SRM (new) Use If you activate the business function Procurement - SRM Integration and want to access harmonized ERP and SRM procurement content, you have to install the Procurement Business Package for SAP ERP and SAP SRM. For more information, see the release note Procurement Business Package for SAP ERP & SAP SRM (new) on SAP Service Marketplace at http://service.sap.com/support under Release and Upgrade Info -> Release Notes -> SAP Solutions -> SAP Supplier Relationship Management (SAP SRM) -> Release Notes SAP SRM 7.0. Effects on Customizing In Customizing for Purchasing, choose Portal -> Set Up Landscape. Then choose SRM System Connected and save. You must make this setting so that the ERP applications that run in the Procurement Business Package for SAP ERP and SAP SRM business package have the links that allow the user to navigate to SRM applications (for example, link for displaying an SRM central contract). See also For more information, see SAP Library for SAP Supplier Relationship Management on SAP Help Portal at http://help.sap.com under Business Packages -> Procurement Business Package for SAP ERP and SAP SRM.
LOG_MM_P2PSE_1: Enhanced BAPIs for Purchase Requisitions (New) Use As of SAP enhancement package 4 for SAP ERP 6.0, business function Purchasing - SAP SRM Integration (LOG_MM_P2PSE_1), you can use the following BAPIs to process bills of material and service items: o
BAPI_PR_CREATE
o
BAPI_PR_CHANGE
o
BAPI_PR_GETDETAIL
You can use the following enhancement objects for BAPIs BAPI_PR_CREATE and BAPI_PR_CHANGE: o
SAP enhancement MEREQ001
o
Business Add-Ins -
ME_PROCESS_REQ_CUST � Enhancements for processing Enjoy purchase requisitions
-
ME_REQ_HEADER_TEXT � Copy header text of Enjoy purchase requisition
-
ME_REQ_POSTED � Purchase requisition posted
-
ME_REQ_OI_EXT � Commitment update for external purchase requisitions
-
ME_COMMTMNT_REQ_RE_C � Check commitment relevance of purchase requisitions
-
ME_BAPI_PR_CUST � BAPIs for Enjoy purchase requisitions
When the BAPIs are called, the following authorization objects are used: o
M_BANF_BSA Document type in purchase requisition
o
M_BANF_EKG Purchasing group in purchase requisition
o
M_BANF_EKO Purchasing organization in purchase requisition
o
M_BANF_WRK Plant in purchase requisition
o
M_BANF_LGO Storage location in purchase requisition
See also For more information, see the central release note for the business function Materials Management Purchasing (LOG_MM_CI_2).
Business Function Serial Numbers in Purchasing LOG_MM_SERNO: Serial Numbers in Purchasing (New) Use As of SAP ECC 6.0, Enhancement Package 4 (SAP_APPL 604), you can enter serial numbers for the main items of purchase orders and purchase requisitions. Within one purchase order or purchase requisition you may want to order several pieces of an item. By serializing the materials, you can easily differentiate between them, making it easier to request a specific piece of material. You serialize the materials using the Maintain Serial Number popup which you access on the Delivery Schedule tab page in the purchase order or on the Material Data tab page in the purchase requisition. The following new features are available o
Serial number transfer When you create a sales order for third-party processing, and assign serial numbers to its items, the created purchase requisition will contain these serial numbers. This purchase requisition is created in the background. When you create purchase orders with reference to a purchase requisition, the serial numbers are transferred automatically from the purchase requisition to the purchase order.
o
Schedule lines You can have more than one serial number per schedule line. If the purchase order has several schedule lines, the serialized numbers need to be assigned manually to the correct schedule line or created by the system by choosing Create Serial Number Automatically in the Maintain Serial Number popup.
o
Base units of measure When serializing base units of measure (for example, piece), the conversion of order unit of measure (for example, kg) must result in a whole number at schedule line level for purchase orders, and at item level for purchase requisitions. For example, if the base unit of measure was 3 pieces and the order unit was 2kg, each unit would be 0.66, which you cannot serialize. oChanging the configuration of purchase requisitions and purchase order items. You cannot change the configuration of a purchase requisition or purchase order item if you are working with already configured objects to which serial numbers are already assigned and the original configuration in the material serial number is not linked to these objects.
Effects on Existing Data The following user interface elements are new:
Transaction
Program/Dynpro Element
ME21N/ME22N/ME23N/ME29N
SAPLMEGUI/1211 Button 'Display
Serial Number List' ME21N/ME22N/ME23N/ME29N
SAPLMEGUI/1212 Button 'Display
Serial Number List' ME21N/ME22N/ME23N/ME29N
SAPLMEGUI/1320 Buttons 'Display
Serial Number List' and 'Assign Serial Numbers' ME51N/ME52N/ME53N/ME54N/ME57 SAPLMEGUI/3211
Button
'Display Serial Number List' ME51N/ME52N/ME53N/ME54N/ME57 SAPLMEGUI/3212
Button
'Display Serial Number List' ME51N/ME52N/ME53N/ME54N/ME57 SAPLMEGUI/3319
Buttons
'Display Serial Number List' and 'Assign Serial Numbers' OLME
SAPLEBNE/0102 Customizing
settings for serial numbers GUI Status POSI, in the menu Extras -> Serial Numbers Effects on Customizing You must activate the business function Serial Numbers in Purchasing (LOG_MM_SERNO). You must make the following Customizing settings: oFor determination of serial number profiles: Materials Management -> Purchasing -> Serial Numbers -> Determine
Serial Number Profiles oFor fine tuning purchasing document's serialization information: Purchasing -> Purchase Order or Purchase Requisition -> Define Document
Types Choose the document type and item category and under Maintenance View Serial Numbers in Purchasing Documents define the serial number profile information. See also For more information, see SAP Library for SAP ERP Central Component on under Logistics -> Materials Management (MM) -> Purchasing (MM-PUR) -> Purchase Requistion/Purchase Order -> Serial Numbers in Purchasing.
Business Function MM, Integration of Materials Management and Financial Accounting 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) oMM_IV_604_MMFI_WEDAT: Checking of Goods Receipt Date
Against Delivery Date (New) oMM_IV_604_MMFI_PARTN: Checking of Partner Roles in the
Incoming Invoice (New) oMM_PUR_604_MMFI_FO: Follow-On Activities for Completed
Purchase Order Items (New) oMM_PUR_604_MMFI_REPO: Business Add-In for Displaying
Reporting Data oMM_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 entering 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 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 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 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 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: 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 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) and Services (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 JIT 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 JIT 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 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 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 also For more information, see the Materials Management component under Purchasing --> Outline Purchase Agreements with Vendors -->Scheduling Agreement --> Administration of Scheduling Agreements.