ERP 2005

SAP ERPPDF download from SAP Help Portal:http://help.sap.com/erp2005_ehp_07/helpdata/en/dc/e7d353ca9f4408e10000000a174cb4/frameset.htm

Created on June 02, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

NoteThis PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. You can manually download the missing subtopics.

2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SEand its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided bySAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable 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 expresswarranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and otherSAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and othercountries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 95

Table of content1 SAP ERP1.1 What's New in SAP ERP1.1.1 What's New in SAP Enhancement Package 7 for ERP 6.01.1.1.1 Support Package Stack 081.1.1.1.1 Accounting1.1.1.1.1.1 Deletion of Personal Data in Flexible Real Estate Management (RE1.1.1.1.1.2 Treasury and Risk Management1.1.1.1.1.2.1 Enhancements in Hedge Accounting for Exposures1.1.1.1.1.2.1.1 TRM, E-HA, Assigning Hedging Instruments with Different Signs1.1.1.1.1.2.1.2 TRM, E-HA, Effectiveness Assessment on Hedged Item Level1.1.1.1.1.2.1.3 TRM, E-HA, Documentation on Hedged Item Level1.1.1.1.1.2.1.4 TRM, E-HA, Eliminate Intraperiod Ineffectiveness1.1.1.1.2 Logistics1.1.1.1.2.1 Materials Management (MM)1.1.1.1.2.1.1 Deletion of Personal Data in Materials Management1.1.1.1.2.1.2 Ariba Network Spot Buy in Purchasing1.1.1.1.2.1.3 Checkbox for Complete Delivery in Purchase Order1.1.1.1.2.2 Sales and Distribution, SAP Jam Integration1.1.1.1.2.2.1 Sales and Distribution, SAP Jam Integration using CDS Views1.1.1.1.2.3 Environment, Health, and Safety1.1.1.1.2.3.1 PS: Managing Exposure Scenarios - Inbound Processing1.1.1.1.2.3.1.1 Specification Management: Change for Inbound Processing1.1.1.1.2.3.2 IH: Deletion of Personal Data in Industrial Hygiene and Safety1.1.1.1.2.4 Product Lifecycle Management (PLM)1.1.1.1.2.4.1 Enhancements for Digital Mockups1.1.1.1.2.4.2 Enhancement for Dependency Maintenance Table1.1.1.1.2.4.3 Support for Geometric Instance Management1.1.1.1.2.4.4 Enhancements for Product Structure Tree1.1.1.1.2.4.5 Enhancements for User Settings1.1.1.1.2.4.6 Visual Instance Planner1.1.1.1.2.5 Plant Maintenance (PM)1.1.1.1.2.5.1 Deactivation of Codes1.1.1.1.2.5.2 Simplified Management of EAM Functions 51.1.1.1.2.5.2.1 Creating Follow-On Orders1.1.1.1.2.5.2.2 Improved UI for User Status on Header Level1.1.1.1.2.5.2.3 Changing the Notification Type1.1.1.1.2.5.2.4 Documents and Long Texts of Notification Codes1.1.1.1.2.5.3 EAM, WCM Safety Certificate Integration into Worker Safety1.1.1.1.2.6 Retail1.1.1.1.2.6.1 Settlement Amounts in Condition Contract Settlement1.1.1.1.2.6.2 API to Generate Listing1.1.1.1.2.6.3 Deletion of Personal Data in SAP Retail Store (LO-SRS)1.1.1.1.2.6.4 Rapid Replenishment Planning1.1.1.1.2.7 Material Segmentation (LO-SGT)1.1.1.1.2.7.1 Material Segmentation Across Logistics (Enhanced)1.1.1.1.3 Cross-Application Components1.1.1.1.3.1 Cross-Application Components1.1.1.1.3.1.1 Archiving and Destruction of Correspondence Requests (New)1.1.1.1.4 Branchen in SAP ERP1.1.1.1.4.1 SAP Student Lifecycle Management1.1.1.1.4.1.1 Deletion of Personal Data in Student Lifecycle Management1.1.1.1.4.1.1.1 Archiving Data in Student Lifecycle Management1.1.1.1.4.1.1.2 Data Destruction in Student Lifecycle Management1.1.1.1.4.2 Contract Accounts Receivable and Payable (FI-CA)1.1.1.1.4.2.1 Real-Time Payments1.1.1.1.4.2.2 Partial Clearing of Payment Orders1.1.1.1.4.2.3 Archiving1.1.1.1.4.2.4 Connecting Multiple CC Systems to an FI-CA System1.1.1.1.4.2.5 Joint Distribution of Master Data1.1.1.1.4.2.6 Aggregation of Consumption Items for Rating


Page 2 of 95

1.1.1.1.4.2.7 Processing of Billable Items and Consumption Items1.1.1.1.4.2.8 Analyze Unbilled Items1.1.1.1.4.2.9 Local Currency Translation in Foreign Currency Valuation1.1.1.1.4.3 SAP Public Sector1.1.1.1.4.3.1 Versioning of TTF-Based Form Bundles1.1.1.1.4.3.2 Destruction of Personal Data in Social Services1.1.1.1.4.3.3 SAP Public Sector Collection and Disbursement (PSCD)1.1.1.1.4.3.3.1 Real-Time Payments1.1.1.1.4.3.3.2 Partial Clearing of Payment Orders1.1.1.1.4.3.3.3 Archiving1.1.1.1.4.3.3.4 Joint Distribution of Master Data1.1.1.1.4.3.3.5 Aggregation of Consumption Items for Rating1.1.1.1.4.3.3.6 Processing of Billable Items and Consumption Items1.1.1.1.4.3.3.7 Analysis of Unbilled Items1.1.1.1.4.3.3.8 VAT Transfer of Credit Memos (Czech Republic)1.1.1.1.4.3.3.9 VAT Transfer of Special VAT Operations (Russia)1.1.1.1.4.3.3.10 Tax Adjustment of Overdue Invoices (Poland)1.1.1.1.4.3.3.11 Enhanced Official Document Numbering1.1.1.1.4.3.3.12 Exchange Rates for Tax Postings1.1.1.1.4.3.3.13 Prevent Invoicing Reversal After Printing of Invoice1.1.1.1.4.3.3.14 Processing of Postdated Checks1.1.1.1.4.3.3.15 Tax Notifications1.1.1.1.4.3.3.16 Invoicing of Currency Translation Differences1.1.1.1.4.3.3.17 Local Currency Translation in Foreign Currency Valuation1.1.1.1.4.4 SAP for Insurance1.1.1.1.4.4.1 SAP Claims Management1.1.1.1.4.4.1.1 Multiple Contract Handling: Change History1.1.1.1.4.4.1.2 Multiple Contract Handling: Archiving1.1.1.1.4.4.1.3 Multiple Contract Handling: Status Management1.1.1.1.4.4.1.4 Multiple Contract Handling: Facts Capture1.1.1.1.4.4.1.5 Multiple Contract Handling: Automatic Contract Selection1.1.1.1.4.4.1.6 Multiple Contract Handling: Remove Contract1.1.1.1.4.4.1.7 Multiple Contract Handling: Direct Input1.1.1.1.4.4.1.8 Notes Processing in Claim Bundle1.1.1.1.4.4.1.9 Determining General Ledger Account per Benefit Type1.1.1.1.4.4.1.10 Handling Supplemental Accident Insurance (Life)1.1.1.1.4.4.1.11 Loan Offset Posting for CML Loan1.1.1.1.4.4.1.12 Claim Bundle Number with Internal Number Assignment1.1.1.1.4.4.1.13 Check for Duplicates During Claim Bundle Creation Process1.1.1.1.4.4.1.14 Processing Notes in Direct Input1.1.1.1.4.4.1.15 Display of Recently Processed Claim Bundles1.1.1.1.4.4.1.16 Importing Correspondence Cluster Data1.1.1.1.4.4.2 SAP Collections and Disbursements1.1.1.1.4.4.2.1 Real-Time-Zahlungen1.1.1.1.4.4.2.2 Archivierung1.1.1.1.4.4.2.3 Teilausgleich von Zahlungsauftrgen1.1.1.1.4.4.2.4 Write-Offs1.1.1.1.4.4.2.5 Local Currency Translation in Foreign Currency Valuation1.1.1.1.4.4.2.6 Sperren von Geschftspartnern1.1.1.1.4.5 SAP for Telecommunications (IS-T)1.1.1.1.4.5.1 Real-Time Payments1.1.1.1.4.5.2 Archiving1.1.1.1.4.5.3 Analyze Unbilled Items1.1.1.1.4.5.4 Processing of Billable Items and Consumption Items1.1.1.1.4.5.5 Joint Distribution of Master Data1.1.1.1.4.5.6 Connecting Multiple CC Systems to an FI-CA System1.1.1.1.4.5.7 Partial Clearing of Payment Orders1.1.1.1.4.5.8 Aggregation of Consumption Items for Rating1.1.1.1.4.5.9 Exchange Rates for Tax Postings1.1.1.1.4.5.10 Prevent Invoicing Reversal After Printing of Invoice1.1.1.1.4.5.11 Invoicing of Currency Translation Differences1.1.1.1.4.5.12 Convergent Invoicing for Service Nota Fiscal (Brazil)


Page 3 of 95

1.1.1.1.4.5.13 Enhanced Official Document Numbering1.1.1.1.4.5.14 Processing of Postdated Checks1.1.1.1.4.5.15 Tax Adjustment of Overdue Invoices (Poland)1.1.1.1.4.5.16 Tax Notifications1.1.1.1.4.5.17 VAT Transfer of Credit Memos (Czech Republic)1.1.1.1.4.5.18 VAT Transfer of Special VAT Operations (Russia)1.1.1.1.4.5.19 Local Currency Translation in Foreign Currency Valuation1.1.1.1.4.6 SAP for Media1.1.1.1.4.6.1 Media, Real-Time Payments1.1.1.1.4.6.2 Media, Archiving1.1.1.1.4.6.3 Media, Partial Clearing of Payment Orders1.1.1.1.4.6.4 Local Currency Translation in Foreign Currency Valuation1.1.1.1.4.6.5 Media, Country-Specific Functions 011.1.1.1.4.6.5.1 Media, Convergent Invoicing for Service Nota Fiscal (Brazil)1.1.1.1.4.6.5.2 Media, VAT Transfer of Credit Memos (Czech Republic)1.1.1.1.4.6.5.3 Media, Tax Adjustment of Overdue Invoices (Poland)1.1.1.1.4.6.5.4 Media, VAT Transfer of Special VAT Operations (Russia)1.1.1.1.4.6.5.5 Media, Enhanced Official Document Numbering1.1.1.1.4.6.5.6 Media, Exchange Rates for Tax Postings1.1.1.1.4.6.5.7 Media, Prevent Invoicing Reversal After Printing of Invoice1.1.1.1.4.6.5.8 Media, Invoicing of Currency Translation Differences1.1.1.1.4.6.5.9 Media, Processing of Postdated Checks1.1.1.1.4.6.5.10 Media, Tax Notifications1.1.1.1.4.7 SAP Utilities, Contract Accounts Receivable and Payable1.1.1.1.4.7.1 Utilities, Real-Time Payments1.1.1.1.4.7.2 Utilities, Archiving1.1.1.1.4.7.3 Utilities, Partial Clearing of Payment Orders1.1.1.1.4.7.4 Utilities, Processing of Billable Items and Consumption Items


Page 4 of 95

1 SAP ERP

Product SAP ERPRelease 6.0SAP enhancement package 7 for SAP ERP 6.0, SPS 7Based On SAP NetWeaver 7.4, SPS 9BI Content Release BI Content Add-On 7.57Documentation Published April 2015

For more information about SAP NetWeaver, SAP Business Suite Foundation (SAP_BS_FND), and cross-application business functions in the SAP BusinessSuite, see:

SAP Business Suite Cross-Application Business FunctionsProcesses and Tools for Enterprise ApplicationsBusiness Functions (SAP Business Suite Foundation 7.01)

1.1 What's New in SAP ERP In this section, you can find the release notes. Use the navigation in the left frame to find a specific release note.

1.1.1 What's New in SAP Enhancement Package 7 for ERP 6.0 In this section, you can find the release notes. Use the navigation in the left frame to find a specific release note.

1.1.1.1 Support Package Stack 08 In this section, you can find the release notes. Use the navigation in the left frame to find a specific release note.

1.1.1.1.1 Accounting 1.1.1.1.1.1 Deletion of Personal Data in Flexible Real EstateManagement (RE-FX) As of enhancement package 7, SP 08 for SAP ECC 6.0, functions are available that simplify the blocking and deletion of personal data by using SAP InformationLifecycle Management (ILM).

Technical DetailsCountry Dependency Valid for all countriesSoftware Component Version EA-FIN 617

Application Component Flexible Real Estate Management (RE-FX)Available as of SAP Enhancement Package 7 (SP08) for SAP ECC 6.0Required Business Functions ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF)

