Beruflich Dokumente
Kultur Dokumente
FINANCE
1. Currency types in S/4 FINANCE
2. Extension ledger
Click the New Entries button and create the entries as highlighted
in Figure 1. In this example, extension ledgers E1 and Z1 are created.
6. Inventory Valuation
8. Account-Based CO-PA
In SAP S/4HANA, the material number field length was extended from
18 to 40 characters.This change was first implemented in SAP
S/4HANA, on-premise edition 1511 and affects this release and higher
releases.
Extending the material number on the database means that the field
length of the MATNR field on the database has been extended from 18
to 40 characters. This has been done in all tables (and all fields within
the tables) in which a material number can be stored.
- The group view considers the group as a whole. The processes are
valued by eliminating intercompany/inter-profit center profits.
With the merge of FI and CO into the Universal Journal, a new approach
for parallel valuations was implemented:
Parallel delta versions for actuals in Controlling are used for statistical
line items updating table COEP only. All other actual line items
updating table ACDOCA use the new data model.
SAP Fiori provides all business roles in real time on compatible hand
devices. It offers business roles on easy to use functions, simple with
unmatched responsiveness on desktop, smartphones and Tablets.
The app is for desktop only. Smart phone or table is not supported.
The app must be connected to the customizing client of a testing
system, do not connect the app to a production client.
Up to now, the app supports G/L account assignments in the
following areas:
1. MM: The app supports all transaction keys under the transaction
group RMK, which includes T-code OBYC, with customizing
tables T030R, T030B and T030.
2. SD: The app supports 4 applications: V, VB, VC & VD. It covers
T-code VKOA, OV64, OV77 and OV87. Condition tables within
SAP and customer namespaces are all supported.
3. FI-GL. The app supports the following processes in FI-GL:
The Object based plans that for Projects, Sales orders, Productions orders will write into
ACDOCP in future.
ACDOCA and ACDOCP will bring the actual and the planning together all in one single source
of truth.
NEW GENERAL LEDGER
ACCOUNTING POWERED BY
SAP HANA
Smart Financials requires New General Ledger Accounting. ( The classic General Ledger
Accounting is not part of Smart Financials)
The data model of new General Ledger Accounting was simplified for the integration with SAP
Accounting powered by SAP HANA. All data in new General Ledger Accounting is stored in
document tables and line item tables. The system calculates the aggregated data in the relevant
views.
The new data model eliminates the need to save redundant data (for example, in totals tables or
index tables). Furthermore, inconsistencies can no longer arise between FI documents and totals
tables.
BSIS
BSAS
GLT0
FAGLFLEXT
FAGLBSIS
FAGLBSAS
Tables GLT1 and GLT2 are no longer available for new General Ledger Accounting within SAP
Accounting powered by SAP HANA. Consequently, ledgers for these tables are no longer
updated and can no longer be processed or analyzed in the Special Purpose Ledger (FI-SL). If
you still need to use one of these ledgers, contact SAP Development Support (message
component FI-SL-SL). The new data model allows you to continue to use programs to access the
database as before. This also applies for user-defined programs.
The following functions are no longer available with SAP Accounting powered by SAP HANA:
Classic General Ledger Accounting is no longer available due to the changed data model within
SAP Accounting powered by SAP HANA. If you have previouslybeen using classic General
Ledger Accounting, you can transfer your data to new General Ledger Accounting during the
migration to SAP Accounting powered by SAP HANA.
Since Customizing for classic General Ledger Accounting is no longer available with SAP
Accounting powered by SAP HANA, the following Customizing activities have been included in
Customizing for new General Ledger Accounting:
As of SAP Accounting powered by SAP HANA, new General Ledger Accounting offers the
following new functions and changes to existing functions (compared against SAP enhancement
package 7 for SAP ERP 6.0 : SAP Accounting powered by SAP HANA.
Balance Carryforward: In addition to the functions that were previously available, the program
for carrying forward balances now enables you to initialize data carried forward previously when
you want to repeat a balance carryforward. Furthermore, you can save results lists and then use
the program to display them at a later point in time.
Integration with Materials Management: Account Determination for Cost of Sales, You can
specify that the cost of sales is posted to different accounts on the basis of the cost component
assignments. For more information, see the relevant release note for Controlling.
Data Aging: The previous functions for archiving accounting documents has been replaced by
data aging. For more information, see the release note for data aging.
SAP Fiori mobilizes some of the most common business functions like Workflow approvals,
information lookups and self service tasks. It is collection of apps with a simple and easy to use
experience for broadly and frequently used SAP software functions that works seamlessly across
devices Desktops, Tablets, Smartphones and Smart Watches.
SAP Fiori is the new user experience (UX) for SAP software. It applies modern design principles
for a completely re-imagined user experience across devices and deployment options. SAP
Solutions, such as the SAP Business Suite (SAP S/4) applications, user SAP Fiori UX to provide
a personalized and role based user experience for enterprise-wide engagement across lines of
business.
While updating a single standalone SAP Fiori App is quite straight forward complexity rises with
increasing number of user cases, applications, custom enhancements, etc. on productive system
landscapes. This guide provides an overview of major challenges and areas of concern.
There are 500+ role-based apps, that apply the SAP Fiori UX providing enhanced user
productivity and personalization for customers using SAP S/4HANA, SAP Simple Finance and
SAP Business Suite on any database.
SAP Fiori UX supports a variety of roles in lines of business include HR, Finance,
Manufacturing, Procurement, and Sales.
SAP UI5
SAP NW Gateway
Software layer for SAP ERP that exposes SAP data using OData (web) protocal
Transnational Apps
Fact sheets
Analytical Apps
Transnational Apps
These apps let you perform transactional apps, such as creating leave request for an employee.
They represent simplified views and interaction with existing business processes and solutions.
They run best on an SAP HANA databases with acceptable performance.
For the transactional apps, the ABAP front-end server contains the UI layer with the product-
specific UI components for the products (for example, ERP Financials (ERP-FIN), Customer
Relationship Management (CRM), Supply Chain Management (SCM)) as well as the
infrastructure components. The infrastructure comprises the central UI component with the SAP
UI5 control library and the SAP Fiori launchpad as well as SAP Gateway with the OData
enablement.
The front-end components have access through a trusted RFC connection to the ABAP back-end
server containing the business logic. The underlying database can be an SAP HANA database, or
any database, and is accessed from the back-end server.
Fact sheets
These apps display contextual information and key facts about central objects used in business
operations. From an architectural perspective major differentiators to transactional apps are:
Fact sheets run only on a SAP HANA database / Suite on Hana system (no support of any DB)
Directly accesses search engine on the backend server via INA search protocol
Requires reverse proxy (SAP Web Dispatcher) handling the request to different systems
Analytical Apps
These apps provide role-based insight into real-time operations of a business by collecting and
displaying key figures directly in the browser. Analytical apps combine the data and analytical
power of SAP HANA with the integration and interface components of SAP S/4. They provide
real-time information on large volume data in a simplified front end for enterprise control. With
analytical apps, most important key performance indicators (KPIs) can be closely monitored in
real time and allow immediate reaction on changes in market conditions or operations. From an
architectural perspective major differentiators to transactional apps are:
Requires reverse proxy (SAP Web Dispatcher) for handling the requests to the different
systems.
SAP Fiori User Roles
SYSTEM CONVERSION TO
S/4HANA FINANCE
For detailed information on the conversion process, please follow the below mentioned SAP
SNotes.
S Notes
2390881 Consistency checks before the installation during the migration to Asset Accounting (new)
Composite SAP Notes: Enhancements and message texts for the program
2333236
RASFIN_MIGR_PRECHECK
Release Scope Information: SAP Simple Finance add-on 1.0 for SAP Business Suite powered by
1968568
SAP HANA
Ledger approach and Asset Accounting (new): Non-calendar fiscal year variant for parallel
2220152
valuation
2023763 SFIN: check old dc engine and parallel currency in precheck report RASFIN_MIGR_PRECHECK
Information about adjusting customer-specific programs to the simplified data model in SAP
1976487
Simple Finance
2186803 SAP Simple Finance, OP: Treatment of NewGL tables and customer enhancements
2160045 S/4HANA Finance: Fields of Appends to COEP and BSEG missing in table ACDOCA
2076652 SAP Simple Finance: SAP Note for adjustment of customer-specific programs for aging
2431747 General Ledger: Incompatible changes in S/4HANA compared to classic ERP releases
Preparation of Data
Before starting system conversion, get system ready by performing the following activities:
Check the consistency of your financial data and perform reconciliation between your
accounting components, so the data can be merged correctly in the universal journal entry. In
SAP S/4HANA all line item documents are stored in the universal ACDOCA data table.
Perform period-end closing including the storage of reporting key figures and closing the
posting periods.
Lock the current and previous periods in Materials Management using program RMMMPERI.
Perform closing for periodic asset postings using program RAPERB2000.
Execute the periodic depreciation posting run using program RAPOST2000.
Make sure that all held documents have either been posted or deleted.
If you are already using account-based profitability analysis, perform a delta upload to SAP BW
for all account-based CO-PA DataSources for which you use the delta method.
Document the posting data. Make sure that all carry forward balances are complete and
consistent. To ensure this, carry forward the balances for all currencies and all ledgers.
Archive any data that you no longer need in every day business processes before the
migration.
If you have not been using the new depreciation calculation from the Enterprise Extension
Financials Extension (EA-FIN) you must implement it as part of a separate project.
Activate the new depreciation calculation in your source system. To do so you must activate the
EA-FIN business function.
Perform Pre-Checks
Pre-Checks help you identify the steps you need to take to ensure your system is compatible
with the conversion process.
The Controlling and General Ledger pre-checks provided analyze whether your ledger,
company code and controlling area settings are consistent and can be migrated to SAP
S/4HANA. These Controlling and General Ledger pre-checks are automatically executed when
you run the report R_S4_PRE_TRANSITION_CHECKS.
To run pre-checks for Asset Accounting (FI-AA), please implement the SAP Notes listed in
the collective SAP Note 2333236. The pre-check program for Asset Accounting (FI-AA) is not
included in the central pre-check report R_S4_PRE_TRANSITION_CHECKS. To execute the
appropriate pre-checks for Asset Accounting, please run the report
RASFIN_MIGR_PRECHECK.
Below mentioned screen shot prescribes traditional Inventory management Vs S/4 HANA
Inventory management based on Material ledger.
Actual Costing:
We activate the Material ledger for one or more valuation areas, if the material ledger is active
for a particular valuation area, all materials in the valuation area are valuated using the material
ledger.
But SAP recommends if you activate the material ledger for a plant, you should also activate it
for all the other plants in the company code. This ensures that the accounts in Financial
Accounting and Materials Management are reconciled.
In this activity, you can specify in each valuation area that a planned price is activated as the
valuation price upon the first goods movement in a new posting period as long as the validity
date of the planned price has been reached.
The planned prices are handled by the system with the following priority:
Actual Costing:
Inventory and material movements are generally valuated either at Standard price (S) which is
constant over a period of time or Moving average price (MAP) which gets adjusted (calculated)
automatically based on every Goods receipt or Invoice receipt. Both of these two methods have
their own pros and cons. Actual costing combines the advantages of standard price with
advantages of using MAP.
ML captures all price variances (like purchase price variances, production variances etc) and
allows (as optional period end activity) revaluation of ending inventories at period end and
releases it as standard price (generally) for next period. Actual costing is optional in S/4 HANA.
You can use this setting if you simply want information about the complete actual quantity
structure. You can assign variances between the plan price of the cost center/activity type or
process, and the actual price calculated at period end to the particular cost object at period-end
closing using the function Revaluation at Actual Prices.
Actual consumption is updated in the quantity structure and taken into account for the price
determination.
If you choose this setting, the variances between the plan price and the actual price are adjusted
subsequently. The cost center or the process is then credited and the material associated with the
consumption is debited. In the context of multi-level price determination, these variances can be
rolled up through the production structure up to the finished product in the same way that
material price variances are rolled up.
If you choose this setting, you cannot use the function Revaluation at Actual Prices at period
closing in Cost Object Controlling, as the variances from the cost centers/processes are debited
to the material direct. If you do use the function Revaluation at Actual Prices at period closing,
the cost centers/processes are credited twice and the materials are debited twice.
We have to keep below mentioned points during Migration of Material Ledger Customizing:
Key Points:
The material ledger is required if you are using SAP S/4 HANA Materials Management
Inventory Management (Simplified Logistics).
You need to migrate the material ledger even if you are already using SAP Simple Finance (that
is, you are migrating from SAP Simple Finance to SAP S/4 HANA Inventory Management).
You need to migrate the material ledger even if you are already using the material ledger in your
source system.
SYSTEM CONVERSION TO
S/4HANA FINANCE
For detailed information on the conversion process, please follow the below mentioned SAP
SNotes.
S Notes
2390881 Consistency checks before the installation during the migration to Asset Accounting (new)
Composite SAP Notes: Enhancements and message texts for the program
2333236
RASFIN_MIGR_PRECHECK
Release Scope Information: SAP Simple Finance add-on 1.0 for SAP Business Suite powered by
1968568
SAP HANA
Ledger approach and Asset Accounting (new): Non-calendar fiscal year variant for parallel
2220152
valuation
2023763 SFIN: check old dc engine and parallel currency in precheck report RASFIN_MIGR_PRECHECK
2226973 sFIN: Period scaling does not correspond to the definition AFASL
Information about adjusting customer-specific programs to the simplified data model in SAP
1976487
Simple Finance
2186803 SAP Simple Finance, OP: Treatment of NewGL tables and customer enhancements
2160045 S/4HANA Finance: Fields of Appends to COEP and BSEG missing in table ACDOCA
2076652 SAP Simple Finance: SAP Note for adjustment of customer-specific programs for aging
2105948 Check report for Financials add-on
2431747 General Ledger: Incompatible changes in S/4HANA compared to classic ERP releases
Preparation of Data
Before starting system conversion, get system ready by performing the following activities:
Check the consistency of your financial data and perform reconciliation between your
accounting components, so the data can be merged correctly in the universal journal entry. In
SAP S/4HANA all line item documents are stored in the universal ACDOCA data table.
Perform period-end closing including the storage of reporting key figures and closing the
posting periods.
Lock the current and previous periods in Materials Management using program RMMMPERI.
Perform closing for periodic asset postings using program RAPERB2000.
Execute the periodic depreciation posting run using program RAPOST2000.
Make sure that all held documents have either been posted or deleted.
If you are already using account-based profitability analysis, perform a delta upload to SAP BW
for all account-based CO-PA DataSources for which you use the delta method.
Document the posting data. Make sure that all carry forward balances are complete and
consistent. To ensure this, carry forward the balances for all currencies and all ledgers.
Archive any data that you no longer need in every day business processes before the
migration.
If you have not been using the new depreciation calculation from the Enterprise Extension
Financials Extension (EA-FIN) you must implement it as part of a separate project.
Activate the new depreciation calculation in your source system. To do so you must activate the
EA-FIN business function.
Perform Pre-Checks
Pre-Checks help you identify the steps you need to take to ensure your system is compatible
with the conversion process.
The Controlling and General Ledger pre-checks provided analyze whether your ledger,
company code and controlling area settings are consistent and can be migrated to SAP
S/4HANA. These Controlling and General Ledger pre-checks are automatically executed when
you run the report R_S4_PRE_TRANSITION_CHECKS.
To run pre-checks for Asset Accounting (FI-AA), please implement the SAP Notes listed in
the collective SAP Note 2333236. The pre-check program for Asset Accounting (FI-AA) is not
included in the central pre-check report R_S4_PRE_TRANSITION_CHECKS. To execute the
appropriate pre-checks for Asset Accounting, please run the report
RASFIN_MIGR_PRECHECK.
B A C K - E N D S E R V E R : A CT I V AT E W E B D Y N P R O A P P L I C A T I O N :
Use transaction SICF and make sure that the ICF service for the Web Dynpro application is
activated.
B A C K - E N D S E R V E R : A S S I G N R O L E W I T H ST A R T A UT H O R I Z A T I O N F O R
W EB D Y N P R O A P PL I C A T I O N:
The Manage Bank Accounts transactional app provides an overview of your bank accounts in a
hierarchical structure and allows you to maintain bank account master data according to your
organizations business requirements, as shown in
Since the system now writes only one journal entry for all of the components G/L,
CO, AA, ML, one document number is sufficient from a business point of view. The
journal entry consists of a header (BKFP) and items {ACDOCA). The respective
document number (BKPF-BELNR/ACDOCA-BELNR) must obey the legal rules of
Financial Accounting. As a consequence, the document number is dependent on
the fiscal year and the company code.
CO document numbers have not been year dependent. Material ledger
document ACDOCA numbers have not been dependent from the DOCLN
organizational unit (e.g. company code). ooooo1 Both numbers did not have a legal
ooooo2 relevance. Moreover, ACDOCA has a 6 digit
field for the document line, whereas COEP oo1o82 has only a 3 digit field. This is still used in
001083 many user interfaces and reports. For compatibility reasons, SAP offers a
new 001130transaction number for every 999 documen lines.
The new universal journal entry replaces the Financial Accounting (FI) document and the
Controlling (CO) document with a universal document. A journal entry is created for every
business transaction in one of the following application components:
Controlling (CO)
Here, you make the settings specifying the document type for postings to non-leading ledgers.
Under Define document types for Entry View, you make the document type settings for postings
in the entry view that effect all ledgers and for postings to the leading ledger.
SIMGSIMG_CFMENUORFBFBN1
In this IMG activity you create number ranges for documents. For each number range you
specify (among other things):
You assign one or more document typesto each number range. The number range becomes
effective via the document type specified in document entry and posting. You can use one
number range for several document types. This means you can differentiate documents by
document type but combine them again for filing the original documents, provided you store
your original documents under the EDP document number.
Upgrades: The migration of the ledger Customizing generates a default mapping variant in which
all CO business transactions are mapped to the document type that was entered in the variant for
real-time CO-FI integration.
This is a facility provided by SAP that enables migrated data to be first cleansed in spreadsheets (or
access depending on the data volumes), and subsequently loaded into SAP via predetermined field
mapping. The facility also caters for data transformation where field values can be created from simple
predefined logic. It is the preferred tool for all data migration into SAP. The main benefits are:
Independence from SAP releases, platforms and the kind of data to be migrated.
Independence from SAP releases, platforms and the kind of data to be migrated.
Read data (legacy data in spreadsheet tables and/or sequential files) from a file on a local PC or file
server.
For representing parallel accounting in New asset accounting, you have two scenarios as
mentioned below.
Ledger approach:
1. Different accounting principles or valuation are mapped in separate ledgers, as in new General
ledger accounting. In general, the same accounts are used in the ledgers.
2. The depreciation areas have equal status. Separate documents are posted for each accounting
principle or valuation.
3. For each accounting principle or valuation, the system posts the correct values in real time. The
values that are posted are full values and not delta values.
4. For each valuation, there is always just one depreciation area that posts to the general ledger in
real time and manages APC. For this leading depreciation area, choose the posting option Area
Posts in Realtime. This applies both for the leading valuation and for all parallel valuations. You
can choose which of these depreciation areas, which post to the general ledger, posts to the
leading ledger.
5. One or more depreciation areas represent a valuation. You must assign an accounting principle
uniquely to all depreciation of a valuation. For each valuation, the accounting principle has to be
assigned to a separate ledger group. The ledgers of these ledger groups are not allowed to
overlap.
6. Differences in values in each accounting principle: You can enter documents that are
valid only for a certain accounting principle or valuation. To do so, when entering the
business transaction, you can restrict the posting to the accounting principle or to one or
more depreciation areas.
7. You can assign different fiscal year variants to each type of valuation. (There is a
restriction in this case: The start dates and end dates of the fiscal year variants must be
the same.)
8. Within an asset class, it is possible to make a simple assignment of different G/L
accounts (such as, reconciliation accounts for APC and value adjustments) for each
valuation.
9. If you have defined parallel currencies in new General Ledger Accounting, and you want
to use these currencies in new Asset Accounting, you are required to create for the
leading valuation and the parallel valuations the necessary depreciation areas for each
currency.
10. Managing quantities: In the standard system, depreciation area 01 is intended for the quantity
update. If needed, you can specify a different depreciation area for the quantity update.
However, this has to be a depreciation area that posts to the general ledger. The quantity if it
is to be managed on the asset is updated in the asset master record only when a posting is
made to this different depreciation area.
You can enter a separate fiscal year variant for each depreciation area in Asset Accounting. The
start and end dates of this fiscal year variant have to be the same as the start and end dates of the
fiscal year variant of the company code. As part of the ledger approach, the system also allows a
posting in a representative ledger, to which any fiscal year variant is assigned. The system then
derives the period from the posting date. The depreciation, however, is determined as before
using the fiscal year variant of the depreciation area of the posting.
ACCOUNTS APPROACH:
1. You represent different valuations on different accounts within the same general ledger.
This means that you have to create the same set of accounts again for each parallel
valuation.
3. For each accounting principle or valuation, the system posts the correct values in real
time. The values that are posted are always full values and not delta values.
4. For each valuation, there is always just one depreciation area that posts to the general
ledger in real time and manages APC. The following applies for these posting
depreciation areas:
1. For the leading valuation, choose the posting option Area Posts in Realtime.
2. For the parallel valuations, choose the posting option Area Posts APC
Immediately, Depreciation Periodically.
You can choose which of these depreciation areas that post to the general ledger represent
the leading valuation.
5. There can also be investment support on the liabilities side for the valuations. These
depreciation areas also receive the posting option Area Posts in Realtime for the leading
valuation or Area Posts APC Immediately, Depreciation Periodically for parallel
valuations.
6. One or more depreciation areas represent a valuation. You must assign an accounting
principle uniquely to all depreciation areas of a valuation. For each valuation, the
accounting principle has to be assigned to a separate ledger group. These ledger groups
must always contain the leading ledger as the representative ledger.
7. If you have defined parallel currencies in new General Ledger Accounting, and you want
to use these currencies in new Asset Accounting, you are required to create a depreciation
area for each currency for the leading valuation. However, this is not mandatory for the
parallel valuations.
8. Differences in values in each accounting principle: You can enter documents that are valid only
for a certain accounting principle or valuation. To do so, when entering the business transaction,
you can restrict the posting to the accounting principle or to one or more depreciation areas.
The line item, totals tables and application index tables of General Ledger Accounting (GLT0,
BSIS, BSAS and FAGLFLEXA, FAGLFLEXT, FAGLBSIS, FAGLBSAS)
The totals tables and application index tables of Accounts Receivable and Accounts Payable
(KNC1, KNC3, LFC1, LFC3, BSID, BSIK, BSAD, BSAK)
The line item and totals tables of Controlling (COEP for certain value types, COSP and COSS)
The material ledger tables for parallel valuations (MLIT, MLPP, MLPPF, MLCR, MLCD, CKMI1,
BSIM)
The Asset Accounting tables (ANEK, ANEP, ANEA, ANLP, ANLC)
Replacing these tables with views with the same names ensures the continuation of all read
accesses to the tables mentioned. With the SAP Simple Finance add-on for SAP Business Suite
powered by SAP HANA 2.0, the comprehensive data table ACDOCA is provided, containing all
line item documents from FI, FI-AA, and CO. All postings of these applications are written to
the new table after the installation and migration are complete. SAP Accounting powered by
SAP HANA is based on new General Ledger Accounting (FI-GL (New)) and uses functions such
as ledgers to update a particular valuation, and the document splitting function. If you want to
use SAP Accounting powered by SAP HANA, but were still using classic General Ledger
Accounting until now, migrate the application data for General Ledger Accounting and the
necessary settings for the new Customizing, for example ledgers and integration for Controlling.
However, none of the functions of new General Ledger Accounting such as Parallel Ledgers and
document splitting, are implemented. For Asset Accounting purposes you use new Asset
Accounting in SAP Accounting powered by SAP HANA. During the migration from classic
Asset Accounting to new Asset Accounting in SAP Accounting powered by SAP HANA,