En Rfsumb00

Year-end closing in Italy 1(48) RFSUMB00 11.1.2008

____________________________________________________________________________________

fico+

YEAR-END CLOSING IN ITALY

RFSUMB00

This document describes how to make the fiscal year-end postings in Italy using the

program RFSUMB00.

Original version 7.1.2008

Updated 11.1.2008 Balance carry forward


____________________________________________________________________________________

fico+

CONTENTS

1 YEAR-END CLOSING IN ITALY.................................................................................................................................. 4

1.1 LEGAL TERMS ............................................................................................................................................................. 4 1.2 SAP SOLUTION............................................................................................................................................................ 4

2 RFSUMB00 YEAR-END POSTINGS ............................................................................................................................. 6

3 PREPARATIONS.............................................................................................................................................................. 7

3.1 PARAMETERS AND CONFIGURATION SETTINGS ........................................................................................................... 7

4 YEAR-END POSTING PROGRAM RFSUM00............................................................................................................ 8

4.1 REPORT PARAMETERS P&L ACCOUNTS - STEP 1 ......................................................................................................... 8 4.1.1 Selections............................................................................................................................................................... 8 4.1.2 Accounts .............................................................................................................................................................. 10 4.1.3 Parameters for closing and opening postings..................................................................................................... 13 4.1.4 Other parameters ................................................................................................................................................ 14

4.2 REPORT PARAMETERS FOR STEP 2 BS ACCOUNTS ..................................................................................................... 15

5 POSTINGS CREATED................................................................................................................................................... 17

5.1 STEP 1 - PROFIT AND LOSS ACCOUNTS ...................................................................................................................... 17 5.2 STEP 2 - BALANCE SHEET ACCOUNTS ........................................................................................................................ 17

6 BUSINESS AREAS.......................................................................................................................................................... 18

7 ACCOUNT ASSIGNMENTS ......................................................................................................................................... 19

7.1 FIELD STATUS VARIANTS .......................................................................................................................................... 19 7.2 VALIDATIONS............................................................................................................................................................ 20

8 RECONCILIATION ACCOUNTS................................................................................................................................ 20

8.1 DUMMY CUSTOMERS AND VENDORS ......................................................................................................................... 20 8.2 ACCOUNT GROUPS .................................................................................................................................................... 21

9 TABLE TABKT............................................................................................................................................................... 24

10 RUN PROCEDURE ........................................................................................................................................................ 28

11 BATCH INPUT SESSION.............................................................................................................................................. 29

11.1 BATCH INPUT SESSIONS............................................................................................................................................. 29 11.2 POSTINGS TO PROFIT AND LOSS ACCOUNTS............................................................................................................... 30 11.3 POSTING TO BS ACCOUNTS ....................................................................................................................................... 34 11.4 SITUATION AFTER THE BATCH RUN ........................................................................................................................... 39 11.5 PROBLEMS WHEN RUNNING BATCH SESSIONS ........................................................................................................... 39


____________________________________________________________________________________

fico+

12 CUSTOMER AND VENDOR BALANCES ................................................................................................................. 43

12.1 DUMMY CUSTOMERS AND VENDORS ......................................................................................................................... 43 12.2 REAL CUSTOMERS AND VENDORS ............................................................................................................................. 44

13 NOTES.............................................................................................................................................................................. 46

14 LINKS TO NET DISCUSSION ABOUT THIS SUBJECT ........................................................................................ 48


____________________________________________________________________________________

fico+

1 Year-end closing in Italy

1.1 Legal terms

Year-end closing procedures in Italy are comprised by the following steps:

� year-end adjustment posting (for ex., deferrals and accruals, items to be settled, internal buildings

etc..)

� determination of stock variations

� value adjustments and provisions carried out exclusively in compliance with fiscal rules

� summary note to the Profit and Loss Account as to positive and negative income items

� calculation of the net operating profit

� general closing of the books (assets, liabilities and equity) with balances referring to the summary

balance sheet account.

1.2 SAP solution

In SAP R/3 the year-end procedure simply means carrying forward the account balances and taking out

the financial reports. SAPF011 Carry fwd G/L balances, SAPF010 Carry fwd Receivables/Payables do

