sap manufacturing execution 6

Installation GuideDocument version: 2.0.3 – 2016-04-26

SAP Manufacturing Execution 6.1

CUSTOMER

Document History

CautionBefore you start the implementation, make sure you have the latest version of this document. You can find the

latest version at the following location: service.sap.com/instguides SAP Business Suite ApplicationsSAP Manufacturing SAP Manufacturing Execution 6.1 .

The following table provides an overview of the most important document changes.

Table 1

Version Date Description

1.0 2012-11-12 First version

1.2 2013-01-22 Minor changes in the Preparation SAP ME SAP ME Database Servers section

1.3 2013-02-20 The following sections were updated:

● Preparation SAP ME SAP ME Database Servers

● Installation SAP ME Scripts

● Installation SAP ME Executing “SAPMEINT Standard Interfaces” CTC Task

1.4 2013-04-26 Minor corrections in the Installation SAP ME Executing “SAP ME NetWeaver Engine

Configuration” CTC Task section.

1.5 2013-05-22 Minor corrections in the Preparation SAP ME SAP ME Database Servers section.

1.5.1 2013-07-30 Added a caution to the Preparation SAP ME Scripts section.

1.6 2013-07-31 Updated the Installation SAP ME Scripts section.

1.7 2013-08-06 Updated the Preparation SAP ME SAP ME Database Servers and Appendix A: Installing Database Software sections.

1.8 2013-08-19 Updated the Preparation SAP ME SAP ME Client Systems section.

1.9 2013-09-27 The Appendix: Installing Database Software is replaced with SAP Notes 1917447 and

1919146 .

1.9.1 2013-10-29 Minor changes in the Installation SAP ME ERP Integration (SAPMEINT) Executing

“SAPMEINT Standard Interfaces” CTC Task .

1.9.2 2013-10-29 Minor changes in the Preparation SAP ME Scripts and Installation SAP ME

Scripts sections.

1.9.3 2013-12-20 Updated the Executing "SAP ME NetWeaver Engine Configuration” CTC Task section.

1.9.4 2014-02-13 Minor changes in the Before You Start and SAP ME Visual Test and Repair Feature (Optional) sections.

1.9.5 2014-02-27 Minor changes in the Installation SAP ME Executing “SAP ME Configuration for

Installation” CTC Task section.

2

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

SAP Manufacturing Execution 6.1Document History

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguides

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D1917447%26_NLANG%3Den%26_NVERS%3D0


Version Date Description

1.9.6 2014-03-12 Updated the Introduction Before You Start section.

1.9.7 2014-04-25 The Preparation SAP ME SAP ME Database Servers section was updated.

1.9.8 2014-06-05 Minor changes in the Preparation SAP ME SAP ME Database Servers section.


2.0 2014-12-22 Updated the Executing “SAP ME Database Setup for Installation” CTC Task section.


2.0.2 2015-04-01 Minor changes in the Executing “SAP ME Database Setup for Installation” CTC Task and Executing “SAPMEINT Standard Interfaces” CTC Task sections.

2.0.3 2016-04-26 Minor changes in the Preparation SAP ME SAP ME Database Servers and Executing “SAP ME Database Setup for Installation” CTC Task sections.

SAP Manufacturing Execution 6.1Document History

CUSTOMER© Copyright 2016 SAP SE or an SAP affiliate company.

All rights reserved. 3

Content

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.1 SAP ME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

