ENhancement Package SAP PDF

What's New in SAP Enhancement Package 8 for ERP 6.
0
PDF download from SAP Help Portal:
http://help.sap.com/erp2005_ehp_08/helpdata/en/d6/8b5b55259a8418e10000000a4450e5/content.htm
Created on April 06, 2016
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
© 2016 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 purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE 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. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC Page 1 of 69
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Table of content
1 What's New in SAP Enhancement Package 8 for ERP 6.0
1.1 Support Package Stack 1
1.1.1 Cross-Application Components
1.1.1.1 Merge of Components
1.1.2 Accounting
1.1.2.1 Financial Accounting
1.1.2.1.1 Enhancements for Tax on Sales/Purchases and VAT
1.1.2.1.2 Collective Call of External Tax System
1.1.2.1.3 Enhancements for Automatic Payment Transactions for Customers an
1.1.2.1.4 Enhancements to Online Payments and Payments with Repetitive Cod
1.1.2.1.5 Enhancements for SAP Bank Communication Management
1.1.2.1.6 Cross-Component Check of IBAN Usage
1.1.2.1.7 Activation of Payment Release List per Company Code
1.1.2.1.8 Time Stamp for Change Documents in Real Estate Management
1.1.2.1.9 Public Sector Management
1.1.2.1.9.1 Public Sector Debt Management: Collection Strategy
1.1.2.1.9.2 Public Sector Debt Management: Debt Set Management
1.1.2.1.9.3 Public Sector Debt Management: Asset Income Register
1.1.2.1.9.4 Enhancements for Budgeting and Availability Control
1.1.2.1.10 Financial Instrument: Letter of Credit
1.1.2.1.11 TRM, Money Market Enhancements
1.1.3 Logistics
1.1.3.1 Product Lifecycle Management (PLM)
1.1.3.1.1 Optimization of Performance with Engineering Record Database
1.1.3.1.2 KPI Dashboard for Engineering Record Data in SAP Lumira
1.1.3.1.3 Introduction of Change Documents for Engineering Records
1.1.3.1.4 Forwarding of Process Route Tasks in Engineering Records
1.1.3.1.5 E-Mails for Process Routes in Engineering Records
1.1.3.1.6 Support of Engineering Record Types in Global Process Route Temp
1.1.3.1.7 Enhancement of Process Route Log
1.1.3.1.8 Display of User Details for Process Routes
1.1.3.1.9 Enhanced Task Rejection for Engineering Records
1.1.3.1.10 Use of All PLM Web UI Objects in Global Process Route Templates
1.1.3.2 Materials Management (MM)
1.1.3.2.1 Incoterms Versions
1.1.3.3 SAP Retail
1.1.3.3.1 Fashion Management
1.1.3.3.1.1 Harmonized Processes for Wholesale, Retail (New)
1.1.3.3.1.1.1 Enhancements in Article Master for Fashion
1.1.3.3.1.1.2 Enhancements in Sales and Distribution and Materials Management
1.1.3.3.1.1.2.1 Season Management (New)
1.1.3.3.1.1.2.2 Value Added Services (New)
1.1.3.3.1.1.2.3 Business for High Fashion Brands (New)
1.1.3.3.1.1.2.4 Protected Species and Preference Management (New)
1.1.3.3.1.1.2.5 Application Variants (New)
1.1.3.3.1.1.2.6 Split or Change Purchase Orders (New)
1.1.3.3.1.1.2.7 ATP Confirmations in Fashion Management (New)
1.1.3.3.1.1.2.8 Order Scheduling (New)
1.1.3.3.1.1.2.9 Availability Overview in Sales Documents (New)
1.1.3.3.1.1.2.10 Mass Data Change in Sales Documents (New)
1.1.3.3.1.1.2.11 Characteristic Value Conversion (New)
1.1.3.3.1.1.2.12 Batch Determination in Deliveries (New)
1.1.3.3.1.1.3 Enhancements in Production Planning and Control for Fashion
1.1.3.3.1.1.3.1 Enhancements to Material Requirements Planning
1.1.3.3.1.1.3.2 Segmentation: Availability Check (ATP)
1.1.3.3.1.1.3.3 Enhancements in Demand Management (New)
1.1.3.3.1.1.3.4 Enhancements in Production (New)
1.1.3.3.1.1.4 Order Allocation Run (New)
1.1.3.3.1.1.5 Integration with Other Components
1.1.4 Human Capital Management
PUBLIC Page 2 of 69
1.1.4.1 Support Package 18
1.1.4.1.1 HCM, Personnel & Organization 09
1.1.4.1.1.1 HR Professional: Generate Processes and Forms
1.1.4.1.1.2 HR Professional: Enhancements to HCM P&F Roadmap Forms
1.1.4.1.2 HR Professional: Simplified Field Control
1.1.4.1.3 HCM, Personnel & Organization Countries FP5
1.1.4.2.1 PCC for the Payroll Administrator- New Payroll Experience
1.1.4.2.2.1 HR Professional: Extended Search Help
1.1.4.2.3 HR Professional: International Infotypes
1.1.4.3.1.1 HR Professional: Conversion to Dynamic Processing Rules
1.1.4.3.1.2 HR Professional: Employee Recognition
1.1.4.3.1.3 HR Professional: Employee History in Master Data Application
1.1.4.3.1.4 HR Professional: External Personnel Number Assignment
1.1.4.3.2 HR Professional: Read-Only Roadmap Form
1.1.4.3.3 HR Professional: Search Enhancements
1.1.4.3.4 Payroll Control Center - New Payroll Experience
1.1.4.4.1 Payroll Control Center (Feature Pack 2)
1.1.4.4.2 Declustering for Concurrent Employment Payroll Result
1.1.4.4.3.1 HR Professional: Enhancement to Dynamic Processing Rules
1.1.4.4.3.2 HR Professional: Enhancements to the Roadmap Form
1.1.4.4.3.3 HR Professional: HR Object Delimitation
1.1.4.5.1 HCM, Employee Self-Service on SAP UI5 2
1.1.4.5.1.1 Record Working Times SAP UI5 (CATS)
1.1.4.5.2 HCM, Personnel & Organization 05 (Reversible)
1.1.4.5.2.1 HR Professional: Dynamic Processing Rules
1.1.4.5.2.1.1 HR Professional: Enriched Context-Relevant Navigation
1.1.4.5.3 HR Professional: Country-Specific Information
1.1.4.5.4 HR Professional: New Role Version and Launchpad Enhancements
1.1.4.5.5 HCM Processes & Forms Enhancements
1.1.4.5.6 HCM, Manager Self-Service on SAP UI5 3
1.1.4.5.6.1 Archive/Destroy Notes Data
1.1.4.5.7 Destruction of PBC Document Data
1.1.4.5.8 Payroll Control Center for the Payroll Process Manager
1.1.5 Industries in SAP ERP
1.1.5.1 SAP Student Lifecycle Management
1.1.5.2 SAP Public Sector
1.1.5.2.1 SAP Public Sector Collection and Disbursement (PSCD)
1.1.5.2.1.1 Connecting Several CC Systems to a FI-CA System
1.1.5.2.1.2 Collaborative Liability
1.1.5.3 SAP Utilities
1.1.5.3.1 Simplified Master Data Synchronization
1.1.5.3.2 Add Customer-Specific Fields to the Device Master Data
1.1.5.3.3 Copy Values from EDM Profile Version in Transaction EEDM01
1.1.5.3.4 Generate EDM Profile Header and Allocate a Register
1.1.5.3.5 Quantity Determination on the Basis of Meter Reading Profiles
1.1.5.3.6 Profile Calculation Using the Formula Calculation EEDMCALCMA
1.1.5.4 SAP for Healthcare
1.1.5.5 SAP for Media
1.1.5.5.1 Media, Provider Contract
1.1.5.5.2 Media: Master Data Objects Provider Contract, Product
1.1.5.5.3 Integration with Revenue Accounting
1.1.5.6 SEM - Strategic Enterprise Management
1.1.5.6.1 FIN_ACC_GC_CHKDGT: Business Function Financials, Group Close, Ch
1.1.5.6.1.1 Check Digits
1.1.5.6.1.2 Consolidation Monitor
PUBLIC Page 3 of 69
1.1.5.6.1.3 Tasks
1.1.5.6.1.4 Data Entry
1.1.5.6.1.5 Reconciliation
1.1.5.6.1.6 Reclassification
1.1.5.6.1.7 Consistency Check for Validation
1.1.5.6.1.8 Technical Reports
1.1.5.6.1.9 Consolidation Group Change
1.1.5.6.1.10 Consolidation of Investments
1.1.5.6.1.11 Deviating Shares
PUBLIC Page 4 of 69
1 What's New in SAP Enhancement Package 8 for ERP 6.0
This section contains all release notes. You can use the navigation structure on the left to find a specific release note.
1.1 Support Package Stack 1
This section contains all release notes. You can use the navigation structure on the left to find a specific release note.
1.1.1 Cross-Application Components
1.1.1.1 Merge of Components
To simplify the component structure, several component versions have been merged.
Technical Details
Technical Name of Product Feature N/A
Product Feature Is Changed
Country Dependency Valid for all countries
Software Component Version SAP_APPL 618
Application Component CA
Availability SAP Enhancement Package 8 (SPS 0) for SAP ERP 6.0
Additional Details
The following components will be merged:
Former Software Component Merged to Software Component
EA-APPL SAP_APPL
EA-APPL-GLO SAP_FIN / SAP_APPL / EA-PS
EA-FI SAP_FIN
EA-FIN SAP_FIN
EA-GLTRADE-GLO EA-GLTRADE
EA-PS-GLO EA-PS
EAFASH EA-RETAIL
C-CEE SAP_APPL/ SAP_FIN
See also
For more information, see 2171334 .
1.1.2 Accounting
1.1.2.1 Financial Accounting
1.1.2.1.1 Enhancements for Tax on Sales/Purchases and VAT
Deactivating Tax Codes

You can define for a tax code that it is to be deactivated. This tax code is then no longer displayed in the input help when posting, for example. You can
continue to use the tax code, however, for example, for reversals. This allows you to phase out tax codes gradually.
Partly Exempt Organizations
To use the following functions, you must first activate the business function Partly Exempt Organizations (FIN_ACC_PEO).
When posting using FMPEBADJ, you can also post to other accounts and account assignments in the event of errors. By using other account
assignments for the tax adjustment posting, you can now post tax adjustments for transactions that could previously no longer be posted, for example, if
the asset has already been retired. For more information, see the documentation for program FMPEB_TAXADJUST.
PUBLIC Page 5 of 69
You can use transaction FMPEBTRANS in FI or transaction F891 for clearing requests in PSM to enter transfer postings that contain only G/L account
items and also contain the respective tax for each of these G/L account items line by line. These are indicated here accordingly, which means there is a
clear assignment between the G/L account posting item and the relevant tax in the FI document. This is not the case with other FI documents because
the tax for these is calculated, entered, and posted for each document and tax code. For more information, see the documentation for program
FMPEB_TAXCALC.
Calculating Tax on Sales/Purchases for BAPIs
Caution
You cannot use the function for India and Brazil.
Method FI_TAX_SERVICES->CALCULATE provides a function for calculating tax on sales/purchases. This method allows tax data for BAPIs to be
filled more easily. The document transferred does not have to be complete, a balance of 0 is generated internally, and the tax is calculated and returned
based on this. A total amount can be predefined for the tax, which is distributed across the tax calculated. For more information, see the documentation
for class FI_TAX_SERVICES. The method can be called using function module FI_TAX_SERVICES_CALCULATE by means of a Remote Function
Call.
Technical Details
Product Feature Is New
Software Component Version SAP_FIN 618
Application Component FI-GL-GL (Basic Functions)
Availability SAP enhancement package 8 for SAP ERP 6.0

For information about availability for lower SAP enhancement packages, see the SAP Notes specified in the “More
Information” section, under Validity .
Effects on Customizing
To set a tax code to inactive, in Customizing for Financial Accounting (New) or Financial Accounting , choose the Customizing activity Define Tax Codes
for Sales and Purchases (transaction FTXP) under one of the following paths:
Financial Accounting Global Settings (New) Tax on Sales/Purchases Calculation
Financial Accounting Global Settings Tax on Sales/Purchases Calculation
More Information
For more information, see the following SAP Notes:
2074351 : Deactivate tax code for input help

2203566 : PEO: Initialization of certain fields in order to post incorrect postings with taxes without the incorrect account assignment
1923189 : PEO: FF747 when printing a parked clearing
2070697 : Filling tax information for BAPIs
1.1.2.1.2 Collective Call of External Tax System
You use this function to collect the line items for a Remote Function Call (RFC) to external tax calculators for tax calculation and to then transfer all line items
collected to the external tax calculators in one call. You can then configure this as required or take it into account if you are using your own programs. One
benefit of this is improved performance, for example. For more information, see the documentation for class CL_XTAX_RULES_RFC.
The following enhancements are also currently available:

The buffering of RFCs for external tax calculators for tax calculation has been improved. You can improve performance by switching to method 2 for
buffering, for example. For more information, see the documentation for class CL_XTAX_CALCULATE_TAX_DOC_BUFF.
The RFCs for external tax calculators can be logged using SET/GET parameters and transaction SAAB. This allows you to log which data is transferred
to and returned from the external calculators:
You can determine and display the RFC data without debugging.
You can save and manage this data with transaction SAAB.
For more information, see the documentation for class CL_XTAX_RFC_LOG.
Technical Details
Country Dependency Valid for USA and Canada
Application Component FI-GL-GL (Basic Functions)
Availability SAP enhancement package 8 SPS01 for SAP ERP 6.0

PUBLIC Page 6 of 69
More Information
SAP Note 2191227
1.1.2.1.3 Enhancements for Automatic Payment Transactions for

Customers and Suppliers
The following new features and enhancements are now available for payment program F110:
Different formats per payment method

Ariba connection
Simplified option to reset a payment run in the event of errors
Direct navigation when analyzing payment data
Number of special G/L transactions to be taken into account by the payment program can be configured
Technical Details
Application Component FI-AP-AP-PT

FI-AR-AR-PT

Additional Details
Payment Method Formats

For payment methods in the country, you can now specify a different format for the Payment Medium Workbench (PMW) for each company code or house
bank.
Ariba Connection
When you create payment advice notes, you can now also connect to Ariba in addition to using the existing output options (print, fax, e-mail, IDoc, and XML).
Payment Run Reset

In the event of errors, you can now reverse the payment run following posting by using repair program RFF110S_REVERSE, assuming the conditions outlined
in the program documentation have been met.
Direct Navigation When Analyzing Payment Data

You can now directly display the details for the objects to be analyzed (such as the invoice document or payment document, master data, or bank chain):
In the payment list (program RFZALI20) and the status display for payments for cross-payment-run payment media (transaction FBPM2) by double-
clicking
In payment proposal processing and when displaying proposal runs and payment runs (transactions F110, F111, FBZ0, and FBZ8) using the new
Display Object function
Effects on System Administration

The requirements and settings for the Ariba integration are outlined in the Administrator Guide at https://help.sap.com/se4aribanetsnc .
In Customizing for Accounts Receivable and Accounts Payable , choose Business Transactions Outgoing Payment Automatic Outgoing Payments
and configure the following settings:
To specify a different PMW format for PMW payment methods for each company code or house bank in cases where the remaining attributes for the
payment method are the same, choose Use in company codes in change mode for the activity:
Payment Method/Bank Selection for Payment Program Set Up Payment Methods per Country for Payment Transactions
You can enhance or influence the direct navigation for payment data using a Business Add-In (BAdI) in enhancement spot
FI_PAYM_DATA_DRILL_DOWN:
Payment Proposal Processing BAdI: Navigation for Customer Fields or Fields not Supported by SAP
To change the number of special G/L transactions to be taken into account by the payment program, which was previously limited to 10, for each
PUBLIC Page 7 of 69
company code, choose:
Payment Method/Bank Selection for Payment Program Set Up All Company Codes for Payment Transactions
More Information
1943453 : PMW format depending on house bank and company code

1967254 : Exit to create payment advice notes (Ariba Integration)
2073200 : FBZP FB05 - only 10-digit parameter for special G/L transactions
2188630 : FB05 history missing for long field for special G/L indicator
2125220 : F110: Cancel payment run
2163855 : RFZALI20 - Enable navigation
1.1.2.1.4 Enhancements to Online Payments and Payments with

Repetitive Code
Arising from enhancements to online payments and repetitive payments, you can now use additional checks and further address fields.
Technical Details
Application Component FI-BL-PT-AP

FIN-FSCM-CLM-CM

Additional Details
If, in the configuration for the payment method, you have specified in the country to which countries payments can be sent, the system checks this
configuration as soon as the payment request is being entered. If the country of the payee is not permitted for the selected payment method, the system
issues the error message at this point; previously this message did not prevent the payment from being executed until the payment run was being processed.
You can activate a new release for the release of payment requests. The system then checks the release of activity 43 ( Release ) rather than 02 ( Change ).
When free-form payments (transaction FIBLFFP) are entered, you can show additional fields for entry (function key F5 ) on the address screen that may be
relevant for the payment. These include the language, the form of address, additional name fields, and the fax number of the payee.

To use activity 43 ( Release ) for authorization object F_PAYRQ, follow the instructions outlined in the documentation for SAP Note 2150759 . Adjust the
authorization profiles and the user master data accordingly.
More Information
2150758 : New activity 43 (Release) for the authorization object F_PAYRQ

2189609 : RVND FRFT no check for permitted country of destination of payment method
2195810 : FIBLFFP account holder, name, and additional fields
1.1.2.1.5 Enhancements for SAP Bank Communication

Management
The new features and enhancements for SAP Bank Communication Management enable you, for example, to formulate rules in the rule currency, implement
exceptions for the reservation of run IDs, schedule the creation of payment batches during the payment run, create the payment IDoc as the format for
Payment Medium Workbench (PMW), and to display additional fields as well as navigate uniformly to related objects in the release and monitoring
transactions.
Technical Details
PUBLIC Page 8 of 69
Application Component FIN-FSCM-BNK

Additional Details
When defining rules, you can now enter the local currency of the company code and define amounts in rule currency as selection criteria.
The reservation of run IDs for SAP Bank Communication Management (transaction OBPM5) does not allow differentiation of payment runs that the system has
scheduled automatically, for example, runs for online payments or salary payments. You can now implement this differentiation based on your own internal
guidelines.
When scheduling a payment run (transaction F110 or F111), you can now also schedule the generation of the related payment batches by specifying program
SAPFPAYM_MERGE as a list. In addition, when creating payment media, you can use payment methods that use the PMW format IDOC (previously program
RFFOEDI1) to create the payment IDoc PAYEXT.
In the transactions for releasing and monitoring payment batches, you can display the amount in payment currency for the batches provided this currency is
unique for all payments. You can show customer fields for batches and payments once you have filled the fields accordingly in a BAdI. Furthermore, in the
release (BNK_APP) and monitoring (BNK_MONI, BNK_MONIP) transactions, you can now navigate uniformly to the displayed objects for payment (for example,
payment document, master data, or bank chain) by double-clicking. You also have the option to implement this navigation for customer fields as well. In the
case of transaction BNK_MONIP, activation by means of the user parameter BNK_MONIP_NAVIGATION is required for this.
You implement the exception rules for the reservation of run IDs as a Business Add-In (BAdI) in the enhancement spot FIBL_MPAY_RESERVATION. For more
information, see the documentation for the related settings:
Accounts Receivable and Accounts Payable Business Transactions Outgoing Payments Automatic Outgoing Payments Payment Media
Define Identification for Cross-Payment Run Payment Media
You implement additional fields in the release and monitoring transactions BNK_APP and BNK_MONI as a Business Add-In (BAdI) in the enhancement spot
BNK_BADI_UI_ENHANCE:
Financial Supply Chain Management Bank Communication Management Basic Settings BAdI: Additional Fields for BNK_MONI and BNK_APP
You can enhance or influence direct navigation from the release and monitoring transactions BNK_APP, BNK_MONI, and BNK_MONIP to the displayed objects
by means of a BAdI in the enhancement spot FI_PAYM_DATA_DRILL_DOWN:
Financial Supply Chain Management Bank Communication Management Basic Settings BAdI: Navigation for Customer Fields or Fields not
Supported by SAP
In the settings for rule maintenance, you can now use the company code currency and the amounts in rule currency. You can find the settings under:
Financial Supply Chain Management Bank Communication Management Payment Grouping Rule Maintenance
The new PMW format IDOC replaces the scheduling of program RFFOEDI1 via the settings for EDI-capable payment methods that you made previously in the
house bank (transaction FI12, table T012E). Remove these settings for EDI-capable payment methods. Instead, create a payment method with the PMW
format IDOC or define the PMW format IDOC in the settings for the payment method in the country as the format in the company code. You can then define
variants for the payment medium program SAPFPAYM in transaction OBPM4 and in this way create the payment IDoc in SAP Bank Communication
Management as well.
More Information
1994602 : BNK_MONI Display of payment currency, if unique

