Domain: xx

Responsibility area: xx

Table of contents 

By default the table of contents displays Heading 1 & Heading 2 (other levels can be added)

Scope


ERP


Frequency

 


References

ZZF_GSBER_BREAKDOWN

FBL3N - G/L Account Line Items

GR55 - Report Group: Z4F2

Table ZZF_BFC_BDGSB 

Table ZZF_BFC_COGSB

Table ZZF_BFC_WKACC

Forms

7. Insert the links accordingly and change the link text with the OP name


Attachments



Previous OP << >>


1. Objective and Scope

1.1. Objective of this Operation

The purpose of this document is to describe how to check if Working Capital specific headings are lacking Business Area. 

The Working Capital is the total of:

  • Value of finished goods inventories
  • Other inventories
  • Trade receivables
  • Trade payables
  • Other receivables and liabilities
  • Other long-term assets
  • Other long-term liabilities
  • Deferrals and accruals

It has to be reported by Activity 1 & 2. In PF1 the determination of the Activity 1 & 2 is done using the Business Area.

When a posting was done without Business Area or with an obsolete Business Area, it is not possible to assign the posting to an Activity 1 & 2.

The aim of this page is to provide a procedure to: 

1.2. Scope

This operating procedure applies to PF1 only and is not applicable to WP1.

2. Definitions

See Finance - Glossary

3. Tasks description

It can occur that the Business Area 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 to have an accurate working capital allocation in BFC.

This will be done by running the program ZF_BFC_GSBER_BREAKDOWN or in case of need the transaction ZZF_GSBER_BREAKDOWN.


3.1. I execute the transaction

The transaction runs by program in FCC at D3 morning after all the closing operations are final and no longer impacting the headings that will be reclassified.

All the postings performed by this transaction are reversed in the first day of the next month.

In case any errors happen, it can be executed manually by using the transaction ZZF_GSBER_BREAKDOWN

Insert:

  1. The chart of accounts: COCA
  2. The period: Year & Month
  3. The document type: SA
  4. The Account (single division): 8BAA310000
  5. The Business Area (single division): 9990
  6. Execute



3.2. I check that the job run

Ensure that 8BA* accounts are equal to zero, by Business Area.

Run FBL3N - G/L Account Line Items using the variant: 3S-BFC-Z4F2

  1. Get variant
  2. Enter variant: 3S-BFC-Z4F2
  3. Execute

In order to catch both posting + reversal, we need to run the transaction for open items on 1st day of next month

  1. Change the company code
  2. Update the date: 1st day of next month
  3. Execute

Check if the total amount of 8BA*accounts is equal to zero, by Business Area.

​Possible reasons of 8BA*accounts by Business Area not equal to zero:

The outcome of the posting will be a number of accounts without parameter:

  • Error is related to OB52: Check if 8BA*accounts are open in Z1F_OB52 for M and M+1 periods ; If periods are closed, the transaction will launch only one of the entries generating further mismatches. Reverse M+1 documents posted, open 8BA*accounts and re-run the job in FCC. 
  • Error is not related to OB52: run the program in SM37 in order to check if there was a technical problem. If yes, re-run the job, otherwise report the issue to Service Unit Finance Accounting GL.



3.3 I check working capital postings without Business Area

Run transaction GR55 in PF1.

  1. Enter Report Group: Z4F2
  2. Execute

  1. Enter the period (Year & Month)
  2. Enter the company code
  3. Execute

In the report, select: 

  1. Reports: BFC - Bal sheet - BA (selection)
  2. Variation: Characteristics: Business Area
  3. Variation: Business Area: Business area undefined

The report is displayed

Check in Business Area undefined and the ones with ZZZZ in the text for the headings below and ensure Heading by Heading associated to breakdown, that the value is zero or is blank. 

Example of a BA that was corrected by the run of breakdown >>

The Headings that need to be checked are the following:

  • Heading A31000, A34000, A37000, A39100, A39400, A39700 and L40800 for schedules L6725 (External Payables and Inventories)
  • Heading A49100 and L41160 for schedules L6735 (External receivables).

The "breakdown" program is not to be used for headings A41100 and L40100. If these headings are extracted with "blank" Business Area or wrong Business Area they will be converted through table ZZR_REPO_DIV_EXC .

Example of a Business Area that was not corrected by the run of breakdown and needs to be analyzed >>

If some lines do not show zero or blank and no Business Area is associated with the Heading in the tables please inform the Controlling team, asking the missing business area. 

All unsolved Business Area corrections will imply Blocking controls in BFC Headings related to Working Capital.



3.4 I request the update of specific tables to correct the errors

The transaction ZZF_GSBER_BREAKDOWN is based on the standard BFC tables and on 3 specific tables managed by GBS Finance Service Line

Tables maintained by SU MAC Data Expert

  • ZZF_BFC_BDGSB for Business area breakdown
  • ZZF_BFC_COGSB for Business area by company

=> Go to Rules - PF1 - Working Capital - Activity 1 & 2 for more information regarding these 2 tables. 

The table ZZF_BFC_WKACC is maintained by SU FAC. It links items between Headings and GL account for heading reclassification - 8BA******)

You can run Transaction SM30 to display the table ZZF_BFC_WKACC

This table is where we define the headings and technical accounts to be launched via the program. As mentioned before, we will not reclassify L40100/A41100. Whenever a new heading of Balance Sheet should be considered for the transaction the technical account should be present in this table.


3.5 I repeat the check after corrections are done

Once the table is updated, run transaction ZZF_GSBER_BREAKDOWN to add the missing Business Area.

After performing the breakdown, repeat the check in step 3.3