Existing DataThese functions enable you to use the SAP Information Lifecycle Management (ILM) component to support the deletion of personal data and to control the deletionand blocking of business partner data. Personal data collected in business partner data can be blocked as soon as business activities for which this data isneeded are completed and the residence time for this data has elapsed; after this time, only users who are assigned additional authorizations can access thisdata. After the retention period for data expires, personal data can be destroyed completely so that it can no longer be retrieved. Retention periods must be definedin the customer system.

Data TransferAn end of purpose check determines whether data is still relevant for business activities based on the retention period defined for the data. The retention period ofdata consists of the following phases.

Phase one: The relevant data is actively used.


Page 5 of 95

Phase two: The relevant data is actively available in the system.Phase three: The relevant data needs to be retained for other reasons.For example, processing of data is no longer required for the primary business purpose but to comply with legal rules for retention the data must still beavailable. In phase three, the relevant data is blocked.Blocking of data prevents the business users of SAP applications from displaying and using data that may include personal data and is no longer relevantfor business activities.

Blocking of data can impact system behavior in the following ways:Display: The system does not display blocked data.Change: It is not possible to change a business object that contains blocked data.Create: It is not possible to create a business object that contains blocked data.Copy/Follow-Up: It is not possible to copy a business object or perform follow-up activities for a business object that contains blocked data.Search: It is not possible to search for blocked data or to search for a business object using blocked data in the search criteria.

It is possible to display blocked data if a user has special authorization; however, it is still not possible to create, change, copy or perform follow-up activities forblocked data.

Customizing

SAP Information Lifecycle Management (ILM)To use SAP Information Lifecycle Management (ILM) to simplify the deletion of application-specific personal data:

Activate the business function Information Lifecycle Management (ILM).Make the necessary Customizing settings related to SAP Information Lifecycle Management (ILM) in Customizing for SAP NetWeaver under ApplicationServer Basis Services Information Lifecycle Management .Run transaction IRMPOL and maintain the required retention policies for the ILM objects of the application.

Blocking and Deletion of Business Partner DataTo use the new functions to simplify the blocking and deletion of business partner data:

Activate the business function ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF).Make the necessary Customizing settings related to the blocking and deletion of customer and vendor master data in Customizing for Cross-ApplicationComponents under Data Protection.

See alsoSAP Information Lifecycle ManagementILM Objects in Flexible Real Estate Management (RE-FX)Deletion of Business Partner Data

SAP Library for SAP ERP at http://help.sap.com/erp Security Information Security Guide SAP ERP Security Guide SAP ERP CentralComponent Security Guide Accounting Real Estate Management

SAP Note 2134204

1.1.1.1.1.2 Treasury and Risk Management 1.1.1.1.1.2.1 Enhancements in Hedge Accounting for Exposures 1.1.1.1.1.2.1.1 TRM, E-HA, Assigning Hedging Instruments withDifferent Signs With this function, you can assign hedging instruments with different plus/minus signs to a hedged item in a hedging relationship with the risk category ExchangeRate Risk. This allows you to avoid overhedging.When assigning hedging instruments, note that the total of all designated amounts of the assigned hedging instruments must not have the same plus/minus signas the hedged item.

Technical DetailsTechnical Name of the Product Feature TRM_EHA_3The product feature is NewCountry Dependency Valid for all countriesSoftware Component Version EA-FINSERV 617Application Component FIN-FSCM-TRM-TMAvailability SAP enhancement package 7 (SP08) for SAP ERP 6.0Prerequisite Business Functions FIN_TRM_LR_FI_AN_5


Page 6 of 95

Effects on Existing DataThe function Hedge Plan (transaction THMEX) has been changed for hedge plans with the risk category Exchange Rate Risk. In the case of such hedge plans, itis now possible to designate hedging instruments that have the same plus/minus sign as the hedged item.

More InformationDocumentation of the business function TRM, Enhancements in Hedge Accounting for ExposuresHedge Plan (Hedging Relationship Management)

1.1.1.1.1.2.1.2 TRM, E-HA, Effectiveness Assessment onHedged Item Level With this function, you can also perform at the hedged item level effectiveness assessments (transaction THM80) for hedging relationships of a hedge plan withthe risk category Exchange Rate Risk. In this case, the system performs the effectiveness assessment for a hedged item and for all hedging instrumentsassigned to that hedged item.

Technical DetailsTechnical Name of the Product Feature TRM_EHA_1

The product feature is NewCountry Dependency Valid for all countriesSoftware Component Version EA-FINSERV 617Application Component FIN-FSCM-TRM-TMAvailability SAP enhancement package 7 (SP08) for SAP ERP 6.0Prerequisite Business Functions FIN_TRM_LR_FI_AN_5

Effects on Existing DataThe Effectiveness Test function (transaction THM80) has been enhanced. Under Perform Assessment, you can now set the Test on Hedged Item Level indicator. Ifyou set this checkbox, the effectiveness assessment is performed for the selected hedged object and for all designated hedging instruments. In the assessment,the results of the individual hedging instruments are added together, and the effectiveness test is then performed for the total.

More InformationDocumentation of the business function TRM, Enhancements in Hedge Accounting for ExposuresEffectiveness Test

1.1.1.1.1.2.1.3 TRM, E-HA, Documentation on Hedged ItemLevel With this function, you can also create at the hedged item level documentation for hedging relationships (transaction THM86) of a hedge plan with the risk categoryExchange Rate Risk. In this way, the documentation contains information about the hedging relationship, the hedge plan, and the hedged item, as well asinformation about all designated hedging instruments for that hedged item.