1999340 : BCM rule maintenance: Missing rule currency amount and local currency
2052436 : PMW/BCM: Exception rule for reservation, in particular for HR
2089199 : PMW - forcing sequential payment medium creation
2095820 : SAPFPAYM_MERGE: Scheduling using payment program
2147168 : SAP Bank Communication Management - Integration of program RFFOEDI1
2170198 : BNK_MONI BNK_APP - BAdI for navigation to payment data
1.1.2.1.6 Cross-Component Check of IBAN Usage
You use this function to check the following:

Is it permitted to change an IBAN?
You can specify which application is permitted to change an existing IBAN. A change can then no longer be made by all other applications. You want to
specify, for example, that an IBAN that is used both in the vendor master record and in Real Estate Management can only be changed by an accounting
clerk for the vendor invoice and based on the dual control principle.
Can an IBAN be deleted?
You can delete an IBAN (from table TIBAN) when the original data record (such as the vendor master record) has been removed from the system (and
archived, for example). The deletion program (RFIBAN_DEL, SAP Note 1809452 ) first checks whether the IBAN is still being used in another
application.
PUBLIC Page 9 of 69
Technical Details
Software Component Version SAP_FIN 618 SPS01

SAP_FIN 617 SPS06
SAP_APPL 616 SPS08
SAP_APPL 606 SPS14
SAP_APPL 605 SPS14
SAP_APPL 604 SPS17
SAP_APPL 603 SPS16
SAP_APPL 602 SPS17
SAP_APPL 600 SPS27
Application Component FI-AP-AP-MD (Master Data)

FI-AR-AR-MD (Master Data)
FI-BL-MD (Master Data)
To be able to use the new check functions, you need to enter the checks for the function modules to be used into a business transaction event (BTE). You
configure these settings in Customizing:
Financial Accounting Financial Accounting Global Settings Business Transaction Events
Financial Accounting (New) Financial Accounting Global Settings (New) Tools Customer Enhancements Business Transaction Events
For more information, see the documentation of the corresponding BTEs. This documentation is available under Environment Info System (P/S) :
Under BTE Interval Search , enter one of the following Business Transaction Events :
00003090 : For the check to determine whether the IBAN can be changed.
00003091 : For the check to determine whether the IBAN can be deleted.
Choose Execute (F8) and then ( Documentation ).
More Information
For more information, see SAP Note 2041942 .
1.1.2.1.7 Activation of Payment Release List per Company Code
Arising from enhancements to the Payment Release List (transaction FPRL_LIST), you can now optimize the processing of large volumes of data and the
Payment Release List per company code.
Technical Details
Application Component FI-AP-AP-PT

FI-AR-AR-PT
FI-BL-PT-AP
FI-LOC-EPI-CN

Additional Details
If the number of items to be approved is considerable, the process to select the items not yet assigned can take some time, for example. The system
therefore restricts the number of items to be displayed to 200 and displays an information message once this threshold value has been reached. This message
contains information indicating that you can adjust the threshold value to reflect your personal requirements by using the custom selections per tab page.
The Payment Release List can now be activated per company code. The system still takes into account for activated company codes the settings for the
application specified at client level for the Payment Release List. In company codes that have not been activated for the Payment Release List, the users can
use payment proposal processing (transaction F110).
PUBLIC Page 10 of 69
Specify all company codes for which the settings for the Payment Release List are to be active:
Accounts Receivable and Accounts Payable Business Transactions Outgoing Payments Automatic Outgoing Payments Payment Release List
Settings for Payment Release List Specify Company Codes
More Information
2017091 : FPRL_LIST Performance problems with large datasets

2116384 : PRL: Activation per company code
1.1.2.1.8 Time Stamp for Change Documents in Real Estate

Management
This function ensures that the time stamp of change documents created in Flexible Real Estate Management is derived from the system time.
Technical Details
Application Component Flexible Real Estate Management (RE-FX)
Available as of SAP Enhancement Package 8 SPS01 for SAP ERP 6.0
Additional Details
In earlier releases, change documents created in Flexible Real Estate Management were given the sy-zonlo time stamp, which is derived from the time in
the time zone of the user who last changed an object. When users located in different time zones made changes related to the same real estate object, the
chronological sequence of the time stamps of change documents was therefore inconsistent.
Effects on Existing Data

Existing change documents remain unchanged. The system creates all new change documents with a time stamp that is derived from the system time. For
this reason, there may be a time offset between change documents that were created in earlier releases and change documents created as of this release.
The time stamps of all change documents created as of this release are consistent, that is, are derived from the system time.

As of this release, it is no longer necessary to implement the correction described in SAP Note 2104832 .
See also
Flexible Real Estate Management (RE-FX)
1.1.2.1.9 Public Sector Management
1.1.2.1.9.1 Public Sector Debt Management: Collection Strategy
Technical Details
Country Dependency Valid for all Countries
Software Component Version IS-PS-CA
Application Component IS-PS-CA
Available as of SAP EHP 8 for SAP ERP 6.0
This product feature enables you to derive the collection strategy using BRFplus or decision management services. For example, you may have a collection
strategy for debtors who are registered for bankruptcy. You may report on a modular level, too.
1.1.2.1.9.2 Public Sector Debt Management: Debt Set

Management
Technical Details
This product feature enables you to manage debt sets.

You can do the following with debt sets:
BRFplus or data management services derivation
Manual management
Link to a collection strategy
Link to an enforcement action
Derive dunning groups
1.1.2.1.9.3 Public Sector Debt Management: Asset Income

Register
Technical Details
Asset income register enables you to describe the financial situation of your debtors. You may create objects for each debtor asset and positive or negative
income.
Asset income objects are modelled in SAP CRM with decision basis functionality and replicated into SAP ERP, where they are used to make decisions such
as:
Create an enforcement action against an asset income object
Write off debt
Approvals and payment arrangement amounts
1.1.2.1.9.4 Enhancements for Budgeting and Availability Control
Budgeting and Availability Control (AVC) offers the following new functions:
Mass Approval for Preposted Budget Entry Documents
With this function, you can approve or reject a wide selection of preposted budget entry documents. It is irrelevant whether such documents are
integrated into a workflow item or not. If the corresponding preposted document is in a workflow item, this function also completes the workflow item.
The main purpose of this function is to find and process pending preposted documents that could not or cannot be approved or rejected in workflow or
using the Budgeting Workbench (FMBB).
Trace Log and Waiting Queue for Exclusive AVC Locks
With these functions, you can test and activate a trace log and a queue for exclusive locks to avoid lock collisions in situations of heavily parallelized
processes or when many users access the same control object at almost the same time.
Display Derived FM Account Assignments
This Web Dynpro application allows you, for example, to find out the corresponding control object for a posting address, before you use it in a budget-
consuming document.
Activate Derivation Traces for Availability Control
With this function, you can view and change the current trace status of the following derivation strategies:
Derivation of the control object
Derivation of the activity group
Derivation of the checking horizon
Derivation of the tolerance profile
Technical Details
Software Component Version EA-PS 618
Application Component PSM-FM-BCS (Budget Control System)
Availability SAP Enhancement Package 8 for SAP ERP 6.0, Add-On EA-PS
Additional Details
Mass Approval for Preposted Budget Entry Documents

Choose Public Sector Management Funds Management Budgeting Budget Control System (BCS) Tools Entry Documents Approve
Preposted Entry Documents (FMBUD_APP). For more information, see ( Program Documentation ).
Trace Log and Waiting Queue for Exclusive AVC Locks

Availability control sets exclusive locks to perform accurate budget availability checks. In situations of heavily parallelized processes or when many users
access the same control object at almost the same time, lock collisions occur, which lead to error messages such as User X locks Y (error messages
MC601, FMAVC123, FMAVC124, or FMAVC125).
You can test the trace log and the queue for exclusive locks, without activating these system features for other users. Choose Public Sector Management
Funds Management Budgeting Budget Control System (BCS) Tools Availability Control Test Trace and Queue for Exclusive Locks
(FMAVC_TEST_QUEUE). It allows you to compare the system behavior of parallelized tasks requesting the same exclusive lock, with or without queue. If you
test the trace logging, you can later use the program RFWQENQ_ENQ_SHOW_TRACE to display the trace items.
With program RFWQENQ_ACTIVATE_QUEUE, you can activate the trace log and the queue for exclusive locks. If lock collisions occur, you first use the trace
log to obtain an overview of the frequency of such lock collisions. You display the trace log with program RFWQENQ_ENQ_SHOW_TRACE. With program
RFWQENQ_ENQ_DEL_TRACE, you can delete the trace log when it is no longer needed.
If possible, only activate the queue during business hours, when you expect a high frequency of lock collisions.
Display Derived FM Account Assignments

Choose Public Sector Management Funds Management Information System Master Data Indexes FM Account Assignments Display Derived
FM Account Assignments (FMBAS_DERI_ACC). For more information, choose ? Display Quick Help in the Web Dynpro application.
Activate Derivation Traces for Availability Control

Choose Public Sector Management Funds Management Budgeting Budget Control System (BCS) Tools Availability Control Activate
Derivation Trace (FMAVCDERITRACE). For more information, see ( Program Documentation ).

Before you can use the Display Derived FM Account Assignments Web Dynpro application (transaction FMBAS_DERI_ACC), you must activate the
corresponding web service FMBAS_GAF_SHOW_DERIV_ACC in Customizing for SAP NetWeaver under Application Server Internet Communication
Framework Configure and Activate HTTP Services Individually (SICF).
1.1.2.1.10 Financial Instrument: Letter of Credit
With this feature you can use the new financial instrument letter of credit (L/C) within SAP Treasury and Risk Management.
L/C Lifecycle Management
The entire life cycle of the new financial instrument Letters of Credit, comprising order execution, expiration, rollover, termination, and Presentations of
Documents Against Letters of Credit, can be continually mapped in the Trade Finance area. You can map L/C transactions to product category Letter of
Credit (850).
Financing transactions for L/C, including import bill advance loan for the buyer and export bills negotiation for the seller, are integrated.
Accounting
The product category in trade finance is enabled in position management and accounting.
Each presentation under a letter of credit can be valuated independently, so that the gain or loss caused by foreign currency valuation can be
calculated into each presentation, which can be reflected in position, and handled in accounting.
The liabilities stated in the HGB and IFRS for letter of credit can be reflected in position, and handled in accounting.
The line items for letter of credit are enabled for posting with special G/L indicator.
Correspondence
Correspondence process is enabled for the product category in trade finance.
The system is pre-configured with the PDF format to view L/C information in correspondence.
The system is pre-configured with the following SWIFT messages. You can also make changes to the existing settings and set up other formats.
Applicant - Application for Documentary Credit Applicant - Notification of Issuance of Documentary Credit
MT798<770> LC Application Index MT798<771> LC Notification of Issuance Index
MT798<700> LC Application Details MT798<700> LC Notification of Issuance Details
MT798<701> LC Application Extension MT798<701> LC Notification of Issuance Extension
Technical Details
Technical Name of Product Feature FIN_TRM_TRADE_FIN_PF01
Software Component Version EA-FINSERV 618

SAP_APPL 618
Application Component Treasury and Risk Management (FIN-FSCM-TRM)
Availability SAP Enhancement Package 8 (SP01) for SAP ERP 6.0
Required Business Functions FIN_TRM_TRADE_FIN
You make customizing settings for TRM, New Instrument, Letter of Credit under Treasury and Risk Management Transaction Manager Trade Finance
.
1.1.2.1.11 TRM, Money Market Enhancements
With this feature you can use scaled conditions, accrued interest conditions with different rates, and condition groups for the existing product category 550
( Interest Rate Instrument ), as well as the new product category 580 ( Current Account-Style Instrument ), for which negative nominal is supported in addition
to scaled condition and parallel condition group. However, product category 580 only supports final repayment, without annuity repayment or installment
repayment.
Technical Details
Technical Name of Product Feature FIN_TRM_MME_PF01
Software Component Version EA-FINSERV 618

SAP_ABA 750
Application Component FIN-FSCM-TRM (Treasury and Risk Management)
Required Business Functions FIN_TRM_MME
See Also
Current Account-Style Instruments
Scaled Conditions
Accrued Interest
Condition Groups
1.1.3 Logistics
1.1.3.1 Product Lifecycle Management (PLM)
1.1.3.1.1 Optimization of Performance with Engineering Record

Database
This feature enables you to significantly speed up your processing of engineering record data. To achieve this, you migrate change items in engineering
records from the case management-based XML storage to the engineering record database tables.
Technical Details
Technical Name of Product Feature ERP_801_PLM_ER_DB
Software Component Version PLMWUI 748
Application Component PLM-WUI-OBJ-ECR (Engineering Change Record)
Required Business Functions /PLMU/ER_2 (Engineering Record Development 2 in PLM Web UI)
Additional Details
To perform the migration, use the following report and follow the detailed instructions in the report documentation in the system:
Migrate Change Items from XML Storage to Engineering Record Database (/PLMI/ER_CI_TRANSFER)
This is the report to migrate engineering record change items.
When the change items are migrated, you can run these follow-up reports:
Delete Engineering Record Change Items From XML Storage (/PLMI/ER_CI_DELETE).
This is the report to delete migrated change items from XML storage.
Set Migration Status for Engineering Record Change Items (/PLMI/ER_CI_SET_TRANSFER_STA).
This is the report to define the system behavior for where-used checks for change items.
To enable this feature, set the parameter value A or B, based on your requirements, for the parameter Switch for Engineering Record Database
(ER_CI_PERSISTENCY) in the Additional Settings Customizing activity under Logistics - General Product Lifecycle Management (PLM) PLM Web
User Interface Objects in PLM Web UI Engineering Record .
For more information, see the documentation of the Additional Settings Customizing activity in the system.
1.1.3.1.2 KPI Dashboard for Engineering Record Data in SAP

Lumira
This feature enables you to analyze engineering record data based on engineering record types. You can do the following:
Generate a core data services (CDS) view that creates KPIs for engineering records. This CDS view can then, for example, be consumed in SAP
Lumira.
View and analyze a predefined example set of key performance indicators (KPIs) for engineering record header data and change item data in reports
available in the SAP Lumira Cloud.
Technical Details
Technical Name of Product Feature ERP_801_PLM_ER_DB
Additional Details
Note that the business function mentioned above is not a prerequisite for viewing the example reports in the SAP Lumira Cloud.
Any change items that you wish to include in your customer-specific CDS view must first be migrated to the engineering record database. For more
information, see Optimization of Performance with Engineering Record Database. Engineering record header data is available without this migration and you
can use the report /PLMI/PLM_ER_CDS_VIEW_ANALYSIS to generate a CDS view for header data.
If you only use SAP standard tables for your engineering record header data, you can use the default CDS view /PLMI/C_ER_STDHD or the DDL source
/PLMI/C_ER_STD_HDR_ANLYS delivered by SAP. It is not necessary to generate your own CDS view in this case.
For information on how to use generated CDS reports in SAP Lumira, see the documentation in your SAP Lumira product.
1.1.3.1.3 Introduction of Change Documents for Engineering

Records
This feature enables you to view and analyze changes, that is, insertions, deletions, or updates, that have been made to an engineering record by choosing
Additional Functions – Display Change Documents .
Change documents are available for changes made to the following change document objects:
Engineering Record Header
Change Items
Document-Object Link
Classification
The changes are displayed in a table, and you can quickly and easily see, for example, the user who made a change or the type of change.
Technical Details
Technical Name of Product Feature ERP_801_PLM_ER_CDOC
Additional Details
Any change items that you wish to include in your change documents must first be migrated to the engineering record database. For more information, see
Optimization of Performance with Engineering Record Database.
This feature is enabled by default for change items and document-object links.
To enable this feature for classification, additional settings are required in the Maintain Object Types and Class Types Customizing activity under
Logistics - General Product Lifecycle Management (PLM) Classification Classes Maintain Object Types and Class Types . For more information,
see the documentation of the Customizing activity in the system.
To enable this feature for the engineering record header, additional settings are required in the Create Attribute Profile Customizing activity under
Logistics - General Product Lifecycle Management (PLM) Case Management Create Attribute Profile . Under Assign Attributes , mark the checkbox
in the Log column for case attributes for which you want the information to appear in the change documents.
1.1.3.1.4 Forwarding of Process Route Tasks in Engineering

Records
This feature enables you, as a processor or change coordinator, to forward process route tasks in your engineering records to other system users.
Select the task on the Process Route tab in your engineering record and choose Actions – Forward Task . The selection is only enabled if the task can be
forwarded, so, for example, it is not enabled if the task has been completed.
The following new columns on the Process Route tab were introduced to support this feature, and to allow you track who exactly processed a task and when:
Processor
Processed On
Processed At
Technical Details
Technical Name of Product Feature ERP_801_PLM_ER_TASKF
Application Component CA-EPT-PRO (Process Route)
1.1.3.1.5 E-Mails for Process Routes in Engineering Records
This feature enables you to do the following:
Manually send e-mails for tasks at any time by selecting a task and choosing Actions – Send E-Mail on the process route tab in your engineering
record.
Set up your system to automatically send e-mails when the processing status of a task related to your engineering record changes.
These e-mails contain the task details, as well as a direct link to the task. You can use the e-mail templates provided by SAP or create your own.
When the task status is changed, the e-mail based on the template is sent. The recipients of the mails are defined based on the people involved in the
process route task. The recipients, subject, and further attributes of the e-mail can be changed, if required.
Technical Details
Technical Name of Product Feature ERP_801_PLM_ER_EMAIL
To enable automatic e-mails, settings are required in the following Customizing activities under Logistics - General Product Lifecycle Management
(PLM) PLM Web User Interface Objects in PLM Web UI Process Route :
Set Up E-Mail Notifications
BAdI: Extension of E-Mails for Process Route Tasks
To enable the Send E-Mail button for manual e-mails, settings are also required in the Set Up E-Mail Notifications activity.
For more information, see the documentation of the Customizing activities in the system.
1.1.3.1.6 Support of Engineering Record Types in Global Process

Route Templates
This feature enables you to set up engineering record types for the object type PLM_ECR (engineering records) for use in global process route templates and
when loading and inserting process routes in your engineering records in the PLM Web user interface.
You can assign a record type to a global process route template. If you assign a record type to a global process route template, then this global process route
template can only be used for this type of engineering record and the record type cannot be subsequently be changed.
If you do not use this feature, you cannot add record types to global process route templates and your global process route templates are valid for all
engineering records.
Technical Details
Technical Name of Product Feature ERP_801_PLM_ER_GPRT
To enable this feature, settings are required in the Set Up Record Type Customizing activity under Logistics - General Product Lifecycle Management
(PLM) PLM Web User Interface Objects in PLM Web UI Global Process Route Template .
For more information, see the documentation of the Customizing activity in the system.
1.1.3.1.7 Enhancement of Process Route Log
This feature improves the usability of the process route log in the PLM Web UI with the following changes:
The addition of status information, including icons to see the processing status of a task at a glance.
Improvements in the terminology.
The provision of a Detailed Log , showing the information about all of the actions executed for a selected task.
Technical Details
Technical Name of Product Feature ERP_801_PLM_ER_PRLOG
Additional Details
In the PLM Web UI, you open the process route log from the Process Route tab within, for example, an engineering record, by choosing Additional
Functions Process Route Log .
1.1.3.1.8 Display of User Details for Process Routes
This feature enables you to have greater transparency on exactly which user processed a task in a process route, by providing links to the processors in the
Process Tasks column. The link opens the following:
The User Details popup window if there is an individual processor listed in the column.
The Available Processors popup window if the agent type is a user group, job, or position.
The Team Definition tab if the team definition is configured for the engineering record, and the agent type is a user group, job, or position.
Technical Details
Technical Name of Product Feature ERP_801_PLM_PR_USER
1.1.3.1.9 Enhanced Task Rejection for Engineering Records
This feature enables you to specify the customer-specific handling of tasks related to engineering records when decisions are made for these tasks. To do
this, you can implement the SAP interface /PLMB/IF_PR_DECISION_SERVICE.
For rejection decisions for the object type PLM_ECR (Engineering Record), SAP delivers a default class /PLMI/CL_ECR_SRV_DEC_REJECTION. This
default class causes the system to cancel parallel tasks, skip sequential tasks, and, depending on other Customizing settings, switch the status, or load a
new process route template.
A parallel change approval process is also available, which allows the system to take immediate action if a corresponding decision service is assigned when
an approver makes a rejection decision. You can display the previous decision in a rework task.
Technical Details
Technical Name of Product Feature ERP_801_PLM_ER_TASKR
To enable this feature, settings are required in the Define and Assign Decision Customizing activity under Logistics - General Product Lifecycle
Management (PLM) PLM Web User Interface Objects in PLM Web UI Process Route .
To switch the status, as mentioned above, settings are required in the Make Settings for Engineering Records Customizing activity under Logistics -
General Product Lifecycle Management (PLM) PLM Web User Interface Objects in PLM Web UI Engineering Record .
To set the system up to load a new process route template, as mentioned above, settings are required in the Set Up Automatic Template Determination
Customizing activity under Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Objects in PLM Web UI Process
Route .
For more information, see the documentation of the Customizing activities in the system.
1.1.3.1.10 Use of All PLM Web UI Objects in Global Process

