Backend Prerequisite Checks
SAP Fiori apps rapid-deployment solution
Document Version: 1.0 – 2015-01-26 / Customer
Backend Prerequisite Checks for Report Quality Issues/My Quality Tasks
Backend Prerequisite Checks for Report Quality Issues/My Quality Tasks
Typographic Conventions / Customer
© 2012 SAP AG. All rights reserved. 1

Typographic Conventions

Type Style / Description /
Example / Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example / Emphasized words or expressions.
EXAMPLE / Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.
Example / Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.
Example / Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example> / Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.
EXAMPLE / Keys on the keyboard, for example, F2 or ENTER.

Document History

Version / Date / Change /
1.0 / 2015-01-26 / First version.

Table of Contents

1 Configuration 5

1.1 Configuration in the Backend System for Report Quality Issue 5

1.1.1 Generating Partner for Processing Notification 5

1.1.2 Settings Related to Code Groups, Codes and Catalog Profile 6

1.1.2.1 Generating Code Group and Code at Header Level 6

1.1.2.2 Generating Code Groups and Codes at Item Level 7

1.1.2.3 Generating Catalog Profiles 8

1.1.3 Setup New Quality Notification Type 9

1.1.3.1 Copy Existing Quality Notification Type 9

1.1.3.2 Copy Screen Setting 10

1.1.3.3 Screen Area Settings of QM 11

1.1.3.4 Assign Catalog Settings to QM 12

1.1.3.5 Format Long Text Setting of QM 13

1.1.3.6 Priority Generation (Optional) 13

1.1.3.7 Priority Type Setting of QM 14

1.1.3.8 Partner Function Settings of QM 15

1.1.4 Storage Settings for Attachments 16

1.1.4.1 DMO Document Type Generation 16

1.1.4.2 Generating Workstation Applications for JPG Files 17

1.1.4.3 Data Carrier Generation 18

1.1.4.4 Storage System Generation 19

1.1.4.5 Storage Category Generation 20

2 Usage of the Fiori app 21

Error! Reference source not found.
Document History / Customer
© 2014 SAP SE or an SAP affiliate company. All rights reserved. / 3

1  Configuration

1.1  Configuration in the Backend System for Report Quality Issue

Use

This document describes the required backend settings in the ERP so that a Quality Notification can be created via the Fiori app Report Quality Issue.

The document describes the creation, however, the by SAP delivered Quality Notification Type Q3 can be used as well. In this case, it is indicated which settings are obsolete.

1.1.1  Generating Partner for Processing Notification

Use

In this activity, you generate a partner.

Procedure

1.  Access the activity using one of the following navigation options:

Transaction Code / SPRO
SAP Reference IMG Menu / Quality Management ® Quality Notifications ® Notification Creation ® Partners ® Define Partner Determination Procedures

2.  On the Choose Activity screen, choose Define Partner Determination Procedure.

3.  On the Maintain: Partner determination screen, choose the Quality Management radio button and then choose Change Partner.

4.  In the dialog structure, choose the Partner Determination Procedures folder.

5.  Copy the partner determination procedure Q3 and maintain the following values:

Field name / Description / User action and values /
PartnDet.Proc. / QM
Decription / Fiori ProbMessage

Example

Copy the partner determination procedure Q3 (Internal ProbMessage) to QM (Fiori ProbMessage) and confirm by choosing Copy all entries in the dialog box.

6.  Choose the copied partner determination procedure QM and then choose the Functions in Determination Procedure folder.

7.  Deselect the Partner mandate. checkbox for all partner roles.

8.  Choose Save.

Result

You have now adapted the Partner Determination Procedure.

1.1.2  Settings Related to Code Groups, Codes and Catalog Profile

1.1.2.1  Generating Code Group and Code at Header Level

Use

In this activity, you generate code groups and codes at the header level.

Procedure

1.  Access the activity using one of the following navigation options:

Transaction Code / SPRO
SAP Reference IMG Menu / Quality Management ®Quality Notifications ®Notification Creation ®Notification Content ®Maintain Catalogs

2.  On the Choose Activity screen, choose Edit Catalogs.

3.  On the Edit Catalog: Initial Screen screen, enter D(Coding) in the Catalog field and choose Create/change.

