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, new_zealand, emea_transversal, apac_transversal

    • 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. Name the title of each section using OPD methodology naming convention - Infinitive verb without the “to”, mainly action verb...something) - " I do something..."

5. Once the description of the operation is completed, ensure it is approved and published by launching the SBS-Finance approval workflow 


Domain: SU Financial Accounting / Central Finance Processes & Compliance

Responsibility area: Ensure figures reporting

Table of contents 

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


Scope

3. Remove the icon when not applicable

ERP

4. Remove the icon(s) when not applicable

Frequency

5. Remove the icon(s) when not applicable

 

References

6. Add the link to SAP transaction(s) (when it exists)

ZZF_BFC_COLLECTIVE

ZZF_BFC_CONVERSION

ZZF_BFC_TRANSFER

ZZF_BFC_LIST

ZZF_BFC_FI_FLOW_AN

ZZF_BFC_FI_FLOW_VA

ZZF_GL_BFC_OVERVIEW

ZZF_BFC_BS_AA_LIST

ZZF_BFC_CUSTOMIZING

Forms

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

Attachments

8. Add the link to attachments or external links

 

I identify the SAP reports and matching information in BFC Interface << >> I identity the differences between the BFC interfaces from PF2/PI2 and WP2 systems



1. Objective and Scope

1.1. Objective of this Operation

The goal of this operation is to have all the necessary configurations in the BFC related tables and sets correctly updated, in order to have the SAP/BFC interface working properly.

 

1.2. Scope

The scope of this operation is a worldwide scope, for all Entities using  PF2, PI2 and WP2 systems and accounting systems.

2. Definitions

See Finance Glossary


3. Task description

3.1 I identify the relevant transactions while handling BFC interfaces



From the user’s point of view:

ZZF_BFC_COLLECTIVE – To extract data from SAP into the tables


ZZF_BFC_COLLECTIVE – To extract data from SAP into the tables

Here you can find the origin of the information:

Y - A/P line items;

X - A/R line items;

B - GL Balance;

V - GL line item;

W - GL line items special flows;

M - GL balance assets w/o AA

N - GL item assets w/o AA

T - AA Assets

A - AA shares

O - COPA P&L statement (in PF2 case)

Main options (depending on the need on perimeter, family fiscal year, month and company code)

Output

Output data to ALV - just to be visualized; WITHOUT uploading the results in table "ZZF_BFC_XXXX

Output data to database - to have the outcome integrated in the database - upload the data directly to table "ZZF_BFC_XXXX".



ZZF_BFC_CONVERSION – to control origin extraction, convert data to value and format for BFC tool and post rounding differences;


ZZF_BFC_CONVERSION – to control origin extraction, convert data to value and format for BFC tool and post rounding differences;

Main options

The same options should be used as in ZZF_BFC_COLLECTIVE

Options

Step 1 - Control

Step 2 - Conversions (selected automatically)

Step 3 - Rounding amounts

Every time ZZF_BFC_COLLECTIVE is run, this transaction must be run too. ZZF_BFC_CONVERSION must be run after ZZF_BFC_COLLECTIVE and before ZZF_BFC_TRANSFER.

Additionally, inside the transaction you will be able to display the columns that were converted:

Green = Data transformed;

Also the conversion time is displayed.


ZZF_BFC_LIST – To display all data currently in the tables

You can select the origin you need. To ease the search in case of need, here are some guidelines on how to find the figures through SAP transactions:

Y - A/P line items; - FBL1N (and FBL3N for BS manual accounts)

X - A/R line items; - FBL5N (and FBL3N for BS manual accounts)

B - GL Balance - FS10N

C - AA assets balances (WP2) - executed via transaction AA BFC program

D - AA assets flows (WP2) -  - executed via transaction AA BFC program

R - COPA P&L statement  (WP2) -  executed via transaction COPA BFC program

V - GL line item; FBL3N

W - GL line items special flows; FBL3N

M - GL balance assets w/o AA FBL3N

N - GL item assets w/o AA FBL3N

T - AA Assets FBL3N

A - AA shares AR02

O - COPA P&L statement (in PF2 case) . KE30 or KE24

P - PCA - origin P is no longer used (confirmed)




ZZF_BFC_TRANSFER – To generate the file to be uploaded into BFC


ZZF_BFC_TRANSFER – To generate the file to be uploaded into BFC

This transaction is used to generate a ".CSV" file with the data previously extracted, to be uploaded into BFC interface.

You can make Multi-Company transfers by selecting "several companies in one file" and also restrict the headings.

The document will be generated with extension ".CSV".

Therefore, in case you want to edit this file, you should do it with ".txt" format.




From the BFC interfaces specialist’s point of view:

ZZF_BFC_FI_FLOW_AN- Flow Analysis 


This transaction retrieves the GL account assignment to the BFC heading and the flows throughout the Fiscal Year. 

It is used for Provisions and, due to that, the scheme to be selected should consider the flows and the origin: SA0F, origin V or W.

If there are documents posted without the mandatory transaction type, the sum of the amount will be available in column FLOW_CONTR (flow control).




ZZF_BFC_FI_FLOW_VA - BFC Flow Variances 

This transaction retrieves the GL account assignment to the set of accounts and the flows variations throughout the requested period. For the flows, you may select the transaction type or the assignment (mainly for Germany).



ZZF_GL_BFC_OVERVIEW - GL/BFC Headings Assig 

This transaction retrieves the GL account assignment to the BFC heading and the opposite, as well as other relevant info:

  • Set name;
  • PL or BS account;
  • Personnel costs (statistical headings);
  • Text in EN and additional language;
  • COCA deletion, blockage;


You can also check the GL accounts created at company code level, as well as display accounts that haven’t been replicated yet.

The green lines mean that the GL account is created at company code level.



ZZF_BFC_BS_AA_LIST - BFC interface - AA Assets extraction (PF2)

This transaction retrieves only AA headings.

ZZF_BFC_CUSTOMIZING - BFC customizing 


The correspondence on transaction type from AA and FI are available in ZZF_BFC_CUSTOMIZING AA - Assets specifications (AA)



ZZF_BFC_CUSTOMIZING

This transaction is like a cockpit for the BFC Interfaces. It is defined

into two big clusters of Maintenance:

1st cluster: Main - it is related to tables that are used in the Interface process; these tables are also used for other purposes;

2nd cluster: BFC Main - it is related to the maintenance of the BFC specific tables like the perimeter, flows, sites, divisions, regions by country, profit centers and markets;

In the 2nd cluster, there is also a split between what is

  • BFC process itself;
  • BFC families
  • Conversion



The ZZF_BFC_CUSTOMIZING is common to PF2 and WP2 systems.