Samuel Blog

What are the steps for integration of FICO with other modules SD, MM etc. ?

Some basic information :

FI-MM: The integration between FI-MM happens in T-code OBYC.

1. When PO is created :

—- No Entry —–

2. When GR is posted

Inventory Account dr (Transaction Key BSX in OBYC)
To GRIR account (T.Key WRX in T-code OBYC)

3. When Invoice is posted

GRIR account Dr.
Vendor account  Cr.

4. Payment made to Vendor

Vendor A/c Dr
To Bank Clearing A/c Cr.

Points to know : Movement Types, Assignment of Movement types to T-keys (T-code OMJJ), Value string (I also need some information on this) , OMWN and OMWB transactions.

—

There is a close integration b/w FI & MM, actually document flows from MM to FI in the following areas such as,

1. Movement Types:

Used to enable the system to find the predefined posting rules determining how the accounts of financial accounting system are to be posted & to update the stock fields in the matrl master data.(Goods Receipt, Goods Issue, etc)

2. Valuation Class:

Assignment of material to grp of gl account, used to determine the gl accounts that are updated as a result of goods movement.

3. Transaction/Event key:

Used to control the storage or filing of documents & assignment of documents.Used to differeniate b/w various transactions such as goods movement tht occur in inventory.

4. Material Type:

Each material should assign mtrl type in mtrl master record used to update whether changes made in qty are updated in material master record & change in value also updated in stock account.

FI-SD Integration: The integration is done in T-code VKOA

1. Sales Order Created

—No Entry—

2. PGI done (Goods issue)

Cost of Goods Sold     Dr (Configured in OBYC GBB T-Key)
To Inventory Account

3. Billing document released to Accounting

Customer Account Dr.
To Sales Revenue Account (ERL T-key in Pricing procedure)

Note : The GL account is assigned to this ERL in VKOA

4. Payment Received

Bank Clearing A/c Dr
Customer A/c Cr.

Points to Know : Good to understand the pricing procedure and how the different transaction keys are used like ERL, ERS etc.

Tips by : Kishore, Balaji.C

财务，财务，呵呵，让我们关心一下给我发工资的部门。某皇帝似的人物牛哄哄的语重心长的俯视着对会计们说，不要做假帐啊。按照中国人的不是什么偏要说什么的特点，我们由此可以知道，财务的任务、终极目标就是做假帐。你反驳道，会计不是财务，财务部是会计。我有说吗？我什么都没说。不管假不假，那是高层建筑，是道；可怜我们这帮下苦力的，so professional地、忠诚而且神圣地研究着各种伎俩以满足传说中的“上面的人”的要求，是术。

拿在手上的是钱、POS机刷的是卡、龙飞凤舞的是支票。若干年前，去超市买二两猪肉回来要在横线本本上记一条，在倒数第三页第四行上写着：××年××日××时于××地购买猪肉二两，花费RMB一元（日记账）。有了这么一个动作，我就能在月光的时候检查一下上个月的工资都跑哪去了。若干年后，科技发达了，我用EXCEL来替换了3毛钱的作业本。为了排序，我还把各种花费分类并且给他一个编码，买酒的记成WINE，买肉的记成PORK，打车的记成TAXI，这样我就可以筛选、排序、求和。呃，人类真伟大，不是吗？某一天，我发现，身边还有很多人和我保持着相同的习惯。想不到这竟然是最原始的会计。

一个人一个帐本，这就是所谓的帐套嘛，各编各的码，就是各有各的会计科目表。中国人记人民币账，美国人记美元账，这就是币种。等到把帐本记满了，换一个新的，把旧的锁起来存档，这不是会计期间么？

朴素归朴素，总的来讲太简单了，东西不复杂人家不买你的，说复杂体现价值。把个体行为放大，你会发现挣钱的方式数都数得过来，但是却有无数种方法把钱花掉，怎么记呢怎么分呢？好在党国给我们方向，定了若干准则下来，我们照着细分就是了。上面说的是科目，SAP总帐（General Ledger）主要管的就是这个，不同的是人家管得是世界500强的财富榜上的，厉害吧。当然，他还包括期间、币种啥的，前提是，要把不管水多深的公司的结构用一些浅薄的代码来表示，而且是树状结构。

OK，架子搭好了，记账吧。记买记卖，应付（对采购行为进行付款，对象同应收）应收（对销售行为进行收款，对象涉及到对谁、多少、何种性质的应收等）；记自己的物品，存货（对自有物品的分类、估价、清查、盈亏处理等）；记大件财物，资产（资产的获得、分类、折旧及其规则等，直到报废）；记钱财和银行的往来，记现金的流动（对账单、Overhead）。

