Configuration of Document Management on PLM Web UI

Document on PLMWeb UINovember 2013English

Configuration ofDocument Management onPLM Web UIConfiguration Guide

SAP Product Lifecycle Management (SAP PLM) 7.03Using SAP® ERP 6.0 (Including Enhancement Package 7)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices Configuration of Document on PLM Web UI

© SAP AG Page 2 of 55

Copyright© 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, SystemStorage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarksof IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarksof Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarksor registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technologyinvented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjectsExplorer, and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions,Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks of SAP France in the United Statesand in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specifications mayvary.

These materials are subject to change without notice. These materials are provided by SAP AG and itsaffiliated companies ("SAP Group") for informational purposes only, without representation or warrantyof any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. Theonly warranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names,program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, forexample, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or theENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.



Content1 Purpose ......................................................................................................................... 62 Important SAP Notes ...................................................................................................... 63 Basic Document Management Configuration (SAP ERP Backend System) ..................... 6

3.1 Control Data ......................................................................................................... 6Define Number Ranges for Document Numbers ............................................... 63.1.1Define Document Types ................................................................................... 73.1.2Define Revision Levels ................................................................................... 113.1.3Maintain Role ................................................................................................. 113.1.4

3.2 General Data ...................................................................................................... 13Define Data Carrier......................................................................................... 133.2.1Maintain Storage System ................................................................................ 143.2.2Define Content Repositories ........................................................................... 153.2.3Maintain Storage Category ............................................................................. 173.2.4Define Workstation Application ....................................................................... 173.2.5Define Category for Markup ............................................................................ 213.2.6Define Profile .................................................................................................. 223.2.7Define Laboratories/Design Offices ................................................................. 233.2.8

4 Enhanced Document Management Configuration (PLM Web UI) .................................. 244.1 Activate Business Functions ............................................................................... 244.2 Set Up Web Dynpro ............................................................................................ 24

Install Services ............................................................................................... 244.2.1Activate Services ............................................................................................ 254.2.2

4.3 Set Up Embedded Search .................................................................................. 25Connect TREX and Embedded Search ........................................................... 264.3.1Set Up Search Connectors for Embedded Search .......................................... 274.3.2

4.4 Document in PLM Web UI .................................................................................. 304.5 Process Route .................................................................................................... 31

Maintain Standard Settings ............................................................................. 314.5.1Define Number Range Interval........................................................................ 314.5.2Activate Process Route Workflow ................................................................... 324.5.3Define Task Types.......................................................................................... 324.5.4Synchronize Runtime Buffer ........................................................................... 334.5.5

4.6 Digital Signature ................................................................................................. 33Maintain Basic Settings for Digital Signature ................................................... 334.6.1Specify Signature Method for Approval Using Simple Signature ...................... 334.6.2Define Authorization Groups ........................................................................... 344.6.3Define Individual Signature ............................................................................. 344.6.4Define Signature Strategy ............................................................................... 354.6.5Workflow and Document Management Integration .......................................... 364.6.6

4.7 Viewer ................................................................................................................ 38Define Viewer Installation ............................................................................... 384.7.1



Define Viewer Application ............................................................................... 394.7.24.8 Set Up White List ................................................................................................ 39

Generate Certificate for White List .................................................................. 404.8.1Set Up Active Controls White List ................................................................... 404.8.2Define URL of Storage Category .................................................................... 414.8.3Activate Active Controls White List .................................................................. 434.8.4Saving Certificates Using the Browser ............................................................ 434.8.5

4.9 Roles and Authorizations .................................................................................... 444.10 Launchpad Customizing ..................................................................................... 444.11 Front-End Installation.......................................................................................... 46

SAP NetWeaver Business Client .................................................................... 464.11.1Installation of Java Runtime Environment ....................................................... 474.11.2SAP Visual Enterprise Viewer ......................................................................... 474.11.3

5 SAP 3D Visual Enterprise Generator ............................................................................ 485.1 Map VEG Instance to Logical Port ...................................................................... 485.2 Maintain Conversion Trigger ............................................................................... 485.3 Map Storage Category to VEG Application Server .............................................. 505.4 Define Tag Category........................................................................................... 505.5 Map Tag Name to Tag Category ......................................................................... 515.6 Map BCV Tag to Tag Name ................................................................................ 515.7 Maintain Tag Mapping ........................................................................................ 525.8 Maintain Application Usage ................................................................................ 525.9 Define Search Sequence for Viewable File ......................................................... 535.10 Define Profile for Excluding Viewer Actions ......................................................... 545.11 Activate Service Binding to Access Web Service ................................................ 545.12 Business Add-Ins................................................................................................ 55



Configuration of Document on PLM Web UI1 PurposeThis document describes the configuration steps that are required to manually set up the PLMWeb user interface (PLM Web UI) including advanced PLM functionality: documentmanagement, visualization, and process route. The following areas are covered:

Basic Document Management Configuration (SAP ERP Backend System)Enhanced Document Management Configuration (PLM Web UI)SAP 3D Visual Enterprise Generator

This document does not include general information about configuring SAP ERP, TREX, andSAP Content Server. These basic settings can be provided as part of SAP Rapid DeploymentSolutions.

2 Important SAP Notes

SAP Note Description

1819440 Understanding PLM WUI Documents and SAP DMS (FAQs)

3 Basic Document Management Configuration(SAP ERP Backend System)

3.1 Control DataIn this step, you define the central parameters and default values for document management(DM).

Define Number Ranges for Document Numbers3.1.1UseIn this step, you define the number ranges for document numbers and the type of numberassignment. When you define a document type, you must enter at least one number range forassigning document numbers.

You have the following options:

Internal number assignment: Your SAP System assigns a numeric number from thenumber range defined.

External number assignment: You can define a numeric number from the number rangedefined.



Procedure1. Access the Customizing activity as follows:

Customizing Menu Logistics - General Product Lifecycle Management(PLM) Document Management Control DataDefine Number Ranges for Document Numbers

Transaction Code SPRO

2. Choose the Change Intervals pushbutton.

3. Choose the Insert line pushbutton.

4. Enter the interval with the number 01 from 000000000001 to 999999999999.

5. Do not select the Ext checkbox.

6. Save your entries.

Define Document Types3.1.2UseIn this step, you make the settings for the document type by performing the followingactivities:

Define document type

Define document statuses and status network

Define object links

PrerequisitesYou have defined a number range.

:

In document management, document info records (that is, the metadata) are stored in theSAP ERP backend system. The document info records contain links to the original files.We recommend that you store these original files on an SAP Content Server (that is, aseparate server).

If an SAP Content Server is not available, storage category DMS_C1_ST can be used. If youuse this category, the original files are saved in the SAP database. This is useful fortesting but not recommended for a production environment.

ProcedureAccess the Customizing activity using one of the following navigation options:

Customizing Menu Cross-Application Components Document ManagementControl Data Define Document Types

Transaction Code DC10

Perform the following steps:



Define Document Type

1. On the Change View Define Document Types: Overview screen, choose the Newentries pushbutton.

2. On the New Entries: Details of Added Entries screen, enter the following values:

Field Name User Action and Values Comment

Document Type KPR KPR is an example.

Document Typedescription KPR Documents

Use KPro <Select thischeckbox>

In PLM Web UI, onlyKnowledge Provider (KPro)is supported.

Use ACM <Select thischeckbox>

When you select thischeckbox, document inforecord (DIR) authorizationis controlled by PLMAccess ControlManagement (ACM).

Display Object Links <Select thischeckbox>

Version Assignment <Select thischeckbox>

Change Docs <Select thischeckbox> Optional

Internal NumberRange 01 Select the required number

range.

External numberrange 01

Number exit MCDOKZNR Select Default to generatethis entry.

Vers. No. Incr. 2Select "1" if you wantversions to start with "00"instead of "01".

Hierarchy indicator - Suppress field

Depending on yourrequirements, select “.”(optional entry) instead of “-“ (suppress field).

Document Status + Required entry

DocumentDescription + Required entry


Authorization Group - Suppress field





Lab./Office - Suppress fieldDepending on yourrequirements, select “.”instead of “-“.