not carry out any postings, but only transfer the corresponding amounts in period 0 of the next fiscal

year. However, for actual postings are required by law.

You find following instructions in note 402917 Balance carryforward is not correct.

“After the regular balance carryforward of the general ledger (F.16), postings are made to a closing account with

RFSUMB00 in the closed fiscal year, which causes the actual G/L accounts in this fiscal year to balance to zero. At the

same time, the identical amount is posted as an opening posting into the new fiscal year in a period selected in

RFSUMB00. The postings are carried out via batch input. You can choose amongst the country versions for Italy,

Slovakia or Turkey. The country versions comply with the legal requirements of the respective countries. The use of

RFSUMB00 requires an extensive Customizing to be able to create the correct postings. In this context, it is essential to

customize dummy vendors and dummy customers to enable the balance carryforward of the reconciliation accounts.

Italy, for example, requires a separate document type for these postings, so that these postings are visible in the

document journal. In Italy, the closing entry must be made with document and posting date equalling the last day of the

fiscal year to be closed, while the opening entry must correspond to the 1st day of the new fiscal year or exactly to the

date and the posting period of the balance sheet closure (this is generally March or April). RFSUMB00 must be

executed in Italy immediately after the balance sheet closing in which case the closing entries and opening entries are

placed into a BI session. Document the postings by means of the document journal.”


____________________________________________________________________________________

fico+

You can start the closing in Italy with running the balance carry forward programs, when all the posting

for the previous year are done.

Transactions:

F.16 Carry fwd G/L balances (program SAPF011)

F.07 Carry fwd Receivables/Payables (program SAPF010)

When the all the balances are carried forward you can start the year-end posting program RFSUMB00.

Check before starting that all the necessary configurations and preparations are done!

The year-end posting program RFSUMB00 creates the year-end profit and loss statement postings

determining the operating result for the fiscal year and generates the postings to open and close the

balance sheet accounts for the new fiscal year.

RFSUMB00 is not only used in Italy. There are country specific versions for Italy, Slovakia, Turkey,

Portugal, Romania and Colombia. There are own transactions in the system for this.

The transactions call for the country specific version of program RFSUMB00. The default for the

program is Italy.


____________________________________________________________________________________

fico+

Note! If new general ledger is in use, a new report FAGL_YEC_POSTINGS is used instead of

RFSUMB00. This new report uses the accounting interface instead of the batch input session to make

postings. If you have not activated the new G/L accounting, continue to use report RFSUMB00.

Program RFSUMB00 is run in two steps.

Step 1: Closing the profit and loss accounts (E)

- Generates the year-end profit and loss statement postings. In the version for Italy, the

profit is also entered on the balance sheet.

Step 2: Closing/Opening the balance sheet accounts (P)

- Closes the balance sheet accounts and carries forward their balances into the new

fiscal year.

2 Rfsumb00 Year-End Postings

Start the program either with SA38 (System/Services/Reporting)

Or with transaction F_IT_01.


____________________________________________________________________________________

fico+

3 Preparations

3.1 Parameters and configuration settings

Before you can run program RFSUMB00 you must do some preparations:

Document types

Italy requires a separate document type for these postings, so that these postings are visible in the

document journal. Create document types and number ranges for opening and closing postings. Create

the number ranges for opening posting to new year.

Dummy customer and vendor master records

Create dummy customers and vendors to enable the opening and closing postings and balance

carryforward of the reconciliation accounts. Consider using an own account group and number range.

Table TABKT

Configure table TABKT by making the entries to close and open the

reconciliation accounts

Posting periods

Make sure that all the postings to the fiscal year to be closed are done before you run this program.

Close the posting periods of the last fiscal year. Open the special periods for year-end closing

procedures and opening postings. Open the first posting period of the new year.

Accounts

Create the accounts for closing and opening

Cost centers

Create a cost center for each business area for the report parameters.

CO-validations

If you decide to inactivate the co-validation rules for batch input sessions, change the IMG settings (tr.

OKC7) before running the batch.


____________________________________________________________________________________

fico+

4 Year-end posting program RFSUM00

RFSUMB00 must be executed in Italy immediately after the balance sheet closing in which case the

closing entries and opening entries are placed into a BI session. Document the postings by means of the

