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 daily bank reconciliation process.

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

In normal course of business, entities 2232 and 4044 regularly hold foreign currency monetary items (AP/AR mainly and other GL accounts) that have to be remeasured at each closing to reflect an accurate value on the B/S in the functional currency of each entity. During the closing process, foreign currency monetary items on the B/S are thus translated into the functional currency using the closing rate.


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 (2232) and D+2 (4044).

1.2. Scope

Detail the scope (legal entities, etc.)

Entities 2232 and 4044

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

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 run the revaluation for customers' accounts.

3.1.1. For company 2232

On D+1, run the steps one by one:

Click on the right button of the mouse and schedule the task (choose Schedule Tasks using time dialog):

The process Schedule means that you are booking Revaluation.

With the second step you just check in transaction code SM35 if there is a batch blocked and to be updated and posted.

3.1.2. For company 4044

On D+2, run the steps one by one:

Click on the right button of the mouse and schedule the task (choose Schedule Tasks using time dialog):

The process Schedule means that you are booking Revaluation.

With the second step you just check in transaction code SM35 if there is a batch blocked and to be updated and posted.

3.2. I run the revaluation for vendors' accounts.

3.2.1. For company 2232

Run the steps one by one:

Click on the right button of the mouse and schedule the task (choose Schedule Tasks using time dialog):

The process Schedule means that you are booking Revaluation.

With the second step you just check in transaction code SM35 if there is a batch blocked and to be updated and posted.

3.1.2. For company 4044

Run the steps one by one:

Click on the right button of the mouse and schedule the task (choose Schedule Tasks using time dialog):

The process Schedule means that you are booking Revaluation.

With the second step you just check in transaction code SM35 if there is a batch blocked and to be updated and posted.

3.3 I run the revaluation for Bank accounts

3.3.1. For company 2232



Run the revaluation for Bank accounts – Variant 3S-2232-BNK / Schedule task using "Schedule Tasks using time dialog"

Please remember that the Variant for Bank accounts revaluation can be only updated by IS. In case you need to make the changes, please open the ticket to IS through the BMC Helix tool.


Check if the revaluation is posted:


Run variant in Test Mode.

Check if the message "No posting necessary" appears at the end of the page.

If the is no message "No posting necessary", there is an error message in red. You should check the account mentioned in the error message and investigate the problem. In the last period of time there were no error messages in this specific action.


Check the existence of batch inputs:

By this step you check if there are no blocked postings, through the transaction code SM35 you will see which account is blocked. We have to investigate the reason why it is blocked and make the necessary adjustment in posting.


3.3.2. For company 4044



Run the revaluation for:

  • Bank accounts - Variant 4044_REV_BNK / Schedule task using "Schedule Tasks using time dialog"
  • Linkage accounts – Variant 4044_REV-LIA / Schedule task using "Schedule Tasks using time dialog"


Check if the revaluation is posted:


Run variant in Test Mode.

Check if the message "No posting necessary" appears at the end of the page.

If the is no message "No posting necessary", there is an error message in red. You should check the account mentioned in the error message and investigate the problem. In the last period of time there were no error messages in this specific action.


Check the existence of batch inputs:

By this step you check if there are no blocked postings, through the transaction code SM35 you will see which account is blocked. We have to investigate the reason why it is blocked and make the necessary adjustment in posting.

3.4. I run the revaluation for Internal Bank accounts (IBA)

3.4.1. For company 2232

The principle is the same as for Specific revaluation.

Run the program with the Variant 2232-REVAL-IBA, where IBA accounts are selected.

The next step is to execute the check in SM35, if there are no blocked batches for posting.


3.4.2. For company 4044

The principle is the same as for Specific revaluation.

Run the program with the Variant 4044-REVAL-IBA, where IBA accounts are selected.

The next step is to execute the check in SM35, if there are no blocked batches for posting.


3.5. I run the revaluation for G/L accounts

3.5.1. For company 2232


Run the program with the Variant 2232-REVAL-CG, where all other G/L accounts are selected.

The next step is to execute the check in SM35, if there are no blocked batches for posting.

3.5.2. For company 4044

Run the program with the Variant 4044-REVAL-CG, where all other G/L accounts are selected.

The next step is to execute the check in SM35, if there are no blocked batches for posting.

Important: Wait for the last IBA creation on D+1 afternoon

Revaluation of IBA accounts can only be done after the creation of the last IBA statements for company 5854 (after 4044) (check with the team members the status of the respective activities)




End of document.