Change Number . Optional entry Allows the optional entry ofa change number.

CAD Indicator - Suppress field

Superior Document - Suppress field

WS Application 2 - Suppress field

CM Relevance - Suppress field

3. Save your entries and choose the Back (F3) pushbutton to go back to the ChangeView “Define Document Types”: Overview screen.

Define Document Status and Status Network

1. On the Change View “Define Document Types”: Overview screen, select thedocument type KPR and choose Define document status in the dialog structure.

2. On the Change View "Define document status": Overview screen, choose the NewEntries pushbutton.

3. Enter the following values:


Document Status FR Choose Enter.

Object Check <Select thischeckbox>

Complete for ECM <Select thischeckbox>

Release Flag <Select thischeckbox>

Check-In Required <Select thischeckbox>

Check in <Select thischeckbox>

Status type S Locked Status

For more information, see the F1 help for the individual fields.

4. Choose the Next Entry (F8) pushbutton and enter the following values:


Document Status IA Choose Enter.

Object Check <Select thischeckbox>

Check in <Select thischeckbox>




Status type I Initial Status

5. Save your entries and go back to the "Define document status": Overview screen(you may need to choose the Back (F3) pushbutton twice).

6. Choose the Select All (F7) pushbutton to select both newly created statuses andthen choose the Details (Ctrl-Shift-F2) pushbutton to change the statuses.

7. For document status FR, enter IA in the Prev. 1 field and then choose the Next Entry(F8) pushbutton.

8. For document Status IA, enter FR in the Prev. 1 field.

This will allow you to switch back from status FR (released) to status IA (inprocess). You may omit this step if you would prefer not to allow changes toreleased documents. In this case, users will have to create a new versionwhenever they need to make changes to a document that has already beenreleased.

9. Save your entries and go back to the Change View “Define Document Types”:Overview screen (you may need to choose the Back (F3) pushbutton twice).

Define Object Links

1. On the Change View “Define Document Types”: Overview screen, select documenttype KPR and choose Define object links in the dialog structure.

2. Choose the New Entries pushbutton and enter the following values:


Document Type KPR

Object MARA Choose Enter.

When New Version 1

Create Document 2

Document Version 1



Document Type KPR

Object AENR Choose Enter.

When New Version 1

Create Document 2

Document Version 1





Document Type KPR

Object DRAW Choose Enter.

When New Version 1

Create Document 2

Document Version 1

5. Save your entries and go back to the Change View “Define Document Types”:Overview screen (you may need to choose the Back (F3) pushbutton twice).

6. Save your entries and exit the transaction (you will need to choose the Back (F3)pushbutton several times).

Define Revision Levels3.1.3UseIn this step, you define the revision levels for documents. You also define the sequence in whichthe revision levels are to be assigned.


Customizing Menu Cross-Application Components DocumentManagement Control Data Define Revision Levels


2. On the Change View “Sequence of Revision Levels for Documents”: Overviewscreen, choose the New entries pushbutton.

3. Enter the sequence and revision level in the corresponding columns.


Maintain Role3.1.4UseIn this step, you can create a standard SAP role that you can then assign to a documentmanagement (DM) profile.

Roles enable you to do the following:

Provide user menus and transactions Control authorizations for documents Link users to a document management (DM) profile

A DM profile is used to define default settings (for example, storage category DMS_C1_ST). If youassign a role to a DM profile, users that have this role are then automatically assigned to the DMprofile (see section 3.2.7).




Customizing Menu Cross-Application Components DocumentManagement Control Data Maintain role


2. Choose the Single Role pushbutton.3. Enter a description, for example, “Profile Role for DM Users”.4. Save the role.5. On the Users tab page, assign the relevant user IDs to the role.6. Save your entries.7. Choose the User comparison pushbutton.



3.2 General Data

In Document on PLM Web UI, application files are stored using the Knowledge Provider.Therefore, the settings in the Customizing activity Maintain Global Settings are not required(Customizing for Cross-Application Components under Document ManagementGeneral Data Maintain Global Settings).

Define Data Carrier3.2.1UseIn this step, you define the data carrier type PC (Personal Computer).

Document on PLM Web UI supports only the standard data carrier, PC. The definition ofadditional frontend types is not allowed. For more information, see SAP Note 1819440.


Customizing Menu Cross-Application Components DocumentManagement General Data Define Data Carrier


2. On the Change View “Define data carrier type “archive”: Overview screen, chooseDefine data carrier type “server, front end” in the dialog structure and choose the NewEntries pushbutton.



Type (data carr. type) PC

Description PC with MS WindowsOperating System

Path If you leave this field empty,the system saves temporaryfiles in the standardWindows folder fortemporary files (LocalSettings\Temp).Alternatively, you can enterany path here, for example,c:\temp or a network drive.

Online <Select thischeckbox>

4. Select your entry and choose Define servers and files or folders in the dialogstructure.

5. Choose the New entries pushbutton and create a new entry with the following values:


Data Carr. PC



Type (data carr. type) Default

Description Personal Computer

6. In the dialog structure, choose Identify frontend computers.

7. Choose the Default entry pushbutton to create a new entry with the following values:


FrontendComputer Default

Data carr. Type PC

Netw. Address DEFAULT

Description Default for localPC

8. In the dialog structure, choose Define mount points / logical drive.

9. Choose the New entries pushbutton to create a new entry with the following values:


Data Carr. PC

Data carr. type PC

Prefix for access path <path> e.g.:

C:\SAP_BP


Maintain Storage System3.2.2UseIn this step, you define storage systems for original application files and assigned additionalfiles. The system uses these storage systems for document types that are to be stored in theKnowledge Provider (KPro). You specify that original application files are to be stored in KProby selecting the Use KPro checkbox in the document type in the Customizing activity DefineDocument Types (see section 3.1.2).

Procedure1. Access the Customizing activity using one of the following navigation options:

Customizing MenuCross-Application Components DocumentManagement General Data Settings for StorageSystems Maintain Storage System

Transaction Code OAC0



2. On the Change View Content Repositories: Overview screen, choose the Create (F5)pushbutton.

3. On the Change View Content Repositories: Detail screen, enter the following values:


Content Rep. Z_DMS_PLM

Repository name in the SAPsystem. The repository willbe linked to the applicationin a separate step.

Description Content repositoryfor PLM Documents

Document Area DMS DocumentManagement System

Version No. 0046

HTTP Server <Hostname ofContent Server>

Host name including domainat which the content servercan be accessed from theSAP system.

Port Number 1090

HTTP port number at whichthe content server can beaccessed from the SAPsystem. The port numbermust be defined duringcontent server installation.The default port number is1090.

HTTP Script ContentServer/ContentServer.dll Content server alias


Define Content Repositories3.2.3UseIn this step, you configure the repository on the content server.

Procedure1. Continue from step 3.2.2 by choosing Environment CS Admin in transaction OAC0.

This takes you to the Content Server Administration transaction.

You can also access the transaction as follows:

Customizing MenuSAP NetWeaver Knowledge Management Settingsin the Knowledge Warehouse System ContentManagement Service Define Content Repositories

Transaction Code CSADMIN

If a dialog box appears asking you to enter a user/password combination, use auser with Web server administrator authorization; for example, on IIS, a user orgroup administrator.



Alternatively, you can set the AdminSecurity=0 flag within the[ContentServer] section of the content server configuration file. This file islocated in the content server installation directory. After changing the parameter,you must restart the Web server on which the content server is based.

2. On the Content Server Administration screen, switch to Change mode and enter thefollowing values on the Create tab page:


Content Rep. Z_DMS_PLM

Description Content repositoryfor PLM Documents

Check Signature active If you select this checkbox,the content server acceptsonly signed URLs from SAPsystems in the certificate list(see step 4 of this activity).

In the Repository Settings screen area, enter the following values:


ContentStorageHost. localhost If the MaxDB instance is notinstalled on the same serveras the content server, enterthe host name of the MaxDBinstance.

ContentStorageName <Name of MaxDBInstance>

The name of the MaxDBinstance is defined duringcontent server installation.The default value is SDB.

Storage ContentStorage.dll

Driver MaxDB Only required for contentservers installed on Windows.