4.  On the Change View “Code groups”: Overview screen, choose New Entries.

5.  Enter the following values and then choose Save:

Field Name / Description / User Action and Values /
Code group / QMOBILE
Short text / Subject codes Quality Issue
Status of code group / Released

6.  Choose the newly created code group and choose the Codes folder.

7.  Choose New Entries.

8.  Enter several new codes, for example as follows:

Code / Description /
0001 / Goods Receipt Area
0002 / Warehouse
0003 / Production
0004 / Purchasing Department
0005 / Shop Floor
0006 / Quality Control

9.  Choose Save.

Result

You have now created a new Code Group and underlying codes for the usage in your Quality Notification Type.

1.1.2.2  Generating Code Groups and Codes at Item Level

Use

In this activity, you generate code groups and codes at item level.

Procedure

1.  Access the activity using one of the following navigation options:

Transaction Code / SPRO
SAP Reference IMG Menu / Quality Management ® Quality Notifications ® Notification Creation ® Notification Content ® Maintain Catalogs

2.  Choose the Activity screen, and choose Edit Catalogs.

3.  On the Edit Catalog: Initial Screen screen, enter 9 (Defect types) in the Catalog field and then choose Create/change.

4.  On the Change View “Code groups”: Overview screen, choose New Entries.

5.  Enter the following values and choose Save:

Field Name / Description / User Action and Values /
Code group / QMOBILE
Short text / Subject codes Quality Issue
Status of code group / Released

6.  Select the newly created code group and choose the Codes folder.

7.  Choose New Entries.

8.  Enter several new codes and select a defect class for each defect code, for example, 01 - Critical , or as follows:

Code / Description / Defect class /
0010 / Broken / Critical defect
0020 / Out of Specification / Critical defect
0030 / Parts Missing / Major defect A
0040 / Reduced Performance / Major defect B
0050 / Outdated / Minor defect A
0060 / Wrong Color / Minor defect A

9.  Choose Save.

Result

You have now created the ciudes on item level.

1.1.2.3  Generating Catalog Profiles

Use

In this activity, you generate a catalog profile.

Note

In case the SAP delivered notification type Q3 is used, this step is obsolete.

Procedure

1.  Access the activity using one of the following navigation options:

Transaction Code / SPRO
SAP Reference IMG Menu / Quality Management ® Quality Notifications ® Notification Creation ® Notification Content ® Define Catalog Profile

2.  On the Choose Activity screen, choose Define Catalog Profile.

3.  On the Change view “Catalog profiles”: Overview” screen, choose Catalog profiles and then choose New Entries.

4.  Enter the following values and then choose Save:

Field Name / Description / User Action and Values /
Cat.Prof. (Catalog profile) / QMOBILE
[description field] / Mobile Quality Issue

5.  Choose the newly created catalog profile and then choose Catalogs / code groups.

6.  Enter the catalog and code group:

Field Name / Description / User Action and Values /
Catalog / 9
Code group / QMOBILE
Catalog / D
Code group / QMOBILE

7.  Choose Save.

Result

You have created a catalog profile.

1.1.3  Setup New Quality Notification Type

1.1.3.1  Copy Existing Quality Notification Type

Use

In this activity, you either create a new quality notification type or copy from an existing notification type.

Note

In case the SAP delivered notfication type Q3 is used, this step is obsolete.

Procedure

  1. Access the activity using one of the following navigation options:

IMG Menu / Quality Management ® Quality Notifications ® Notification Creation ® Notification Type ® Define Notification Types
Transaction Code / SPRO
  1. Either copy from an existing notification type or create a new entry.

Example

Copy the notification type Q3 (InternalProbNotif.) to notification type QM (QM Fiori).

  1. Choose Save.

Result

You have now created your own Quality Notification Type.

1.1.3.2  Copy Screen Setting

Use

In this activity, you copy the standard screen areas to the new notification type.

Note

In case the SAP delivered notfication type Q3 is used, this step is obsolete.

Procedure

1.  Access the activity using one of the following navigation options:

IMG Menu / Quality Management ® Quality Notifications ® Notification Creation ® Notification Type ® Define Screen Templates
Transaction Code / SPRO