除了被动的记录，我们还可以做一些预测/预算，打算某某时间内要花（收）多少钱，这些钱的来源、去处？于是我们在期初做计划支付、承诺支付，实际发生时的支付可能与计划不一致，或追加或阻挡，待期末我们再来对比查看我们计划的准确不准确。

按照SAP的定义，我上面说的应该就是Finacial Accounting的范畴了。Controlling？不懂！说说自己的看法，我觉得他就是搞“开源节流”中的节流的，不主动，而是被动的记录罢了，记录花费的成本。建个模先：

首先，你要知道你到底要知道那些东西的成本？也就是需要确定你的成本对象。

其次，你要知道谁花掉了钱？也就是成本中心。

第三，你要确定都花了什么钱，也就是成本要素，在SAP中，由初级和次级成本要素之分。

第四，你要搞清楚，某个成本中心花掉了钱，最后这笔消耗是怎么转移到成本对象上面的？也就是成本流。

最后，成本计算出来，你还要知道消耗成本后的获益者，是哪个客户，或者那个渠道，或者那个产品？统称之为获利段。

有了这个模型，然后你要明确：

1，是否：某项支出是否应该记入产品成本或期间费用；

2，区分：如果要记入，应该计入哪一项，即是记入产品成本还是记入期间费用；

3，时段：一个会计期间内，从什么时候开始到什么时候截至的支出需要记入；

4，细分：支出应该细分到何种产品成本、完工品和在产品的费用界限。

接着，我们要当事后诸葛亮了（成本核算是事后措施，对已经发生的费用进行归集和分配的过程）：

1，收集：那些耗费需要记入、应该记到什么地方（是产品成本还是期间费用）

2，截至：本月实际支出和待摊的正确处理，需要做好界限划分

3，分配：横向分配，本月总的费用应该分摊到哪些产品哪些项目中

4，分配：纵向分配，产成品和在产品之间的分配归集

嗯，就这么多。其实也是记账而已，所以，我们仅需要关注这些科目而已（成本核算的相关科目）：

1，基本生产成本

2，辅助生产成本

3，制造费用

4，废品损失

5，营业费用

6，管理费用

7，财务费用

8，待摊费用

9，长期待摊费用

10，预提费用

最后说一句，这些“上面的人”都不关心的，他们只关心报表：资产负债表、损益表、股东权益变动表、现金流量表。所以，干“好”（you know that）是你应该的，干不好屎盆全往你头上扣。

Module Functions:
The module that performs most of the traditional legal entity accounting functions, reporting by company, income statements and balance sheets. This is the module where you will find the A/R and A/P sub-ledgers and their open items along with the Asset Accounting Ledger.

