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


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



Attachments

8. Add the link to attachments or external links


 

 

Previous operation << >> Next operation



. Objective and Scope

1.1. Objective of this Operation

WHY - Describe the objective of the operation

 

1.2. Scope

ww


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

How do give access to end user according to role.

3.1. I receive the request

 Usually we are going to receive this kind of request:



I need to user code, the responsibility group and the system.


This access allow the users to see which accounts should be reconcile to your role.

3.2. I release access for responsibility groups.

I go to /n/bsar/menu on Master Data option:


I select Responsibility group; 


I select the current period and run;



I choose the Responsibility group to release the access;


I click on New;


I update with the user code and the role:


About the roles:

REC  - Access to the people whom will perform the conciliation.

REV - Access to check the accounts after closed, can be release to Leaders or experts in the process.

OWN - This role, is just to see the accounts but without access to edit, I usually does not give this access.

COO -  Master access, just for coordinator users.


After that, I save the information


3.3. I release access for PXY

This access allow the end users to see the automatic reports created on ARA by this process.


I go to /n/pxy/rb0 and click on menu;


I go to Master Data, select Define Users and run;


I click on New;


I include the user code, click on insert details and save;

After that click on New:


In the next box I select  Operator, View, Teams and save;



Go back to the previous screen on master data and select Define Teams;


Click to edit the Default line;


I click on new:



I include the user and save the data;


I save again:


This way all access were released.




End of document.