sap offline word template - websmp204.sap-ag.de€¦ · web viewthe only warranties for sap or...

Backend Prerequisite ChecksSAP Fiori apps rapid-deployment solutionDocument Version: 1.0 – 2015-01-26

CUSTOMER

Backend Prerequisite Checks for Report Quality Issues/My Quality Tasks

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 .

2

CUSTOMER © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Error: Reference source not foundTable of Contents

Document History

Version Date Change

1.0 2015-01-26 First version.

Error: Reference source not foundDocument History

CUSTOMER© 2014 SAP SE or an SAP affiliate company. All rights

reserved. 3

Table of Contents

1 Configuration.................................................................................................................................51.1 Configuration in the Backend System for Report Quality Issue.....................................................5

1.1.1 Generating Partner for Processing Notification................................................................51.1.2 Settings Related to Code Groups, Codes and Catalog Profile..........................................61.1.2.1 Generating Code Group and Code at Header Level.........................................................61.1.2.2 Generating Code Groups and Codes at Item Level..........................................................71.1.2.3 Generating Catalog Profiles.............................................................................................81.1.3 Setup New Quality Notification Type................................................................................91.1.3.1 Copy Existing Quality Notification Type...........................................................................91.1.3.2 Copy Screen Setting.......................................................................................................101.1.3.3 Screen Area Settings of QM...........................................................................................111.1.3.4 Assign Catalog Settings to QM.......................................................................................121.1.3.5 Format Long Text Setting of QM....................................................................................131.1.3.6 Priority Generation (Optional)........................................................................................131.1.3.7 Priority Type Setting of QM............................................................................................141.1.3.8 Partner Function Settings of QM....................................................................................151.1.4 Storage Settings for Attachments..................................................................................161.1.4.1 DMO Document Type Generation..................................................................................161.1.4.2 Generating Workstation Applications for JPG Files.........................................................171.1.4.3 Data Carrier Generation.................................................................................................181.1.4.4 Storage System Generation...........................................................................................191.1.4.5 Storage Category Generation........................................................................................20

2 Usage of the Fiori app..................................................................................................................21

4

CUSTOMER © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Error: Reference source not foundTable of Contents

1 Configuration

1.1 Configuration in the Backend System for Report Quality Issue

UseThis 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

UseIn this activity, you generate a partner.

Procedure1. 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

Usage of the Fiori app


reserved. 5

ExampleCopy 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.

ResultYou 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:


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 ValuesCode group QMOBILE

Short text Subject codes Quality Issue

6

CUSTOMER © 2014 SAP SE or an SAP affiliate company. All rights reserved. Configuration

Field Name Description User Action and ValuesStatus 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 Area0002 Warehouse0003 Production0004 Purchasing Department0005 Shop Floor0006 Quality Control

9. Choose Save.

ResultYou 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.



SAP Reference IMG Menu Quality Management Quality Notifications Notification Creation Notification Content Maintain Catalogs

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



reserved. 7

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 ValuesCode 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 class0010 Broken Critical defect0020 Out of Specification Critical defect0030 Parts Missing Major defect A0040 Reduced Performance Major defect B0050 Outdated Minor defect A0060 Wrong Color Minor defect A

9. Choose Save.

ResultYou have now created the ciudes on item level.

1.1.2.3 Generating Catalog Profiles

Use In this activity, you generate a catalog profile.

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

8




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 ValuesCat.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 ValuesCatalog 9

Code group QMOBILE

Catalog D

Code group QMOBILE

7. Choose Save.

ResultYou 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.



reserved. 9

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


IMG Menu Quality Management Quality Notifications Notification Creation Notification Type Define Notification Types


2. Either copy from an existing notification type or create a new entry.

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

3. Choose Save.

ResultYou 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.



IMG Menu Quality Management Quality Notifications Notification Creation Notification Type Define Screen Templates


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.

10


ResultYou 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.


IMG Menu Quality Management Quality Notifications Overview of Notification types


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 ValuesScreen 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 ValuesScreen 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).



reserved. 11

10. Select the Tab checkbox. 11. The tab page is displayed when a notification is displayed or changed. 12. Choose Save.

NoteIn 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.

ResultYou 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.





2. Select the quality notification type QM.3. In the dialog structure, choose the Catalogs and Catalog Profiles folder.4. 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 ValuesCoding D (Coding)

Problems 9 (Defect types)

Causes 5 (Causes)

Tasks 2 (Tasks)

Activities 8 (Activities (QM))

ObjectParts E (Defect Locations)

12


6. Save your entries.

ResultYou 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.





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.

ResultYou 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.



reserved. 13



IMG Menu Quality Management Quality Notifications Notification Processing Response Control Define Priorities


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 ValuesPrtyp QM

Priority Type QM priorities

5. Choose Save.

ResultYou 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.



IMG Menu Quality Management Quality Notification Overview of Notification types


2. Choose the quality notification type QM.

14


3. In the dialog structure, choose the Priority Type folder.4. In the Priority type field, enter QM (QM priorities). 5. Choose Save.

ResultYou have now assigned the priority type to your Quality Notification Type.

1.1.3.8 Partner Function Settings of QM