Technical DetailsTechnical Name of the Product Feature TRM_EHA_2

The product feature is NewCountry Dependency Valid for all countriesSoftware Component Version EA-FINSERV 617Application Component FIN-FSCM-TRM-TMAvailability SAP enhancement package 7 (SP08) for SAP ERP 6.0Required Business Function FIN_TRM_LR_FI_AN_5

Effects on Existing Data


Page 7 of 95

The Documentation function (transaction THM86) has been enhanced. For hedging relationships of a hedge plan with the risk category Exchange Rate Risk, youcan now decide on the level at which you would like to create documentation: at the level of the hedging instrument or at the level of the hedged item.

Documentation at the Hedging Instrument LevelAs was already the case with the previous function, the documentation is created for one hedging instrument and the relevant hedged item.Documentation on Hedged Item LevelIn this case, documentation is created for a hedged item and for all hedging instruments assigned to that hedged item.

Before you can use this function, you need to create a new entry for the company code, the valuation area, and the risk category Exchange Rate Risk and assignthe new form TR_F_THA_HREL. You perform these steps in Customizing under Transaction Manager General Settings Hedge Accounting for Exposures Documentation Assign Forms to Hedging Relationships .If you would like to make changes to the form, you can copy the form and make your changes to the copied version.

More InformationDocumentation of the business function TRM, Enhancements in Hedge Accounting for ExposuresPrinting Hedging Relationship Documentation

1.1.1.1.1.2.1.4 TRM, E-HA, Eliminate Intraperiod Ineffectiveness You use this function to eliminate any intraperiod ineffectiveness of your hedging relationship. This ineffectiveness results when a hedged item and its hedginginstrument are discounted on different dates. In Customizing for Treasury and Risk Management, you use for this purpose the Discounting Method in the activityDefine Hedge Strategies. If you opt for the setting Discount Exposure on Date of Derivative, the system discounts the hedging instrument as well as the hedgeditem for the same date so that intraperiod ineffectiveness is avoided.

Technical DetailsTechnical Name of the Product Feature TRM_EHA_4The product feature is NewCountry Dependency Valid for all countriesSoftware Component Version EA-FINSERV 605Application Component FIN-FSCM-TRM-TMAvailability SAP enhancement package 5 (SP15) for SAP ERP 6.0

SAP enhancement package 6 (SP15) for SAP ERP 6.0SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA, Support Package 09SAP enhancement package 7 (SP08) for SAP ERP 6.0

Effects on Existing DataIn Customizing for Treasury and Risk Management under Transaction Manager General Settings Hedge Accounting for Exposures Effectiveness Test Define Hedge Strategies , you can use the new Discounting Method. Before you can use the new function, you need to select the discounting method DiscountExposure on Date of Derivative in your hedge strategy.

1.1.1.1.2 Logistics 1.1.1.1.2.1 Materials Management (MM) 1.1.1.1.2.1.1 Deletion of Personal Data in Materials Management As of enhancement package 7 SP08 for SAP ECC 6.0, functions are available that simplify the processes for blocking and deleting personal data in the followingMaterials Management components through the use of SAP Information Lifecycle Management (ILM):

Purchasing (MM-PUR)Procurement of External Services (MM-SRV)Inventory Management (MM-IM)Logistics Invoice Verification (MM-IV)

Technical DetailsCountry Dependency Valid for all countries

Software Component Version SAP_APPL 617

Application Component MM (Materials Management)


Page 8 of 95

Available as of SAP Enhancement Package 7 (SP08) for ECC 6.0

Required Business Functions ERP_CVP_ILM_1

Effects on Existing DataThese functions allow you to use the SAP Information Lifecycle Management (SAP ILM) component to support the deletion of personal data and to control thedeletion and blocking of business partner master data. Personal data in business partner master data can be blocked as soon as business activities for whichthis data is required have been completed and the residence time has passed. Once this time has expired, only users that have been assigned additionalauthorizations can access this data. Once the retention period has expired, personal data can be destroyed permanently, which means it can no longer beaccessed. The residence time and retention periods must be defined in the system.The check to identify the end of the intended purpose uses the retention period defined for the data to determine whether this data is still relevant for businessactivities. The lifecycle of data in the system involves the following phases:

Phase one: The data is used actively.Phase two: The data is actively available in the system.Phase three: The data must be kept and retained for other reasons.

Example: Phase 1: A business partner acts as a vendor on a number of occasions. Phase 2: The business partner could be commissioned but is not actuallyawarded any more orders. Phase 3: The business partner may no longer be commissioned. The data no longer needs to be processed for the primary intendedpurpose in phase 2, and processing is not supported in phase 3. The data is still available in the system in phase 3, however, to ensure that legal provisions fordata retention are observed. This data is blocked for use in business processes in phase 3, however.When data is blocked, users of the SAP applications can neither display nor access personal data that is no longer relevant for business activities. Data blockinghas the following impact on system behavior:

Display: The system does not display any blocked data.Change: It is not possible to change a business object* that contains blocked data.Create: It is not possible to create a business object* that contains blocked data.Copying or follow-on activities: A business object* that contains blocked data either cannot be copied in its entirety or the blocked data is not copied. Neitheris it possible to perform follow-on activities with the blocked data for a business object*.Search: It is not possible to use blocked data as search criteria when searching for a business object.

* Note: Inventory management documents can contain various items that are related to different vendors. In this case, it is not the business object that is affected,that is, not the document as a whole; it is only the items with blocked data that cannot be created, changed, copied, or used in follow-on activities. Those documentitems that relate to other vendors that are still active are not affected by the blocking.

NoteOnly users with special authorization can display blocked data; they are not authorized, however, to create, change, or copy business objects with blockeddata, or perform follow-on activities with these business objects.

Blocking and Deleting Data in Materials ManagementIn Materials Management, the process up to the blocking and deletion of personal data might look as follows:Once all goods receipts and invoices have been processed for a purchase order for a vendor, and all payments have been processed in FI, the businessactivities with this vendor are deemed completed.Before the personal data can be permanently deleted, it may need to be retained in the system for a defined period of time when stipulated by legal provisions.The check to identify the end of the intended purpose determines when the personal data for a vendor was last used in a document. If this check indicates nofurther use and the residence time has passed, the data can be blocked to prevent it from being used further. Once the legally stipulated retention period hasended, the data blocked up until this time can be deleted permanently.

Customizing

SAP Information Lifecycle Management (ILM)To use SAP Information Lifecycle Management (ILM) to simplify the process to delete application-specific personal data, you need to proceed as follows:

Activate the Information Lifecycle Management (ILM) business function.Configure the relevant Customizing settings for SAP Information Lifecycle Management (ILM) in Customizing for SAP NetWeaver under Application Server -> Basis Services -> Information Lifecycle Management.Call transaction IRMPOL and maintain the required retention policies for customer and vendor master data (ILM objects FI_ACCPAYB and FI_ACCRECV)as well as for the ILM objects in the Materials Management application (MM_EBAN, MM_EKKO, MM_EINA, MM_INVBEL, MM_REBEL, and MM_SPSTOCK).

Locking and Deleting Customer and Vendor Master DataTo use the new functions for simplifying the processes to block and delete customer and vendor master data, you need to proceed as follows:

Activate the following business functions:ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF)ILM-Based Deletion of Customer and Vendor Master Data (ERP_CVP_ILM_1): The MM_DPP_SFW_01 option must be activated.

Configure the required Customizing settings for blocking and deleting customer and vendor master data in Customizing for Logistics - General underBusiness Partner -> Deleting Customer Master Data and Vendor Master Data.

See also


Page 9 of 95

SAP Library for SAP ERP under http://help.sap.com/erp ->Application Help -> SAP ERP Cross-Application Functions -> Cross-Application Components -> SAP Information Lifecycle ManagementApplication Help -> SAP ERP Cross-Application Functions -> Cross-Application Components -> Data Protection -> Deletion of Business PartnerData/Deletion of Customer Master Data/Deletion of Vendor Master DataApplication Help -> SAP ERP Central Component -> Logistics -> Materials Management -> Data Archiving in Materials ManagementSecurity Information -> Security Guide -> SAP ERP Security Guide -> SAP ERP Central Component Security Guide -> Logistics -> MaterialsManagement -> Data Protection

SAP Notes

1825544

2007926

2131233

1.1.1.1.2.1.2 Ariba Network Spot Buy in Purchasing With this feature you can add materials from the Ariba eBay catalog to your purchase requisition. Your purchase requisition, which is created for a generic Aribasupplier, is then referenced to in the purchase order. Ariba Network takes over the purchase order, which has been created for the same generic Ariba supplier,and directs it to the actual eBay supplier.

Technical DetailsTechnical Name of Product Feature ERP_MM_SPOTBUYProduct Feature Is NewCountry Dependency Valid for all countriesSoftware Component Version SAP_APPL 617

Application Component Purchase Requisitions (MM-PUR-REQ)Availability SAP Enhancement Package 7 (SP08) for SAP ERP 6.0

Required Business Functions MM, Spot Buy in Purchasing

