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 


Scope

ERP

Frequency

References

SM30 - Tables

ZZF_BFC_SCH_DIM

ZZF_BFC_CALCUL

ZZF_BFC_COMPANIE

ZZF_T001_MGT

ZZF_BFC_SITE

ZZF_CALA_SITE

ZZF_BFC_HEADING

ZZF_BFC_SETACCT


GS03 - display sets

ZFC-FL-602

Forms

Attachments

 

I identity the differences between the BFC interfaces from PF1/PI1 and WP1 systems << I identify the several tables and sets used in the BFC Interfaces >> I identify the several families and schemes in the BFC Interfaces



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  PF1, PI1 and WP1 systems and accounting systems.

2. Definitions

See Finance Glossary


3. Task description

3.1 I identify the several tables and sets used in the BFC Interfaces


Relevant tables to be visualized via SM30

A table is a set of rows. Each row in a table has the same number of columns and contains a value for each column.

Eg.:

  • SM30 - Table BFC Schemes ZZF_BFC_SCH_DIM 
  • SM30 - Table ZZF_BFC_CALCUL 
  • SM30 - ZZF_BFC_COMPANIE


A set is “used to group data and to define data hierarchies. A set links together specific values or ranges of values under a set name.

The sets can be viewed via GS03

Eg.:

  • GS03 - ZFC-FL-602




Management responsibilities for all tables are split among different teams being that SUFA GL manages the following:

  • ZZF_T001_MGT
  • ZZF_BFC_COMPANIE 
  • ZZF_BFC_SITE/ZZF_CALA_SITE
  • ZZF_BFC_HEADING
  • ZZF_BFC_SETACCT

 

  • ZZF_BFC_SCH_DIM Dimension by scheme, DT responsible to update with input from SUFA GL.


ZZF_BFC_HEADING

In this table, SUFA GL updates the list of headings to be considered in a concerned family.



ZZF_BFC_SETACCT

In this table, SUFA GL links the families, schemes, headings, origins, set of accounts, signs and flows.



Take as example heading L45800, for scheme SA0F, only the flows in set of flows ZFC-FL-024 are acceptable to BFC upload.


...


End of document.