To make an application for a removal in the intranet, you choose the scenario Removal request. In Customizing this request category is specified as requiring approval. Therefore once you send this notification, the approval process is triggered. When the removal is carried out, costs are posted to the requesting cost center.

The removal request in the intranet is structured as follows:

The title contains the request name, in this case Removal Request, and the company logo. Underneath the request creation function is the request number.

Under this, on the right-hand side is the Entry data, such as Name and Telephone number of the person who makes the entry, and the Date entered.
On the left-hand side is the Removal data with the following fields:

• Who is moving? (initiated by)
• From building
• From room
• To building
• To room
• Removal date
• Number of PCs to be moved
• Change telephone?
• Number of packing boxes required

Underneath this is a free text field called Remarks.

Next to the fields for the building or room, you may have included a pushbutton when you defined the request form. This pushbutton takes you to the building plan.

You choose Internal Service Request in the launchpad for your work place.

You choose the scenario Removal request.
The entry form for the removal request is displayed.

The fields for the person entering data are derived from the user data, and cannot be changed.

As a standard setting the field Initiated by is defaulted with the name of the person making the entries, and can be changed.

The fields for the removal details are mandatory.

Once you have entered your data, you can choose from the following two options:

• Check request
• Send request

After you send the request, you receive a success message containing the notification number.

The fields Who is moving? and Removal date are checked according to the entry format.

At the same time, the Requesting controlling area and Requesting cost center are derived from the initiator data.

A notification is created in the SAP R/3 System for the intranet request. The fields in the HTML form are transferred to the notification.
Three tasks are created for the notification.

The notification is automatically costed using three costing items.

The name of the person responsible for the notification is the cost center manager of the employee moving (this is a standard setting).

The notification is forwarded to the manager for approval.

You need to store certain data in Customizing to allow the system to forward the removal request to an SAP R/3 notification with notification items.

• You specified whether the request requires approval, and who is to approve it for the notification type Removal request.
• For each field from which a notification item is to be generated (for example, in this case, the number of PCs), the following was stored in Customizing independently of the requesting cost center:

The system displays the basic data for the request to the processors for the notification and task in the Extended view in the processing type.

If you make, enter, or initiate a request, you can check its status in the intranet.
The system displays (for example) the notification short text, who it was entered by, and on what date. You can see the notification priority and number for example, by using the worklist.

You can go from here to the notifications detail screen, or add a note.

In the detail screen for each notification, you can see the request form, which cannot be changed.
In addition, the following fields are displayed underneath:

• Status
• Approved by

Under this, there is a free text where you can enter more remarks.

You (the approving manager) also use the intranet. You receive a list of all service requests (regardless of request type) for approval.

The list contains the following fields:

• Description of notification type, such as removal request
• Entered by
• Initiated by
• Date entered
• Required date
• Status

You can go from here to the detail screen for a notification or to approve a notification.

In the detail screen for each notification you can see the request form, which cannot be changed.

In addition, the following fields are displayed underneath:

• Debited cost center
• Estimated costs

Underneath this there is a free text in which you can store more remarks, for example, if you reject the request.

Once you have entered your data, you can choose from the following options:

• Reject request
• Approve request

After you approve the service request, the system sets the status to Approved. Each item is forward to the processor who is determined using the settings in Customizing.

Each task has a different processor.

You (the processor) receive a list of all the tasks that are to be processed.
The list contains the following fields:

• Service request number
• Required date
• Initiated by
• Date entered
• As well as more data from the form

You can go from here to the detail screen for a task, or complete a task.

In the detail screen for each notification you can see the request form, which cannot be changed.
Underneath this there is also a free text in which you can store more remarks, such as when a material no longer exists and is replaced by another.

Once you have entered your data, you can choose from the following two options:

• Forward
  Forwarding is useful if you are not responsible for this notification.
  You can enter the processor who is responsible.

• Complete
  There are two different situations for completing a notification that you can choose in Customizing for the service request type:

• Non-Integrated R/3 Posting You complete your work in and outside of the SAP System (for example, you carry boxes and post the activity allocation manually in the SAP System using confirmation). In this case, only Completed is available. This only closes the task in R/3.

• Integrated R/3 Posting You complete your work outside of the SAP System and want to make an integrated posting of the R/3 data upon completing the service request. In this case, you can use the action box for Execution-Services. A simple screen appears for the current application (such as activity entry, or for material issue) in which the relevant fields are defaulted with values from the plan data for the notification, and which you can change. You make your posting to the account assignment object stored in Customizing. The postings are integrated in R/3. The system prevents accidental double postings by issuing a warning, and preventing you from going to the document flow.

If all the notification tasks are completed, it receives the Completed status.

You (the approver) can analyze the costs of the service request using a report for your cost center.

You go from the totals records report to the line item report. In the line items, the system displays the service request number if the line item was posted integrally from a service request. You can go from the line items of a service request to the service request itself.