Effects on CustomizingTo maintain a supplier to be used for Ariba Network Spot Buy in purchasing, perform the Customizing activity Maintain Suppliers for Spot Buy under MaterialsManagement Purchasing Purchase Requisition Maintain Suppliers for Spot Buy

1.1.1.1.2.1.3 Checkbox for Complete Delivery in Purchase Order With this feature you can indicate that only a complete delivery for purchase orders (POs) is acceptable. The checkbox Complete delivery is available both onheader- and on item level. This feature is provided for standard purchase orders, stock transport orders, and third-party order processing. In a third-party purchaseorder process, the request for a complete delivery is automatically transferred using IDocs from the PO of an end-customer into the sales order of a wholesaler.After the MRP run, the request for a complete delivery is transferred from the sales order to the third-party purchase order. From there, it is transferred to the salesorder of the supplier. Note that, if you create a PO manually, you must also select this checkbox manually.

Technical DetailsTechnical Name of Product Feature LOG_SDMM_CMPL_DLV_01_MRKCMPLPOProduct Feature Is NewCountry Dependency Valid for all countriesSoftware Component Version SAP_APPL 617

Application Component MM-PUR-PO (Purchase Orders)Availability SAP enhancement package 7 (SP 8) for SAP ERP 6.0

Effects on Data TransferIf you have activated the business function LOG_SDMM_CMPL_DLV_01 (MM, Checkbox for Complete Delivery), the information that only a complete delivery isacceptable for the purchase order is sent using the IDoc.

Effects on CustomizingThe following settings are relevant:


Page 10 of 95

Field selectionIf you want to hide the checkbox, adjust the field selection. You do this in Customizing for Materials Management under Purchasing Purchase Order Define Screen Layout at Document Level .Print relevanceMaintain the settings for print relevance both at header and item level in Customizing for Materials Management under Purchasing Messages FieldsRelevant to Printouts of Changes .Message severityMaintain the settings for message severity in Customizing for Materials Management under Purchasing Environment Data Define Attributes of SystemMessages .

1.1.1.1.2.2 Sales and Distribution, SAP Jam Integration 1.1.1.1.2.2.1 Sales and Distribution, SAP Jam Integration usingCDS Views As of SAP enhancement package 7 SP08 for SAP ERP 6.0 (SAP_APPL 617), the business function Sales and Distribution, SAP JAM Integration using CDS(LOG_SD_JAM_INTEG_CDS) is available. With this business function, you can retrieve data using the OData serviceESJI_SD_SRV for business objects suchsales orders, customers, outbound deliveries, invoices, and quotations.

More InformationFor more information on the business function, see Sales and Distribution, SAP Jam Integration using CDS Views

1.1.1.1.2.3 Environment, Health, and Safety 1.1.1.1.2.3.1 PS: Managing Exposure Scenarios - InboundProcessing The ESCom standard for exchanging exposure scenarios between IT systems was developed to enable exposure scenario information to be communicated alongthe supply chain in a consistent and harmonized manner. Supporting the standardized exchange of exposure scenario data along the supply chain helps toreduce the manual effort as well as time and costs during the transfer and communication of regulatory data. Inbound processing of ESComXML files helps therecipient of an ESComXML file to import the data into the system.

Technical DetailsTechnical Name of Product Feature LOG_EHS_PS_CI_6_ESC_INBOUND_1

Product Feature Is NewCountry-Dependency Valid for all countriesSoftware Component Version EA-APPL 617Application Component Product Safety in SAP EHS Management as part of SAP ERPAvailable From SAP EHP7 (SP08) for SAP ERP 6.0Required Business Functions LOG_EHS_PS_CI_6

More DetailsIn addition to the new functions described below, enhancements for the new functions are used in the following areas:

Specification Management: Change for Inbound ProcessingSpecification Management: New Identifiers

The new functions are integrated into the existing components of Environment, Health and Safety, and are available in the new component Management ofExposure Scenarios (EHS-SAF-ESM).For more information, refer to the following release notes:

Effects on System AdministrationBefore you configure Exposure Scenario Management, you need to configure the following settings:

Switch Business Configuration Sets (Switch BC Sets) for Inbound Processing of ESComXML Files: If you activate the business functionLOG_EHS_PS_CI_6 (EHS - Continuous Improvement for Product Safety), the following switch BC sets are imported:

EHHSS_ESCOM_INB_ESEESCV_INBBASIC (EHS: Settings ESComXML Inbound Processing)EHHSS_ESCOM_INB_ESEESCV_INBIMP (EHS: Specify Settings for ESComXML Data Import)EHHSS_ESCOM_INB_ESEESCV_INBMSG (EHS: Specify Message Types for Import Preparation)EHHSS_ESCOM_INB_ESEESCV_INBMSGWI (EHS: Specify Message Types for Supplier Material Checks)EHHSS_ESCOM_INB_ESV_TCG56 (EHS: Specify Data Origin for ESComXML Data Import)


Page 11 of 95

EHHSS_ESCOM_INB_ESV_TCG52 (EHS: Assign EHS Document Types to DMS Document Types)EHHSS_ESCOM_INB_VC_DVS10 (EHS: Define 'SBX' Document Types for ESComXML Inbound Processing)EHHSS_ESCOM_INB_VC_TCG26 (EHS: Specify Identification Listing for ESComXML Inbound Processing)EHHSS_ESCOM_INB_VC_TCG96 (EHS: Specify Usage Profiles)

These Switch BC sets contain all the basic settings for inbound processing of ESComXML files.

Effects on Customizing

New Customizing ActivitiesExposure Scenario Management has been extended to include the Inbound Processing of ESComXML Files node.Exposure Scenario Management has been extended under the Inbound Processing of Exposure Scenarios node to include the following Customizing activities:

Specify Number Ranges for Allocation of Import RequestsSpecify Number Ranges for Allocation of Record NumbersSpecify Settings for Inbound Processing of ESComXML FilesSpecify Settings for ESComXML Data ImportSpecify Message Types for Inbound Processing ChecksSpecify Message Types for Import Preparation

The following Customizing activity has been added:Check Configuration of Exposure Scenario Management

The following documentation for the implementation has been enhanced in Customizing for Exposure Scenario Management:Exposure Scenario ManagementConfiguration of Exposure Scenario ManagementCheck Configuration of Exposure Scenario ManagementPrerequisites for Inbound Processing of ESComXML FilesAssign Phrases to Units of Measurement

New TransactionsThe following new transactions are available to you in Inbound Processing of ESComXML Files:

Prepare ESComXML Files for Import (CGESCIP)You use this new transaction to upload ESComXML files to your system. When you do so, the system checks the ESComXML file in the background,assigns it a status, and creates an import request.You use the new transaction to assign the objects from the ESComXML file to the objects in the SAP system.You use the new transaction to select exposure scenarios that you want import and start the data import.

Monitor ESComXML Data Import (CGESCMONITOR)You use this new transaction to monitor the ESComXML data import. While the data is imported, the system carries out checks. The system createsnew contributing scenarios and exposure scenario header data if these do not yet exist in the system and assigns them to the Use and ExposureScenario value assignment type in the supplier material. You can view the check results of the import in the import log.

New Document Type in Document ManagementThe following new document type is available in the Customizing activity under Cross-Application Components -> Document Management -> Control Data ->Define Document Types:

SBX: ESComXML FileThe following new document type is available in the Customizing activity under Environment, Health & Safety -> Basic Data and Tools -> Report Definition ->Settings for Document Management -> Assign EH&S Document Types to DMS Document Types:

EHS document type: SBXDocument type: SBXName of the data carrier: SAP system

New Data Origin in Basic Data and ToolsThe following new data origin is available in the Customizing activity under Basic Data and Tools -> Tools -> Import and Export -> sic Settings for Import andExport -> Specify Data Origin:

ESCOMXML: ESComXML Interface

New Usage Profile in Basic Data and ToolsThe following new usage profile is available in the Customizing activity under Basic Data and Tools -> Specification Management -> Additional Information forValue Assignment -> Usage -> Specify Usage Profiles:

ESCOMXML: ESComXML Interface

More Information

For more information, see SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com under SAP ERP Central Component Logistics Environment, Health and Safety (EHS) Product Safety (EHS-SAF) Exposure Scenario Management .For more information about implementing Exposure Management, see Customizing for Product Safety under Exposure Scenario Management.

1.1.1.1.2.3.1.1 Specification Management: Change for InboundPUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 12 of 95

1.1.1.1.2.3.1.1 Specification Management: Change for InboundProcessing

Specification Management (Changed)This enhancement is part of the release note PS: Management of Exposure Scenarios - Inbound ProcessingAs of SAP enhancement package 7 SP 08 for SAP ERP 6.0, the Specification Management (EHS-BD-SPE) component contains the following new functions:

New Function

New Identification ListingsThe following new identification listings are available in the Customizing activity Check Identification Listing:

D_ESC_SUPP: Identifiers for supplier nameD_ESC_SMTN: Identifiers for supplier material nameD_ESC_RSE: Identifiers for supplier material (input help)D_ESC_CMP: Identifiers for component assignment (input help)D_ESC_SMNR: Identifiers for supplier material number

1.1.1.1.2.3.2 IH: Deletion of Personal Data in Industrial Hygieneand Safety Functions are available that simplify blocking and deletion of personal data with SAP Information Lifecycle Management (ILM).