Route Templates
This feature enables you to use process routes based on global process route templates in all GOS object types on the PLM Web UI. You specify the object
type when you create the global process route template. Once you activate the global process route template, the resulting process route is available for that
object type. The following object types are now available:
Engineering Record
Material
Document
Change Number
Recipe
Specification
Access Control Context
Material BOM
Assembly Group
Product Family
Product Item
Product View
Building Block
The default object type if not other object type is specified is the Engineering Record .
Technical Details
Technical Name of Product Feature ERP_801_PLM_GOS_GPRT
1.1.3.2 Materials Management (MM)
1.1.3.2.1 Incoterms Versions
With this feature you can use the Incoterms 2010 version in the procurement process. You enter the applicable Incoterms version in the Inco. Version field of
the document header. Depending on the version you select, the corresponding clauses are applied. The implemented logic guarantees that only Incoterms that
are valid for a specific version can be selected.
Also, to allow you to specify the location precisely, you can now enter up to 70 characters.
The following document types have been enhanced:
Purchase Order
Purchase Contract
Purchasing Info Record
Request for Quotation
Scheduling Agreement
Technical Details
Technical Name of Product Feature LOG_MM_INCO2010
Software Component Version SAP_APPL 618
Application Component MM-PUR (Materials Management, Purchasing)
Availability SAP enhancement package 8 (SP00) for SAP ERP 6.0
Effects on Data Transfer

If you have activated the business function LOG_SDMM_INCO_VERSIONS ( SD MM Incoterms Versions ), the Incoterm data is sent using the IDoc.
The following settings in Customizing are relevant:
Materials Management under Purchasing Vendor Master Incoterms Define Incoterms Versions .
Materials Management under Purchasing Vendor Master Incoterms Map Incoterms to Versions .
The following BAdI is relevant:
Materials Management under Purchasing Vendor Master Incoterms Business Add-Ins (BAdIs) Check Incoterms .
1.1.3.3 SAP Retail
1.1.3.3.1 Fashion Management
1.1.3.3.1.1 Harmonized Processes for Wholesale, Retail (New)
With this business function, you can use the harmonized processes for the vertical fashion companies. To activate this business function, you must first
activate the following business functions:
Other Enhancements for SAP Retail (ISR_RETAILSYSTEM)
Retail (EA-RET)
Harmonized Processes for Wholesale, Retail (Fashion_01)
Harmonized Processes for Wholesale, Retail (FASHION_02)
Material Segmentation Across Logistics (LOG_SEGMENTATION_03)
Datelines in Classical Purchase Order (ISR_RETAIL_PODATELINES)
Characteristic Values in Documents (ISR_RETAIL_CHAR_VALUES)
The following software components support these features:

SAP_APPL(618) SP1
EA-RETAIL(618) SP1
Technical Details
Technical Name of Business Function FASHION_03
Availability SAP ERP 6.0 Enhancement Package 8 Support Package Stack 01
Additional Details
For more information about the features provided with this business function, see the following release notes:
Enhancements in Article Master for Fashion
Enhancements in Sales and Distribution and Materials Management
Enhancements in Production Planning and Control for Fashion
Order Allocation Run (New)
Integration with Other Components
More Information
For more information about Fashion Management, see SAP Library on SAP Help Portal under Enterprise Management SAP ERP Application SAP
ERP Central Component Logistics SAP Retail Fashion Managemnet .
1.1.3.3.1.1.1 Enhancements in Article Master for Fashion
Fashion Management has made changes related to master data in the article master to support features related to maintenance of segmentation, fashion
attributes, seasons, characteristic value conversion, order allocation run (ARun), and material conversion. These changes can be broadly divided into changes
made for client data and changes made for site data.
Technical Details
Technical Name of Product Feature FASHION_20_MASTERDATA
Product Feature is New
Software Component Version EA-RETAIL (618) SP1
Application Component LO-FSH (Multichannel Fashion)
Required Business Functions Harmonized Processes for Wholesale, Retail 3 (FASHION_03)

Harmonized Processes Wholesale, Retail 3 (New)
Features
Segmentation
You can maintain the Segmentation Structure and the Segmentation Strategy fields as mandatory or optional fields in article master based on the settings
maintained in Customizing activity Define Attributes of System Messages under Logistics – General Material Master Basic Settings . In this
Customizing activity, for application Area SGT_01 and number 022, 030 and 084, maintain the system message category as W to set fields Segmentation
Structure and Segmentation Strategy as optional or maintain E to set the Segmentation Structure and Segmentation Strategy fields as mandatory.
You can extend an article to several DCs in article master. You can use the Multiple DC push button to maintain and fix segmentation related data for non-
reference DCs.
Using the Segment Specific MRP Data button, you can maintain segment level MRP data. This button is enabled only if you have created segmentation
structure and strategy with characteristics relevant for MRM and MRQ, and the segmentation relevant checkbox is selected.
You can maintain the following segmentation dependant master data:
Weights and volumes (Net Weight, Gross Weight, and Volume)
Client level data such as gross weight, net weight and volume are subject to reference handling. When an article is segmentation relevant, the
segmentation relevant gross weight, net weight and volume are referenced from their respective higher level data maintained at the article level.
Sales status (Scope of segmentation strategy is 1, that is, only if both requirement segment and stock segment are maintained)
Client level data such as distribution channel and validity are subject to reference handling.
You can copy the segmentation details of a variant to another variant. In addition, you can copy the segmentation relevant data of a segment combination to
another segment combination.
You can maintain segmentation relevance for functions such as, valuation type maintenance, MRP data, quantity based MRP Data, seasons management,
and pricing. You can use the segmentation data in the functions only if they are relevant for segmentation.
Fashion Attributes
You can maintain fashion attributes for an article at the client level. The system allows you to maintain up to three fashion attributes at any time. The values of
these fashion attributes can be maintained using the report program Maintain Fashion Attributes. Fashion attributes can be used to search articles. The
attributes maintained for an article also apply to all the variants of the article.
Seasons
Seasons form an important aspect in the product life cycle for the fashion industry. The production of fashion wear is determined or varies qualitatively
according to the season for which it is manufactured. You can maintain Season Usage as one of the Additional data of the article.
Additionally, the Season Active in Inventory Management checkbox is available in Logistics DC Fashion view and follows the IS-Retail Reference handling
in Article Master. For generic articles, the variant level inherits the value set at the generic article. However, you can modify the variant level value at the
variant level and the Article Master then maintains that value as deviated data specific to that variant.
The Season Active in Inventory Management checkbox is only available at plant level in the article master. Therefore, you can maintain the value of the
Season Active in Inventory Management checkbox at plant level. You can only change the value of the checkbox for a variant if the batches are not
maintained for the variant. For more information, see SAP Note 2026854 .
Season workbench is a one stop shop to manage seasons. You use this function to not only define, change, and delete season year, season, collection, and
theme, you also use it to assign articles (single articles, generic articles, and structured articles). You can assign season year, season, collection, and theme
to sales, purchasing and production views. You can specify the order, delivery, and sales windows for sales, and the order and delivery windows for
purchasing.
Material Conversion
You can use the report Conversion of Material (SGT_CONVERT_MATERIAL) to change information of the fields related to segmentation, season, order
allocation run (ARun) that cannot be changed using traditional material modification processes that make use of dialog, BAPI, or IDOC. You can also use this
report to change the Season Usage data for an article. In addition, you can change the setting for the Season Active in Inventory Management checkbox by
changing the article in the article master or by using direct input methods such as BAPI and IDoc.
Archiving Fashion Data in Master Data

The standard archiving objects are enhanced for segmentation and fashion relevant data in master data (MD). The relevant tables are listed below for the
archiving object, MM_MATNR (Material Master Records).
SGT_MADKA (Segmentation-Dependent Valuation Data)
SGT_MLGN (Segmentation-Dependent Material Data for Each Warehouse No.)
SGT_MLGT (Segmentation-Dependent Material Data for Each Storage Type)
SGT_MVKE (Segmentation | Sales Status)
SGT_MARM (Segmentation | Weights and Volumes)
NRF Code for Size and Color

The NRF Standard Color and Size Codes give retailers, vendors and manufacturers a common language for product color and size identification for EDI
purposes that supplements the information conveyed by UPC codes. The color and size codes are only available electronically, either from the NRF website,
or through our partners GXS, InterTrade and SPS Commerce.
You can maintain NRF codes for sizes using the Customizing activity Maintain NRF Codes for Sizes under Logistics - General Material Master
Retail-Specific Settings Settings for New Characteristic Value Storage .
You can maintain NRF codes for colors using the Customizing activity Maintain NRF Codes for Colors under Logistics - General Material Master
Retail-Specific Settings Settings for New Characteristic Value Storage .
The following Business Application Programming Interfaces (BAPIs) are enhanced:
BAPI_MATERIAL_MAINTAINDATA_RT
The following Remote Function Calls (RFC) are created:

FSH_SEASON_GETDATA_RFC
FSH_SEASON_MAINTAINDATA_RFC
The following intermediate documents (IDocs) are created:
ARTMAS07
ARTMAS08
ARTMAS09
More Information
Enhancements to Fashion Master Data
1.1.3.3.1.1.2 Enhancements in Sales and Distribution and

Materials Management for Fashion
With this feature, you can use the following enhancements for articles with fashion attributes in the logistics processes, Sales and Distribution and Materials
Management .
Season Management
Value Added Services
Business for High Fashion Brands
Protected Species and Preference Management
Application Variants
Split or Change Purchase Orders
ATP Confirmations in Fashion Management
Order Scheduling
Availability Overview in Sales Documents
Mass Data Change in Sales Documents
Characteristic Value Conversion
Batch Determination in Deliveries
Technical Details
Technical Name of Product Feature FASHION_20_LOGISTICS

1.1.3.3.1.1.2.1 Season Management (New)
You can define the production of fashion wear according to the season for which it is manufactured. Summer and winter are few examples of seasons. In the
fashion industry, a season belongs to a season year and have collections associated with it. The collections in turn have themes associated with them. You
can define a validity period for every season. The seasons assigned to the articles are used or determined in both the sales and the purchasing documents.
These seasons can then be transferred to the follow-on documents such as, outbound or inbound delivery and billing document.
Season Determination Log

You can change the seasons determined in the sales documents using the BAdI BADI_FSH_SEASONS. You can use the parameter CT_SEASON_LOG in the
BAdI BADI_FSH_SEASONS to enhance the season determination log with your own Reason Codes . These Reason Codes indicate whether the season is
determined or filtered in the document. The system displays the season information along with appropriate Reason Codes for the determined or filtered
seasons in the documents. The same values are stored in the database. This means that when you reopen the documents created earlier, the log only
displays the earlier entries. When you make the changes in the document, the system records the current changes and saves it again in the database.
Search Options: Season Determination in Sales Documents

Using one of the options − Search with Generic Key or Search with Specific Key − you can enable the system to determine seasons for an article. The
Search with Generic Key option enables the system to look for the best match and the specific season is displayed in the document. The other best matches
are available for selection. If you have maintained different combinations of sales details, the system determines the season by searching the sales details in
the following order of sequence:
Sales organization
Distribution channel
Customer
Customer group
Country
Region
Segmentation Based Seasons

In addition to maintaining seasons for non-segmentation relevant article (single, generic, or structured) or maintaining the seasons for blank segmentation
value, you can maintain seasons for the individual segmentation value of the article. You can maintain season only for the segmentation values that are
relevant for season. You can assign season to an article or variant for every segmentation value combinations as well as blank segmentation value.
When you place an order (such as sales order, purchase order, production order) for an article that is relevant for segmentation, system determines the season
according to the segmentation value you enter in the document and the updates the relevant season in the document. During the season determination
process, the system validates only the seasons maintained for the segmentation value you have entered in the document against the order and / or delivery
periods (maintained in the sales period, purchase periods, production periods, according to the order document). These order / delivery periods are maintained
in the season master using the season workbench transaction (FSH_SWB).
If you have not maintained any season records to the article for that particular segmentation value input against the order item, the system validates the
seasons maintained for the blank segmentation value against the relevant periods maintained in the season master. Season log is also generated with this
determination process. If you change the requirement segmentation value or stock segmentation value in the order document, the system triggers re-
determination of seasons accordingly. For example, if you change the segmentation value in the sales order, the system determines the season according to
the changes in the segmentation value. This is applicable in sales orders, purchase orders, and deliveries.
Existing Data
The following new transactions are available:
FSH_SRED – Mass Season Processing
FSH_SWB – Season Workbench
Retail Transactions
If you activate the business function FASHION_01, the Seasons function delivered with SAP Fashion Management will override the Seasons for SAP
Retail , in the following transactions:
ME2L ME2M
ME2K ME2J
ME2C ME2B
ME2N ME2W
VKP5 RWBE
WPOHF1 WRFAC01/02/03
Customizing
You make Customizing settings for this function in Customizing for the following areas:
Logistics – General under SAP Fashion Management Cross-Applications Seasons
Materials Management under Purchasing Purchase Order
Sales and Distribution under Sales Documents Sales Document Header
Sales and Distribution under Sales Documents Sales Document Item
Sales and Distribution under Master Data Business Partners Customers Sales
Logistics – Execution under Shipping Deliveries
Master Data
Materials Management
FSH_API_PURCHASINGORDER_CREATE
FSH_API_PURCHASINGORDER_CHANGE
FSH_API_PURCHASINGORDER_GET_DETAIL
FSH_API_GOODSMVT_CREATE
Sales and Distribution

FSH_API_SALESDOCUMENT_CREATE
FSH_API_SALESDOCUMENT_CHANGE
FSH_API_SALESORDER_GETLIST

Article master
ARTMAS07

FSHORD01
FSHDLV01
FSHINV01
FSHPORDCR101
FSHPORDCH01
FSHPORDGD101
FSHGMCR01
The following Business Add-Ins (BAdIs) are created:

BADI_FSH_SEASONS
BADI_FSH_SEA_DET
See also
Season
1.1.3.3.1.1.2.2 Value Added Services (New)
You can request for special labels, packing according to certain criteria, or other special services for their goods. Depending on the service requested,
additional articles, labor, or special skills are required. These services increase the value of the finished goods, which are being delivered. You can handle
these services through value added services in the fashion industry. You can assign the information related to different services using conditions. Later, the
system determines the services in the application documents (sales order, stock transport order, purchase order). During the special business processes in
sales, such as Third Party Order (TPO) and Purchase-to-Order (PTO), the system copies the VAS information to the purchasing documents from the sales
documents and you cannot change the values in the purchasing documents.
You can maintain VAS long text for a condition record in different logon languages. When you determine VAS conditions in the purchasing documents or sales
documents according to the condition types, you can view the VAS long text maintained for the logon language along with the other details.
Define Values for User-Defined Fields for VAS Determination

You can add new user-defined fields in the VAS condition tables relevant for purchasing documents or sales documents. If you add a new user-defined header
field in the table, you need to update the structure FSH_HCOM with the new field. If you add a new user-defined item field in the table, you need to update the
structure FSH_ICOM with the new field. You can map the fields of the tables and fields of the structures (FSH_HCOM and FSH_ICOM) in Customizing for
Maintain Mapping Table for Field Catalog under Logistics - General SAP Fashion Management Cross-Applications Value-Added Services (VAS)
Controls for VAS Determination .
When you create an outbound delivery, purchasing document, or sales document, the system uses the fields and their values in the structures FSH_HCOM and
FSH_ICOM for VAS determination.
You can use the following BAdIs to enter or change the field values for the newly added user-define fields in the structure:
BADI_VAS_FIELD_MAP_DELV for outbound delivery
BADI_VAS_FIELD_MAP_SD for sales documents
BADI_VAS_FIELD_MAP_MM for purchasing documents
The system then uses the new values of the fields available in the BAdI for VAS determination in the outbound delivery, purchasing document and sales
document.
VAS Redetermination
You can use the VAS re-determination report to re-determine the VAS details (items and data) for multiple sales document items or purchase document items.
The report retrieves the VAS details for the documents selected based on VAS Service Types and VAS Sub Services and redetermines VAS details for the
selected documents.
VAS Pricing Using Charge Codes

You can define a charge code to the VAS details in the sales or purchasing document. If you have defined this in your VAS conditions per value-added
service, the system determines the charge code along with the other value-added service details in the document.
VAS Customer Group

You can define VAS customer groups and assign customers to a VAS customer group by entering a unique ID in the customer master. Depending on the
values defined here, you can control the requested value-added services in the sales documents by maintaining different VAS conditions for these VAS
customer groups.
VAS Correlation in Deliveries

VAS correlation enables you to define the delivery mode of VAS items along with the main item. VAS correlation ensures that the VAS items (relevant or not
relevant for ARun) are delivered only if the main item is delivered. VAS correlation is only applicable when you create the outbound delivery document.
Existing Data
FSH_VASA – VAS Condition Maintenance at article level
FSH_VAS_SD – VAS Condition Maintenance at SD level
FSH_VAS_MM – VAS Condition Maintenance at MM level
FSH_VPO – VAS Details in Purchasing Documents
FSH_VSO – VAS Details in Sales Documents
The VAS redetermination report (transactionFSH_VAS_RED) is available. You can use this report to redetermine VAS details (items and data) for multiple
sales document items or purchase document items. You can access this report in SAP Easy Access under SAP Easy Access Retailing SAP Fashion
Management Cross-Applications Value-Added Services (VAS) .
Customizing
You make Customizing settings for this function in Customizing for Logistics – General under SAP Fashion Management Cross-Applications Value
Added Services .
Master Data
Structures BAPI_FSH_VAS_MM_ITEM and BAPI_FSH_VAS_MM_ITEMX are extended with a new field CHARGE_CODE.
Structures BAPI_FSH_VAS_MM_ITEM and BAPI_FSH_VAS_MM_ITEMX are extended with a new field CHARGE_CODE.
FSH_API_PURCHASINGORDER_GET_DETAIL
Structure BAPI_FSH_VAS_MM_ITEM_LIST is extended with a new field CHARGE_CODE.

Structure BAPI_FSH_VAS_ITEM is extended with a new field CHARGE_CODE.
Structures BAPI_FSH_VAS_ITEM and BAPI_FSH_VAS_CHNG_ITEMX are extended with a new field CHARGE_CODE.
FSH_API_SALESORDER_GETLIST
Structure BAPI_FSH_VAS_ITEM_LIST is extended with a new field CHARGE_CODE.

Article master
ARTMAS07

FSHDLV02
FSHORD02
IDoc segment E1EDP23 is enhanced with the new parameter CHARGE_CODE.
FSHPORDCH02
IDoc segment E1BPFSHVASMEPOITEM is enhanced with the new parameter CHARGE_CODE.
FSHPORDCR102
FSHPORDGD102
See also
Value-Added Services
1.1.3.3.1.1.2.3 Business for High Fashion Brands (New)
You can enable the system to create a snapshot for the pre-defined fields of the sales or purchasing documents. You can define snapshot statuses and
assign them to the sales or purchasing documents. The system creates a snapshot of the document based on the status you assigned for the document. You
can enable the system to create a snapshot of the header, item, or the schedule line of the documents based on the settings you defined.
You have to activate the business function HI_FASHION_01.

The user interface for the following transactions have been reworked to include the new parameter Snapshot Status (FSH_SNST_STATUS). You can use this
parameter to indicate a unique snapshot status assigned to a sales or purchasing document.
You can assign the snapshot status for a sales document using this parameter in the Order Data tab of Header Data screen while creating or changing the
sales order.
You can assign the snapshot status for a purchasing document using this parameter in the Additional Data tab of Header section while creating or changing
the purchase order or stock transport order.
You make the following Customizing settings for this function in the Customizing for:
Maintain Snapshot Status under Logistics - General SAP Fashion Management Snapshot
Maintain Sales Document Types per Sales Area for Fashion Management under Sales and Distribution Sales Sales Documents Sales
Document Header
Maintain Purchase Order Types per Purchasing Area for Fashion Management under Materials Management Purchasing Purchase Order
Maintain Stock Transport Order Types per Sales Area for Fashion Mgmt under Materials Management Purchasing Purchase Order
New importing parameter FSH_HEADER of BAPI structure type BAPI_FSH_PURCHORDER_HEADER
New importing parameter FSH_HEADERX of BAPI structure type BAPI_FSH_PURCHORDER_HEADERX
MASS_CHANGE_PURCHASE_ORD_BAPI
New table parameter SMASSEKKO of BAPI structure type SMASSEKKO is enhanced with the new parameter FSH_SNST_STATUS

