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: 1. Enter the Domain identified in OPD matrix (for Country specific operations, Domain = Country Accounting)

Responsibility area: 2. Enter the responsibility area described in OPD matrix ("N/A" for Country Accounting Operations)

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

EMEA


ERP

4. Remove the icon(s) when not applicable

PF2

WP2



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

The purpose of this process is to revalue/remeasure at the month end, the monetary items posted in foreign currency in the functional currency of the entity.

This process has to be performed during the monthly closing in D+1 on the EMEA entities

 

1.2. Scope

EMEA entities in PF2 and WP2


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

The revaluation process should be performed after the last IBA run in D+1



3.1. I run the revaluation for PF2 EMEA entities

3.1.1. Run the revaluation variants by country

We select each job by country and run on the transaction F.05 in PF2 the different variants indicated on the notes: 

 

3.1.2. Validate the batchs on the transaction SM35

After run the variants on the previous steps we need to verify if all the batchs were processed or we need to process them manually

On the SM35 we select the Sess: "Reval" and will appear our batchs created by our user:


Then we need to select "process" and then select the option: "display errors only":


After that, the postings of the batch are processed.

However, we can have some possible errors while process the batch:


a) If in the the account appears the text: " <2450000000REVENU> - we need to replace the text by "7540000000"

b) If in the the account appears the text: " <2450000000EXPEN.  > - we need to replace the text by "6540000000"

Note: The other counterpart of the posting should not be changed, just the errors on the 1st part of the posting as the examples above.


c) If the account is blocked we select inside the batch the option: system→Services→Batch Input→Next Transaction:


After process all the batch we select the batch and the locker with lock date: 31.12.9999 as the example below:


If you make a mistake correcting the batch, use /bend and press enter to go back to the SM35 screen:


In the end we check if SR documents are posted on the different entities between: last day of the month and the 1st day of the next month.


3.2. I run the revaluation for WP2 EMEA entities

3.2.1. Run the revaluation variants by country

 


Select each remote job in the option: "Schedule Tasks Using Time Dialog" and each batch will be processed automatically:

3.2.2. Validate the batchs on the transaction SM35

 After run the variants on the previous steps we need to verify if all the batchs were processed or we need to process them manually

On the SM35 we select the Sess: "Reval" and will appear our batchs created by our user:

 


Then we need to select "process" and then select the option: "display errors only":

 After that, the postings of the batch are processed.

However, we can have some possible errors while process the batch:


1) Reval Bank accounts (accounts that starts with 5*)

Example:

a)  If in the the account appears the text: " <51000914EXPEN.  > - we need to replace the text by  "98622200"

b)  If in the the account appears the text: " <51000914REVENU.> - we need to replace the text by "98622210"


1) Reval Other accounts (all the accounts except the 5*)

Example:

a)  If in the the account appears the text: " <21900200EXPEN. > - we need to replace the text by  "98622000"

b)  If in the the account appears the text: " <21900200REVENU.> - we need to replace the text by "98622004"

c) Accounts that doesn´t find (example 40100129) → replace with account 40100109

d) Transaction type error: Select→F32


e) Missing cost-center:

Reval 8485 → Cost Center: 8485-8390

Reval 3919 → Cost center: 3919-8390

Reval 6771 → Cost center: 6771-4700


If you make a mistake correcting the batch, use /bend and press enter to go back to the SM35 screen:


In the end we check if SR documents are posted on the different entities between: last day of the month and the 1st day of the next month.


3.3. Inform teams that revaluation process is finished for both systems


After we validate that all batchs were processed in both systems and all the errors were corrected we can process the following remote job:


The task will send the automatic email to the respective teams to inform that the revaluation of EMEA entities is completed:


End of document.