Technical DetailsTechnical Name of Product Feature EHS_IHS_ERP617_08

Product Feature Is NewCountry-Dependency Valid for all countriesSoftware Component Version EA_APPL 617

Application Component SAP EHS Management as part of SAP ERPAvailable From SAP Enhancement Package 7 (SP08) for SAP ERP 6.0

These functions enable you to use the SAP Information Lifecycle Management (ILM) component for deleting personal data and controlling the deletion and lockingof personal data in industrial health and safety. You can block the personal data as soon as business activities for which this data is needed are completed andthe residence period for this data has elapsed. After this time, only users who are assigned additional authorizations can access this data. If the retention period fordata expires, personal data can be destroyed completely such that it can no longer be retrieved.Residence and retention periods must be defined in the customer system.

Effects on Existing DataChecking the End of the PurposeAn end of purpose check determines whether data is still relevant for business activities based on the residence period defined for the data. The residence periodof data consists of the following phases:

1. Phase one: The relevant data is actively used.2. Phase two: The relevant data is actively available in the system.3. Phase three: The relevant data needs to be retained for other reasons.For example, processing of data is no longer required for the primary business purpose, but to comply with legal rules for retention, the data must still beavailable.

In phase three, the relevant data is blocked. Blocking of data prevents the business users of SAP applications from displaying and using data that may includepersonal data and is no longer relevant for business activities. Blocking of data can impact system behavior in the following ways:

Display: The system does not display blocked data.Change: It is not possible to change a business object that contains blocked data.Create: It is not possible to create a business object that contains blocked data.Copy/Follow-Up: It is not possible to copy a business object or perform follow-up activities for a business object that contains blocked data.Search: It is not possible to search for blocked data or to search for a business object using blocked data in the search criteria.

It is possible to display blocked data if a user has special authorization; however, it is still not possible to create, change, copy, or perform follow-up activities onblocked data.Locking and Deleting in Industrial Health and SafetyIn industrial health and safety, you can block the following personal data as soon as business activities for which this data is needed are completed and theresidence period for this data has elapsed:

Incident/accident log data


Page 13 of 95

The following data can be deleted as soon as the retention period for this data has expired:Incident/accident log dataRecorded persons in measurement managementRecorded persons in risk assessmentRecorded persons in the actionRecorded persons in the work area

Effects on CustomizingProceed as follows to simplify deletion of personal data in Industrial Hygiene and Safety with SAP Information Lifecycle Management:

Activate the business function Information Lifecycle Management (ILM).Make the required Customizing settings for SAP Information Lifecycle Management (ILM) in Customizing for SAP NetWeaver under the following path: Application Server Basis Services Information Lifecycle Management Execute transaction IRMPOL and maintain the required retention rules for the following ILM objects of Industrial Hygiene and Safety:

EHS_IHS_IAL_DESTRUCTIONEHS_IHS_MEM_PRD_DESTRUCTIONEHS_IHS_RAS_PRD_DESTRUCTIONEHS_IHS_SAF_PRD_DESTRUCTIONEHS_IHS_WA_PRD_DESTRUCTION

More InformationSAP Information Lifecycle Management

SAP Library for SAP ERP under http://help.sap.com/erp Application Help SAP ERP Central Component Logistics Environment, Health andSafety (EHS) Industrial Health and Safety (EHS-IHS) Data Destruction in Industrial Health and Safety

SAP Library for SAP ERP under http://help.sap.com/erp Security Information Security Guide SAP ERP Security Guides SAP ERP CentralComponent Security Guide Logistics Environment, Health and Safety (EHS)

SAP Note 2126202

1.1.1.1.2.4 Product Lifecycle Management (PLM) 1.1.1.1.2.4.1 Enhancements for Digital Mockups This feature enables you to:

Use digital mockups (DMUs) for the 3D visualization of a product structure, based on lightweight viewable files and geometric instances, in oneconfigurable engineering BOM (EBOM) structure.Define whether the lightweight viewable file is available at the material level (via material master document object link) or at the product item variant level(via linked document info records).Take geometric instances into consideration when you explode the product structure.

Technical DetailsTechnical Name of Product Feature PLM_PLMWUI_DMU

Product Feature Is ChangedCountry Dependency Valid for all countriesSoftware Component Version PLMWUI 702

PLMWUI 747

Application Component PLM-WUI-OBJ-PSM (Product Structure and Assembly Management)

Availability SAP Enhancement Package 6 (SP15) for SAP ERPSAP Enhancement Package 7 (SP08) for SAP ERP

Required Business Functions /PLMU/IPPE_INT_4 (PLM, Product Structure and Assembly Management 4)

Effects on CustomizingTo enable this feature, settings are required in the Create and Assign Views and View Sets for Product Structure TreeCustomizing activity under Logistics -General Product Lifecycle Management (PLM) PLM Web User Interface Objects in PLM Web UI Product Structure and Assembly Management . For moredetails, refer to the documentation of the Customizing activity.

1.1.1.1.2.4.2 Enhancement for Dependency Maintenance Table With this feature, you can view and maintain the object dependencies of a whole product structure in a tree view in the dependency maintenance table (DMT).


Page 14 of 95

This tree view allows you to expand and collapse your structure as required.You use the DMT to enter object dependencies for product item variants and geometric instances. You use object dependencies in the product structure to controlthe selection of variants for a particular product item or geometric instances for a particular product item variant.

Technical DetailsTechnical Name of Product Feature PLM_PLMWUI_DMT


PLMWUI 747




1.1.1.1.2.4.3 Support for Geometric Instance Management This feature enables you to use geometric instances, which contain the geometric data of an individual occurrence of a component within a product structure, onthe Product Lifecycle Management (PLM) Web UI.With this feature, you can:

Use the integration with the Visual Instance Planner to assign geometric instances to product item variants in product structures and use these geometricinstances in the display of digital mockups (DMUs).Group geometric instances and maintain object dependencies per group.Display and maintain object dependencies at geometric instance or instance group level, or using the dependency maintenance table (DMT).Copy the assigned geometric instances with their maintained object dependencies within the structure.

Technical DetailsTechnical Name of Product Feature PLM_PLMWUI_GEOINST

Product Feature Is NewCountry Dependency Valid for all countriesSoftware Component Version PLMWUI 702

PLMWUI 747



Required Business Functions /PLMU/IPPE_INT_4 (PLM, Product Structure and Assembly Management 4)PLM_VIP_1(Visual Instance Planner)

Effects on CustomizingTo enable the different aspects of this feature, settings are required in the following Customizing activities under Logistics - General Product LifecycleManagement (PLM) PLM Web User Interface Objects in PLM Web UI Product Structure and Assembly Management :

Define Relevant Node Types for Assignment of Geometric InstancesMaintain Views for the Definitions TabBAdI: Adjust Parameter for Geometric Instance MaintenanceBAdI: Instance Grouping Check

For more information, see the documentation of the Customizing activities.

1.1.1.1.2.4.4 Enhancements for Product Structure Tree This feature enables you to do the following for the product structure tree:

Tailor the design and product views in the Show dropdown to suit the requirements of different user roles and provide more comprehensive content.Use the product view types available for the product structure tree to display non-configurable structures (material BOMs). These views provide both amulti-level and a multi-structure display.Use design view types to display bill of documents (BoD) structures as part of the structure explosion and define which BoD is used for digital mockupviewing and how this BoD is exploded (for example, as saved or latest released version).In addition, individual users can define user-specific view settings via their User Settings.


Page 15 of 95

Technical DetailsTechnical Name of Product Feature PLM_PLMWUI_PST


PLMWUI 747




Effects on CustomizingTo enable this feature, settings are required in the following Customizing activities under Logistics - General Product Lifecycle Management (PLM) PLM WebUser Interface Objects in PLM Web UI Product Structure and Assembly Management :

Create and Assign Views and View Sets for Product Structure TreeDefine Settings for Product StructureMaintain User ProfilesMaintain Default User Settings for Product Structure Management


1.1.1.1.2.4.5 Enhancements for User Settings With this feature, you can make additional user settings for the product structure Web UI.For example, you can select a tree view type that makes sense for your role, that is, you can choose between a Product View, a Design View, or a ProductStructure Only view in the Tree Settings. This view will be loaded when you initially start the UI.The Material BOM Explosion section of the User Settings enables you to define explosion parameters for MBOMs within a product view.In Customizing, you can predefine all default settings for the User Settings that are available for users on the Web UI. You can also define whether specificsettings should be visible to users, hidden from users, or read-only.

Technical DetailsTechnical Name of Product Feature PLM_PLMWUI_USERSETTING


PLMWUI 747




Effects on CustomizingTo enable this feature, settings are required in the following new Customizing activities under Logistics - General Product Lifecycle Management (PLM) PLMWeb User Interface Objects in PLM Web UI Product Structure and Assembly Management :

Maintain Default User Settings for Product Structure ManagementMaintain Default User Settings for Product Assembly Management