New parameter FSH_ORDER_HEADER_IN of BAPI structure type BAPI_FSH_ORDER_HEADER_IN is enhanced with the new parameter
FSH_SNST_STATUS
New parameter FSH_ORDER_HEADER_INX of BAPI structure type BAPI_FSH_ORDER_HEADER_INX is enhanced with the new parameter
FSH_SNST_STATUS
New parameter FSH_ORDER_HEADER_IN of BAPI structure type BAPI_FSH_ORDER_HEADER_IN is enhanced with the new parameter
FSH_SNST_STATUS
New parameter FSH_ORDER_HEADER_INX of BAPI structure type BAPI_FSH_ORDER_HEADER_INX is enhanced with the new parameter
FSH_SNST_STATUS
MASS_SALESORDER_CHANGE
New table parameter SMASSSDHEAD_S of BAPI structure type FSH_MASSHEAD_S is enhanced with the new parameter FSH_SNST_STATUS
The following Intermediate Documents (IDocs) are enhanced:

FSHORD02
IDoc segment E1EDK37 is enhanced with the new parameter FSH_SNST_STATUS
FSHPORDCR102: New IDoc segments E1BPFSHMEPOHEADER and E1BPFSHMEPOHEADERX
FSHPORDCH02: New IDoc segments E1BPFSHMEPOHEADER and E1BPFSHMEPOHEADERX
The following Business add-Ins (BAdIs) are created:

BADI_FSH_SNAPSHOT
You can use this BAdI to include additional fields of a sales document.
BADI_FSH_ME_SNAPSHOT
You can use this BAdI to include additional fields of a purchasing document.
See also
Snapshot
1.1.3.3.1.1.2.4 Protected Species and Preference Management

(New)
Protected Species Management is a functionality that allows you to enhance the textile composition data of fashion articles with details of endangered species
identity. The identity can include any empowered protection agencies restriction data such as Convention on International Trade in Endangered Species
(CITES) of Wild Fauna and Flora . When you trade these products, they must be accompanied by a CITES license, and undergo specific customs control.
Therefore Protected Species Management Rules PSM Rules can be setup to group/split these articles in the outbound delivery documents or the billing
documents.
Preference Management (Preferential Origin) indicates the origin of goods in relation to specific trade agreements stipulated by economic communities like
EEC with certain countries or other economic communities which grants goods of this type an exemption or reduction of duty when imported. The preferential
origin of goods can have enormous benefits for customers since they can enjoy an exemption or considerable reduction of customs duty when importing such
goods, thus increasing their advantage in the market. Therefore Preference Management Rules PFM Rules can be setup to group articles in outbound
delivery or billing documents by preference status to be able to leverage profitable import conditions.
You have to activate the following business functions:
FASHION_03
ISR_RETAIL_PSM

FSH_PFM: You can maintain the PFM grouping rules for a specific application type for a specific company code.
FSH_PSM: You can maintain the PSM grouping rules for a specific application type for a specific company code.
You make Customizing settings for this function in Customizing for Logistics – General SAP Fashion Management Cross-Applications Protected
Species and Preference Management . The following Business Add-In is created:
BADI_FSH_PFM_PSM: You can use this BAdI to define user-specific logic when determining the group ID to split the delivery documents and billing
documents. The system then uses these group IDs to group the order items in the delivery documents and the billing documents.
See also
Protected Species Management and Preference Management
1.1.3.3.1.1.2.5 Application Variants (New)
You can co-ordinate and plan the sale and purchase of different variants of the generic article. This is relevant in sales orders, purchase orders, stock transfer
orders, and fashion-relevant sales contracts. You can only define application variants for the generic article. The system determines the application variants
according to the determination procedure defined in the order type.
You can only enter the relevant application variants through variant matrix or enter them as a stand-alone variant in the documents. After application variants
are determined, system does not allow the invalid variants to be entered in the document.
Additional Details
You can mark few variants of a generic article activated for sales application variants as core variants. For example, you sell sizes Medium (M) and Large (L)
most for an article T-shirt. You can flag these as core variants in the application variant in control data for the sales application variants. During Order
Allocation Run (ARun) release check, you can specify a different fulfillment % for core variants.
You can assign a leading dimension for a generic article. This leading dimension is a characteristic of an article that is used frequently (color and size). You
can maintain a separate ARun release check for an article at the leading dimension level.

FSH_VAR_SD: You can maintain sales application variants using condition record.
FSH_VAR_MM: You can maintain purchasing application variants using condition record.
You make Customizing settings for this function in Customizing for the following:
Logistics – General SAP Fashion Management Cross-Applications Application Variants .
Materials Management Purchasing Purchase Order Maintain Purchasing Document Types for Fashion Management .
Sales and Distribution Sales Sales Documents Sales Document Header Maintain Sales Document Types for Fashion Management .
The following Business Add-Ins are created:
BADI_VAR_FIELD_MAP_SD: You can use this BAdI to enter values for the user-defined fields (relevant for sales application variants) in the structure
and change the field values for the user-defined fields in the structure.
BADI_VAR_FIELD_MAP_MM: You can use this BAdI to enter values for the user-defined fields (relevant for purchasing application variants) in the
structure and change the field values for the user-defined fields in the structure.
See also
Application Variants
1.1.3.3.1.1.2.6 Split or Change Purchase Orders (New)
You can split purchase order items among vendors, plants, purchasing organizations, or company codes to optimize your goods receipts. You need to be able
to change purchase orders quickly and efficiently based on changing circumstances. For example, you may want to re-evaluate a purchase order in the
following situations:
The purchase order quantity is so large that no single vendor can fulfill the order
The existing vendor cannot deliver the goods on time, but another vendor can
You can obtain one of the purchase order items from a different vendor at a better price

The following new transaction is available:
FSH_SPLITPO: You can use this report to split purchase order items among vendors, plants, purchasing organizations, or company codes to optimize
your goods receipts. By changing the receiving plant or splitting schedule lines by plant, you can optimize distribution of the goods to your various
locations.
See also
Split or Change Purchase Orders
1.1.3.3.1.1.2.7 ATP Confirmations in Fashion Management (New)
You can enable the system to allow rescheduling for the existing order quantities that are fixed for the confirmed delivery dates proposed by availability check
(ATP). When the ATP Confirmations is enabled for the order document type, the system automatically fixes the delivery dates for the document item proposed
by ATP. MRP only considers the confirmed quantities proposed by ATP check during the planning process. In addition, the system allows the rescheduling
process to process these confirmed documents to improve the ATP results when needed according to the changes in the stock.
Additional Details
When the confirmed quantity is not equal to the order quantity for the ATP confirmation enabled document item, the system performs the following:
Generates the VAS items only for the confirmed quantities
Determines the pricing for the confirmed quantity using the new condition type to enable the end-user to know the loss of sales due to non-confirmation
of quantities by ATP which cannot be delivered
You can enable ATP confirmations for both stock transport order documents and sales documents.
You make customizing settings for this function in Customizing for the following:
Sales and Distribution Sales Sales Document Sales Document Header Maintain Sales Document Types per Sales Area for Fashion
Management .
Materials Management Purchasing Purchase Order Set up Stock Transport Order Assign Delivery Type and Checking Rule .
See also
ATP Confirmations in Sales Orders
ATP Confirmations in Stock Transport Orders (STO)
1.1.3.3.1.1.2.8 Order Scheduling (New)
During the processing of sales documents and purchasing documents you can optimize the delivery dates for every item. You can define the strategies to
consider the special customer requests or the general business requirements before influencing the delivery date for the items. This is applicable only in sales
orders and stock transport orders.
If you have enabled order scheduling, after ATP proposes the delivery dates for the items, the system can group the different schedule lines in the sales order
or stock transport order that can be delivered together according to the selected business rules.
Additional Details
Order scheduling is an optimization process based on rules - Field-based grouping rule and Date-based grouping rule. You can apply the rules on the document
items. You can define field-based grouping rules using the list of fields from specific tables. The system uses the values of these fields and maps them to the
values entered in the document item during the order scheduling run, to group the schedule lines. You can select one of the pre-defined date-based grouping
rules. The system uses the selected rule to perform one of the following and then groups the schedule lines accordingly:
To compare the confirmed delivery dates between the schedule lines
To fix the number of schedule lines in a shipment, or
To decide the number of shipments needed for a document
You can add your own fields for field-based grouping rule and define your own logic for date-based grouping rule to apply across the different document items
in optimizing the delivery dates.
You make Customizing settings for this function in Customizing for Logistics – General SAP Fashion Management Cross-Applications Order
Scheduling .
BADI_FSH_ORDER_SCHEDULING: You can use the standard implementations of this BAdI to define user-specific date-based grouping rules according
to your requirements and group the different schedule lines during order scheduling process.
BADI_FSH_ORDER_SCHEDULING_GB: You can use this BAdI to define user-specific field-based grouping rules to group the different schedule lines
during order scheduling process.
You can specify the scheduling strategy in the customer master or centrally in the settings for the sales or purchasing document type.
Fashion Specific Data tab in customer master
Sales document type: Maintain Sales Document Types per Sales Area for Fashion Management under Sales and Distribution Sales Sales
Documents Sales Document Header .
Purchasing document type: Maintain Stock Transport Order Types per Sales Area for Fashion Mgmt under Materials Management Purchasing
Purchase Order .
See also
Order Scheduling
1.1.3.3.1.1.2.9 Availability Overview in Sales Documents (New)
You can view the availability overview for generic articles in the sales documents. The availability overview displays the ATP situation for all the variants of a
generic article in the defined plant. You cannot change the ATP overview data in the document.
The ATP Overview tab contains the following information for the individual variants of the generic article:
Different characteristic values
Requirement segment (for articles relevant for segmentation)
ATP stock quantity at different availability dates
You make the following Customizing settings for this function in the Customizing for:
Maintain Sales Document Types per Sales Area for Fashion Management under Sales and Distribution Sales Sales Documents Sales
Document Header .
See also
Availability Overview in Sales Documents
1.1.3.3.1.1.2.10 Mass Data Change in Sales Documents (New)
You can use the Mass Data Change (transaction FSH_MASS_SD) report to perform a mass price change or mass ATP change for the selected sales
documents. The report performs the mass price change using the pricing type you choose for the selected sales documents. The report performs the mass
ATP change for the selected sales documents including contracts which are requirement relevant (Fashion Contracts). At a given point in time, you can use
the report to perform a mass price change or mass ATP change for the selected documents.
In addition to performing the mass ATP for the selected sales documents, you can use the report to perform the mass ATP only for the documents containing
the materials for which any of the properties related to stock (for example, stock segment, storage location, batch number) is created or changed after the
previous run or a pre-defined date. For more information, refer to the report documentation (transaction FSH_MASS_SD) in the system.

You can use the report Mass Data Change for Sales Documents (transaction FSH_MASS_SD) to perform the re-pricing and to re-run available-to-promise
(ATP) in the sales documents that you have already created.
The following new entry has been added to the area menu under SAP Easy Access Retailing SAP Fashion Management Sales and Distribution .
Mass Data Change for Sales Documents
The following Business Add-In (BAdI) is created:
BADI_FSH_MASSATP_SORTING
You can use this BAdI to maintain different sorting rules for the sales documents. The system uses the rules to sort the sales documents during mass
ATP in SAP Fashion Management .
See also
Mass Data Change
1.1.3.3.1.1.2.11 Characteristic Value Conversion (New)
You can represent the value of few characteristics of a generic article on different scales for different countries or region. Apart from defining base
characteristic values, the feature allows you to define characteristic values in different country scales. You can maintain characteristic conversion type
controls which can be country or region-specific identifiers. You can define the characteristic conversion IDs for an article, customer or vendor, and a user
parameter.
You have to activate the following business functions:
Other Enhancements for SAP Retail (ISR_RETAILSYSTEM)
Retail (EA-RET)
Material Segmentation Across Logistics (LOG_SEGMENTATION)
Customizing
You make Customizing settings for this function in Customizing for Logistics – General under SAP Fashion Management Cross-Applications
Characteristic Value Conversion .
Master Data

Article master
ARTMAS07

BADI_FSH_SIZE_CONV
See also
Characteristic Value Conversion
1.1.3.3.1.1.2.12 Batch Determination in Deliveries (New)
Segmentation is integrated in the batch determination process. If you use articles that are not relevant for segmentation, batch is determined similar to the
batch determination process in standard SAP ERP.
Outbound Delivery
You 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 an article that is relevant for segmentation, batch numbers are filtered according to the
segmentation value and appropriate batch number(s) is proposed with batch split.
If you have not activated automatic batch determination for an article that is relevant for segmentation, you can manually provide the batch number in
the delivery documents. You can only enter the batches that belong to the valid stock segment value maintained in the mapping rule in the
Requirement/Stock Allocation table in the Customizing activity Define Segmentation Strategy .
If the article is relevant for seasons (you have selected the Season Active in Inventory Management checkbox in the article master), the season is also
copied from the batch you have provided.
If you have configured to execute order allocation run for an article that is relevant for segmentation and season, the allocation run proposes the
allocated batch with batch split entries in the document, irrespective of the batch determination process being configured or not.
For more information, see Batch Determination for Outbound Deliveries
Inbound Delivery
You can enable the system to check if the batch entered in the inbound delivery document already exists in the system. To do this, you can use the No
Batch Check checkbox in the Customizing activity Define Item Categories for Deliveries under Logistics Shipping Deliveries .
If you select this checkbox, the system does not update the new batch number in the document and does not perform a batch split, although the batch
is relevant for segmentation. However, if the system determines an existing batch number, the system updates the batch number in the document and
performs a batch split.
If you do not select this checkbox, the system determines a new batch number or an existing batch number and updates the determined batch number
in the document and performs a batch split.
If the article is relevant for seasons (you have selected the Season Active in Inventory Management checkbox in the article master), the season is also
copied from the batch you have provided.
1.1.3.3.1.1.3 Enhancements in Production Planning and Control

for Fashion
With this feature, you can use the following enhancements for articles with fashion attributes in Material Requirements Planning , Demand Management , and
Available-to-Promise process:
Material Requirements Planning
Grouping of Stock Proposals During MRP Run
Stock/Requirements List for Fashion
Stock Sort Method
Source of Supply Determination
Variant Group
MRP Area
Segment Level MRP Data
Segmentation: Availability Check (ATP)
Planned Independent Requirements for Generic Article
Technical Details
Technical Name of Product Feature FASHION_20_PP_ENHANCEMENTS
Application Component LO-FSH

1.1.3.3.1.1.3.1 Enhancements to Material Requirements Planning
You can enable the following features during the planning process:
Grouping of Stock Proposals During MRP Run

You can enable the system to group the individual purchase requisitions or group multiple planned orders into single master planned order during Material
Requirements Planning (MRP) using Customizing activity Activate Grouping of Stock Proposals during MRP under Production Material Requirements
Planning Planning Procurement Proposals . Grouping of purchase requisitions or planned orders is applicable only for variants of the generic article.
Planned orders are grouped into master planned orders during MRP, as per the grouping criteria. The system groups the stock proposals of variants of a
generic article only if the following attributes have the same value across variants of the generic article:
Plant
Release date
Delivery date
Supplying plant (in stock transport requisition)
Supplier or vendor (in external procurement)
Account assignment category
Purchasing organization
Purchasing group
Requirement segments
Stock segments
Document type
Document category (item category)
Storage location
For more information about implementing this feature, see SAP note 1971859 .
Stock/Requirements List for Fashion

You can view the stock and requirements situation for individual segments of an article using transaction FSH_MD04. Each time you access the
stock/requirements list, the system selects the various MRP elements and displays the most up-to-date situation. The list maps the appropriate stock
elements to the requirement elements for the individual stock segments and displays them in separate tabs according to MRP Statuses. The system
considers the segmentation strategy in the mappings.
Additionally you can filter the list based on MRP area. In case of a master planned order or master production order, you can double-click the ID and navigate
to Production Control Workbench .
Stock Sort Method

You can define whether the system should assign the available or incoming stock (future receipts) to the requirement based on segmentation or customer's
requested delivery date during material requirements planning. You can use this sorting method if you use articles with segmentation strategies (scope =
Requirements and Stock Segments Maintained ) in which it is permitted that more than one stock segment can be used to cover a specific requirement
segment.
Source of Supply Determination

You can define the sources of supply for a generic article in the system in the documents such as source list, outline agreement, and purchasing info record.
You can maintain the outline agreement or purchasing info record for an article of a particular site in the source list. The system considers the outline
agreement or purchasing info record maintained in the source list to determine the source of supply during the MRP run.
Variant Group
You can maintain the variants of a generic article in different groups at the client level for a reference DC in article master. The grouping of variants helps in
optimizing the production or the procurement process. During MRP run, the system combines all variants that belong to the same generic article and the
variant group in a single master planned order or purchase requisition. For achieving variant grouping, you must activate the grouping of stock proposals using
Customizing activity Activate Grouping of Stock Proposals during MRP under Production Material Requirements Planning Planning Procurement
Proposals .
MRP Area
You can assign the various MRP areas to the articles that are relevant for segmentation using the report RMMDDIBE. To do this, you have to create an MRP
area segment for an article for every MRP area, in which it is used. In this MRP area segment, you can define MRP parameters such as the lot size or MRP
type. This allows you to plan the articles with segmentation differently in the MRP area from how you plan it in the plant MRP area. The system supports MRP
area for articles relevant for segmentation in MRP Live (MD01N). You can view the stock/requirements situation for articles that relevant for segmentation in
transaction FSH_MD04 for the selected MRP area.

You can maintain the following MRP relevant parameters for the individual segments of the article in article master ( Logistics:DC Fashion Segment Level
MRP Data ).
Minimum Lot Sizes
Safety Stock
Safety Time Indicator
Valid From (applicable for ATP/MRP Status)
Rounding Value
Purchasing Group
Safety Time
Planned Delivery Time
In-house Production Time
ATP/MRP Status for Article and Segment
For a generic article, the system considers the minimum lot-size MRP relevant parameters maintained in article master in the following order of priority
sequence in the lot-sizing procedures during material requirements planning run:
Variant +non-reference distribution center + segment
Variant + reference distribution center + segment
Generic article + reference distribution center + segment
Variant + non-reference distribution center
Variant + reference distribution center
Generic article + reference distribution center
For a single article, the system considers the minimum lot size MRP relevant parameters maintained in article master in the following order of priority
sequence during material requirements planning run in the lot-sizing procedures:
Article + non-reference distribution center + segment
Article +reference distribution center + segment
Article + non-reference distribution center
Article + reference distribution center

FSH_MD04
You can use Stock/Requirements List for Fashion (FSH_MD04) to view the stock/requirements situation for the individual segments of an article.
The following Business Application Programming Interface (BAPI) is enhanced:

Structures SEGMRPGENERALDATA and SEGMRPQUANTITYDATA created.
The following Intermediate Document (IDoc) is created:

ARTMAS09
IDoc segments E1BPSGTMRPGN and E1BPSGTMRP are created.
You make Customizing settings for grouping of stock proposals in Customizing for Production Material Requirements Planning Planning
Procurement Proposals Grouping of Stock Proposals during MRP for Fashion Mgmt .
The following Business Application Programming Interface (BAPI) is created:
FSH_API_GET_STOCK_REQ_LIST
Structures SEGMRPGENERALDATA and SEGMRPQUANTITYDATA created for segment level MRP data.