3. To create the repository on your content server, choose Execute.

4. On the Certificates tab page, send the PSE of the SAP system to the content serverby choosing the Send Certificate pushbutton.The certificate appears in the certificate list.

5. Select the certificate that you just sent to the content server and choose the Activatepushbutton.

The sending and activating of certificates ensures that the content server for thisrepository only accepts URLs created by your system. This, in turn, helps toensure that no documents are deleted due to incorrect assignments in other SAPsystems.



Maintain Storage Category3.2.4UseIn this step, you set up one or more logical views (storage categories) for a storage system(content repository). The use of several views allows you to store original application files andassigned additional files in a more structured way.

This is a cross-client Customizing activity.


Customizing Menu Cross-Application Components DocumentManagement General Data Settings for StorageSystems Maintain Storage Category


2. Set up a new storage category for a storage system by choosing Edit New entriesin change mode.



Category Z_DMS_PLM

Description Storage Category forRDS documents

Document Area DMS

Content Repository Z_DMS_PLM

Define Workstation Application3.2.5UseIn this step, you define the settings for workstation applications. The workstation applicationdefines with which application a file is to be displayed, edited, and printed (for example,Microsoft Word).

You enter the path for the program name of the application. This allows you to start theapplication from different data carrier types via different paths.

Standard SettingsThe following entries are provided for the PLM Web UI:

%AUTO% (application path): The system automatically finds the program to be started foreach frontend computer. This means, the application (for example, WinWord) no longerhas to be installed under the same path on all frontend computers.

%VIEWER-CONTROL%, followed by %SAPPROVIS%: You use this entry to start anintegrated viewer. The second entry defines the user to be started.

%SAP-OFFICE-INTEGRATION.INPLACE%: You use this entry to start the MicrosoftOffice application located within the window for processing the document info record. Youmust add one of the following entries in addition:

o %XLS% for Microsoft Office Excel format



o %WRD% for Microsoft Office Word format

o %PDF% for Adobe PDF format

You can display only checked in files in the same session. If the file is checked out, anexternal session starts.

%WINDIR%: You use this entry to provide the path to a Microsoft Windows directory. Forexample, %WINDIR%\system32\mspaint.exe starts the Miscrosoft Paint application.

Procedure1. Access the transaction using one of the following navigation options:

Customizing Menu Cross-Application Components DocumentManagement General Data Define WorkstationApplication


2. On the Change View “Define Workstation Application”: Overview screen, choose NewEntries.



WS application DOC Key field

Description Microsoft Word

Archive identificatio *

File suffix for appl. doc File format for a temporaryfile

File format *.doc,*.* File format for selection viathe file manager

MIME type application/msword

Appl. Icon @J7@

Start authorization <Select thischeckbox>

Application can be startedimmediately



WS application XLS Key field

Description Microsoft Excel


File suffix for appl. Xls File format for a temporaryfile

File format *.xls,*.* File format for selection viathe file manager

MIME type application/vnd.ms-excel



Appl. Icon @J7@





WS application RH Key field

Description Viewer Document


File suffix for appl. Rh File format for a temporaryfile

File format *.rh,*.* File format for selection viathe file manager

MIME type

Appl. Icon @AR@



6. Save your entries and go back to the Change View “Define workstation application”:Overview screen.

7. On the Change View “Define workstation application”: Overview screen, select theworkstation application DOC and choose Define workstation application in network inthe dialog structure.

8. Choose the New Entries (F5) pushbutton and enter the following values:


WorkstationApplication

DOC Already filled

Data carr. Type PC

Application type 1

Path with prog. Name %SAP-OFFICE-INTEGRATION.INPLACE%%WRD%




DOC Already filled

Data carr. Type PC

Application type 2

Path with prog. Name %SAP-OFFICE-INTEGRATION.INPLACE%



%WRD%




DOC Already filled

Data carr. Type PC

Application type 3

Path with prog. Name %SAP-OFFICE-INTEGRATION.INPLACE%%WRD%


12. On the Change View “Define workstation application”: Overview screen, select theworkstation application XLS and choose Define workstation application in network inthe dialog structure.




XLS Already filled

Data carr. Type PC

Application type 1

Path with prog. Name %SAP-OFFICE-INTEGRATION.INPLACE%%XLS%




XLS Already filled

Data carr. Type PC

Application type 2





XLS Already filled

Data carr. Type PC

Application type 3






17. On the Change View “Define workstation application”: Overview screen, select theworkstation application RH and choose Define workstation application in network inthe dialog structure.




RH Already filled

Data carr. Type PC

Application type 1

Path with prog. Name %VIEWER-CONTROL%%SAPPROVIS%




RH Already filled

Data carr. Type PC

Application type 2





RH Already filled

Data carr. Type PC

Application type 3



Define Category for Markup3.2.6UseIn this step, you define a category for markups to which all layers are assigned duringredlining. The notes and comments (markups) that you attach to an original file are saved in a



layer. Markup categories serve as defining criteria for the layer. You can edit a layer preciselyif you allocate the layer to separate categories, such as engineering, and sales anddistribution. Authorization for editing the layer is assigned using an authorization object indocument management (C_DRAW_MUP - Authorizations for Markups).

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

Customizing Menu Cross-Application Components DocumentManagement General Data Define Category forMarkup


2. Make the following entry:

Category Description

ENG Engineering

Define Profile3.2.7UseIn this step, you define profiles that combine default values and settings for processingoriginal application files. The background information in a profile is standard information thatis often required in similar constellations for processing original application files.

We recommend that you assign only one role or user to a profile.


Customizing Menu Cross-Application Components DocumentManagement General Data Define Profile


2. Choose New Entries and enter the following values:

Field Name Value

Profile key Z_PROFILE

Description My profile

3. Confirm by choosing Enter and select the new entry in the table.

4. In the dialog structure, choose Assign groups/user to the profiles.

5. Choose New Entries and assign a user or role to the profile key:

Field Name Value


Role <My role>



Field Name Value

User <User ID>

6. Confirm by choosing Enter and select the new entry in the table.

7. In the dialog structure, choose Determine definitions for application.

8. Choose New Entries and enter following values, if applicable:

Field Name Value Comment


Applic. DOC Workstation application thatyou want to automaticallystart when printing ordisplaying a document.

Working directory <Path> The working directory towhich you want to copy theoriginal applications files, forexample, C:\temp\sap.

Storage Category Z_DMS_PLM The storage category forstoring the original applicationfile using KnowledgeProvider.

9. Confirm by choosing Enter and then save your entries.

Define Laboratories/Design Offices3.2.8UseIn this step, you can define which laboratories/design offices or which persons/groups ofpeople are responsible for specific document info records. You can then use the entries youdefine when maintaining document info records.

The "laboratories" and "offices" are also used by other areas, such as MaterialsManagement. For this reason, do not delete any entries that you did not make yourself.


Customizing Menu Cross-Application Components DocumentManagement General Data DefineLaboratories/Design Offices


2. Choose New Entries and enter the following values:

Field Name Value

Lab/Office ENG

Test: Lab./engineeringoffice

Engineering

3. Confirm by choosing Enter and then save your entries.



4 Enhanced Document ManagementConfiguration (PLM Web UI)

4.1 Activate Business FunctionsUseTo enable the SAP PLM Web UI objects, you must activate business functions in the system.

Activating a business function makes irreversible changes to your system. Beforeactivating a business function, make sure that you check the documentation for moreinformation about the impact of a particular business function.Business functions are visible in the Switch Framework only if you have implemented thecorresponding enhancement package.


Transaction Code SFW5

SAP Menu Tools ABAP Workbench Development SwitchFramework

2. On the Switch Framework: Change Business Function Status screen, expand theEnterprise Business Functions node.

3. Select the checkbox in the Planned State column for the following business functions:

Business Function Description

ERP_ENTERPRISESEARCH Embedded Search in SAP ERP

/PLMU/IPPE_INT PLM IPPE Integration

/PLMU/WEB_UI PLM Web User Interface

/PLMU/WEB_UI_2 PLM Web User Interface 2

/PLMU/WEB_UI_3 PLM Web User Interface 3

4. Choose the Activate Changes pushbutton.

