Enhancement packages give enterprises the flexibility to extend their SAP software by adding

only those functions and technical improvements that they actually need.

ECC6.0 EHP3 EHP4 EHP6 EHP7

Introduced for ERP

Activating Switch Framework (SFW5)

Customers can activate the new business functions that they want to use via the
Switch Framework
Activating a business function triggers switches. The switch controls whether the
switch controlled code is executed or not at runtime.
The enhancement packages contain new functions for both generic and industry-
specific processes. These new functionsare activated and usually delivered to
customers every two years bundled with all the new and enhanced business software
functionalities that SAP has delivered.

EHP7 Overview

750+ business functions

650 business functions accumulated from prior EHPs
100 new business functions covering financial accounting, Logistics, HR, QM, and
more.
First EHP to be optimized for both SAP HANA and traditional DBs
Reduce adjustment efforts required to migrate SAP Business Suite to SAP HANA in-
memory platform

Top three functional Highlights:

1. SAP Fiori productivity apps (The current collection of 25 role-based productivity

apps in SAP Fiori empower end users to perform recurring daily tasks with enhanced
speed and efficiency across devices whether theyre working on a desktop PC,
smartphone, tablet, or notebook. The apps offer role-based processes that are
personalized for specific user groups in the organization and that are intuitive to
operate. This means that users can complete all their tasks simply and conveniently in
a single userinterface no matter how many different SAP applications they work
with.)
2. Speedy MRP (Use SAP HANA Live to check on material availability and inventory
days of supply in real time at exploded view level. There is also an option to perform
ad hoc simulations. Leveraging these options makes it possible to speed up complex
MRP runs and capacity planning dramatically.)
3. Real-time access to ERP data ( The data aging objects for SAP Business Suite
applications running on the SAP HANA in-memory platform make it

possible to efficiently implement a data aging strategy. This gives end users near-real-
time access to data that is frequently required in day-to-day

operations such as the financial results for previous years ).

New Functionalities:

EHP 7 for SAP ERP 6.0 offers more than 100 new functions and is the first
enhancement package to be optimized for both the SAP HANA database and the
traditional certified databases
The enhancement packages reduce the adjustment effort required for customers who
subsequently migrate their SAP BusinessSuite to the SAP HANA in-memory
platform
SAP EHP 7 also includes numerous new functions for financial accounting, logistics,
human resources, and quality management, as well as cross-application functions and
improvements for SAP Master Data Governance and manager self-service (MSS)

Financial Accounting Functionalities:

1. Reporting Using XBLR Standards ( XBRL is beneficial for reporting in financial

accounting because certain authorities and institutions require enterprises to report
information in this format.)
2. As of SAP EHP7 for SAP ERP 6.0, you could use a prepared enhancement to add
additional account assignments, such as business area, segment, and profit center, that
have not been assigned to past postings, but will have an impact on follow-on
postings such as clearing, dunning charges, interest, and so on.
3. Financial Data SOA (Service-Orientated Architecture)

( You can use this business function to create inbound services for data replication from
Master Data Governance for Financials

(MDG-F) to Strategic Enterprise Management and BI-based

Business Consolidation (SEM-BCS). This enables you to distribute the master data for chart
of accounts, accounts including hierarchies, and consolidation units including hierarchies.)

Master Data Governance Financials.

You can use this business function to configure a governance process for your master data in
Financials. The governance of the master data is centralized and is managed by an approval
process. The changes can be replicated in the decentralized systems and are documented at all
times.

4. Master Data Governance Customers, Vendors

With the business function MDG_ERP_CUSTOMER_2, the following data sets are
supported: Business Partner categories Person and Group Business Partner

Relationships (including Contact Persons). With the business function

MDG_ERP_SUPPLIER_3, the following data sets are

supported: Business Partner categories Person and Group Business Partner Relationships
(including Contact Persons).
6. FI-GL (New) Change in Leading Valuation: Business Functions:
FIN_GL_CHNG_LEAD_VAL

