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: Treasury Accounting

Responsibility area: Ensure the interest on IBA calculation.

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

Please remove the icon when not applicable.


ERP

4. Remove the icon(s) when not applicable

Please remove the icon when not applicable.
Frequency

5. Remove the icon(s) when not applicable

Please remove the icon 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 Form name



Attachments

8. Add the link to attachments or external links




Previous operation << >> Next operation



1. Objective and Scope

1.1. Objective of this Operation

WHY - Describe the objective of the operation

Ensuring that the intercompany interests on IBA are calculated accurately on a timely manner and providing affiliates with their interests notes in order for them to record it in their accounting (entities non under PI1)


This process is required on a monthly basis on Day -1.


1.2. Scope

Detail the scope (legal entities, etc.)

This procedure is under the responsibility of the SU Treasury Accounting team who also needs to ensure the replication in the affiliates. It applies to:


Code

Entity 

Country

0231

Solvay SA treasury Department

Belgium

4044

Solvay Finance America

US

5854

SOLVAY FINANCE IRELAND UNLIMITED CO

Ireland

2. Definitions

Definitions should be added in the Finance Glossary - Add definition and link it to respective Letter in Finance Glossary 

See Finance Glossary:

  • IBA - Internal Bank Account

  • PI1 - SAP Treasury Production System

  • BOIC - Business Object Intercompany Consolidation

  • Spool - SAP extract


3. Tasks description

WHAT and HOW - Main content of the operation

The content should be mainly organized in 2 levels of Headings to ensure a proper link with the Table of Contents.

Select the level of heading in the "Paragraph" option.

3.1. I perform the sending of the interest calculation.

3.1.1. I run ZZF_READ_OUT

Run transaction ZZF_READ_OUT. In this step, the transaction will send the information of the interests previously calculated to post in the different ERPs – we may have a relay calculating in PF1 and affiliate in WP1. This transaction will send out the information of items to post. Purpose is to ensure completeness of the mirroring process in the affiliates' books.

In company 0231 it releases to other systems, variant INT_REPLICAT.

 


For 5854 and 4044 use variant INT_REPL 4044 & INT_REPL 5854.

After this, use the same transaction to transfer via IBA, by choosing variants:

INT_IBA_4044 & INT_IBA_5854.


3.2. I post the interest calculation in the affiliates' system.

3.2.1. I run ZZF_READ_IN

Run transaction ZZF_READ_IN. In this step, the transaction will receive the information to post in the different ERPs (in the Affiliates' side) – Execution to be ensured in PF1, and WP1. This transaction will post the interests in the affiliates' books.

These variants allows the transfer of all data: INT_REPLICAT & INT_IBACICC.

Please run these 2 variants and then use the following one to check if there are no error message:  SBS_AFF_I (please keep inside 2 companies 0020 and 4265, financial relays).

If there is an error message, we need to check the reason. If the message is saying period is closed, we can reopen the period for the specific accounts and re-run the 2 Variants.

If it is a technical error, need to contact IS Team for investigation and correction.


3.3. I generate the Interest Notes to affiliates using Z3CTB / ZINTERET / Sending Interest notes in background and monitor with SM37.

3.3.1. I Run Z3CTB/ZINTERET

The Interest Notes can just be sent after all IBA statements have been generated.

Run Z3CTB and transaction ZINTERET.


Click on "Sending interests notes".


The following screen will appear – insert the company code 0231 / 5854 (one by one) and Enter. The information will be filled in automatically.

Update the sender email if needed, in general there should be SU Treasury Accounting Team Freshdesk email: IHB.accounting@solvay.com



Insert the address image.archive@solvay.com in the “Send a copy to” field (this is a general mailbox, where we keep all the notes, could be used during the audit period or general affiliates' requests).


Start the program in Background.

3.3.2. I run Z3CTB/SM37

Monitor progress via transaction Z3CTB/SM37.


3.4. I post the interests in the affiliates ERP

3.4.1. I run ZZF_READ_IN in PF1 and WP1

Run transaction ZZF_READ_IN, in PF1 and WP1, using parameters below and make sure to select the documents that come from PI1 (D3 documents).

 

If the the interest program needs to be run again, when performing this step in PF1 and WP1, make sure to select only the new documents posted in PI1 to avoid having duplicated postings.

...

End of document.