4.2 Set Up Web Dynpro Install Services4.2.1

UseTo activate Document on PLM Web UI, you must install the required web services.

Procedure1. Call the following transaction:

Transaction Code SICF_INST

2. On the ICF: Report for Activating Special Service During Installation screen, enterWEB DYNPRO ABAP in the Technical Name field.

3. Choose Execute.



Activate Services4.2.2UsePLM Web UI uses HTTP services, which are defined in the Internet CommunicationFramework (ICF). By default, HTTP services are delivered as inactive for security reasons.


Transaction Code SICF

2. On the Maintain Services screen, enter Service in the Hierarchy Type field to filter theICF hierarchy.

3. Choose Execute.

4. Under Virtual Hosts / Services, expand the hierarchy as follows to access the relevantservices and choose Activate Service in the context menu of each service:

Service Name Position in Hierarchy

PLMU Default_host SAP BC WebDynpro PLMU

ESH_ADMIN_UI_COMPONENT Default_host SAP BC WebDynpro SAP ESH_ADMIN_UI_COMPONENT

ESH_ENG_MODELLING Default_host SAP BC WebDynpro SAP ESH_ENG_MODELLING

ESH_ENG_WIZARD Default_host SAP BC WebDynpro SAP ESH_ENG_WIZARD

COCKPIT Default_host SAP ES COCKPIT

SAPLINK Default_host SAP ES SAPLINK

SEARCH Default_host SAP ES SEARCH

nwbc Default_host SAP bc nwbc

4.3 Set Up Embedded SearchUsePLM Web UI uses Embedded Search as the search engine within the work center and onobject-specific search UIs.

Embedded Search has to be installed before you can use the work center. However, it ispossible to switch to a database search on the search UIs.

Prerequisites You have installed SAP NetWeaver Search and Classification (TREX) and have a

working TCP/IP connection to the SAP ERP system. To perform the search configuration, your user has the SAP_ESH_LOCAL_ADMIN role

and the SAP_ESH_LOCAL_ADMIN profile.Note that the SAP_ESH_LOCAL_ADMIN role should usually be sufficient. However, ifyou face any authorization errors, assign other required roles or SAP_ALL andSAP_NEW authorization.



Connect TREX and Embedded Search4.3.1UseEmbedded Search uses a TREX Search Engine running on a remote computer. You must seta TREX destination to enable Embedded Search to connect to the TREX server.

After installing the index server, it may be necessary to apply additional SAP Notes to theSAP system. For more information, see SAP Note 1518396. Make sure that you also applySAP Note 1462623, which provides report ESH_OM_ADJUST_NONCONF_KEYWORDS to resolvethe issue. Otherwise, an error will occur when setting up the connection that is essential forthe Embedded Search.

4.3.1.1 Check TREX DestinationPrerequisites

The RFC connection to TREX has been set up in SM59 by the customer’s systemadministration.

You know the name of the TREX RFC destination.


Transaction Code SM59

2. Choose the Search pushbutton and enter your TREX RFC destination.

3. Choose your TREX RFC destination.

4. On the RFC Destination screen, choose the Connection Test pushbutton.

5. On the next screen, check the connection test results.A result should be shown for all test packages.

4.3.1.2 Set TREX DestinationProcedure

1. Call the following transaction:

Transaction Code SE38

2. On the ABAP Editor: Initial Screen, enter ESH_ADM_SET_TREX_DESTINATION in theProgram field.

3. Choose Execute.

4. On the Set the RFC destination of TREX screen, enter your RFC destination forTREX.

5. Choose Execute.

If the RFC destination for TREX has not yet been set, the following system messageappears: RFC destination for TREX changed to <RFC Name>. Otherwise, an errormessage appears, which you can ignore.



4.3.1.3 Clean Up TREX DataUseTo avoid problems caused by legacy data relating to your client, you can use reportESH_ADM_INDEX_ALL_SC to clean up all client-specific settings related to EmbeddedSearch.


Transaction Code SE38

2. On the ABAP Editor: Initial Screen, enter ESH_ADM_INDEX_ALL_SC in the Programfield.

3. Choose Execute.

4. On the next screen, select the checkbox Delete All Search Connectors and deselectall other checkboxes

5. Choose Execute.

Wait for system confirmation that step 1 is complete.

By performing this step, you delete all search connectors including those from othersoftware components, not just the search connectors from PLM-WUI.

Set Up Search Connectors for Embedded Search4.3.2UseThis step is required to configure Embedded Search (ESH) technology.


Transaction Code ESH_COCKPIT

2. On the Connector Administration Cockpit screen, the following system messageappears: Resolution of pending text references is already running.

If no system message appears, the background job has already been scheduled andyou can proceed with the next step.

If a background job for Embedded Search is already running (for example, initialset up of Embedded Search; creating or deleting search connectors), thisbackground job could block further activities such as creating or deleting anothersearch connector. We therefore recommend that you wait until this backgroundjob has been completed before you continue with the next steps.



4.3.2.1 Create Search ConnectorsUseThis section describes the steps required to create search connectors and indexes for thedifferent PLM business objects. You first have to create connectors, then prepare them, andfinally run indexing.



2. On the Connector Administration Cockpit screen, choose the Create pushbutton.

3. In the dialog box, select SAP PLM Web UI in the Software Component field.

This action prompts the Connector Templates table to rebuild, which may take a fewmoments. Once rebuilt, the list displays several connector entries.

4. Select the business objects (models) that you want to use in the PLM environment.Use the following table:

Field Name Input Value

Business objectname DOCUM_INFO_REC

Include all connectors that are added automatically in the next steps.

5. Choose the Create Connector pushbutton.

The search connectors are prepared in the background. The status of each searchconnector changes from New to Preparing, and finally to Prepared. The statuschange may take some time. You can use the Refresh pushbutton to update your list.

4.3.2.2 Perform a Full Indexing RunUseOnce all the search connectors have been prepared, you can perform a full indexing run.

Procedure1. Select all table entries (by clicking on the first table entry and clicking with pressed

Shift key on the last table entry) and choose Actions Schedule Indexing.

2. In the Schedule Indexing dialog box, choose Show Input Form.

3. Select the Start Immediately checkbox.

4. In the table selection menu, select all table entries.

5. Choose the Copy Settings pushbutton.The Start Immediately checkbox is now selected for every object type.

6. Confirm this step and begin full indexing by selecting OK.After a short time, the status of the search connector changes to Schedule forIndexing. Choose the Refresh pushbutton to monitor your system activities.During data indexing, the status of the search connector changes to Indexing.Indexing is complete once the status changes to Active. In addition, a checkmarkappears in the Search column.If your user has sufficient authorization, your name appears as the job creator; if not,a general ESH user is used to extract the data.



4.3.2.3 Schedule Delta IndexingUseTo keep your data in the TREX search engine up to date, you need to transfer all changesthat have been made in the SAP ERP system to TREX. This procedure is called deltaindexing, and it is triggered by ABAP background jobs. In general, you can choose to updateyour data either periodically or using real-time indexing.

Note that not every search connector can use real-time indexing. In this case, you have tochoose a periodical interval for delta indexing. You can choose a different indexing schedulefor each object type of a search connector.

Real-time indexing or short-time intervals in scheduled delta indexing requiresbetter hardware than long-time intervals in scheduled delta indexing.

Procedure1. To schedule the updates using real-time indexing, call the following transaction:


2. In the Search Object Connectors list, select all entries (by clicking on the first tableentry and clicking with pressed Shift key on the last table entry) and choose Actions

Schedule Indexing.


4. Select the Start Immediately checkbox.

5. Select the Real-Time Indexing checkbox.

6. In the table selection menu, select all table entries.

7. Choose the Copy Settings pushbutton.

8. Choose the OK pushbutton to save your settings.The status of some search connectors could change to Schedule for Indexing.Choose the Refresh pushbutton to monitor your system activities.During data indexing, the status of the search connector changes to Indexing.Indexing is complete once the status changes to Active again.

In the next step, you configure a one-day interval for delta indexing for all object types ofthe different search connectors that do not support real-time indexing:1. In transaction ESH_COCKPIT, select all entries in the Search Object Connectors list