1.1.1.1.2.4.6 Visual Instance Planner You use this application to enrich the Product Structure Management (PSM) engineering structure with the visual information present in the Computer AidedDesign (CAD) file. The Visual Instance Planner is intended to close a gap to bring CAD data into PSM using SAP Variant Configuration (VC).The planning session is launched directly from Product Structure Manager or CDESK or using the transaction VIP_LAUNCH. When planning is complete, the planis saved back to Product Structure Manager.You can perform a number of tasks when working with Visual Instance Planner, including the following:


Page 16 of 95

Assign instances to the product structureCreate product item variants, instance groups, and instancesCreate variants and instances automaticallyMove instances between instance groupsBuild, edit, and delete variants, instance groups, and instances from the product structureReload the product structureSimulate save to validate changes made to the product structureSave changes back to Product Structure ManagerSearch for and load alternative source filesSpecify preferred settings

Technical DetailsTechnical Name of Product Feature PLM_VIP_1

Product Feature Is NewCountry Dependency Valid for all countriesSoftware Component Version SAP_APPL 606

SAP_APPL 617

Application Component CA-VE-VEP-INT (Visual Enterprise Planner integration with ERP)


1.1.1.1.2.5 Plant Maintenance (PM)

1.1.1.1.2.5.1 Deactivation of Codes Codes ensure that issues can be entered in a standardized way and therefore be evaluated automatically. In Plant Maintenance, codes describe damage andmalfunctions, the causes of the damage as well as its maintenance and repair, all of which is entered as technical findings in the plant maintenance history. InQuality Management, codes can be used, for example, to describe defect types, defect locations, defect causes, tasks, characteristic values, and usagedecisions. You can use this business function to retrospectively deactivate codes that you have already used in documents. Deactivated codes are no longeravailable in the input help and can no longer be assigned manually either. However, even after deactivation, the codes and their long texts and assigneddocuments are still available as selection criteria in reports.

Technical DetailsTechnical Name of the Product Feature LOG_EAM_QM_CODE_DEACT

Product feature is newCountry Dependency Valid for all countriesSoftware Component Version SAP_APPL 604

Application Component PM (Plant Maintenance)QM (Quality Management)PS-CLM (Claim Management)

Availability SAP enhancement package 4 (SP17) for SAP ERP 6.0Required Business Function(s) EAM/QM, Deactivation of Codes

Effects on Existing DataYou define codes in Customizing for Plant Maintenance and Customer Service, for Quality Management (Quality Planning, Quality Inspection, Quality Notification)and for Claim Management, by choosing, for example:

Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Content Maintain Catalogs Quality Notifications Notification Creation Notification Content Maintain Catalogs Project System Claim Notification - Claim Notification Creation Notification Content Maintain Catalogs

In the Change Codes view (Customizing view cluster V_QPGR_CL, view B_TQ15) for catalog maintenance, there is a new Deactivated checkbox. You can onlydeactivate codes if they are not part of a selected set.

More InformationDeactivation of codes in SAP GUI transactions: Working with Notification CodesDeactivation of codes on the Web UI: Working with Notification Codes

1.1.1.1.2.5.2 Simplified Management of EAM Functions 5PUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 17 of 95

1.1.1.1.2.5.2 Simplified Management of EAM Functions 5 This business function enables you to use various functions for processing maintenance documents on the SAP Web UI for Plant Maintenance that up to nowwere only available in SAP GUI transactions.

More InformationFor more information about this business function, see Simplified Management of EAM Functions 5.

Technical DetailsTechnical Name of Business Function LOG_EAM_SIMPLICITY_5

Availability SAP enhancement package 7 (SP08) for SAP ERP 6.0 (EA-APPL 617)

For more information about the functions that are included in this business function, see the following product feature release notes:Creating Follow-On OrdersImproved UI for User Status on Header LevelChanging the Notification TypeDocuments and Long Texts of Notification Codes

1.1.1.1.2.5.2.1 Creating Follow-On Orders You can use this function to create maintenance orders as follow-on orders for an order or order operation. When you create a follow-on order, you create arelationship to the reference order or operation. You can display this relationship as a hierarchical list in the document flow of the corresponding SAP GUItransactions. You can create follow-on orders either directly from the Work Overview (Create Order) or whilst you are displaying, changing, or confirming an order.

Technical DetailsTechnical Name of the Product Feature LOG_EAM_SIMPL5_FOLLOW_ON

Product feature is newCountry Dependency Valid for all countriesSoftware Component Version EA-APPL 617Application Component PM (Plant Maintenance)Availability SAP enhancement package 7 (SP08) for SAP ERP 6.0Required Business Function(s) Simplified Management of EAM Functions 5

Additional DetailsWhen you create a new order as a follow-on order for an existing order, the system copies the header data of the existing order to the new order. You can usecheckboxes to specify whether the system should also copy operation data, components, relationships, document links, settlement rules, and order descriptionsto the follow-on order.You can create follow-on orders for existing orders or for individual order operations. You can create a new order as a follow-on order or you can choose to create afollow-on order for an order you are displaying, changing, or confirming, which takes you to the order creation screen.When creating an order by copying another order, the system creates the new order independently of the order you used as a template. When creating a follow-onorder, however, the system creates a relationship to the reference order, in which the reference order becomes the preceding order. In SAP GUI, you can displaythis relationship as a hierarchical list.

NoteThe hierarchical list displays at most one level above and one level below the selected order. In other words, only the orders directly preceding and directlyfollowing the order that you selected are displayed. If you have created follow-on orders for more than one order operation, the system displays all the follow-onorders that have been created for the selected order or its operations.You can only display this relationship between preceding and follow-on orders if you are using the enhanced document flow functions in the maintenance order.You can activate the enhanced document flow with the business function Enterprise Asset Management Part 6 (LOG_EAM_CI_6) or Enterprise AssetManagement Part 7 (LOG_EAM_CI_7).You can also create follow-on orders with the BAPI BAPI_ALM_ORDER_MAINTAIN.You can only create follow-on orders for orders that have been released.

Effects on Existing DataTo create and display follow-on orders, the user interface has been enhanced as follows:


Page 18 of 95

SAP Web User Interface for Plant Maintenance (PM)When you create maintenance orders, there is a new checkbox Create Follow-On Order in the Create by Copying screen area. You can use thischeckbox to specify that the existing order is not only used as a reference order, but also becomes a preceding order for the new order. Furthermore,there is a new field in which you can enter an operation number if you wish to create the follow-on order for a specific order operation. Each time youcreate an order, you can use the new Operations and Components checkboxes to specify whether operation data and specific operation detail datais also copied to the follow-on order.When you change or display an order on the Web UI, there are new symbols that show you whether a follow-on order or a preceding order exists forthe current order.So that you can create a follow-on order for an order or an order operation that you are currently displaying, changing, or confirming, the entry CreateFollow-On Order has been added to the context menu for the operation data. When you change or display an order, there is a new option CreateFollow-On Order under Additional Functions.

SAP GUI TransactionsYou can display the relationship between the preceding order or operation and the follow-on order in a hierarchical list in SAP GUI.

When you change or display an order, the new pushbuttons with the tooltips A preceding order exists for this order and A follow-on order exists for thisorder indicate whether the order has a preceding or a follow-on order. You can use these pushbuttons to display the hierarchy list with the precedingand/or follow-on orders in the document flow.In the document flow that you call either directly (transaction code iw12) or from the order, there is a new Follow-On Orders pushbutton. You can usethis to display the hierarchical list of preceding and follow-on orders.

NoteIf you wish to allow follow-on orders to be created directly from the confirmation, you have to create a new PFCG role based on the SAP standard roleMaintenance Worker (SAP_COCKPIT_EAMS_MAINT_WORKER2) and add the object-based navigation Create Order. You must also grant the respective usersthe authorization for creating orders so they can create follow-on orders in confirmations.

More InformationCreating an Order with Reference and Creating a Follow-On Order

1.1.1.1.2.5.2.2 Improved UI for User Status on Header Level This function provides you with an enhanced user interface (UI) for setting the user status on header level. It is available in maintenance orders, notifications, andtechnical objects. All the user statuses that have been entered in the corresponding status profile are listed in the drop-down list for the new Set User Statuspushbutton. In this list you can set a user status and even reset it, if allowed.

Technical DetailsTechnical Name of the Product Feature LOG_EAM_SIMPL5_USER_STATUS


Effects on Existing DataFor processing maintenance orders, notifications, functional locations and equipment, the SAP Web User Interface for Plant Maintenance has been modified asfollows:

The Status Information, where you can assign a status profile, is no longer a pushbutton, but rather can be accessed via the menu Additional Functions Status Information .All the user statuses in the assigned status profile are listed in the drop-down list for the Set User Status pushbutton. You can set and reset all the userstatuses that are not grayed out directly from the list. If a status that has been set can be reset, Reset Status: prefaces the name of the status in the list.The technical IDs of the user statuses that are set for the current order, notification, or technical object are displayed in the Identification Region. Thedescriptions of these user statuses are displayed in a tooltip.

More InformationMaintenance OrderMaintenance NotificationTechnical Objects on the Web User Interface (PM-EQM)

1.1.1.1.2.5.2.3 Changing the Notification Type This function enables you to make Customizing settings that allow the notification type to be changed when users create and change maintenance and service


Page 19 of 95

notifications.

Technical DetailsTechnical Name of the Product Feature LOG_EAM_SIMPL5_NOTIF_TYPE_CHA


