Document number ranges in S/4 HANA sFIN

Document number ranges in S/4 HANA sFIN

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.

2016-04-14_142900

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:

  • General Ledger Accounting (FI-GL)

  • Asset Accounting (FI-AA)

  • Controlling (CO)

    Exception: Costing-based Profitability Analysis (CO-PA)

  • Material Ledger (CO-PC-ACT)

Changes in S/4 HANA sFIN Document types and Number ranges:

2016-04-14_151701

In this activity, you define your document types. Document types are used to differentiate the business transactions and to manage how document are stored. This documentation describes the special procedure for setting up document types for New General Ledger Accounting.

2016-04-14_151825

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.

2016-04-14_152000

SIMGSIMG_CFMENUORFBFBN1

In this IMG activity you create number ranges for documents. For each number range you specify (among other things):

  1. a number interval from which document numbers are selected
  2. the type of number assignments (internal or external)

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.

Integration of Controlling with Financial Accounting:

New Settings for customizing Controlling in S/4 HANA sFIN

2016-04-14_150055

In this activity, you can create new Document types for posting in Controlling, example you can create a document type that you can use for the manual reposting of primary costs.

2016-04-14_150630.jpg

2016-04-14_151033

In this activity, you define a mapping variant that maps CO business transactions to document types. This mapping must be done for all CO business transactions that do actual postings.

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.

2016-04-14_151259

You place your mapping of FI documents to CO transaction / document types here

2016-04-14_151441

Advertisements

Introduction to SAP Fiori

What is SAP Fiori?

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.

Technology behind Fiori?

Here comes my favorite web language “HTML5”

⇒ SAP UI5

‣ HTML5 and JAVA Script UI development framework

‣ Future direction for SAP User interfaces

⇒ SAP NW Gateway

‣ Software layer for SAP ERP that exposes SAP data using OData (web) protocal

Scope of SAP Fiori?

SAP Fiori comes with three major app types,

⇒ 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.

2015-07-15_110109

 ⇒ 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
2015-07-15_111053

⇒ 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:

‣ They require HANA database / Suite on HANA system and XS Engine

‣ Directly accesses HANA XS Engine

‣ Requires reverse proxy (SAP Web Dispatcher) for handling the requests to the different systems.

2015-07-15_111528

2015-07-15_104637

⇒ SAP Fiori User Roles

2015-07-15_104853

Click here to get configuration document of “Configuring SAP Fiori Apps

Parallel Accounting in New Asset accounting powered by SAP HANA

In New asset accounting, you can handle parallel accounting using depreciation areas.

For representing parallel accounting in New asset accounting, you have two scenario’s as mentioned below.

  • Using Parallel ledgers: The Ledger approach
  • Using Additional accounts: The Accounts approach

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.

Different Fiscal Year Variants:

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.

  2. 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 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.

Source:SAP Library

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)

  • Either you already have New General Ledger Accounting active

  • Or when you don’t have New General Ledger Accounting active yet, you can install the Smart Finanicals first. Then you can migrate to New General Ledger Accounting directly and active it there.

2015-03-02_123350

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.

The following tables have been replaced by views:

  • 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:

  • Balance Sheet Planning
  • Reports for comparing planning data and actual data in Profit Center Accounting
  • Destruction of data or deletion of FI documents (Information Lifecycle Management)
  • Average balance ledger

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:

  • Clocing Cockpit: General Ledger Accounting(New) Periodic Processing Closing Cockpit.
  • ReGroup: General Ledger Accounting(New) Periodic Processing Re Classify.

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.