Organizational Elements (Structures):
• Chart of Accounts – contains all account numbers and some general control data.
• Company Code – an independent balancing / legal accounting entity. each company code is assigned to one Chart of Accounts
• Functional Area – Classify operating expenses according to of cost-of-sales accounting by production, admin, S&D marketing, R&D, etc. By breaking costs into functional areas cost- of-sales accounting shows why costs accrue and indicates the economic purpose of the expense.
• Trading Partner
• Operating concern – the central organizational element in profitability analysis. It represents the environment within which a market or (customer defined) segment of the business can be monitored and profitability analyzed. 1:n relation to controlling.
• Controlling area – identifies a self-contained unit for which the management of costs and profits can be performed. Only one chart of accounts is allowed within a controlling area. However,
• (FI-AA) Asset Accounting – Depreciation (both book and tax), net book values, transfers and retirements
Document Posting Principles:
Each posting is in the form of a complete document. It must contain:
• Basic account assignment data (i.e. document date, posting date, document type, posting key, account number and amount.
• Entries must be made in all required fields.
• Debit and credit balances must be equal.
Every document contains a document header and at least two or more line items.
• The header contains information valid for the whole document (i.e. document date and type).
• Line items contain transaction specific data (i.e. posting key, account number and amount).
Document header:
• Document Date is the date that the transaction took place. (Must be on or before the Posting date ?) Posting Date determines the posting period (the system will enter this date if not provided?)
• Document Number is normally assigned b the system from a range predefined for each document type. (Not an input for g/l doc types {S}
• Reference and Document Header Text is descriptive data
• Period is the accounting period. Normally numeric (1 to 16?)
• Document type, a two character alphanumeric field. This field determines the document number range and the valid account types which may be used.
• A df Fixed Assets
• D df Accounts Receivable
• K df Accounts Payable
• R df Logistics (MM & SD)
• S df G/L
• T df Treasury
• W df Material Management
• Z df Sp0ecial purpose
Line Items:
• Posting Key is a two character numeric
• Together with the account number controls posting at item level
• Controls valid account type (D,K,M,A)
• Defines a Debit or credit entry
• Controls fields required optional or suppressed
• Valid FI posting keys
o 01-09 DR Customer
o 11-19 CR Customer
o 21-29 DR Vendor
o 31-39 CR Vendor
o 40 DR G/L
o 50 CR G/L

By Rajagopalan M
———————
ABAPer, mail: abap.community@gmail.com http://abaplearner.blogspot.com

SAP FICO Module

Configuration -Primary configuration considerations:

Once a business has decided to use the SAP FI(Financial Accounting) Module, there are several Configurations prerequisite steps that must be completed.Determining the organizational structure is one of the first steps in setting up the business functions in SAP as well as your reporting requirements.

The Organizational structure is created by defining the organizational units consisting of the following:
Client
Company
Company Code
Business Area

Client is the highest unit within an SAP system and contains Master records and Tables. Data entered at this level are valid for all company code data and organizational structures allowing for data consistency. User access and authorizations are assigned to each client created. Users must specify which client they are working in at the point of logon to the SAP system.

Company is the unit to which your financial statements are created and can have one to many company codes assigned to it. A company is equivalent to your legal business organization. Consolidated financial statements are based on the company’s financial statements. Companies are defined in configuration and assigned to company codes. Each company code must use the same COA( Chart of Accounts) and Fiscal Year. Also note that local currency for the company can be different.

Company Codes are the smallest unit within your organizational structure and is used for internal and external reporting purposes. Company Codes are not optional within SAP and are required to be defined. Financial transactions are viewed at the company code level. Company Codes can be created for any business organization whether national or international. It is recommended that once a Company Code has been defined in Configuration with all the required settings then other company codes later created should be copied from the existing company code. You can then make changes as needed. This reduces repetitive input of information that does not change from company code to company code as well as eliminate the possibility of missed data input.

When defining company codes, the following key areas must be updated:
Company Code Key- identifies the company code and consists of four alpha-numeric characters. Master data and business transactions are created by this key.
Company Code Name- identifies the name of the business organization within your organizational structure.
Address- identifies the street address, city, state, zip code for the company code created. This information is also used on correspondence and reports.
Country- identifies the country to which your business is based. Country codes within SAP are based on ISO Standards.
Country currency- identifies the local currency for the company code that you have defined.
Language- identifies the language to be used for you company code and is also used for text in your documents. SAP unlike other applications, offers over thirty languages including EN( English) , ES (Spanish), FR (French), DE (German), EL (Greek), IT(Italian), AR( Arabic), ZH (Chinese) , SV (Swedish) , and JA (Japanese) to name a few.

More FI configuration considerations:

Business Area, COA, GL, Fiscal year and Currencies

Business Area is optional and is equivalent to a specific area of responsibility within your company or business segment. BA (Business Area) also allows for internal and external reporting.

Another configuration requirement for set-up in SAP are the Basic settings consisting of the following:
Chart of Accounts(COA)
Fiscal Year Variants.
Currencies

The COA(Chart of Accounts) lists all General Ledger accounts that are used by the organization. It is assigned in configuration to each company code and allows for daily General Ledger postings.

The General Ledger accounts are made up of such data as account number, company code, a description of the account , classification of whether the account is a P & L Statement Account or a Balance Sheet Account.

Control data of the GL Account is where currency is specified, Tax category (posting without tax allowed) , marking the account as a reconciliation account ( e.g. Customer, Asset, Vendors, Accounts Receivable) or not.
Marking the G/L Account as a “reconciliation” account allows for postings to an Asset Account ( for example) as well as automatic update to the G/L Account.

Configuration prevents direct postings to reconciliation accounts thereby assisting in maintaining integrity of the data.
This allows reconciliation between the sub-ledger and general ledger to always be guaranteed.
Within the General Ledger control data , you can also designate whether line item display is possible in the account. The system then stores an entry per line in an index table which links back to the account. (Display of line item details are then available for reporting purposes ,etc.)

Open Item Indicators can be set on the G/L Account allowing for better management of open items. Examples include: Bank Clearing Accounts, GR/IR Clearing Accounts, Payroll, etc.
Fiscal Year configuration is a must and can be defined to meet your company’s reporting periods whether Fiscal (any period combination that is not calendar) or Calendar( Jan-Dec).
Posting Periods are defined and assigned to the Fiscal Year.Within the periods you specify start dates and finished dates.
SAP allows for 12 posting periods along with specially defined periods that can be used for year-end financial closing.
Currencies are another basic configuration setting requirement which defines your company’s legal means of payment by country.
It is recommended that all Currency set-ups in SAP follow the ISO Standards.
The ISO Standards ensure Global conformity across businesses worldwide utilizing SAP.
Contents taken from SAP In Fico.