Version
Date
Description
01
14/12/2015
New Document
Authorizations & Roles
Author(s) | Verification | Approval |
Marta Pimenta | Diann Shiver | Didier Rifflet |
09/05/2015 | 04/12/2015 | 14/12/2015 |
07/08/2020 Inês Brandão Finance Operations Operator | Susana Sénica | Susana Sénica |
Version | Date | Description |
01 | 14/12 | New Document |
| 02 | 07/08/2020 | Minor Change |
Version Control
Table of contents
1 Objective and Scope
1.1 Objective of this Procedure
1.2 Scope
2 Reference Documents
3 Definitions
4 PROCEDURE
4.1 Executing the transaction
4.2 Checking working capital postings without Business Area
4.3 Run ZZF_GSBER_BREAKDOWN
4.4 Correction of errors
4.5 After performed the breakdown
5 Appendix
The purpose of this document is to describe how Finance Operations can check if Working Capital specific headings are lacking Business Area.
This handbook contains:
This operating procedure (OP) applies to ERP Solvay environment.
N.A.
PRS: In the current document, "PRS" means "SAP reference environment".
PF1: In the current document, "PF1" means "ERP Solvay-production environment".
Working Capital: The working capital is the total of:
SBS: Solvay Business Services
BFC: Business Financial Consolidation
BA: Business Area
BU: Business Unit – (Reflect via BA Code)
FO: Finance Operations
Why the Working Capital has to be posted by Business Area: This is a Reporting procedure that the Working Capital can be analyzed by Business Unit ("Division" in BFC, BA in SAP). In the ERP, the Business Area helps determine the BFC Division.
Who is responsible for providing the information: This an ERP process, run every month during the Closing operations that will post corrective documents to align Business Area in the reporting. The fine tuning of this process is under the responsibility of eachLocal Accounting Team.
Who is responsible of checking Business Areas: Finance Operations is responsible of performing the launch and check of the accurate allocation via the transaction detailed below.
What to do in case of errors: In case of errors, the concerned Local Accounting Team has to be informed: they will have to provide input to correct the related 2 tables (ZZF_BFC_BDGSB and ZZF_BFC_COGSB) so the transaction can correctly allocate the BA.
What to do when the checking is correct: The Finance Operations can go on normally.
Possible types of errors: Working Capital postings without Business Area.
The transaction should be launched after all the closing operations are final and no longer impacting the headings that will be reclassified.
The transaction can be executed via SCMA Program or manually.
Transaction code: ZZF_GSBER_BREAKDOWN
In the "Others sections" we define the heading of the posting detail – Period, Doc type.
The Account is not considered as this is just a technical indication. The accounts that the transaction will read are in the table ZZF_BFC_WKACC (see detail in next section).
The outcome of the posting should always be a posting in M and a reversal in M+1.
If periods are closed, the transaction will launch only one of the entries generating further mismatches. This is also applicable for year end.
So in example above we see the posting in M and reversal in M+1 detailed by allocation of BA.
The outcome of the posting will be a number of accounts without parameter
And at the end on the screens the documents posted and reversed in the following month.
Run transaction GR55 in PF1. Enter Z4F2 in the Report Group field.
Run the Report by clicking on 
.
Fill in the following information:
Then click again
In the report:
Checking the result: The report is displayed. Ensure Heading by Heading associated to breakdown, if the value is zero or is blank.
Remarks: The Headings that need to be checked are the following:
The "breakdown" program is not to be used for headings A41100 and L40100.
If headings are extracted with "blank" BA or wrong BA there will be converted through table ZZR_REPO_DIV_EXC.
How to perform the check: Correct wrong or missing business area for working capital allocation. It can occur that the BA used in the document was a wrong one or that this information was missing. In this case, at the end of the month, it is necessary to allocate automatically the amount concerned to the good business area in order to be able to send the correct data to the BFC database.
(Note: Technical name to launch program in SCMA is ZZF_BFC_GSBER_BREAKDOWN)
What tables to update: Transaction ZZF_GSBER_BREAKDOWN is based on the standard BFC tables and on 3 specific tables managed by SBS/IS: (ZZF_BFC_BDGSB for Business area breakdown; ZZF_BFC_COGSB for Business area by company; ZZF_BFC_WKACC to link items between Headings and GL account for heading reclassification - 8BA******).
For each Heading associated with the breakdown please check which BA is associated with the Heading in the tables.
How to see the tables: Run Transaction SM30 to check the company code by heading and Business area.
Table: ZZF_BFC_BDGSB
This table provides detail by company and heading – where a one to one or multiple allocation can be defined (example company 0005 is allocating proportionally to different BU for A37000 when no BU exist – Blue highlight). Or can define from one BU to another fully (Red Highlight).
Table: ZZF_BFC_COGSB
This table is where we define the accurate BU for each company. Keep in mind we have companies with multi BU (Example 0005) or single BU (example 0003).
This table should be updated at any change in the company perimeter of Business Units (entries or exits of BU).
Table: ZZF_BFC_WKACC
This table is where we define the headings and technical accounts to be launched via the program. As mentioned in section 4.2 we will not reclassify L40100/A41100 (void in this table). Whenever a new heading of Balance Sheet should be considered for the transaction the technical account should be present in this table.
N/A.
End of document