SAP NetWeaver AS Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 SAP ME Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 SAP ME Client Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.2 SAP ME Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 SAP MII / SAPMEINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.4 Planning Safeguarded and Custom Content SAP ME Integrated System Landscapes . . . . . . . . . . . . . 163.5 Statit e-Server for SAP ME SPC Server (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.6 SAP ME BusinessObjects Reports (SAPMEBOBJ) (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.1 SAP ME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Deploying SAP ME Core and SAPMECTC Components to SAP NetWeaver AS Java . . . . . . . . . . . . 18 Executing “SAP ME NetWeaver Engine Configuration” CTC Task . . . . . . . . . . . . . . . . . . . . . . . . . 18 Executing “SAP ME Database Setup for Installation” CTC Task . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Executing “SAP ME Configuration for Installation” CTC Task . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.2 SAP ME Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.3 SAP ME ERP Integration (SAPMEINT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Deploying SAPMEINT and SAPMEINTCTC Components in SAP NetWeaver Java AS . . . . . . . . . . . 29 Executing “SAPMEINT Standard Interfaces” CTC Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Re-Executing SAPMEINTCTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Post CTC Execution Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.4 SAP ME SPC Server (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.5 SAP ME BusinessObjects Reports (SAPMEBOBJ) (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5 Post Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.1 Wily Introscope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.2 SAP ME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.3 SAP ME Visual Test and Repair Feature (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.4 SAP ME SPC Server (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6 Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426.1 SAP ME Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4


SAP Manufacturing Execution 6.1Content

1 Introduction

1.1 About this Document

This installation guide describes the steps required to install SAP Manufacturing Execution (SAP ME). It specifies the sequence of the installation activities and their dependencies.

SAP ME is a manufacturing execution system (MES) that controls, captures, shares, and stores data that determine how a product is manufactured. SAP ME provides real-time configuration data capture and global visibility across a manufacturing line, plant, or enterprise. This allows manufacturers to recognize and respond rapidly to configuration or quality changes resulting in the production of the highest quality product at the lowest cost.

The installation includes the following:

● SAP ME core

● SAP ME optional components

○ SAP ME ERP Integration (SAPMEINT)

○ SAP ME Scripts

○ SAP ME SPC Server

○ SAP ME BusinessObjects Reports (SAPMEBOBJ)

Integration

SAP ME 6.1 allows you to integrate your plant and enterprise systems and to display integrated data. For a

complete list of components, see the SAP ME Master Guide at service.sap.com/instguides SAP Business Suite Applications SAP Manufacturing SAP Manufacturing Execution 6.1 .

Constraints

This guide provides instructions for installing core SAP ME 6.1 software and its subcomponents. Instructions for installing additional required SAP software and configuration documentation can be found on SAP Service

Marketplace at service.sap.com/instguides SAP Business Suite Applications SAP Manufacturing SAP Manufacturing Execution 6.1 .

Instructions for installing other required software can be obtained from the respective software vendor.

Instructions for executing SAP ME 6.1 Oracle SQL scripts assume you use Oracle SQL*Plus Worksheet. For Oracle 10g Release 2, Oracle SQL*Plus Worksheet is installed with the Oracle 10g Client and for Oracle 11g Release 2, Oracle SQL*Plus is installed with the database. You can execute the scripts using any tools available from Oracle

including SQL*Plus. For more information, see www.oracle.com .

SAP Manufacturing Execution 6.1Introduction





http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.oracle.com

1.2 Before You Start

You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. You can find the most up-

to-date version in the SAP Service Marketplace at service.sap.com/notes .

Table 2

SAP Note Number Title Description

1409811 SAP ME System Landscape Recommendations

Recommendations and best practices for implementing an SAP ME productive system landscape

1745394 Installing SAP JVM 6.1 for SAP ME Scripts

Instructions on how to install SAP JVM 6.1 for SAP ME Scripts on a separate server from the SAP ME NetWeaver installation

1688669 API calls to SAP ME from SAP MII fail if SAP ME restarted

Anytime SAP ME goes down or is taken down and is restarted, SAP MII should also be restarted.

1695315 Release Information Note for SAP ME 6.1 Important information about SAP ME 6.1 and Service Packs

1908404 Call MII Transactions from ME Extension, Hook, or POD Plug-in

SAP MII supports writing customizations without code compilation and deployment. However, such customizations cannot be invoked directly from SAP ME and participate in SAP ME transactions.

1989071 SAP ME Language Support Displaying SAP ME in one of the supported languages

Naming Conventions

The following naming conventions are applicable:

Table 3

Variables Description

<SAPSID> SAP system ID in uppercase letters

<SAPSID>adm OS user created during SAP NetWeaver installation. For example, user me1adm is created for instance named ME1.

<DVD-DIR> Directory on which a DVD is mounted

<instance_name> Instance name under <SAPSID>

<dbprovider> SAP ME database provider

6


SAP Manufacturing Execution 6.1Introduction

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fnotes







2 Planning

To plan your SAP ME installation, do the following:

1. Review SAP Note 1409811 — SAP ME System Landscape Recommendations.

2. Plan your SAP ME system landscape.

3. Check hardware and software requirements for each system landscape component.

SAP Manufacturing Execution 6.1Planning




3 Preparation

3.1 SAP ME

3.1.1 SAP NetWeaver AS Java

Prerequisites

You have installed SAP NetWeaver 7.3 SPS07 Patch 06 or higher for SAP ME with the following usage types:

● Application Server Java

● Adobe Document Services (ADS)

For information on ADS configuration, see Configuring Adobe Document Services for Form Processing (Java)

at help.sap.com SAP NetWeaver SAP NetWeaver 7.3 SAP NetWeaver Library Function-Oriented View Adobe Document Services Configuration Guide .

3.1.2 SAP ME Database Servers

Prerequisites

● You have installed the SAP ME 6.1 database software.

SAP ME supports the following major releases of RDBMS and their patches:

○ Oracle Database 10g Release 2

○ Oracle Database 11g Release 2

○ Microsoft SQL Server 2005 SP3/X86 64 bit



For more information, see SAP Notes 1917447 — Installing Oracle Software for SAP ME Demonstration

Install and 1919146 — Installing MS SQL Software for SAP ME Demonstration Install.

You have installed client software (Microsoft SQL or Oracle) to execute SQL scripts.

CautionIf you obtain database installation media from SAP Service Marketplace, you must install the SAP ME databases using the vendor installation program rather than the SAP installation script (sapserver.xxx).

○ If you use Oracle for your SAP ME databases, you have downloaded ojdbc6.jar from

www.oracle.com/technetwork/database/enterprise-edition/jdbc-112010-090769.html .

○ If you use Microsoft SQL Server for your SAP ME databases, you have downloaded Microsoft JDBC

Driver 4.0 for SQL Server from www.microsoft.com/en-us/download/details.aspx?id=11774 . This

8


SAP Manufacturing Execution 6.1Preparation

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com



http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.oracle.com%2Ftechnetwork%2Fdatabase%2Fenterprise-edition%2Fjdbc-112010-090769.html

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D11774

is a self-extracting executable that contains the sqljdbc4.jar, install.txt, and sqljdbc_xa.dll required files.

● For SAP ME productive system landscape, you have applied all recommendations and best practices for SAP ME 6.1 databases.

Recommendations and Best Practices for SAP ME Databases

General

● For large transaction volume manufacturing systems, the SAP ME WIP and SAP ME ODS databases and database users must be created on separate dedicated physical servers prior to SAP ME installation.

● The SAP ME WIP, ODS, GODS, and INT databases must be created in accordance with SAP ME System

Landscape Recommendations (see SAP Note 1409811 ).

Oracle

NoteAll configuration settings below must be done for WIP and ODS databases as well as for INT database if SAPMEINT_* tables are located outside of WIP database.

● The db_block_size is 8K or higher. This can only be set when the instance is created. A block size of 16K is recommended for large databases.

● The GLOBAL_NAMES parameter is set to FALSE.

● Usage of the WORLD domain name must be disabled.

● For a server dedicated to a single Oracle instance, 80% of the total RAM is allocated to Oracle.

● The following settings are recommended and assume 2 GB RAM available to the database:

○ db_block_size = 16K; This cannot be modified; it is set on instance creation.

○ sga_target = 1500MB○ pga_aggregate_target = 500MB○ undo_management = AUTO○ nls_characterset = AL32UTF8○ nls_nchar_characterset = UTF8

● optimizer_mode = ALL_ROWS (this is the default setting).

● The following parameter values must be set:

○ optimizer_index_caching = 90○ optimizer_index_cost_adj = 10○ timed_statistics = TRUE

● The cost-based optimizer (CBO) in Oracle 10g and Oracle 11g requires gathering statistics. The DBMS_STATS package is recommended; the ANALYZE command does not gather all the statistics needed. The DBMS_STATS.GATHER_SYSTEM_STATS procedure tells the optimizer hardware information and the CBO creates execution plans based on the hardware information and statistics. Statistics must be gathered regularly on the SAP ME databases so they do not become stale resulting in system performance degradation.

● Oracle has a default job for statistics gathering that is based on the DBMS_STATS settings described below. This job is supposed to be used, and no other job or tool for statistics gathering is needed.





● Full statistics must be gathered for all tables and indices; no sampling

● No histograms may be created during statistics collection

● The following statistics options must be set for optimal performance. These parameters address the previous two items:

○ METHOD_OPT = 'FOR ALL COLUMNS SIZE 1'○ ESTIMATE_PERCENT = NULL○ CASCADE = TRUE

● SAP ME WIP and ODS listeners and database instances must be created manually.

● Database Users (WIP, ODS, INT)

○ Name begins with a nonnumeric character

○ The SYSTEM user must grant the following permissions to the users:

○ System privileges:

○ ADVISOR○ CREATE SESSION○ CREATE TABLE○ CREATE TRIGGER○ CREATE VIEW○ CREATE SEQUENCE○ CREATE PROCEDURE○ CREATE SYNONYM○ CREATE DATABASE LINK○ SELECT ANY DICTIONARY○ UNLIMITED TABLESPACE

○ Roles:

○ CONNECT○ RESOURCE

○ The SYS user must grant the following permission to the user:

○ Object privilege: EXECUTE ON DBMS_WORKLOAD_REPOSITORY

Microsoft SQL

● SQL Server must use the Latin1_General_CI_AS collation for WIP, ODS, GODS, and INT

For SQL Server 2008 and SQL Server 2012, on the Customize the SQL Server 2008 (2012) Database Engine Collation screen, select the Windows collation designator and sort order checkbox, enter Latin1_General as Collation designator, and select the Accent-sensitive checkbox.

NoteSAP ME database requires case-insensitive installation.

See also SAP Note 1989071 - SAP ME Language Support.

● For WIP, ODS, and INT databases the isolation level is set to Snapshot.

○ Set the Snapshot Isolation option to On by executing the following statement: alter database [<Database_name>] set ALLOW_SNAPSHOT_ISOLATION ON

10




where <Database_name> is the actual name of the database.

○ To verify the Snapshot Isolation state, execute the following query: SELECT sd.snapshot_isolation_state, sd.snapshot_isolation_state_desc FROM sys.databases AS sd WHERE sd.[name] = '<Database_name>'

○ Snapshot Isolation State Description:

○ 0: Snapshot Isolation is Off (default).

○ 1: Snapshot Isolation is On. Snapshot isolation is allowed.

○ 2: Snapshot Isolation is in transition to Off. All transactions have modification versions. You cannot start new transactions using snapshot isolation. The database remains in transition to Off until all transactions are completed.

○ 3: Snapshot Isolation is in transition to On. Transactions cannot use snapshot isolation until the state becomes 1. The database remains On until all transactions are completed.

○ Set the Read Committed Snapshot option to On by executing the following statement: alter database [<Database_name>] SET READ_COMMITTED_SNAPSHOT ON.

○ To verify the Read Committed Snapshot state, execute the following query: SELECT sd.is_read_committed_snapshot_on FROM sys.databases AS sd WHERE sd.[name] = '<Database_name>'

○ Read Omitted Snapshot Option State Description

○ 0: Read-committed snapshot is Off (default). Read operations under the read-committed level use share locks.

○ 1: Read-committed snapshot is On. Read operations under the read-committed level are based on snapshot scans and do not acquire locks.

● Auto Updating/Creating Statistics for WIP, ODS, and INT Databases

○ alter database <Database_name> set auto_create_statistics on○ alter database <Database_name> set auto_update_statistics on○ alter database <Database_name> set auto_update_statistics_async on

● Database Users

○ WIP User

○ Map the WIP user to the WIP, ODS, and INT databases.

○ Specify dbo as a default schema for each of the mapped databases.

○ The WIP database must be configured as a default database for the WIP user.

○ ODS, GODS, and INT Users

○ Map the user to its database.

○ Specify dbo as a default schema for the mapped database.

○ The database must be configured as a default database for the user.

○ Assign roles to the database users as follows:

Table 4

User/Database WIP Database ODS Database GODS Database INT Database

WIP User db_owner db_owner




NoteOnly if WIP and ODS databases are located in the same Microsoft SQL instance.

ODS User db_datareader

NoteOnly if WIP and ODS databases are located in the same Microsoft SQL instance.

db_owner

GODS User db_owner

NoteAssuming that GODS database is always located in a separate instance.

INT User db_owner

NoteOnly if you want SAPMEINT tables to be located in a separate database instead of WIP database.

NoteMake sure that a port for each instance (WIP, ODS, INT, GODS) is defined as static. For more information,

see support.microsoft.com/en-us/kb/823938 .

● If WIP and ODS databases are located in separate named instances, create the linked servers as follows:

○ ODSLINK linked server in WIP instance to ODS instance

EXEC sp_addlinkedserver @server='ODSLINK', @srvproduct='', @provider='SQLOLEDB', @datasrc='ODS_SERVER\ODS_INST,ODS_PORT'GOEXEC sp_addlinkedsrvlogin 'ODSLINK', 'false', 'wip_user', 'ods_user', 'odsadm_pass'

12



http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fkb%2F823938

GO○ WIPLINK linked server in ODS instance to WIP instance

EXEC sp_addlinkedserver @server='WIPLINK', @srvproduct='', @provider='SQLOLEDB', @datasrc='WIP_SERVER\WIP_INST,WIP_PORT'GOEXEC sp_addlinkedsrvlogin 'WIPLINK', 'false', 'ods_user', 'wip_user', 'wipadm_pass'GOWhere

*_SERVER is the server name of the named instance of MS SQL server

*_INST is the name of the named instance of MS SQL server

*_PORT is a port of the named instance of MS SQL server

*_user is a user to log on to the database

*_pass is a password of the user

○ If WIP and ODS databases are located in default instances on separate servers, create the linked servers as follows:

○ ODSLINK linked server in WIP instance to ODS instance

EXEC sp_addlinkedserver @server='ODSLINK', @srvproduct='', @provider='SQLOLEDB', @datasrc='ODS_SERVER,ODS_PORT'GOEXEC sp_addlinkedsrvlogin 'ODSLINK', 'false', 'wip_user', 'ods_user', 'odsadm_pass'GO

○ WIPLINK linked server in ODS instance to WIP instance

EXEC sp_addlinkedserver @server='WIPLINK', @srvproduct='', @provider='SQLOLEDB', @datasrc='WIP_SERVER,WIP_PORT'GOEXEC sp_addlinkedsrvlogin 'WIPLINK', 'false', 'ods_user', 'wip_user', 'wipadm_pass'GO

● If GODS database is used (always on a separate server), create GODSLINK linked server in ODS instance to GODS instance in a similar way as above.

● XA Transactions

Using SAP ME with SQL Server requires the database server to be configured to support XA transactions. Do the following:

1. Follow the comments in xa_install.sql and copy the sqljdbc_xa.dll file (extracted from the Microsoft SQL Server JDBC Driver 4.0 archive) to the folder containing sqlservr.exe for each Microsoft SQL Server instance where an SAP ME-related database (WIP/ODS/GODS/INT) is located.

2. Run xa_install.sql to register the DLL.

3. Choose Control Panel Administrative Tools Component Services Computers My ComputerDistributed Transaction Coordinator Local DTC . Right-click and choose Properties.

4. On the Local DTC Properties screen, choose the Security tab.




5. Select Enable XA Transactions and choose OK.

For Windows Server 2008, select Network DTC Access, Allow Remote Clients, Allow Inbound, Allow Outbound, Enable XA Transactions, and Mutual Authentication Required and choose OK.

NoteThe MSDTC service will be stopped and restarted.

6. Stop and restart the SQL Server instance.

7. Open SQL Server Management Studio and do the following:

○ Log on with the administrator to the MS SQL server of the WIP database.

○ Choose Instance Security Logins .

○ Right-click on the WIP user and select Properties.

○ Click User Mapping in the left panel and select a checkbox against master database in the top-right pane. Make sure that Default Schema is set to dbo for this row,

○ Check the SqlJDBCXAUser database role membership.

8. Repeat step 7 for ODS, GODS, and INT users. If separate MS SQL servers are used for WIP, ODS, GODS, and INT databases, the XA configuration must be performed on each server.

3.1.3 SAP ME Client Systems

Prerequisites

● You have Microsoft Internet Explorer installed. For information about supported versions, see the Product

Availability Matrix for SAP MFG EXECUTION 6.1 at support.sap.com/pam .

NoteAntivirus software running on the client machines can cause performance issues with Internet Explorer.

Consult your antivirus provider documentation for information about disabling scanning of scripts executed by the browser. Any changes to the antivirus configuration must be made in accordance with your company’s security policy.

● You have installed JRE 1.6.

● You have set the following:

○ Screen resolution to 1280 x 1024 (recommended)

○ Windows font size to normal (96 dpi)

○ IE text size to medium (recommended)

○ All activities to display in a new window

● You have downloaded and saved JDBC driver on your system.

14



http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fpam

3.2 SAP ME Scripts

Prerequisites

● You have installed SAP JVM 6.1 and Flash Player plug-in for Internet Explorer.

NoteBy default, SAP JVM 6.1 is delivered with the SAP NetWeaver 7.3. If you are installing SAP ME Scripts on a physical server different from your SAP NetWeaver installation, you should install SAP JVM separately. For

more information, see SAP Note 1745394 .

● You have downloaded the latest SAPCAR archive for the required operating system from SAP Service

Marketplace ( service.sap.com/swdc Download Support Packages and Patches Search for Support Packages and Patches ).

Procedure

1. From SAP Service Marketplace, download SAPMESCRIPTS<xx>.SAR.

CautionThe service pack level version of SAPMECORE<xx>.SCA and SAPMESCRIPTS<XX>.SAR must be the same.

2. Extract the SAPMESCRIPTS<xx>.SAR file to a local folder onto your system using the SAPCAR tool.

ExampleFor Windows, the extraction can be done using the following command:

SAPCAR -xvf D:\Download\SAPMESCRIPTS01_0.SAR -R D:\SARFor UNIX, the extraction can be done using the following command:

SAPCAR -xvf /home/hp3adm/SAPMESCRIPTS01_0.SAR -R home/hp3adm/SAR

3. Check if the JAVA_HOME environment variable is specified in the system. If not, define this variable to specify

the path chosen during the installation of SAP JVM (see SAP Note 1745394 ).

4. For UNIX, grant the user at least the Read and Execute permissions for the following files:

○ lmauto.sh○ updatepwd.sh

5. In the folder newly created by the SAPCAR extract, start lmauto.bat (or lmauto.sh for UNIX).

CautionIf you get the no sapjco3 in java.library.path error message after the launch of the lmauto script, please see SAP Note 1781156 .

CautionAdministrative privileges are required to run all the SAP ME scripts.

The system prompts you to enter and confirm a password for the Lifecycle Management Automation administrator user. The password must consist of 6 to 40 characters including at least one uppercase, one lowercase, and one digit.





http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fswdc



NoteThe default administrator user name is lmauser.

3.3 SAP MII / SAPMEINT

The following steps are required if you use SAP ME ERP integration (SAPMEINT). See SAP Note 1409811 for SAP ME system landscape recommendations.

Deploying SAP MII in SAP NetWeaver Java AS

NoteThis section uses Software Update Manager (SUM) to deploy SAP MII to SAP NetWeaver AS Java. For more

information about SUM, see Software Update Manager 1.0 guides at service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.3 Upgrade .

Procedure

To deploy SAP MII using SUM, proceed as follows:

1. Copy the XMII_<XX>.SCA and MII_ADMIN<XX>.SCA files to the local SAP SUM inbox.

2. Deploy XMII_<XX>.SCA and MII_ADMIN<XX>.SCA using SUM in the manual deployment mode.

For more information, see Installing SAP MII using the Software Update Manager in SAP MII 14.00 Installation

Guide at service.sap.com/instguides SAP Business Suite Applications SAP Manufacturing Integration and Intelligence SAP MII 14.00 .

3. Stop and then start the SAP NetWeaver system.

3.4 Planning Safeguarded and Custom Content SAP ME Integrated System Landscapes

The SAP ME integrated environment allows for flexible customization. However, certain customizations may have a detrimental impact on the performance of your environment. Therefore in some cases, the Safeguarded SAP ME integrated system landscape is recommended.

If you use customizations, perform the standard SAP ME Installation Guide steps with the additional requirements specified in the Safeguarded SAP ME Integrated Environment section of the SAP ME 6.1 System Landscape

Recommendations Guide (attached to SAP Note 1409811 ).

16







3.5 Statit e-Server for SAP ME SPC Server (Optional)

Prerequisites

● You have installed Windows Server 2008.

● You have installed Java JRE 1.5 or later.

● You have obtained Statit e-Server 5.4.3 software from your Statit Software vendor.

Installing Statit e-Server Software

1. Execute the Statite-Server.exe file obtained from your Statit Software vendor.

The Searching for Installed Components message appears, followed shortly by the Statit Not Found dialog box.

2. On the Statit Not Found screen, choose No.

3. Read the information on the subsequent screens, enter the required data, and choose the appropriate buttons.

NoteOn the wizard screen where results locations are defined, enter http://<serverName.dnsSuffix>:7994/ (for example, http://spcserver.abc.corp:7994/) in the Results URL field.

3.6 SAP ME BusinessObjects Reports (SAPMEBOBJ) (Optional)

Prerequisites

You have installed SAP BusinessObjects BI 4.0. For installation instructions, see SAP ME BusinessObjects BI 4.0 Reporting Guide.




4 Installation

4.1 SAP ME

4.1.1 Deploying SAP ME Core and SAPMECTC Components to SAP NetWeaver AS Java

NoteThis section uses Software Update Manager (SUM) to deploy the SAP ME Core and SAPMECTC components to SAP NetWeaver AS Java. For more information about SUM, see Software Update Manager 1.0 guides at

service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.3 Upgrade .

Procedure

To deploy SAP ME Core and SAPMECTC using Software Update Manager (SUM), proceed as follows:

1. Copy the SAPMECORE<XX>.SCA and SAPMECTC<XX>.SCA files to the local SAP SUM inbox.

2. Start all SAP NetWeaver AS Java instances using SAP Management Console (if using Windows). Wait until all processes have fully started (displayed in green).

For Unix, use the startsap script.

3. Run the Software Update Manager (SUM).

For more information, see Software Update Manager 1.0 guides at service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.3 Upgrade .

4. Deploy SAPMECORE<XX>.SCA and SAPMECTC<XX>.SCA using SUM.

4.1.2 Executing “SAP ME NetWeaver Engine Configuration” CTC Task

Prerequisites

You have deployed SAPMECTC.

Procedure

1. Log on to SAP NetWeaver Administrator using the following URL: http://<AS_Java_hostname>:<AS_Java_HTTP_port>/nwa.

18


SAP Manufacturing Execution 6.1Installation



NoteIn a clustered environment, access SAPMECTC via the primary URL for this SAP NetWeaver system.

2. Choose Configuration Scenarios Configuration Wizard .

3. On the Configuration Wizard: Overview screen, find SAP ME NetWeaver Engine Configuration and choose Start to run the CTC wizard.

RecommendationFor more information about SAPMECTC fields and values, see the SAPMECTC online help.

Table 5

SAPMECTC Page / Field Example Value / Comment

Page 1 of 3: Configuring SAP NetWeaver Service Parameters

Transaction Timeout 300

JSP Debug Support true

For information about JSP debug support, see SAP Library

for SAP NetWeaver at help.sap.com/nw731 . Under Application Help, open SAP Library and search for Enabling JSP Debug Support.

Maximum Heap Size of javac Process 300

Number of Threads for FCA 50

Page 2 of 3: Confirmation Page: Last Configuration Step Choose Next.

Page 3 of 3: Confirmation Page Finished “SAP ME NetWeaver Engine Configuration”

NoteTo run background processes on your application server, you must add the -Dvm.bkg.processor parameter manually in SAP NetWeaver AS Java Config Tool. For more information, see SAP Note 1958664

.

4.1.3 Executing “SAP ME Database Setup for Installation” CTC Task

Prerequisites

● You have deployed SAPMECTC.

● For a Unix/Oracle environment, set the timezone parameter on the application server before executing the SAP ME Database Setup for Installation CTC task using the appropriate tool below:

○ system-config-date (Red Hat)

○ yast2 timezone (SuSE)




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnw731


○ # /sbin/set_parms timezone (HP UX)

NoteX-window is required to configure it on Red Hat and SuSE. A system restart is required on HP UX for changes to take effect.

CautionIf the timezone parameter is not set when installing SAP ME on a Unix-based server using an Oracle database, the SAP ME Database Setup for Installation CTC task will fail.

Procedure

1. In SAP NetWeaver Administrator, choose Configuration Scenarios Configuration Wizard .

2. On the Configuration Wizard: Overview screen, find SAP ME Database Setup for Installation and choose Start to run the CTC wizard.

3. Enter correct values in the fields described in the following table:

RecommendationUse the Help link on the SAPMECTC wizard screens for assistance during the configuration process.

Table 6


JDBC Driver Information

JDBC Driver Path For SQL Server, load sqljdbc4.jarFor Oracle 10g or 11g, load ojdbc6.jar

Upload a New JDBC Driver Select this checkbox, if the JDBC driver already exists but you want to upload the new driver.

SAP ME WIP and ODS Database Configuration

WIP Database

Host Name of the host on which WIP database for SQL Server or Oracle is installed

Port 1433 for SQL Server

1521 for Oracle

Database SQL Server database name

NoteThis field appears only when SQL Server is used.

Instance SQL Server database instance name

20




NoteThis field appears only when SQL Server is used.

SID Oracle SID

NoteThis field appears only when Oracle is used.

User WIP user name

Password WIP user’s password

NoteDo not use the dollar sign ($) and the backslash (\) in

your password. These characters are not supported in database passwords.

ODS Database

Host Name of the host on which ODS database for SQL Server or Oracle is installed.


1521 for Oracle

User ODS user name

Password ODS user’s password





SID Oracle SID

Create Database Tables for SAP BusinessObjects Reports If selected, creates database tables that are used by SAP BusinessObjects to create reports

SAP ME INT and GODS Configuration

Is GODS Implemented If GODS database is present, select the checkbox and enter the GODS database details.

SAP ME INT Database

Host Name of the host on which SAP ME INT database for SQL Server or Oracle is installed






1521 for Oracle

User SAP ME INT user name

Password SAP ME INT user’s password





SID Oracle SID

GODS Database

Host Name of the host on which GODS database for SQL Server or Oracle is installed


1521 for Oracle

User GODS user name

Password GODS user’s password



Database SQL Server GODS database name


SID Oracle SID

Database Server Link Configuration

NoteThis page is visible only for SQL Server.

WIP and ODS Are on Different Servers Select this checkbox if WIP and ODS databases are located on different database servers.

ODS and GODS are on Different Servers Select this checkbox if ODS and GODS databases are located on different database servers.

WIP and ODS Database Server Link A linked server in the WIP database to the ODS database

22




ODS and WIP Database Server Link A linked server in the ODS database to the WIP database

ODS and GODS Database Server Link A linked server in the ODS database to the GODS database

Page 5 of 7: SAP ME User Creation

Provide a Password for "SITE_ADMIN" User

Password SITE_ADMIN’s password

Confirm Password Re-enter SITE_ADMIN’s password

Confirmation Page

Last Configuration Step You have completed all the configuration steps. Choose ‘Next’ to proceed with the current settings.

Finished “SAP ME Database Setup for Installation“

NoteFor more information about SAPMECTC fields and values, see the SAPMECTC online help.


4.1.4 Executing “SAP ME Configuration for Installation” CTC Task

Prerequisites

You have deployed SAPMECTC.

Procedure

1. In SAP NetWeaver Administrator, choose Configuration Scenarios Configuration Wizard .

2. On the Configuration Wizard: Overview screen, find SAP ME Configuration for Installation and choose Start to run the CTC wizard.

RecommendationUse the Help link on the SAPMECTC wizard screens for assistance during the configuration process.

Table 7


SAP ME Global Site Configuration

Create Global Site





Language Select a language of the initial data (.idat files) for the

global (*) site

NoteYou cannot change the language of the initial data for the global site once it is loaded. Fore more information,

see SAP Note 1989071 SAP ME Language Support.

Time zone Select a time zone for the global (*) site

Configuration Complete SAP ME configuration is completed

Choose Next.

Finished “SAP ME Configuration for Installation”.

NoteFor information about SAPMECTC fields and values, see the SAPMECTC online help.

4.2 SAP ME Scripts

SAP ME Scripts Installation

To install SAP ME Scripts, proceed as follows:

1. In Microsoft Internet Explorer on your SAP ME client system, open the Lifecycle Management Automation (LMA) tool by using the following URL: http://<hostname>:50099/lmauto, where hostname is the server where you started lmauto.bat or lmauto.sh (see Preparation SAP ME Scripts above in this guide).

The system prompts for user and password.

2. Log on with the lmauser user and the password that you defined for this user when executing lmauto.bat or lmauto.sh (see Preparation SAP ME Scripts above in this guide).

3. On the next screen, choose Process for SAP ME Scripts Installation.

4. Choose Start With Protocol to run the automation task.


Table 8

SAP ME Scripts LMA Page / Field Example Value / Comment

Process for SAP ME Scripts Installation

Page 1 of 4: Scripts Information

Scripts Installation Location Path to the directory on the client system where SAP ME scripts are to be placed.

Default: C:\SAP\SAPME (/home/SAPME/ for UNIX)

24





NoteThis directory is located on the server where you have started lmauto.bat or lmauto.sh.

CautionThe user must have the administrative rights for this directory.

Application Server Host Name Host name of the server where SAP ME application is installed

Application Server P4 (RMI) Port P4 port number of the server

Default: 50004

Application Server SID SID value

SAP JVM Path Location of SAP JVM.

For more information, see Preparation SAP ME

Scripts earlier in this guide.

Database Vendor

● SQLSERVER

● ORACLE

ORACLE

Driver File Path Location of JDBC driver

For SQL Server, specify path to sqljdbc4.jarFor ORACLE 10g and 11g, specify path to ojdbc6.jarC:\jarfile\ojdbc6.jar (/home/jarfile/ojdbc6.jar for UNIX)

NoteThe JDBC driver is located on the server where you have started lmauto.bat or lmauto.sh.

Page 2 of 4: WIP Database Information

Host Name The name of the host on which WIP database for SQL Server or Oracle is installed

Port Number Port number of the database

1433 for SQL Server

1521 for Oracle

Username WIP user name

Password Password of WIP user







SID Oracle SID

NoteThe field appears only for Oracle.

Database Name WIP database name


NoteThe field appears only for SQL Server.

Page 3 of 4: ODS Database Information

Is GODS Implemented If GODS database is present, select the checkbox and enter the GODS database details.

Host Name The name of the host on which ODS database for SQL Server or Oracle is installed


1433 for SQL Server

1521 for Oracle

Username Name of ODS user

Password Password of ODS user



SID Oracle SID


Database Name ODS database name



26




Page 4 of 4: GODS Database Information

Host Name Name of the host on which GODS database for SQL Server or Oracle is installed


Example:

1433 for SQL Server

1521 for Oracle

Username Name of GODS user

Password Password of GODS user



SID Oracle SID


Database Name GODS database name



6. Choose Next to complete the task.

The scrips are ready for execution.

SAP ME Scripts Patch Installation

To apply a patch to SAP ME Scripts, proceed as follows:

1. From SAP Service Marketplace, download the latest SAPMESCRIPTS<xx>.SAR2. Extract the SAPMESCRIPTS<xx>.SAR file to a local folder onto your system using the SAPCAR tool (see

Preparation SAP ME Scripts earlier in this guide).

3. In Microsoft Internet Explorer on your SAP ME client system, open the Lifecycle Management Automation tool by using the following URL: http://<hostname>:50099/lmauto, where hostname is the server where you started lmauto.bat or lmauto.sh (see Preparation SAP ME Scripts above in this guide).


4. Log on with the lmauser user and the password that you defined for this user when executing lmauto.bat or lmauto.sh (see Preparation SAP ME Scripts above in this guide).

5. On the next screen, select Process for SAP ME Scripts Patch Installation.






Table 9

SAP ME Scripts Patch Installation Page / Field Example Value / Comment

Process for SAP ME Scripts Patch Installation

Page 1 of 1: SAP ME Scripts Path

SAP ME Scripts Installed Path Path to the directory on the system where SAP ME scripts are located.



SAP ME Custom Scripts Installation

To install custom SAP ME scripts created by a customization development team, proceed as follows:

1. Copy the custom scripts .SCA file to a directory on the system.

2. In Microsoft Internet Explorer on your SAP ME client system, open the Lifecycle Management Automation tool by using the following URL: http://<hostname>:50099/lmauto, where hostname is the server where you started lmauto.bat or lmauto.sh (see Preparation SAP ME Scripts above in this guide).


3. Log on using the lmauser user and the password that you defined for this user when executing lmauto.bat or lmauto.sh (see Preparation SAP ME Scripts above in this guide).

4. On the next screen, select Process for SAP ME Custom Scripts Installation.



Table 10

SAP ME Custom Scripts Installation Page / Field Example Value / Comment

Process for SAP ME Custom Scripts Installation

Page 1 of 1: Information

SAP ME Scripts Installed Location Path to the directory on the system where SAP ME scripts are installed

Custom Scripts SCA Location Path to the directory on the system where the custom scripts .SCA file is located.



4.3 SAP ME ERP Integration (SAPMEINT)

Prerequisites

● You have configured SAP ERP to communicate with SAP MII / SAP ME. This involves the following:

○ Setting up ALE user

28



○ ALE configuration

○ Other customizing activities

For more information, see SAPMEINT: SAP ERP Configuration at help.sap.com SAP Business SuiteSAP Manufacturing SAP Manufacturing Execution SAP Manufacturing Execution 6.1 SAP ME ERP Integration (SAPMEINT) SAPMEINT Configuration .

● You have reviewed the following SAP Notes:

Table 11

SAP Note Number Title

1793291 FAQ about the improved integration of ERP with an SAP ME

NoteSee the Notes to be Implemented column in the attached Release_Combinations_ERP-ME.pdf.

1555198 Activating functions for SAP ME integration

1573547 User authorization roles for SAP ME integration

1595628 Planned order distribution: Conversion of data fields

1572373 Enhancement of IDOC Segment PM-Order Header (E1ORHDR)

1568468 BAPI_ALM_ORDER_GET_DETAIL does not return any service data

1577479 BAPI_ALM_ORDER_GET_DETAIL: No object list for EAM order

1688669 API calls to SAP ME from SAP MII fail if SAP ME restarted

1727437 SAPMEINT PAPI Interface Custom Action for SAP MII

1732789 SAP ME PAPI example

1678736 Special character support for Configuration Wizard

4.3.1 Deploying SAPMEINT and SAPMEINTCTC Components in SAP NetWeaver Java AS

NoteSAPMEINT must be deployed on the SAP NetWeaver instance where SAP ME and SAP MII are deployed and running. In the case of a clustered environment, make sure SAPMEINT is propagated to all additional instances. Also, make sure that SAP MII is deployed and running in SAP NetWeaver by checking the status of SAP MII application (xapps~xmii~ear) using the URL http://<AS Java host name>:<HTTP port>/nwa and navigating to Operations Systems Start & Stop Java Applications .
















NoteThis section uses Software Update Manager (SUM) to deploy SAPMEINT to SAP NetWeaver AS Java. For more

information about SUM, see Software Update Manager 1.0 guides at service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.3 EHP1 Upgrade .

Procedure

1. Copy SAPMEINT<XX>.SCA and SAPMEINTCT<XX>.SCA files from the local directory that holds the SAP ME installation files to the local SAP SUM inbox.

2. Start all SAP NetWeaver AS Java instances using SAP Management Console (if using Windows). Wait until all processes have fully started (displayed in green).

For UNIX, use the startsap script.

3. Run the Software Update Manager (SUM).

For more information, see Software Update Manager 1.0 guides at service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.3 Upgrade .

NoteThe SAP_XMII_Administrator role must be assigned to the administrative AS Java user to log on to SUM and deploy SAPMEINT<XX>.SCA.

4. Deploy SAPMEINT<XX>.SCA and SAPMEINTCT<XX>.SCA using SUM in the manual deployment mode.

NoteYou can safely ignore a warning that may appear during the SAPMEINT<XX>.SCA deployment.


4.3.2 Executing “SAPMEINT Standard Interfaces” CTC Task

The SAPMEINT CTC wizard (SAPMEINTCTC) configures SAPMEINT, SAP MII, and integration-related SAP ME elements for SAP ME ERP integration.

SAP ERP must be configured manually according to the SAPMEINT documentation. For more information, see

SAPMEINT: SAP ERP Configuration at help.sap.com SAP Business Suite SAP Manufacturing SAP Manufacturing Execution SAP Manufacturing Execution 6.1 SAP ME ERP Integration (SAPMEINT) SAPMEINT Configuration .

NoteSAPMEINTCTC must be executed in the SAP NetWeaver system where SAP MII is deployed and running and SAPMEINT is deployed (but not running yet).

In a clustered environment, access SAPMEINTCTC via the primary URL for this SAP NetWeaver system.

30






Prerequisites

You have deployed SAPMEINTCTC.

Procedure

SAPMEINT is configured through SAPMEINTCTC by accessing the URL http://<host>:<port>/nwa and proceeding as follows:

1. Choose Configuration Scenarios Configuration Wizard .

2. On the Configuration Wizard screen, find and select the SAPMEINT Standard Interfaces CTC task and choose Start or Re-Execute to begin the configuration.

3. Follow the CTC wizard to complete the SAPMEINT configuration.

RecommendationUse the Help link on the SAPMEINTCTC wizard screens for assistance during the configuration process.

NoteIf the SAPMEINTCTC wizard is interrupted for any reason, see the Re-Executing SAPMEINTCTC section below in this document.

Table 12

SAPMEINTCTC Page / Field Example Value / Comment

Page 1 of 8: Supported SAP ME Site / ERP Plant

SAP ME Site / ERP Plant The name of an existing SAP ERP plant to be integrated with SAP ME

2010

SAP ME SITE_ADMIN Password <SITE_ADMIN's password>

NoteIf SAP ME site has been created, it is not required to enter SITE_ADMIN's password.

SAP ME Time Zone America/New_York

SAP ERP Time Zone America/New_York

SAP ERP Plant Language SAP ME will create objects transferred from SAP ERP in this language

● 1 for Chinese Simplified

● M for Chinese Traditional

● E for English

● F for French

● D for German

● I for Italian





● J for Japanese

● 3 for Korean

● L for Polish

● P for Portuguese

● R for Russian

● S for Spanish

● T for Turkish

SAP ERP Version:

● SAP ERP 6.0 with EHP 5 and Activated MES Integration

● All Other Releases of SAP ERP

SAP ERP 6.0 with EHP 5 and Activated MES IntegrationFor information about supported SAP ERP versions, see

SAP Note 1793291 and Release_Combinations_ERP-ME.pdf attached to

this SAP Note.

Page 2 of 8: SAP NetWeaver Instance for SAP MII

SAP NetWeaver Information

Protocol :

● http

● https

http

CautionTo use SSL (HTTPS) communication channel, the SAP_XMII_Developer role with the

Destination_Service_Write_Permission action must be assigned. Proceed as follows:

1. Log on to SAP NetWeaver Administration and

choose Configuration Security Identity

Management Search Criteria: Role and search for SAP_XMII_Developer.

2. Modify the SAP_XMII_Developer role.

3. Move Destination_Service_Write_Permission to Assigned Actions.

For more information, see SAP ME Security Guide.

Host miiserver

Port 50000

SSL Port 50001Note that this field appears only if the HTTPS protocol was selected.

MESYS Password <MESYS' password>

XMIIIDOC Listener: XMIIIDOC01

32





● XMIIIDOC01

● XMIIIDOC02

● [...]

● XMIIIDOC10

SAP ERP Connection Information

XMIIIDOC01 Listener

Program ID XMII_ERP3

Server erp3.sap.corp

User VERPSFI_ALE

Password <The user's password>

Client 200

System Number 62

Language EN

Page 3 of 8: SAP NetWeaver Instance for SAP ME

Host meserver

Port 50200

SSL Port 50201Note that this field appears only if the HTTPS protocol was selected.

Used for Reporting in SAP MII Selected

Page 4 of 8: SAP ME Integration to SAP ERP Quality Management Notification

Notification Type F3

Priority 2

Catalogue D

Code 1

Code Group QM

Download SAP ERP Quality Inspection Lot If you want to download the quality inspection lot data from SAP ERP to SAP ME, select this checkbox.

This field is visible only when you select the SAP ERP 6.0 with EHP 5 and Activated MES integration radio button.

Page 5 of 8: SAP MII Settings

Java Connector (JCo)





Alias XMIIIDOC01_SAP_JCO

Description XMIIIDOC01_SAP_JCO

Pool Size 25

Use Logon Group Deselected

R/3 Name <R/3 name>

Logon Group <R/3 logon group>

Page 6 of 8: SAP MII Schedulers

Message Dispatcher

Number of Messages (qty) 50

Pattern 0 * * * * * (every minute)

Message Enquequer



Queue Message Cleaner

Message Retention Period (hours) 24


IDOC Inbound Enqueuer



Page 7 of 8: Database Configuration

SAPMEINT Database Vendor

SAPMEINT Database Vendor

● Oracle

● Microsoft SQL Server

Microsoft SQL Server

SAPMEINT MSSQL Data Source

Host medbhost

Port 1433

Instance

User SAPME61WIP


34






Database SAPME61WIP

SAPMEWIP MSSQL Data Source

Host medbhost

Port 1433

Instance

User SAPME61WIP




Database SAPME61WIP

SAPMEINT ORACLE Data Source

Host medbhost

Port 1521

SID MESID

User SAPME61WIP




SAPMEWIP ORACLE Data Source

Host medbhost

Port 1521

SID MESID

User SAPME61WIP








Page 8 of 8: Confirmation Page

The Last Configuration Step

NoteFor more information about SAPMEINTCTC fields and values, see the SAPMEINTCTC online help.

4. To execute the post-configuration process, follow the instructions provided on the Configuration Complete page of the CTC wizard.

5. Restart SAP NetWeaver system.

4.3.3 Re-Executing SAPMEINTCTC

Use Re-execute on the Configuration Wizard screen in the following cases:

● Multiple SAP ME sites need to be configured for SAP ME ERP integration

When SAPMEINTCTC is executed, it configures one SAP ME site that corresponds to a plant in SAP ERP. If you wish to configure multiple SAP ME sites for integration with multiple SAP ERP plants, execute SAPMEINTCTC for each additional SAP ME site (plant). For example, if you have two additional SAP ME sites (plants), execute SAPMEINTCTC two additional times.

If you need to configure additional SAP ME sites, and the original SAP ME site is being used in production, do the following:

1. Stop or disable all SAP MII Schedulers.

2. Execute SAPMEINTCTC for the required sites.

3. Restart the SAP MII application.

4. Restart or enable the SAP MII Schedulers.

NoteTo make minor corrections or modifications in the current configurations manually, see Configuration of

SAPMEINT Interfaces at help.sap.com SAP Business Suite SAP Manufacturing SAP Manufacturing Execution SAP Manufacturing Execution 6.1 SAP ME ERP Integration (SAPMEINT)SAPMEINT Configuration .

● CTC task was interrupted

If the SAPMEINTCTC wizard was interrupted for any reason, resolve the root cause issue and re-execute the SAPMEINTCTC wizard.

In Configuration Tasks view, choose Show Category All Configuration Tasks , select appropriate SAPMEINT task, and choose Re-execute.

36




RecommendationDo not use the Resume or Takeover Session buttons to continue with SAPMEINTCTC configuration. If SAPMEINTCTC is in the Currently Executing status, choose Show Category Running Configuration Tasks , select appropriate task and choose Cancel Process.

4.3.4 Post CTC Execution Procedures

Updating the SAP MII Message Listener

1. Log on to SAP MII with the MESYS user using the following URL: http://<SAP_MII_host>:<SAP_MII_port>/XMII.

2. In the SAP ERP ME Integration menu, choose MII Configuration Message Listeners .

3. On the SAP MII: Message Listeners screen, select the XMIIIDOC<xx> that has been recently configured with the CTC wizard.

4. If the SAP Server and SAP Client fields the Configuration tab page are blank, choose Update.

5. On the Details tab page, verify the connection status.

If the status of the SAP MII message listener XMIIIDOC<xx> is Not Connected, check if the SAP ERP system is accessible and correct credentials are defined in SAP NetWeaver XMIIIDOC<xx> resource adapter properties. If you cannot access the SAP ERP system, resolve connection issues and then update the message listener in SAP MII.

RecommendationIf you notice any incorrect configurations in SAP NetWeaver XMIIIDOC<xx> resource adapter properties, re-execute the SAPMEINTCTC wizard with correct values.

Adding the READ_WSIL Role for SAPMEINT Configuration Diagnostic Tool

This role is required to perform validations in SAPMEINT Configuration Diagnostic Tool.

1. Log on to SAP NetWeaver Administrator using the following URL: http://<AS_Java_hostname>:<AS_Java_HTTP_port>/nwa.

2. Choose Configuration Security Identity Management Search Criteria: Role and choose Create Role.

3. On the General Information tab page, enter READ_WSIL in the Unique Name field.

4. On the Assigned Actions tab page, search for WSILSecurityRole in the Available Actions list, and add it to the Assigned Actions of the READ_WSIL role.

The Service/Application for this action is tc~esi~esp~wsil.

5. On the Assigned Users tab page, search for MESYS in the Available Users list, and add it to the Assigned Users of the READ_WSIL role.

6. Save your entries.




4.4 SAP ME SPC Server (Optional)

Prerequisites

You have installed Statit e-Server software on Windows Server 2008.

Procedure

1. Copy the DATA_UNITS/SPC folder under the local directory that holds the SAP ME installation files to the Windows Server where Statit e-Server software is installed.

2. Execute the SPC_61.exe setup file.

3. Read the information on the subsequent screens, enter the required data, and choose the appropriate buttons.

4. After you complete the installation of SAP ME SPC Server, copy the StatitRMIServer.jar and StatitServerCom.dll files from the DATA_UNITS/SPC folder to the SAP ME SPC Server installation directory to overwrite the existing files.

5. Start the SPC Server by choosing Start Programs SAP SAPMfg SPC Server Start SPC Server .

4.5 SAP ME BusinessObjects Reports (SAPMEBOBJ) (Optional)

Prerequisites

You have installed SAP BusinessObjects BI 4.0.

Procedure

See SAP ME BusinessObjects BI 4.0 Reporting Guide.

38



5 Post Installation

5.1 Wily Introscope

If you are installing SAP ME in a productive environment, you must install Wily Introscope for end-to-end root cause analysis prior to SAP ME go-live.

For more information, see SAP Service Marketplace at service.sap.com/diagnostics .

5.2 SAP ME

Procedure

1. In the Internet Explorer, navigate to the SAP NetWeaver User Management logon screen using the following URL: http://<SAP_ME_host>:<SAP_ME_port>/manufacturing.

NoteYou need to know the host name and port number for a running server

2. Enter the correct logon ID and password. For a new installation, enter the following:

○ SITE_ADMIN in the Login field

○ The initial password defined in SAP NetWeaver User Management Engine (UME) for the SITE_ADMIN user.

NoteUME will ask to change the initial password on the first logon.

3. Choose Log On.

The SAP Manufacturing Execution initial screen appears.

4. Choose Operation Maintenance from the Activity Manager tree under Maintenance Product Configuration by default.

On the Operation Maintenance screen, do the following:

1. Choose the Browse icon to the Operation field and select the predefined PMR operation.

2. Choose Retrieve and verify that the record is loaded, for example, Preliminary Materials Review is displayed in the Description field.

5. Choose Routing Maintenance from the Activity Manager tree under Maintenance Product Configurationby default.

The Routing Maintenance application is downloaded through Java Web Start (choose Start if prompted with a security warning).

On the Routing Maintenance screen, do the following:

SAP Manufacturing Execution 6.1Post Installation



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fdiagnostics

1. Choose the Browse icon next to the Routing field and select the predefined PMR routing.

2. Choose Retrieve.

3. On the Routing tab page, verify that the routing images appear.

6. If you want to use archiving, enable Archiving on the Background Processing Execution screen.

We recommend that you use Windows Task Scheduler or Unix cron for operational data store (ODS) extracts.

5.3 SAP ME Visual Test and Repair Feature (Optional)

This section is required only if you are using the SAP ME Visual Test and Repair feature.

NoteVisual Test and Repair (VTR) supports the viewing of 3D models in the Right Hemisphere (.rh) file format.

In order to view other 3D models in VTR, the models must first be converted and stored in the .rh format. This can be accomplished via the SAP Visual Enterprise Author or SAP Visual Enterprise Generator products. For

more information, see www.righthemisphere.com/products .

VTR also supports viewing ECAD models. For more information, see the Administrator Guide for SAP Visual

Enterprise Viewer 7.1 that is available on SAP Service Marketplace at service.sap.com/instguides .

Procedure

Download the latest SAP Visual Enterprise Viewer installation program from SAP Service Marketplace and store it in a network share directory.

There are several approaches to installing the Visual Test and Repair model viewer (SAP Visual Enterprise Viewer) on each client device that will be using this feature:

● Have the user of the client device install it.

● Have the implementation team or system administrator install it on each client device.

● Set up a Group Policy to install it on each device.

In the first two cases, proceed as follows:

1. From the client device, download and execute the installation program.

2. Interact with the installer as follows:

1. Choose Yes, if prompted with a security warning.

2. Close all SAP applications and choose Next.

3. Select the Visual Enterprise Viewer Complete checkbox and choose Next.

4. Specify the installation directory on the client device and choose Next.

5. Choose Close.

For using Windows Group Policy, see the Microsoft Group Policy Settings Reference document for your operating

system. Reference documents are available from www.microsoft.com/downloads (search for Group Policy Settings Reference).

40



http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.righthemisphere.com%2Fproducts


http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fdownloads

5.4 SAP ME SPC Server (Optional)

NoteThis section is only required if you are using the SAP ME SPC Server subcomponent.

The number of simultaneous clients allowed to run Statit charts is determined by the SAP ME SPC Server. To change this value, edit the statit.server.licenses setting in the system.properties file found in the SAP ME SPC Server installation directory. This value is set to 5 by default. If this is increased, the system must be tested to ensure that it performs adequately under the additional load.

The SPC installation creates a 30-day evaluation license for the Statit e-Server. Once you have received a full license, the Windows registry must be edited on the Statit server as follows:

1. Launch the registry editor on the SPC server machine by choosing Start Run and then entering regedit.

2. Navigate to the following folder:

○ HKEY_LOCAL_MACHINE\SOFTWARE\Statit Software, LLC\Statit e-Server\License for Windows Server 2008 32–bit.

○ HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Statit Software, LLC\Statit e-Server\License for Windows Server 2008 64–bit.

3. Modify the following registry keys based on the values provided with your license:

Table 13

Statit Data Name Registry Key Notes

Site Name SiteName

Site ID SiteID Your input must be in decimal mode

Password SiteCode

4. After entering the license information, reboot the machine and restart the SAP ME SPC Server.

Verify the Windows registry on the Statit server to make sure that Statit e-Server is configured correctly:

1. Launch the registry editor on the SPC server machine by choosing Start Run and then entering regedit.

2. Navigate to the following folder:

○ HKEY_LOCAL_MACHINE\SOFTWARE\Statit Software, LLC\Statit e-Server\ResultsTopURL for Windows Server 2008 32–bit.

○ HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Statit Software, LLC\Statit e-Server\ResultsTopURL for Windows Server 2008 64–bit.

3. Verify the registry key value:

ResultsTopURL=http://serverName.dnsSuffix:7994/

For information on SPC configuration, see Setting Up Statistical Process Control at help.sap.com SAP Business Suite SAP Manufacturing SAP Manufacturing Execution SAP Manufacturing Execution 6.1 Data Collection (DC) Statistical Process Control .





6 Uninstallation

6.1 SAP ME Scripts

Procedure

1. Delete the SAPME/MEScripts folder from the location that had specified during SAP ME Scrips installation.

2. Delete the folder where SAPMESCRIPTS<xx>.SAR was extracted (see Preparation SAP ME Scriptsabove in this document).

42


SAP Manufacturing Execution 6.1Uninstallation

Typographic Conventions

Table 14

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

SAP Manufacturing Execution 6.1Typographic Conventions



http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com



www.sap.com

© Copyright 2016 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.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#trademark for additional trademark information and notices.

http://www.sap.com

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

sap manufacturing execution 6

Documents