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 GBS-Finance approval workflow 




Domain: Investments & Divestments



Responsibility area: Control GBS IS Projects


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

PF2

Frequency

5. Remove the icon(s) when not applicable

  D-3

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


 


I create missing CATS report<< >> I post CATS hours



1. Objective and Scope

1.1. Objective of this Operation

  • Ensure that all data are consistent (no input is missing and it was posted always on an standard manner)
  • Ensure that the data is reliable (the controllers can trust on the financial figures)

1.2. Scope

The scope of CATS control for GBS IS is for all legal entities in PF2.

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 extract the timesheet

3.1.1. In D-3, download the CATS Monthly control of the previous month

3.1.2. Open the CATS Monthly control file and go to the tab “CADO Upload File”

3.1.3. Delete all the data from the columns without formulas

3.1.4. Run “CADO” transaction in SAP PF2 System: Display Time Sheet Data.

This transaction, extracts all timesheets details completed by users and by cost centers.

  • Click on “Sender parameters field”

  • Enter the closing month period or choose “Current Month”

  • Upload GBS Cost Center list for allocation purposes (The list is available on the Time Allocation google sheet)
  • Choose the layout “CATS GBS IS”.
  • Run the transaction (Click on    )

  • Download your result into a Spreadsheet. (List -> Save -> File -> Spreadsheet -> Generate)

3.1.5. Open the extracted file and copy the data collected to the “CADO Upload File” tab of the CATS Monthly Control.

3.1.6. Convert the networks to number format.

3.2. I extract the networks detail information

3.2.1. Run “CN46N” transaction in SAP PF2 System: Project Info System: Network Initial Screen

This transaction gives the networks parameters, including the company code associated.

  • Copy the networks list extracted in CADO and upload them in CN46N

  • Run the transaction (Click on  )
  • Change the layout in order to obtain the following fields:

- Network;
- Text
- Project definition
- WBS Element
- Network type
- Plant
- Basic start date
- Basic finish date
- Duration
- Status

  • Download your result into a Spreadsheet. (Evaluate ->Export-> Spreadsheet -> Save)

3.2.2. In the CATS Monthly control file and go to the tab “CN46N”.

3.2.3. Delete all the data from all the columns except Company code (this column contains formulas).

3.2.4. Open the extracted file and copy the data collected to the “CN46N” tab of the Monthly Report.

3.2.5. Refresh the file.

3.3. I extract Cost centers list, whenever needed

3.3.1. Verify in “CADO Upload File” tab if the column M “CoCd CC” contains errors.

3.3.2. If yes, Run “KS13” SAP transaction: Display Cost Centers: Initial Screen.

  • Put the first date of the actual year to have valid cost center at date
  • Run the transaction (Click on    )
  • Add the company code to the selection:

  • Download your result into a Spreadsheet. (List -> Export -> Spreadsheet -> Save)

3.3.3. In the CATS Monthly control file and go to the tab “KS13”.

3.3.4. Delete all the data from all the columns.

3.3.5. Open the extracted file and copy the data collected to the “KS13” tab of the Monthly Report.

3.3.6. Refresh the file (F9)

3.4. I verify if the user used the correct network to allocate the hours

  • Compare the results in the “CADO Upload File” tab


  • The NOK results, which are “not allowed by the group”, have to be corrected.
  • The column “CoCd CC” indicates the correct company code to use. The column CoCd network, indicates the network that was used in the time allocation.
  • Copy the NOK results to the tab Corrections.

3.5. I correct the network, if errors detected


  • Analyze if there are networks created for the selected project in the correct company code consulting the WBS Elements request file for the current and previous year.
  • If there is no network created for the project, inquire the controller if it is needed the creation of WBS/network or if the hours should be transferred to Recurrent Networks.
  • Go to transaction CAT2 and select the Data Entry Profile SIS-PMSX - SIS time sheet for super user:

    1. Enter the personnel number in scope and click in 

    2. Correct the network and click in the icon  to save.

    3. It will be given a message . Do not worry, just click enter and it will save the changes performed.

    4. Repeat this step to perform all the necessary corrections employee by employee.

3.6. I repeat the extractions of the timesheet and the network details until no more action to execute

If the results in the “CADO Upload File” tab are all green “OK”, proceed to the next step. If not, perform the necessary corrections until all data is “OK”.


3.7. I confirm that the settlement key control of the network is related to Projects

Run “CN47N” transaction in SAP PF2 System: Overview: Activities/Elements. This transaction extracts networks parameters to control that the projects networks are correctly settled.To differentiate a structural network of the ones generating allocation, the settlement control key of the network must be “PD01” and not “ZS01”.

  • “PD01” Settlement control key should be used for all projects in order to generate costs.

  • “ZS01” is used for recurrent allocations.

Include the control key in the layout in order to validate the settlement control key.


3.8. I correct the settlement key control of the network, if any error is detected

If there is any project with the control key ZS01, proceed to the correction in the network using transaction CJ20N.


End of document.