In EHP7, SAP added a new business function to change the valuation of the balances,
revenues, expenses,

7.FI-AA (New) Asset Accounting:

Business Functions: FIN_AA_PARALLEL_VAL

In EHP7, SAP introduced parallel valuation via ledger groupspecific postings instead of
using delta depreciation areas. With the pervious new business functions, it is referred to as
New Asset accounting.

Controlling New Functionalities:

1. New roles for internal controller, project planner, and cost center manager in SAP
NetWeaver Business Client software
2. New planning applications for cost center, internal order, and project planning. New
cost estimation application for projects. Entry of planning data by cost center, activity
type, and cost element with planning functions for distribution from year to period.
3. Enhanced express planning
4. New master data applications with change requests
5. New hierarchy maintenance, including inactive hierarchy functions
6. Operational data providers
7. Side panels for additional info on global user invoice transactions

_____

New Asset Accounting EHP7 Functionality and

configuration
With SAP Enhancement Package 7, a new functionality is available in Asset Accounting to
manage Parallel Valuations. The following document contains information about use of this
functionality for a new implementation customer. In OSS Note 1776828 SAP recommends
activation of New Asset Accounting for new customers. To use this solution, prerequisite is
the use New GL Accounting with Ledger Approach. Prior to New Asset Accounting, to
manage parallel valuations one had to use delta depreciation areas, as only one
depreciation area (01) could post to the General Ledger in real time.

With the new solution it is now possible to post actual values to different depreciation areas
in real time. Theres no need for delta postings and delta depreciation areas. In the
following paragraphs I shall attempt to explain the configuration steps involved with an
example of our implementation project.

Before you actually begin implementation of New AA, take a stock of Global Settings related
to General Ledger, particularly Ledgers and Currencies. This will help you ascertain the Chart
of Depreciation settings required in Asset Accounting.
E.g. if you have two ledgers for your Company Code (leading and non leading) there must be
two depreciation areas that post in real time.

Note This is not applicable to Depreciation areas for Investment Support. Also if there are
multiple currencies there must be a depreciation area for each currency. This ensures
consistencies between General Ledger and Asset Accounting sub ledger.

In our case we had:

Ledgers:
o Leading Ledger for Indian GAAP 0L
o Non Leading Ledger for IFRS NL
Additional Currencies:
o Group Currency INR
o Hard Currency EURO

Also we had to implement Investment Support, so additional Depreciation areas were for
created for the same. Also had a separate depreciation area to Income Tax depreciation.
This is what the final Chart of Depreciation looked like:

Now if you didnt have Investment Support in scope, area 51, 59, 71 and 75 wouldnt be
required. Also if Investment Support accounting is not applicable for Accounting Principle
IFRS, area 71 and 75 wouldnt be required.

Once this is sorted the rest of configuration settings are straight forward:

Business Functions: Activate the following Business Functions:

Transaction Code SFW5

o ENTERPRISE_EXTENSIONS EA-FIN
o ENTERPRISE_BUSINESS_FUNCTIONS FIN_AA_PARALLEL_VAL
This will activate a new path in SAP IMG:

Copy the chart of depreciation as usual and define your depreciation areas
Assign each depreciation area to a ledger group.
For Depreciation area 60, define depreciation area 01 as Alternate depreciation area
for account determination
 Specify Area type:

Asset Accounting (New)->General Valuation->Depreciation Areas->Define Depreciation

Areas->Specify Area Type

Specify transfer of APC values:

Asset Accounting (New)->General Valuation->Depreciation Areas->Specify Transfer of APC Values

Here we define the reference depreciation area that provides values to other depreciation areas. Depreciation
areas that dont post in real time must takeover APC and depreciation values from a reference depreciation
area.

Specify Transfer of Depreciation Terms

Asset Accounting (New)->General Valuation->Depreciation Areas->Specify Transfer of Depreciation Terms

Depreciation Area Currencies

Asset Accounting (New)->General Valuation->Currencies->Define Depreciation Areas for Foreign Currencies

