Show TOC

Approve Service Entry SheetsLocate this document in the navigation structure

With the transactional app Approve Service Entry Sheets, you can view and approve pending service entry sheets (SES), or even reject approvals. The app enables you to quickly and efficiently process the approval of service entry sheets while away from your desk.

Key Features

The Approve Service Entry Sheets app enables you to:

  • View a list of only those service entry sheets that are approvable and for which you are responsible


    The system checks the authorization of the release code (M_EINK_FRG) in Customizing.

  • Easily approve your service entry sheets

  • Reject service entry sheets and enter a rejection reason in one step, but not after final approval


    When a service entry sheet is rejected, it is sent back to the previous approval step. Your rejection notes will be visible in the app to other approvers, and they can also be viewed in the back-end in the Attachment List in the Services for Object menu (Generic Object Service – GOS).


Within your worklist, you can:

  • Obtain an overview of each service entry sheet, including its description, creation date, value, creator, and service provider

  • Sort according to creation date, total value, and the creator’s name

  • Click on the responsible person to contact her/him by email or phone via business card

Service Header

Within the service header, you can:

  • View the information contained in the worklist overview for easy reference

  • Use the details offered in the information tab to assist you in making approval decisions

  • Access service entry sheet notes in form of generic object service texts (GOS), if available


    Notes can only be edited in the back-end in the Service for Object menu. Examples of commonly used notes are rejection texts.

  • Access service entry sheet attachments (GOS), if available


    Attachments open in an additional viewer depending on your device configuration.

  • Access the total consumed value (sum of all service entry sheets for a purchase order item) by viewing the overall percentage of consumption, overall consumed value, overall planned value, and overall limit

Service Line Overview

Within the service line overview, you can:

  • Obtain an overview of each service line, including its description, quantity, and subtotal value

  • Quickly identify whether a service is fulfilled as planned by viewing the status:

    • Unplanned (not included in purchase order item)

    • Below Plan (value lower than requested in purchase order item)

    • Above Plan (value higher than requested in purchase order item)

    • As Planned (value equal to requested in purchase order item)

Service Line Details

Within the service line details, you can:

  • View the information contained in the service line overview for easy reference

  • Quickly identify risk on item level and increase insight by accessing service line number, activity number, tax code, planned value, planned quantity, and company code

  • Verify that service is posted to the correct G/L account using the following Account Assignments data:

    • Description and Category columns contain for example the WBS element, cost center, or profit center

    • Share column contains the percentage of the full amount that will be posted to a particular account

    • G/L Account column contains the account the share will be posted to

System Landscape Requirements

In order to be able to implement this app, your system landscape has to be enabled for SAP Fiori. One of the requirements for your system landscape is that your back-end product meets the required product version stack:

Required Back-End Product (Product Version Stack)

SAP enhancement package 7 for SAP ERP 6.0 (10 (10/2015))

The front-end components of this app (such as the user interface) are delivered together with the components of other apps as part of this SAP Fiori product:

Front-End Components Delivered with (Product Version Stack)

SAP Fiori 1.0 for SAP ERP ( 08 (10/2015) )

For more information, see the app implementation document of this app.

Component for Customer Incidents