BADI_FSH_STOCK_REQ_LIST_UI
You can use this BAdI to change the standard layout of the stock/requirements display for Fashion Management.
BADI_FSH_STOCK_REQ_LIST_APPL
You can use this BAdI to add or change the values of an MRP element for the display of the stock/requirements list for Fashion.
The following Intermediate Document (IDoc) is created for segment level MRP data enhancements:
ARTMAS09
IDoc segments E1BPSGTMRPGN and E1BPSGTMRP are created.
See also
Materials Requirement Planning
Variant Group
1.1.3.3.1.1.3.2 Segmentation: Availability Check (ATP)
An availability check is carried out at order entry to check whether the required article (for example, the selected color or size) is available for the requested
delivery date. If you are using articles that are relevant for segmentation, you can use the segmentation values to assign the stock to the requirements. The
assignment of the requirements to the stock or the stock to the requirement is determined according to the mappings defined in the ARun/MRP/ATP:
Requirement/Stock Allocation table in the Customizing activity Define Segmentation Strategies under Logistics - General Segmentation . You can
map a requirement segment to multiple stock segments (m:n) in the segmentation strategy so that the article in specific requirement segment can be fulfilled
by more than one stock segment.
More Information
Segmentation: Availability Check (ATP)
1.1.3.3.1.1.3.3 Enhancements in Demand Management (New)
You can plan requirement (forecast) quantities for generic articles using transaction FSH_PIR and distribute the requirements across the variants and
segments of the generic article.
You can enter a range of articles and plants, the version, and the planning horizon to create the planned independent requirements. You can change or delete
the existing requirements based on generic article.

FSH_PIR: You can use transaction FSH_PIR to plan requirement (forecast) quantities for the generic article and distribute across the variants and
segments of the generic article.
See also
Planned Independent Requirements (PIRs) with Segmentation
1.1.3.3.1.1.3.4 Enhancements in Production (New)
Production Relevant Master Data in Fashion

Segmentation in Bill of Material and Routing
Bill of Material Explosion
Bill of Material for Generic Article and its Variants
Routing for Generic Article and its Variants
Production Version for Generic article and its variants
Planned Orders and Production orders
Master Orders
Additional Details
Production in Fashion Management relies on SAP ERP standard production scenario and production related master data and documents.
Production Relevant Master Data in Fashion
Production Master Data in Fashion Management involves in creating the definition of a fashion product. Customers often use non SAP software to design and
develop a fashion product definition. Once a final design of the fashion product is developed, the components required and the operations to be performed to
produce the fashion product is defined and would be maintained in Fashion Management as Bill of Material (BOM) and Task list or Routing.
Fashion Management is architecturally relying on the IS-Retail platform and a typical fashion product is modeled in Fashion Management as a single article or
a generic article when the product would have different dimensions, such as sizes and colors, or a structured article.
Production Relevant Master Data
Fashion Management provides enhancements to BOM maintenance user interfaces and program interfaces and supports segmentation in such a way that you
can assign which component would be applicable in a production BOM with a particular segmentation value combination. Likewise, with Task list or Routing
object, you can also assign which operation in a task list for fashion article, is applicable and which not, for every segmentation value combination.
Bill of Material Explosion
Also the Bill of Material explosion used in order documents and MRP run and various other situation, is enhanced such that
based on the stock segment of the fashion product being produced, and the segmentation strategy rules associated with the fashion product, the
component requirement segment is determined.
segmentation would influence which component would be applicable and which not.
BOM Explosion
Bill of Material for Generic Article and its Variants
Fashion Management provides enhancements to BOM maintenance user interfaces and program interfaces. Fashion Management allows you to create bill of
material for a generic article and assign components and quantities. Also when the header article is a generic article with the fact that the generic article
comprises of variant group or variants, it is imperative that for every variant of the header generic article, BOM with its components and quantities. Fashion
Management provides enhancement to maintain every variant group or variant's BOM and to this purpose, you need to maintain the quantity of component for
every variant group or variant as deviation quantity that is deviating from the quantity for the same component on generic article. Once for every component,
for all the variant group or variants, the deviation quantities are maintained, then the system will generate the BOM for different variant groups or variants in the
background.
Bill of Material for Generic Articles
Routing for Generic Article and its Variants
Fashion Management also provides means to create Tasklists or Routing for the generic article and this Routing can be applied to all variants or variant group
of a generic article with ease.
Routing for Generic Articles
Likewise maintaining production version for variants of a generic article can also be done with minimum effort.
Planned Orders and Production orders
The planned orders and production orders maintenance user interfaces and program interfaces have been enhanced to bring segmentation. While manually
creating a planned order or production order through the user interfaces or program interfaces for a single article or variant of a generic article, if the article is
segmentation relevant then, the stock segmentation should be provided.
When the planned order is generated by MRP run, the stock segment of the header article is determined based on the following:
requirement segment coming from the demand document, that is if make-to-order scenario, then it is sales order document; if make-to-stock scenario,
then it is planned independent requirement document.
segmentation strategy (assigned to header article) and its condition or rules of converting requirement segment to Stock segment for MRP run.
During the MD read and BOM explosion in planned order and production order, the components and their requirement segment are to be determined. Once the
stock segment of header article is known or identified, the following are determined:
the components that are applicable to the header when the specific stock segment is applied.
the requirement segment of each component is determined by the use of segmentation strategy (assigned to header article) and its Dependent
Requirement condition or rules of converting stock segment of header to requirement segment (values from segment strategy ) of the component.
Planned Orders and Production Orders
Master Orders
Fashion Management is built over the SAP Retail software and articles with fashion attributes, size and color dimensions, would be typically modelled as
Retail generic articles. Generic articles produce variants for every size and color dimension combination and that leads to unique material code for every
variant. Planned orders and production orders by nature can be created for an article and therefore for order per variant.
But production is usually performed for multiple size and color dimension combinations for the obvious reasons of optimizing the overall production process.
To accommodate the former, the solution provides grouping of variant planned orders into master planned orders and variant production orders into master
production orders and support execution of production of variant groups or variants together. Master planned orders and master production orders can be
managed and controlled by Production Control Workbench , a new comprehensive planned and production order management tool.
Master Orders

The following new transaction is created:
FSH_PCW
You make customizing settings for this function in Customizing for the following:
Logistics - General SAP Fashion Management Production Planning and Control
PCW_CHECK_MASTER_ORDER: You can use this BAdI to validate assignment or unassignment of planned and production orders from the master order.
BADI_FSH_PP_SEASON: You can use this BAdI to prioritize the order of the seasons that are determined in a production order using by the season
determination process in a production order.
More Information
Basic Data
1.1.3.3.1.1.4 Order Allocation Run (New)
Order Allocation Run (ARun) helps to improve and optimize stock usage. It helps to improve customer service supporting, for example, preference for
important customers. This feature enables you to assign stock to the orders depending on the changing fashion requirements.
For example, the allocation run ensures an assignment of the available stock to the open requirements according to your business requirements when there is
a shortage of stock. The allocation run creates a fixed assignment between the requirement records, physical stock (batch managed or non-batch managed),
and future receipts. You can only manually undo this assignment. The allocation run is a process based on rules.
You can activate Order Allocation feature per plant/material combination.
Technical Details
Technical Name of Product Feature FASHION_20_ARUN
Required Business Function(s) Other Enhancements for SAP Retail (ISR_RETAILSYSTEM)

Retail (EA-RET)
Material Segmentation Across Logistics (LOG_SEGMENTATION_03)
Features
The following are the main features of Order Allocation Run (ARun):
Order Allocation execution in dialog, parallel, or batch processes
Order Allocation in normal mode, preview mode, simulation mode
The following are the main steps and rules of order allocation:
Requirements selection
Physical stock selection
Future stock selection
Grouping rule to create temporary groups of requirements
Requirement sorting rules
Stock sorting rules
Allocation rules: FIFO logic or Spread logic
Release rules with checks at many levels
Immediate allocation of rush orders and stock transfer orders
Stock protection: You can use this feature to protect stock across many sales channels
The order allocation run results in assignments which have the following statuses depending on the result of the release check:
Fix (F): The stock is fixed and the outbound delivery is possible
Fix and Hold (H): The stock is on hold and the outbound delivery cannot be created
Reserve (R): The stock is reserved but outbound delivery is not possible
On Delivery (D): The order is on track for delivery (outbound delivery is created)
Order Allocation Consistency Check report: You can use this report to identify and resolve inconsistencies in the database tables
Order Allocation Insight to Action report: You can use this report to analyze the exceptions and perform the necessary corrective or follow up actions
ARun Workbench report: This report allows you to manually change existing allocations. You can execute the report in normal or background mode. For
example, you can perform actions such as allocation, de-allocation, adjust, and release check.
Existing Data
ARUN – Order Allocation Run (online mode)
ARUN_PROI – Display Exceptions
ARUNWB – ARun Workbench
ARUN_BATCH – Batch Allocation Run (background processing)
ARUNP
You can start multiple processes in parallel across several servers to shorten the run time and effectively use the system resources. This report is used
when a large number of sales orders and stock transport orders are processed in ARun.
ARUNWB_BATCH
Background processing for ARun Workbench
The following function/programs is available:
FSH_ARUN_SDRQ: Order Allocation Run - Consistency Check Report
FSH_ARUNITA: Order Allocation Run - Insight to Action
Customizing
You make Customizing settings for this function in Customizing for Logistics – General under SAP Fashion Management Order Allocation Run .
BADI_MD_ARUN_HANDLE
You use this BAdI to overwrite the order allocation run (ARun) relevancy settings that comes from the plant master during listing in article master.
FSH_BADI_ARUN
You can use this BAdI to create your own implementations and customize certain steps when you execute an order allocation run.
FSH_BADI_ARUN_STOCK_PROTECTION
You can use this BAdI to set aside stock for certain segments that should be given the highest priority for their orders or planned independent
requirements (PIRs). When you execute the order allocation run, the existing stock is set aside based on the priority of these segments. Stock is
allocated to lower priority segments only if sufficient stock remains.
FSH_BADI_ARUN_WORKBENCH
You can use this BAdI to create your own implementations and customize certain steps when you execute Order Allocation Run Workbench .
FSH_BADI_ARUN_ITA
You can use this BAdI to create your own implementations and customize certain operations when you execute Insight to Action .
See also
Order Allocation Run
1.1.3.3.1.1.5 Integration with Other Components
Integration of Fashion Management and Extended Warehouse Management (EWM)

You use this component to replicate the fashion attributes (stock segment, season year, season, collection, and theme) of the batches as characteristic
values of the batches in as Extended Warehouse Management (EWM).
Integration of Fashion Management and SAP Advanced Planning and Optimization (SAP APO)
You use this component to connect Fashion Management, which is based on the ERP system, with other components of the SAP Business Suite such as
SAP Advanced Planning and Optimization (SAP APO).
The integration includes the following:
Integration with Demand Planning (DP)
Integration with Supply Network Planning (SNP)
Integration of Master Data
Integration of Transaction Data
Integration of Fashion Management and SAP Global Trade Services (GTS)

SAP Global Trade Services (GTS) helps companies better manage global trade operations, ensure ongoing trade compliance, and optimize the cross-border
supply chain.
Technical Details
Technical Name of Product Feature FASHION_20_INTEGRATION
Application Component Multichannel Fashion (LO-FSH)

FSH_CFMH: You can use this report to transfer the product hierarchy and location product hierarchy.
FSH_PROD: You can use this report to create reference product numbers and save them to the fashion database.
You can define the default class for all the batch-managed articles that are relevant for segmentation and season using Customizing activity Define Default
Class for Batch Transfer to EWM under Integration with Other SAP Components Extended Warehouse Management .
You can define the table name and the corresponding field name that the system uses to transfer additional attributes of the batches (for example, stock
segment and season) to Extended Warehouse Management (EWM) using Customizing activity Define Table Name and Field Name for Batch Transfer to
EWM under Start of the navigation path Integration with Other SAP Components Extended Warehouse Management .
See also
Integration of Fashion Management and Extended Warehouse Managem
Integration of Fashion Management and SAP Advanced Planning and
Integration of Fashion Management and SAP Global Trade Services
1.1.4 Human Capital Management
In this section, you can find the release notes for SAP_HR 608 and EA-HR 608, Support Package 18. Use the navigation in the left frame to find a specific
release note.
HCM, Personnel & Organization 09
For more information about the features provided with this business function, please see the following release notes:
HR Professional: Generate Processes and Forms
HR Professional: Enhancements to the Roadmap Form
More Information
For more information about the technical prerequisites of the business function, please see HCM, Personnel & Organization 09.
Technical Details
Technical Name of Business Function HCM_PAO_CI_9
Available as of EA-HR 608 SP31
1.1.4.1.1.1 HR Professional: Generate Processes and Forms
This feature enables customers using HCM Processes & Forms (HCM P&F) for multi-infotype scenarios - such as hiring or internal transfers - to automate the
creation of HCM P&F scenarios for the type, Roadmap Form.
Technical Details
Software Component Version EA-HR 608

EA-HR 607
Application Component Personnel & Organization

PA-PAO
Required Business Functions HCM_PAO_CI_9 (HCM, Personnel & Organization)

To generate processes and forms based on Personnel Actions, please choose Personnel Management Personnel & Organization Processes
Generate Processes and Forms (Based on Personnel Actions) .
Additional Information
Generating HCM Processes & Forms
HR Professional: Enhancements to HCM P&F Roadmap Forms

Allow users to edit the initial step of the roadmap form even after subsequent infotype steps have been maintained
Users can now change key information, such as the personnel area in the first step General Process Data even after they have edited subsequent infotype
steps. After such a change, the system checks that data in the other steps is still correct and alerts the users to any data that might need to be adjusted as a
result of the change made in the first step.
Assign employee change processes to different processors who in turn can edit different content
Available in the HCM Processes & Forms framework for the Roadmap Form form type, you can now assign attributes such as read-only, edit, and so on, for
an infotype in a specific form scenario step. You can assign the scenario step to a specified user or role who gets the item for processing via the workflow.
Technical Details

EA-HR 607

PA-PAO

See also
Roadmap
1.1.4.1.2 HR Professional: Simplified Field Control
You can use this feature to set field properties, such as read-only or mandatory for IT ( infotype) fields.
With this feature you can also change field properties for one specified application context, such as the context for HR Professionals or ESS Personnel
Information (WDA) without affecting other applications running on the decoupled IT framework. You can also make settings for fields belonging to the UI-
structure only – for example derived or calculated fields.
We recommend you use this for field properties for IT screens in the WDA Master Data Application and the roadmap forms for HR Professionals.
Technical Details

EA-HR 607

PA-PAO

EA-HR 607 SP41
HCM, Personnel & Organization Countries FP5

With this feature, you can enhance the Personnel & Organization (PA-PAO) application component with management of employee master data for the
following country versions:
Croatia
France (Public Sector)
Indonesia
Oman
Technical Details
Business Function Is New
Country Dependency Croatia

France (Public Sector)
Indonesia
Oman
Application Component Personnel & Organization (PA-PAO)
Available as of EA-HRRXX 607 SP44

EA-HRRXX 608 SP21
Business Function that Needs to Be Activated HCM_LOC_CI_85

SAP Note Number Croatia: 2187852

France (Public Sector): 2121419
Indonesia: 2152258
Oman: 2185457
Additional Details
IMG Changes
New nodes for the relevant countries have been created in Customizing for Personnel & Organization under Infotypes Infotypes for Employees
Country-Specific Infotypes and Infotype Settings .
See Also
Personnel & Organization
release note.
1.1.4.2.1 PCC for the Payroll Administrator- New Payroll

Experience
As of EA-HRRXX 608 SP015, the payroll experience for the payroll process manager introduced in EA-HRRXX 608 SP012 is now enhanced with a payroll
experience for payroll administrators.
It is supported by a new SAP Fiori Design-based user interface. This application allows payroll administrators to perform, for example, the following tasks :
Employee and payroll error specific solution proposals,
Ability to navigate from a solution proposal to the maintenance screen for error correction,
Immediate validation of a payroll error after the solution has been applied,
Forwarding of payroll errors to other payroll administrators for processing,
Filtering and mass processing of the payroll errors,
Quick actions for multiple payroll errors on an overview screen,
Detailed information per payroll error to enable in depth root cause analysis,
Support for payroll administrator teams.
The new SAP Fiori Design-based user interface for payroll administrator offers a simple overview of payroll errors per process. As a payroll administrator you
can easily get all required information for the payroll errors you are responsible for to support an in depth root cause analysis and to choose and execute the
right solution proposal fast and efficiently.
As of EA-HRRXX 608 SP015, as payroll administrator, you have the following options:
Use the new payroll experience as described above,

OR
Use the classic solution provided in previous Support Packages.
Technical Details
Country Dependency All countries
Software Component Version EA-HRRXX_608
Application Component PY-XX-PYD

Payroll Process
Available as of EA-HRRXX 608 SP15
Required Business Functions Payroll Control Center 03

and
Payroll Control Center 04
See also
For more information about using this feature, please see the documentation in the Customizing activity Payroll International Payroll Control Center
Notes for Upgrading to HR Renewal 2.0, Feature Pack 4 .
For more information about the feature provided with this business function, please see the following release note:
HR Professional: Extended Search Help
More Information
For more information about the technical prerequisites of the business function, please see HCM, Personnel & Organization 08.
Technical Details
1.1.4.2.2.1 HR Professional: Extended Search Help
With this feature, you can choose between using a text-based search or a structure-based search to find positions or organizational units. The extended
search help is available in the following cases:
On the start screen of the roadmap form (for selecting a position)
On the individual infotype screens in the Master Data application
On the individual infotype screens that form part of a roadmap form
In FPM-based processes
If you tend to use certain organization structures frequently, you can define these organizational structures as favorites and use them as the starting point for
your search.
Technical Details
Required Business Functions HCM, Personnel & Organization 08
See also
For more information about using this feature, please see the documentation in the Customizing activity Personnel Management Personnel &
Organization Organizational Chart/Tree Configure Extended Search Help

The infotypes Main Personnel Assigment (IT0712), Notifications (IT0128), and Travel Privileges (IT0017) are now available for use in the Master Data
application and for HCM P&F processes.
Technical Details
Required Business Functions HCM, Personnel & Organization 08
See also
Main Personnel Assignment for Concurrent Employment (IT 0712)
Notifications (Infotype 0128)
Travel Privileges (Infotype 0017)
release note.
HR Professional: Conversion to Dynamic Processing Rules
HR Professional: Employee Recognition
HR Professional: Employee History in Master Data Application
HR Professional: External Personnel Number Assignment
HR Professional: Added Country Enablement
More Information
For more information about the business function, see HCM, Personnel & Organization 07.
Technical Details
1.1.4.3.1.1 HR Professional: Conversion to Dynamic Processing

Rules
With this feature you use the Launcher for Dynamic Action Conversion report (transaction HRPAO_DY_MIGRATION ) to convert dynamic actions into
dynamic processing rules (DPRs). This report supports the conversion of all configurable content. It displays the Customizing entries from the T588Z
( Dynamic Actions ) view that can be selected for conversion. When you select your dynamic actions and start the conversion process, the system performs a
consistency check and displays the results in Conversion Results: Preview . In the Conversion Results: Preview , you confirm the conversion. Once the
converted DPRs are available in the DPR framework, you can adjust them as required.
Technical Details

Own function calls and ABAP-based parts of dynamic actions must be converted manually by creating a matching class for the new framework.
See also
For more information, please see the documentation in the Customizing activity Personnel & Organization Master Data Application Dynamic
Processing Rules Convert Dynamic Actions
1.1.4.3.1.2 HR Professional: Employee Recognition
With this new feature, you can see if a new employee who you are adding to the organization:
Has to be assigned a new personnel number, that is the employee is a new hire
Already has a personnel number within your organization but does not currently have a contract (the employee is in an inactive employment relationship),
that is the employee is a rehire.
Already has a personnel number and requires an additional contract within the same legal entity as part of the concurrent employment concept
Already has a personnel number and requires an additional global assignment in another legal entity as part of the management of global employees
concept
This feature can be used with or without Concurrent Employment or the Management of Global Employees.
Technical Details

See also
Please see the Customizing documentation available for Personnel & Organization Basic Settings Employee Recognition
1.1.4.3.1.3 HR Professional: Employee History in Master Data

Application
You can use the Employee History tab in the Master Data Application to display what and when changes were made to employee data such as Change in
Pay , Organizational Reassignment, Hiring, and so on.
To be exact, the changes that Employee History displays are those changes that are made to IT0000 ( Actions ) and IT0302 (Additional Actions ). Since the
Master Data Application is automatically updated with changes to these infotypes, based on the configuration of your processes, Employee History is a
display only list.
Technical Details

1.1.4.3.1.4 HR Professional: External Personnel Number

1.1.4.3.1.4 HR Professional: External Personnel Number
Assignment
You can use this feature in any processes in which a personnel number is assigned from an external or internal number range in the Roadmap Form.
When external numbers are being used, you'll see an input field for Personnel Number where you can enter the number yourself. The system validates this
number against the range defined for the external number range in Customizing.
When internal numbers are being used, you'll see that the Personnel Number field contains the information that the system generates this number
automatically.
You'll not see this block when your system configuration uses only the internal numbers for generating personnel numbers. In this case, the system
automatically generates the personnel number.
Technical Details