document journal.

4.1 Report parameters P&L accounts - step 1

Enter the Italian company code.

Enter the fiscal year to be closed

If you use business area balance sheets, you should run the program separate for all business areas in

order to get zero balances also on business area level. Create separate variants for all business areas.

4.1.1 Selections


____________________________________________________________________________________

fico+

4.1.1.1 Postings periods.

Enter the periods 01-16 or a range that covers all the postings for the year to be closed.

4.1.1.2 Selection of account type P (P&L) B (BlSh)

Here is an error in the English translation. You can only enter values E for profit and loss accounts and

P for balance sheet accounts. There is a correction for this in note 633884 “RSUMB00 Parameter

‘Account Selection’ incorrect in English”. Enter E.

4.1.1.3 Create batch input production run

X - Batch input creation. Activation of the batch input session for posting.

If you set X here, the program creates a batch input session. If you leave the field empty no batch is

created and you can run the program in test mode.

4.1.1.4 Bach input session name

Name the batch input session.

4.1.1.5 Hold processed session

Indicator, that the session should not be deleted after faulty processing.

4.1.1.6 Report variant for TRVOR tab

The first step of RFSUMB00 is to create a profit and loss statement. The program saves the profit or loss

for the year in table TRVOR and uses it as a comparison value when closing the balance sheet accounts.

When you run the step 1 for P&L accounts, the system sets the result in table TRVOR. The system uses

it to check the actual execution of the income closing before starting the asset closing. Its introduction in

the table is managed automatically by the system.

You cannot run the step 2 before you have run the step 1. Note 922311 ”RFSUMB00: Closing of

balance sheet accounts is not possible” makes it possible


____________________________________________________________________________________

fico+

Look at table TRVOR with SE16.

The first row shows the profit and loss posted to the Retained Earnings account updated in my first

RFSUMB00 test.

The second amount is the amount still to be posted (profit and loss posted at this stage). Note that I ran

this in the test environment and these are postings that have come afterwards. In real life you must not

run RFSUMB00 before all postings for the previous fiscal year are made.

The log of the RFSUM00 shows the same amount.

4.1.2 Accounts

Here you define the G/L accounts to be used in closing and opening postings. All these accounts are

balance sheet accounts.


____________________________________________________________________________________

fico+

On the selection screen of the RFSUMB00 report the search help is missing. This is a program error,

which is corrected in note 1017626 – “RFSUMB00: Search for closing accounts”. P&L account

Here you enter the account number of the balance sheet account to which the closing balances of P&L

accounts are to be posted. Which postings are made, depends on the posting specifications for closing

(country version).

The P&L statement account type in account master determines the retained earnings account(s) for each

P&L account. The retained earnings account is used during year-end closing to calculate the company's

result.

The retained earnings account is defined in the chart of accounts (table T030). The P&L accounts are

first carried forward to this account. The balance of the P&L accounts is set to zero. The balance of the

retained earnings account is posted to P&L account (910000 in this example). If no retained earnings

account exists the balances of P&L accounts are carried forward to the P&L account. In this example the

retained earnings account is used.

4.1.2.1 Retained Earnings account

You find the retained earnings account from the FI automatic account assignments (transaction FBKP).


____________________________________________________________________________________

fico+

The retained earnings account is a balance sheet account to which the balance of the profit and loss

closing accounts is to be posted. The carryforward program (tr. F.16) transfers the corresponding

amounts to period 0 of the next fiscal year


____________________________________________________________________________________

fico+

4.1.2.2 Balance sheet account – closing

Here you enter the account number of the balance sheet account to which the closing balances of

balance sheet accounts are to be posted.

4.1.2.3 Balance sheet account - opening

Here you set the account number of the balance sheet account to which the opening balances of balance

sheet accounts are to be posted.

4.1.3 Parameters for closing and opening postings

4.1.3.1 Document type

If you create a document type and number range for opening and closing postings, you can find the

documents more easily. Italy, for example, requires a separate document type for these postings, so that

these postings are visible in the document journal.

4.1.3.2 Posting date and period

Closing entries must be carried out with the posting date of the closing year. In Italy, the closing entry

must be made with document and posting date equalling the last day of the fiscal year to be closed,

