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

ZZF_BFC_COLLECTIVE.

ZWFA67A MAGNITUDE - Interface COPA P&L. 

ZWFA113

ZWFAT038A

SM30 ZZF_BFC_COPA_VF,

ZWFA46A > ZWFAT110 :FC/PPE Rubrics

Forms

Attachments

 

I identify the relevant transactions while handling BFC interfaces << I identity the differences between the BFC interfaces from PF2/PI2 and WP2 systems >> I identify the several tables and sets used 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  PF2, PI2 and WP2 systems and accounting systems.

2. Definitions

See Finance Glossary:

3. Task description


3.1 I identity the differences between the BFC interfaces from PF2/PI2 and WP2 systems



1.One of the differences between PF2 BFC Interfaces and WP2 BFC Interfaces remain in the CO-PA retrieve.


In PF2 PL headings retrieve is done via ZZF_BFC_COLLECTIVE.

In WP2, PL headings retrieve is done by running transaction ZWFA67A MAGNITUDE - Interface COPA P&L. 

There are also other two transactions in order to fill in the information for schedules 

L6710 acquisition by CGU and Site(transaction ZWFA113);

L6720 Fixed asset closing balance (transaction ZWFAT038A).



In WP2, P&L headings retrieve is done by running transaction ZWFA67A MAGNITUDE - Interface COPA P&L. Depending if this is a monthly or quarterly closing, selections may defer.

Only after running this transaction can the ZZF_BFC_COLLECTIVE be run and consider the P&L headings. The origin O is not selectable in WP2 environment. 



This transaction created a logical file. Via SM37, we can check the outcome by double clicking in the spool.



2. Another difference between PF2 and WP2 is that there are also other two transactions in WP2 to fill in the information for schedules:


L6710 Acquisition by CGU and Site (transaction ZWFA113);

L6720 Fixed asset closing balance  (transaction ZWFAT038A).

If the update tables is not flagged, it will only display the figures and will not be considered in the ZZF_BFC_COLLECTIVE.



3. The last difference between PF2 and WP2 is related to the tables used by SU MAC to manage the P&L headings.


In PF2, the table used is ZZF_BFC_COPA_VF, while in WP2 it is ZWFA46A > ZWFAT110 :FC/PPE Rubrics