Chapter 1-GL Configuration
Chapter 1-GL Configuration
Chapter 1-GL Configuration
CHAPTER 1
Table of Contents
1
1.1
Introduction..........................................................................................................
Purpose..................................................................................................................
Reference Documents.........................................................................................
3
3.1
Configuration Settings........................................................................................
Basic Customizing.................................................................................................
Page 1 of 140
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.1.8
3.1.9
3.1.10
3.1.11
Page 2 of 140
3.1.12
3.1.13
3.1.14
3.1.15
3.1.16
3.1.17
3.1.18
4
4.1.1
4.1.2
Other reference..................................................................................................
Business Area......................................................................................................
Functional Area....................................................................................................
Page 3 of 140
Page 4 of 140
1
1.1
Introduction
CHAPTER 1
Purpose
The purpose of this Configuration document is to:
Page 5 of 140
Page 6 of 140
Page 7 of 140
Page 8 of 140
CHAPTER 1
Field
Short description
Company Code
Page 9 of 140
Configuration
reference
Section 3.1.3 of
Chap1
Type (Document
type)
A business unitCHAPTER
might be1doing
business from Jan-Dec , Apr-Mar
or Jul-June
Chap1
Section 3.1.14 of
Chap1
Page 10 of 140
Section 3.1.9 of
Chap1
Page 11 of 140
Section 3.1.14 of
Chap 1
and section 3.1.16
Posting Key
CHAPTER 1
Section 3.1.15 of
Chap 1
40- GL Debit
50 - GL Credit
01- Debit customer
11- Credit customer
31- Credit vendor
21- Debit customer
Page 12 of 140
CHAPTER
1
100000- Petty Cash
Account
476000 - Office expenses
800000 - Sales revenue
Chap 1
Currency
USD/GBP/INR/EUR
Chapter 6
Reference Documents
Page 13 of 140
CHAPTER 1
Page 14 of 140
3
3.1
3.1.1
Configuration SettingsCHAPTER 1
Basic Customizing
Page 15 of 140
as exchange rates, for example) are entered at the client level. This eliminates theneed to enter this
information more than once. Each client is an independent
CHAPTER 1
unit with separate master records and a complete set of tables and data. Users
must enter a client key and have a user master record in the client in order to log
on to the system.
Company (Trading partner):
In an enterprise structure, it is placed at the highest level in hierarchy. This is nothing
but the group company.
Page 16 of 140
Via Menus
Page 17 of 140
Page 18 of 140
Click on
Page 19 of 140
Page 20 of 140
Click on
to save.
Page 21 of 140
3.1.2
CHAPTER 1
Credit Control Area: This is the area where credits offered to the customers are
maintained and monitored. One company code cannot be share the credit limit from
credit control area other than the CCA to which it is assigned.
MODEL Group is using one credit control area.
Via Menus
Page 22 of 140
Page 23 of 140
Page 24 of 140
CHAPTER 1
3.1.3
Page 25 of 140
Since most government and tax authorities require the registration of a legal entity for
CHAPTER 1
every company, a separate company code
is usually created per country.
Certain information is mandatory for creation of company code:
1. Currency
2. Language
3. Company code key ( 4 digit alphanumeric key)
Page 26 of 140
CHAPTER 1
Page 27 of 140
Page 28 of 140
Use Copy, delete, Check company code option to copy all properties from standard company
code and modify Name & Address and other details.
Page 29 of 140
Page 30 of 140
Click on
Pop up comes up
Page 31 of 140
Click on Yes.
Page 32 of 140
CHAPTER 1
Page 33 of 140
Page 34 of 140
Click on Yes.
Page 35 of 140
Now use Edit company code option to change the company code, address etc.
Page 36 of 140
Page 37 of 140
CHAPTER 1
Page 38 of 140
Page 39 of 140
icon CHAPTER
and input 1the full address of the company code.
Page 40 of 140
Page 41 of 140
3.1.4
Page 42 of 140
Page 43 of 140
Page 44 of 140
CHAPTER 1
3.1.5
Page 45 of 140
Page 46 of 140
GENERAL
LEDGER
Figure
5: Assign Company
codeCONFIGURATION
to Credit control Area
CHAPTER 1
In Model Group Only Company code 2008 is selling goods and Credit control area is assigned only to this
company code.
3.1.6
Page 47 of 140
CHAPTER 1
3) Assign it to objects
Fiscal Year Variant: FYV is nothing but the accounting year for a co code. In SAP R/3
system FYV might be following English calendar year (January-December) or might not
be following.
FYV contains the definition of Posting periods and special periods. Special periods are
used for postings that are not assigned to time periods, but to the process of year-end
closing. In total you can define 16 periods.
Page 48 of 140
Via Menus
Page 49 of 140
Page 50 of 140
Page 51 of 140
Page 52 of 140
GENERAL
LEDGER
CONFIGURATION
Figure 6:
Fiscal year Variant
K4 provided
by SAP (standard ) with 4 special periods
CHAPTER 1
Year Dependant: If we intend to change the FYV in the subsequent years this need to be checked
Calendar Year: I f the FYV is from Jan-Dec, this need not be checked. If it is other than Jan to Dec, this needs to
be checked
No of Posting Periods: It represents how many times we close our books accounts in a year. Generally it is 12.
No of Special periods: The periods used for year- end adjustments. SAP allows a max of 4 spl periods.
Here is an example of FYV for Jun-July and how the year shift needs to be manipulated to get the year we need.
Page 53 of 140
GENERAL
LEDGER CONFIGURATION
Year
Year
Month
1
2
3
4
5
6
7
Day
31
29
31
30
31
30
31
Period
7
8
9
10
11
12
1
Shift
2010
-1
-1
-1
-1
-1
-1
0
CHAPTERShift
1
2011
0
0
0
0
0
0
1
Page 54 of 140
8
9
10
11
12
3.1.7
31
30
31
30
31
0
0
0
0
0
CHAPTER 1
1
1
1
1
1
Page 55 of 140
OB37
Page 56 of 140
Page 57 of 140
Page 58 of 140
LEDGER
Figure 7: GENERAL
Model companies
are assignedCONFIGURATION
to FYV K4
How to test the New FYV we create
3.1.8
CHAPTER 1
1.
2.
3.
Page 59 of 140
Via Menus
Page 60 of 140
Click on new entries and define Variant for Each company code.
Page 61 of 140
3.1.9
Page 62 of 140
Page 63 of 140
Page 64 of 140
GENERAL
CONFIGURATION
Assign
Variants to LEDGER
Company codes
as above
Use T code OB52 and open appropriate periods.
CHAPTER 1
Page 65 of 140
Page 66 of 140
A - Assets
S- GL accounts
CHAPTER 1
K- Vendors
D- Customers
M- Materials
+ All the above put together. It is a must to have this in OB52.
How to test the New FYV we create
Page 67 of 140
CHAPTER 1
Page 68 of 140
3.1.10
Via Menus
Page 69 of 140
OB13
Page 70 of 140
Page 71 of 140
Page 72 of 140
Page 73 of 140
Click on
CHAPTER 1
Account Group regulates the appearance of fields on the GL master data. We can design a
field on the GL master to be
Page 74 of 140
S- Suppressed
D- Display
R- Required
O- Optional
Page 75 of 140
Page 76 of 140
Double click on anyone of the A/C Group rows to get the field status groups.
To get Field status for a Group, select the group and click on
double clicking on it, we can see the detailed field status for each field:
Page 77 of 140
Page 78 of 140
GENERAL
SDRO is the key word to remember
the status.
LEDGER CONFIGURATION
CHAPTER 1
Page 79 of 140
Page 80 of 140
GENERAL
Field status ofLEDGER
Group CASH CONFIGURATION
CHAPTER 1
3.1.11
Retained earnings are the difference between the revenue and expenses. We can design
more than one RE accounts for COA.
Page 81 of 140
CHAPTER 1
Page 82 of 140
Page 83 of 140
CHAPTER 1
When you run the balance carry forward program (using transaction code FAGLGVTR), the balances
in P&L accounts are carried forward to the retained earnings account.
3.1.12
Page 84 of 140
SPRO
Page 85 of 140
Page 86 of 140
Page 87 of 140
Enter your company code and reference co code as 0001. Save the entry
CHAPTER 1
Page 88 of 140
Page 89 of 140
Click
Page 90 of 140
Click on
Page 91 of 140
CHAPTER 1
Page 92 of 140
Page 93 of 140
CHAPTER 1
Press enter
Click on Save icon
Message
Page 94 of 140
3.1.13
Page 95 of 140
Via Menus
While doing business transactions based on the GL account used fields might be
required/optional/suppressed. Here is a simple illustration
GL code &
Description
100000- Cash
Account
Value
date
Cost
Center
X
Profit
Center
X
Page 96 of 140
476000- Office
expenses
800000- Sales
Revenue
CHAPTER
1
Field status variant has many field status groups. The FSG regulates whether for a
given GL account, a field like text/assignment/CC/PC should be made as required or
optional at transaction level. One FSG is assigned to each GL master.
Page 97 of 140
Page 98 of 140
GENERAL
LEDGER CONFIGURATION
Field Status Variant Path
CHAPTER 1
Select FSV 1000 and click on
. Rename the FSV as 2008 Field status as Model Field status variant
Page 99 of 140
GENERAL
LEDGER CONFIGURATION
Field Status Groups for FSV 2008
CHAPTER 1
Select Field status group G001 and double click on the group.
It shows a summary of the group. Double clicking on the same will take us to details field
status level.
GENERAL
LEDGER CONFIGURATION
Field Status for General data (G001)
CHAPTER 1
3.1.14
CHAPTER 1
CHAPTER 1
Document type KE
CHAPTER 1
Click on save. On the main page make sure to change the description of the doc type.
Note: Use OBZO to define the default doc types to be used for Enjoy transactions.
3.1.15
For Instance, for posting key 01, 04 and 11, the XREF1 key field has been made Ready for Input
CHAPTER 1
CHAPTER 1
Click on
Note: Use OBXJ to define the default posting Keys to be used for Enjoy transactions
3.1.16
Input No range year from Number and to Number. Save it after that. Ignore messages if any.
>> Indicator which determines whether the number range interval is external or internal. External means the user
will input manually.
3.1.17
OBA0
CHAPTER 1
We have assigned blank tolerance group for each of the company codes. Double click on
any one entry
Please note the group is Blank. If need be we can create different Groups and assign as
shown below.
3.1.18
Global Parameters
Via Menus
CHAPTER 1
Make sure that the assignments done at various places are correct. COA, Company, Fiscal
year variant, Credit control area, field status variant, posting period variant are to be carefully
checked.
Please ensure to enter VAT registration no.
Click on
icon on the left, the detailed address of the company codes opens up.
Make sure that this is correct. It gets printed in various correspondences and other important
documents
Other reference
4.1.1
CHAPTER 1
Business Area
Business Area: Business areas are independent area within an organization and can be
used cross-company code. They are balancing entities that create their own set of
financial statements for internal purposes. The use of business area is optional.
Via Menus
GENERALSPRO
LEDGER CONFIGURATION
CHAPTER 1
Enter BA and description and save the entry. BA is not assigned to any co code.
4.1.2
Functional Area
Via Menus
CHAPTER 1
To create a new FA click on new entries and input the code and description.
CHAPTER 1