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: Costing



Responsibility area: Ensure Costing Allocations


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)

FS10N; GR55; KE30; KE21N; F.01; GR55


Forms

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



Attachments

8. Add the link to attachments or external links




Previous OP << >> Next OP




1. Objective and Scope

1.1. Objective of this Operation

The goal of this operation is to guarantee that, at the end of each month, the results in FI match with the ones in COPA.


1.2. Scope

Finance Operations performs and checks the reports, takes the necessary actions to guarantee that FI-COPA difference equals 0 at the end of the month during closure. They perform the necessary corrections based on defined and approved instructions and the necessary internal controls.


2. Definitions

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

See Finance Glossary:


3. Tasks description


3.1. I run the FI report "net result"



Go to transaction GR55, report Z4F1. Update the company code, the period, and check the result in heading L12000:



Go to transaction FS10N. Update the company code, the year, and check the result for all BS 98* accounts:



3.2. I run the CO-PA report "net result"




Go to transaction KE30, report ZZZ-SOLV00. Update the company code, the period, and check the result in the Net Result:




Go to transaction KE30, report ZZZ-SOLV00. Update the company code, the period, and check the result in the Net Result:


3.3. I compare both results


Both amounts must match.


3.4. I analyse the reason of the discrepancy and take the corresponding corrective action













All postings done directly in COPA should be avoided. If possible, all necessary corrections must be done in the original CO object.


Anyway, several times it's necessary to make these postings, and therefore we need to guarantee that the total impact in PL of those postings is 0 (or that they were posted to correct already some discrepancy coming from FI - example: from Z1K_Reconciliation).


Go to KE24 and search for manual postings (record type = Z):


All postings that we find should have a total amount 0:

  • In the same value field - transfer of characteristic (profit center, product, customer, etc)

  • In different value fields - transfer of value field (example below)






SBS-OP-DRTR-02-052 - I perform the FI/CO reconciliation of net result




3.5. I perform a direct CO-PA posting in PL (KE30), in case of impossibility to correct automatically the FI/COPA discrepancy





3.6. I properly check the result of the posting


After correcting all differences, re-check the results in FI and in COPA to guarantee that the postings were correctly made, and that the difference doesn't exist anymore.


Also it's necessary to remark that, after the closure, all differences not corrected properly must be analyzed and corrected in the origin:

  • New materials should be costed before being used (delivery, production, billing)
  • New orders or WBS elements should have a settlement rule
  • New cost centers should be included in the assessment cycles
  • Blocked invoices in VFX3 should be processed everyday
  • Avoid returns with stock movements in different periods of the corresponding credit memos. 





https://wiki.solvay.com/pages/viewpage.action?pageId=18681437


Important: Please note that the following amounts must be added to the result of the COPA report KE30 as they concern manual corrections:

  • Manual Postings in account 98350050 with cost center XXXX-9200 (XXXX stands for company code);
  • Manual Postings in COPA derivation accounts 98154199, 98258199 and 98254199;
  • MR11 postings in account 98150363 (documents beginning with  48*).


End of document.