Visit the SAP Forum

Languages : English | Dutch | French | Portugese | Italian

Get 30,000 Interview Questions & Answers in an eBook.

Interview Success Kit - Get Success in Job Interviews

Send your Resume to 6000 Companies
India's Best Web Hosting Company

SAP Finance

Home » SAP Finance


S A P - R E S O U R C E S

Get Free SAP Resources:

Are you looking for:
  • SAP Jobs
  • Free SAP eBooks
  • SAP Softwares
  • SAP Tutorials
  • ERP Implementation Examples
Enter Email Address:
(Enter your email address above and we will instantly send you the download link to you, when you confirm your email.)
Search SAP Resources:

1. Minimum configuration to post a journal in FI:

(The assumption is that you do not want to copy either the standard SAP company or an existing company code because it will copy across too much that is not similar or not required and therefore too much cleanup will be required).

Initial Business Decisions Required:

Item to be decided


Code of company code (4 Digit Alphanumeric)

You could setup new one later, copying the configuration

Code of Chart of Accounts

Not very visible, but the maintainers of the chart may want to decide this name

Length of the GL A/c number and the account number range guidelines, possibly also the numbers of some key accounts required for automatic postings (see below)

SAP allows 10 digits, however 5-7 appears to be the normal range.� Typically the number of accounts should be in the low hundreds.�� Decide on the ranges of numbers for each type of account as much as you can so that the team can start getting used to them. EG: standard SAP usually has 4xxxxx as expense accounts, 11xxxx as Bank Related accounts etc.��

Configuration steps:



Define the company code


Define the name for a chart of accounts


Maintain the global parameters

IMG - Use standard SAP variants for the parameters to start with & update later

Define the default amount tolerances

IMG - Define for a blank group - so any new test user can post during prototyping

Define document number ranges

IMG - Copy from the standard ranges

Create some of the minimum accounts needed to start off with.�

GL Master data:
A/R and A/P control a/cs, a petty cash or suspense a/c to hold sundry offset postings while debugging, a revenue account, some expense accounts.� This list will expand as you go - see the section on account determination.

Suggest you create with reference from the standard chart and company code and use those specifications (account groups, fields status groups etc)� for now, so that these accounts will be reasonably appropriately setup.

Now you should at least be able to post a GL journal. To test I suggest you use balance sheet accounts only, since you will not have setup the cost elements for the expense accounts. All projects would at least be using the Cost center and Cost Element functionality of CO as a minimum.� So - on to the next step.

2. Minimum configuration to see expenses by cost center / post through to the CO Module

Initial Business Decisions Required:

Item to be decided


Structure of standard cost center hierarchy

The structure should follow the organizations intended responsibility reporting hierarchy (the budgetary responsibility).� Allow the appropriate number of levels.

Hierarchy node name coding

The coding of the nodes is quite important because they can be used to report on the levels in the standard reports, and so will be very visible to the users

Cost Center Naming Standards

Useful to begin following the intended standards ASAP so that test data looks as real as possible.

Configuration steps:



Define the controlling area

IMG, not very visible to users, if you are only going to have one, you could default it later

Assign the company code to the controlling area


Create the beginnings of the standard cost center hierarchy

CO - Cost Center Master data

Create a representative set of cost centers, assigning them to the appropriate node in the cost center hierarchy

CO - Cost Center Master data

Create all the expense accounts as primary cost elements

Either in the IMG - for all GL accounts in a specific range, or individually in the CO - Cost Center Master data

Now you should be able to post a GL document (journal) to an expense account and code it to the cost center.� The posting should then be viewable via Cost Center reporting and GL Account line Item Display.

3. Minimum configuration to post to sub ledgers (AR, AP)

Initial Business Decisions Required:

Item to be decided


GL Account Number of Control accounts

see account number range comments above

Configuration steps:



Create the AP and AR Control accounts in the GL

see account creation comments above

Create a couple of customer and vendor accounts

If using SD and MM too, inform the SD and MM analysts so that they can complete the account creation on the SD/MM side for the customer and vendor respectively.

Now you should be able to post a FI-AR customer invoice and an FI-AP vendor invoice.

4. Minimum configuration to post from logistics modules to FI/CO (similar concept for other modules)

So far it was relatively easy going, now it starts getting a little more difficult.� Following are the very broad steps - for more detail see the sections on Organization structure and Integration.

Initial Business Decisions Required:

Item to be decided


SD and MM organization structure and relationship to the FI/CO elements

Not a trivial decision, and may require rework, so at this stage, decide on a simple best guess with the SD/MM team to get you going

Configuration steps:



Assign the SD and MM organization elements to the FI/CO elements