while the opening entry must correspond to the 1st day of the new fiscal year or exactly to the date and

the posting period of the balance sheet closure (this is generally March or April).

The period must be entered, if you want to the postings to be grouped under the special periods. If you

don’t specify the period, it will be taken from the date.


____________________________________________________________________________________

fico+

4.1.4 Other parameters

The batch uses transaction FB01 and it will make the same checks as in manual posting. It checks the

field status variants and validation rules. Also the automatic posting rules are taken into account. You

need to have all the account assignments, tax codes, business areas etc. in the postings. For some of

them you can use these report parameters.

4.1.4.1 Posting keys

Use debit and credit posting keys 40 and 50. For asset postings use keys 70 and 75.

4.1.4.2 Tax codes

For the accounts relevant for tax you need to have tax codes. Use tax codes for zero-tax.

4.1.4.3 Text

Segment Text, text entered during posting on all document lines.

4.1.4.4 Cost center

For accounts that are cost elements you need to have an account assignment otherwise the batch will

abort. You find more of this in note 379276 “RFSUM: Batch input folder aborts”

Create special closing cost centers (one for each business area). In order to get the business area

balances right, you should create a cost center for each business area and save them in business area

variants.


____________________________________________________________________________________

fico+

4.1.4.5 Accounts with cost center postings

If you defined a cost center, the bacth program will set it in every posting. If you have in the data P&L

accounts that are not cost elements, the bacth will abort. Enter here only the cost elements where you

want to have this cost center.

If you have defined cost centers in CO automatic account assignment table (tr. OKB9) and want to use

these instead of the cost center defined here, remove these accounts from the range.

4.1.4.6 Transaction type

You need a transaction type for asset posting. You can use transaction type 100.

4.2 Report parameters for step 2 BS accounts

The account selection parameter for BS-accounts is P.


____________________________________________________________________________________

fico+

The accounts can be the same as well as the document types and dates.

For BS-account you don’t need the cost center definitions.


____________________________________________________________________________________

fico+

5 Postings created

5.1 Step 1 - profit and loss accounts

The posting specifications for the country version define, if and what posting are made.

When you run the program with account selection E (profit and loss accounts), the balances of all profit

and loss accounts are first posted to the retained earnings account (203000). The balance of the P&L

accounts is set to zero. The balance of the retained earnings account is then posted to P&L account

(910000 in this example). Last the P&L account (910000) is carried forward to BS closing account

(950000) and the balance of account 91000 is set to zero.

Note! The balance of the Retainded Earnings Account is not posted to next fiscal year. You do this with

the balance carry forward program (tr. F.16)

5.2 Step 2 - balance sheet accounts

If 'P' is entered for the account selection, the closing balances of the balance sheet accounts are posted to

the Balance sheet account – closing (here 950000).

The opening balances for the balance sheet accounts are posted to the specified accounts via Balance

sheet account – opening (here 960000).


____________________________________________________________________________________

fico+

6 Business areas

If business area balance sheets are in use, also the BA balances need to be closed and opened. The only

way to get the balances right, is to run the RFSUMB00 separate for each business area.

In this example the account balance is zero, but the business area balances are not.

Create report variants for each business area.


____________________________________________________________________________________

fico+

7 Account assignments

When you process the batch input folder generated by report RFSUMB00, you will encounter lots of

problems because of the account assignments.

Usually the system aborts due to missing account assignments. As postings from the batch input folder

are generated using transaction FB01, the system performs the same checks as with a manual posting.

SAP suggests solutions in note 379276 “RFSUM: Batch input folder aborts”

“There are two ways of preventing the folder from aborting:

1. Process the folder in the foreground: By doing this, you can enter the missing account assignments directly on the screen or react to the error message as it is posted. 2. Change the corresponding field status group for this run only:

Before processing the batch input folder, change the corresponding field status group for the affected accounts, so that there are no more required entry fields. This means that no check is made for theses fields. Once you have processed the folder, reset these changes.

(Alternatively, you can create a new field status group without any required entry fields. Before processing the folder, assign the field status group to the accounts and reset this change once processing has finished.)

In all cases, make absolutely sure that NO further postings are made to your system during this time.”

7.1 Field status variants