(by clicking on the first table entry and clicking with pressed Shift key on the lasttable entry) and choose Actions Schedule Indexing.


3. Enter the current date in the Start Date field.

4. Enter 23:30:00 in the Start Time field.

5. In the Recurrence Period screen area, enter 001 in the Days field.

6. Do not select the Real-Time Indexing checkbox.

7. In the table, select all object types for which the Real-Time Indexing checkbox is notselected.

8. Choose the Copy Settings pushbutton.

9. Choose the OK pushbutton to save your settings.



4.4 Document in PLM Web UICarry out the following Customizing activities and implement the required Business Add-Ins(BAdIs) in Customizing for Logistics – General under Product Lifecycle Management (PLM)

PLM Web User Interface Objects in PLM Web UI Document in PLM Web UI:

Customizing Activity / BAdI Description

Define Document Types for Folder Creation You define which document types can beused to create folders in the PLM Web UIDocument Browser application.

BAdI: Enrich Object Link Information(/PLMI/EX_DIR_LINK)

You can use this BAdI to implementcustomer-specific object types linked to adocument info record (DIR).

BAdI: Change Search Sequence forViewable File(/PLMI/EX_DIR_THMB)

You can use this BAdI to implement acustomer-specific search for a thumbnail.

Define Search Sequence for Viewable File You define the search sequence for choosingfiles from SAP objects to be displayed as athumbnail or in the Viewer. For example, billof material (BOM), material, and document.You can link a file from an SAP object todocuments and display them as eitherthumbnails, or in the Viewer.For more information, see the examplebelow.

BAdI: SAP Easy Document ManagementEnhancements(EASYDMS_MAIN01)

In PLM Web UI, you can use this BAdI in thedocument browser to display or hide rootfolders for individual users.Note:The BAdI provides several implementationsthat are not applicable for the documentbrowser. Only the implementation forSHOW_ROOTS is considered.

BAdI: Definition of Explosion Settings forDocument Browser(/PLMI/EX_DIR_BRW_EXPLSN_SETING)

You can use this BAdI to filter out thedocuments from the content regiondepending on the options chosen from thedropdown menu.

Icon for Release Status You can activate the release status icon onthe PLM Web UI for documents.

Additional Settings You set values to parameters that define thebehavior of certain functions in Document onthe Web UI.

For more information, see the documentation of the Customizing activities and BAdIs in thesystem.

The following table shows example settings for the Customizing activity Define SearchSequence for Viewable File:

SAPobject

VAppl Num Type Applic.

MARA T Thumbnail 0 KPR RH

MARA V Viewer 1 KPR RH



4.5 Process Route Maintain Standard Settings4.5.1

UseIn this step, you maintain standard settings automatically for the workflow.

Prerequisites User WF_BATCH has the required authorization to configure the RFC destination as

part of the automatic Customizing workflow. Therefore, make sure the SAP_ALL userprofile is assigned to this user.

Your user belongs to the SUPER user group that is assigned in transaction SU01.


Customizing Menu SAP NetWeaver Application Server BusinessManagement SAP Business Workflow MaintainStandard Settings

Transaction Code SWU3

2. Choose the Perform Automatic Workflow Customizing (F9) pushbutton.

ResultThe following activities are carried out automatically and are marked green in the MaintainRuntime Environment screen area:

Configure RFC destination

Maintain system administrator for workflow

Maintain active plan version

Classify decision task as general

Document generation/form integration

Maintain time units

Schedule background job for missed deadline

Schedule background job for work items with errors

Schedule background job for condition evaluation

Schedule background job for event queue

Schedule background job for clearing reports

Define Number Range Interval4.5.2UseIn this step, you define the number range interval 01 for the process route.




Customizing Menu Logistics - General Product Lifecycle Management(PLM) Case Management Set Process RouteCreate Number Range Interval 01 for Process Route


2. Select activity area SCMG.

3. Choose the Change Intervals pushbutton.

4. Enter the interval with the number 01 from 000000000001 to 999999999999.


Activate Process Route Workflow4.5.3UseIn this step, you activate an event to trigger the process route.

Procedure1. Access the General Task Maintenance activity using transaction PFTC.

2. Select the WS Workflow template task type.

3. Enter task 00100012.

4. Choose the Display (F7) pushbutton.

5. Make sure that event START_WORKFLOW is active for this workflow.

You can check the status on the Triggering Events tab page. A green light in the firstcolumn indicates that the status is active. If the Triggering Events column is notactive, click on the column to activate it.

Define Task Types4.5.4UseIn this step, you define the workflow template and tasks as general tasks so that they can beassigned to all users.



3. Enter task 00100012.


5. Choose Additional Data Agent assignment Maintain.

6. On this screen, select GOS Object frame workflow.

7. Choose the Attributes pushbutton.

8. In the dialog box, select the General Task radio button.

9. Choose the Transfer pushbutton.

Repeat steps 4-9 for workflow tasks 00100010 and 00100011. To do this, select task type TSStandard Task in step 2 and enter 00100010 or 00100011.



Synchronize Runtime Buffer4.5.5UseIn this step, you synchronize the runtime buffer.

Procedure1. Call transaction SWU_OBUF.

2. Choose the Start Synchronization pushbutton.

4.6 Digital SignatureIn a set of work instructions, signatures can be used by a processer to sign off a work step orconfirm an input value that lies outside the predefined value range. The following chapterdescribes the steps required to implement a simple digital signature process by using the signaturemethod System signature with authorization by user ID and password.

Maintain Basic Settings for Digital Signature4.6.1UseIn this step, you enter the required data in the user master records of users who are to signdocuments using digital signatures and who are to receive the relevant workflow items.

Procedure1. Access the transaction as follows:

Customizing Menu Production Planning for Process Industries ProcessManagement Control Recipes / PI Sheets DigitalSignatures Maintain Basic Settings for Digital Signature

Transaction Code SU01

2. Enter the user ID of the user whose data you want to maintain and choose Change.

3. On the Address tab page, enter the user's first and last names.

4. On the Defaults tab page, enter the user's personal time zone.


Specify Signature Method for Approval Using Simple4.6.2Signature

UseIn this step, you define the signature method that is to be used for approving an SAP object with asimple digital signature.


Customizing Menu Production Planning for Process Industries ProcessManagement Control Recipes / PI Sheets DigitalSignatures Specify Signature Method for ApprovalUsing Simple Signature


2. On the screen “Specify Signature Method for Approval Using Simple Signature:”Overview, choose New Entries.



3. In the table Specify Signature Method for Approval Using Simple Signature, enter thefollowing values:

Field Name Value

Signature Obj. Type Document Management: Status Change

Signature Method System Signature with Authorization by SAPUSERID/Password


Define Authorization Groups4.6.3UseIn this step, you define authorization groups for digital signatures. The authorization groupsdefined in this step are the link between a recipient of a task (defined by the assignment of anauthorization group to a user master record) and a workflow task (defined by the assignment of anauthorization group to a signature strategy).


Customizing Menu Production Planning for Process Industries ProcessManagement Control Recipes / PI Sheets DigitalSignatures Signature Strategy Define AuthorizationGroups


2. On the screen “Authorization Group for Digital Signatures:” Overview, choose NewEntries.

3. In the Authorization Group for Digital Signature table, enter the following values:

AGrpDigSig Authorization Group for Digital Signature

KPR_AUT1 Sign Off Stage 1

KPR _AUTH2 Sign Off Stage 2


Define Individual Signature4.6.4UseIn this step, you define the digital individual signatures that have to be executed by usersbelonging to a certain authorization group. You can use the individual signatures as partialsteps of a signature strategy that is executed when you release a document.


Customizing Menu Production Planning for Process Industries ProcessManagement Control Recipes / PI Sheets DigitalSignatures Signature Strategy Define IndividualSignatures




2. On the “Define Individual Signatures:” Overview screen, choose New Entries.

3. In the Authorization Group for Digital Signature table, enter the following values:

Indiv. sig. AGrpDigSig Indiv.signature descriptn

KPR _SIG1 KPR _AUT1 Ind.signature for documents- Operate