You configure the number ranges in Customizing for Personnel Management Personnel Administration Basic Settings Maintain number range
intervals for personnel numbers
See also
Personnel Number Assignment
Employee
1.1.4.3.2 HR Professional: Read-Only Roadmap Form
With this enhancement, the HCM P&F form type Roadmap Form supports a read-only mode. You can now ensure that any HCM P&F-based processes that
require an approval or are subject to the four eyes principle are read-only before they can be released and stored on the database. For example when an
employee is hired, the HR Professional user maintains the data in the Roadmap Form and sends it on for approval. If corrections are needed, the approver can
reject the form and return it to the HR Professional user for correction.
Technical Details

See Also
Please see the Customizing documentation in Personnel & Organization Processes Design Time for Processes and Forms
1.1.4.3.3 HR Professional: Search Enhancements
With these enhancements you can benefit from the following:

Default Date Range for Search Dialogues
Available for HR Professionals in the Landing Page Search Lane and for the search in the Master Data Application, you can configure a default date
range such as Today plus 3 Months for search dialogues. This saves time, since users do not have to set the desired date range manually.
Enhanced Date Handling in the Search Lane Quickview
Details are now also shown for past and future objects, or for employees.
Easier Availability of the Search Lane Action Menu
Action menus are now also displayed in the search lane for those HR Professional users who do not have an active IT0105 communication subtype user
record.
Technical Details
Additional Details
Configurable Date Range for Search Dialogues
For users with the Employee Self-Services role (which uses the search feature to find contact details of fellow employees), you can leave the default search
date as Today .
Use the personalization object, HRPAO_SEARCH_DATE_RANGE to assign this default date range to the required roles. You can do this in the Customizing
activity Personnel & Organization Role Assign Role to Users
1.1.4.3.4 Payroll Control Center - New Payroll Experience
Starting with EA-HRRXX 608 SP012, the payroll control center introduces a new payroll experience for the payroll process manager.
This innovation consists of a new concept on how to run payroll which is complemented by a new SAP Fiori Design-based user interface.
One of the major concept enhancements in EA-HRRXX 608 SP012 is the introduction of the monitoring phase. During this phase and before the productive
payroll run begins, you as a payroll process manager can at any time validate data changes against policies ‑ including validations based on test payroll
results‑, identify possible errors, trigger the resolution of them and monitor this progress. As a result, you can identify and resolve most of the payroll issues,
which traditionally arise during the productive payroll run, long before the productive payroll run is started.
The new SAP Fiori Design-based user interface for payroll process managers offers a simple overview of current, upcoming and completed processes. As a
payroll process manager you can easily follow the processes you are responsible for and also monitor every single step.
As of EA-HRRXX 608 SP012, you can choose between two possibilities to work with the role of the payroll process manager within the payroll control center:
The new payroll experience as described above, or

The classic solution (as is being provided in previous support packages)
To enable this new payroll experience, two business functions must be activated:
Payroll Control Center: Payroll Log Storage (HCM_LOC_CI_79)
Payroll Control Center 03 (HCM_LOC_CI_76)
Technical Details
Technical Name of Product Feature PAOC_PAY_PYD_003
Country Dependencies Valid for all countries
Software Component Version EA-HRRXX_ 608
Application Component PY-XX-PYD
Available as of SAP Support Package 12 (SP12) for EA-HRRXX 608
Required Business Functions Payroll Control Center: Payroll Log Storage (HCM_LOC_CI_79)
Payroll Control Center 03 (HCM_LOC_CI_76)

Even if you have activated the above mentioned business functions, you have to complete all processes and their instances within the Payroll Control Center
“Classic”solution.
If you want to use the new payroll experience solution provided by EA-HRRXX 608 SP012, you have to create new payroll processes and their instances
using the corresponding new templates.

As of EA-HRRXX 608 SP012, the report Admin Transaction Report (PYC_ADMIN_TRANSACTION) is available. This report enables the system
administrator to do the following tasks:
Maintain user name for batch processing
Maintain recurrence for daemon job
Maintain recurrence for regular wrap up jobs
Maintain user list for master data
Generate general process ID for HR Process Workbench
For more information see the system documentation of the report.
You can access the Customizing activities under Payroll International Payroll Control Center .
See also
For more information, see the documentation of the above mentioned business functions.
release note.
1.1.4.4.1 Payroll Control Center (Feature Pack 2)
As of EA_HR 608 SP07, the business function HCM_LOC_CI_72is available.

You can use this business function to allow payroll process managers to:
Plan payroll processes and all involved process steps
Execute all needed process steps of a payroll process
Monitor the progress and status of all payroll processes
Execute validation rules and distribute the identified issues and compliance violations to the responsible payroll administrator for correction
Confirm successful execution of process steps, step groups, and processes
Enable audit processes based on a log file that is filled automatically by the system and can be enhanced by the user creating new log entries
In addition, the payroll administrators can interact between themselves and with the payroll process managers for processing the identified issues and
compliance violations by setting different error statuses for the issues or violations.

You can use the Text Configuration for Process Step Templates (PYC_TEXT_CONFIGURATION) report to customize the texts displayed on the front-end
user interface of each process step of the Payroll Control Center. And can you use the Action Log Viewer (PYC_ACTION_LOG_VIEWER) report to query the
payroll process action log and download the query result in an Excel file for further processing.
You can access the Customizing activities under Payroll Control Center in the Payroll International structure to do the following:
Configure the payroll process for payroll process managers to suit your requirements in Customizing. You can define process templates and categories,
process step templates and assign the process templates to processes.
Activate the text configuration for process step templates so as to overwrite the standard text delivered by SAP.
Use the Business Add-Ins (BAdIs) to define your own logic for the following:
Generating the start date and end date of step groups of each process instance
The step group periods are automatically filled in the Generate Process Instances (PYC_GENERATE_INSTANCE) report.
Generating the value for the time parameter Period for Third Party in US (CUS_PERIOD_3RD)
This parameter type is defined and included in the SAP standard delivery. For a payroll process that uses this parameter CUS_PERIOD_3RD, the
Generate Process Instances (PYC_GENERATE_INSTANCE) report reads the time parameter value to generate a process instance for each
period.
See Also
For more information see the business function description.
1.1.4.4.2 Declustering for Concurrent Employment Payroll Result
In Human Capital Management (HCM), the concurrent employee information is stored as a large object in a field within a database table. The database tables
are referred to as cluster tables. The results for Payroll are stored in cluster tables, that is, the transparent tables are compressed to form a binary string. The
cluster tables PCL1 and PCL2 store these binary strings (RAW format). This type of data storage does not allow the results of the payroll to be accessed
directly from the database layer.
This feature involves the creation of simple transparent database tables in addition to the standard non-transparent database tables and stores existing cluster
data as well as synchronously updating the transparent tables. This feature allows you to process or retrieve data using complex SQL queries and perform
aggregations on these concurrent employment payroll results right at the database layer.
Technical Details
Technical Name of Product Feature HCM_LOC_CI_75
Country Dependency Valid for the following countries:

International
Russia
United States
Software Component Version SAP_HRRXX 604 and above

EA_HRRXX 604 and above
Application Component Payroll Process (PY-XX-PYP)
Available as of SAP-HR 604 SP80

EA-HR 604 SP80
Required Business Functions HCM, Declustering for Concurrent Employment Payroll Result (HCM_LOC_CI_75)
HCM, Declustering for Concurrent Employment Payroll Result

When you activate the business function and perform the activities under Customizing, the system creates and synchronously updates transparent DDIC
tables with the existing data contained in the registered HCM cluster result tables. If configured accordingly, the system will consistently update the
corresponding transparent tables during the end-to-end payroll process.

You can execute the initial load report (RPCDCT_INITIAL_LOAD_CE) to fill in the new transparent DDIC tables with the existing payroll results.
You can control access to the new transparent tables (transaction SE16), using S_TABU_NAM. You can implement authorization checks at database level
using suitable SQL privileges. In the report, you can check authorizations against the existing authorization objects for employee data, and against the cluster
authorization object P_PCLX.
You can switch on the declustering function and define the database connection per PCLx table and RELID, and you can configure which subset of the allowed
cluster tables shall be declustered, using the Customizing activities iunder the Declustering Tools node of the relevant payroll structure.
HR Professional: Enhancements to Dynamic Processing Rules
HR Professional: Enhancements to the Roadmap Form
HR Professional: HR Object Delimitation
HR Professional: Country-Specific Information
More Information
For more information about the business function, see HCM, Personnel & Organization 06.
Technical Details

EA-HR 607 SP31
1.1.4.4.3.1 HR Professional: Enhancement to Dynamic

Processing Rules
With this enhancement, you can now assign a dynamic processing rule (DPR) to a delete operation. This allows you to configure dynamic processing rules
that are triggered when the system deletes an infotype record. This happens in the Master Data Application or in the roadmap form when the user deletes
infotype records. Alternatively, a DPR can be configured so that when, for example, an infotype is delimited, this results in another infotype record being
deleted.
Technical Details

EA-HR 607

PA-PAO

EA-HR 607 SP31

Customizing
Make the settings for your operations in the operations view in Customizing for Personnel & Organization Master Data Application Dynamic
Processing Rules
Dynamic Processing Rules
1.1.4.4.3.2 HR Professional: Enhancements to the Roadmap Form

Add attachments to roadmap form steps
You can now configure attachment types for a given form scenario in the roadmap form. For each individual step, you can define what the user is authorized to
do with the attachment. For example, can the user create the attachment, display it, or should the existence of an attachment be hidden from the user? Does
the step require an attachment? Or is the attachment optional?
Select from multiple valid infotype records in roadmap form operations
In the roadmap form, multiple valid records are now available for selection for the operations Modify , Copy , Delete , and Delimit . The availability of
multiple records is dependent on the operation and the time constraint.
Delete Operation for Roadmap Forms
In the roadmap forms, you can can now process infotypes that are configured for deletion. One option is to configure an infotype with the operation Delete in
the HCM P&F design time (transaction HRASR_DT). The other option is to configure a dynamic process rule (DPR) with the operation Delete .
Technical Details

EA-HR 607

PA-PAO

EA-HR 607 SP31

To configure attachment types for the roadmap form, see the Customizing activity Personnel & Organization Processes Design Time for Processes
and Forms Define Attachment Types
See also
Time Constraints: Roadmap Forms for information on the relationship between the time constraint of a record, the operation, and availability of multiple records
for selection.
Dynamic Processing Rules for information on the operation Delete in the document Operations View.
1.1.4.4.3.3 HR Professional: HR Object Delimitation
This feature enables you to ensure that only valid HR objects are displayed for selection in the input value help (F4) for HR Professional solutions. For detailed
information, please see the SAP Note 1883014 .
Technical Details

EA-HR 607

EA-HR 607 SP31
See also
In this section, you will find the release notes for SAP_HR 608 and EA-HR 608, Support Package 04.
1.1.4.5.1 HCM, Employee Self-Service on SAP UI5 2
With this business function, you can use the SAP UI5-based Record Working Times application and the My Timesheet lane.
More Information
For more information about the business function, see HCM, Employee Self-Service on SAP UI5 2.
Technical Details
Technical Name of Business Function HCM_ESS_UI5_2
Available as of EA-HRRXX 607 SP31; EA-HRRXX 608 SP04
Record Working Times SAP UI5 (CATS)
Customizing
For more information about Record Working Times SAP UI5, see Customizing under Personnel Management Employee Self-Service (SAPUI5)
Working Time Record Working Time .
1.1.4.5.1.1 Record Working Times SAP UI5 (CATS)
This feature enables you to perform the following tasks:

Create a new time recording entry.
View the recorded data.
Delete recorded data.
Provides fast data-entry options such as Worklist and Favorites.
Print the time sheet data by using the Print icon in the lane.
Release time sheet data.
Technical Details
Technical Name of Product Feature HCM_ESS_UI5_2_PF01
Software Component Version EA-HRRXX
Application Component PA-ESS-XX
Availability EA-HRRXX 607 SP31; EA-HRRXX 608 SP04
Required Business Function(s) HCM, Employee Self-Service on SAP UI5 2
Customizing
For more information about Record Working Times SAP UI5, see Customizing under Personnel Management Employee Self-Service (SAPUI5)
Working Time Record Working Time .
See also
SAP Library for SAP ERP under SAP ERP Central Component Human Resources Shared Services Employee Self-Service Employee Self-
Service (SAPUI5) Applications and Features for Employee Self-Service (SAPUI5) .
HCM, Personnel & Organization 05 (Reversible)
HR Professional: Dynamic Processing Rules
HR Professional: Enriched Context-Relevant Navigation
More Information
For more information about the business function, see HCM, Personnel & Organization 05 (Reversible).
Technical Details

EA-HR 607 SP31
1.1.4.5.2.1 HR Professional: Dynamic Processing Rules
With this feature, users are able to maintain employee and organizational master data better than ever before. Available in the HR renewal Web Dynpro ABAP
Master Data Application for single infotypes and infotypes in the roadmap forms, a dynamic processing rule (DPR) evaluates the impact of user changes and
guides them to the next infotype for processing, or automatically updates infotypes in the background.
Supported by preconfigured forms comprising all the relevant master data, a DPR enhances data quality and increases system automation. You can use or
adapt a delivered DPR, for example the international DPR, Maintain Children , or use this rich configurable rules framework to create your own DPR.
Technical Details

EA-HR 607

EA-HR 607 SP31
Required Business Functions HCM_PAO_CI_5 (HCM, Personnel & Organization 05)
Additional Details
DPRs are similar to the dynamic processing actions available for SAP GUI applications for the transactions PA40 and PA30. In the Web Dynpro Master Data
Application, this rich configurable rules framework offers you the following features:
Use or adapt DPRs that SAP provides – for example, the international DPR, Maintain Children or the DPR available for Germany,
CREATE_IT0019_PRIOR_ATTACHMENT.
Create your own DPRs to meet your requirements. For example, you can define DPRs as follows:
Internationally, locally, or for a number of countries
To overwrite international DPRs with country-specific settings, if other conditions apply in certain countries
With conditions and target operations based on simple settings
Add in code-based logic, if required as part of configuration (no modification)
Rule Manager
Checks that DPRs are correct. If there are errors, troubleshooting is easy thanks to an extensive error log from which you can navigate directly to the
source of the error. Allows you to manage the activation and deactivation of DPRs.
Customizing
Make the settings for DPRs in Customizing for Personnel & Organization Master Data Application Dynamic Processing Rules
See also
1.1.4.5.2.1.1 HR Professional: Enriched Context-Relevant

Navigation
With this feature, employee and organizational master data now offers context-specific navigation options. In the Web Dynpro ABAP Master Data Application,
this new navigation option, Further Options lets users seamlessly navigate to related infotypes, reports, other applications, as well as to information required
to complete their tasks in as short a time as possible.
Context-specific navigation links are available for various countries including Germany where, for example, you can directly link to documentation provided by
Health Insurance companies from the infotype General Social Insurance Data . You can use the transaction LPD_CUST to create context-specific navigation
links.
Technical Details

EA-HR 607

EA-HR 607 SP31
Required Business Functions HCM_PAO_CI_5 (HCM, Personnel & Organization 05)
Additional Details
If required, you can refer to one of delivered launchpads in the transaction LPD_CUST , for example, the instance IT_NAVIGATION_DE for the role
HRPAO as a guideline for creating your own context-specific links.
Customizing
You make the required settings in Customizing for Personnel & Organization Role Configure Launchpad for Actions
See also
Infotype Navigation
1.1.4.5.3 HR Professional: Country-Specific Information
In this version of HR renewal, localization enhancements are available for the following countries:
HR Professional: Country-Specific Information for Austria, Columbia, Czech Republic, Ireland, Malaysia, Russia, Saudi Arabia, Singapore, and South
Africa.
HR Professional: Country-Specific Information for Germany
Technical Details
Country Dependency Valid for countries listed
Software Component Version See the country-specific release notes listed above
Application Component See the country-specific release notes listed above
Available as of See the country-specific release notes listed above
Required Business Functions See the country-specific release notes listed above
See also
1.1.4.5.4 HR Professional: New Role Version and Launchpad

Enhancements
With this HR composite role ( SAP_PAO_HRPROFESSIONAL_4 ), users have access to the landing page for the HR Professionals and to a new configuration
concept for the Actions lane. The entry role HRPAO , instance BASIC_ACTIONS contains international infotypes for employees. You can copy this record
as a basis, and assign it to your customer-specific HR Professional role. A new type of Launchpad, repository, stores navigation links for employee and
organizational master data and you can include this in the central Launchpad. Sample repository repositories are available for country-specific menus for
employee master data, time management master data, and organizational management master data.
Technical Details

EA-HR 607

EA-HR 607 SP31
Additional Details
SAP recommends including repositories in the copy of the instance BASIC_ACTIONS .
A repository can be used if the same application is contained in several launchpads. In this case, you maintain the application entry once only in a repository.
The launchpads that you want to include in this application do not contain the whole application data, but only reference the repository application. It is also
possible to reference complete repository folders, if the folder structure in the referencing launchpad still adheres to the launchpad type. It is, however, not
possible to create references between repositories. If an application in the repository is changed, all launchpads that reference this application are updated
automatically.
It is still possible to use the previous instance ACTIONS , but BASIC_ACTIONS and the linking concept with repositories is an alternative that enhances
performance and reduces TCO.
Customizing
Make the settings for this feature in Customizing for Personnel & Organization Role Configure Launchpad for Actions
See also
HR Professional
HCM Processes & Forms Enhancements
With this new feature, users can choose Save Draft and then decide either to stay in the draft and continue editing, or to exit the application, and continue to
work on the draft later on.
The handling of attachments in the form type FPM Form is the same in the standalone HCM P&F application and in the HCM P&F application which is
embedded in the Master Data Application.
The form type Roadmap Form has been enhanced with the Utilities feature, allowing users to view customer-specific links and history. In the Landing Page
for the HR Professional, the handling of the form types FPM Form and Roadmap Form has also been made consistent in the Tasks by Draft lane, the
Processes lane, and the Process Monitor .
Technical Details

EA-HR 607