Field statuses are usually not the biggest problem, because already the fact that the account is a cost

element makes the cost assignment a required entry.


____________________________________________________________________________________

fico+

7.2 Validations

CO validations (tr. OKC7) can be very tricky. You might have validation rules that require assignments

other than cost center (sales order, order and profitability segment). There are no report parameters

available for these. I would not recommend changing the validation rules.

You could process the batch in foreground and enter the missing account assignments directly on the

screen or react to the error message as it is posted. I tried this, but run into problems, because my

choices were never validated.

I then created internal orders (one for each business area) and entered them in the CO automatic

accounts assignment table (tr. OKB9) per business area. This worked, when I first removed the accounts

from the report parameters (Accounts with cost center postings). An additional problem here was that

statistical orders were not accepted. Posting to the real orders should be settled somewhere (the cost

centers of the report parameters?)

The best solution was to make the validation inactive during batch runs (tr. OKC7).

After this change the posting goes nicely to the cost center defined in report parameters.

8 Reconciliation accounts

8.1 Dummy customers and vendors

Reconciliation accounts for customers and vendors cannot be directly posted. For this purpose you need

to create fictitious customer/vendor master records to carry out the closing and re-opening.

You need to have one master record per each reconciliation account. In order to keep these separate

from real customers and vendors, you might want to create an own account group for them. Then you

also can have own field status definitions, which allow you to have only the necessary fields. Use an

external number range.


____________________________________________________________________________________

fico+

From table SKB1 you can find the reconciliation accounts for customers and vendors in the company

code.

Create a dummy customer and vendor for each of these accounts.

8.2 Account groups

If you create own account groups for the dummies, you can keep them separate in their own number

ranges. Account groups and number ranges are created in IMG.


____________________________________________________________________________________

fico+

Assign the number range to the account group.

Do the same thing for vendors.

Create the master records for dummy customers and vendors for each reconciliation account.

When you create the master records the field status might be a problem. Probably there will be field

status variants on the company code level, which make fields like payment terms, cash management

group etc. mandatory entries. Discuss with your client which values you can use for the dummies.


____________________________________________________________________________________

fico+

If you have difficulties determining the dummies you can use the Balance reports check which

reconciliation accounts have postings.

You need to create a dummy customer for these three reconciliation accounts.


____________________________________________________________________________________

fico+

9 Table TABKT

When you have created the dummy customers and vendors, configure the table TABKT by making the

following entries:

BUKRS: company code

SAKNR: all reconciliation accounts are entered

KOART: account type of reconciliation account (customer, vendor)

LIFNR/KUNNR: dummy customer or vendor account number

UMSKZ: special G/L account for posting bills of exchange, down payments etc.

BSCHS: posting key for dummy customer and vendor accounts

BLART: document type (not currently used). The document type from the program parameters is

used. In the version for Turkey, the document type must support all account types (such as "AB").

You can do this with the maintenance transaction SM30 or in IMG

SM30

Table TABKT or view V_TABKT.


____________________________________________________________________________________

fico+

In this example customer numbers 2999997-299999 and vendor numbers 31099996-31099999 are used

as dummy customers and vendors.

In column G/L Account you have the reconciliation accounts. The number must be unique. Account

type is either K Vendor or D customer. In vendor and customer columns you enter the account vendor

and customer numbers. In column S you fill in the special g/l-indicator. Enter the posting keys for debit

and credit postings. Document type is not used.


____________________________________________________________________________________

fico+

In order to have the special g/l postings to be carried forward you need to specify them in this table.

You can use table T074 to find out which accounts have a special G/L-indicator. The accounts in the

table are on the chart of accounts level. In table SKB1 you find all the reconciliation accounts per

company code level. Some of these are alternative reconciliation accounts used for special g/l-postings.

Table T074

Accounts in columns G/L account are alternative reconciliation accounts.

You can only enter same account once. Thus you cannot make entries where same alternative account is

used for several reconciliation accounts.

You can also use the customer / vendor balances report to find out which special g/l items (noted items)

have postings.


____________________________________________________________________________________

fico+

From table T074 you can see the alternative reconciliation account for 121100.


____________________________________________________________________________________

fico+

10 Run procedure

