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: Central Finance Processes & Compliance

Responsibility area: Coordinate the document types management

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

Spot requests


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 aim of this operation is to describe what to take into consideration when it is requested a new document type or the deletion of an existing document  type.


1.2. Scope

To be applied for PF1,WP1 and PI1 ERP systems.


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 receive a request for a new document type to be created and I assess it

3.1.1. I receive a request for a new document type and I assess it


After receiving  a request for the creation of a new document type, I must assess:

  •         The balance between the benefits of the creation vs constraints/costs on maintenance; (if the benefit of having the new document type is less than the workload of maintaining it, it should not go further);


o   To meet this, the request must have a clear explanation on the need for this improvement

  • If the new document type segregates business transactions;
  • For which processes will it be used?
  • if we can reuse or use an existing document type? If not, why not?
  • for which systems will this new document type be used?
  • for which countries or companies codes will the new document type be used? If it is to be delimited?
  • If the new document type is directly linked to account types (vendor/customer or GL accounts) and if it can determine which account type to impact;
  • If the range number is well identified. It is crucial to  be informed of the range number because it should be aligned with the purpose of the posting itself (for instance, if the new document type is to be used for automatic postings the range should be a broader while if for manual postings, the range would be more limited)
  • If there is a validity period.


If the need for the new document type is not met or if the balance between the pros and cons do not justify the improvement, I must inform the requester that the change will not proceed.

If all of these criteria are met, I should forward information to DT colleagues (at this stage still IS GAC team in Service One).

3.1.2. I request DT to create a new document type

.


3.2. I receive a request for deletion of a document type and I assess it

3.2.1. I receive a request for deletion of a document type and I assess it

3.2.2. I request DT to delete an existing document type

...


End of document.