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

    • 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. Once the description of the operation is completed, ensure it is approved and published by launching the SBS-Finance approval workflow 




Domain: Finance Data & Reporting



Responsibility area: Ensure consistency of Reporting axis


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)


Forms

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


Attachments

8. Add the link to attachments or external links



Previous OP << >> I update the necessary tables for the new BFC activity 1/IECRA implementation



1. Objective and Scope

1.1 Objective of this Operation


In WP1 ERPRCS , the main reporting axis, the “BFC Activity 1” (market axis) and “BFC Activity 2” (industrial axis) are represented by IECRA for activity 1 and value stream for activity 2.

It is materialized in the system by DC x DIV link to one IECRA (basis of the structure) for activity 1 and the value stream in the profit center hierarchy for activity 2.

The description of the process of defining Reporting axes in the systems linked ERPRCS can be divided into 5 sub-processes, for an easier understanding:

  • New “BFC activity 1”

  • New IECRA in an existing Activity 1

  • New implementation of an existing activity 1 ERPSOLV in ERPRCS

  • Reorganization of reporting elements “below activity 1”

  • Update of Group structure “above activity 1”. 

In the ERP RCS, the “BFC activity 1” is representing the level of analysis validated with the GBU controllers to analyze the sales, the level of BFC reporting for Accounts receivables and P&L.

All the structure implemented by Data administrators and IS Structure can be displayed in SAP transaction (ZWFAR571) combination of axis managed at GBU level (Data administrators) and tables updated to link SAP codes to BFC codes.

It is mainly materialized in SAP by:

  • One DC (distribution channel) used in the Sale x division (product division) in the material link to an IECRA link to one activity 1

  • IECRA for postings linked to P&L assessment cycles 

  • IECRA for A/R determined in reporting BW with the sale account in counterpart of the posting


For the operations linked to the sales, iecra is determined by the combination of distribution channel (market) x division (product). 

For FI postings IECRA is not in the posting but determined with the counterpart accounts (P&L). For manual postings B&S to B&S accounts the profit center will be inserted manually in the posting to be able to determine the activity in the reporting. Table ZWFAT205 can also be updated in case of we forget to enter the profit center in the posting when the field is open for the account.

Scheme to determine activities 1 for accounts receivables 


For postings through cost objects→ Cost centers: IECRA in assessment cycles 

1.2 Scope

This procedure covers the implementation of a new BFC activity 1 in SAP WP1.

2. Definitions

See Finance Glossary:


3. Tasks description

3.1. I receive the information that a new BFC activity 1/ IECRA has been implemented


All requests for data under the responsibility of Finance Data & reporting must be made through the “MDWF” workflow.


For complex changes and topics, there are usually several preliminary contacts and the workflow is created when the solution has been designed and agreed.


In terms of reporting axes, the information can also be provided by an email from Corporate Controlling. 

3.2. I analyze and validate the information provided in the request 

3.2.1. Global process

The introduction of a new “activity 1” is requested by the GBU and formally accepted / decided by Corporate controlling, who assign its code in BFC. 