IMG; to get prototyping going you need at least 1 set of working relationships that the whole team can work with (EG: 1 Sales Area, 1 Purchasing Organization, 1 Plant etc)

Maintain the basic automatic account determination for each module

IMG; For example : Revenue Account Determination for SD.� As the modules test or prototype expanded functionality, the SAP will look for the accounts to which it should post.� You could maintain on an as needed basis. The SAP documentation and configuration does not always explain clearly which piece of account determination is used for which type of functionality, so it is sometimes difficult to be pro-active.� being reactive has the benefit that hopefully each side (e.g.: MM and FI) can develop an understanding of what the business transaction is and therefore where it should be posting. Otherwise the MM person may not even be aware that he has generated a certain type of posting ! (You'd be amazed at some of the lack of ownership from a logistics consultant for the financial postings that they generate).

Now the other modules will be able to process a thin 'path' using agreed organization elements and base functionality, all the way through to FI.


discussionDiscussion Center


Yahoo Groups
Y! Group
Sirfdosti Groups
Contact Us
Sign in

User Name:
Forget password? | Register


Get 30,000 Interview Questions & Answers in an eBook.

Interview Success Kit - Get Success in Job Interviews

Send your Resume to 6000 Companies

SAP Resources

  • SAP Articles
  • SAP Books
  • SAP Certifications
  • SAP Companies
  • SAP Study Materials
  • SAP Events
  • SAP Faqs
  • SAP Jobs
  • SAP Job Consultants
  • SAP Links
  • SAP News
  • SAP Sample Papers
  • SAP Interview Questions
  • SAP Training Institutes
    SAP Tutorial

  • Introduction
  • SAP History
  • SAP Facts
  • SAP Tables
  • SAP Function
  • SAP Report
  • Reasons To Use SAP
  • SAP Landscape
  • SAP Transaction Code
  • SAP Lotus Notes Integration
  • Business Connector and XML
  • Enterprise Release 4.7

  • SAP Training Institutes

  • SAP Training Institutes
  • Job Consultants Address
  • SAP Companies Address

  • Business Process Cycle

  • Analyze
  • Design
  • Implement
  • Operate
  • Optimize
  • Skills And Education

  • Logistics Module

  • Sales and Distribution
  • Quality Management
  • Materail Management
  • Plant Maintenance
  • Financial Modules (FI/CO)
  • Project system
  • Production Planning
  • Service Management

  • SAP NetWeaver

  • Introduction
  • Object Model
  • Interoperability
  • Creating Web Apps
  • Java Connector
  • Advantages & Conclusion
  • Life Cycle Management
  • Composite Application Framework

  • SAP Tools

  • SQL Trace Tool
  • SAP BW

  • SAP Modules

  • SAP FI Module
  • SAP CO Module

  • SAP Technical

  • SAP ITS Architecture
  • Financial Management
  • Manufacturing Planning and Execution
  • Customer Order Management
  • Lackbox Processing
  • SD and Financial Accounting Integration
  • SAP - HR (Human Resource)

  • SAP Miscellanous

  • Web Application Server(WAS)
  • Data Archiving
  • Mobile Engine
  • SAP Script
  • SAP Transactions
  • SAP Business Warehouse(BW)

  • SAP Reference

  • SAP Facts
  • SAP Tables
  • SAP Function
  • SAP Report
  • SAP Landscape

  • SAP Others

  • SAP Treasury
  • SAP Finance
  • SAP Data Archiving
  • SAP Exchange
  • SAP Applications Components
  • SAP Software
  • Dunning
  • SAP Payroll Basics
  • SAP BASIS and Security Authorization
  • SAP Backup
  • SAP Router

  • ABAP Tutorials

  • Introduction
  • ABAP Transaction
  • ABAP Function
  • ABAP File Processing
  • ABAP Objects
  • ABAP Syntax
  • ABAP Queries
  • SAPMail Using ABAP
  • ABAP Programming Hints

  • SAP Projects & Codes

  • Finding the user-exits
  • Purchase Order Display
  • Batch Input
  • Dynamic Open SQL
  • Creating Extract Dataset
  • Reading database tables
  • Load table from a UNIX file
  • Create subscreen

  • SAP Resources

  • SAP Books
  • SAP Links

  • Interview Question

  • Common Interview Que.
  • ABAP Interview Que.
  • ERP Interview Que.
  • HR Interview Que.
  • MM Interview Que.
  • PP Interview Que.
  • ALE Interview Que.
  • EDI Interview Que.
  • Basis Interview Questions
  • SAP-SD Interview Questions
  • FI&CO Interview Questions
  • BW Interview Questions
  • CRM Interview Questions
  • Interview Questions

  • Careers at SAP

  • Careers in SAP (SAP Jobs)
  • Advertise