KPR _SIG2 KPR _AUT2 Ind.signature for documents– Sign Off


Define Signature Strategy4.6.5UseIn this step, you define a signature strategy that consists of partial steps of a set of individualsignatures.


Customizing Menu Production Planning for Process Industries ProcessManagement Control Recipes / PI Sheets DigitalSignatures Signature Strategy Define SignatureStrategies


2. On the “Define Individual Signatures:” Overview screen, choose New Entries.

3. In the Signature Strategy table, enter the following values:

Column Title Value

SigStrat KPR_STRA

Signature StrategyDescription

Signature Strategy PLM Document

Signature Method System Signature with Authorization by SAPUSERID/Password

Display Comment Possible

Display Remark Possible

Disp. Document Possible

Verification <Deselect this checkbox>

4. Choose Enter.

5. Select the recently added signature strategy KPR_STRA and choose Assignindividual signatures in the dialog structure.

6. Choose New Entries and enter the following values in the Assign individualsignatures table:



Column Value

Indiv. Sig. KPR_SIGN01

KPR SIGN02

7. Choose Enter and save your entries.

Workflow and Document Management Integration4.6.64.6.6.1 Activate Process Route WorkflowUseIn this step, you activate an event to trigger the process route.

PrerequisitesYou have configured a basic workflow for processing workflow tasks. For more information,see section 4.5.1 and 4.5.2.



3. Enter task 002000020.


5. Make sure that the START_WORKFLOW event is active for this workflow.

You can check the status on the Triggering Events tab page. A green light in the firstcolumn indicates that the status is active. If the Triggering Events column is notactive, click on the column to activate it.

4.6.6.2 Define Task TypesUseIn this step, you define the workflow template and tasks as general tasks so that they can beassigned to all users.


2. Select the TS Standard task task type.

3. Enter task 002000038.


5. Choose Additional Data Agent assignment Maintain.

6. On this screen, select GOS Object frame workflow.

7. Choose the Attributes pushbutton.

8. In the dialog box, select the General Task radio button.

9. Choose the Transfer pushbutton.



4.6.6.3 Activate Digital Signature PackageUseIn this step, you activate the use of digital signatures when the status of a document changes.


Customizing Menu Cross-Application Components-> Document Management Control Data Define Document Types


2. On the Change view: "Define Document types:” Overview screen, double-click thedocument type that is to use the digital signature package (for example, KPR).

3. On the Change view: "Define Document types: Details" screen select the Use DSPackage checkbox.

4. Go back to the "Define Document types:” Overview screen.

5. In the table, select the relevant document type (for example, KPR) and choose Definedocument status” in the dialog structure.

6. In the list of document statuses, double-click the status for which a digital signature isrequired (for example, RE – Released).

7. In the Workflow Task screen area, enter the following values:

Field Name Value

Object Type WS

Object ID 2000020

8. In the SignStrat. Field, enter KPR_STRA.


ResultYou have activated the digital signature package for a document type and assigned thesignature strategy and workflow template.

4.6.6.4 Define Workflow Processors by PFCG RolesUseIn this step, you create a set of PFCG roles that contain the authorization objectC_SIGN_BGR. These roles provide the user with authorization to process a certain digitalsignature.

Procedure1. Call transaction PFCG and enter Z_KPR_SIGN_AUTH01 in the Role field.2. Choose the Single Role pushbutton.3. Enter a description, for example, “Authorization to Process Individual Signature 01”

and save the role.4. On the Authorizations tab page in the Maintain Authorization Data and Generate

Profile screen area, choose Change Authorization Data.5. On the Choose Template screen, choose Do not select templates.6. Choose Manually or Manual entry of authorization objects (CTRL+SHIFT+F9) and

enter C_SIGN_BGR.



7. Choose Continue.8. Expand the hierarchy completely for role Z_RDS_SIGN_AUTH01.9. Choose Change for the Authorization Group for Digital Signature.10. In the Interval field, enter the authorization group KPR_AUTH01 and confirm by

choosing Enter.11. Choose Back (F3).12. In the dialog box Exit Authorization Maintenance, choose Generate F6 and then Save

F5.13. On the User tab page, enter the user IDs of the users that are to process individual

signatures of authorization group 01.14. Save your entries and then choose the User Comparison pushbutton.

Repeat steps 1-14 for the role Z_ KPR _SIGN_AUTH02, using the following values:

Role description: Authorization to Process Individual Signature 02 Authorization group: Z_ KPR _SIGN_AUTH02 Users: IDs of the users that are to process individual signatures of authorization

group 02

4.7 Viewer Define Viewer Installation4.7.1

UseIn this step, you define the URL that will be used for downloading and installing the viewer. If theviewer is not yet installed, the URL defined here will be displayed. The end user can then followthis link and install the viewer.

This is a cross-client Customizing activity.


Customizing Menu Cross-Application Components Processes and Toolsfor Enterprise Applications Viewer Define ViewerInstallation


2. Check the following entries and enter your own download URL:

Field Name User Action andValues

Comment

ID SAPPROVIS

Viewer Name SAPPROVIS

URL Link HTTP://SAPPROVIS.COM

Change the URL to a customer-specific download location.



Define Viewer Application4.7.2UseIn this step, you define the entries that are relevant for redlining, such as the redlining identifier. Ifyou want to use redlining, the identifier you enter in the Redlining ID field will be used as the prefixin the file name when you save layers or markups.


Customizing Menu Logistics - General Product Lifecycle Management(PLM) PLM Web User Interface PLM WebApplications Viewer Define Viewer Application




ABB ID

Redlin. ID SAPPROVIS

Explosion I Stop explosion atviewable

Geo. Data A All levels


ABB ID PLM_DIR

Redlin. ID SAPPROVIS

Explosion I Stop explosion atviewable

Geo. Data A All levels


4.8 Set Up White ListThe white list contains the authorized servers and directories used to communicate WebDynpro UI elements using HTTP. An administrator stores this list locally.

To avoid problems related to uploading original files of a DIR to Kpro and downloading themfrom Kpro, properly configured white list settings should be downloaded to the user’scomputer.

For more information about configuring the white list, see SAP Note 1706291. In addition,see SAP Library for SAP NetWeaver 7.4 on SAP Help Portal athttp://help.sap.com/nw74. Under Application Help, choose UI Technologies inSAP NetWeaver UI Frameworks Based on Application Server ABAP DevelopingWeb Dynpro ABAP Applications Tasks Web Dynpro ABAP: Development in Detail

Integration Active Component Framework (ACF) Working with White Lists.



PrerequisitesWorking with a white list in an SAP system requires a certificate for the system used. Thecertificate is stored in table WDR_ACF_WL_CERT.

You have done the following:

Imported a certificate from a central system or generated a certificate usingtransaction WDR_ACF_GEN_CERT.

Installed SAPCRYPTOLIB. For more information see SAP Note 455033.

To check the installation of SAPCRYPTOLIB, use transaction STRUST. Check whetherthe SAPCRYPTOLIB entry exists.

Generate Certificate for White List4.8.1UseThis transaction is used to create and transport certificates. This enables all ABAP systems (as ofSAP NetWeaver 7.02) belonging to the same customer to be provided with the same certificate,which means that only one certificate has to be distributed for the installation.

Note on creating a certificate: If the old certificate has been overwritten, the new certificate mustalso be distributed to the end users. If this has happened by mistake, a transported certificate canbe reimported.

PrerequisitesYou have applied SAP Note 510007 (SSL Library). If you do not do this, the system issues theerror message Certificate cannot be read.


Customizing Menu SAP NetWeaver Application Server Web DynproABAP Generate Certificate for White List

Transaction Code WDR_ACF_GEN_CERT

2. Select Generate New Certificate.

3. Choose Execute.

Set Up Active Controls White List4.8.2UseThe authorized servers and directories are contained in a white list. If requests for access todirectories or servers are sent using HTTP or HTTPS, the control first checks whether this isallowed.


Customizing Menu SAP NetWeaver Application Server Web DynproABAP Set-up Active Controls White List

Transaction Code WDR_ACF_WLIST



2. In change mode, choose the New Entries (F5) pushbutton and enter the followingvalues:

Whitelist Whitelist