Additional DetailsYou can allow the notification type of maintenance and service notifications to be changed if the original notification type and the target notification type have thesame notification category. You allow this in Customizing for Plant Maintenance and Customer Service under Maintenance and Service Processing Maintenance and Service Notifications Notification Creation Notification Types Define Allowed Changes of Notification Type . In the SAP standardconfiguration, you can allow the change between the following notification types:

Notification types with notification category Maint. Notification:Maintenance Requests (M1)Malfunction Reports (M2)Activity Reports (M3)

Notification types with notification category Service Notification:Problem Notifications (S1)Activity Reports (S2)Service Requests (S3)

The notification type of maintenance and service notifications can only be changed if the notification has not yet been completed.When the notification type is changed, the system does not assign a new notification number and all data of the original notification type is retained (such asreference objects). This also applies even if specific data is irrelevant for the target notification type. To override this behavior, implement the Business Add-In(BAdI) Checks for Extended Change of Notification Type (BADI_IQS0_NOTIF_TYPE_CHANGE).

NoteIf you wish to be able to change the notification type on the Web UI, you have to allow the change of notification types in the SAP GUI transactions as well(iw21, iw22, iw51, and iw52). To do this, activate the business function Enterprise Asset Management Part 7 (LOG_EAM_CI_7).

Effects on Existing DataIn the applications Create Notification and Change Notification, the new entry Change Notification Type is now available in the dropdown menu of the AdditionalFunctions pushbutton.

More InformationChanging the Notification Type

1.1.1.1.2.5.2.4 Documents and Long Texts of Notification Codes Codes ensure that issues can be entered in a standardized way and therefore be evaluated automatically. In Plant Maintenance, codes describe damage andmalfunctions, the causes of the damage as well as its maintenance and repair, all of which is entered as technical findings in the plant maintenance history.You can use this function to copy long texts and documents attached to codes, which you assign during notification processing, to the corresponding maintenanceand service notifications. If the damage codes, cause codes, activity codes, and task codes you selected have long texts or documents stored in Customizing, youcan copy them to the notification. The system copies the long text of the code to the Long Text column and stores any documents assigned to the code on theDocuments tab page. The documents that are copied with the code are always assigned to the notification on header level.

Technical DetailsTechnical Name of the Product Feature LOG_EAM_SIMPL5_DOCU_CODE

Product feature is newCountry Dependency Valid for all countriesSoftware Component Version EA-APPL 617Application Component PM (Plant Maintenance)Availability SAP enhancement package 7 (SP08) for SAP ERP 6.0


Page 20 of 95

Required Business Function(s) Simplified Management of EAM Functions 5

PrerequisitesThe system copies long texts and documents that you have assigned to codes in Customizing under Plant Maintenance and Customer Service Maintenanceand Service Processing Maintenance and Service Notifications Notification Creation Notification Content Maintain Catalogs .You can only assign documents to notification codes if you have also activated the Document Link to Code switch in Customizing under Quality Management Basic Settings Maintain Settings at Client Level .

Effects on Existing DataWhen you add damages, causes, activities, or tasks to a notification, select the appropriate codes on the popup. In the new Attachment column, a symbolindicates whether long texts or documents are assigned to the codes. When you hover over the symbol, a quickview displays the long text as well as links to theassigned documents. Below the table, you can use the new checkboxes Copy long text of selected codes and Copy documents of selected codes to specifywhether the system should copy the long texts and documents to the notification.

More InformationWorking with Notification Codes

1.1.1.1.2.5.3 EAM, WCM Safety Certificate Integration intoWorker Safety With this business function, you can enhance work permit processing in EAM Worker Safety by integrating safety certificates. Such integration includes thefollowing:

creation of new safety certificates for a given work permitassignment of existing safety certificates to a given work permitremoval of assigned safety certificates from a given work permitprocessing of safety certificates

With each safety certificate, you can describe the dedicated safety and approval process that is a prerequisite for a work permit. Common examples for safetycertificates are: fire protection certificate, isolation certificate, confined space entry certificate, excavation certificate.

Technical DetailsTechnical Name of the Product Feature EAMPLM/LOG_EAM_WCM_WS_2

Product feature is newCountry Dependency Valid for all countriesSoftware Component Version EA-APPL 617Application Component PM-WCM (Work Clearance Management)Availability SAP enhancement package 7 (SP08) for SAP ERP 6.0Required Business Function(s) EAM, WCM Integration into Worker Safety

1.1.1.1.2.6 Retail 1.1.1.1.2.6.1 Settlement Amounts in Condition ContractSettlement This new feature enables you to analyze the settlement amounts of condition contracts. Instead of viewing the single settlement documents of a particular conditioncontract, you get an overview of the settlement amounts for a particular set of condition contracts. You can also define your own drilldown levels to analyze thesettlement values from a highly aggregated level down to a more detailed level.The data selection is based on CDS view technology. If you run the settlement amounts on an SAP HANA database you will save significant processing time byusing SAP HANA capabilities.

Technical DetailsTechnical Name of Product Feature ISR_GLT_VENDOR_FUND_2_PF12Product Feature Is NewCountry Dependency Valid for all countries


Page 21 of 95

Software Component Version EA-GLTRADE 617Application Component LO-GT-CHBAvailable as of SAP Enhancement Package 7 (SP08) for SAP ERP 6.0

1.1.1.1.2.6.2 API to Generate Listing With this feature you can create an assortment and generate a listing through an RFC enabled function module.

Technical DetailsTechnical Name of Product Feature RAP_LISTING_ERP_API

Product Feature Is NewCountry Dependency Valid for all countriesSoftware Component Version RTLRAP 100

UIRAP001 100

Application Component CA-RT-AP

Available as of CAR RETAIL APPL BUNDLE 1.0 FP01

Additional Details

NoteAs a prerequisite to creating the listing, the assortment plan has to be finalized and all the PHPs must be matched. If the PHPs in the assortment list are notmatched, you will receive an error message.

As of SAP Assortment Planning for Retail 1.0 FP01, assortment listings are created in ERP with the validity period of the assortment list. You use the followingRFC function modules:

Wrf_Mapinb_Assort_RfcYou use this function module to create an assortment in SAP ERP given a set of locations. This function module contains the following parameters:Importing:

Assortment ID (optional)Validity Dates (optional)Sales OrganizationDistribution ChannelProduct Hierarchy IDProduct Hierarchy Node IDAssortment TypeName/Description of the assortment (which is it?)Table of material groups/merchandise categories (which is it?)Table of location IDs to be assigned to the assortment

Exporting:Assortment IDList with warning and error messages (if any)

Wrf_Mapinb_Asrt_List_RfcYou use this function module to create listing conditions for the specified assortment in the system without the generation of prices. This function modulecontains the following parameters:Importing:

Assortment IDTable with product IDsValidity Dates (optional)Listing Procedure (optional)

Exporting:List with product IDs which have been successfully listedList with warning and error messages (if any)

See alsoMy Assortment Lists

1.1.1.1.2.6.3 Deletion of Personal Data in SAP Retail Store (LO-SRS) As of enhancement package 7, SP 08 for SAP ECC 6.0, functions are available that simplify the blocking and deletion of personal data by using SAP InformationLifecycle Management (ILM).


Page 22 of 95

Technical DetailsCountry Dependency Valid for all countriesSoftware Component Version EA-RETAIL 617

Application Component SAP Retail Store (LO-SRS)Customer Master (LO-MD-BP-CM)Vendor Master (LO-MD-BP-VM)

Available as of SAP Enhancement Package 7 (SP08) for SAP ECC 6.0Required Business Functions ERP_CVP_ILM_1

Existing DataThese functions enable you to use the SAP Information Lifecycle Management (ILM) component to support the deletion of personal data and to control the deletionand blocking of customer and vendor master data. Personal data collected in customer and vendor master data can be blocked as soon as business activities forwhich this data is needed are completed and the residence time for this data has elapsed; after this time, only users who are assigned additional authorizationscan access this data. After the retention period for data expires, personal data can be destroyed completely so that it can no longer be retrieved. Retention periodsmust be defined in the customer system.

Data TransferAn end of purpose check determines whether data is still relevant for business activities based on the retention period defined for the data. The retention period ofdata consists of the following phases.

Phase one: The relevant data is actively used.Phase two: The relevant data is actively available in the system.Phase three: The relevant data needs to be retained for other reasons.For example, processing of data is no longer required for the primary business purpose but to comply with legal rules for retention the data must still beavailable. In phase three, the relevant data is blocked.Blocking of data prevents the business users of SAP applications from displaying and using data that may include personal data and is no longer relevantfor business activities.

Blocking of data can impact system behavior in the following ways:Display: The system does not display blocked data.Change: It is not possible to change a business object that contains blocked data.Create: It is not possible to create a business object that contains blocked data.Copy/Follow-Up: It is not possible to copy a business object or perform follow-up activities for a business object that contains blocked data.Search: It is not possible to search for blocked data or to search for a business object using blocked data in the search criteria.

It is possible to display blocked data if a user has special authorization; however, it is still not possible to create, change, copy or perform follow-up activities forblocked data.

Customizing