EA-HR 607 SP31
1.1.4.5.6 HCM, Manager Self-Service on SAP UI5 3
You can use this business function to archive/destroy notes data in Manager Self-Service (MSS). Note that when you activate this business function, the
switch HRMSS_SFWS_UI5_UI_03 is activated.
More Information
For more information about the business function, see HCM, Manager Self-Service on SAP UI5 3.
Technical Details
Technical Name of Business Function HCM_MSS_UI5_3
Available as of EA-HRGXX 607 SP31; EA-HRGXX 608 SP04
For more information about the feature provided with this business function, see the following release note:
Archive/Destroy Notes Data
Customizing
For more information about Destruction of Notes Data, see Customizing under Personnel Management Manager Self-Service (SAPUI5) Employee
Profile Archive/Destroy Notes Data .
1.1.4.5.6.1 Archive/Destroy Notes Data
This feature enables you to archive or destroy notes data from the HRMSS_D_NOTES table by using the archiving object HRMSS_NOTE. You can filter the
records to destroy data based on any of the following fields:
PERSG- You use this for the employee group.
PERSK- You use this for the employee subgroup.
MOLGA- You use this for the country grouping.
Note
You can use the BAdI - Available Condition Fields: Value Determination (BADI_IRM_OT_FLD) to implement the condition fields.
It also takes into consideration the value determination for the time reference (Direct) which is the last changed date of the table. With this feature, it would
now be possible to adhere to the various country-specific rules for management of employee data.
Technical Details
Technical Name of Product Feature HCM_MSS_UI5_3_PF01
Software Component Version EA-HRGXX
Application Component CA-MSS-HCM
Availability EA-HRGXX 607 SP31; EA-HRGXX 608 SP04
Required Business Function(s) HCM_MSS_UI5_3
Customizing
For more information about Archiving of Notes Data, see Customizing under Personnel Management Manager Self-Service (SAPUI5) Employee
Profile Archive/Destroy Notes Data .
See also
SAP Library for SAP ERP under SAP ERP Central Component Human Resources Shared Services Manager Self-Service Manager Self-Service
(SAPUI5) .
1.1.4.5.7 Destruction of PBC Document Data
This function simplifies the deletion of data belonging to PBC documents with the help of SAP Information Lifecycle Management (ILM).
You can remove data relating to PBC documents that is no longer needed in daily business from the database. You can store the data in archive files and
destroy it after the defined retention duration has expired. After data destruction, the data is irretrievably removed from the data base and from the archive
system.
In addition to data archiving, the archiving object Archiving PBC Documents (HR_PBCDOC) now supports the function for data destruction using Retention
Management for SAP Information Lifecycle Management (ILM). In Retention Management, you can create and edit policies and rules for the residence duration
(residence rules) and the retention duration (retention rules) of the data objects. PBC documents (Position Budgeting and Control (PBC)) consist of data
relating to commitment documents for budget planning and budget management that is stored in SAP ERP HCM.
Technical and Other Details
Technical Name of Product Feature PSM_PBC_ARCH
Software Component Version EA-HRGXX
Application Component Position Budgeting and Control (PA-PM-PB)
Available as of HR renewal 2.0 SP04
Existing Data
In addition to the archiving and reloading of archived commitment documents, the following new and modified functions are available for HR_PBCDOC in
Archiving Administration (transaction SARA):
Deletion
You use this function to schedule and start the deletion program. The system evaluates the retention rules and determines whether the retention duration
for the data objects that have been read from the previously created archive file has expired. If this is the case, then the data is deleted from the
database and the archive system.
Reading
With this function, you can schedule or start the read program with which you read or evaluate archived data.
Customizing
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
Application Server Basis Services Information Lifecycle Management .
Run transaction IRMPOL and maintain the required retention policies for the ILM object HR_PBCDOC.
See also
Using ILM Retention Management in the Application System
Data Archiving with Archive Development Kit in the SAP Library for SAP NetWeaver under SAP NetWeaver Platform Application Help Function-
Oriented View Solution Life Cycle Management Data Archiving Data Archiving in the ABAP Application System
Using HR_PBCDOC to Archive or Destroy Data Relating to PBC Documents
For security-relevant information, see the SAP ERP Central Component Security Guide (sectionData Protection under Human Resources ).
1.1.4.5.8 Payroll Control Center for the Payroll Process Manager
As of SAP_HR 6.08, SP04 the business function Payroll Control Center for the Payroll Process Manager is available.
You can use this business function to allow payroll process managers to:
Plan payroll processes and all involved process steps
Execute all needed process steps of a payroll process
Monitor the progress and status of all payroll processes
Execute validation rules and distribute the identified issues and compliance violations to the responsible payroll administrator for correction
Confirm successful execution of process steps, step groups, and processes
Enable audit processes based on a log file that is filled automatically by the system and can be enhanced by the user creating new log entries
More Information
For more information about the business function, see Payroll Control Center for the Payroll Process Manager
Technical Details
Technical Name of Business Function HCM_LOC_CI_68
Available as of SAP_HR 6.08, SP04
Existing Data
When you activate the business function, you can configure the payroll process for your payroll process manager using data grouped by processes, process
step groups, and process steps.
In the process hierarchy, a process consists of several process step groups, such as pre-payroll, payroll, pay remuneration, bank transfer, and posting. Each
process step group contains one or more steps, such as payroll run and payroll data verification
For processes and process steps you can define templates (e.g. regular payroll process). These templates can be used to define processes and process
instances (e.g. monthly payroll for payroll area A1 and payroll period July 2014).
System Administration
You can assign authorization to users to access the data during the different processes.
Customizing
You can configure the payroll process for payroll process managers to suit your requirements in Customizing. You can define process templates and
categories, process step templates and assign the process templates to processes.
You can access the Customizing activities under Payroll Control Center in the Payroll International structure.
1.1.5 Industries in SAP ERP
1.1.5.1 SAP Student Lifecycle Management
1.1.5.2 SAP Public Sector
1.1.5.2.1 SAP Public Sector Collection and Disbursement (PSCD)
1.1.5.2.1.1 Connecting Several CC Systems to a FI-CA System
If you have integrated SAP Convergent Charging with SAP Convergent Invoicing, you can distribute processing in SAP Convergent Charging to multiple
systems (CC systems) and connect these in parallel to the system in which SAP Convergent Invoicing is running (FI-CA system). You control the
communication between SAP Convergent Invoicing and SAP Convergent Charging using rating areas that you enter in the provider contracts of your business
partners.
Processes that exchange data with SAP Convergent Charging over the interface determine the CC system, to which they should communicate master data
and transaction data, using the rating area.
If you are connected to more than one CC system, you can transfer provider contracts from one CC system to another. You trigger the contract transfer in
SAP CRM.
SAP Convergent Charging makes Web services for the contract transfer available. Contract Accounts Receivable and Payable uses the service consumers
CustomerDataExportImportServices and OperationalStatusServices for the contract transfer. You have to enter a suitable connection to the
CC system for these service consumers (for example, in transaction SOAMANAGER).
Technical Details
Technical Name of Product Feature PSCD_CONNECT_MULTI_CC_SYSTEMS
Software Component Version IS-PS-CA 618
Application Component IS-PS-CA (Public Sector Contract Accounts Receivable and Payable)
Available As Of SAP Enhancement Package 8 (SP01) for SAP ERP 6.0
Required Business Functions PSCD_COLLECTIONS_MANAGEMENT_5
The following transactions on the SAP Easy Access screen under Master Data For Integration with Rating and Charging Replication now also take
rating areas into account:
Monitor Replication (transaction FKKCC_MD_MON)
Resend Failed Replication (transaction FKKCC_MD_PRC)
Manual Replication (transaction FKKCC_MD_MAN)
Delete Distribution Records (transaction FKK_CC_CLU)
Compare Master Data in FI-CA and SAP CC (transaction FKKCC_MD_COM)
The prerequisite for connecting multiple CC systems to an FI-CA system is activating the joint replication of all master data to SAP Convergent Charging. In
Customizing for Contract Accounts Receivable and Payable, choose Integration Convergent Charging Activate Joint Replication of All Master Data .
Then activate the use of multiple CC systems in Customizing for Contract Accounts Receivable and Payable under Integration Convergent Charging
Specifications for Connecting Multiple CC Systems to an FI-CA System Activate Multiple CC Systems for an FI-CA System .
Finally, define the rating areas in Customizing for Contract Accounts Receivable and Payable under Integration Convergent Charging Specifications for
Connecting Multiple CC Systems to an FI-CA System Define Rating Areas .
Then in the following activity, Assign Rating Areas to Logical Ports , specify which logical ports the individual rating areas use to communicate with your CC
systems.
More Information
PSCD, Collections Management 5
Master Data in SAP Convergent Invoicing
Provider Contract
1.1.5.2.1.2 Collaborative Liability
This function makes the collaborative liability available in Public Sector Contract Accounts Receivable and Payable. Processes are provided to support the
various types of collaborative liability, such as shared liability and third-party liability in the system. Existing receivables to a contract partner can be replicated
to additional contract partners. This ensures that the replicated receivables do not generate a value update in general ledger accounting.
The following functions are available to users in the Web Dynpro-based collaborative liability work center:
You can define involved contract partners as a debtor group in collaborative liability. You can assign a percentage share of the total debt to each debtor.
In the collaborative liability data record, you can select a receivable, distribute it from the main debtor to the co-debtor, manually edit the receivable
amounts calculated by the system and then trigger the posting in Contact Accounts Receivable and Payable. Distributed receivables are posted as
statistical document items in Contract Accounts Receivable and Payable.
The business transaction for a distributed receivable and the postings that result from this are managed as items (original item and distributed items) in a
co-debtor data record. Receivable items, incoming payment amounts and the distributed payment amounts are shown in the items.
You can assign a user status to the business transactions used in status management for the collaborative liability. You can remove completed
collaborative liability data using a deletion program.
You can make customer-specific enhancements to the collaborative liability using the events 0490-0498.
Technical Details
Technical Name of Product Feature ISPSCA_COLIABILITY
Software Component Version IS-PS-CA 618
Application Component IS-PS-CA (Public Sector Contract Accounts Receivable and Payable)
Available As Of SAP Enhancement Package 8 (SP01) for SAP ERP 6.0
Required Business Functions PSCD Collection and Disbursement
Make the Customizing settings for collaborative liability under Financial Accounting (New) Contract Accounts Receivable and Payable Business
Transactions Collaborative Liability .
More Information
For more information, read the PSCD, Collaborative Liability business function.
1.1.5.3 SAP Utilities
1.1.5.3.1 Simplified Master Data Synchronization
The report REAMI_SIMPLEMDSYNC simplifies the master data synchronization by only synchronizing new or modified master data with the external system
(such as MDUS). This replaces the existing synchronization procedure, which is based on sending several enterprise services, and in addition to a
significantly shorter runtime, also has the benefit that it is no longer necessary to configure and maintain individual services.
Delta replication to the external system is provided by automatically including the ID of modified or new devices and EDM profiles created in the trigger table
TEAMI_SMDSTRIGG.
Technical Details
Technical Name REAMI_SIMPLEMDSYNC
Country Dependency Valid in all countries
Software Component Version SAP Enhancement Package 8 for SAP ERP 6.0 SP01
Application Component IS-U-DM (Device Management)
Available As Of SAP Enhancement Package 8 for SAP ERP 6.0 SP01
Required Business Functions ISU_AMI_5 (Utilities, Advanced-Metering-Infrastruktur 5)
Prerequisites
If you want to use the simplified master data synchronization, you must do the following:
Activate the business function ISU_AMI_5 with the switch ISU_AMI_5_SMDS.
You make settings in Customizing for SAP Utilities under Advanced Metering Infrastructure Basic Settings Define Simplified Master Data
Synchronization .
Have the authorization E_AMI_SMDS.
More Information
For more information, see: Simplified Master Data Synchronization.
For more information about the existing master data synchronization, see
Synchronize Device Data
Synchronize Profile Data
1.1.5.3.2 Add Customer-Specific Fields to the Device Master Data
You can use the new Business Add-In (BAdI) ISU_DM_DEVICE to add customer-specific fields to the IS-U device master data. You can store these fields in
the device master data (EGERS) and incorporate your own customer-specific tables.
You must perform the following steps to integrate your fields in master data maintenance:
1. Extend standard IS-U database tables (using an append) and/or create customer-specific database tables.
2. Extend standard IS-U database views and structures using an append (optional).
3. Display customer-specific screens (of the type Subscreen ) to display or maintain the fields in the customer enhancement.
4. Define and activate the BAdI ISU_DM_DEVICE to integrate customer-specific fields in the standard master data maintenance transactions.
You do not need to implement all interface methods provided. This is defined by the required scope of the planned enhancement.
Technical Details
Technical Name of Product Feature ISU_DEVICE_ENHANCEMENT
Software Component Version IS-UT 6.18
Application Component IS-UT ( SAP Utilities Device Management )
Available As Of SAP Enhancement Package 8 for SAP ERP 6.0, SP 01
Required Business Functions Keine
More Information
For more information, see the system documentation for the BAdI ISU_DM_DEVICE.
1.1.5.3.3 Copy Values from EDM Profile Version in Transaction

EEDM01
In the transaction EEDM01 (Change Profile Values), you can choose Version to copy profile values from EDM profile versions. This can be advisable if
values that were modified manually contain errors or are not to be tracked during a check.
The Copy Values from Version function accesses a dialog box on which the existing versions are displayed. To restrict profile values from versions more
specifically, you can modify the value of the following columns on this dialog box:
Day From
Day To
Time From
Time To
Note
The columns listed above cannot be modified if you have defined several lines as relevant periods in the lower half of the SAP List Viewer (ALV).
Once you have selected the versions to be used to copy the profile values, the system replaces the current values with the values of the selected versions.
The system also stores the replaced values as a version.
Technical Details
Technical Name of Product Feature ISU_EDM_VALUES_FROM_VERSION
Application Component IS-U-EDM
Required Business Functions ISU_EDM_2
1.1.5.3.4 Generate EDM Profile Header and Allocate a Register
You can use the master data template category EDM_PROFHEAD_ASSIGN to generate an EDM profile and allocate an interval meter to the register. The
register can be identified using the register number (ZWNUMMERE) or the register code (REGISTERCODE). You can also use this master data template category
to change the profile allocation.
You can use the master data template category EDM_PROFHEAD_ASSIGN to create and allocate formula instances.
Technical Details
Technical Name of Product Feature ISU_EDM_MDT
Required Business Functions ISU_EDM_2
1.1.5.3.5 Quantity Determination on the Basis of Meter Reading

Profiles
SAP Utilities now supports quantity determination based on EDM meter reading profiles (equidistant time series).
The process is as follows:
1. Time series data containing equidistant meter readings (measured every 15 minutes, for example) is imported into the SAP EDM data repository.
2. Equidistant quantity values are calculated based on the imported meter readings.
3. The calculated quantity values are stored as time series values of an EDM profile.
4. Calculated quantities are made available for subsequent processes such as RTP billing, settlement, and intercompany data exchange.
Technical Details
Technical Name of Product Feature ISU_EDM_METER_READING_PROFILE
Required Business Functions ISU_EDM_2 (Utilities, Energy Data Management 2)
1.1.5.3.6 Profile Calculation Using the Formula Calculation

EEDMCALCMA
You can use the transaction EEDMCALCMA for optimized execution of the EDM formula calculation. You use this mass activity for calculation runs involving
very large numbers of formula instances and you can use it as an alternative or in parallel to transaction EEDMCALCWB.
The advantage of transaction EEDMCALCMA compared to transaction EEDMCALCWB is that it has a shorter runtime. However, EEDMCALCMA does not support
formula hierarchies, which is the case for transaction EEDMCALCWB.
Technical Details
Technical Name of Product Feature ISU_EDM_CALCULATION
Required Business Functions ISUU_EDM_2 (Utilities, Energy Data Management 2)
1.1.5.4 SAP for Healthcare
The release notes for SAP Patient Management (IS-H) and SAP Ambulatory Care Management (IS-H-ACM) are available on SAP Service Marketplace at
http://service.sap.com/healthcare-releasenotes .
1.1.5.5 SAP for Media
1.1.5.5.1 Media, Provider Contract
As of SAP enhancement package 8 for SAP ERP 6.0, SP01, you can use the provider contract in SAP Convergent Invoicing in the SAP for Media area.
Technical Details
Technical Name of Product Feature MED_INV_PP_1
Software Component Version IS-M 6.18
Application Component IS-M ( Contract Accounts Receivable and Payable )
Required Business Function MED_INV_PP
Activities
You make the system settings for provider contracts in Customizing for Contract Accounts Receivable and Payable under Basic Functions Provider
Contract in the following activities:
Activate Provider Contract
In this step you activate the usage of provider contracts.
If you are already using a different contract object and are therefore activating the provider contract as a second contract, the system uses
subapplication P for the provider contract. In this case, activate subapplication P under Basic Functions Activate Subapplication .
Derivation of Standard Account Assignment
You record specifications here for deriving the account assignments required.
Define Number Range
You must maintain number ranges here to ensure that replication of provider contracts is successful. You require number range 01 with internal number
assignment and number range 02 with external number assignment.
Check that the number ranges have been synchronized with those used in SAP CRM.
Enter Field Attributes per Activity
You define here according to the activity which fields in the master record maintenance require an entry, are ready for input, are displayed or hidden.
Specify Authorization Types
You define new authorization types here, which are to be controlled using a maintenance authorization.
Define Field Groups for Authorization Check
You can define whether the authorizations are checked for every field group in the provider contract.
Define Counters on Provider Contract Items
Record the types of ID you want to use in Customizing for Contract Accounts Receivable and Payable under Basic Functions Provider Contract
Define the Type of ID . You also specify what types are relevant when searching for partner agreements or prepaid accounts.
Define Counter on Provider Contract
In Customizing for Contract Accounts Receivable and Payable under Basic Functions Provider Contract Counter on Provider Contract
Record the counters you require for display in the ERP system
Counters from the rating and charging system and their assignment to counters in the ERP system
Counter groups for restricting the display
Define Product Storage Control
Record the product storage you want to use in Customizing for Contract Accounts Receivable and Payable under Basic Functions Provider
Contract Make Central Settings for Products .
You make the settings for the Common Object Layer Framework in Customizing for Contract Accounts Receivable and Payable under Integration
Convergent Charging Set Up Replication of Provider Contracts .
More Information
Provider Contract
Media: Master Data Objects Provider Contract, Product
Media, Billing in Contract Accounts Payable and Receivable 1
1.1.5.5.2 Media: Master Data Objects Provider Contract, Product
You can use the new master data objects Media, Provider Contract and product in an integrated scenario with SAP Customer Relationship Management (SAP
CRM), Contract Accounts Receivable and Payable in SAP ERP, and SAP Convergent Charging (SAP CC). In the individual components, the product and
provider contract are used as follows:
SAP Customer Relationship Management (SAP CRM)
In the CRM system, you configure and manage your products. You also manage customer and contract data. You transfer the parts of this data needed
in conjunction with SAP Convergent Invoicing to the affected systems.
SAP Convergent Charging (SAP CC)
SAP Convergent Charging generates billable items for the services used and transfers them for subsequent processing to billing in Contract Accounts
Receivable and Payable in the ERP system. The basis for the creation of billable items are sets of rules stored in SAP CC for pricing and account
determination in combination with customer data, contract data and product data that was replicated from SAP CRM. The billable items contain the price
that is due for the use of the service, and information about the account to which the receivables or payables are to be posted.
SAP ERP
Billing in Contract Accounts Receivable and Payable accepts the billable items from SAP Convergent Charging. It creates invoices and credit memos
from them, posts the corresponding receivables or payables, and manages them until they are paid.
The following describes the processes in billing in Contract Accounts Receivable and Payable. Reference is made to SAP CRM and SAP CC only where it is
necessary for creating a clear picture of the processes.
Overview
In the case of integrated use of Contract Accounts Receivable and Payable, SAP CC and SAP CRM, SAP CRM is the leading system as regards master
data. That means that you enter and change provider contracts and products in SAP CRM and then replicate these to SAP ERP and SAP CC. SAP ERP
keeps only the information for the provider contract and product that you need directly for the business transactions that take place in SAP ERP.
In SAP ERP you normally just display provider contracts and products. Change transactions are available for exceptional cases. However, these changes are
purely local and are not distributed to the connected systems. During the next replication of master data from SAP CRM, the system overwrites any manual
changes.
Provider Contract
A provider contract relates to one business partner. Each contract item relates to a contract account and/or a prepaid account.
The following data is saved in the provider contract header:
Number of the business partner who signed the provider contract.
Contract start and contract end
Authorization group and company code for authorization checks
The header of every provider contract references the contract items that contain the following data:
Contract account and/or prepaid account
Number of the product to which the provider contract refers.
Standard account assignment used for the billable item, such as company code, business area, standard division, profit center and segment.
You can display (transaction FP_VT3) and change (transaction FP_VT2) provider contracts from the SAP menu under Master Data For Integration with
Rating and Charging Provider Contract . You can change provider contracts in Contract Accounts Receivable and Payable, but should only do so in
justified exceptional cases, for example if errors occur when replicating the data from the CRM system, but current data is urgently required in Contract
Accounts Receivable and Payable.
When the billable item is generated in SAP CC, the system determines which contract account, business partner and provider contract (specifically which
contract item) are affected. This information is found in the billable item and is transferred to SAP ERP.
Product
The product information in Contract Accounts Receivable and Payable consists of the following parts:
Language-dependent texts
Sales-area-dependent data
You can display products from the SAP menu under Master Data For Integration with Rating and Charging Product . You can change products
(transaction FPPRD2) in Contract Accounts Receivable and Payable or create them (transaction FPPRD1), but this should be limited to exceptional cases (for
example, to temporarily correct errors during replication).
During the replication of products from SAP CRM, Contract Accounts Receivable and Payable stores the sending system and the product type as part of the
product. The information is used to ensure that when products are transferred, an existing product in Contract Accounts Receivable and Payable is not
overwritten by a product with the same name or another product type. If you create a new product in Contract Accounts Receivable and Payable, or set the
technical settings (logical system and product type) to their initial values, the system overwrites the changed data with the currently valid values during the
next replication from the CRM system.
Common Object Layer Framework (COL Framework)