Make sure that before you run the procedure:

� Print the trial balance of the previous fiscal year

� Check that all the preparations are done

� Run the test on the P&L and BS sides in order to check logs for the correctness of the numbers

Take a closer look at the log for the BS run. Check that the reconciliation accounts have a

dummy customer or vendor in the table TABKT.

� Run the final procedure of the income side with the determination of the operating profit.

� Run the final procedure of the balance sheet side.

� Close the periods of the previous fiscal year

� Print the trial balance of the current year and carry out the final check of the balance

situation


____________________________________________________________________________________

fico+

11 Batch input session

The program creates a batch input session. When running the batch input session, the "Post

automatically only" indicator is deactivated for all balance sheet accounts marked as such. After the

posting is successfully completed, the indicator is reset. No other postings should be carried out in

your system while the batch input session is running.

The batch uses transaction FB01, which means that it will make the same checks as a manual posting. It

checks the field status variants and validation rules. Also the automatic posting rules are taken into

account. You need to have all the account assignments, tax codes, business areas etc. in the postings. For

some of them you can use the report parameters.

11.1 Batch input sessions

Access from menu or with transaction SM35. Run the batch first in background and then start to tackle

the problems in the faulty sessions.


____________________________________________________________________________________

fico+

11.2 Postings to profit and loss accounts

Analyse the sessions and look at the postings.

FB01 makes a G/L posting

FS02 removes and sets back the ‘Post automatic only’ indicator.

Take a closer look at the screens.


____________________________________________________________________________________

fico+

The balances of all profit and loss accounts are posted to retained earnings accounts and the balance is

set to zero.


____________________________________________________________________________________

fico+

The tax code and item text come from report parameters. The cost center comes from the report

parameters. The business are comes from the cost center.


____________________________________________________________________________________

fico+

The balances of the profit and loss accounts are posted to the retained earnings account.


____________________________________________________________________________________

fico+

The balance of retained earnings account is posted to P&L closing account.

11.3 Posting to BS accounts


____________________________________________________________________________________

fico+

ABF1 postings to asset reconciliation accounts

The BS account balance is posted to BS closing account.


____________________________________________________________________________________

fico+

Posting to asset reconciliation account.

FB41 Post tax payable


____________________________________________________________________________________

fico+

Posting to dummy customer closes the reconciliation account.


____________________________________________________________________________________

fico+

Posting to year-end opening account.


____________________________________________________________________________________

fico+

11.4 Situation after the batch run

All P&L Accounts have zero balance at the end of 2007

P&L Closing Account 910000 has zero balance

Retained Earnings Account 203000 shows the cumulative net profit at the end of 2007

In the column Balance you have the profit and loss from the closed fiscal year. The cumulative balance

shows the profit and loss from all years. This amount was carried forward to next year in the Balance

carry forward program (F.16).

All BS accounts have zero balance at the end of 2007

BS closing accounts 950000

All BS accounts show an opening balance at the beginning of 2008. P&L accounts have no balance

carried forward.

BS opening account 960000

11.5 Problems when running batch sessions

The batch uses standard posting keys and makes all the regular checks. You will have the most problems

with batches aborting in faulty or missing account assignments. Here I will include examples of the

errors that I encountered during my test runs.

Run the batch first in back ground and then check how many errors you have. Correct the errors and run

the batch again. Continue until you have no errors left. Run the RFSUMB00 in test mode and check that

the log shows zero.

Check that you posting periods are open and the number ranges are created.


____________________________________________________________________________________

fico+

Message no. KI235 Account 301000 requires an assignment to a CO object

Account is defined as a cost element. This means that you must always specify a CO account assignment.

This message you will see a lot. The cost assignment can come from the report parameters (cost center),

OKB9, or you can enter it in foreground processing.

Message no. F5562 Account can only be posted to internally in company code IT01

The batch should remove the ‘automatic posting only’ check, but for some accounts it did not. For these

the check had to be removed manually. Remember to put it back afterwards!

Warning for a missing field. Probably a field status problem. This is only a warning, just press enter.

Here the cost center came defaulted from the report parameters, but was not accepted as account

assignment. The requirement came from validation rules.


____________________________________________________________________________________

fico+

