Beruflich Dokumente
Kultur Dokumente
Version No : 1.0
Date : 17.03.2009
Summary Document
Name
Finance and Controlling
Version
No.
1.00
Description
This document explains steps to
be followed for closing the Fiscal
Year in Finance and Controlling.
Table Of Contents
Activities In Finance
1. Opening the New Posting Period
2. Copying Number Ranges for New Fiscal Year.
3. Valuation Of Foreign Currency
4. Asset Year Closing
i. Capitalization Of Assets Under Construction
ii. Depreciation Run
iii. Closing the Asset Year and Change the New Year.
5. Carry Forward Receivables and Payables balances
6. Carry forward the GL balances
7. Reports
Activities In Controlling
1. Assessment Run
2. Over Head Run
3. WIP
4. Settlement
Version Management
This document is subject to the version management. Each change has to be entered
into following table.
Version
1.0
Client
Electropnumetics
Author
Ravikiran Kulkarni
Date
17.03.2009
To be changed if you
want to close 2009.
To be changed if you
want to open 2010.
To open a New Year change fiscal year in column Year (col. After To Period). E.g.
if you want to open fiscal year 2010 then change fiscal year as mentioned above.
Here we are not yet closing fiscal year 2009. When you want to close fiscal year 2009
for posting then make as mentioned below -:
Change year (appearing after col. From per.1 & From per.2) to 2010. This will close
year 2009 for posting.
Maintain the Periods
Close a period by selecting the period specifications so that the period to be closed
does not fall within them.
The authorization groups for permitted posting periods could be assigned. This means
that in month-end or year-end closing for example, you can open some posting
periods for specific users only
Important Points
There must be a minimum entry for each variant.
This entry must have + in column.
This activity is once in the year and should be done with extreme care.
Version Management
This document is subject to the version management. Each change has to be entered
into following table.
Version
1.0
Client
Electropnumetics
Author
Ravikiran Kulkarni
Date
17.03.2009
Specify intervals of document number ranges are to be copied from one fiscal year
into another fiscal year. Enter following details -:
Field
Description
Company Code
Source
Year
To
Fiscal
Click on
Example
Company Code
1100
2009
2010
Version Management
This document is subject to the version management. Each change has to be entered
into following table.
Version
1.0
Client
Electropnumetics
Author
Ravikiran Kulkarni
Date
17.03.2009
Description
Example
Company Code
1100
Tick
Valuate
Customer Tick Valuate Customer Open Items
Open Items
Tick
Posting Date
31.03.2009
Posting
01.04.2009
date
for
reversal
of
revaluation
transaction
Click on
button to execute the transaction
Following screen will appear -:
On above screen see that no errors exist. If any error exist then remove that and
process as mentioned above again.
To generate postings select as mentioned in following screen -:
System will generate documents. If you select Reverse postings then system will
reverse these posting.
Select Create Postings and run in background processing.
Valuating Open Items
Use
When foreign currencies are valuated, all the OPEN ITEMS that were posted in a
foreign currency are valuated.
The valuation is based on the individual open account items in a foreign currency, that
is, each open account item in a foreign currency is valuated individually.
Prerequisites
1) Before foreign currencies for open items can be valuated, the appropriate
foreign currency postings must exist in the system.
2) The exchange rate table must be maintained (transaction OB08).
Version Management
This document is subject to the version management. Each change has to be entered
into following table.
Version
1.0
Client
Electropnumetics
Author
Ravikiran Kulkarni
Date
17.03.2009
4. Assets Closing.
Steps Involved in Assets Closing
i.
ii.
Execute the depreciation run and update the batch input session
iii.
iv.
Run the fiscal year change in Asset Accounting - This process creates
the balance carry forwards for Asset Accounting.
Carry out inventory postings
i.
ii.
iii.
Before you can close a fiscal year in Financial Accounting from a bookkeeping
perspective, you have to carry out preparatory measures in Asset Accounting.
PROCESS FLOW
You use the year-end closing program to close the fiscal year for a company code
from an accounting perspective.
Once the fiscal year is closed, you can no longer post or change values within Asset
Accounting (for example, by recalculating depreciation).
The fiscal year that is closed is always the year following the last closed fiscal year.
You cannot close the current fiscal year.
Example : Current fiscal year (current date): 1st April 2009
Last closed fiscal year
: 2007 [2009 2]
You can close fiscal year : 2008 [2009 1]
BACKGROUND PROCESSING
You have to carry out the year-end closing as background processing for performance
reasons. Therefore, start the report as a background job. You can carry out test runs
with fewer than 1000 assets in the foreground.
CHECKS
The system only closes a fiscal year in a company code if
The system found no errors during the calculation of depreciation (such as,
incorrectly defined depreciation keys).
Planned depreciation from the automatic posting area has been
completely posted to the general ledger.
Balances from depreciation areas that are posted periodically (ie. Not posted
online) have been completely posted to the general ledger.
All incomplete assets (master records) have been completed.
The system lists any assets that do not meet the above requirements in the log of the
year-end closing. The log also shows the reason for the errors.
REVERSING THE YEAR-END CLOSING [OAAQ]
If you closed a fiscal year too soon, and still need to make corrections, you can reset
the last closed fiscal year in Customizing for Asset Accounting. Using this function,
you can re-open the last closed fiscal year, either for selected depreciation areas in a
company code, or for all depreciation areas in a company code. You do this by
changing the field for the last closed fiscal year.
Reconcile the asset register balances with the GL accounts balances (ABST2)
When Asset values in the asset master doesnt match with the GL account balances.
The above reconcile program is need to be run.
Put the Company Code and Fiscal Year. Run the same in Test Run and in background
processing run take the actual run.
Version Management
This document is subject to the version management. Each change has to be entered
into following table.
Version
1.0
Client
Electropnumetics
Author
Ravikiran Kulkarni
Date
17.03.2009
Description
Company Code
Carryforward to fiscal year
Selection for Customer A/cs
Selection for Vendor A/cs
Test Run
For c/f balance Details
Click on
to execute.
Following screen will appear -:
Example
1100
2009
Tick
Tick
Tick
Tick
Remove test run and execute to carryforward balance. You can run this transaction
as many times as you want.
Version Management
This document is subject to the version management. Each change has to be entered
into following table.
Version
1.0
Client
Electropnumetics
Author
Ravikiran Kulkarni
Date
17.03.2009
carried forward balance represents only the items posted within the new year to the
prior year, not the items posted during the prior year.
Note:
If you find in the new year that a G/L account was mistakenly set up as a P&L
account in the prior year instead of as a balance sheet account (or vice versa), you
have to rerun program SAPF011 after changing the G/L account master record, so
that the balance carried forward is corrected.
T. Code -: FAGLGVTR
Logs after running the program in test run balance sheet accounts
Version Management
This document is subject to the version management. Each change has to be entered
into following table.
Version
1.0
Client
Electropnumetics
Author
Ravikiran Kulkarni
Date
17.03.2009
7. Reports
Main Reports :
Client
Electropnumetics
Author
Ravikiran Kulkarni
Date
17.03.2009
3. WIP
4. Settlement
Version Management
This document is subject to the version management. Each change has to be entered
into following table.
Version
1.0
Client
Electropnumetics
Author
Ravikiran Kulkarni
Date
17.03.2009
30 - Reclassification of GL balances
31 - Balance Carry forward (Year End Only) - F.16
32 - PCA Balance Carry forward (Year End Only) - 2KES
33 - Transfer to FI - 1KE8
Hi BSR,
Flow for period end CO activities.
RJV's
Internal Order Settlement (IO to Cost Center
Distribution
Cost Center - Assessment Cycles
Actual Activity Price Calculation
WIP
Variance Calculation
Settlement.
COPA - Assessment Cycles
In case you are using Material Ledger with actual costing. 3 Additional T-codes
CKMDUVACT Distribution of Activity Differences
CKMDUVMAT Distribution of Inventory Diffs
CKMLCP
Regards,
Vikrant Sood
Edited by: VIKRANT SOOD on Jan 2, 2010 6:20 PM
1) Transactions: ZACO88
Transfer the expense from the testing/rework order to the corresponding cost center or Internal
orders
2) Transactions: KP46
Upload SKF using as tracing factor when Cost allocation
3) Transactions: KSV5
Allocations in Cost Center Accounting are performed to move costs between cost objects (i.e. cost
center, order).
This step is for Allocate the expense from shared cost center to other cost centers.
4) Transactions: KO8G
Settlement the expense from Specific Expense Internal to the corresponding cost centers.
5) Transactions: CO43
Run Overhead Calculation transaction to calculate OH debiting production order/cost collector and
crediting cost centers. It is calculated applying a % on current BOM/Routing.
6) Transactions: KKS5
Run Variances calculation procedure to have the difference between current BOM/routing and SIC
BOM/routing. You need to perform this task to have actual recovery (Actual in SAP terminology)
and SIC recovery (Target in SAP terminology) values in PC reporting. Target costs are calculated
by the system only after this step multiplying the SIC values and the qty declared.
Variance calculation provides you with detailed cost information on production orders.
Variances can be calculated in simulation mode (test mode) for a single production order or
collectively
Variance calculation accomplishes the following:
Shows the amount of the variance between the standard costs and the actual costs.
Determines the difference between the actual costs debited to the production order and the credit
from goods receipts (total variance).
Determines production variances and planning variances for informational purposes.
Shows the causes of the variances and assigns the variances to different variance categories
depending on the cause.
There will be corresponding messages for the result of the variance calculation; they need be
checked in detail. If there is error message which is caused for Standard Price missing, the standard
price for the related SKU must be maintained immediately.
7) Transactions: CO88
Run settlement variances to post in FI the difference between recovery and actual (material
consumption, hours and oh at current BOM/routing). You need to perform this task to have on
production orders/cost collectors balance = 0
Settlement is based upon:
Sender: the production order
Receiver: the GL-account
After settlement no costs are associated to the production order anymore.
Settlement calculation
During the production process, production orders are debited with actual costs (confirmations).
Each time goods are received into inventory; the system valuates the receipt and credits the
production order accordingly.
The actual costs posted to the production order can be more or less than the value with which an
order was credited when the goods receipt was posted
8) Transactions: KKRC
This step is a data preparation for reporting and you need to perform it before run PC reports.
Hope it will help you.
Regards
Ravi
Month end closing Activities in Controlling(CO)
1. Calculate Overheads on all process Orders (CO43)
2. Technically complete all process orders which are fully processed (CORM).
3. Calculate Variance (KKS1) (Relevant only if Standard cost is calculated).
Diagnosis
Either the settlement rule for the sender does not exist, or it is incomplete.
The settlement rule must contain settlement parameters and at least one valid distribution rule. A distribution rule is
valid for a settlement run if
The settlement period is in the validity interval for the rule, and - if a settlement type was specified during
settlement -
The settlement type corresponds to the rule for the specified settlement type.
Settlement type FUL -> The system selects all rules with the FUL and PER settlement types.
Settlement type PER -> The system selects all rules with the PER settlement type.
The settlement share is set for the rule (percentage, equivalence number).
Procedure
The settlement rule belongs to the sender master data, where you can maintain it.
Internal order
Proceed
CO Production order
Proceed
Project
Proceed
Cost object