Specify the depreciation areas currency for your company code(s).

Activate New Asset Accounting

Asset Accounting (New)->New Asset Accounting: Preparation and Activation-

>Check Prerequisites for Activating Asset Accounting (New)

Asset Accounting (New)->New Asset Accounting: Preparation and Activation->Activate Asset Accounting (New)
 Technical Clearing Account

To enable parallel postings to different ledgers system uses a technical clearing account for
Asset acquisition and Investment support postings. This is required from a technical purpose
and the balance of this account is always zero after each posting.

See an example of integrated posting with technical clearing account at Example 1:

Acquisition, Integrated Posting Asset Accounting (FI-AA) (New) SAP Library.

The technical clearing account must be a reconciliation account for assets and it cant be
used in account determination for Asset Accounting (for example, tables T095, T095B, T095P)

Rest of the configuration remains unchanged. You define your asset classes, account
determination, depreciation keys etc. as usual.

An example of Acquisition posting (without investment support)

Integrated posting in different ledgers:

Area 01 Ledger 0L-

Area 60 Ledger NL
Separate documents are generated for the two postings:
References:

1. OSS Note 1776828

2. Release Notes for EHP7
3. Various Help.sap.com pages on New Asset Accounting

I guess you know: Enhancement Package 8 for SAP ECC 6.0 is different, from our technical
perspective of Software Logistics.
These are the aspects that I am aware of:

1. EHP 8 is an upgrade
SAP Business Suite 7 Innovations 2016 with SAP ECC 6.0 EHP 8 (6.18) is
based on SAP NetWeaver 7.50 (NW 7.50), and the procedure is load-based. It
is not an update in the sense of the Enhancement Packages (EHPs) until now.
It is an upgrade, as the shadow system is created from DVDs, not cloned from
the customer system (compare my outdated SCN blog on shadow system:
SUM: introduction to shadow system).
You may check the following SAP notes: SAP Note 2318321, SAP Note
530335.
Note that with SUM 1.0 SP 19, the Report
RSUPG_TADIR_COMPONENT_CHECK (attached in SAP Note 2318321)
will be executed by SUM automatically.
(In the future, the handling concerning DVDs will be simpler: Simplified
Download for SUM Procedure.)
2. Unicode only
NW 7.50 is unicode-only, and SAP has announced long time ago that the
successor of SAP NetWeaver 7.40 will only by offered as Unicode system,
and that the path to the successor of SAP NetWeaver 7.40 can only be reached
from a unicode system what was that again? I mean to say that you have to
start from a Unicode system to reach NW 7.50 (and to reach EHP 8). For NW
7.50, we do not have a non-unicode kernel. But the SUM procedure to create a
shadow system requires the non-unicode kernel for a non-unicode source
system. Further one, there is no non-unicode load for the load-based procedure
for NW 7.50.
3. ASCS split
The SUM will create a separate ASCS instance for the following condition (all
have to apply together):
1. The SUM maintenance activity (like an upgrade) is targeting NW 7.50
2. The source system does not yet has a separate ASCS.
3. The source system has more than one instance

If the source has just one instance, no specific handling happens. Note that the SUM does not
explicitely mention this behavior on the dialog, only in the log files. For SUM SP 17, I can
imagine that the ASCS split could be offered as option for target 7.40 as well just an idea.
[Added on 2016-07-11] Note that with SUM SP 17, for a target based on 7.40, SUM will
offer to (optionally) split ASCS.

Attention
important side effect for DMO and the (optional) use of an Additional Application Server
(AAS, fka DI): if your target for DMO is 7.50, and your system does not yet has an ASCS,
and you decide to run the SUM on an AAS (e.g. for better performance), then the SUM will
create the (required) ASCS on the AAS. And (strange but true): from the perspective of the
SUM running on AAS, the PAS (CI) is handled as a remote dialog instance. DMO cannot
handle and cannot start remote instances (other than ASCS), so your CI will not come up at
the end of the SUM procedure