Professional Documents
Culture Documents
SAP is an acronym for Systeme, Anwendungen, Produkte der Dataenverarbeitung, in German, meaning Systems,
Applications, and Products in Data Processing. Founded in 1972, SAPwith its headquarters in Walldorf, Germany
is the global market leader in collaborative, inter-enterprise business solutions (i.e., business software). SAP employs
close to 40,000 employees worldwide, with more than 100,000 installations in about 40,000 companies in 120 countries.
More than 12 million people use SAP on a daily basis. There are more than 20 industry-specific Industry Solutions,
known commonly as IS (IS-Oil, IS-Retail, IS-Bank, etc.).
2. Tell Me More About (The History Of) SAP.
SAP was founded by five former IBM employees, in 1972, to develop a standard business application software,
with the goal of processing business information in real-time. The company, SAP GmbH, was started in
Mannheim, Germany.
During 1973, the company released its first financial accounting software, R1 (the letter R stands for RealTime Processing).
In the late 1970s, SAP R/2 was released with IBMs database and a dialogue-oriented business application.
R/2 was further stabilized during the early 1980s and the company came out with a version capable of
processing business transactions in several languages and currencies to meet the needs of its international
clientele.
SAP GmbH became SAP AG in 1988. Later on, the company established subsidiaries in countries such as the
United States, Sweden, Denmark, and Italy.
The 1990s saw the introduction of SAP R/3, with client-server architecture and GUI, which ran on almost any
database, and on most operating systems. SAP R/3 heralded a new era in enterprise computing, moving from a
main frame to a 3-tier architecture (Database->Application->User interface), which became the new industry
standard.
By 1996, the company had more than 9,000 installations worldwide. By the end of the 1990s, SAP had
introduced the e-commerce enabled mySAP suite of products for leveraging ever-expanding web technology.
SAP began the twenty-first century with the Enterprise Portal and role-based access to business information.
Explain how mySAP ERP Financial is Better/Different than R/3 Financial Accounting.
mySAP ERP Financials is built on the NetWeaver platform, which is the foundation for service-oriented business
solutions, for deploying financial processes at a faster pace. Irrespective of the business type, mySAP ERP Financials is
designed to support financial accounting requirements to provide a single complete platform to achieve excellence in
accounting, performance management, financial supply chain, and corporate governance. The features include:
Performance Management
mySAP ERP Financials provides a single solution for the entire life cycle of Corporate Performance
Management by delivering real-time, personalized measurements and metrics to improve business insight and
productivity of non-technical users. Executives, managers, and business workers will now have access to
information such as business statistics and Key Performance Indicators (KPI) presented in the context of
business tasks for better insight and faster decision making. mySAP ERP Financials encompasses:
Risk management
Financial analytics
Corporate Governance
With a set of applications and tools, mySAP ERP Financials assists in meeting the specific requirements of
todays financial regulations such as the SarbanesOxley Act. You now have an intuitive mechanism to collect,
document, assess, remediate, and attest to internal control processes and safeguards to ensure transparent
business activity. By configuring controls and defining rules and tolerances for your business, you can easily
customize internal processes for security, reporting, and error prevention. In addition, you can now document all
your internal control processes and make them visible to corporate executives, auditors, and regulators.
Provides the tools to help you manage your financial supply chain and cash-flow cycle more effectively, through
end-to-end process support of:
o
Credit Management
Collections Management
Dispute Management
Bank Relationship
Database Layer
Application Layer
Presentation Layer
In a 3-tier Client server model, all the above three layers run on three different machines.
The Database Layer consists of an RDBMS (Relational Database Management System), which accepts the database
requests from the Application Layer, and sends the data back to the Application Layer, which in turn passes it on to the
Presentation Layer.
The Application Layer or the server interprets the ABAP/4 programs, receiving the inputs from them and providing the
processed output to them.
The Presentation Server or Presentation Layer is what is installed on the typical workstation of a user. This is nothing
but the SAPGUI, which when started provides the user with the interface of SAP R/3 menus. This interface accepts the
inputs from the user, passes them on to the Application Server, processes the inputs and sends back the output. If
database processing is required, the Application Server sends the details to the Database Layer, receives the data, and
then processes it at the Application Layer level and sends back the output to the Presentation Layer where the SAPGUI
may format the data before displaying it on the screen.
Integrated with FI-GL, FI-AA, FI-TR, MM and SD, this submodule manages customers and receivables, and
integrates with SD. It is well-known for credit management functionalities and the dunning program.
77. Name the Submodules Within FI, from Which FI-GL Gets Simultaneous Postings.
Multi-currency capability
Integrated with FI-GL, FI-AA, FI-TR and MM, this submodule manages vendor transactions by linking with
material management, asset accounting, travel management, etc. Notable is the payment program for making
payments to vendors.
Name the Submodules Within FI, from Which FI-GL Gets Simultaneous Postings.
Multi-currency capability
SAP FICO is also mentioned as SAP FI/CO, where FI stands for Financial Accounting and CO stands for Controlling,
now referred to as Management Accounting. There are two target groups that use accounting information:
1. External users: These users typically require information that conforms to legal requirements. This data is
managed in the application component FI. Groups that would fall under this category are the federal
government, state governments, financial institutions, and insurance providers.
2. Internal users: These users come from all levels within the company. They need information for the internal
operations of the company. This information is contained in the application component CO.
The FI module is used to monitor and review the financial statements of a given entity. Financial reports used for
external reporting purposes (such as balance sheets, profit and loss calculations, and cash flows) are created in FI.
These external reporting requirements are based on the varying legal requirements set by the relevant financial
authorities, usually prescribed through general accounting standards such as Generally Accepted Accounting Principles
(GAAP) or International Accounting Standards (IAS). The FI module is called external accounting because it focuses on
external reporting.
The application component CO contains all the functions for effective controlling of cost and revenue of an entity. CO
covers all aspects of management. It is management oriented and management driven. It offers a broad spectrum of
tools that can be used to compile information for the company management, which greatly exceeds that required by law.
The FI module comes with the following submodules. You will learn more about sub-modules later in this book.
The General Ledger (FI-G/L) records all relevant accounting transactions from a business point of view in the G/L
accounts. In order to retain a clear overview, the G/L often contains collective postings. In such cases, the information
posted is displayed in more detail in the subsidiary ledgers, which provide their information to the G/L in summarized
form.
Accounts Payable (FI-AP) records all financial transactions with your vendor. This module often gets it data from
procurement or Materials Management (MM).
Accounts Receivable (FI-AR) records all financial transactions for dealings with customers. Much of its data is obtained
from Sales and Distribution.
Asset Accounting (FI-AA) records all accounting transactions relating to the management of assets starting from
acquisition of assets to the sale or scrap of an asset. This submodule interacts with FI-AP, FI-AR, and G/L of FI
modules, as well as MM modules.
Travel Management (FI-TM) manages, calculates, and supports travel costs, travel planning, and travel expenses. This
submodule is tightly integrated with SAP HR and FI-AP because employees in SAP are treated as vendors.
Bank Ledger (FI-BL) supports the posting of cash flow, cash payments, and cash receipts.
All transactions posted to G/L expenses and revenue account directly or indirectly flow to controlling. Similarly, when
cross object transactions happen between controlling objects, the system creates and FI posting. Figure 2.1 shows data
flows between various submodules of FI.
Like FI, CO covers following submodules. However, we will cover those in more detail later in the book.
Cost and Revenue Element Accounting [CO-OM-CEL] is part of Overhead Cost Controlling. It provides classification of
transaction items. These transactions are captured in various cost objects, such as a cost center or an internal order,
depending on their cost or revenue element.
Cost Center Accounting (CO-CCA) is used for cost collection and provides information about where costs are incurred
in your organization.
An Internal Order (CO-IO) is another kind of cost object used for a wide variety of purposes to capture costs and, in
some cases, revenues within a controlling area.
Product Costing (CO-PC) takes care of all aspects of a product, from planning to tracking of costs. This submodule
consists of following components:
Actual Costing
If you are looking for multidimensional reporting tool, then Profitability Analysis (CO-PA) is the best solution. Through
profitability analysis you can analyze market segments and profitability measures.
The questions are arranged into several areas within FI, including:
Company
Company codes
Fiscal year
Posting period
Currency
Exchange rate
Tax
these after the business is activated. It is also necessary that you restrict the access to these structures through
appropriate authorization profiles. Remember to define only the required structuresnothing more, nothing less!
Segment (optional)
You will be defining these units under SAP Customizing Implementation Guide>Enterprise
Structure>Definition>Financial Accounting (Version SAP ERP/ECC6) (Figure 1.1).
Figure 1.1: FI Organizational Units
Figure 1.4: Options to Define a Company Code
6 WHAT NEEDS TO BE DONE IF YOU DEFINE A COMPANY CODE BY A COPY FUNCTION?
When you copy an existing company code, all the company code-specific specifications of the source (From Company
Code) are copied to your new company code target (To Company Code) (Figure 1.5).
Figure 1.6: Define a Company Code (with the "Edit Company Code Data" Function)
Once you create the new company code using this option, then you need to maintain the global parameters using
the Transaction Code OBY6.
8 HOW DO YOU CHANGE THE COMPANY CODE KEY?
Use the "Replace" function in the Transaction Code EC01 to change the company code key. But this is only possible if
no postings have been made in the company code that are to be replaced with the new company code key.
9 WHAT ARE ALL THE IMPORTANT GLOBAL PARAMETERS FOR A COMPANY CODE?
The global parameters for a company code are divided into two sections:
Accounting Organization
The parameters under this section include the chart of accounts, the credit control area, the FM area, the
company, the fiscal year variant, and more (Figure 1.7). This is also the area where you will normally set the
company code as "productive" before activating the system.
Processing Parameters
The processing parameters include settings like field status variant, fiscal period variant, whether you want the
system to propose the fiscal year during document entry, the company codecontrolling area assignment, the
calculation base for discounts/taxes, whether you will need financial statements per business area, the
maximum exchange rate deviation allowed, and more (Figure 1.8).
Enabling the business area financial statements for more than one company code at the same time (Figure
1.11).
You should only set the indicator for the business area field if you work with all the financial statements (this way, the
business area field is always ready for input irrespective of your settings if field control for posting keys/accounts). If you
only work with business areas in a few financialstatement areas (for example, P&L), then you should not set the
indicator. Instead, you should make the business area field ready for input for the business arearelevant accounts
using the field control of the accounts/posting keys.
14 CAN YOU DERIVE A BUSINESS AREA BY NOT ASSIGNING ONE IN A POSTING?
Yes. The business area can also be derived from other account assignmentsfor example, cost center. But to do this,
you need to define the business area in the master record of that particular cost center.
15 HOW DO YOU POST CROSS-COMPANY CODE BUSINESS AREA POSTINGS?
By using a cross-company code transaction, you can post to different business areas cutting across various company
codes. Any number of business areacompany code combinations are possible.
The content of the book is arranged into ten chapters:
1. General Controlling (CO)
2. Cost Element Accounting (CO-OEM-CEL)
3. Cost Center Accounting (CO-OM-CCA)
4. Internal Orders (CO-OM-OPA)
5. Activity Based Costing (CO-OM-ABC)
6. Product Cost Controlling (CO-PC)
7. Profitability Analysis (CO-PA)
8. At the Cross-Roads...
9. SAP Tables in Controlling
10. SAP Transaction Codes in Controlling
The chapter General Controlling (CO) has 64 questions covering the fundamentals of SAP Controlling. To help
understand the CO organizational elements together with their assignment, an organizational map is provided before we
even start the questions. Besides the organizational structure, the chapter also discusses the basics in CO like account
assignment, business transactions, currency, number ranges, settlement, distribution, etc.
The Cost Element Controlling (CO-OM-CEL) chapter discusses the cost elements, cost element categories, cost
element groups, accruals, overhead structure, etc. (in 17 questions), providing the necessary insight on all these.
The 3rd chapter focuses through 73 questions - on Cost Center Accounting (CO-OM-CCA): cost center, cost center
group, cost center category, standard hierarchy, activity types, statistical key figures , resources, planning profile,
versions, distribution, assessment, allocation, budgeting, variances, summarization, etc., are all discussed here.
The chapter on Internal Orders (CO-OM-OPA) discusses individual orders, standing orders, statistical order, real order,
order types, order categories, order manager, order management, archiving orders, etc., in a total of 20 questions.
The Activity Based Costing (CO-OM-ABC) is discussed in Chapter 5. There are 23 questions covering the definition,
usage, benefits, approaches (push and pull), allocation, etc. You will also see questions on parallel and integrated ABC,
planning aids, and ABC information system.
The Product Cost Controlling (CO-PC) is the largest chapter, with 184 questions, covering the four sub-components
namely, Product Cost Planning (CO-PC-PCP), Cost Object Controlling (CO-PC-OBJ), Actual Costing / Material Ledger
(CO-PC-ACT) and Product Costing ControllingInformation System (CO-PC-IS). Here, you will find questions on terms /
concepts, use / benefits of product costing, valuation variant, costing variant, reference variant, transfer / date / quantity
controls, costing, costing run, cost estimates, cost component structure, cost component split, cost roll-up, product cost
by order / period, standard / moving average price, price change, price control, valuation, variance, WIP, overhead,
overhead calculation, costing sheet, collective orders, sub-contracting, results analysis, joint production, template,
actual costing, revaluation, material ledger, mixed costing, prices and inventory values, value flow monitor, reports, etc.
The 7th chapter is devoted to Profitability Analysis (CO-PA). The questions (42) throw light on key terms, difference
between PA and PCA (Profit Center Accounting), operating concern, characteristics, values fields, segments, currency,
PA structure, master data, conversion, realignment, valuation, planning framework, planning methods, etc.
You will find the 8th chapter At the Cross-Roads... very interesting as it draws the most challenging real-life scenarios
and situations encompassing the entire scope of Controlling. The solution(s) suggested to each of the questions in this
chapter will certainly help you to resolve any similar situation in your work place. You will also get more help and
comprehension from the screen-shots displayed along with the answers.
The SAP Tables in Controlling chapter lists 75 of the most important tables in SAP CO application area.
A total of 1,335 Transaction Codes are listed in the three sections (Overhead Cost Controlling, Product
Cost Controlling and Profitability Analysis) in the chapter SAP Transaction Codes in Controlling. Unlike an alphabetical
listing of Transaction Codes / Tables which is the convention, here you will find something functional and useful: the
information is arranged the way you need, as most of the time you may not know the Transaction Code or Table to look
at, but you know the functionality or task for which you are trying to find the information.
So, how to use this book?
Read in any way you want.
Pick a chapter and read all the questions or simply pick a particular question, go to the relevant page and see the
answer. Use the book as a reference or a study-guide or a just as reading material, but make sure you understand a
particular question or concept before moving on to the next.
The SAP ERP Central Component (ECC 6.0) can be broadly sub-divided into three major application areas, namely:
Financials
Logistics
Human Resources
1.
Controlling (CO)
SAP Banking
Country Versions
SAP calls managerial accounting Controlling and the module is commonly known as CO. The CO module is
thus primarily oriented towards planning, managing, and reporting cost/revenue and is mainly used in internal decision
making, focusing on determination variances. Facilitating coordination, monitoring, and optimization of all processes in
an organization, CO involves recording both the consumption of production factors and the services provided by an
organization. As in with any other application module in SAP, this also has (a) configuration setup and (b) application
functionality.
The Controlling module focuses on the internal users, and helps the management by providing reports on cost centers,
Profit Centers, contribution margins and profitability, etc.
The data flows regularly between Financial Accounting and Controlling: all the cost information flow automatically
from SAP FI to CO; the system assigns the costs and revenues to various CO objects (internal orders, cost centers,
projects, etc.); the required and relevant accounts of SAPFI are maintained as cost elements / revenue elements in CO,
for easy and effective reconciliation between FI and CO.
SAP Controlling is meant for providing the necessary information for management decision-making. Integrated with
other applications like Financial Accounting (FI), Materials Management (MM), Sales and Distribution (SD), Production
Planning (PP), etc., this facilitates coordination, monitoring and optimization of all processes in an organization, by
recording both the consumption of production factors and the services provided by an organization. This application
component contains the following modules:
General Controlling
The relationship between various organizational units within and outside CO is depicted in Figure 0.1. It is essential that
you understand the structure to comprehend the functionality better.