DEFAULT Default white list for everybody

3. Choose Enter.

4. Select the default white list in the table and choose Whitelist for File Extension in thedialog structure.


Whitelist File Extension

DEFAULT DOC

XLS

RH

JPG

6. Choose Enter.

7. Select the default white list in the table and choose Download (Server->Directory) inthe dialog structure.


9. Choose Enter.

10. Select the default white list in the table and choose Upload (Directory -> Server) inthe dialog structure.



Define URL of Storage Category4.8.3UseThe URL of the storage category is required for uploading and downloading files.



Whitelist File Store File Extension

DEFAULT C:\ D Directory


DEFAULT C:\ D Directory




2. Select the default white list in the table and choose Download (Server->Directory) inthe dialog structure.


Findthe URL of a Storage Category (Z_DMS_PLM)To set up the white list, you must know the server and port number. You use a storagecategory for uploading and downloading. The server is available in the details of thecorresponding content repository.

Procedure1. Use transaction OACT to access the content repository of a storage category.

Alternatively, you can access the content repository of a storage category inCustomizing for Logistics - General under Product Lifecycle ManagementDocument Management General Data Settings for Storage SystemsMaintain Storage Category.

2. Use transaction CSADMIN to access the content repository details.

Alternatively, you can find the content repository details in Customizing for SAPNetWeaver under Application Server Basis Services Knowledge ProviderContent Management Service Administrate Content Server.

3. If you use the database as the storage medium (DMS_C1_ST) then use the serveraddress as the URL.

4. Choose Enter to confirm.

5. Select the default white list in the table and choose Upload (Server->Directory) in thedialog structure.



ResultThe white list has been completed and can be downloaded.


DEFAULT <URL of storagecategory>

Server


DEFAULT <URL of storagecategory>

Server



Activate Active Controls White List4.8.4UseEach user must install this white list locally on his or her PC. Administrators can do this usingtransaction ACF_WHITELIST_SETUP, which is installed locally on their PC.


Customizing Menu SAP NetWeaver Application Server Web DynproABAP Activate Active Controls White List

Transaction Code ACF_WHITELIST_SETUP

2. Execute the activity.

3. Choose the Install Certificate pushbutton.

ResultThe white list (file SAPFrontendService<SystemID><generic String>.xml) is createdlocally on each PC.

Saving Certificates Using the Browser4.8.5UseIn this step, you deactivate the security standard and make it possible for users to savecertificates using the browser.

Saving certificates using the browser deactivates an SAP security standard. Setting this switchis therefore at your own risk and assumes that all possible consequences have beenconsidered.

This setting is valid for all users across the entire application server and is therefore usuallyperformed by administrators.

For more information about using this option in transaction WDR_ACF_WLIST, see SAP Note1731458.




2. Choose the Allow Cert. to be Saved Using Browser pushbutton.

3. In the next dialog box, choose the Deactivate pushbutton.

ResultIf the Web Dynpro application WD_ACF_DOWNLOAD_CERTIFCAT is started by a user orautomatically as part of an application, it is now possible to save the certificate using the browser.

The save procedure is visible to the user and requires the user's explicit confirmation by choosingthe Save Certificate pushbutton of the related browser dialog. After being downloadedsuccessfully, the local storage path of the certificate is displayed.



The current status of the option Allow Cert. to be Saved Using Browser is now constantlydisplayed in the browser dialog, that is, Saving Certificate is Allowed.

Reactivating the Security StandardIf you decide to reactivate the security standard, you must first repeat step 1. On the next dialogscreen in step 2, select Activate. It is then no longer possible to save certificates using thebrowser, the status message in the browser shows a relevant text, and the Save Certificatepushbutton is no longer active.

Releasing All Client DirectoriesReleasing client directories also deactivates an SAP security standard. Setting this switch istherefore at your own risk and assumes that all possible consequences have been considered.

By setting the All Client Directories switch, all available drives, network drives, and directories arereleased for writing and reading the files on the frontend computer. This means that existing clientrestrictions that were entered in the white list are ignored after release. The white list itself is stillused as it can contain further entries (for example, addresses of the content server, starting ofapplications, and so on).

Specified content servers are not affected by this change.

4.9 Roles and AuthorizationsUseTo access PLM documents, you need certain authorizations and you therefore need newadditional roles. To assign authorizations and user menus in PLM Web UI, you must assignseveral roles.


Transaction Code SU01

2. On the Roles tab page, assign the following roles:

Role Name Purpose

SAP_PLMWUI_MENU (EHP4)

SAP_PLMWUI_DISCRETE_MENU (EHP5)

SAP_PLMWUI_DISCRETE_MENU2 (EHP6)

User menu with links to PLM WebUI

SAP_PLMWUI_TRUSTED_USER_ALL(EHP4)

SAP_PLMWUI_TRUSTED_USER_ALL2(EHP5)

Trusted user for PLM documents,required for accessing documentson the PLM Web UI with theaccess control context


4.10 Launchpad CustomizingUseIn this step, you can maintain navigation launchpads for Document on PLM Web UI.


Transaction Code LPD_CUST



2. The following launchpads are available for the PLM Web UI:

Role Instance Description

PLM CM_DIR_BROWSER Context Menu for DocumentBrowser

PLM YCA_DIR You can also - DIR

PLM CM_DIR Context Menu Documents



4.11 Front-End Installation SAP NetWeaver Business Client4.11.1

SAP NetWeaver Business Client (NWBC) is a new SAP UI that provides end users with theseamless integration of classic SAP GUI-based transactions and newer Web Dynpro-basedapplications. The desktop variant offers a high-fidelity UI to improve user experience. Thus,the NWBC provides a typical, modern desktop-based user experience.

There are two types of NWBC:

NWBC for HTML is a browser-based shell for ABAP systems that is used for casualuse scenarios. Within this environment, all SAP GUI transactions are rendered usingthe SAP GUI for HTML rendering engine.

NWBC for Desktop is a Microsoft .NET-based application that targets the poweruser. In this scenario, the SAP GUI itself is used as the rendering engine if installed.NWBC effectively replaces SAP GUI as the main entry point to SAP applications.

SAP NetWeaver Business Client is available as of SAP NetWeaver 7.02 SP02.

ProcedureDownload the software from SAP Service Marketplace at http://service.sap.com/installations

A-Z Index NETWEAVER BUSINESS CLIENT.

After downloading the software, install the SAP NetWeaver Business Client on a local PC.

For further requirements and restrictions, see SAP Note 1029940. For configurationinstructions, see SAP Note 1368177.

Note that when using NWBC for Desktop, specific information is required for the frontendconfiguration. To determine the URL for the NWBC for Desktop configuration, proceed asfollows:

1. Log on to your SAP system using SAP GUI.

2. Start transaction NWBC.NWBC for HTML opens in the default browser.

3. Copy the path from the address, for example, https://<domain>:<portnumber>/nwbc.Ignore any additional path information in the URL after “…/nwbc”.

4. Start NWBC for Desktop and create a new connection.

5. Define the following parameters:

a. Name: <for example, DMO System>

b. URL: https:// <domain>:<portnumber>/nwbc

c. Type: ABAP

d. Client: <Client number>

6. Choose the Connect (Restart) pushbutton.

If problems occur, see SAP Note 1400383.

More InformationFor more information, see SAP Note 900000. Once you have installed SAP NetWeaverBusiness Client, you can access the documentation by choosing Help ShowDocumentation.



Installation of Java Runtime Environment4.11.2To run the WebDynpro application of the PLM Web user interface and to upload anddownload originals using the Active Component Framework (ACF), you must have JavaRuntime Environment 1.6 or above installed on your local machine.

ProcedureDownload the software at http://www.java.com/en/download/.

The following Java Runtime environment releases are currently supported: JRE 1.6.0.13 orhigher.

SAP Visual Enterprise Viewer4.11.3Product visualization is an integral component of modern business software solutions. TheSAP viewer for 2-dimensional (2D) images and 3-dimensional (3D) scenes provides basicvisualization as a permanently available and fully integrated solution component. That is,basic viewing functionality is always available to enable the visualization of parts andassemblies when working on tasks within a business process.

