Tasks to be completed when documenting an operation (from creation to publication)
1. Enter the Title of the operation / page
2. Add the following Labels:
Scope of applicability: ww, country_accounting
Country or group of countries (if applicable): belux, china, france, italy, lam, nam,uk_ie, bulgaria, dach, netherlands, iberia, poland, latvia, australia, india, japan, south_korea, thailand, singapore
Unit and Domain according to the List of labels to be used in the Finance Service Line space
E.g. 1: WW Operation in Financial Accounting under domain "Central Finance Processes & Compliance":
Labels to be used: ww, financial_accounting, central_fin_proc_compliance
E.g. 2: France Operation in Financial Accounting:
Labels to be used: country_accounting, france, financial_accounting
(for country operations, the Domain is always country_accounting)
3. Fill in all fields as described above
4. Once the description of the operation is completed, ensure it is approved and published by launching the SBS-Finance approval workflow
Responsibility area: N/A
Table of contents
Scope
ERP
Frequency
References
Forms
IT 8090 Manual Postings Diversi
Attachments
Previous OP << IT - Final Postings for Year End Closure >> Next OP
1. Objective and Scope
1.1. Objective of this Operation
The Italian General Accounting usages demand that at year end all the accounts should close through the account "Closing balance sheet"- Bilancio di chiusura. This means that, after the regular balance carry forward of the general ledger (F.16) postings are made to close the 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.
This procedure explains how to run the standard ERP transaction (program RFSUMB00) that process the final postings that will close the balance sheet at year end for all Italian entities. The first phase closes the profit and loss accounts and the second step makes the year end closing and opening postings for balance sheet accounts.
1.2. Scope
This procedure is applicable to all Italian companies from both systems PF2 and WP2.
1.3. Periodicity
This procedure should run after the General Shareholders' Meeting (around April) and after CAD or CAM approval .
2. Definitions
See Finance Glossary.
3. Tasks description
3.1. Responsibilities
- CAD/CAM's are responsible to communicate when statutory financial statements are finalized so you can start run the closing procedure.
- Acc. Platform team is fully responsible for the procedure execution in accordance with the operations explained in this document.
3.2. I perform the year end closure activity for PF2 entities
When statutory financial statements are finalized you use a program in new General Ledger Accounting to perform the closing and opening of accounts balance for a change in fiscal year, this procedure is know as Diversi a Diversi..
As you may know, master data is a sensitive topic and it is under service units responsibility to maintain them updated. As this procedure is done once a year and very restrict rules exist your first step is to ensure that you have the accesses to process the transactions described.
During the execution (and just to prevent further questions) we have to aggregate the outcome of the transactions after each step and send the information to CAM (according to each company code).
We need to have:
- BS data - period 16 before execution of each Variant (GR55 - Z4F1)
- Retrieve of the Diversi Transaction F_IT_01 (same in HTML format and change to excel after)
- BS data - period 16 after execution of each Variant (GR55 - Z4F1)
- F.08 before manual posting
- F.08 After manual posting
- Posting documents and final check outcome.
Documentation from previous years are archived in Gdrive:
3.2.1. I ask for the necessary accesses to perform the procedure
To run this procedure it is mandatory to have authorization to the transaction FS02 and FSS2.
Go to SyRA Digital Workplace and create a SAP Access Request to assign you both transactions temporarily (1 month) and note that it is important that you clearly identify the procedure and explain why we need the access.
Take as example:
Italian Procedure - Year End closure of Fiscal Year "Diversi a Diversi "- Temporary access request for user XXXXXXX.
Approval was received to start the execution of the of accounting procedure Year End closure of Fiscal Year "Diversi a Diversi".
This is a specific procedure to be executed in WP2 and PF2, once a year we need to run specific transactions only for Italian entities and for this reason access that is usually forbidden we need to activate temporarily to FS02 and FSS2 (2 months).
3.2.2. I request to unblock the GL accounts and Cost centers
It is under service units responsibility to open/close the GL accounts and cost centers.
You have to login on in PRS / PF2 client 050 and launch transaction ZZF_MDWF_REQUEST to create a request by company code to unblock:
Guidelines on how to complete the request to unblock the master data is available here below:
ZZF_MDWF_REQUEST - Fast track for G/L company views
ZZF_MDWF_REQUEST - Cost Centers request using the Workflow
Share also by email with the team responsible the validation you have received from the CAD/CAM to support your request and speed up the process.
Taking previous years as example here a list of GL accounts and cost centers we must ask to be unblocked before starting the procedure.
| GL ACCOUNTS | ||
| 5835 | 6306 | 6428 |
| 8900090002 | 8900090002 | 8900090002 |
| 8900090003 | ||
| 8900090004 | ||
| 8900090005 | ||
| 8900060013 | ||
| 591EUR0279 | ||
| 505DHEUR70 | ||
The cost centers to be unblocked are:
| Cost center |
| ZZ5835ALFA |
| ZZ6306ALFA |
| ZZ6428ALFA |
3.2.3. I perform the opening of periods
To start the task it is necessary to manage some past periods opening:
1) Transaction OB52 – opening the periods
Using the transaction OB52 you have to open the accounting period nr.16 of the previous year and period 01 of the current year, please ask the team responsible to do it.
2) Transaction /N/FIN3/OKP1_BK – opening the periods for CO postings
Using the transaction /N/FIN3/OKP1_BK you have to open the accounting period 16 of the previous year and period 01 of the current year for CO postings – "CO Through-postings from FI".
3.2.4. I perform the year end closure/opening of accounts
The transaction to run the year end closure activity is F_IT_01 (program RFSUMB00):
For each company code there are 4 variants to be selected and run with the following order:
Each variant will be explained in detail in this procedure and also the parameters that need to be updated in each tab of the transaction to ensure that every GL account is balance
Each variant will carry forward the data and in Balance Sheet report GR55 – Z4F1 you can control the outcome after each batch session is processed.
When running the transaction in real mode a Batch Input Session will be created in SM35 with the following names:
- XXXX CHIUS 1 – for first variant (Conti Alphanumerical)
- XXXX CHIUS 2 – for second variant (Conti Economic)
- XXXX CHIUS 2- for second variant (Conti Economic) (exists due to the implementation of KE30 for Solvay entities and this will limit the number of errors to be manually processed as some PL accounts do not allow the usage of a cost center)
- XXXX CHIUS 3 – for third variant (Conti Patrimoniale)
When processing SM35 batch input, errors might be displayed on every variant, those are explained in section 3.2.6 of this procedure.
Open transaction F_IT_01 and select 1st variant "XXXX CHIU.ALF.":
Pay very attention on the selections that need to be updated every year, all the other fields are fixed:
- Fiscal Year must be always the one we are closing
- TAB Selections - Create Batch Input Update Run – If the field is empty you are in TEST MODE when you select "X" the batch session will be created. By default this field will be empty.
- TAB Postings - the date of the postings (doc date and posting date) have to be updated accordingly to the year that is being close and reopened, doc type and period should remain (S8 – period 16 and S7 – period 01)
If these fields are ok and you are in test mode run transaction by selecting 
When the report finish, scroll down the data until the end of the page where will find a total amount resuming all the alphanumerical accounts G and F type.
Now we have to confront the data with report GR55 - Z4F1:
If the amount in lines (F and G) are the same, then we can run the program in real mode.
Go back to the main screen of the transaction, all selections are the same except on Create Batch Input Update Run where we need to insert "X" to create the batch session:
The outcome will be exactly the one displayed before but instead of test run you will see Update Run – this means that a batch session has been created.
Before processing the batch session never forget to save this outcome, you will need to send it to CAM along with the excel with the final checks performed.
Choose:
Save this file in one folder, open it in Excel and save it back in XLS, in the end will be send with the other two variants outcome to CAM.
Now go to transaction SM35 select the line with batch session name "XXXX CHIUS 1" and run it in mode display errors only.
STEP 1
Use transaction code: SM35
SM35 - Batch Input: Initial Screen
Batch input is a SAP interface that allows you to transfer large amounts of data to an SAP system. You can use batch input to transfer legacy data and perform periodic imports of external data.
A batch input session is a sequence of transactions supplied with user data by a program. SAP stores these transactions on a stack until you decide to process them online. No database updates are performed until the session has been processed. Using this technique, you can transfer large amounts of data to SAP in a short time.
STEP 2
Look for the batch input session to be processed
If you don't know the session name you can run this transaction using the "Selection criteria" in the top of the screen.
These selection criteria can be combined in order to strengthen the list of batch input sessions.
Selection by
- Session: where you can insert the session name you are looking for
- Period: where you can insert the period for which the batch was created
- Created By: where you can insert the user who created the batch input session
STEP 3
Select the batch input session to be processed
After you find the session, select the line with the batch input that you want to run:
STEP 4
Start processing by clicking on 
.
STEP 5
Check the status of the batch input session
Double click over the session.
To see detailed information (e.g. document numbers generated), click on "Log created on dd.mm.yyyy":
During this process some errors might be displayed, please consult section 3.2.6 to see how they are solved.
After complete SM35 we need to open again GR55 - Z4F1 and see what happen in column definitive lines G and L:
As expected accounts have been balanced, we can go ahead to next variant.
3.2.4.2. I run the 2nd Variant – Balance P &L Accounts (Net Result)
Open transaction F_IT_01 and select 2nd variant "XXXX-CHIU.ECO." and afterward 3rd variant XXXX-CHIU.ECO1 :
The 3rd Variant has the same purpose as the second variant, however, the difference is that some accounts dont need cost centers and for that purpose was created the third variant to avoid unnecessary errors.
Make the same selection you have chosen in the first variant, additionally confirm that in the last tab "other parameters" you have one cost center identified. Usually this data should be saved in the variant although in case this does not happen go to section errors 3.2.6 and choose the right object according to the company code you are taking care.
After confirmation that all selections are ok, click on 
and run the transaction, first in test. When outcome is displayed, scroll down the report and cross check the result with balance sheet report GR55 – Z4F1 in heading L12000 - Profit/Loss for the period.
F_IT_01 outcome:
GR55 – Z4F1 Outcome
If pre-check is ok, follow the same actions explained in 1st variant run:
- Run transaction in real mode
- Extract the outcome in HTML and convert in xls.
- Run batch session named "XXXX CHIUS 2"
- Open log and confirm that documents where posted
During the batch session running some errors can be displayed, you need to consult the section 3.2.6.
Afterwards open again GR55 – Z4F1 and look to column definitive confirm that amount was carry forward (set to zero).
If yes we can proceed and run the last variant.
3.2.4.3. I run the 4th Variant - Balance Sheet Accounts Balanced
Open transaction F_IT_01 and select 4th variant "XXXX-CHIU.PAT.":
Follow the same selections and actions has in first variant ensure the update of:
In this step of the procedure the TEST running outcome seems different from the one when you run in REAL MODE
Test Outcome
Real Mode Outcome
No issues with this, we can continue the work and generate the last batch input session with name "XXXX CHIUS 3".
In case or errors displayed consult section 3.2.6 of this procedure.
One important highlight in this step are the posting booked in this case per each line two posting are done, one in past year and other in the new year for the opening balance.
Example:
In this last variant there is no need to make any pre-check against Balance Sheet Report GR55 – Z4F1, only after we book all the documents we open the report and column "Definitive" has to be blank, all the G/L balances have been carry forward.
If the running of the procedure went well the balance sheet was set to zero at year end YYYY and we can go ahead with the final steps described in section 3.2.4.
3.2.5. I perform the final postings and checks
3.2.5.1. I check the balance on F.08 to perform the final postings
Once you complete all steps described in section 3.2.3 in order to finalize you should come up with all GL accounts set to zero except the following ones :
- 3042000000 Retained earnings-current year
- C042000000 Retained earnings-current year (only if there are differences between statutory and GAAP balance sheet)
- 89000900002 Pick-up account nr. 2
The final balance has to be any how at zero and you need to perform a final posting to ensure that.
Open transaction F.08 and fill in the information listed here under and run the report by clicking on 
:
- Company Code
- Fiscal Year
- Reporting periods
If amounts are displayed in accounts mentioned, two postings have to be booked:
| 1) In closure year | 2) In new year | ||
| Period 16 – 31/12/201Y | Period 01 – 31/01/201+Y | ||
| Doc Type S8 | Doc Type S7 | ||
| 50/40 | 3042000000 | 40/50 | 3042000000 |
| 40/50 | C042000000 | 50/40 | C042000000 |
| 40/50 | 8900090002 | 50/40 | 8900090002 |
In both posting the same descriptions to include are:
- In reference field text: CLOSE/OPEN
- In assignment field text: Chiusura/Apertura
- In text field: CHIUSURA CONTI
The second posting is the opposite of the first one, the only changes are the document type, posting date, period and the posting keys used.
E.g. Company 5835 closure year 2018
Posting in period 16
The correspondent opposite in 2019
Once postings are finalized, go back to F.08 and run it again with the same selections.
The report will show all the accounts line by line with accumulated balance, if this column total is zero all is ok and we can consider the year end closure procedure completed.
3.2.5.2. I do a final validation with BFC result
Compare amount in heading L12800 from report GR55 → Z4F1 with BFC in January of the current year:
3.2.5.3. I check customer and vendor final balances to clear open items
After complete all the steps described on the previous points we can make one additional check on customer and suppliers closing balance and confirm that have been updated correctly.
- Customers balances
Open report S_ALR_87012172, and select the company code, the year that is being closed and the reporting periods 1 to 16.
Afterwards in OUTPUT CONTROL choose "normal balances":
Confirm that customers are set to zero in column Balance Carryforward.
If you look carefully you will find customer account "410759 CHIUSURA" has the counterpart balance (fictitious customer created in the system to close and reopen the balances).
Repeat the operation for "Special G/L balances" using the same previous selections:
- Vendor Balance
Now we need to apply the same check for supplier's balances with report S_ALR_87012082.
The selections to be considered are exactly the same has for Customers.
The column Balance Carry forward should be set to zero and the supplier fictitious "406188153" has the counterpart balance (fictitious vendor created in the system to close and reopen the balances).
Repeat the operation for "Special G/L balances" using the same previous selections:
3.2.5.4. I clear Customer, Vendor and G/L accounts
After the previous check we need to proceed with clearings on the fictitious customer and supplier number and also per each type of Special GL indicator linked to both.
Hereunder the number to be consider equal for all Italian companies:
- Customer - 410759
- Supplier - 406188153
Customer data to clear:
Customer Normal Customer Normal Items - open FBL5N Customer Normal Items - open FBL5N.
After open F-32 and clear the data open.
Second step is to repeat the process for customer special GL indicator data:
For each type of special GL make a clearing in F-32.
Vendor data to clear:
Open FBL1N and choose first normal items for supplier.
After select again supplier but now with Special G/L transactions.
The clearing is to be performed in F-44 first to normal items and after for special G/L transactions following the same steps as explained for the customer accounts.
G/L accounts data to clear:
In this step we need to drill down the G/L accounts that we have seen in the F.08 report and clear the ones that are managed by open items.
The transaction to be use can be the automatic clearing F.13 by inserting all the accounts and run it or the F-03 clear individually.
3.2.6. I perform the final actions
I close periods in OB52 and /FIN3/OKP1_BK and close again all master data open during the execution of the procedure (GL accounts and cost centers).
When completing the all the tasks and send data to CAMs; it is mandatory to close all the periods (FI and CO) has described in the beginning of this documentation.
3.2.7. I identify and solve possible errors in the variants
Note: Some errors described below, can be common to other variants also systems and transversal to all companies, like the periods and accounts blocked.
3.2.7.1. I identify errors in 1st variant
For each company code one cost center was defined to be use in this case. See the table bellow with all companies cost centers and orders to be considered.
| Company Code | Cost center | Statistical Order |
| 0270 | ZZ0270ALFA | 40551005341 |
| 0279 | ZZ0270ALFA | 40151002060 |
| 5835 | ZZ5835ALFA | 42258000140 |
| 6306 | ZZ6306ALFA | 40551005723 |
| 6277 | ZZ6277ALFA | 40551005721 |
| 6428 | ZZ6428ALFA | 40551005722 |
Error 2 - " Posting period is not opened"
In this case open the periods 16 and 1 with transaction OB52
Error 3 – "Transaction CO through postings from FI has been locked"
Open the periods 16/2013 and 01/2014 with transaction /FIN3/OKP1_BK, both have to be opened.
And
Error 4 – "G/L account in tax code DZ not found"
In this case continue to process the batch session until the end by selecting in the toolbar – System - Services – Batch Input – Next transaction.
Leave these errors to be the last ones to processed they will be booked by running the batch session in Foreground mode.
Per each line that is displayed with tax code "DZ" delete this code and give enter for the next screen, repeat this operation until the end and ensure you remove all "DZ" tax codes.
Error 5 - Error 2"CHEF/ET89999999 CTR belong to business area 7310 not 7530"
In this case you have to cancel the business area. Push Enter and the system starts again.
Error 6 - "Create account 6xxxxxxxxx for 31/12/2007 has a cost element in controlling area CHEF "
In this case you need to delete the cost center and push enter to continue to process the batch impute session.
Error 7 – "Field quantity is a required field for G/L account 6141030000"
To solve this error we need to process the batch session in foreground mode, therefore first select in the Menu Bar "/Ne
You will leave the batch input to be able to start again, when you have the main screen again
Click on 
and then select the following modes
Press on 
and the batch starts again in manual mode. Then you click until account 6141030000 is pointed out. Now you have to input Quantity = 1 and Type = KM. You have to continue manually until you meet a document without the aforesaid account inside.
Then return to a processing using only a blocking error in this way:
System
Batch-input
Display errors only
The transaction starts automatically again.
Error 8 – Amount higher then 1.999.999.999,99
To solve this problem is necessary to open a fas connect
3.2.7.2. I identify errors in 3rd variant
Error 1 - Account 410759 in company 5916 is blocked for posting
Open transaction FD02, select the account and company code in error and afterwards in header select the tab 
. Choose fields (Blocking data and Deletion flags) and unblock everything.
Leave the batch session with the following control:
Enter again and process using the option display errors only.
After process the batches don't forget to re-block the account in the fields changed before.
Error 2– "Account 1200000000 0270 is blocked for posting"
In this case the first check to be done is to understand in which level account is blocked:
At Client Level (COCA) - Open FS02 and in the main menu toolbar choose G/L account - Block
The following window is displayed:
Remove all the blocks that are selected save the data 
go back to SM35 and process the batch input session in error.
STEP 1
Use transaction code: SM35
SM35 - Batch Input: Initial Screen
Batch input is a SAP interface that allows you to transfer large amounts of data to an SAP system. You can use batch input to transfer legacy data and perform periodic imports of external data.
A batch input session is a sequence of transactions supplied with user data by a program. SAP stores these transactions on a stack until you decide to process them online. No database updates are performed until the session has been processed. Using this technique, you can transfer large amounts of data to SAP in a short time.
STEP 2
Look for the batch input session to be processed
If you don't know the session name you can run this transaction using the "Selection criteria" in the top of the screen.
These selection criteria can be combined in order to strengthen the list of batch input sessions.
Selection by
- Session: where you can insert the session name you are looking for
- Period: where you can insert the period for which the batch was created
- Created By: where you can insert the user who created the batch input session
STEP 3
Select the batch input session to be processed
After you find the session, select the line with the batch input that you want to run:
STEP 4
Start processing by clicking on .
STEP 5
Check the status of the batch input session
Double click over the session.
To see detailed information (e.g. document numbers generated), click on "Log created on dd.mm.yyyy":
When you complete to process the information NEVER FORGET to come back again in FS02 and set back the original blockings.
These accounts are not allowed to be used for postings in any company of the group.
Error 3 - " Make an entry in all required fields – due date "
The system requires a due date. This date has no consequences, so you can input the end of previous year.
Input the date 31-12-2013 and press enter, the batch session will starts again.
Error 4 - " Make an entry in all required fields – Business Area"
If the business area is missing, you have just to input the preponderant one and push enter, the batch session will continue to be processed
Error 5 - " Make an entry in all required fields – Material and Partner"
If the Material and partner is missing you have to add this information
For company 5835
|
Error 6 - Provision accounts field "transaction type" missing
Go to FSS0 open account 4003000000 in change mode and in tab "Creat/bank/interest"change the parameter "Field status group" from GEN3 to GENE. 
Go back to the batch session, in order to the system assume the new customization for the account it is necessary to leave the batch session (type /NEND) and start again processing display errors only.
After process the batch input don't forget to open again FSS0 in change mode and set up again the correct group "GEN3" on "Field status group".
Error 7 – "Missing data in table TABKT"
Open transaction SM30 and confirm in table TABKT that account displayed in error is missing for the company being treated.
We need to open a IS ticket to request the table update, meantime contact Accounting Platform and CAM team in order to inform them about the issue.
In case of information needed they will provide.
Note: In case G/L exist in other company, it is possible to copy the data with reference.
If amounts are displayed in accounts mentioned, two postings have to be booked:
1 – In closure year - 2018
Period 16 – Posting date 31/12/2018 | |||
Doc Type S8 | |||
50/40 | 3042000000 | ||
40/50 | C042000000 | ||
40/50 | 8900090002 |
| |
2 – In new year - 2019
Period 01 – 31/01/2019 | |||
Doc Type S7 | |||
40/50 | 3042000000 | ||
50/40 | C042000000 | ||
50/40 | 8900090002 |
|
In both posting the same descriptions is considered:
- In reference field text: Year-end closing 2019
- In assignment field text: Chiusura/Apertura
- In text field: CHIUSURA CONTI
NOTE:
The second posting is the opposite of the first one, the only changes are: posting date, period and the posting keys used.
Eg: Company 0345 closure year 2013
Posting in period 16 
The correspondent opposite in 2014 
In case we don't see the figures in this report on column "Balance carry forward we need to open a Fas connects.
3.3. I perform the year end closure activity for WP1 entities
3.3.1. I ask for the necessary accesses to perform the procedure
Follow the steps mentioned in 3.2.1 we need to activate temporarily transaction FS02/FSS2 and ZWFA32A.
RCS Role GACM049 - IND - Manage carry forward for Italian companies
3.3.2. I request to unblock the GL accounts and Cost centers and update some parameters in the GL accounts
As you may know, master data is a sensitive topic and it is under service units responsibility to maintain them updated.
You have to login on in PRS / PF1 client 050 and launch transaction ZZF_MDWF_REQUEST to create a request by company code to unblock.
Guidelines on how to complete the request to unblock the master data is available here below:
ZZF_MDWF_REQUEST - Fast track for G/L company views
ZZF_MDWF_REQUEST - Cost Centers request using the Workflow
Share also by email with the team responsible the validation you have received from the CAD/CAM to support your request and speed up the process.
These are the accounts that need to be unblocked:
Account | Description |
89899999 | REPORT ITALIE COMPTE DE RESULTAT |
85999900 | REPORT ITALIE COMPTE DE BILAN CLOTURE |
85999901 | REPORT ITALIE COMPTE DE BILAN OUVERTURE |
18000100 | REPRISE STOCKS |
18000200 | REPRISE CLIENTS |
18000300 | REPRISE FOURNISSEURS |
18000400 | REPRISE COMPTES GENERAUX |
Cost center | |
| 8090-9999 | ZZZZ Milano Reprise |
Transaction FSS0 – Change G/L account parameter
Some results of analytic accounts with a mandatory charge the "cost center" area is not accessible.
In fact, the accounts listed in the table below include a group zone where the cost center is hidden.
For these accounts, the group zone must be temporarily changed with G004 value (where the cost center is available) of the time of the passage of closing entries.
Go to FSS0 and select change mode:
These are the accounts that need to be changed:
Company | Accounts | Origin group Zone | Target Group Zone |
XXXX | 98100000 | G036 | G004 |
XXXX | 98100010 | G036 | G004 |
XXXX | 98100020 | G036 | G004 |
XXXX | 98100030 | G036 | G004 |
XXXX | 98100100 | G036 | G004 |
XXXX | 98100110 | G036 | G004 |
XXXX | 98100120 | G036 | G004 |
XXXX | 98100130 | G036 | G004 |
XXXX | 98100200 | G036 | G004 |
XXXX | 98100210 | G036 | G004 |
XXXX | 98100250 | G036 | G004 |
XXXX | 98100260 | G036 | G004 |
XXXX | 98100400 | G036 | G004 |
XXXX | 98100450 | G036 | G004 |
XXXX | 98120100 | G036 | G004 |
XXXX | 98150362 | G100 | G004 |
XXXX | 98300853 | G100 | G004 |
XXXX | 98360101 | G036 | G004 |
XXXX | 98360102 | G036 | G004 |
XXXX | 98360106 | G036 | G004 |
XXXX | 98360107 | G036 | G004 |
Ensure that the customers/vendors listed below are unblocked at company level by using transaction FD03/FK03:
Type | Account | Description |
Suppliers | 59812 | FOURNISSEUR COMPTABLE TECHNIQUE 1 |
Suppliers | 59813 | FOURNISSEUR COMPTABLE TECHNIQUE 2 |
Suppliers | 59814 | FOURNISSEUR COMPTABLE TECHNIQUE 3 |
Suppliers | 59815 | FOURNISSEUR COMPTABLE TECHNIQUE 4 |
Suppliers | 59816 | FOURNISSEUR COMPTABLE TECHNIQUE 5 |
Suppliers | 59817 | FOURNISSEUR COMPTABLE TECHNIQUE 6 |
Suppliers | 59818 | FOURNISSEUR COMPTABLE TECHNIQUE 7 |
Suppliers | 59819 | FOURNISSEUR COMPTABLE TECHNIQUE 8 |
Customers | 56215 | COMPTABLE CLIENT TECHNIQUE 1 |
Customers | 56221 | COMPTABLE CLIENT TECHNIQUE 2 |
Go to Service One Digital Workplace and create a SAP Access Request to assign you both transactions temporarily and note that it is important that you clearly identify the procedure and explain why we need the access.
3.3.3. I perform the opening of periods
3.3.3.1. Transaction OB_GLACC12
Some general accounts are defined with the group of statutes Z001 areas "Gen Accounts. With flow carat obliged codes ".
For these accounts the "consolidation movement Code" field is mandatory.
However, this information is not taken into account by the generation program closing / opening writings.
The number of accounts affected is about 80 account by society. This group will be replaced by the ZZ01 group (where the area in question has the status "Optional").
After recognition of the parts, the group will be reset to Z001 state.
Note: ZZ01 group was created specifically for this treatment, and is therefore used only temporarily.
- Go to OB_GLACC12 and select variant: RAN_8090
Execute:
NOTE: Select all the accounts and copy to excel, after the procedure you will have to run this again to change again from ZZ01 to Z001.
Change all accounts from area Z001 to ZZ01
Following messages appear:
3.3.3.2. Transaction ZWFA32A
Some accounts are set to be charged only by automatic input (through integration with other modules).
The postings related with opening and closing accounts are from manual input for this reason is necessary to change some accounts settings.
This is taken into account by the RFSUMB00 program and treatment is provided in the batch input.
For Cons, the RCS model, automatic imputation setting only became compulsory for all accounts attached to AUTO group account.
A specific program ZWFAI01300 allows changing the group account by selecting the accounts to change from AUTO group. These are modified with Zsák group account (for special treatment).
This will put the accounts in the initial state after closing registrations.
Warning !!! This treatment is a change in the general level of the account plan. Therefore quickly process Batch Input accounting records in order to put the accounts in their original condition, with the AUTO group account.
Go to Transaction →ZWFA32A
Make the selection:
Accounts = Z001 |
The following screen appears:
NOTE: Select all the accounts and copy to excel, after the procedure you will have to run this again to change again from ZSAK to AUTO:
You will insert the accounts in the G/L account fields.
3.3.3.3. Transaction OB52 – opening the periods
Before starting the task it is necessary to open some past periods.
We need to open the accounting period 16 of the previous year and period 1 of the current year.
- Periods of 13-16 year N
- Period to 01 year N + 1 (or other period Opening writes)
3.3.3.4. Transaction n/FIN3/OKP1_BK – opening the periods for CO postings
Open the accounting period 16 of the previous year and period 1 of the current year for CO postings – "CO Through-postings from FI",
Select Actual, execute and change the columns of the "special periods" 13,14,15 & 16 and unflag the periods: 
3.3.3.5. Transaction KEDR (for information)
Since the 1st of January 2007, Rhodia Geronazzo and Rhodia Engineering Plastics where merged into Rhodia Italia.
Following this merging Rhodia Italia used the profit center.
For technical reasons it's necessary to create a temporary derivation rule using a dummy profit center: Z006-9999 
3.3.4. I start to execute the procedure
Go to Transaction → F_IT_01 (prog. RFSUMB00)
This program creates the Batch Input files for posting the closing and openning entries.
Select the following variants of 8090:
NOTE: We need to execute each variant by the order here mentioned and one by one:
1 - 8090PL_HGRP | Income statements outside the group |
2 - 8090PL_GRP | Income statements inside the group |
3 - 8090BI_HGRP | Balance sheet accounts outside the group |
4 - 8090BI_GRP | Group Balance Sheet Accounts |
We run 1st in TEST mode, extract the reports, after checking the result we proceed with the REAL mode.
Variant 8090PL_HGRP
1 - Change the Fiscal Year: Y-1 (previous year)
2 - Tab Postings:
Parameters for Closing Postings:
Change the Posting Date and Document Date = 31.12.Y-1
(Last day of previous year)
Parameters for Opening Postings:
Change the Posting Date and Document Date = 01.01.Y
(1St Day of the Current Year)
3 – Tab Other Parameters:
Change the Text: RIPORTO SALDI YYYY
Variant 8090PL_GRP
1 - Change the Fiscal Year: Y-1 (previous year)
2 - Tab Postings:
Parameters for Closing Postings:
Change the Posting Date and Document Date = 31.12.Y-1
(Last day of previous year)
Parameters for Opening Postings:
Change the Posting Date and Document Date = 01.01.Y
(1St Day of the Current Year)
3 – Tab Other Parameters:
Change the Text: RIPORTO SALDI YYYY
Variant 8090BI_HGRP
1 - Change the Fiscal Year: Y-1 (previous year)
2 - Tab Postings:
Parameters for Closing Postings:
Change the Posting Date and Document Date = 31.12.Y-1
(Last day of previous year)
Parameters for Opening Postings:
Change the Posting Date and Document Date = 01.01.Y
(1St Day of the Current Year)
3 – Tab Other Parameters:
Change the Text: RIPORTO SALDI YYYY
Variant 8090BI_GRP
1 - Change the Fiscal Year: Y-1 (previous year)
2 - Tab Postings:
Parameters for Closing Postings:
Change the Posting Date and Document Date = 31.12.Y-1
(Last day of previous year)
Parameters for Opening Postings:
Change the Posting Date and Document Date = 01.01.Y
(1St Day of the Current Year)
3 – Tab Other Parameters:
Change the Text: RIPORTO SALDI YYYY
3.3.4.1. I Execute in Test Mode the Batch input
Execute one by one in test mode the variants:
DO NOT Select Create Batch Input Update Run and Hold processed session.
Extract the reports and copy to excel file:
3.3.4.2. I Execute in Real Mode the Batch input
Execute the variants in real mode to create the batches in SM35.
SELECT Create Batch Input Update Run and Hold processed session.
4 batches in SM35 are ready to run.
(Note: you need to run them in the order mentioned before)
Variants Errors
Bellow Listed types of errors to be manually processed during the execution of Batch Input files.
Common Errors while processing Batch-input | Solution |
Movement type field mandatory Pour certains comptes, cette zone est rendue obligatoire via une procédure de validation FI | Fill the area with the "F99" value corresponding to the code used for occasions. |
Partner company code | This information will be populated with the value corresponding to the Company being treated .Ex. : 77436 pour la société 7743 Rhodia Siliconi |
Value Date Mandatory Mandatory for bank accounts | Closure period (31/12/NN) |
Baseline Date Mandatory Mandatory for 3rd parties accounts with code CGS | Closure Period (31/12/NN) |
VAT CODE Mandatory to insert the VAT code for Suppliers and Customers accounts | Codes to use : 1G for VAT collective (Customers) |
Use Profit center: Z006-9999
Others Errors may appear during procedure and could be similar to the one's that happen in PF1, check variants error for PF1.
3.3.5. I perform the final postings
Execute manually the posting template.
Supporting file is available in appendix of this procedure.
3.3.6. I ensure consistency of data
After all the steps are done, we need to:
1 - Check the consistency and to reverse ALL the changes that we did before.
2 - Reverse all the changes done before
3 - Close the periods (OB52 and n/FIN3/OKP1_BK)
3.3.7. I perform the final validation
Compare the heading L12800 form report GR55 → Z4F1 with January BFC