2.  On the Choose Activity screen, choose Copy screen Areas from the Standard System.

3.  In the Notification type field, enter QM and leave the test box blank.

4.  Choose Execute.

5.  The screens are automatically created for the new notification type.

Result

You have now copied the screen settings.

1.1.3.3  Screen Area Settings of QM

Use

In this activity, you complete the screen areas setting of the notification type QM. The main purpose is to make the Linked Documents visible – since in the Fiori app attachments can be added to the notification.

Procedure

1.  Access the activity using one of the following navigation options:

IMG Menu / Quality Management ® Quality Notifications ® Overview of Notification types
Transaction Code / SPRO

2.  Choose the quality notification type QM.

3.  Choose the Screen Areas in Notification Header folder.

4.  Enter the following values:

Field Name / Description / User Action and Values /
Screen type hdr / H500
Scm Type Object / O520

5.  In the dialog structure, choose the Screen Structure for Extended View folder.

6.  Select the row 10\TAB01 (Notification 1) and choose (Details).

7.  Enter the following values into the Screen area fields:

Field Name / Description / User Action and Values /
Screen area 1 / 005
Screen area 2 / 040
Screen area 3 / 025
Screen area 4 / 031
Screen area 5 / 092

8.  Choose Save and return to the previous screen.

9.  Choose the row 10\TAB04 (Dates) and choose (Details).

10.  Select the Tab checkbox.

11.  The tab page is displayed when a notification is displayed or changed.

12.  Choose Save.

Note

In case of the SAP delivered notification type Q3 and you want to see the attached documents from the Fiori app, you need to add Screen area 5 with value 092 to Q3 notification type.

Result

You have now applied the relevant screen settings.

1.1.3.4  Assign Catalog Settings to QM

Use

In this activity, you complete the catalog setting of the notification type QM by assigning the catalog profile.

Note

In case the SAP delivered notification type Q3 is used, this step is obsolete.

Procedure

  1. Access the activity using one of the following navigation options:

IMG Menu / Quality Management ® Quality Notifications ® Overview of Notification types
Transaction Code / SPRO
  1. Select the quality notification type QM.
  2. In the dialog structure, choose the Catalogs and Catalog Profiles folder.
  3. In the Catalog profile field, enter QMOBILE (Mobile Quality Issue).

5.  To set the catalog types, enter the following data:

Field Name / Description / User Action and Values /
Coding / D (Coding)
Problems / 9 (Defect types)
Causes / 5 (Causes)
Tasks / 2 (Tasks)
Activities / 8 (Activities (QM))
ObjectParts / E (Defect Locations)
  1. Save your entries.

Result

You have now assigned the catalog profile to your Quality Notification Type.

1.1.3.5  Format Long Text Setting of QM

Use

In this activity, you complete the setting for formatting long texts of the notification type QM.

Note

In case the SAP delivered notfication type Q3 is used, this step is obsolete.

Procedure

1.  Access the activity using one of the following navigation options:

IMG Menu / Quality Management ® Quality Notifications ® Overview of Notification types
Transaction Code / SPRO

2.  Select the quality notification type QM.

3.  In the dialog structure, choose the Format Long Text folder.

4.  Select the Log line and No text change checkboxes.

5.  Choose Save.

Result

You have now applied the settings for the long text display.

1.1.3.6  Priority Generation (Optional)

Use

In this activity, you define the priority only for the notification type QM.

Note

In case the SAP delivered notification type Q3 is used, this step is obsolete.

Procedure

1.  Access the activity using one of the following navigation options:

IMG Menu / Quality Management ® Quality Notifications ® Notification Processing ® Response Control ® Define Priorities
Transaction Code / SPRO

2.  On the Choose Activity screen, choose Priority Types.

3.  Choose New Entries.

4.  On the New Entries: Overview of Added Entries screen, enter the following values:

Field Name / Description / User Action and Values /
Prtyp / QM
Priority Type / QM priorities

5.  Choose Save.

Result

You have now created your new priority type.

1.1.3.7  Priority Type Setting of QM

Use

In this activity, you assign the newly created priority type to the notification type QM.

Note