Because the order was an option, I created a new order type and orders for each Business area. In my

material there where lots of this error and I entered the orders in OKB9-table on business area level.

I had to remove these cost elements from the report parameters before it worked.

Maybe an alternative could be to inactivate the validation.

BS accounts

The closing account 950000 did not balance. The reason was that on vendor reconciliation account was

not included in the batch because the posting keys were missing from the table TABKT.

There were also warnings about the currency rates.

Message no. KI163 Business area X changed to Y

The posting row orginally received business area X The CO account assignment object, however, is

assigned to business area Y. In Customizing, you can deactivate this message entirely. See the

Implementation Guide under "Controlling: General" and choose Change message control. The message

area is KI and the message number is 163.


____________________________________________________________________________________

fico+

In the report parameters Accounts for cost center I first had nothing defined, but the batch enters then

the cost center in every posting. Accounts that are not cost elements (often MM accounts, posted to

profit centers) caused an error and stop.

Enter only cost elements in the range. Don’t include accounts that are in CO accounts assignment table

(tr. OKB9), if you want them to be used.

Vendor postings Part. bank mandatory

Did not accept an empty field. The only solution I could come to

was to open the vendor bank details with BankType and enter the

bank type to Part.bank in foreground.

This is probably a field status problem.


____________________________________________________________________________________

fico+

Problems with GR/IR-account.

The account was not included at all in the batch. There was a difference between accounts 950000 and

960000 which was exactly the balance of GR/IR account. The balance showed also up in the

RFSUMB00 BS-log list.

I first tried to run the RFSUMB00 for the GR/IR account, but it did not help. Next I reversed all the

closing documents for GR/IR and run the closing again. After this the balances were OK.

12 Customer and vendor balances

12.1 Dummy customers and vendors

If you don’t run the balances carryforward program (tr. F.07) for receivables and payables, you will

have opening balances matching with the reconciliation account balances only for the dummy customers

and vendors.


____________________________________________________________________________________

fico+

The dummy accounts also have line items.

12.2 Real customers and vendors

The real customers have no balance carried forward but the line items are OK. You must run the balance

carry forward for receivables and payables to get the balances transferred to next year.

You can run this also after you have run RFSUMB00, because it does not do any postings and change

anything in G/L.

Here it was run afterwards.


____________________________________________________________________________________

fico+

The balance of dummy customers was reduced.

Reconciliation account 121100

The reconciliation account at the end of 2007

The reconciliation account at the beginning of 2008


____________________________________________________________________________________

fico+

The special G/L transaction balances were also carried forward.

13 Notes

https://service.sap.com/sap/support/notes/402917

Look at p. 10. It describes the relation of balance carry forward and RFSUMB00.


____________________________________________________________________________________

fico+



On the selection screen of the RFSUMB00 report the search help is missing. This is a program error,

which is corrected in note 1017626 – RFSUMB00: Search for closing accounts. https://service.sap.com/sap/support/notes/1017626


When processing the batch input folder generated by report RFSUMB00, the system aborts due to missing account

assignments. As postings from the batch input folder are generated using transaction FB01, the system performs the same

checks as with a manual posting.

There are two ways of preventing the folder from aborting:

1. Process the folder in the foreground: By doing this, you can enter the missing account assignments directly on the

screen or react to the error message as it is posted.

2. Change the corresponding field status group for this run only:


____________________________________________________________________________________

fico+

Before processing the batch input folder, change the corresponding field status group for the affected accounts, so that there

are no more required entry fields. This means that no check is made for theses fields. Once you have processed the folder,

reset these changes.

(Alternatively, you can create a new field status group without any required entry fields. Before processing the folder, assign

the field status group to the accounts and reset this change once processing has finished.)

In all cases, make absolutely sure that NO further postings are made to your system during this time.

Field statuses are usually not the problem, as already the fact that the account is a cost element, makes

the cost assignment required entry. I would also be careful to mess up the OKB9-table.

14 Links to net discussion about this subject

http://sap.ittoolbox.com/groups/technical-functional/sap-acct/year-end-posting-rfsumb00-for-italy-

1416729#

http://www.jt77.com/financials/finan-03718.html

En Rfsumb00

Documents

Transcript of En Rfsumb00