вторник, 14 июня 2016 г.

SAP FI-AA, basic configuration guide

It will be a very high level explanation. Basically there's only one SAP training for FI-AA configuration, which is AC305. Just attending this one single course should be enough for understanding the module. 

For sure, there should be new updates for S/4 HANA, because you might probably know that this new S/4 HANA Finance changed the concept of FI-AA module a lot, which I would like to cover a little bit later. But now there's no more ANLP, ANEK, ANEA, ANLC tables any longer (if you ever experienced writing a logic for calculating ,for instances, cumulative depreciation, then you'd probably know how complicated this can be with all those tables). Now there's only one table for line items, which is ACDOCA. Well, let me try to cover the topic later, when I feel more encouraged to do so.

So if you're about to start FI-AA implementation, then here is the list of steps you might need to accomplish: 

(1)  Assumption is that you’re done with As-Is part of the program;

(2)  Organization structure: Chart of Depreciation. It is maintained according to business needs, whether they want to have IFRS, local accounting standards, tax depreciation area, revaluation depreciation areas, and maybe they need depreciation areas in different currencies and with some business specific accounting rules and needs, all together. All that is getting maintained by copying some SAP standard depreciation area into your new, company code specific one, and then you simply add/delete/edit depreciation areas in newly created depreciation area. So you go to IMG/SPRO:

Financial Accounting (New) →Asset Accounting →Organizational Structures → Copy Reference Chart of Depreciation/Depreciation Areas → Copy Reference Chart of Depreciation or EC08 t-code.

In order to configure depreciation areas into newly created depreciation plan, go to:

Financial Accounting (New) →Asset Accounting →Organizational Structures → Copy Reference Chart of Depreciation/Depreciation Areas →Copy/Delete Depreciation Areas or OADB t-code.

What else.. you will have to define whether depreciation area posts APC to G/L in real time, or periodically (OABC t-code), how depreciation is getting posted to G/L, or maybe there’s no depreciation posting happening and it is just informative display of depreciation values (OABD t-code) and etc. and etc.

Next what you’re doing is, assigning newly created depreciation plan to company code. Depending on organization structure of the company, there can be lots of company codes, with their own accounting principles, due to geographical dimension, then you will be maintaining lots of depreciation plans for each company code, and assign them by the following menu path:

Financial Accounting (New)  →Asset Accounting  →Organizational Structures  →Assign Chart of Depreciation to Company Code or OAOB t-code.
Organization structure: Asset Classes. This one is pretty simple, normally accountants already have asset classes/groups they’re using in legacy system. So on As-Is part of the project, you already know how many classes/what are the names of asset classes and etc. When maintaining asset class, you will have to start from:
a)     Configuring account determination directory (based on which integration with General Ledger will be maintained next);
b)     Screen layout groups (suppose, different asset classes, have different requirements for statuses of fields on asset master data level);
c)     Number range of asset class (can be external/can be internal, depending on business requirements) via AS08 t-code;
Centralized t-code for maintaining asset classes is OAOA, which can be accessed by following SPRO menu path:
Financial Accounting (New) → Asset Accounting → Organizational Structures → Asset Classes→ Define Asset Classes

(3)  Master Data:

You’ve already created screen layouts for asset classes on step above. Then you probably are in need of configuring statuses of fields on tabs level and etc. (you might need to check for AOLA and AOLK t-codes in order to proceed). Also there’s separate screen layout that needs to be defined for depreciation... There are several so called blank fields, which can be used for whatever purposes you have. Check for ANLA-GDLGRP. Asset different dimensions, tax groups, and things like that can be stored here. These fields are informative, and good to have them for different reporting purposes. Besides, there’s nothing much to be said here.. So let’s continue with next step.