After Corporate controlling approval, corporate controlling & the GBU (administrators or contact defined for the GBU needs to communicate to Finance Data the necessary elements in order to implement changes in the ERP’s.

3.2.2. SAP Objects

A “BFC activity 1” involves the following WP1 SAP objects:

  • IS Structure Data creates link Distribution channel (DC) x division
  • GBU data administrators (transaction ZWOC54A), create or update the link between DC x Division and the chain IECRA/CDPRF/ENTRP/ZSECT.


ZSECT for the GBU 

(ZSECT00078 TECHNOLOGY SOLUTIONS)

ENTRP for the “group of BFC activities 1” 

(ENTRP00190 TECHNOLOGY SOLUTIONS)

CDPRF for the “BFC Activity 1

(CDPRF00716 PHOSPHORUS DERIVATIVES) 

IECRA for the “IECRA” - no equivalent in PRS

(IECRA01219 PHOSPHORUS DERIVATIVES) 



3.2.3. SAP implementation: roles and actors


The implementation of a new “BFC activity 1” requires the following steps:


  • Corporate controlling informs the “community” of the creation of a “BFC activity 1” with its BFC code and position in the Reporting chain.

  • Finance Data works with GBU’s administrators or with IS Structure Data when we have no administrator for the GBU and with GBU controllers when necessary to define the data needed for the new act1.

  • GBU’s administrators request with a template to IS Structure Data create new link DC x  Div in transaction ZWOC54A (freshdesk ticket) 

  • Data administrator create the structure in ZWOC54A link SD x Div to IECRA / CDPRF / ENTRP / ZSEECT

  • The GBU controller makes a request to Finance Data including the elements defined in step above or Finance Data formalizes in one Worflow the structure validated together.




CD x Div link to IECRA


IECRA link to Activity 1 (CDPRF in SAP) /ENTRP/ZSECT 




  • Finance Data analyzes the request and, if all clear and OK

    • Use transaction ZWFAR571 - class ZS2 (new year) or ZS1 (during the year) - select “RCS GBU” using the BFC code to validate that new structure appears.

  • If yes update table ZWFAT228 to link : 

    • CDPRF code to BFC activity 1 code, 

    • ENTRP code to BFC group of activities if a new group of activities has been created

    • ZSECT code link to BFC GBU code


  • For new activity1 ask to IS (freshdesk ticket) to create the new activity in KES1

And when done 


    • To be repeated for all companies quoted in the GBU document :

      • GBU doc / GBU xx / sheet “DC- Vte” and “DC Interco” to identify by Sale organization the cross DC (distribution channel) x division and sheet Soc (link sales org - company code ) to find in witch companies ZWFAT111 has to be updated or with SM30 on view V_TVKO_ASSIGN.


Example:


    • Sheet DC- Vte


    • BR33 / 9NxSB / IECRA in ZWFAR571 IECRA01219 


    • ZWFAR571 : 9NSB IECRA01219 PHOSPHORUS DERIVATIV  


    • GBU doc TS sheet Soc BR33 link to the entity 



    • So you have to create in 7523 ZWFAT111 IECRA1219 market TSDP



3.3. I update "Structure axes" table ZWFAT228

At the end of each year, the Corporate Management decide on the modifications of the group structures, in terms of Operating Segment (clusters), groups of GBU, GBU, group of activities and “activity 1 and 2”.

3.3.1. Global process

The present section only deals with the situation in which the changes are made only above the BFC Act1.

Finance Data receives this information from GAR, who communicates the required changes.

3.3.2. SAP objects


  • GBU data administrators, with ZWOC54A transaction in SAP, update the link between CDPRF/ENTRP/ZSECT and create if necessary new ENTRP code for new group of activities, new ZSECT code for new GBUs

ZSECT for the GBU 

(ZSECT00078 TECHNOLOGY SOLUTIONS)

ENTRP for the “group of BFC activities 1” 

(ENTRP00190 TECHNOLOGY SOLUTIONS)

CDPRF for the “BFC Activity 1

(CDPRF00716 PHOSPHORUS DERIVATIVES) 


The full hierarchy of Solvay Business structure is implemented in two ways in the WP1:

      • ENTRP code to BFC group of activities if a new group of activities has been created

      • ZSECT code link to BFC GBU code


    • The hierarchy of Profit centers if activity 2 has to be moved under a new ENTRP code or ENTRP code have to be move under a new ZSECT code. Be careful that IECRA code in profit center link to VS link to activity 2 must be in same ENTRP code as activity 1.

3.3.3. SAP implementation: roles and actors

The implementation of a change of organization above “Act1” requires the following steps :

  • Finance Data fixes a date for implementing the change, together with the GBU Controller and the Service Center manager (usually at the end of the year) 

  • At the given date, Finance Data implements the change in the tables and the profit center hierarchies.


3.4. I request CGI team to create the new BFC activity 1/IECRA as a new characteristic value


For new entries/codes, COPA characteristics are automatically updated.

Check in transaction KES2 if the new/updated elements are already available. 

If not, open a Freshdesk ticket to IS, asking to update it accordingly: 



End of document.