The Common Object Layer Framework (COL Framework) is available for integration and data distribution for the provider contract in SAP ERP and SAP CC.
The COL Framework is not restricted to the provider contract here, but can be extended to additional replication objects by making program enhancements and
additional settings in Customizing.
You can use the authorization object X_COL_OBJ to perform general authorization checks in the COL Framework.
The Business Object Layer (BOL) model (BOL component ISXCTR), which has been integrated in the COL Framework, is also available for the provider
contract. This means that specific Web services can be generated for the provider contract on the basis of the BOL Web service framework.
Technical Details
Technical Name of Product Feature MED_INV_PP_2_PF1
Software Component Version IS-M 618
Application Component IS-M-CA ( Contract Accounts Receivable and Payable Convergent Invoicing )
Required Business Function MED_INV_PP_1
Activities
You make the system settings for provider contracts in Customizing for Contract Accounts Receivable and Payable under Basic Functions Provider
Contract in the following activities:
Activate Provider Contract
In this step you activate the usage of provider contracts.
If you are already using a different contract object and are therefore activating the provider contract as a second contract, the system uses
subapplication P for the provider contract. In this case, activate subapplication P under Basic Functions Activate Subapplication .
Derivation of Standard Account Assignment
You record specifications here for deriving the account assignments required.
Define Number Range
You must maintain number ranges here to ensure that replication of provider contracts is successful. You require number range 01 with internal number
assignment and number range 02 with external number assignment.
Check that the number ranges have been synchronized with those used in SAP CRM.
Enter Field Attributes per Activity
You define here according to the activity which fields in the master record maintenance require an entry, are ready for input, are displayed or hidden.
Specify Authorization Types
You define new authorization types here, which are to be controlled using a maintenance authorization.
Define Field Groups for Authorization Check
You can define whether the authorizations are checked for every field group in the provider contract.
You make the settings for theCommon Object Layer Framework in Customizing for Contract Accounts Receivable and Payable under Integration
Convergent Charging Set Up Replication of Provider Contracts .
1.1.5.5.3 Integration with Revenue Accounting
You can integrate SAP Convergent Invoicing with Revenue Accounting if you:
Use provider contracts
Use the SAP ERP add-on SAP Revenue Accounting and Reporting
If you have integrated SAP Customer Relationship Management (SAP CRM), SAP Convergent Invoicing (in SAP ERP) and SAP Convergent Charging (SAP
CC) in the Offer-to-Cash end-to-end process, the integration with Revenue Accounting takes place solely by means of the ERP system. The ERP system
transfers all necessary data to Revenue Accounting.
Technical Details
Technical Name of Product Feature FICA_REVENUE_ACCOUNTING_INTEGR
Software Component Version FI-CA 617
Application Component FI-CA-IN (Integration)
Available As Of SAP enhancement package 7 (SP09) for SAP ERP 6.0
Required Business Functions None
Additional Details
In Revenue Accounting, data is updated using revenue accounting items. The following types of revenue accounting items exist in Revenue Accounting:
Order items
Fulfilment items
Invoice items
SAP Convergent Invoicing generates:
Order items from provider contract maintenance, and from one-off charges that are transferred to the system as billable items
Fulfillment items during the transfer of billable items to rated consumption
The interface component Integration with Revenue Accounting (REVENUE_ACC) provides the fields in the interface for transferring billable items that
you use for transferring data that is needed for Revenue Accounting to billing and invoicing.
Invoice items from invoicing
You control the type of revenue accounting items the system creates using the service types assigned to provider contract items and billable items.
Creation of Order Items from the Provider Contract
If the system is configured for it, the ERP system generates order items (for Revenue Accounting) for contract items, when you create and change provider
contracts.
For each contract item affected by a change, the system generates at least one order item for Revenue Accounting. Each order item consists of a main item
and dependent conditions. The conditions consist of a condition for the total transaction price, and, if a standalone selling price is entered in the item, a
condition for the total standalone selling price. The system determines the values for the service type for recurring charges, as well as the condition types,
from Customizing.
For each service type of a contract item, the ERP system generates a separate revenue accounting item, consisting of a main item and a condition (if the
system is configured for this). The system determines the condition type from Customizing.
There could be additional service types entered on the contract item. These service types reflect the consumption affecting the contract item, without an
amount or quantity being entered. The system, therefore, identifies the main item as an estimated quantity, and does not show an amount in the condition. In
SAP Revenue Accounting and Reporting , you can use a BRFplus function to add the quantity and amount.
If you create or change contracts, the system processes event 8205 before saving the revenue accounting items. You can use this event to enrich the items
with additional information.
Example
You can use event 8205 to change customer fields or other allowed fields in main items. Or you can use it to adjust existing conditions or to add new
conditions.
Note
When you change amount fields or add conditions, the system marks the revenue accounting items to reflect this.
If you change a provider contract in SAP CRM, you can enter a change reason. The system updates this change reason in the provider contract item in the
ERP system and it is copied to the revenue accounting item. You can use this entry in reporting in Revenue Accounting.
Example
In the case of a contract renewal, you create a new revenue accounting contract in Revenue Accounting for the new performance obligations to be created.
You do this based on the change reason.
Creating Order Items from Billable Items for One-Off Charges
When billable items for one-off charges are transferred, the system generates order items for Revenue Accounting.
The system uses the service type you assign to billable items to determine if a billable item is a one-off charge that is relevant for Revenue Accounting.
In posting area 8172, you define the derivation of the service type for one-off charges reported from SAP CRM.
Creating Fulfillment Items
When billable items for rated consumption are transferred, the system generates fulfillment items for Revenue Accounting.
The system determines if a billable item leads to the creation of a fulfillment item based on the service type that you assign to the billable item using posting
area 8122.
The treatment of fulfillment items is different from all of the other types of revenue accounting items mentioned here. The system does not create fulfillment
items individually for each billable item. Instead it creates a fulfillment item for an aggregate of billable items, in order to reduce the volume of data transferred
to Revenue Accounting.
Creation of Invoice Items
If your system is configured for it, invoicing generates revenue accounting items for line items that are relevant for Revenue Accounting. These revenue
accounting items are used for reporting invoicing results to Revenue Accounting.
You specify by how you configure the service type assigned to the invoicing document item, if the invoicing document item is relevant for creating invoice
items for Revenue Accounting.
Transferring Data to Revenue Accounting
You use a mass activity to forward the revenue accounting items created by SAP Convergent Invoicing to Revenue Accounting. On the SAP Easy Access
screen, choose Periodic Processing Forward Postings Execution Revenue Accounting Transfer (transaction FP_RAI_TRANSF).
You can use the following as selection criteria:
Source Document Item Type
You can enter one or more source document item types: order item (contract item), order item (one-off charges), fulfillment item, invoice item.
Company Code
You can select data from several company codes.
Business Partner
You can select several business partners.
Selection To
You can restrict the data selected to a specific time period.
The mass activity creates revenue accounting items in the following order:
Order items from provider contracts
During the generation, the system uses the time stamp to check if an older version of the revenue accounting item exists that was not yet transferred. If
there is an older version, the system takes only the newest version into account.
Order items from one-off charges
Fulfilment items
To reduce the volume of data transferred to Revenue Accounting, the system aggregates billable items into fulfillment items during a preliminary step.
In the standard system, the mass activity aggregates the billable items into fulfillment items and forwards the fulfillment items in one step. However, you
can change this by choosing a different processing level. Then the mass activity aggregates billable items into fulfillment items in one run, and transfers
the data to Revenue Accounting in a later run.
Invoice items
The revenue accounting items forwarded to Revenue Accounting receive the date and time they were sent.
Reconciliation of Data
You can display and analyze revenue accounting items in Contract Accounts Receivable and Payable. On the SAP Easy Access screen, choose Periodic
Processing Forward Postings Reconciliation Display Revenue Accounting Items (transaction FP_RAI_MON).
In Revenue Accounting, you can find discrepancies between the data sent and the the data stored in Revenue Accounting in transaction FARR_CHECK_CONS,
which checks data consistency.
Archiving
The system makes use of the new table of service types for the provider contract (DFKK_VT_ST) when archiving provider contracts (archiving object
FI_MKKCAVT). See Archiving of Provider Contracts (FI_MKKCAVT)).
Affects on Customizing Settings

You activate the integration with Revenue Accounting and configure the RFC destination to the revenue accounting system, meaning the system, in which
SAP Revenue Accounting and Reporting is running, in Customizing for Contract Accounts Receivable and Payable under Integration Revenue
Acccounting .
In the activities that follow, you then configure your system for the data transfer to Revenue Accounting.
Integration with Revenue Accounting
1.1.5.6 SEM - Strategic Enterprise Management
1.1.5.6.1 FIN_ACC_GC_CHKDGT: Business Function Financials,

Group Close, Check Digits
You can use this business function to calculate check digits for transaction data and persist them in the system. Check digits are a highly summarized display
of the totals data of Business Consolidation (SEM-BCS). They are relevant for the auditability of reported financial data in particular because no
corresponding documents with audit-relevant details such as the user or the date and time of posting exist in the system for reported financial data. By
evaluating the check digits calculated by the system at different times, however, it is possible to see immediately whether the transaction data was changed
during the corresponding time period. Check digits therefore simplify the check process for the consolidated financial statements.
The business function also contains additional new and changed functions.
For more information, see the following release notes:
Check Digits
Consolidation Monitor
Tasks
Data Entry
Reconciliation
Reclassification
Consistency Check for Validation
Technical Reports
Consolidation Group Change
Consolidation of Investments
Deviating Shares
Technical Details
Software Component Version SEM-BW 748
Application Component FIN-SEM-BCS
More Information
SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp608 Application Help <Language> Business Functions Business
Functions in SAP ERP Enterprise Business Functions Accounting Group Close with SEM-BCS → Financials, Group Close, Check Digits.
1.1.5.6.1.1 Check Digits
You can use this function to calculate check digits for transaction data at the level of detail of the organizational unit (consolidation groups and consolidation
units) at three different posting levels (reported financial data, standardizing entries, consolidation entries) and persist them in the system. Evaluation of the
check digits facilitates and accelerates the check process for the consolidated financial statements.
Technical Details
Technical Name of the Product Features FIN_ACC_GC_CHKDGT_PF01
Required Business Functions Financials, Group Close, Check Digits (FIN_ACC_GC_CHKDGT)
Additional Details
Calculation of the check digits is triggered by the execution of tasks in update mode that are located at suitable positions in the task hierarchy and by changes
made to the period status by a user.
You can display check digits in the consolidation monitor. To do this, select a check digit display in the menu bar of the consolidation monitor under the
Environment entry. In the same place, you can find a comparison function that causes the system to recalculate check digits. The system displays the
newly calculated check digits as well as the check digits already persisted in the database, together with status information.
Consolidation Area
Once you have activated the business function, you first need to generate the consolidation area again. You then activate the Check Digits for Transaction
Data function for the consolidation monitor in the consolidation area settings.
Configuration Menu for Consolidation
In the configuration menu for consolidation (transaction UC00), under the Tasks entry, you can find the following settings:
Calculate Check Digits During Task Execution
Here, you specify that the system calculates and persists check digits while executing tasks that are located at suitable positions in the task hierarchy.
You can restrict the calculation of the check digits by making the following entries at individual posting levels:
R: Check digits for reported financial data
S: Check digits for standardizing entries
C: Check digits for consolidation entries
U: Check digits for reported financial data and standardizing entries
A: Check digits for totals data at all posting levels
Hide Unchanged Check Numbers During Comparison
If you activate this setting, during the comparison of check digits in the consolidation monitor, the system displays only those results from the
comparison for which the newly calculated check digit differs from the check digit persisted in the database. To activate the setting, select Hide
Unchanged Check Numbers During Comparison in the first column and enter X in the Characteristic Value column.
More Information
Check Digits for Transaction Data
1.1.5.6.1.2 Consolidation Monitor
You can also change the task status (block, block by user intervention, unblock, or reset) manually for multiple consolidation units simultaneously. This
is possible for the following tasks and task groups:
Tasks that are processed per consolidation unit
Task groups that contain only tasks that are processed per consolidation unit
You can assign a separate authorization for blocking tasks by user intervention. The additional activity Complete Technically is available for tasks in
the authorization object R_UC_TASK for this purpose.
Technical Details

To ensure that the system considers the Complete Technically activity in the authorization check, in the configuration menu for consolidation (transaction
UC00), under the Tasks node, you need to select the entry Authorization Check in the Case of Block by User Intervention in the first column and enter X
in the Characteristic Value column.
More Information
Status Management in the Consolidation Monitor
Authorizations for Tasks
1.1.5.6.1.3 Tasks
You can use this function to specify a default method for tasks in which you assign the method per consolidation unit. When the task is executed, the system
then uses the default method specified for all consolidation units for which you have not entered any explicit settings.
Technical Details
More Information
Method
1.1.5.6.1.4 Data Entry
When copying transaction data, you can specify that the system ignores the posting and data entry block.
A search function is available on the display screen of the goodwill inheritance.
Technical Details
Additional Details
Set the Ignore Posting Block When Copying indicator in the settings of a copy task in the Global Settings group box or on the selection screen for the
execution of a copy method. The system then also copies data for blocked items or transaction types to a target environment (for example, to a plan
version).
More Information
Copy Task
Goodwill Inheritance
1.1.5.6.1.5 Reconciliation
You can use this function in matrix consolidation to influence the level of detail for calculating and recording reconciliation differences. In the settings of a
reconciliation task, you can specify the Reconciliation Level in the Matrix Dimension group box. Specify the level of detail at which the system calculates
and records the reconciliation differences between consolidation units or consolidation unit combinations in the matrix consolidation.
Technical Details
More Information
Reconciliations
1.1.5.6.1.6 Reclassification
You can change the components of a reclassification (trigger, percentage, condition, source, target) by means of custom implementations of
enhancement spot UC_RCL_USER.
You can change the level of detail of the postings in a reclassification in such a way that the reclassification does not post a separate document for
each data line of the trigger, but instead generates documents at the posting level of the document type.
The system writes the information about the method and method step used to post a reclassification or allocation to the document text field, but only if
the document type of the reclassification or allocation does not post by group (that is, it does not post at posting level 30).
Technical Details
More Information
Execution of a Reclassification
1.1.5.6.1.7 Consistency Check for Validation
You can use this function to have the system check all Customizing settings for validation in the consolidation workbench. If it is obvious that a particular
setting negatively affects the runtime of the validation task, the system issues warning messages.
Technical Details
More Information
Execution of Validations
1.1.5.6.1.8 Technical Reports
In the list of journal entries, you can select the following additional control options for database selection:
Do Not Display Reversal Document Pairs
Do Not Display Inversion Document Pairs
You can activate a value check for all input parameters on a selection screen.
Technical Details
To activate the value check for all input parameters on a selection screen, in the configuration menu for consolidation (transaction UC00), under the
Environment node, select the Activate Value Check on Selection Screen entry in the first column and enter X in the Characteristic Value column.
More Information
Technical Reports
1.1.5.6.1.9 Consolidation Group Change
By means of new settings in the consolidation unit hierarchy, you can specify that the postings for the consolidation group change contain not only the
balance sheet, but also the income statement (IS).
You can post acquisitions and divestitures in a consolidation group change and consolidation of investments in the case of an organizational change
using separate transaction types.
Technical Details
You can specify separate transaction types for acquisition or divestiture in an organizational change in the settings for transaction types, in the Carryforward,
Change to Cons Group group box.
1.1.5.6.1.10 Consolidation of Investments
In the automatic consolidation of investments, you can adjust the postings of a first consolidation subsequently.
In the automatic consolidation of investments, you can post the currency translation of a goodwill in local currency from prior years with or without an
effect on net income following an organizational change.
In the automatic consolidation of investments, you can perform the total divestiture of a consolidation unit combination without affecting earnings.
Technical Details
Additional Details
Collection of investment and equity data
For the First Consolidation Adjustment activity, you can enter Additional Financial Data for both investments and equity. However, this is only
possible at a point in time (year, period) that is later than the time of the first consolidation of the investee unit.
Consolidation of investments
The automatic Consolidation of Investments processes investments and equity in an almost identical manner for the First Consolidation and First
Consolidation Adjustment activities. The only difference lies in how the indirect differential that results from the First Consolidation Adjustment activity
is treated. The decision made by the system regarding positive or negative goodwill and the value allowance procedure is not based on the sign of the
indirect differential. Instead, the system applies the decision that it made for the indirect differential in the First Consolidation activity for the same
investee unit to the indirect differential in the First Consolidation Adjustment activity.
If you have set the Total Divestiture with OC Logic or Total Divestiture for a Merger indicator for a consolidation unit combination, the automatic
consolidation of investments generates a posting for the total divestiture of this combination that does not affect earnings.
Data origin
In the settings for the data origin of the consolidation of investments on the Investment Data and Equity Data tab pages, you can specify reported
items for the First Consolidation Adjustment activity.
Activities
In the settings for the activities of the consolidation of investments on the Enter Investment Data and Enter Equity Data tab pages, you can specify
default values for the items for entering the First Consolidation Adjustment activity.
On the Default Sequence tab page, you can change the position of the First Consolidation Adjustment activity. In the standard system, this activity
appears immediately after the First Consolidation activity in the default sequence.
Selected items
In the settings for the selected items of the consolidation of investments on the Goodwill in Local Currency tab page, you can select the Affecting
Earnings (default) or the Not Affecting Earnings value for the setting Translation Prior Years for OC . This setting affects postings in the Goodwill
Currency Translation activity after an organizational change.
More Information
Selected Items
Combinations of Consolidation Units
1.1.5.6.1.11 Deviating Shares
You can use this function to perform the automatic consolidation of investments in parallel with share percentages for regular as well as deviating investments.
This may be necessary, for example, due to special contracts or the requirements of local generally accepted accounting principles. In the additional financial
data for investments, you can enter up to four percentages for deviating direct shares of an investor in an investee unit for this purpose.
Technical Details
BI Content
The delivered BI content contains four additional key figures that you can use to depict deviating shares in the SEM-BCS system:
Share Change, with Voting Rights (0BCS_PCTIN2)
Share Change, with No Voting Rights (0BCS_PCTIN3)
Share Change, Net Income (0BCS_PCTIN4)
Share Change, Other Comprehensive Income (0BCS_PCTIN5)
Data Basis
Once the additional key figures in the BI content have been activated, you can select four additional percentages for investments as Additional Fields in the
data basis on the Data Stream Fields tab page. When you save the data basis, the system generates the data stream for investments again, including the
four percentage fields.
Consolidation Area
In the settings for the consolidation area, you activate the Deviating Shares function.
In the consolidation workbench, in the Settings for Consolidation of Investments , choose the following entries:
Equity
On the Deviating Shares tab page, assign one of the four types of percentages for deviating shares to each of the equity items for which you enter
equity data for the Subsequent Consolidation or Distribution of Dividends activity.
Selected Items
On the Shares tab page, specify statistical items for posting deviating shares.
If you read the investment from the totals database, specify the statistical items for which you enter deviating share percentages on the Deviating
Shares tab page.
More Information
Deviating Shares

ENhancement Package SAP PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ENhancement Package SAP PDF

Hochgeladen von

Copyright:

Verfügbare Formate

What's New in SAP Enhancement Package 8 for ERP 6.

Created on April 06, 2016

1.1 Support Package Stack 1

1.1.1 Cross-Application Components

1.1.1.1 Merge of Components

Technical Name of Product Feature N/A

Product Feature Is Changed

Country Dependency Valid for all countries

Software Component Version SAP_APPL 618

Availability SAP Enhancement Package 8 (SPS 0) for SAP ERP 6.0

Former Software Component Merged to Software Component

EA-APPL-GLO SAP_FIN / SAP_APPL / EA-PS

C-CEE SAP_APPL/ SAP_FIN

1.1.2.1 Financial Accounting

1.1.2.1.1 Enhancements for Tax on Sales/Purchases and VAT

Deactivating Tax Codes

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SAP_FIN 618

Application Component FI-GL-GL (Basic Functions)

Availability SAP enhancement package 8 for SAP ERP 6.0

2074351 : Deactivate tax code for input help

1.1.2.1.2 Collective Call of External Tax System

The following enhancements are also currently available:

Product Feature Is New

Country Dependency Valid for USA and Canada

Software Component Version SAP_FIN 618

Application Component FI-GL-GL (Basic Functions)

Availability SAP enhancement package 8 SPS01 for SAP ERP 6.0

1.1.2.1.3 Enhancements for Automatic Payment Transactions for

Different formats per payment method

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SAP_FIN 618

Application Component FI-AP-AP-PT

Availability SAP enhancement package 8 SPS01 for SAP ERP 6.0

Payment Method Formats

Payment Run Reset

Direct Navigation When Analyzing Payment Data

Effects on System Administration

1943453 : PMW format depending on house bank and company code

1.1.2.1.4 Enhancements to Online Payments and Payments with

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SAP_FIN 618

Application Component FI-BL-PT-AP

Availability SAP enhancement package 8 SPS01 for SAP ERP 6.0

Effects on System Administration

2150758 : New activity 43 (Release) for the authorization object F_PAYRQ

1.1.2.1.5 Enhancements for SAP Bank Communication

Product Feature Is New

Software Component Version SAP_FIN 618

Application Component FIN-FSCM-BNK

Availability SAP enhancement package 8 SPS01 for SAP ERP 6.0

1994602 : BNK_MONI Display of payment currency, if unique

1.1.2.1.6 Cross-Component Check of IBAN Usage

You use this function to check the following:

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SAP_FIN 618 SPS01

Application Component FI-AP-AP-MD (Master Data)

Availability SAP enhancement package 8 for SAP ERP 6.0

Choose Execute (F8) and then ( Documentation ).