SAP Information Lifecycle Management (ILM)To use SAP Information Lifecycle Management (ILM) to simplify the deletion of application-specific personal data:

Activate the business function Information Lifecycle Management (ILM).Make the necessary Customizing settings related to SAP Information Lifecycle Management (ILM) in Customizing for SAP NetWeaver under ApplicationServer Basis Services Information Lifecycle Management .Run transaction IRMPOL and maintain the required retention policies for the ILM objects of the application.

NoteFor SAP Retail Store, the ILM objects for the following components are usually relevant:

Logistics objects: LO, MM, SD, and LECross-application objects: BC and CARetail objects: LO and MM, names beginning with WFinancials (if used): FI and CO

Blocking and Deletion of Customer and Vendor Master DataTo use the new functions to simplify the blocking and deletion of customer and vendor master data:

Activate the following business functions:ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF)ILM-Based Deletion of Customer and Vendor Master Data (ERP_CVP_ILM_1)

Make the necessary Customizing settings related to the blocking and deletion of customer and vendor master data in Customizing for Logistics - Generalunder Business Partner Deletion of Customer and Vendor Master Data .


Page 23 of 95

See alsoSAP Information Lifecycle ManagementData archiving and data destruction documentation for the relevant component, for example, for Sales and Distribution (SD):

Data Archiving in Sales and Distribution (SD)Data Destruction in Sales and Distribution (SD)

Deletion of Customer Master Data and Deletion of Vendor Master Data

SAP Library for SAP ERP at http://help.sap.com/erp Security Information Security Guide SAP ERP Security Guide SAP ERP CentralComponent Security Guide Logistics Retail

SAP Note 2088284

SAP Note 2141448

SAP Note 2012217

1.1.1.1.2.6.4 Rapid Replenishment Planning With this feature, you can use a performance-optimized method for replenishment planning, which is called rapid replenishment planning.Rapid replenishment planning allows you to save substantial runtime in the replenishment planning process, depending on the planning scenario used. Theresponse time in dialog planning for larger numbers of items is noticeably better. Batch planning takes significantly less time, so the planning process can bescheduled for a later point in time and/or will be finished earlier, and system resources can be used for other tasks.Rapid replenishment planning uses the same master data and control data (from Customizing) as classic replenishment planning, provides the same calculationlogic, and is fully integrated into the overall replenishment process (for example, usage of the replenishment monitor or parameter overview, lock concept).Business Add-Ins and user exits of classic replenishment can still be used with rapid replenishment planning. The main differences between rapidreplenishment planning and classic replenishment planning are:

Rapid replenishment planning can be used only for sites, not for external customers. Only forecasts from materials management can be used, not fromflexible planning.The determination of receipts/issues is not performed via functions of ATP (Available-to-Promise), although the existing ATP control is used for rapidreplenishment planning. With the current version of rapid replenishment planning, purchase orders, order confirmations, and purchase requisitions can beconsidered as receipts/issues (both for external and internal procurement). There are some minor differences in the consideration logic for openreceipts/issues, compared to ATP.

Rapid replenishment planning is executed via transaction WRP1R (report RWRPLRRP), which is available after activation of business function ISR_APPL_RRPL.Rapid replenishment planning and classic replenishment planning can be used at the same time.Rapid replenishment planning, with its optimized runtime and alternative data access implemented as core data services (CDS), is an alternative to classicreplenishment planning (transaction WRP1).The database access contains joins to multiple tables with conditions, aggregations, and calculations. Database access like this can be very efficiently executedin a column-based in-memory database such as SAP HANA, especially when processing large data sets. The execution performance may also improvesignificantly on other database platforms.The actual performance impact also depends largely on the replenishment scenario as well as on data volumes and the execution mode for replenishment

planning. See SAP Note 2051280 for more details, also about database specific information. You should evaluate the performance and functional fit of rapidreplenishment planning for your actual use case and potentially adjust the execution mode (for example, packet size) before using it productively.Classic replenishment planning is, as before, available on all database platforms supported by ECC Retail.

Technical DetailsTechnical Name of Product Feature ISR_ERP6_EHP7_SP07_RRPLProduct Feature Is NewCountry Dependency Valid for all countriesSoftware Component Version SAP APPL 6.17Application Component IS-R-PUR-RPAvailable as of SAP Enhancement Package 7 (SP08) for SAP ERP 6.0Required Business Functions Retail, Rapid Replenishment Planning

See alsoReplenishment: Classic and Rapid Planning

1.1.1.1.2.7 Material Segmentation (LO-SGT) 1.1.1.1.2.7.1 Material Segmentation Across Logistics (Enhanced) SAP ERP 6 enhancement package 7 SP 07 includes the following enhancements in Segmentation (LO-SGT):


Page 24 of 95

Batch Determination in DeliveriesIn ERP 6 enhancement package 7 support pack 08, segmentation is integrated in the batch determination process.Outbound DeliveryYou can activate automatic batch determination for delivery item categories using the Customizing activity Activate Automatic Batch Determination in SD under Logistics - General Batch Management Batch Determination and Batch Check .

If you have activated automatic batch determination: For a material that is relevant for segmentation, the system filters the batch numbers based on thesegmentation value and proposes appropriate batch number or batch numbers with batch split.If you have not activated automatic batch determination: For a material that is relevant for segmentation you can enter the batch number manually in thedelivery documents. You can only enter the batches that belong to the valid stock segment value maintained in the mapping rule in the Requirement/StockAllocation table in the Customizing activity Define Segmentation Strategy.

For more information, see Batch Determination for Outbound Deliveries.Inbound DeliveryYou can enable the system to check whether the batch entered in the inbound delivery document already exists in the system. To do this, you can use the NoBatch Check checkbox in the Customizing activity Define Item Categories for Deliveries under Logistics Execution Shipping Deliveries .

If you select this checkbox, the system does not create a new batch number in the document and does not perform a batch split, although the batch isrelevant for segmentation. However, if the system determines an existing batch number, it enters this batch number in the document and performs a batchsplit.If you do not select this checkbox, the system determines a new batch number or an existing batch number and enters the determined batch number in thedocument and performs a batch split.

For more information, see Batch Determination for Inbound Deliveries.

Requirement Segment Value Determination in Purchasing DocumentsDuring stock transfer, if the supplying plant is relevant for segmentation and the receiving plant is not relevant for segmentation, you can use the followingCustomizing activities to determine the requirement segment value in purchase orders and purchase requisitions:

Purchase Orders under Logistics - General Segmentation Define Segment Value for Automatic Determination .Purchase Requisitions under Logistics - General Segmentation Define Segment Value for Automatic Determination .

In addition, you can define your own logic for determining the requirement segment using the BAdI BADI_SGT_REQ_SEGMENT_VALUE. When you implement thisBAdI, the system overrides the settings defined in the Customizing activities for purchase orders and purchase requisitions and determines the segmentationvalues according to the user-defined logic.

Effects on CustomizingThe following Business Add-Ins (BAdI) are created:

BADI_SGT_REQ_SEGMENT_VALUEYou can use this BAdI to determine the requirement segmentation value in the purchase order and purchase requisition. You can call this BAdI when thesupplying plant is relevant for segmentation but the receiving plant is not to determine the requirement segmentation value.

See alsoFor more information about material segmentation, see SAP Library on SAP Help Portal under SAP ERP SAP ERP Central Component Logistics Logistics -General (LO) Segmentation (LO-SGT) .

1.1.1.1.3.1 Cross-Application Components 1.1.1.1.3.1 Cross-Application Components 1.1.1.1.3.1.1 Archiving and Destruction of CorrespondenceRequests (New) For correspondence requests, functions are available to assist you with archiving and destroying data using archiving object CORRSPND.

Technical DetailsCountry Dependency Valid for all countriesSoftware Component Version SAP_ABA 740

Application Component CA-GTF-COR

Available as of SAP NetWeaver 7.40 SPS10Required Business Functions DA_ARCHOBJ_STANDARD_2, ILM


Page 25 of 95

PrerequisitesYou have activated the business function Data Archiving: Standardization of Archiving Objects - 2 (DA_ARCHOBJ_STANDARD_2).You have activated the Information Lifecycle Management (ILM) business function. For more information about SAP NetWeaver Information LifecycleManagement, see SAP Library under SAP ERP SAP ERP Central Component SAP ERP Enhancement Packages ERP Central ComponentEnhancement Package 5 Cross-Application Functions in SAP ERP Cross-Application Components Information Lifecycle Management .

FeaturesYou can use these functions to control the deletion, archiving and destruction of correspondence requests.

On the selection screen of the write program for archiving object CORRSPND in the Process Control group box, you can specify whether the program is to berun in test or update mode.In the section on the log settings, you can specify the type of log to be issued (complete detailed log or partial log) and how the log is output. Furthermore,you can enter a note on the archiving run.If you are using the archiving object within the framework of SAP NetWeaver Information Lifecycle Management and the prerequisites for this are satisfied(such as activation of the associated business functions), the ILM Actions box is shown in addition. With the aid of these actions, you can carry out archivingduring which the retention periods defined in the Information Retention Manager are evaluated. Furthermore, you can make snapshots (copies) of data ordestroy data that satisfies the appropriate criteria.You can also archive d

ERP 2005

Documents

Transcript of ERP 2005