(4)  Business transactions: such as acquisitions, write- off, asset transfer. There’s a list of standard acquisition types that are already there, but if you need something specific, then you should go by the following menu path:
Financial Accounting → Asset Accounting→ Transactions → Acquisitions → Define Transaction Types for Acquisitions or AO73 t-code. Then there should be integration with G/L configured via AO90 t-code, or by the following menu path: Financial Accounting→  Asset Accounting → Integration with the General Ledger → Assign G/L Accounts. While maintaining Integration with G/L for each asset class, on step (2) of current guide, you might noticed that there is single field, where you should put precise G/L account for asset acquisitions. But, suppose, you want different G/Ls to be used for acquisition of same asset class, depending on transaction type (like, for instance, you want acquisition G/L 1000 to be used for transaction type 100, G/L 2000 for acquisition type 110 and etc.) This can be done via small user- exit in GGB1. Create some Z* table, write the logic of user exit so that, on line items level:
If ANLA- ANLKL= ‘A01’ and BWASL= ‘100’, then KTANSW= ‘1000’
Or something of a kind.
Same goes with write- offs- transaction types, integration with G/L. Nothing complicated.
Regarding transfer, there should always be two types of transaction types configured for asset transfer: for old assets and for newly acquired ones. Also I’ve highlighted one small thing about asset transfer Enjoy t-code by the following topic in my blog: http://autumnmoodpushkin.blogspot.com/2016/06/sap-fi-aa-asset-values-transfer-t-code.html
Capitalization of AUC- integration with CO, or Investment Management, depending on design of your ERP system, or you can also do it in FI-AA itself.

(5)  Period –End closing: Depreciation run (monthly, yearly and etc). Depreciation keys are specified by the following menu path:
Financial Accounting → Asset Accounting→ Depreciation→ Valuation Methods→ Depreciation Key→ Maintain Depreciation Key or AFAMA t-code. These keys are assigned to asset classes in OAYZ t-code. Depreciation run program is RAPERB2000. What else is here.. Depreciation posting is done in real time only in one single depreciation area, rest are getting updated in G/L periodically.

(6)  Data migration: master data is happening in both iterations, first is, you create new-old asset master data via AS91 t-code, and afterwards, you upload all of the asset values via AS92 t-code. This can be done via LSMW, via batch input with help of ABAP developer and etc. LSWM tool is quite easy to use here. I will be uploading LSMW guide a little bit later.

(7)  Finally, set the status of the company code as ‘Production’ and that’s pretty much about it.













воскресенье, 12 июня 2016 г.

SAP, Romanian Intrastat Declaration, legal requirement

Starting from 2015, according to legal requirement, following new fields were supposed to be added into Intrastat report for Romania for dispatches:



(1) VAT registration number of the customer;
(2) Country of origin

This legal requirement was released with OSS note 2119495.


Screen above is before OSS note implementation.
After implementing the note, VAT registration number gets updated with proper values from KNA1-STCEG.

But second part of legal requirement was missed from the OSS. Most probably it was added with further additions to 2119495, but back then, due to urgency, we had to manually add Country of origin field both in:

- screen layout of /CEECV/ROM;
- report structure,

by copying standard Intrastat report into Z* report. 

ps: we've added logic for fetching data from EIPO-HERKL, because on materials master data level, 'Country of origin' field is not mandatory, and was missing for most of the materials. 



SAP, FI-AA, asset values transfer t-code

Since release 4.6C, most of the transactions in FI-AA were replaced with Enjoy transactions, such as ABUMN, ABT1N, ABZON, AFABN and etc. and etc.
There's one small thing about Asset transfer t-code ABUMN. This Enjoy transaction doesn't allow to edit asset values on depreciation areas level.

Suppose you need to do following asset transfer transaction:

Asset A:
      Net Book Value   Cumulative depreciation  
01          100                          75
10           95                           70

You need to do partial transfer of asset value on another, newly created asset B.

What you want to do is:

Depreciation area 01:

Posting key                   Amount
      75           Asset A       60
      40           G/L             60
      70           Asset B       60
      50           G/L             60

Depreciation area 10:

Posting key                   Amount
      75           Asset A       55
      40           G/L             55
      70           Asset B       55
      50           G/L             55

This kind of operation is not possible with ABUMN.

This is due to design of Enjoy transactions, which is explained in OSS note 370530 - Functions in new Enjoy transactions.

Extract from the OSS 370530 on reasons:

Reason and Prerequisites:
1. This problem is caused by the program design: The Enjoy transactions are designed to cover the features required by a majority of users every day. Therefore, other functions are provided by the previous transactions to keep the Enjoy transactions as simple as possible in the application.
2. Release planning: We plan to enhance the Enjoy transactions step by step and add some of the previous functions. However, we do not yet know which functions will be available in the Enjoy transactions in which release.

So basically if your roles contain only access to Enjoy t-codes, you might need to add ABUM t-code in FI-AA roles, and proceed with executing transaction described above, separately for each depreciation area.