Responsibility area: to be completed


Table of contents 

By default the table of contents displays Heading 1 & Heading 2 (other levels can be added)

1. Objective and Scope

1.1 Objective of this Operation

The aim of the procedure is to explain how to request the creation of a new cost center

1.2 Scope

Worldwide, for PF1, WP1 & PI1

2. Definitions

Finance - Glossary



Scope

   

 
Frequency

On demand  
References

ZZF_MDWF_REQUEST - Workflow for Master Data
Attachments



Previous OP << >> Next OP


3. Tasks description

3.1 I access the application PRS_050

3.2 Request follow up


You can check all the finance data requests in several ways. The most common are:

  1. By person in charge
  2. By Category of the data
  3. By Cost center

If you just want to have a full overview of the pending requests, just select the day's date in "Ignore requests closed before" and .














You will retrieve a list of the finance master data requests by status, category of the data, requester, etc. 





STATUS:



3.3 Actions on a request - Finance data mgt user


The action menu is located at the top of request screen.


If the request is in a “final” status (cancelled, rejected, completed), only “display” buttons are available.

For you to access most actions, the requests must be in status “2 – taken in charge”.




3.3.1 Action: take in charge or assign to somebody


When a new request is submitted using the workflow, this request has to be taken in charge by someone inside of the Finance data mgt Team:

1) The user who opened the request can click on “take in charge” to set him/herself as the person in charge

2) The user can assign the request to another member of the team. In this case, a new field is available to select the required SAP user ID.


If the request is already taken in charge by someone else then you will get the following message:


3.3.2 Action: reject a request


The rejection of a request is a “final” action.

Afterwards, it is “frozen”: no further action is possible. That's why it should only be used in specific situations (the user is not an authorized requester). In most cases, we should use the option to return it and ask the requester to cancel it.


  After clicking on the reject button, you will get a new “Reason tab”. This tab, will automatically contain the default text that will be send to the requester + person in copy. 

You can update this email (Title + Body) in 2 ways : only add text at bottom [normal case], or set the whole text in “modify fixed text” mode and access the whole text [only exceptionally – in that case, the whole text is stored in the request]

You can save “temporarily”  your update  

Once completed, you can reject the request, via the “send” button

You can also cancel the action and go back to the previous status



3.3.3 Action: return to requestor for modification

When we need to challenge the request [because it is unclear, incomplete…], we need to “return” it to the requester, with our comments / questions.

  After clicking on the return button, you will get a new “Reason tab”. This tab, will automatically contain the default text that will be send to the requester + person in copy. 

You can update this email (Title + Body)

You can save “temporarily” your update  

Once completed, you can finalize the return with the “send” button

You can also cancel the action and go back to the previous status

 


3.4 Overview of a finance data request in the workflow

1 General info on the present module

2 Workflow navigation buttons : actions you can do in the present status / situation

3 Main request information 

4 General info tab – contains details of the request 

5 Masterdata tab - where the detailed data must be filled for cost centers and G/L accounts at company code level

6 Communication Tab – communication channel between the requester and the Data Team

7 Attachment(s) region, allows you to list the files attached to the request

8 General description: free text zone where the requester must enter his/her requirements and justification of the request

9 Optional list of persons that will receive a copy of the email notifying the workflow progress