Use In this activity, you complete the partner function setting for the notification type QM.



IMG Menu Quality Management Quality Notification Overview of Notification types


2. Select the quality notification type QM.3. In the dialog structure, choose the Partner Determination Procedure folder.4. Assign Partner Determination Procedure QM in column PartnDetProc.5. Choose Save.6. In the dialog structure, choose the Partner Functions, Approval folder.7. In the Author function field, select the AO Author entry.

NoteTo avoid value confusion, in SAP GUI, enable show keys within dropdown lists.

8. Choose Save.

ResultYou have now adapted the partner determination procedure.



reserved. 15

1.1.4 Storage Settings for Attachments

1.1.4.1 DMO Document Type Generation

Use In this activity, you generate a DMO document type.


IMG Menu Quality Management Environment Central Functions Define Document Types


2. Choose New Entries to create a new document type. DOC (Tech. documentation). 3. Maintain the following values:

Field Name Description User Action and ValuesDocument Type DOC

Doc.Type Desc. Tech. documentation

Use KPRO X

Rev.Lev.Assgmnt X

Version Assgmt X

Archiving Authorization X

Internal Number Range 02

External Number Range 01

Number Exit MCDOKZNR

Vers. No. Incr. 1

File Size 99999

Default Appl. JPG

4. In the Field Selection area, set the indicators as follows and leave other fields blank:

Field Name Description User Action and ValuesHierarchy indicator -

Document Status -

Change Number -

Superior Document -

16


5. Choose Save.6. In the dialog structure, choose the Define language-dependent descriptions folder.7. Choose New Entries.

Field Name Description User Action and ValuesLang. EN

Doc. Type desc. Tech. documentation

8. Choose Save.9. In the dialog structure, choose the Define object links folder. 10. Choose New Entries.11. Enter the following data:

Field Name Description User Action and ValuesObject QMQMEL

Screen no. 234

12. Choose Save.

ResultYou have now created the relevant DMO type.

1.1.4.2 Generating Workstation Applications for JPG Files

Use In this activity, you generate workstation applications for the jpg type. Skip this activity if they already exist.


IMG Menu Cross-application Components Document Management General Data Define Workstation Application


2. On the Define Workstation Application Overview screen, if there is no jpg type application, choose New Entries

3. On the Define Workstation Application Details screen, make the following entries and leave others blank:



reserved. 17

Field Name Description User Action and ValuesWS application JPG

Description JPEG Graphic

Archive identification *

File suffix for appl. Jpg

File format *.jpg

MIME type image/jpeg

Appl. Icon @J0@

Start Authorization X

4. Choose Save.

ResultYou have checked the required settings for workstation applications.

1.1.4.3 Data Carrier Generation

Use In this activity, you generate the pc type data carrier. Skip this activity if it already exists.


IMG Menu Cross-application Components Document Management General Data Define Data Carrier


2. In the dialog structure, choose the Define data carrier type “server, front end“ folder.3. Check the data carrier. If there is no data carrier type (PC), choose New Entries.4. Enter the following values:

Field Name Description User Action and ValuesType PC

Description Local PC

Online X

5. Choose Save.6. Choose the newly created table entry.

18


7. In the dialog structure, choose the Identify frontend computers folder.8. Check if the following data is available:

Field Name Description User Action and ValuesFrontendComputer DEFAULT

Data carr.type PC

Netw. Address DEFAULT

Description Default for local PC

9. Choose Save.

ResultYou have configured the data carrier.

1.1.4.4 Storage System Generation

Use In this activity, you generate a storage system only for mobile apps.


IMG Menu Cross-application Components Document Management General Data Settings for Storage System Maintain Storage System


2. If necessary, choose Create to create an new content repository for storage system DMS_C1 with the following data:

Field Name Description User Action and ValuesContent Repository DMS_C1

Document Area DMS

Storage Database SAP System Database

Version 0045

Description Database storage documents

3. Choose Save.



reserved. 19

ResultYou have now maintained the storage system settings.

1.1.4.5 Storage Category Generation

Use In this activity, you generate a storage category of the newly created storage system.


IMG Menu Cross-application Components Document Management General Data Settings for Storage System Maintain Storage Category


2. If necessary, create an entry for storage category DMS_C1_ST with the following data:

Field Name Description User Action and ValuesCategory DMS_C1_ST

Description Default storage DMS (main files)

Document Area DMS

Content Repository DMS_C1

ResultYou have now maintained the storage system settings.

20


2 Usage of the Fiori app

Use This section gives a hint regarding the usage of the Fiori app Report Quality Issue. It is assumed that the app was configured as described in the configuration guide ' SAP Fiori Transactional Apps Deployment'.Problem: Once starting the app the first time and you have created the first Quality Issue and saved it, the search on the left hand list screen does not display any results. The search is running in an endless loop.

Procedure 1. After logging into the Report Quality Application, click on the user displayed at the top right corner.2. Select Settings -> Display {0} Issues and then set the number of issues to, for example, 100. 3. Select OK.

ResultThe Issues List will be populated properly.



reserved. 21

www.sap.com/contactsap

© 2014 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Material Number:

http://www.sap.com/corporate-en/legal/copyright/index.epx