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: Country Accounting



Responsibility area: N/A


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

(please delete the icons not applicable)(error)

Frequency

5. Remove the icon(s) when not applicable

 

References

6. Add the link to SAP transaction(s) (when it exists)

ME23; KSB1


Forms

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

(add here the link to the templates when you upload them in AODocs)(error)


Attachments

8. Add the link to attachments or external links



Previous OP << >> Next OP



1. Objective and Scope

1.1. Objective of this Operation

This procedure explains how we can manage the amounts vendor INSPIRUS, LLC.

The jubilee costs are coming through from a P card purchase with the vendor INSPIRUS, LLC. 


1.2. Scope

This procedure is applicable for 4045,3384, 4290 and 4291.


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 jubilee costs are coming through from a P card purchase with the vendor INSPIRUS, LLC. We need to reclass these costs to the accrual account of 4090100002 with transaction type F35.

The accrual for 4291 needs to be posted on 4290.

3.1. Responsibilities

SBS Responsibilities:

SBS-RTR OPS (please change RTR, it is no longer applicable)(what do you mean by OPS?)(error) is responsible to handling the PO for Inspirus, the items should be reclassified until D+1.



3.2. I receive the case from salesforce (salesforce is not used. Do you mean Freshdesk?)(error)

Go to transaction ME23 with vendor 2101519 to check if there is new purchase order then updated the table below with new PO.

Transaction ME23 then press F4 for searching.


Insert the vendor number then click on button .


It will show all the POs for the vendor number.


SPTH

ST3

25.09.2008

F

NB

4510914379

SPTH

ST3

19.02.2009

F

NB

4510982241

SNHN

SHA

01.01.2010

F

NB

8345497922

SNHN

SHA

01.01.2010

F

NB

8345498551

SNHN

SHA

01.02.2010

F

NB

8345534633

SRAL

SAC

21.06.2010

F

NB

8345550947

SCLV

SL2

23.07.2010

F

NB

8345554391

SCPC

SP1

14.10.2010

F

NB

4511254851

SCGR

SGE

18.10.2010

F

NB

4511256726

SCLV

SL2

11.01.2011

F

NB

4511306814

SNHN

SHA

14.01.2011

F

NB

4511309573

SRAL

SAC

05.07.2012

F

NB

4511639804

SCLV

SL2

13.02.2013

F

NB

4511790294

SNHN

SHA

17.03.2016

F

NB

4512609624

SNHN

SHA

17.03.2016

F

NB

4512609625

SNHN

SHA

17.03.2016

F

NB

4512609626

SNHN

SHA

17.03.2016

F

NB

4512609627

SNHN

SHA

18.03.2016

F

NB

4512610606

SNHN

SHA

18.03.2016

F

NB

4512610609

SNHN

SHA

24.03.2016

F

NB

4512614474

SNHN

SHW

16.12.2016

F

NB

4512792047

SFAO

SCD

11.09.2017

F

NB

4512969833

SNHN

SHA

12.09.2017

F

NB

4512970781

SNHN

SHA

12.09.2017

F

NB

4512970787

SCDP

SD1

11.10.2017

F

NB

4512991295

SNHN

SHA

12.12.2017

F

NB

4513032918


4290 and 4291 Purchase orders

4290

4511254851

Z716200000

4290

4511306814

R016400000

4290

4511790294

R016400000

4290

4512970787

C016200000

4290

4512991295

R916200000

4290

8345554391

R016400000


4291

4511256726

211658000500

3384

4512969833

ON16200000

3384

4512970781

NT18400001


4045

4513032918

U516400402

4045

4512792047

U516400402

4045

4512614474

U5131P0050

4045

4512610609

U516111130

4045

4512610606

U5131P0070

4045

4512609627

U516200230

4045

4512609626

U516200230

4045

4512609625

U516300202

4045

4512609624

U516112400

4045

4511309573

U516400402


After check new purchase order or new line in the PO (make sure that there is any new CCs which is listed in this procedure), please go to KSB1 with the cost center then make a sum by offsetting account 2101519.


The total amount will be reclass to GL  4090100002 with transaction type F35.

3.2.1. I perform the posting

(please upload the file in AODocs Forms, click here to know here)(error)

(please upload the file in AODocs Forms, click here to know here)(error)

End of document.