ProcedureDownload the software from SAP Service Marketplace athttp://service.sap.com/installations Support Packages and Patches Search for SupportPackages and Patches.

Enter Visual Enterprise Viewer as the search term and start your search. As a minimum,download Visual Enterprise Viewer 7, which includes redlining and digital mock-up (DMU).



5 SAP 3D Visual Enterprise Generator5.1 Map VEG Instance to Logical PortUseIn this step, you configure the Visual Enterprise Generator (VEG) instance. This instancename represents Visual Enterprise Generator as the conversion server in the SAP system.

Procedure1. Access the Customizing activities as follows:

Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator Map VEGInstance to Logical Port


2. On the Maintain VEG Instance: Overview screen, choose the New Entries pushbuttonand enter the following values:


Instance <VEG_Instance>

Logical Port <Name of your logical Port>


Depending on your system, you may have to create or use an existing Customizingrequest.

5.2 Maintain Conversion TriggerUseIn this step, you configure the conversion trigger. This is the main configuration activity todefine what can be converted and how.


Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator MaintainConversion Trigger


2. On the DMS VEG Conversion Specifications: Overview screen, choose the NewEntries pushbutton and enter the following values:


Document Type KPR

Sequence No 1

Document Status

Auto Start




Application Type <Your CAD workstation application>

Explosion Mode Single File

VEG Instance <Your VEG instance>

Configuration ID CONVERT 3D CAD


Document Type KPR

Sequence No 2

Document Status FR

Auto Start X


Explosion Mode Actual


Configuration ID CONVERT ASSEMBLY CAD


Document Type KPR

Sequence No 3

Document Status

Auto Start


Explosion Mode Actual


Configuration ID CONVERT ASSEMBLY CAD

3. Save your entries

Depending on your system, you may have to create or use an existing Customizingrequest.

ResultYou have configured the conversion triggers. These settings allow you to convert CAD datathat is attached to document info records of the defined document types.



5.3 Map Storage Category to VEG Application ServerUse

In this step, you map a Visual Enterprise Generator (VEG) application server to a storagecategory. Based on the storage category of the document, the system picks the VEG applicationserver for conversion. This enables the load balancing scenario.


Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator MapStorage Category to VEG Application Server


2. On the Tag Category: Overview screen, choose the New Entries pushbutton andenter the following values:


Category Z_DMS_PLM

Instance <Your VEG instance>


5.4 Define Tag CategoryUseIn this step, you define a tag category that represents a metadata category in the converted3D visualization files for metadata from the SAP system.


Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator MaintainTag Category


2. On the Tag Category: Overview screen, choose the New Entries pushbutton andenter the following values:


Tag Category SAP

Category Description SAP Business Objects


ResultYou have configured a metadata category with the name SAP that is to be created in all 3DRH files that are generated using SAP 3D Visual Enterprise Generator.



5.5 Map Tag Name to Tag CategoryUseIn this step, you create a new metadata field, MATERIAL, to display tagged IDs of a linkedmaterial master, and you assign it to a previously created metadata category.


Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator Map TagName to Tag Category


2. On the Tag ID for Metadata: Overview screen, choose the New Entries pushbuttonand enter the following values:


Tag Category SAP

Tag Name MATERIAL <In upper case only>

Tag Description (+) <MATERIAL OBJECT>


ResultYou have configured the field MATERIAL within the metadata category SAP that is to beadded to all 3D RH files that are authored using SAP 3D Visual Enterprise Generator.

5.6 Map BCV Tag to Tag NameUseIn this step, you map the Business Context Viewer (BCV) tag to a tag name. The mapped BCV tagreads the value of the tag name and enables the system to display the analytical data of an objectin the BCV side panel.


Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator Map BCVTag to Tag Name


2. On the Map BCV Tag to Tag Name: Overview screen, choose the New Entriespushbutton and enter the following values:


Tag Category SAP

Tag Name MATERIAL <In upper case only>




BCV Tag /BCV/:1MATERIAL <In upper case only>


5.7 Maintain Tag MappingUseAny object link of a DIR can be tagged in the RH file generated by SAP 3D Visual EnterpriseGenerator. In this step, you define an object link for a material master object that is to betagged. This has to be done for each document type that contains originals that are to beconverted by SAP 3D Visual Enterprise Generator.


Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator MaintainTag Mapping


2. On the Assembly Tagging Customizing Table: Overview screen, choose the NewEntries pushbutton and enter the following values:


Ty. RDS <Assembly Document Type>

SAP object MARA

Tag Category SAP

Tag Name MATERIAL

3. Save your entriesDepending on your system, you may have to create or use an existing Customizingrequest.

ResultAll of the 3D RH files created using SAP 3D Visual Enterprise Generator for the abovedocument types contain SAP business data for the material number, filled from documentobject links. To see the SAP business data, launch an RH assembly file and display the treestructure.

If additional fields need to be tagged, this can be extended by consultants outside of therapid-deployment solution package.

5.8 Maintain Application UsageUseIn this step, you specify the applications for which the search sequence to view a viewable file for adocument is defined.




Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator MaintainApplication Usage


2. On the View for Usage Application Maintenance: Overview screen, choose the NewEntries pushbutton and enter the following data:


Usage DMS

Appl. Description DMS

Usage CDESK

Appl. Description CAD Desktop


5.9 Define Search Sequence for Viewable FileUse

In this step, you define the search sequence for choosing files from SAP objects to be displayed asa thumbnail, in the Viewer, and so on. For example, you can view the 3D file of a material in theViewer. You can also define the search sequence that must be used for an application. You canlink a file from an SAP object to documents and display them as either thumbnails, or in theViewer.


Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator DefineSearch Sequence for Viewable File


2. On the Define Search Sequence for Viewable File: Overview screen, choose the NewEntries pushbutton and enter the following data according to your requirements:


SAP Object DRAW

Viewing T Thumbnails

Usage DMS

Sequence 1

Document Type KPR

Application JGP




5.10 Define Profile for Excluding Viewer ActionsUseIn this step, you can define a profile for excluding context menu actions from the Viewer. Thisprofile can be linked to an application and to a role.

You can set only one profile as default. If no application or role-specific profile is maintained, thedefault profile picks up the actions to be excluded from the Viewer.


Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator DefineProfile for Excluding Viewer Actions


2. On the Viewer Profile: Overview screen, choose the New Entries pushbutton andenter the following values:


Viewer Profile DMS Profile

Profile Description DMS Profile

3. Confirm by choosing Enter.4. Select the new entry in the Viewer Profile table and choose Usage in the dialog

structure.5. On the Usage: Overview screen, choose the New Entries pushbutton and enter the

following values:


Usage DMS

Role <Enter PFCG role for identification>

6. Confirm by choosing Enter.7. In the dialog structure, choose Details.8. Choose the New Entries pushbutton and enter the following values:


Action ID <Use F4 help>


5.11 Activate Service Binding to Access Web ServiceUseIn this step, you activate the service binding that you configured previously.

ProcedureTo run the report to activate service bindings, execute the following Customizing activity:



Customizing Menu Cross-Application Components DocumentManagement Visual Enterprise Generator ActivateService Binding to Access Web Services


5.12 Business Add-InsThe following Business Add-Ins (BAdIs) are available in Customizing for Cross-ApplicationComponents under Document Management Visual Enterprise Generator Business Add-Ins:

BAdI Description

BAdI: Registration Logic for Conversion ofOriginal Appl. Files in DMS(DMS_ES_DOC_REG)

You can use this BAdI to define the logic usedto register a document's info record for fileconversion.

BAdI: Batch Job for Starting Conversion ofRegistered Files(VEG_EX_BATCHJOB)

You can use this BAdI to start the conversionof registered files in batch mode.

BAdI: Enhancement for Conversion ofOriginal Appl. Files in DMS(DMS_ES_DOC_CNV)

You can use this BAdI to obtain theinformation required for proper storage of aconverted file.

BAdI: Get Files for Thumbnail and ViewerDisplay(DMS_ES_GET_FILE)

You can use this BAdI to obtain the types offiles that can be displayed as thumbnail andviewer.

For more information, see the documentation of the BAdIs in the system.