Creating User, Employee Master Data, and Internal Business Partner

The same user who is configured on the front-end server must also be configured on the back-end server. First, you need to create PFCG roles on the back-end server that contain the necessary transactions, Web Dynpro for ABAP apps, and other app types if necessary – as well as the necessary authorizations.

As on the front-end server, you can copy the available standard roles to create your own roles and modify them as needed.

The following standard roles provide all Web Dynpro for ABAP apps for SAP S/4HANA Asset Management are also relevant for the scenario SAP S/4HANA Service with Advanced Execution: Bear in mind that the Web Dynpro for ABAP apps and their roles need to be activated via the business functions starting with LOG_EAM_SIMPLICITY. This is not necessary for the traditional transactions.

• SAP_COCKPIT_EAMS_GENERIC_FUNC2 – Generic EAM Functions

• SAP_COCKPIT_EAMS_MAINT_WORKER2 – Maintenance Worker

The following standard roles are available in SAP S/4HANA Service:

• SAP_BR_CUSTOMER_SERVICE_MGR: Customer Service Manager (Customer Management

• SAP_BR_CUST_SRVC_MGR_REPA: Customer Service Manager – In-House Repair

• SAP_BR_CUST_SRVC_REP_REPA: Customer Service Representative – In-House Repair

• SAP_BR_CUST_SRVC_TEC_REPA: Service Technician – In-House Repair

• SAP_BR_SERVICE_PLANNER: Service Planner – Recurring Service

• SAP_BR_SERV_REP_T: Customer Service Representative (Customer Management)

The following standard roles, which are also relevant for SAP S/4HANA Service with Advanced Execution, are available in SAP S/4HANA Asset Management:

• SAP_BR_EMPLOYEE_MAINTENANCE: Employee

• SAP_BR_MAINTENANCE_PLANNER: Maintenance Planner

• SAP_BR_MAINTENANCE_PLANNER_RSH: Maintenance Planner – Resource Scheduling

• SAP_BR_MAINTENANCE_TECHNICIAN: Maintenance Technician

• SAP_BR_MAINT_SUPERVISOR: Maintenance Supervisor

• SAP_BR_MD_SPECIALIST_EAM: Master Data Specialist – Maintenance Management

SAP Fiori launchpad is designed to be the central entry point for all deployment models.

SAP Fiori launchpad is a role-driven front end and consists of tile groups, which can be put together flexibly based on tile catalogs. Which tile catalogs are available for which user is determined via the role assignment on the front-end server.

This means that SAP S/4HANA has a three-tier architecture:

• SAP Fiori launchpad running in a browser as the front end for the user

• Front-end server with SAP Fiori roles

• Back-end server with back-end roles

When logging on to SAP Fiori launchpad, the user first connects to the front-end server. The front-end server acts as a hub for one or several back-end systems and contains the Fiori-specific apps, roles, and services. Communication between the SAP Fiori launchpad and the front-end server is based on the HTTPS protocol, as well as on a set of OData services. Therefore, the required OData services must be activated on the front-end server.

When choosing a tile in the SAP Fiori launchpad, the user executes an application. The code of these applications in many cases is located on the back-end system. Therefore, the user must be able to log on to the back-end system and must be authorized to run the application. Communication between the front-end server and the back-end server is based on remote function call (RFC). Therefore, the user needs certain RFC authorizations.

The following steps on the front-end server are necessary for work with SAP Fiori apps:

• Install the back-end component.

• Install the product-specific UI component on the back end.

• Install the front-end component on the front-end server.

• Implement the necessary SAP Notes.

• Activate the OData services on the front-end server.

• Activate the SAPUI5 apps on the front-end server.

• Check/create roles containing SAP Fiori catalogs and SAP Fiori tile groups.

• Assign roles to users.

• Assign the OData service authorizations (back end / front end).

The following steps on the back-end server are necessary for working with Fiori apps:

• Install the required software components/products.

• Implement the app on the back end (additional steps might be required, for example, create selection variants, activate workflow tasks, assign responsible employees, link SAP user and personnel number, and so on).

• Check/create roles containing transactions, Web Dynpro for ABAP apps, and their authorizations.

• Assign roles to users.

• Activate business functions for WDA apps.

  Business functions

  The functionality of SAP Enterprise Asset Management (EAM) Web Dynpro for ABAP is shipped with the following business functions:

• LOG_EAM_SIMPLICITY

• LOG_EAM_SIMPLICITY_2

• LOG_EAM_SIMPLICITY_3

• LOG_EAM_SIMPLICITY_ ...

The spaces mode was developed to offer more flexibility to influence the launchpad layout for specific user groups.

Pages are assigned to users via Spaces that are assigned to business roles. The business role defines which users see a specific space. If you enable spaces for your users and define specific spaces and pages for them, you can reach a better fit.

By defining pages with meaningful Sections, you can define in which order the apps are sorted on the page. You can, for example, sort the most used apps in the top-level section and then create separate sections for apps that belong together. SAP delivers predefined spaces and pages that you can use to start.

An SAP Business Partner is an organization (company, subsidiary), person, or group of people or organizations in which your company has a business interest.

You can enter and manage your business partner centrally with regard to various business transactions.

This is particularly relevant if a business partner has various roles for a company, such as sold-to party and ship-to party.

A business partner can be created in various business partner roles and can take on additional business partner roles over the course of the business relationship. It's not necessary to reenter general data for a business partner that's not dependent on their function or on application-specific enhancements, meaning that entry and storage of redundant data can be avoided.

The following Business partner concepts can be distinguished:

• Business partner category:

  The business partner category denotes whether a business partner is a natural person (private individual), organization (legal person/entity or part of a legal entity, such as a department), or a group.

• Business partner role:

  You can use the business partner role to classify a business partner from a business perspective. The attributes for the business partner role are tailored to the requirements of the respective business transaction involved. Data that is available for a transaction is also dependent on the business partner category. The transaction Service Order is, for example, associated with the business partner role Sold-to party.

• Business partner relationship:

  A business partner relationship represents the commercially relevant connection between two business partners.

  The concept of business partner relationships will be explained later on in more detail.

For a better understanding of business partners in SAP S/4HANA Service, S47000 distinguishes between:

• Internal business partners
• External business partners

Internal business partners are service employees of a service provider, for example:

• Service managers
• Service agents
• Service technicians
• Backoffice employees