Intentionally left blank - Mettler Toledo...7.17.2Edit Lines ScreenAdding a new Line .....2828 7.37.4Editing a LineDeleting a 7.5Line Format7.5.1Adding a new Line Format to a Line

PCE Site Manager - PSM 1.14Document Version D

User

Man

ual

PCE Site Manager - PSM 1.14 - User Manual - Document Version D 9/12/2019 9:05 AM - SchemaST4 PDF engine - Layout by Victor Mahler

PCE

Site

Man

ager

- PS

M 1

.14

Inten

tiona

lly le

ft blan

k

2 / 170 PCE Site Manager - PSM 1.14 - User Manual - Document Version D

Table of Contents

Glossary 7

1 General Information 81.1 Service ....................................................................................................................... 81.2 Language ................................................................................................................... 81.3 Formatting and Meaning............................................................................................... 81.4 How to Use Screenshots ............................................................................................... 9

2 Hardware Requirements 102.1 Requirements for the PSM Database Server ..................................................................... 10

2.1.1 Hardware ..................................................................................................... 102.1.2 Software....................................................................................................... 102.1.3 DB Size Calculation....................................................................................... 10

2.2 Requirements for the PSM Server ................................................................................... 112.2.1 Hardware ..................................................................................................... 112.2.2 Software....................................................................................................... 112.2.3 Virtualization ................................................................................................ 112.2.4 Required Free Ports ....................................................................................... 11

3 Safety 133.1 Explanation of Symbols ................................................................................................ 133.2 Principles of Proper Use................................................................................................ 133.3 Qualifications of Personnel............................................................................................ 13

4 Functions Overview 144.1 Scope......................................................................................................................... 144.2 Level Definitions .......................................................................................................... 154.3 Definition of Common Used Terms ................................................................................. 16

5 The PSM Workspace and Usage 175.1 Log in / Log off ............................................................................................................ 175.2 Stopping and Restarting PSM ........................................................................................ 175.3 Dashboard.................................................................................................................. 185.4 Menu Tree Overview..................................................................................................... 19

6 Administration of Users and Groups 216.1 Password Policy.......................................................................................................... 216.2 User Management........................................................................................................ 22

6.2.1 The Edit Users Screen .................................................................................... 226.2.2 Adding a User............................................................................................... 226.2.3 Editing Users ................................................................................................ 236.2.4 Changing Username and Password ................................................................ 236.2.5 Adding a User to a Group............................................................................... 246.2.6 Adding or Withdrawing Rights to a User........................................................... 246.2.7 Exporting Registered Users to Excel ................................................................. 24

6.3 User Group Management .............................................................................................. 256.3.1 The Edit Groups Screen.................................................................................. 256.3.2 Adding a New Group ..................................................................................... 256.3.3 Editing Groups.............................................................................................. 266.3.4 Changing the Name of a Group ...................................................................... 266.3.5 Assigning User Rights to a Group.................................................................... 26

7 Line Management 287.1 Edit Lines Screen ......................................................................................................... 287.2 Adding a new Line ....................................................................................................... 287.3 Editing a Line .............................................................................................................. 297.4 Deleting a Line ............................................................................................................ 307.5 Line Format................................................................................................................. 30

7.5.1 Adding a new Line Format to a Line ................................................................ 307.5.2 Assigning a Product to a Line Format .............................................................. 31

PCE Site Manager - PSM 1.14 - User Manual - Document Version D 3 / 170

7.5.3 Deactivating (Deleting) a Line Format.............................................................. 327.6 Line Settings................................................................................................................ 34

7.6.1 Adding Line Settings ...................................................................................... 347.6.2 Editing line settings ....................................................................................... 357.6.3 Deleting Line Settings .................................................................................... 37

8 AI Management 388.1 The Edit AIs screen....................................................................................................... 388.2 Adding AI .................................................................................................................... 388.3 Editing AIs................................................................................................................... 38

8.3.1 Defining Dependencies .................................................................................. 398.3.2 Deactivating / Activating AI’s........................................................................... 40

9 Order Management - Adding, Editing and Moving Orders 439.1 The Order Management Screen ...................................................................................... 439.2 Creating a New Order ................................................................................................... 439.3 Editing an Order........................................................................................................... 44

9.3.1 Add Order Data ............................................................................................. 459.3.2 Change GTIN ................................................................................................ 469.3.3 Change Order Name, Description, and State..................................................... 469.3.4 Resending an Order if Sending Failed .............................................................. 479.3.5 Delete an Order / Delete Order Details .............................................................. 49

9.4 Duplicating Orders ....................................................................................................... 509.5 Moving an Order to Another Line.................................................................................... 519.6 Exporting Orders .......................................................................................................... 53

9.6.1 Exporting a single order ................................................................................. 539.6.2 Configuring Filters for Order Export .................................................................. 54

9.7 Importing Orders.......................................................................................................... 559.8 Order Result Hierarchy.................................................................................................. 569.9 Order Unit Search......................................................................................................... 589.10 Run Test Order............................................................................................................. 589.11 Archiving Orders .......................................................................................................... 589.12 Order Processing Under Russian Regulations .................................................................. 60

10 Product Management - Adding and Editing Products 6410.1 The Edit Products Screen .............................................................................................. 6410.2 Adding a Product ......................................................................................................... 6410.3 Editing a Product ......................................................................................................... 65

10.3.1 Deactivating a Product / Deleting Product Data................................................. 6710.3.2 Activating Products........................................................................................ 67

11 Serial Number Management 6911.1 Module Settings SN Import ............................................................................................ 6911.2 GTIN Numbers............................................................................................................. 69

11.2.1 The edit GTIN Numbers screen........................................................................ 7011.2.2 Adding GTIN ................................................................................................. 7011.2.3 Importing Serial Numbers............................................................................... 7111.2.4 Editing values of a GTIN................................................................................. 7211.2.5 The edit PPN Number screen .......................................................................... 7311.2.6 Adding PPN.................................................................................................. 7311.2.7 Editing values of a PPN ................................................................................. 7411.2.8 Create Serial Number Ranges ......................................................................... 7411.2.8.1 Create GTIN/ NTIN Serial Number Ranges................................................... 7511.2.8.2 Create SSCC Serial Number Ranges........................................................... 7511.2.8.3 Create PPN Serial Number Ranges ............................................................ 76

11.3 SSCCNumbers ............................................................................................................. 7611.3.1 The edit SSCC Numbers screen ....................................................................... 7611.3.2 Adding SSCC ................................................................................................ 7711.3.3 Requesting Serial Numbers for SSCC ............................................................... 7811.3.4 Editing values of a SSCC................................................................................ 78

11.4 Product Code Numbers................................................................................................. 7911.4.1 Adding a Product Code Number...................................................................... 79


11.4.2 Importing Serial Numbers with a Product Code Number..................................... 8011.4.3 Editing Product Code Numbers ....................................................................... 81

11.5 Automatic Serial Number Request .................................................................................. 8211.6 Import Serial Number for Product (China Coding, 01 R14 R18 and R25)........................... 8211.7 Serial Number Overview................................................................................................ 8211.8 Serial Number List Overview.......................................................................................... 83

12 System Settings 8412.1 System Information ...................................................................................................... 8512.2 General Settings........................................................................................................... 8512.3 E-Mail Notification........................................................................................................ 8812.4 Active Directory Settings................................................................................................ 8912.5 S/N Settings ................................................................................................................ 9012.6 Import Serial Numbers.................................................................................................. 9012.7 Archive Settings ........................................................................................................... 9312.8 Polling Requests.......................................................................................................... 9312.9 CTC Purge Scheduler.................................................................................................... 94

13 Settings for all Lines 9513.1 Serial Number Management .......................................................................................... 9513.2 Password and Login Settings ........................................................................................ 96

13.2.1 Active Directory Settings ................................................................................. 9713.3 Rank Descriptions........................................................................................................ 98

14 Log Entries 99

15 Appendix 10115.1 Modules ..................................................................................................................... 101

15.1.1 SecurPharm ................................................................................................. 10115.1.1.1 Purpose ................................................................................................. 10115.1.1.2 General Settings - Order Export ................................................................. 10115.1.1.3 Specific Module Settings - SecurPharm ...................................................... 10115.1.1.4 Message Codes ...................................................................................... 10415.1.1.5 Appendix................................................................................................ 10515.1.2 TraceLink ..................................................................................................... 11115.1.2.1 The TraceLink Module .............................................................................. 11115.1.2.2 Installing New Versions of the Modules ...................................................... 11115.1.2.3 Order Export Module ................................................................................ 11115.1.2.4 Serial Number Import Module ................................................................... 11815.1.2.5 Supported Regulations ............................................................................. 12015.1.3 Multitenancy................................................................................................. 12215.1.3.1 Overview................................................................................................ 12215.1.3.2 Requirements ......................................................................................... 12415.1.3.3 Module Upgrades and Customer Definitions ............................................... 12415.1.3.4 Creating a Customer Configuration ............................................................ 12415.1.3.5 Re-Creating Customer Definitions After an Upgrade with Changes in Module

Settings.................................................................................................. 12615.1.3.6 Rework Hierarchy Import .......................................................................... 12615.1.3.7 Importing Serial Numbers......................................................................... 12915.1.3.8 Exporting Orders ..................................................................................... 13015.1.4 Generic XML Order and Product Import ............................................................ 13415.1.4.1 Generic XML Order Import......................................................................... 13415.1.4.2 Generic XML Product Import ..................................................................... 13915.1.4.3 Specifying Date Formats........................................................................... 14215.1.4.4 Appendix................................................................................................ 14215.1.5 Arvato MAH .................................................................................................. 14515.1.5.1 Overview................................................................................................ 14515.1.5.2 General Settings ...................................................................................... 14515.1.5.3 Specific Module Settings........................................................................... 14515.1.6 Arvato CMO .................................................................................................. 14715.1.6.1 Overview................................................................................................ 14715.1.6.2 Installation ............................................................................................. 147


15.1.6.3 General Settings ...................................................................................... 14815.1.6.4 Specific Module Settings........................................................................... 14815.1.7 The MDLP Connector ..................................................................................... 15215.1.7.1 Overview................................................................................................ 15215.1.7.2 Requirements ......................................................................................... 15215.1.7.3 Configuration .......................................................................................... 15215.1.7.4 Messages and Trouble-Shooting ............................................................... 15415.1.8 Order Export Dispatcher Module...................................................................... 15515.1.9 Module Trigger via Scheduler.......................................................................... 15615.1.10 AIs with special behavior during export ............................................................ 156

15.2 User Rights Table......................................................................................................... 15715.3 The PSM Watchdog...................................................................................................... 15915.4 Troubleshooting Guide.................................................................................................. 159

Glossary 167


GlossaryAI

GS1 Application Identifier

Bundle

A bundle is a packaging unit at the aggregationprocess. It consists of several items. It is usuallyaggregated to a case or directly to a pallet.

Case

A case is a packaging unit at the aggregation process.It consists of several items or bundles. It is usuallyaggregated to a pallet.

EPC

An Electronic Product Code (EPC) is a universalidentifier that gives a unique identity to a specificphysical object.

ERP

Enterprise Resource Planning; planning the use ofresources within an enterprise with the aid of software(e.g., SAP)

ERP-System

Enterprise Resource Planning System (typically ordertransaction)

GS1

Global Standards One. GS1 is dedicated to the designand implementation of global standards and solutionsto improve the efficiency and visibility of supply anddemand chains globally and across sectors. The GS1system of standards is the most widely used supplychain standards system in the world.

GTIN

Global Trade Item Number

Item

An item is the smallest unit at the aggregation process.This can be a carton or a blister. It is usuallyaggregated to a bundle or directly to a shipping case.

Pallet

A pallet is a packaging unit at the aggregationprocess. It consists of several cases.

PCE

Pharmacontrol Electronic GmbH

PLM

PCE Line Manager

PSM

PCE Site Manager

Rank

At each aggregation rank, unambiguous assignment ofunits to parent-child aggregation levels is done

SOAP

Simple Object Access Protocol is a protocol specifi-cation for exchanging structured information in theimplementation of web services in computer networks.

SSCC

Serial Shipping Container Code maintained by GS1

Unit

A unit is the result of an aggregation level. The termunit is used for an item, a bundle, a shipping case ora pallet.


1 General Information

1.1 ServiceIf you wish to contact the Service Department, please have as much information on hand as possible:• Machine type• Serial number• Line name• METTLER TOLEDO PCE order number and date• Software version• Precise wording of the displayed error message or detailed fault description• Your contact detailsThe Service Department will send you a technical questionnaire to analyze your technical request.Completing this questionnaire will help us to solve your technical issue in an efficient way.

Country E-Mail Address PhoneAustria [email protected] +43 1 6041990

France [email protected] +33 825 00 15 15

Germany [email protected] +49 5121 933 160

Korea [email protected] +82 2 3498 3566

Switzerland [email protected] +41 44 944 47 47

USA, Mexico [email protected] +1 630-446-7716

Rest of the World [email protected] +49 6251 8545-555

1.2 LanguageThis English document is the original document.

1.3 Formatting and MeaningThe formats used in this manual have determined meanings. If they are used they denote the following:

Format MeaningPC Menu Paths, Buttons at the screen surface, fixed tab

names, names of screens and dialogs

'apostrophes' Names of fields, checkboxes, modes, parameters

<angle brackets> wildcard for tab names of devices (individual namescan be assigned)

Bold UI texts


1.4 How to Use ScreenshotsBelow each screen, you see the path how to get there1. Additional actions that are to perform at this screenare described below the screen2. Wildcard buttons3 and actions at the path are placed in brackets. See thefollowing example:

1 Management > Line Management > Edit Lines > edit Lines (select line)3

2 After you made the changes press Save.

Screens (a)All full screens accessed from the main navigation bar.

Windows (b)All pop-up screens accessed by clicking or double clicking an entry/button. After performing an action at aframe the frame has to be closed by clicking the “x” buttons at the upper right corner of the window.

Frames (c)The screens and windows are divided in frames that can be opened by clicking the “+” buttons or closed byclicking the “-“ buttons.


2 Hardware Requirements

2.1 Requirements for the PSM Database Server

2.1.1 Hardware• Processor: Intel® Xeon® 5630 series or better• Minimum RAM: 8 GB, better 16 GB• Hard drive space: 1 TB

2.1.2 SoftwareRequired RDBMS:• Microsoft® SQL Server™ 2014, Standard Edition, SP3 OR Oracle 11g or later with SQL Server Authenti-

cation and Database Admin Account (Notice: The password of this account should not expire).Requirement not for Oracle Database

• SQL Server Agent is required OR Oracle SQL Developer• Collation of the MSSQL server and database have to be the same. The following collations are allowed:

– Latin1_Gerneral_CS_AS– Latin1_Gerneral_BIN2

NOTICEChanging Collation in Existing InstallationsUsing a case sensitive collation, as mentioned above, has always been the preferredsetting but some MSSQL DB installations deviated. If you are currently running a globaldatabase with a case-insensitive setting and are upgrading your system, it should first beanalyzed if data that is already in the system might cause errors when switching thecollation to case sensitive. If any input, may it be from users or systems, relies on notbeing matched case sensitive, the workflow could be interrupted. In summary, changingthe collation in existing systems should be a case by case risk based decision.

2.1.3 DB Size CalculationSome tables might show significant growth, depending on your settings and workflow. The databaseadministrator should watch the database size and archive data if necessary.

ExampleThese two tables will increase during production:• The audit trail table contains all log information and will grow over time. The increase is normally

moderate, but can increase significantly when problems occur during the production.• The serial number table is the second table which will grow over time, depending on the number of

produced items. Following is a calculation of the table size for 200 million serial numbers.id BIGINTid_order BIGINTid_parent BIGINTid_user_lastchanged BIGINTdte_lastchanged DATETIMEstr_serial_number NVARCHAR(20)i64_sequence BIGINTbit_printed BITbit_verified BITbit_valid BITi16_recordchanges INTi16_boxingrank INTDataType INT is 32 bit = 4ByteDataType BIGINT = 64 bit = 8Byte


DataType date = 8ByteNVarchar(20) = (20 * 2) + 2 Bytes = 42Bytes3bits are stored as 1 ByteThis adds up to 99 Bytes per record.99 * 200000000 = 19800000000 Bytes = 18,44 GBNote that the DB performance depends on the size of the table.The list below shows tables that can grow significantly over time during production:• tbl_prodcodenumberlists• tbl_prodcodecryptolists• tbl_ordersunits• tbl_ordersunits_ext

2.2 Requirements for the PSM Server

2.2.1 Hardware• Processor: Intel/AMD x64- architecture (64-bit)• Minimum Memory: 8 GB (4GB allocated to JVM)• Recommended Memory: 16 GB (8GB allocated to JVM)• Minimum Disk Space: 2 GB free• Recommended Disc Space: 8GB freeSee https://javaee.github.io/glassfish/doc/4.0/release-notes.pdf for more details.

2.2.2 Software• Operating System: Any operating system that is supported by Java 8.• Database access for Glassfish Server (default port 1433 for MS SQL and 1521 for Oracle)• Microsoft Internet Explorer 10 or later OR latest Mozilla Firefox OR latest Google Chrome Browser

If you use Microsoft Internet Explorer, deactivate the Compatibility View.• Network access between all Line Manager (PLM) and PSM (on port 80)• An SMTP Mail Server for e-mail notification (credentials, host, port) (only if e-mail notification is active)

PSM Version 1.7.x or later• Java EE 7 (included in Glassfish Installation)• Glassfish Application Server 4.1: https://download.oracle.com/glassfish/4.1/release/index.html

Do not install version 4.1.X.• Java Software Development Kit (JDK) 8.0 – 64-bit version

2.2.3 VirtualizationSystem virtualization is a technology that enables multiple operating system (OS) instances to executeindependently on shared hardware. Functionally, software deployed to an OS hosted in a virtualizedenvironment is generally unaware that the underlying platform has been virtualized. The PCE Site Managercan very well run on a virtualized machine.

2.2.4 Required Free PortsYou must have seven unused ports available. The installation program automatically detects ports that arein use and suggests currently unused ports for the default settings. The initial default port assignments arelisted in the following table. If these default port numbers are in use, the installation program assigns arandomly selected port number from the dynamic port range. The selected port number might not be thenext available port number.

Table: Default Port Assignments for Enterprise Server v3 Port Number Usage:

Port Assignment3700 IIOP


https://javaee.github.io/glassfish/doc/4.0/release-notes.pdf

https://glassfish.java.net/download.html

Port Assignment3820 IIOP/SSL

3920 IIOP/SSL with mutual authentication

4848 Administration Console

8080 HTTP

8081 HTTPS

8686 Pure JMX clients


3 Safety

3.1 Explanation of SymbolsThe notes contain recommended instructions for workflow and data handling to avoid data loss or otherproblems.

NOTICE<short description>This symbol indicates instructions and Information which help avoiding data loss or otherissues.

• This symbol indicates useful workflow recommendations.

3.2 Principles of Proper UseFor correct and safe application of the PCE software observe the following instructions.• It is necessary to read the complete operations instructions before starting up the PCE components in

order to avoid false application of the systems.• For your own safety, please observe the safety instructions in the operating manual. Please read the

instructions carefully even if you are already used to the application and operation of PC components.• These operating instructions do not replace installation and service by trained personnel!• The sottware must only be used in a technically flawless condition, as intended and in accordance with

this operating manual, and only by safety-conscious persons aware of the risks involved! In particular,any malfunctions affecting safety must be remedied immediately.

• Always keep the operating manual close at hand in the location where the system is in use.• In addition to the operating manual, observe all generally applicable legal and other mandatory

provisions regarding accident prevention and environmental protection and instruct others to do so aswell.

• Amend the operating manual by adding instructions, including supervisory and reporting duties, toallow for specific operational aspects, e.g. regarding the organization of work, processes, and assignedpersonnel.

• It is mandatory that all personnel assigned to perform tasks involving the system have read theoperating manual, above all the safety information chapter, prior to starting their work.

• Regularly check that personnel members are working in accordance with the operating manual in asafety-conscious manner and are demonstrating risk awareness in doing so.

• Adhere to the deadlines for recurring inspections if these are specified in the operating manual.• These operating instructions are to be treated as strictly confidential. The information given herein shall

not be copied, misused or made available to third parties without PCE’s prior written consent.• PCE is continuously enhancing all components. Modifications of the scope of delivery in form, technique

and configuration are subject to change. We appreciate your understanding that no claims can be madefrom information and illustrations of this operation manual.

3.3 Qualifications of PersonnelFor the purpose of these operating manual, a “qualified person” is one who is familiar with the operation ofthe software and system and the hazards involved.• Work at/using the system must only be performed by authorized personnel• Only assign trained or instructed personnel to such tasks. Clearly define personnel responsibilities for

operating, setup, maintenance and repairs• Make sure that only assigned personnel uses the system• Only allow personnel that is currently being trained or instructed or is undergoing general vocational

training to use the machine under the supervision of a person with experience


4 Functions Overview

4.1 ScopeThe PCE Site Manager (PSM) is the management component of the PCE Software Suite of PCE. A productionplant comprises typically a number of lines that are equipped with track & trace equipment. Each line ismanaged by a line controller (PCE Line Manager). The PCE Site Manager (PSM) is the centralizedmanagement software for track & trace at a production site with the following key functionalities.• Order Management: Add / edit Orders• Product Management: Add / edit Products• Serial number Management• User Management: Add / edit Users and User groups• Report generation for states, qualification etc.• Connection to ERP systems to exchange serial numbers and order / product data

Production line track and trace

The order, the product, and the line format can be created and edited and data is stored to the centraldatabase (e.g. LOT, GTIN). The data is then retrieved and processed by the PLM. Dynamic data (serialnumbers) are sent after request during production. The supervisor is able to manage all lines with minimumeffort; the provided settings are stored in the central database.Further features of the PSM are standard web services for 3rd party vendors and direct client implementationof order/product and serial number import and export. PSM allows you to manage all PCE Line Managersfrom a single application. You can add / edit orders, products, manage formats and serial numbers,generate reports, and track the audit trail. The scope for the PCE Line Manager is to execute orders on aline, the PSM on the other hand is for management purposes and the interaction between other enterprisesoftware in your company.The PSM acts also as the interface between the PCE system and external resources such as ERP systems.PSM offers a set of SOAP web services you can directly use as the interface or customized extensions canbe provided to perfectly fit in the existing IT environment.The PSM is designed as a web based application that can be made accessible from PC, tablet PC, andsmartphone. It runs on an application server based on the latest Java Enterprise Technology. Therefore, itcan be accessed from any device, which is connected to the same network via web browser.


To meet custom specific requirements, the PSM is divided into the Core Module (which is described in thismanual) and modules to perform actions like serial number import, order export customer-specifically.

4.2 Level DefinitionsThis is an overview of the control levels at the aggregation/serialization process. The following figure is anexample how a visual inspection production can basically look like. The detailed structure of your system isdefined in the functional specification.

Control levels at the aggregation/serialization process


4.3 Definition of Common Used TermsCommon terms used to describe aggregation are determined below.

Aggregation Ranks

Unit and Rank

tradeUnit

Rank Explanation

Item 1 An item is the smallest unit at the aggregation process. This can be a folding box, ablister or a bottle for example. It is usually aggregated to a bundle or directly to ashipping case.

Bundle 2 A bundle consists of several items.

Case 3 A case is a carton box where either bundles or items directly are packed into.

Pallet 4 A pallet contains several cases.

Unit 1/2/3/4 A unit is the term for any aggregation level. The term unit is used for an item(Rank1), bundle (Rank2), a shipping case (Rank3), or a pallet (Rank4).


5 The PSM Workspace and Usage

5.1 Log in / Log offLog inTo login enter the username and the password at the start page.

The Login Screen

After log in you get to the dashboard (see following chapter).

EULAThe first time you access a new PSM installation through the browser, PSM will redirect you to the EULApage as long as the EULA is not accepted. Once you accepted the EULA, PSM does not redirect you to thepage anymore.

NOTICEJavaScript NeededPSM shows a warning if it is accessed by a browser that has no support for JavaScript ora browser that has JavaScript disabled. Without the script, the EULA cannot be shownand therefore can also not be accepted by you.

Log offTo log off click Logout : <User>.

Automatic logoff after a certain time of inactivity is triggered by the session timeout configured in theGlassfish settings. If an automatic logoff takes place, then the session is automatically re-directed to thelogin screen.

5.2 Stopping and Restarting PSMIf, for some reason, PSM has to be restarted, use the following procedure exclusively:1. Log onto the server that is running the PSM/Glassfish application.2. Start the Windows "services.exe" application.3. Select the PSM service (usually "PCE-PSM GlassFish Server").4. Stop the process.5. Wait until process is shut down, before you perform further steps that require a stopped PSM.6. Start the service again.


NOTICERestart from GlassFish ConsoleRestarting the PSM application from the GlassFish console may result in corruption of theinstallation.

5.3 DashboardAfter log in at the PSM, you see the Dashboard:

The Dashboard

The navigation bar at the top contains the following buttons:

Menu Item Description

Dashboard Overview of lines, log entries, schedulers, and date

Settings System Information Change Language E-Mail Notification Settings Active Directory Settings Timer Settings

Management Add, edit and activate AIs Add, edit, import, export, and move orders andproductsAdd, edit user and user groups Import and manage serial numbers and serialnumber ranges

Log Entries All log entries of all lines (Audit Trail)

Help User Manual, PDF automatically opened in thebrowserEULA, Mettler-Toledo End User License Agreement(EULA) for Software

User > log off Log off

Table: Overview at Dashboard

Frame Name Content

Date At this field you see the current date and time.

Line Overview Overview of all lines

Log Entries Last 7 Log entries of all added lines (AuditTrail)


Frame arrangement at DashboardAt the Dashboard you can arrange the frames individually. The arrangement will be saved and retained forlater logins. Simply drag a frame, move it and drop it to the wished area. Possible areas where you candrag a frame, are displayed as a gray horizontal bar.

Dashboard (arrangement)

5.4 Menu Tree OverviewThe menu tree shows the maximum possible menu structure of the system.

Main Menu Sub Menu

Dashboard

Settings System Settings System InformationGeneral SettingsEmail Notification SettingsActive Directory Settingsimport Serial Numbers

Settings for all Lines Serial Number ManagementPassword and Login SettingsRank Descriptions

Module Settings

Management AI Management AI Management

Order Management Ordersmove OrdersDuplicate OrdersOrder ImportOrder ExportOrder Result HierarchyOrder Unit Searchrun Test Order

Product Management edit Productsimport Products

Serial Number Management edit GTIN Numbersedit SSCC Numbersedit Product Code Numbersedit PPN NumbersCreate Serial Number RangesSerial Number Overviewimport Serial NumbersSerial Number File ImportSerial Number List Overview


Main Menu Sub Menu

Line Management edit Lines

User Management edit Usersedit Groups

Log Entries

Help User Manual

EULA

log off


6 Administration of Users and GroupsThe User Management settings at the PSM are equivalent to the settings at the PLM. Both systems use thesame user profiles. At the PSM, all user rights are being managed centrally. Name, password and certainrights are assigned to each user access/group respectively. The type of right/group determines access to thepossible program functions. A user management is included in order to add/edit and delete users andgroups. All functions in the software can be restricted due to user rights, assigned to a group or user. Rightscan be assigned directly to a user, or along with other rights building a group which can then be assignedto a user.

General Password SettingsSome password and login settings are set for all users. For example the password validity whichdetermines after how many months a password must be changed. You can find these general settingsunder Settings > Settings for all Lines > Password and Login Settings.

6.1 Password Policy

NOTICEPassword is Mandatory for Every UserLogging in without a password is not possible. New users cannot be created withoutassigning a password.

The password strength that has to be met is set in the system settings.

Forbidden in categories LOW, MEDIUM, and HIGH• Whitespaces• Numerical sequences

123; 654• Alphabetical sequences

abc; zyx• Username

Additional rules for category LOWThe password length must be at least 6 characters till 32 characters. Character duplication of 3 or more insuccession is forbidden e.g. ddd, eee

There are 4 character rules and at this level you have to match 2 of them:

• 1 Upper case character• 1 Lower case character• 1 Digit• 1 Special character

Additional rules for category MEDIUM (default)The password length must be at least 10 characters till 32 characters. Character duplication of 2 or more insuccession is forbidden e.g. dd, ee

There are 4 character rules and at this level you have to match 3 of them:

• 2 Upper case characters• 2 Lower case characters• 1 Digit• 1 Special character

Additional rules for category HIGHThe password length must be at least 12 characters till 32 characters. Character duplication of 2 or more insuccession is forbidden e.g. dd, ee

There are 4 character rules and at this level you have to match ALL of them:

• 3 Upper case characters• 3 Lower case characters


• 2 Digits• 2 Special characters

Category NONECategory NONE sets no requirements for password strength; a password is, however, still required. Thepassword length may be from 1 to 32 characters. The password may use any character or combination ofone or more characters other than white spaces.

6.2 User Management

6.2.1 The Edit Users ScreenBelow the edit Users Screen is shown. From this screen you can add users, change username andpassword, add users to a group, add or withdraw rights to a user, and export all registered users to anExcel file. Click Management > User Management > edit Users, the following screen appears:

Management > User Management > edit Users (edit Users)

6.2.2 Adding a UserAt a user profile you can determine which rights are assigned to each user, i.e. which functions are allowedto perform on the PSM/PLM and which not. Each user must be allocated to a profile. User profiles can beassigned, edited, and removed by users with the corresponding administration rights. See the "User RightsTable" at the PLM manual.Perform the following steps:

1 Open the edit Users screen (see chapter [The Edit Users Screen } Page 22]).

2 Click add User.ð The following screen is shown:

Management > User Management > edit Users (add User)

3 Click the input field next to 'Username' and enter a name for the new user. The username cannot belonger than 64 characters.

4 Click the input field next to 'Description' and enter the description.5 Click the input field for 'Password' and enter the password. The password is always displayed as

asterisks ****. It does not appear in plain text while entering.6 If you want the user to be member of one or more user groups, activate the options in the Groups list

accordingly.


7 Click add to save all entries. If you wish to clear the fields click reset.ð After clicking add the new user is added.• We recommend writing down the passwords and keeping them in a safe place. If passwords have been

lost or forgotten, only the "after sales service" of PCE can reestablish the access.

6.2.3 Editing UsersSelect a user to edit from the list at the frame edit User at the edit Users screen (see chapter [The EditUsers Screen } Page 22]). The following window appears:

Management > User Management > edit Users > (edit Users) > (select user)

At the window above you have the following options:• Change username and password• Add user to a group• Add or withdraw rights to a userThese actions are described in the following chapters.

6.2.4 Changing Username and PasswordTo change username and password, perform the following steps:1 Go to the screen at chapter [Editing Users } Page 23].

2 At the frame User click the field next to Username and enter a new username or change the existingone.

3 Click the field next to Description and enter the description.

4 To change the password, fill in the old password.


5 Into the fields next to new Password and repeat Password, enter the new password that follows thepassword policy. See chapter [Password Policy } Page 21].

6 Click save to save the settings.

ð After clicking save the new data is saved.

6.2.5 Adding a User to a GroupGo to the screen at chapter [Editing Users } Page 23]. At the ‘Groups’ frame drag and drop (or select andclick the add button) a group from the left list (available) to the right list (assigned). The user then belongsto all the groups at the right list (assigned).To define group affiliations you have the following options:

Table: Options for group affiliations

Add Select one or more users and click Add One or more users are added

Add All Select Add All All users are added

Remove Select one or more users and pressRemove

One or more users are removed

Remove All Select Remove All All users are removed

6.2.6 Adding or Withdrawing Rights to a UserGo to the screen at chapter [Editing Users } Page 23]. At the Rights frame drag and drop (or select andclick the add button) a right from the left list (available) to the right list (assigned). All rights at the right list(assigned) are assigned to the user.

6.2.7 Exporting Registered Users to Excel

§ Users are already created in PSM.

1 Go to the edit Users screen.

2 Click the button 'Export as Excel'.

3 Select the location where the file is stored.ð The following screenshot shows an example of a user list exported to Excel:


6.3 User Group ManagementWithin the menu edit Groups you can create new groups. For user group rights see chapter [User RightsTable } Page 157].

6.3.1 The Edit Groups ScreenBelow the edit Groups screen is shown. From this screen you can add or edit groups. Click Management >User Management > edit Groups. The following screen appears:

Management > User Management > edit Groups > (edit Groups)

6.3.2 Adding a New GroupTo add a new group perform the following steps:


1 Click add group at the EDIT GROUPS screen (see chapter [The Edit Groups Screen } Page 25]). Thefollowing window appears:

Management > User Management > Edit Groups > Add Group

2 Click the input field next to ‘Groupname’ and enter the name of the new group.3 Click the input field next to ‘Description’ and describe the group in a few words.4 Click add to save all entries. If you wish to clear the fields click reset.

ð After clicking add the new group is added.

6.3.3 Editing GroupsSelect a group to edit from the list at the frame ‘edit Groups’ at the EDIT GROUPS screen (see chapter [TheEdit Groups Screen } Page 25]). The following window appears:

Management > User Management > Edit Groups > (select group)

At this window you have the following options:• Change the name of a group• Assign user rights to a groupThese actions are described in the following chapters.

6.3.4 Changing the Name of a GroupGo to the screen at chapter [Editing Groups } Page 26]. At the frame ‘User Group’ click the field next to‘Groupname’ and enter the group name.

6.3.5 Assigning User Rights to a GroupGo to the screen at chapter [Editing Groups } Page 26]. At the frame ‘Rights’ drag and drop (or select andclick the add button) a right from the left list (available) to the right list (assigned). The right is thenassigned to the group.


To assign user rights to a group you have the following options:

Table: Options at user right assignment

Button Action ResultAdd Select one or more users and click Add One or more users are added

Add All Select Add All All users are added

Remove Select one or more users and pressRemove

One or more users are removed

Remove All Select Remove All All users are removed


7 Line ManagementTo use a line at the PSM, it has to be created. Afterwards a line format has to be assigned to each line. Youcan use an existing line format or create a new one. A line format contains the settings for all used devicesat a line. Here the fields and permitted values of each device are defined at the PLM. Optionally, you canassign a product to the line format to apply its settings to the line format. For each line you can change theline settings. The changes made at the line settings in the PSM are immediately accepted at the systemsettings in the PLM.

7.1 Edit Lines ScreenBelow the edit Lines screen is shown. From this screen you can create or delete lines and make all settingsconcerning line and line format. Go to Management > Line Management > edit Lines. The screen looksas follows:

Management > Line Management > Edit Lines

At this screen you have the following options:• Add / edit / delete lines• Add a line format to line / deactivate a line format• Assign a product to a line format• Add / edit / delete line settingsThese actions are described in the following chapters.

7.2 Adding a new LineTo add a new line perform the following steps:

1 Click add Line at the edit Lines screen (see chapter [Edit Lines Screen } Page 28]). The followingwindow appears:

Management > Line Management > Edit Lines > add line

2 Click the input field next to Line Name and enter the name of the line.

3 Click the input field next to Description and enter some description for the line.

4 Press add to add the line.

ð After clicking add the new line is added.


7.3 Editing a LineTo edit a line perform the following steps:1 Select a line to edit from the list at the frame ‘edit Lines’ at the EDIT LINES screen (see chapter [Edit

Lines Screen } Page 28]). The following window appears:

Management > Line Management > Edit Lines > edit Lines (select line)

2 At the frame ‘Line’, click next to ‘Line Name’. An input field appears, where you can change the name.3 Click next to ‘Description’. An input field appears where you can change the description.4 Press save to safe the settings.ð After clicking save the new line settings are saved.


7.4 Deleting a LineSelect a line to delete from the list at the frame ‘edit Lines’ at the EDIT LINES screen (see chapter [Addinga new Line } Page 28]). The following window appears:


To delete the line click delete.

7.5 Line FormatA line format contains the settings for all used devices at a line. In the line format the fields and permittedvalues of each device are defined. The line format has to be created either at the PLM or at the PSM and canthen be edited by both programs.In this chapter it is described how to:• Add a new line format• Assign a product to a line format• Delete a line format

7.5.1 Adding a new Line Format to a LineTo add a new line format to a line perform the following steps:


1 Select a line from the list at the frame ‘edit Lines’ at the EDIT LINES screen (see chapter [Edit LinesScreen } Page 28]). The following window appears:


2 Click add at the ‘lineformats’ frame. The following window appears:

Management > Line Management > Edit Lines > edit Lines (select line) > add (line format)

3 Enter the name for the line format and click add to save the new line format to the line

ð After clicking add the new line format is added to the line.

7.5.2 Assigning a Product to a Line FormatTo assign a product to a line format perform the following steps:


1 To use a product it has to be assigned to a line format. Select a line from the list in the frame ‘edit Lines’at the EDIT LINES screen (see chapter [Edit Lines Screen } Page 28]). The following windowappears:


2 At the screen above select the line format under ‘lineformats’. At the screenshot above the available lineformat is called <Virtual Lineformat>. The following screen appears:

Management > Line Management > Edit Lines - edit Lines > (double click line format)

3 Click next to ‘Productname’, a scroll down menue appears. Select a product.4 Press save to assign the product to the line format.

ð After clicking save the product is assigned to the lineformat.

7.5.3 Deactivating (Deleting) a Line FormatA line format cannot be deleted but deactivated. When a line is deactivated it is stored to the database andno longer available at the PSM. To deactivate a line format perform the following steps:


1 Select a line from the list in the frame ‘edit Lines’ at the EDIT LINES screen (see chapter [Edit LinesScreen } Page 28]). The following window appears:

Management > Line Management > Edit Lines > edit Lines

2 Select the line format under ‘lineformats’. At the screenshot above the available line format is called<Virtual Lineformat>. The following screen appears:

Management > Line Management > Edit Lines - edit Lines > (double click line format)

3 Click deactivate. A dialog appears, confirm with delete.

ð After clicking delete the line format is deactivated.


7.6 Line SettingsFor each line the line settings at the PSM are equivalent to the system settings at the PLM. Adding a linesetting at the PSM equals setting a checkbox to activate a setting at the system settings in the PLM. Toassign a line to the PLM, the PLM has to be switched to the line (see PLM Operating Manual). The linesettings made at the PSM are applied immediately to the PLM system settings of a line. Conversely, allsettings made at the PLM system settings will be applied immediately to the PSM line settings.

7.6.1 Adding Line SettingsTo add line settings to a line perform the following steps:1 Select a line at the EDIT LINES screen (see chapter [Edit Lines Screen } Page 28]). The following

window appears:

Management > Line Management > Edit Lines > edit Lines > (select line)


2 Click add at the frame ‘linesettings’. The following window appears:

Management > Line Management > Edit Lines > edit Lines > (select line) > add

3 Select the line setting you wish to add at the scroll down menu next to ‘Linesetting’.4 Enter the value for the line setting at the field next to ‘Value’.5 Click add to add the line setting to the line.

ð After clicking add the new line setting is added to the line.

7.6.2 Editing line settingsIn this chapter it is described how to:• Change name of a line settingTo edit the line settings perform the following steps:


1 Select a line at the EDIT LINES screen ([Edit Lines Screen } Page 28]). The following windowappears:


2 Click the pencil button at the frame ‘Linesettings’ in the column ‘edit’ of the setting you wish to edit.ð The screen looks as follows:

Management > Line Management > Edit Lines > edit Lines > (select line) > (click pencil)


3 Enter the new value at the field in the column ‘value’.

4 Click the checkmark to close the editing mode.ð After clicking the checkmark, the window closes and the value is changed.

7.6.3 Deleting Line SettingsTo remove a line setting from a line perform the following steps:1 Select a line at the EDIT LINES screen (see chapter [Edit Lines Screen } Page 28]). The following

window appears:


2 Select the line setting you wish to delete.3 Click delete to delete the line setting.

ð After clicking delete the line setting is removed from the line.


8 AI Management

8.1 The Edit AIs screenAt the EDIT AI’s screen you can edit the name and the description of the AIs, deactivate it and definedependencies between it. Defining dependencies between AIs means, when an AI is selected at the PLM, alldependent AIs are also selected and have to be used.To edit AIs go to the EDIT AI’s screen:

Management > AI Management > AI Management > Edit AI’s

8.2 Adding AIClick add AI at the EDIT AI’s screen (see chapter [The Edit AIs screen } Page 38]). The screen looks asfollows:

Management > AI Management > AI Management > Add AI

Enter the AI (code) into the input field next to ‘AI’. Enter the name for the AI into the input field next to‘Name’. Enter some description for the AI into the input field next to ‘Description’.

8.3 Editing AIs• We recommend retaining settings of predefined AIs because these are corresponding to the predefined

device formats at the PLM.To edit AIs perform the following steps:


1 Click edit AI's at the edit AI's screen (see chapter [The Edit AIs screen } Page 38]). The followingscreen appears:

Management > AI Management > AI Management > edit AI’s

2 Double-click the AI you wish to edit. The following window appears:

Management > AI Management > AI Management > edit AI’s > (double-click AI) > (AI)

8.3.1 Defining DependenciesDefining dependencies between AIs means, when an AI is selected at the PLM, all dependent AIs are alsoselected and have to be used. For example you can define the AIs BATCH/LOT (AI10) and EXPIRY (AI17) asdependent on GTIN (AI01). Then when the GTIN is selected at the PLM line format, the fields for thedependent AIs (Batch, expiry) also appear.• We recommend retaining settings of predefined AIs because these are corresponding to the predefined

device formats at the PLM.


Management > AI Management > AI Management > edit AI’s

1 Click edit AI’s at the EDIT AI’S screen (see chapter [The Edit AIs screen } Page 38]). The screenlooks as follows:

2 Double click the AI for which you wish to define dependencies. The following window appears:

Management > AI Management > AI Management > edit AI’s > (double-click AI) > (AI)

3 At the frame ‘Dependencies’ drag and drop (or select and click the add button) an AI from the left list(available) to the right list (dependent AI’s). The AIs at the right list (dependent AI’s) are dependent onthe AI previously opened via double click. To define dependencies you have the following options:

4 Press save to save the settings.

ð After pressing save the dependencies settings are saved.

Table: AI Dependencies

Button Action ResultAdd Select one or more AIs and click

AddOne or more AIs are added

Add All Select Add All All AIs are added

Remove Select one or more AIs and pressRemove

One or more AIs are removed

Remove All Select Remove All All AIs are removed

Some dependencies are predefined but you can edit the dependencies individually.

8.3.2 Deactivating / Activating AI’s

DeactivateWhen deactivating an AI, it is no longer available at the PLM. This feature can be useful if you do not needsome AIs for the moment and you do not want to have them at the list of AIs but want to reuse them later.


1 Click edit AI’s at the EDIT AI’S screen (see chapter [The Edit AIs screen } Page 38]). Thefollowing screen appears:

Management > AI Management > AI Management > edit AI’s > edit AI’s

2 Double click the AI you want to deactivate. The following window appears:

Management > AI Management > AI Management > edit AI’s > (double click AI) > (Dependencies)


3 Click deactivate. The following window appears:

Management > AI Management > AI Management > Edit AI’s > edit AI’s > (double click AI) > (Dependencies) >deactivate

4 Click deactivate to confirm the deactivation.

ð After clicking deactivate, the AI is deactivated.

Activate AI1 Click deactivated AI’s at the EDIT AI’S screen (see chapter [The Edit AIs screen } Page 38]).

The screen looks as follows:

Management > AI Management > AI Management > deactivated AI’s

2 At the frame 'deactivated AI’s' set a check at one or more AIs and click activate to activate it.ð After clicking activate, the AIs are activated.


9 Order Management - Adding, Editing and Moving OrdersAt the PSM you can add, edit, move, delete, export, and import orders.

NOTICERules for order namesOrders are not allowed to have names with more than 64 characters and descriptionswith more than 255 characters.Order names must be unique. Upper and lower cases in the order name are ignoredduring the validation.

9.1 The Order Management ScreenTo work with active or archived orders, go to the Order Management screen:

Management > Order Management > Orders

The darker tab is active. On the Active orders tab, you can do the following:

• Create orders• Edit ordersOn the Archived orders tab, you can search for and display the orders that have been archived to thearchive database. The ArchivedArchived tab is displayed only if you have activated archiving. Please seeArchive Settings for more information.

These actions are described in the following chapters.

9.2 Creating a New OrderClick create order at the edit Orders screen (see chapter [The Order Management Screen } Page 43]).The following screen is opening:

Management > Order Management > Orders

1 Enter the name of the order into the input field next to Order Name.

NOTICERules for order namesOrders are not allowed to have names with more than 64 characters and descriptionswith more than 255 characters.Order names must be unique. Upper and lower cases in the order name are ignoredduring the validation.


2 Enter some description for the order into the input field next to Description.

3 Click add to create the new order.

4 For multi-module support, select the module for which this order is exported (e.g. Arvato, Tracelink,etc.). This destination module is saved in AI R50.

ð After clicking add the order is created.

NOTICEAI R50 is ignoredIf only one order export module is installed, the automatic order export job ignores AI R50of the order. The one module installed will automatically be selected as the destinationmodule when creating a new order.

9.3 Editing an OrderIn the following chapters it is described how to:• Add order data: Rank, AI, AI Value• Change GTINs• Change order name, description, and state• Delete orders

1 Click edit Orders at the edit Orders screen (see chapter [The Order Management Screen } Page 43]).The screen looks as follows:

Management > Order Management > Orders > edit Orders

2 Select an order to edit.ð You can filter the orders.

3 To edit an order, select it from the list. The window edit Order Details appears:

Management > Order Management > Orders > edit Orders (select order)

ð At this window you have the following options:- Add order data: Rank, AI, AI Value - Change GTIN - Change order name, description, and state. The states SUSPENDED, RUNNING, CACHED,UNDEFINED can only be edited in PLM. The state READ_ONLY is only visible in PSM.- Delete order


NOTICESpecial behavior when assigning a line format with a productIn the PCE Line Manager (PLM), it is possible to assign a product to a line format. If youassign such a line format to an order, the import mechanism described in [Add OrderData } Page 45] applies.

These actions are described in the following chapters.

9.3.1 Add Order Data1 Select an order at the edit Orders screen. See chapter[The Order Management Screen } Page 43].

2 At the edit Order Details window select add.

ð The following window appears:

Management > Order Management > edit Orders > edit Order Details (select order) > add

3 Select rank and AI at the corresponding dropdown menus.

4 Enter a value for the AI at the Value field.

5 Click add to add the new AI.

NOTICESpecial behavior for AI R07If you add an order data with the AI R07 (product identifier) and a known product name(see [Product Management - Adding and Editing Products } Page 64]) as the value,product data is imported from this product into the order. This means: For each productdata, a non-editable order data is created with the same AI and value. This reducesmanual work as the order thus has the product-relevant data that may be needed duringproduction. Product data with AI that is already part of an order is not imported.


NOTICESpecial behavior for AI R52In PLM (PCE Line Manager) different kinds of devices with device formats can beconfigured per line. The device format for the PLC can be overwritten using the AI R52.This is done on the order level if you add an order data with AI R52, the rank of the PLCdevice, and the desired PLC format name as the value to the order. The PLC format namespecified in the order data with AI R52 is taking priority over what is defined on the lineformat level during production start of the order. A respective message will inform the userabout AI R52 overwriting the PLC format defined on the line format.

9.3.2 Change GTINAt the ‘edit Orderdetails’ window (see above) click on the pencil button next to the AI you wish to edit, atthe frame ‘Orderdata’ in the column ‘edit’. Edit the GTIN value and click the checkmark to confirm thesettings. See screen below:

Management > Order Management > Edit Orders > edit Orders (select order) > (pencil)

9.3.3 Change Order Name, Description, and StateTo edit the order name and description perform the following steps:

1 Select an order from the edit Orders list.

2 At the section Master Data click the field next to Order Name and enter a name for the order.

3 Click the field next to Description and enter a description for the order.

Edit Order State

NOTICEAvoid manual assignment of order statesManual assignment of states should only be done in exceptional cases and by authorizedand trained personnel.

The states SUSPENDED, RUNNING, CACHED, UNDEFINED can only be edited in PLM. In PSM these statesare read only. The state FINISHED cannot be set in PSM manually.The state READ_ONLY can only be edited in PSM. In PLM orders in this state are invisible.


9.3.4 Resending an Order if Sending FailedUsually, if sending of an order failed, its state “sent” is automatically set to state “sent_failed”. In this caseyou can select the corresponding setting at the order module for export (see chapter [Configuring Filters forOrder Export } Page 54]).If an order is set to state “sent” but is not found in the ERP system for any reason; it can be sent again bysetting it to state “sent_failed” and selecting the corresponding setting at the order module (see chapter[Configuring Filters for Order Export } Page 54]).Click the field next to 'State’. A scroll down menu appears. Select a state for the order from the scroll downmenu. See the following screen:

Management > Order Management > Orders > edit Orders (select order) > (Edit fields)

An order can only have one state at once. The following table lists the states and their meaning:

Table: Order states

State ExplanationCREATED Created but not assigned. Default state after the order

has been initiated.

ASSIGNED Order is assigned to line and line format. The usercan assign the order in PLM or PSM. This state isalso possible after importing orders from anothersource.

SUSPENDED Production of the order is temporarily halted. The"suspend" button in PLM was pressed manually orany critical error has been encountered.


State ExplanationFINISHED Production has been finalized. The "finish" button in

PLM was pressed manually (user needs specialright).

QA_RELEASED Optional. This state may be used as a marker e.g.for verification by third person. The verifier sets thisstate to verify the release. The state is set manuallyand can be used as a filter in exports.

SENT After an order has been exported successfully thestate is set automatically to “sent”.

SENT_FAILED If an order could not be sent e.g. due to lost ofnetwork connection, it is set to state “sent failed”.

FINISHED_TESTORDER Test order in PSM has finished processing.

SENT_TESTORDER Test order was sent to ERP system. Only meant fortesting purposes.

EXPORTING A transition state when the order has begunexporting but the operation is not completed yet.

CACHED Production in PLM is running in local cache mode.

UNDEFINED Only for PCE service staff.

Lifecycle of an Order

ERP

Created

Assigned

Running

Suspended Finished

Exporting

Sent_failed Sent

PLM / PSM

PLM

PSM

order import (PSM)

no lineformat

order import (PSM)lineformat present

rese

t (PL

M)

expo

rtor

der (

PSM

)

fail success


9.3.5 Delete an Order / Delete Order DetailsThe button delete is only visible for users with the right mayEditOrder and if the Glassfish server systemproperty MAY_DELETE_WORKORDER was added and set true. See also Service Manual "Installationrequirements", chapter "System Properties".The order must not be finished. This is to ensure consistency so that it is not possible to produce an order inPLM with a set of order data and later export the order in PSM with a different set of order data.

1 To delete an order or details of the order, select the order at the edit Orders screen from the table (seechapter [Editing an Order } Page 44]).

ð The window edit Order Details is opened.

2 At the bottom of the window edit Order Details click the button delete.

ð A confirmation window is opened.

3 To delete the order, click the button delete.

Management > Order Management > Edit Orders > edit Orders (select order)

Deleting order detailsTo delete order details, open the edit Order Details window. Activate the select checkbox at the corre-sponding row, press delete and confirm by pressing delete again.


In the example shown below, the GTIN for rank 4 will be deleted after pressing delete.

9.4 Duplicating OrdersIn the edit Orders view (see[The Order Management Screen } Page 43]), you can create new orders. It isalso possible to create a new order that is completely or partially similar to an already existent order. Tocreate duplicates of orders:

1 Open Management > Order Management > Duplicate Orders. Every user that has the "maySeeBut-tonOrderMove" right can see this menu.

Management > Order Management > Duplicate Orders

ð The Duplicate Orders view opens up.

2 Select an order you want to duplicate.ð A dialog opens up that shows general information about the order with a proposed name for the

duplicated order.


Management > Order Management > Duplicate Orders > select an order

3 To duplicate the order, click Duplicate.

ð If the original order has a line format assigned to it, the new order is created in the state ASSIGNED.Otherwise the new order is created in the state CREATED.

You can now edit the newly created order in the edit Orders view. For instructions on how to edit orders,refer to [Editing an Order } Page 44].

9.5 Moving an Order to Another LineThis action allows you to move an order from one line to another, if it is in status ASSIGNED or CREATED.An order is assigned to a line via line format. To move an order to another line you have to assign the lineformat which is assigned to the line. The order is only visible and executable on the line where the lineformat is referencing.

1 To move an order, open Management > Order Management > move Orders.

ð At the move orders screen you can select an order to move it to another line. The screen looks asfollows:

Management > Order Management > Move Orders


2 Select the order you want to move to another line. The move Order window opens up:

Management > Order Management > move Orders > select the order to move

ð The movement of the order is done via the line formats. This means: To move an order to anotherline:

3 Click the field next to Line Format and select a line format from the window that appears:

ð

Management > Order Management > move Orders > select order to move > click the line format


4 Change the line format assigned to the order and click Assign.

ð The move Order window opens up again:

Management > Order Management > move Orders > select the order to move

5 To move the order to the corresponding line, click move.

ð The order is moved to the selected line.

9.6 Exporting OrdersThe export module allows exporting orders manually for later import to an ERP system. The function is onlyavailable when a module for order export is installed. For specific information about your module seechapter [Modules } Page 101].

NOTICEAI R50 is ignoredIf only one order export module is installed, the automatic order export job ignores AI R50of the order. The one module installed will automatically be selected as the destinationmodule when creating a new order.

9.6.1 Exporting a single order

NOTICEExporting empty ordersIf the system setting Check order consistency before exporting Order is deactivated, it ispossible to manually export empty orders under Management > Order Management >Export Order for Target Customer.

To export an order, perform the following steps:

§ Under Settings > System Settings > Order Export you have selected at least one order state to beexported. See chapter [Configuring Filters for Order Export } Page 54].

1 Go to the order export screen Management > Order Management > Order Export.ð The screen looks as follows:

Management > Order Management > Order Export


2 Select the order to be exported. The order states shown here are based on the exportable states specifiedin the system settings.ð A window opens:

Management > Order Management > Order Export > select the order you want to export

3 Click Consistency Check.

ð A window opens in which PSM analyses the workorder and provides statistics. The Export button isnow activated:

Management > Order Management > Order Export > Consistency Check

4 Click Export.ð The order export is finished.

NOTICEOnly valid and verified unitsThis refers to bit_valid und bit_verified in the database.

If values are missing in the statistics, the following points could be the reason:• To show the "target value" (R06) for item level (rank1), a value for R06 has to be defined in the order

data.• The entries "empty" and "full" are not available for item level (rank1) but for higher levels (rank 2-8).• If no value for "full bundle / full case / full pallet" is shown, check if there is a value defined for 37 or

R37 in the order data for the specific rank. Note: If 37 and R37 are both used, 37 will be selected andR37 will be ignored.

9.6.2 Configuring Filters for Order Export1 Go to Settings > System Settings > Order Export .


2 In the Order Export Scheduler Settings you can define a delay for the order export. Only if the scheduleris activated, the option Only export orders that are at least n days in stat FINISHED or QA_RELEASEDis shown.

3 In the extended Settings panel, select the order states that you want to define as exportable. Orders inthese selected states appear by default on the Order Export page.

ð

Settings > System Settings > Order Export

4 If you want an order consistency check to happen before export, click the check box next to Check orderconsistency before exporting Order.If the system setting is deactivated, it is possible to manuallyexport empty orders under. See chapter [Exporting a single order } Page 53].

5 If you want to override the timestamp set in the PLM during production, click the check box next toOverride orderunit update timestamp during order export.

6 Click save.

See also2 Change Order Name, Description, and State } Page 46

9.7 Importing OrdersThe import function allows importing orders manually (previously exported from an ERP system). Thefunction is only available when a module for order import is installed.Orders including all order data can be imported from external sources like ERP systems or just XML files. Ifthe import succeeds, the order has one of the following states:• CREATED• ASSIGNED• READ_ONLYDuring order import PSM creates order data in the imported order based on AIs available in the line format.However, the AIs from the line format have a subordinate role. They are only added to the order if the orderdoes not already have an order data with the AI and rank combination that has a value. The order can beedited manually in PSM.


NOTICELength restrictions for order namesOrders are not allowed to have names with more than 64 characters and descriptionswith more than 255 characters.

Re-importing ordersAfter a re-import of an order, the order will have only the order data as specified by the latest order importrequest. No data will be merged with previous imported order data as existing data will be overwritten. Thebehavior is the same for orders that are sent from a level 4 system to the PSM. Supported states for re-imports are the same as for the initial import:• CREATED• ASSIGNED• READ_ONLY

NOTICERe-import not possible if status reset manuallyYou can only re-import orders if they were never used in a production before. Although thestate could be reset manually to CREATED, ASSIGNED or READ-ONLY in PSM, the orderwill not be re-imported.

9.8 Order Result HierarchyThis feature allows you to view all serial numbers in the state finished(3), Sent(4), sent failed(5), finished-Testorder(8), Sent_Test(9), or QA-Released(6) belonging to an order. If the order is for aggregation, youcan step through the whole hierarchy of the order, starting with the highest rank (most likely pallets).

1 Click Management > Order Management > Order Result Hierarchy. The Order Result Hierarchyscreen appears:

Management > Order Management > Order Result Hierarchy

2 To see the history of an order that has been produced, click on the order.3 Choose an order unit (pallet/ case).

Management > Order Management > Order Result Hierarchy > Choose Order Unit > Show Hierarchy


4 Click the Show Hierarchy button.

ð The statistic displays units of an order grouped by rank, fill level (full, partial, empty), aggregation(aggregated, orphan), and validity (good, decommissioned).

Background information on statistics• A unit is considered full if the number of aggregated children equals the number of expected children as

specified by the order data with AI 30 on the units rank. Consequently, if no aggregation was performedon PLM, a unit may not be full.

• A unit is considered partial if the number of aggregated children is lower than the number of expectedchildren as specified by the order data with AI 30 on the units rank or if the unit was marked incompletein PLM.

• A unit is considered empty if zero children were aggregated on it or if it was marked incomplete in PLMwith the content 0 or if in case of a serialized production it was not marked as incomplete in PLM. Bydefinition, the lowest rank is always considered empty.

• A unit is considered good if it is valid and verified by PLM. Otherwise it is displayed as decommis-sioned.

• A unit is considered as aggregated if it was aggregated to another unit. It is considered as orphan if it isnot aggregated to another unit. Consequently, the highest rank units of an order will always bedisplayed as orphans in this statistic.

NOTICEFull vs. partial in aggregated and non-aggregated productionThe term "full" is only applicable to aggregated production, whereas "partial" may alsorefer to non-aggregated production. Thus, the statistics for a non-aggregated productionnever includes full units, but may include partial units.


9.9 Order Unit Search

While searching for an order unit, there are autocomplete hints; the number of hints is equal to the numberof the configured value for this setting. In case, there are more hints available, a text is displayed in the endof all the hints. See also chapter [General Settings } Page 85].

9.10 Run Test OrderThis action allows creating and running a test order. At a test order the PSM creates serial numbers only fortest purposes. Click Management > Order Management > run Test Order.

Management > Order Management > Run Test Order

To simulate an order perform the following steps:1 Enter the quantity of serial numbers you wish to simulate.2 Enter the first rank at the field next to ‘from Rank’ and then enter the last rank at the field ‘until Rank’.

ð Serialization = from Rank1 (item) to Rank1 (item)ð Aggregation = from Rank1 (item) to Rank4 (pallet)

3 Click run Test Order and a test order will be executed.

ð This simulates a production and generates serial numbers.

9.11 Archiving OrdersAs an additional option for PSM, you can set up archiving of your production PCE database.Archiving reduces the number of orders and associated log information held in your production database,thereby reducing the size of the database and potentially improving its performance. At the same time, youretain access to your archived orders and log entries. You can display them on demand in PSM.


Archiving is based on the completion date and time of orders. Orders that are older than the daysToKeepspecification in the archiving job in the database are moved to the archive database. Other dispensabledata that is linked to the order, such as the order units that belong to the order, are also archived. Additionaldata that is needed by orders, such as line formats, is also copied to the archive database but not removedfrom the production database.

Similarly, log entries that are older than the daysToKeep specification are moved to the archive database.

ArchitectureArchiving works with the following architecture:

• A second archive database system. This database holds the orders and related information that arearchived from your PCE production database. Archived orders are removed from the productiondatabase and are held only in the archive database. Related data, such as line definitions, are copied tothe archive database, but are not deleted from the production database.See the Installation Requirements Service Guide for more information on setting up the archive database.

• An archiving job running in the production database to archive orders as they become eligible forarchiving. You specify a number of days of records to hold in the production database to determine howlarge the database is and when to archive older orders.

There is a set of database scripts that set up the job and the stored procedures it uses. The scripts alsolet you perform the initial archiving of an existing database.

• The Archive Reporting Service (ARS). The ARS is responsible for reading archived orders on requestfrom PSM, so that they can be displayed in PSM.The ARS is a separate program that runs as a Windows Service. It is usually installed on the hostsystem of PSM.

• Controls in PSM, in the System Settings. These controls activate archiving and connect the ARS toPSM, for displaying archived orders. You can also suspend archiving, if necessary, by setting atimestamp at which the archiving jobs may resume running.

• Modifications to Order Management and Log Entries to show Active and Archived orders and logentries.

InstallationIf you would like to use archiving, then please see the Installation Requirements Service Manual forinstructions for installing and setting up archiving.

Starting ArchivingThe initial archiving run must be planned, as potentially a large amount of data must be moved to thearchive database. Please see the Installation Requirements Service Manual for more information onplanning and performing the initial archiving.After the initial archiving has been done (existing databases only), a database job runs regularly to archiveorders as they become eligible for archiving. For information on setting up this job, please see the sectionon archiving scripts in the Installation Requirements Service Manual.

Archiving is active on an ongoing basis only if you maintain the Archive Settings in the System Settings:

• You must enter an Archive URL. PSM uses the URL ask the Archive Reporting Service to displayarchived information.

• You haven't temporarily stopped archiving with the Suspend archiving until field.

Please see the Archive Settings section for more information.

Using ArchivingAfter you have set up archiving, you will find Active and Archived tabs in the following places:

• Management > Order Management > Orders > edit Orders: You can display "active" orders from yourproduction database. Or you can switch to the Archived tab. Here, you can display archived orders fromthe archive database. The ARS fetches these records for you from the archive database.

• Log Entries: You can display current log entries in the Active tab. Or log entries that are older than thelast date to keep in the production database, in the Archived tab.

• Management >


9.12 Order Processing Under Russian RegulationsBeginning in 2019, pharmaceutical companies that deliver into the Russian Federation market must complywith a new set of labeling regulations. In essence, these regulations require that each product sGTIN (serialnumber and GTIN) at the lowest serialization rank (usually the item rank) is accompanied by a speciallygenerated crypto-code and key identifier.A crypto-code is a cryptographic signature that encodes the sGTIN of a product at the lowest serialized rank,together with other information. Product labeling at the lowest serialized rank must include not only thesGTIN but also the crypto-code and crypto key.This section explains the implementation changes that have been made to support order management inaccordance with the new Russian regulations. We also describe the workflow for order management underRussian regulations.

ImplementationThe table below lists the main features that have been implemented for complying with Russian Federationregulations.

Implementation Feature DescriptionDatabase schema 2.3, newwith PSM 1.14/PLM 4.19

The new database schema adds tables and relations for associatingsGTINs and crypto-codes and for managing crypto-codes.PLM versions 4.xx and newer are compatible with DB schema 2.3 andPSM 1.14, but they can not be used for serialization in compliance withRussian regulations.

"Russian" GTINs You can now mark GTINs as relevant for the Russian market. This desig-nation enables features for downloading crypto-codes and keys andassociating them with sGTINs."Russian" GTINs may be used only with products intended for the RussianFederation market. It is not possible to use the same GTIN for Russian andother markets.

Mapping table of sGTINs tocrypto-code modules

The Serial Number Import system settings have been enhanced with atable that associates a customer and a Russian-relevant GTIN to a modulefor obtaining crypto-codes and keys. This module association is inaddition to the association of a GTIN with a serial number import module.The new table makes it possible to make a separate request for crypto-codes, where this is not integrated with the request for serial numbers.

Extension of existing serialnumber import modulesAddition of new MDLP CTC(crypto-code) and TraceLinkCTC import connectors

Depending on the serial number supplier, crypto-codes may be importedwith serial numbers or may need to be imported separately.The SN import modules have been extended or released in new form asnecessary to manage the import of crypto-codes for Russian-relevantsGTINs.There is also a new crypto-code connector for independent requests ofcrypto-codes for a set of sGTINs. This connector can also be used toobtain both serial numbers and their accompanying crypto-codes. Crypto-codes (and optionally also serial numbers) are obtained from the MDLPsystem of the Center for Advanced Technology Development (CRPT) in theRussian Federation.

Importing serial numbers and crypto-codes by hand with Management >Serial Number Management > import Serial Numbers is generallysupported. For "Russian" GTINs, there are extra fields for entering thecrypto-code import module and customer configuration.Note that serial numbers for "Russian" GTINs must have a length of 13characters.


Implementation Feature DescriptionPolling requests scheduler If crypto-codes are not imported with serial numbers, then it is necessary

to submit an asynchronous request for the crypto-codes.Because of the time needed to generate crypto-codes for a set of sGTINs, itis not possible to wait in a request for the answer. Instead, the crypto-codeprovider returns a request ID, which PSM stores for polling.PSM has implemented a scheduler that manages polling using the ID ofan asynchronous request until the requested crypto-codes can beimported. When the waiting time specified for a request has elapsed, thepolling scheduler re-issues the request, multiple times if necessary, andmanages the response.

Production support Enhanced DMX coding to include the crypto-code and crypto-code key inDataMatrix codes.New dynamic application identifiers AI 91 (crypto-code key) and AI 92(crypto-code) have been added. A "Russian" item DMX specifies AI's 01,21, 91, and 92.Enhancements of certain Smart Camera, High-Resolution Camera, andprinter cores/drivers to print and read codes containing crypto-codes.

New module for reporting tothe CRPT

On order export, separate reporting to the CRPT on the crypto-codes thathave been used may be needed, if the L4 system does not itself take careof this reporting.A separate connector will be added if this requirement in fact becomesnecessary under the Russian regulations.

New order export dispatchermodule

PSM now provides a dispatcher module for exports. The module candispatch separate modules - for order export and for CRPT reporting, forexample - as necessary to perform all notifications in an order export. Themodule is implemented as a multitenancy module, so that the module candispatch for multiple customers. It is also integrated into PSM; no separateinstallation is needed.

Scheduler for purging crypto-codes

Russian Federation regulations require, as of this writing, that crypto-codes are not retained after their use.PSM provides a new scheduler for regularly checking for serial numbersthat have been used and that are not being held in local cacheprocessing. The associated crypto-codes are then deleted.Because of their transient nature, crypto-codes are not displayed in PSM orPLM. They are not, for example, displayed in an order hierarchy or in theOrder Result Hierarchy. You can display them by scanning a DataMatrixcode in the of a global hand scanner device in PLM.

PLM Direct PLM Direct has also been enhanced to support production in compliancewith the new Russian Federation regulations.

WorkflowProducing for the Russian Federation under the new regulations proceeds as follows:

Setup and Serial Number/Crypto-Code Import1. Set up the Polling Requests scheduler in the System Settings. This scheduler manages the

asynchronous requests for crypto-codes by the CTC Import Connector from MDLP at the Russian CRPT.It also manages asynchronous requests for crypto-codes by the TraceLink CTC Import Connector.Note: Not required if you are using only serial number import modules that import both serial numbersand the accompanying crypto-codes and keys. For more information, see [Import SerialNumbers } Page 90].

2. Set up the CTC Purge Scheduler in the System Settings. This scheduler deletes crypto-codes after theyhave been used. Russian Federation regulations require that crypto-codes are not kept after use. Theserial numbers used for items for the Russian Federation market are not affected.

3. Identify the item-rank GTINs that need to have crypto-codes. Mark such GTINs as Russian-relevant inSerial Number Management.Notes:


– Russian coding is supported only for GTINs at the item rank.– "Russian" GTINs may not be used for markets other than the Russian market. A "Russian" GTIN

always has a crypto-code and key associated with it.– If you declare a GTIN that already has non-Russian serial numbers to be "Russian," then the existing

serial numbers are orphaned. They are not used. By the same token, removing the Russian desig-nation from a GTIN orphans any serial numbers and crypto-codes that may already have beenimported.

4. Map each "Russian" GTIN to the appropriate serial number import module in the import SerialNumbers settings. Do this in the Prodcode Mapping table.

This setting specifies the serial number import module to use for automatic importing of serial numberswith the SN Import Schedulers.

5. Map each "Russian" GTIN to the appropriate crypto-code import module in the CTC GTIN MappingTable.

The effect of the table is to add an optional second module call to the process of importing serialnumbers for "Russian" GTINs. The crypto-code import module takes care of supplying the importedserial numbers to the Russian CRPT and requesting crypto-codes and keys for the serial numbers andGTIN. Not all serial number import modules need a separate request for crypto-codes; maintaining thistable is not needed in all cases.For any Russian GTIn, the CTC request is triggered automatically after the requested serial numbershave been imported by the automatic serial number import job. Since a separate CTC import isasynchronous, the crypto-codes are available only after the final download of the requested CTCs hasbeen triggered by the polling scheduler. The Polling Scheduler takes care of attempting to downloadcrypto-codes and keys, until all requested CTC are available.

Until the download is complete, the imported serial numbers are shown as Pending in the SerialNumber List Overview.

For more information on filling out this table, please see [Import Serial Numbers } Page 90].

6. In Serial Number Management, set the pool minimum and maximum of "Russian" GTINs so that theautomatic serial number import requests serial numbers and crypto-codes for the GTINs.

You can use the Serial Number List Overview to see the status of your imported serial numbers. Theavailable column shows the number of serial numbers ready for production.

The "Russian" sGTINs are now ready for use in production.

Production with sGTINs and Crypto-CodesPlease note the following when you produce for the Russian Federation market:1. Your order definition for production for the Russian Federation market should include not only appli-

cation identifiers 01 and 21 at the item rank.

In your order, you must also define AI's 91 (crypto-code key) with a length of 4 and 92 (crypto-code)with a length of 44 characters (or 88 characters, not yet clear at the time of this writing; PSM will beinstalled with the correct length) at the item rank (lowest serialized rank). AIs 91 and 92 are notneeded at any other rank.

Your definition of AI 21 (serial number) must set the length to 13.

2. Only aggregated orders are supported for "Russian" GTINs.3. In your order definition, the serialization algorithm at the lowest serialization rank (usually the item

rank) must be set to RUSSIA.

For items pre-printed with an sGTIN, crypto-code and key, set the serialization algorithm to PCPOOL forserial numbers that are to be validated or PCLIST for serial numbers that are to be read and stored. Forthe pre-print scenarios, the SMC (320) must be set to PRINT_INSPECTION with Read-Only andWildcard modes enabled.

4. At the lowest serialization rank, the DMX definition of the label printer and verification camera should beset to include AIs 91 and 92. The Russian Federation regulations require that the crypto-code accom-panies the sGTIN.By default, PLM defines a Russian DMX as 01-21-91-92-17-10. According to the Russian regulations,AIs 10 and 17 are optional, the others are required.If crypto-codes are not available for the sGTINs that you wish to produce, PLM displays a corre-sponding message and will not start production.


To accommodate AIs 91 and 92, items must be printed with a larger DMX than has been usual in thepast. At present, the Wolke, Domino, and REA printer drivers, Series 3 SMCs, and the HRC 2 (50 MBresolution) support the printing and reading of the larger DataMatrix codes. Please see the data sheetsof PLM and the devices for current and official information.With Wildcards off, PLM sends a reference to 21-91-92 to an SMC for code verification.

5. At ranks higher than the item rank, production is unchanged.Since Russian Federation regulations require (as of this writing) that crypto-codes are deleted as soonas they are used, crypto-codes are visible only on printed item labels. The view does not show crypto-codes. However, scanning a physical DataMatrix code with a hand scanner displays the crypto-codeand key in the view of the global hand scanner device.Crypto-codes are also not exported and are not archived.


10 Product Management - Adding and Editing ProductsA product at the PSM is a set of information about a product that can be assigned to a line format or to anorder e.g. GTIN, quantity, bundle size, case size, pallet size. The values of the product are then filled intothe fields of the line format / order. The possibility to reuse the contents of variables avoids having to re-enter it at the creation of every order. The AI values are then transferred into the fields of the order. Creating aproduct is not essential but optional. The Product Management settings at the PSM are equivalent to thesettings at the PLM. They use the same products and these can be created or edited at both systems.One attribute of every product is a mandatory field, namely the "owner". The owner is the end-customer ofthe product. In case that you are producing only for yourself, you should choose your company name. Theother case is that you act as an CMO. Then you create one owner per end-customer and assign the appro-priate owner to each product. Note that for implementing the complete workflow you will need a multi-tenancy-capable export module. See chapter [Multitenancy } Page 122].The owner name is saved as AI R51. Note that it does not make sense to add R51 to an order as it will beoverwritten by the owner saved in the product data.

10.1 The Edit Products Screen

Management > Product Management > edit Products

At this screen you have the following options:• Add a product• Edit a product• Activate products again that were deactivatedThese actions are described in the following chapters.

See also2 Product Management - Adding and Editing Products } Page 64

10.2 Adding a Product1 Open Management > Product Management > edit Products. The edit Products screen opens up.


2 Click add Product. The add Product panel opens up.

Management > Product Management > edit Products > add Product

3 In the new Product panel, enter the product name into the field Product Name.

4 Enter a description for the product into the field Description.

5 For multitenancy support, select an existing Owner Name for this product or type a new owner nameinto the field. This ensures that the exporter assigns the client/owner orders containing this productcorrectly.

6 To save the new product, click add. To delete the entries, click reset.

10.3 Editing a Product1 Open Management > Product Management > edit Products. The edit Products screen opens up.

2 Click edit Products and select a product from the list. Use the Search field to filter the products, ifneeded. The edit Product Details window opens up:

Management > Product Management > edit Products > edit Products > select a product from the list

Edit Product NameIn the panel Master Data, click next to the field Product Name and edit the name of the product.


Edit Product AI

NOTICEAI R14 only for specific ranksAI R14 (product code reference) is valid only for specific ranks, not for rank 0 (global).When adding a new ProdCode reference (R14) definition as product data, PSM will add itonly as product code if the rank is between 1 and 8.

NOTICEAI R09 and R10 may not be assigned to productsAI R09 (line format) and R10 (line) may no longer be assigned to products. Instead, youmay use R90 (Default line assignment for product) and R91 (Default line formatassignment for product) in product definitions. Please also see the Generic XML Productand Order Import Module, where the Prioritize Line Format from Product option providesmore information.

1 In the column edit of the Product Data panel, click the pencil button next to the AI you wish to edit.

2 Edit the GTIN value and click the checkmark to confirm the settings. See screen below:

Management > Product Management > edit Products > select a product from the list

Duplicating ProductsIn the edit Product Details window you have the possibility to duplicate an existing product. Products get asuffix to the name on duplication. The first duplicate of a product will have the suffix "_copy" andsubsequent duplicates of the same product will have suffixes "_copy_1", "_copy_2" and so on.

1 Click Duplicate.

2 Select the owner.3 Select the desired details for the product.

4 Click save.


See also2 The Edit Products Screen } Page 64

10.3.1 Deactivating a Product / Deleting Product Data− Open Management > Product Management > edit Products > select a product from the list. The edit

Product Details window opens up:

Management > Product Management > edit Products > select a product from the list

Deleting Product DataTo delete product data, select the checkbox next to the product data you want to delete in the panel ProductData and click delete. Confirm by clicking delete again.

Deactivating a ProductTo deactivate a product, select deactivate at the bottom of the window. Confirm by clicking deactivateagain.

See also2 The Edit Products Screen } Page 64

10.3.2 Activating ProductsAny user with the user right mayEditProducts can activate deactivated products. Activated productsappear in the edit Products panel and may be edited and used again (e.g. for assignment to a line format).To activate a product:

1 Navigate to Management > Product Management > edit Products.


2 In the deactivated Products panel, select one or more products to activate and click the activate button.

ð



11 Serial Number Management

NOTICEMenu not visible per defaultThe menu Management > Serial Number Management is visible as soon as the S/NSettings are activated under Settings > System Settings > S/N Settings. See chapter [S/N Settings } Page 90].

Which menu items are visible in the sub menu depends also on your individual configuration and themodules you have installed. If only a serial number file import module is installed, the import SerialNumbers menu item is hidden. When using the import Serial Numbers view, all serial number file importmodules are excluded from the select module list, that is used to define with which module the import willbe performed.

11.1 Module Settings SN ImportNote that your individual module can differ from the following screen. Your own module can provide moreor less functions according to your needs. The description of your individual module you find in theappended module description. A SNImport module can, for example, look as follows:

Settings > ModuleSettings > SN Import

11.2 GTIN NumbersIn this chapter it is described how to:• Add new GTIN• Request serial numbers for GTIN• Generate serial numbers for GTIN• Edit values of GTIN


11.2.1 The edit GTIN Numbers screen

Management > Serial Number Management > edit GTIN Numbers

11.2.2 Adding GTINIn order to generate or request serial numbers a GTIN (or SSCC) must be defined. The pool sizes define thethreshold of the serial number ranges. The pool buffer is used by the PLM to reserve a set of serial numbersduring production.

Management > Serialnumber Management > edit GTIN Numbers

At the GTINNumber frame you can edit the following fields (Fields with an *(asterisk) are mandatory):

Table: GTIN details

Field ExplanationGTIN* GTIN (14 digit numeric value)


Field ExplanationRussia Mark the Russia checkbox for a GTIN that will be used for production for the Russian

Federation market. Marking the checkbox indicates to PSM that crypto-codes andkeys need to be obtained for the GTIN when serial numbers are requested.You may declare a "Russian" GTIN only on the item rank. A "Russian" GTIN may notbe used for production for any market other than that of the Russian Federation.If you change a "normal" GTIN to a "Russian" GTIN, then all previously importedserial numbers become unusable.

EPC Hexadecimal The EPC Hexadecimal field provides an optional value for this GTIN. It includes thesame Information as the GTIN + the filter value specified by GS1. The serial numberpart of the Hex will be ignored.The EPC Hexadecimal is important for the import of serial numbers. If this field isempty, PSM will generate a new EPC Hexadeciaml during the import.

Rank* Corresponding rank 1-8

Pool Minimum* Threshold, when number of available serial numbers drops below, an automaticserial number import is activated via timer and the pool of serial numbers will befilled up with number of serial numbers corresponding to the Pool Buffer (requested)but not more than to the Pool Maximum.

Pool Maximum* Maximum size of buffer to which the pool is filled up.

Pool Buffer* Size of Buffer. The number of serial numbers buffered by the PLM at a request.

11.2.3 Importing Serial NumbersIn addition to importing serial numbers automatically with the import job, you can import serial numbersmanually from a serial number supplier. This feature is not available for file-based serial number importmodules.To import / generate serial numbers, perform the following steps:

1 Open Management > Serial Number Management > import Serial Numbers.

2 In field SN Type, select the type of GTIN, SSCC, or other product code for which you wish to import serialnumbers. If you select a "Russian" GTIN, then two additional fields appear: CTC Module and CTCModule Customer. These fields let you enter both a module for importing serial numbers, and anadditional module for importing the crypto-codes and keys that are needed for a "Russian" item-rankGTIN. The processing of a request for a "Russian" GTIN is the same as that described here: [ImportSerial Numbers } Page 90].

Management > Serial Number Management > import Serial Numbers

3 In the Module field, select the serial number import module to use.

4 If the module is multitenant, then enter the Customer to use.

5 Enter the number of serial numbers to import.

6 Click Import. Messages on the user interface and in Log Entries report whether the import wassuccessful or not. The number of imported serial numbers is shown in the box to the right.


7 You can verify the imported GTINs at Management > Serial Number Management > Serial NumberList Overview.

ð Details about the imported serial numbers are displayed in the Serial Number List Overview table:

Management > Serial Number Management > Serial Number List Overview

11.2.4 Editing values of a GTINPreviously created GTINs can be edited afterwards. Go to the edit GTINNumbers frame at the editGTINNumbers screen (see chapter [The edit GTIN Numbers screen } Page 70] ):

Management > Serial Number Management > edit GTIN Numbers

1 Double-click a GTIN at the edit GTINNUMBERS screen to edit the corresponding GTIN.


Management > Serial Number Management > edit GTIN Numbers > edit GTIN Numbers

2 You can edit the fields 'Russia', ‘EPC Hexadecimal’, ‘Rank’, ‘Pool Minimum’, ‘Pool Maximum’ and ‘PoolBuffer’ by clicking the fields next to it (See chapter [Adding GTIN } Page 70]).


11.2.5 The edit PPN Number screen

Management > Serial Number Management > edit PPN Numbers

See also2 The edit GTIN Numbers screen } Page 702 Adding GTIN } Page 70

11.2.6 Adding PPNIn order to generate or request serial numbers a PPN must be defined. The pool sizes define the threshold ofthe serial number ranges. The pool buffer is used by the PLM to reserve a set of serial numbers duringproduction.

Serialnumber Management > edit PPNNumber (add PPNNumber)

At the PPNNumber frame you can edit the following fields (fields with an * (asterisk) are mandatory).

PPN Details:

Field ExplanationPPN* PPN (12 digit numeric value)

Rank* Corresponding rank 1-8

Pool Minimum* Threshold, when number of available serial numbersdrops below, an automatic serial number import isactivated via timer and the pool of serial numberswill be filled up with number of serial numbers corre-sponding to the Pool Buffer (requested) but not morethan to the Pool Maximum.

Poll Maximum* Maximum size of buffer to which the pool is filled up.

Pool Buffer* Size of Buffer. The number of serial numbers bufferedby the PLM at a request.

See also2 The edit GTIN Numbers screen } Page 702 Adding GTIN } Page 70


11.2.7 Editing values of a PPNPreviously created PPNs can be edited afterwards. Go to the Edit PPNumbers frame at the edit PPNNumbersscreen.

Management > Serial Number Management > edit PPN Numbers

1 Double-click a PPN at the edit PPN Number screen to edit the corresponding PPN The following window appears:

Management > Serialnumber Management > edit PPNNumber - (edit PPNNumbers)

2 You can edit the fields 'Rank', 'Pool Minimum', 'Pool Maximum', 'Pool Buffer' and 'Prefix' by clicking thefields next to it.

11.2.8 Create Serial Number RangesIn this section you will see how you can create your own serial numbers.

PrerequisiteIn the Settings > System Settings > S/N Settings section the appropriate option is activated. See chapter[S/N Settings } Page 90].


11.2.8.1 Create GTIN/ NTIN Serial Number Ranges

Management > Serial Number Management > Create Serial Number Ranges (GTIN/NTIN)

1 Go to Management > Serial Number Management > Create Serial Number Ranges.

2 Select the tab GTIN/NTIN. All existing active and inactive serial number ranges are listed.

3 Choose the desired GTIN/NTIN for the specified rank from the dropdown list.4 Define the start value and the quantity.

5 Click the Create button to begin with the generation.

Supported NTINsSupported NTINs are:• GERMANY ("4150")

+PZN + CheckDigit• AUSTRIA ("908888")

+PZN + CheckDigit• FRANCE ("3400")

+ CIP/ACL Code + CheckDigit• SPAIN ("847000")

+ Codigo Nacional• NORDICS ("704626")

+ Nordic Drug Code from Nordic Number Office + CheckDigitFor Sweden, Finland, Denmark, Iceland, Norway

• SWITZERLAND ("7680")+ Swissmedic Code (5-digit product license number + 3 digits pack size indicator) + check digit

• POLAND_AND_SLOVAKIA ("590999")Shared prefix for Poland and Slovakia

See also2 S/N Settings } Page 90

11.2.8.2 Create SSCC Serial Number Ranges

Serial Number Management > Create Serial Number Ranges (SSCC)



2 Select the tab SSCC. All existing active and inactive serial number ranges are listed.

3 Choose the desired SSCC for the specified rank from the dropdown list.4 Define the start value and the quantity.

5 Click the Create button to begin with the generation.

11.2.8.3 Create PPN Serial Number Ranges

Serial Number Management > Create Serial Number Ranges (PPN)


2 Select the tab PPN.

3 Choose the desired PPN for the specified rank.4 Define the start value and the quantity.5 Click the create button to begin with the generation.

11.3 SSCCNumbers• This menu item is available only when a module for SSCC numbers is installed.In this chapter it is described how to:• Add new SSCC• Request serial numbers for SSCC• Edit values of SSCC

11.3.1 The edit SSCC Numbers screen

Management > Serial Number Management > edit SSCC Numbers


11.3.2 Adding SSCCIn order to generate or request serial numbers, a SSCC (or GTIN) must be defined. The pool sizes define thethreshold of the serial number ranges. The pool buffer is used by the PLM to reserve a set of serial numbersduring production.


At the SSCC Numbers dialog you can edit the following fields (Fields with a * are mandatory):

Table: SSCC details

Field ExplanationCompany Prefix* 6-12 digit numeric value

Extension ID* Used to increase the capacity of the serial reference(1 digit numeric value)

EPC Hexadecimal The EPC Hexadecimal field provides an optionalvalue for this SSCC. It includes the same Informationas the SSCC + the filter value specified by GS1. Theserial number part of the Hex will be ignored.

Rank Corresponding rank 1-8

Pool Minimum* Threshold, when number of available serial numbersdrops below, an automatic serial number import isactivated via timer and the pool of serial numberswill be filled up with number of serial numbers corre-sponding to the Pool Buffer (requested) but not morethan to the Pool Maximum.

Pool Maximum* Maximum size of buffer to which the pool is filled up.

Pool Buffer* Size of Buffer. The number of serial numbers bufferedby the PLM at a request.

Unique CombinationsNew SSCC numbers can have the same company prefix and rank of an existing record as long as they havea different extension digit.

NOTICEDatabase changes requiredIn order to guarantee the uniqueness of the combination of company prefix, SSCC, andextension digit, changes on the database are required. See scriptalter_tbl_ssccnumbers.sql


11.3.3 Requesting Serial Numbers for SSCCYou can import serial numbers from an ERP system or use generated serial numbers at the PSM. Toimport / generate serial numbers:


2 Select an SSCC number from the scroll down menu in the corresponding area (SSCC Request).ð The screen looks as follows:

Management > Serial Number Management > import Serial Numbers > select an SSCC

3 Enter the quantity of serial numbers to be requested.

4 Click Import to generate serial numbers.

11.3.4 Editing values of a SSCCTo edit existing SSCCs, go to the edit SSCC Numbers section on the edit SSCC Numbers screen (see alsochapter [The edit SSCC Numbers screen } Page 76]):


1 To edit the corresponding SSCC, double-click this SSCC in the edit SSCC Numbers list.



Management > Serial Number Management > edit SSCC Numbers (double-click SSCC)

2 You can edit the fields EPC Hexadecimal, Rank, Pool Minimum, Pool Maximum, and Pool Buffer byclicking the fields next to it (See chapter [Adding SSCC } Page 77]). Type in the new values, and clicksave.

ð The Company Prefix is only editable during creation of a new SSCC.

11.4 Product Code NumbersProduct code numbers define import scenarios for the import module with which you can import automat-ically or manually a range of serial numbers that you pre-define in the product code number.

11.4.1 Adding a Product Code NumberTo add a product code number:

1 Go to Management > Serial Number Management > edit Product Code Numbers > add ProductCode Number:

Management > Serial Number Management > edit Product Code Numbers

2 In the add Product Code Number section, define at least all mandatory fields, i.e. all fields with an *asterisk. The following table explains the meaning of the configurable product code number values:


Field ExplanationAI Defines the Application Identifier (AI) for whom to

import serial numbers.

ProductCodeRef Provides the reference to an AI. For example, if theselected AI is "01 (GTIN)", the Product Code Ref isa GTIN.

Rank Defines on which rank the imported serial numberswill be used.

Pool Minimum Defines the minimum number of available serialnumbers for this product code number. If the numberof available serial numbers drops below this value,and if an import module is installed, new serialnumbers are imported automatically by the importmodule.

Pool Maximum Defines the maximum number of available serialnumbers for this product code number.

Pool Buffer Defines the size of the buffer with which the numberof serial numbers are buffered by the PLM at arequest.

NOTICEUnique combinationsIf you add a new GTIN / SSCC as product code, the combination of required values isvalidated. A GTIN with the same value and rank like an existing GTIN cannot be added.For SSCCs, the combination of prefix, company prefix, and rank must be unique.

11.4.2 Importing Serial Numbers with a Product Code NumberThere are two ways to import serial numbers with a product code number: manually or automatically. Forboth import scenarios you need to have an import module installed.

Automatic Import of Serial Numbers with a Product Code NumberIf you have an import module installed, the import module periodically imports serial numbers according tothe values you have configured in the product code number. For details on defining values for the productcode number, refer to [Adding a Product Code Number } Page 79] .

Manual Import of Serial Numbers with a Product Code NumberTo trigger the import of serial numbers manually by triggering a specific import module once:

1 Open Management, select Serial Number Management > import Serial Numbers and select ImportProd. Codes.

ð The Import Prod. Codes pane opens up:

Management > Serial Number Management > Import Serial Numbers


2 In the Import Prod. Codes panel, select the ProductCodeRef for which you want to import serialnumbers. If the same ProdCode exists on different ranks, you can see for which rank serial numbers areimported when requesting serial numbers for this ProdCode.

3 Specify the quantity of serial numbers and the import module you want to use for the import. Multiplemodules might be available to import serial numbers.

11.4.3 Editing Product Code NumbersIt is possible to edit existing product code numbers.

1 In the edit Product Code Numbers screen, double-click a product code.

ð The Product Code Ref dialog opens up:

Management > Serial Number Management > edit Product Code Numbers

2 Edit the required values by clicking on them.

3 Once you are finished, save your changes by clicking save.

NOTICEDeleting Product Code ReferencesWhen you delete a Product Code Number reference, the deletion is aborted if that ProductCode Number or its associated GTIN, SSCC, or PPN are still referenced by other records.


11.5 Automatic Serial Number RequestWhen the count of available serial numbers drops below pool minimum an automatic serial number importis activated via timer, the pool of serial numbers will be filled up (requested) to the pool maximum. Fortimer settings see chapter [Module Trigger via Scheduler } Page 156].

11.6 Import Serial Number for Product (China Coding, 01 R14 R18 and R25)1 You can import serial numbers for assignment to a specific product and rank. The serial numbers are

then assigned to the product in the database.ð See the following screen:


2 Select the SN Type with the targeted Product Code, for example R18.

3 Choose the target module from the list labelled Module.

4 Enter the quantity of serial numbers you want to import into the input field next to Quantity.

5 Click Import to request the serial numbers.

11.7 Serial Number OverviewAt the serial number overview you see the amount of available serial numbers (‘Available’), start- (‘RangeStart’) and end (‘Range End’) number per product, GTIN or order. The last used number is shown under‘Current’.

NOTICERange start equals range endPSM allows range imports where the range's start equals the range's end - that is therange has exactly 1 serial number. The Serial Number Overview displays 1 availableserial number for these ranges.


Management > Serial Number Management > Serial Number Overview

11.8 Serial Number List OverviewThe Serial Number List Overview shows you the status of serial numbers from a list, belonging to an AI, arank or an order. In the overview:

• available indicates the number of serial numbers available for production. With respect to "Russian"GTINs, this is the number of serial numbers for which crypto-codes and keys have been imported.This number is shown in red if it is below the pool minimum.

• Cached is the number of serial numbers currently held in local cache storage.

• Pending is the number of serial numbers that have been imported for a "Russian" GTIN but for whichcrypto-codes have not yet been imported; the import request is pending and has not yet beencompleted. These serial numbers are not available for production for the Russian Federation market.

• used shows the number of serial numbers that have been used.

If a serial number module is installed, the page displays only enabled product code numbers.

Management > Serial Number Management > Serial Number List Overview


12 System SettingsUser Rights NeededYou need to have the user right "mayEditSysGlobals" to change the system settings. If you do not have thenecessary right, the settings will be grayed out.

Installed ModulesIf additional modules are installed along with the PSM core version, the settings menu will be extended byan additional ‘ModuleSettings’ menu which will show the individual settings each module provides. For thespecific ‘ModuleSettings’ please refer to the corresponding module manual. All general system settings canbe found at Settings > System Settings:

Settings > System Settings

The buttons Order Export, Order Import, Product Import, and import Serial Numbers are displayed only ifthe corresponding modules are installed.


12.1 System InformationThe system Information shows the version of the installed PSM, the connected database, the Application-Server the PSM runs on, and the installed modules, if any.

Settings > System Settings > System Information

12.2 General SettingsLanguageTo change the language of the PSM GUI:

1 Open Settings > System Settings > General Settings.

2 Click the installed language, for example English. A drop-down list box appears:

ð

Settings > System Settings > General Settings (Language)


3 Select the language you want to be displayed and click save.

ð As a result, the GUI language of the PSM changes to the selected language. A new log-in is notnecessary.

Log Settings

Settings > System Settings > General Settings (Log Setting)

Log entries are always written to the log entries table in the Log Entries menu. In the Log Setting you canconfigure whether logs with certain log levels should additionally be logged to the application log file.


Eudralex Recording of Reasons for ChangesThe Eudralex regulations governing medicinal products require that PSM is able to record the reason for anychange to the settings and parameters of the system. With the Activate reason for change loggingcheckbox, you can switch mandatory recording of changes to the configuration of PSM on or off.

Settings > System Settings > General Settings

If you mark the checkbox, then a user who changes the configuration of PSM, for example, by changing asystem setting or defining a new GTIN, must record the reason for the change in either the Reason forchange field or the reason for change dialog. Which form of change recording appears depends onusability aspects of the function in use. The user must record a reason for change that is at least fivecharacters in length. Otherwise, the configuration change will be refused.If activated, then the reason for a change is appended to the log entry that documents the change.If you change the checkbox setting, then refresh PSM in the browser to make the change effective in yoursession.The changes for which a reason is requested (if this feature is activated) are as follows:

• System Settings• Settings for all Lines• Module Settings (module-specific)

• Multi-tenancy Modules (module-specific)

• edit Products and product fields

• edit Orders and order fields

• edit Product Code Numbers• edit GTIN Numbers• edit SSCC Numbers• edit PPN Numbers• edit Users• edit Groups


• AI ManagementFor more information, see chapter 9 of https://ec.europa.eu/health/sites/health/files/files/eudralex/vol-4/annex11_01-2011_en.pdf

The right mayChangeLogReasonForChangeFlag is required for changing the setting of the checkbox.

Trigger DelayThe delay time before a data table filter is triggered is set in the field Trigger delay for table filters (ms).

Auto complete resultsTo control the number of auto complete hints when searching for an order unit, the setting Auto completeresults limit is used. The default value for this setting is "10" and can be changed to a maximum of "30"hints. If there are more hints available, a text is displayed at the end of all the hints. See also chapter [OrderUnit Search } Page 58].

12.3 E-Mail NotificationPreconditionsTo define the e-mail account, pre-settings have to be made at the Glassfish Console. See PSM InstallationGuide.Setup and editing of the recipients and the according message codes is done in the PSM.

1 Go to Settings > System Settings > Email Notification Settingsð The Email Notification Settings panel opens up:

Settings > System Settings > Email Notification Settings

2 To add an email address, click add. Enter an email address into the add Email dialog.

Settings > System Settings >Email Notification Settings > add

3 Your email address is added to the list. Click the pencil button in the edit column of the emailaddress you have just entered and enter the message codes for which you want to receive email notifi-cations. Separate the Message codes by comma, e.g. 99000, 99001, … Find the message codes inthe PSM Alarm List. For all messages codes listed in the PSM Alarm List you can configure email notifi-cations.

4 If you want to receive emails for all message codes, type "*". If you want to exclude Message Codestype "!". For example "*,!12345" means: send an email for all Message Codes except 12345.

ð When an email is sent, a log entry is be created with message code 91024 (sent) or if its not sent91025 (could not be sent).


12.4 Active Directory SettingsPreconditionsActive directory for PSM is implemented under the following paradigms:• Group membership is managed by the Active Directory server• Group rights are managed by the PSM• Mapping is done by setting up PSM groups with the same names as Active Directory groups• Password changes etc. are managed only by the Active Directory server, not by PSMIn order to manage PSM users via the Active Directory, you have to create user groups on the ActiveDirectory and assign Active Directory users to them. Then you have to create groups with exactly the samenames in PSM and assign user rights to them. When logging on PSM as an Active Directory user, the PSMwill assign memberships to all groups in PSM of which the user is a member in the Active Directory. AnyActive Directory groups not defined in PSM will be ignored. Domain names are not required, neither forgroup names nor for user IDs.

PSM SettingsThis setting allows you to activate / deactivate Active Directory usage.

1 Open Settings > System Settings > Active Directory Settings.

ð The Active Directory Settings screen opens up:

Settings > System Settings > Active Directory Settings

2 Select activate.

3 Enter the domain name.4 Optional: Enter a server name and port.

5 Optional: If you want to use a secure connection, activate the option Enable SSL (default port 636). Ifyour LDAPS service is running on the default port 636, you may leave the field Active Directory ServicePort empty; otherwise, enter the appropriate port for your service.

6 Click save.

Once you have activated the active directory successfully, the login screen looks as follows:

Login screen when logging in with AD account


12.5 S/N SettingsWith the settings in the S/N Settings section, you can activate or deactivate some features of PSM regardingserial number ranges:

1 If you activate the option activate, you enable the Management > Serial Number Management menu:

Settings > System Settings > S/N Settings/ activate

2 If you activate the other options GTIN/ NTIN Range, PPN Range, and SSCC Range, you enable therespective tabs on the Management > Serial Number Management > Create Serial Number Rangesview. See chapter [Create Serial Number Ranges } Page 74].

Management > Serial Number Management > Create Serial Number Ranges

ð You can then view these ranges at Management > Serial Number Management > Serial NumberOverview. During production, these ranges can be used to obtain serial numbers.

12.6 Import Serial NumbersIn Settings > System Settings > import Serial Numbers, you can map GTINs, SSCCs, and other productcodes to the following:• A serial number import module.• For "Russian" lowest serialization-rank GTINs, an additional crypto-code (CTC) import module.

(Please see [Order Processing Under Russian Regulations } Page 60] for more information on orderprocessing for the Russian Federation market.)


These mappings are used by the automatic serial number import job to import serial numbers or serialnumbers and CTCs for the Russian market. For manual imports, you must specify the module mappingsseparately.

Maintaining the Prodcode Mapping tableMaintaining the Prodcode Mapping table is discussed here: [Importing Serial Numbers Automat-ically } Page 129]. This mapping is used only for the automatic import of serial numbers. In manualimports, you specify the module yourself.

Maintaining the CTC GTIN Mapping TableYou need to maintain the CTC GTIN Mapping Table only for GTINs at the lowest serialization rank (usuallythe item rank) for the Russian Federation market. The table maps the combination of customer and GTIN toa module for requesting CTCs, either from a service of a serial number provider or from the MDLP system ofthe CRPT, the Russian provider of these cryptographic signatures.CTCs are always requested together with serial numbers. A serial number for a "Russian" GTIN is availablefor use only if its CTC is also available in the database.Because it takes time to generate the CTCs for a set of sGTINs, a serial number provider must either pre-request and store CTCs, or the request for CTCs must be carried out as an asynchronous module call. In thecase of an asynchronous call, you upload a set of sGTINs and request CTCs for them, you get a request IDback, and then you call back later with the request ID to import the actual CTCs.Some providers of serial numbers pre-request CTCs and let you import them with the serial numbers. Otherproviders have their own special interface for requesting CTCs for serial numbers asynchronously. Andsome serial number providers use the standard MDLP CTC Import module. The standard MDLP CTC Importmodule can be used both to import CTCs for a set of uploaded sGTINs or to request both serial numbersand CTCs for a "Russian" GTIN.

In effect, the CTC GTIN Mapping Table lets you add a second module call - for requesting CTCs - to theserial number import module call already defined in the Prodcode Mapping table.

Serial number import modules that import CTCs with serial numbers for a "Russian" GTIN do not need anentry in CTC GTIN Mapping Table. All other SN import modules do need such an entry. In these cases, themodule in the Prodcode Mapping table requests serial numbers. The module defined in the CTC GTINMapping Table requests CTCs for the imported serial numbers.

The table below shows whether an entry in the CTC GTIN Mapping Table is needed for each serial numberimport module. For those modules that need an entry in the CTC GTIN Mapping Table, the table belowshows which CTC import module to enter.

SN Import Module Entry in Prodcode Table Entry in CTC Table CTC Call TypeSAP ATTP Serial NumberImport Module

Module entry required No entry needed. CTCssupplied with serialnumbers.

Not applicable

Tracelink serial numberimport

Multitenancy Tracelink SNImport

MDLP CTC Import ModuleorTracelink CTC importmodule (For informationon availability, pleasecontact PCE.)

Asynchronous, requestrepeated by PollingScheduler

SAP ICH (Pharmacode)Connector

SAP ICH Connector No entry needed. CTCssupplied with serialnumbers. (For infor-mation on availability,please contact PCE.)

Not applicable

Arvato CMO serialnumber connector

Arvato CMO serialnumber connector

No entry needed. CTCssupplied with serialnumbers. (For infor-mation on availability,please contact PCE.)

Not applicable


SN Import Module Entry in Prodcode Table Entry in CTC Table CTC Call TypeArvato MAH order andserial number connectorNote: Cannot be enteredas a serial number importmodule, because itfunctions as an orderimport module. Includedhere for completeness inlisting SN-importmodules.

Arvato MAH order andserial number connector

No entry needed. CTCssupplied with serialnumbers. (For infor-mation on availability,please contact PCE.)

Not applicable

MDLP (CRPT) CTC ImportConnector

MDLP CTC Import Module(both serial numbers andCTCs are imported fromCRPT)

No entry required Asynchronous, requestrepeated by PollingScheduler

MDLP (CRPT) CTC ImportConnector

Entry of moduleresponsible for SN import(not the MDLP CTCImport module)

MDLP CTC Import Module Asynchronous, requestrepeated by PollingScheduler

Settings > System Settings import Serial Numbers

To add an entry to the CTC GTIN Mapping Table, do the following:

1. Choose Management > Settings > import Serial Numbers.

2. Select a GTIN from the drop-down list. Only "Russian" GTINs are shown in the list.3. Select a CTC import module from the drop-down list. The list shows only the modules that are installed

in PSM.4. If the module is a multitenancy module, then you must also select the customer for whom the CTCs

should be imported.

5. Click the CTC-GTIN Mapping button.

Your entry is added to the CTC GTIN Mapping Table.

The entry is effective with the next run of the serial number import job. Unless otherwise noted in thetable above, CTC imports are supported only for the automatic import with the serial number import job.

Notes on Execution of SN/CTC Imports for "Russian" GTINsIf there is an entry in the CTC GTIN Mapping Table, then the system takes care of calling the CTC importmodule; no separate action on your part is required. The log messages concerning the serial number importmodule are unchanged. Additional log messages report the execution of the CTC import module.A CTC import module does not directly return CTCs. Instead, it returns a UUID, an ID for the import request.The Polling Scheduler (configured in the Settings) takes over responsibility for repeating the request inorder to pick up the CTCs after they have been generated.The system is responsible for interpreting the results of a polling request, deciding, for example, when arequest has failed in the event of repeated errors. A polling request is reported in Log Entries.

Manual import of serial numbers and CTCs for "Russian" GTINs is also supported, in addition to imports bythe automatic job for serial number imports.


12.7 Archive SettingsWith the Archive Settings, you can do the following:

• Activate archiving. After setup, archiving is active only if you enter a value in the Archive URL field.

• Temporarily stop archiving by entering a date in the future in the Suspend archiving until field.

Settings > System Settings > Archive Settings

Choose Settings > System Settings > Archive Settings to access these fields:

• Archive URL: This field specifies the host and port for communicating with the Archive Reporting Service(ARS). If archiving has been set up, then this field probably contains the URL determined during setup.Example: The field would be set to http://localhost:8084 if the ARS is installed on the PSM server.

• Test Connection lets you verify that the ARS answers, that you can communicate with the ARS. Thebutton is enabled only if you make a change to the address in Archive URL.

• Suspend archiving until lets you prevent the archiving jobs in the production database from archivingany records. The database archiving job checks the field when it starts. If a time stamp has been enteredinto the field, then the job does no archiving until the date and time specified in the field have beenreached. Archiving is effectively suspended.Use this field, for example, when you need to use a downtime for production and want to prevent anyextra workload from archiving.

12.8 Polling RequestsIn Settings > System Settings > Polling Requests, you can activate the Polling Scheduler. This scheduleris responsible for finishing asynchronous requests for crypto-codes and keys.Crypto-codes and keys are needed, together with sGTINs, for production for the Russian Federation market.Some serial number import modules need to make an asynchronous request for these crypto-codes. Since ittakes time to generate the crypto-codes, one needs to make an initial request, and then "call back later" toobtain the finished codes.You need to activate the scheduler only if the following conditions are true:• You are producing for the Russian Federation market, and your products are already required to have

crypto-codes. (Most if not all pharmaceuticals sold in the Russian Federation will need crypto-codes asof 1.1.2020.)

• Your serial number supplier needs an extra, asynchronous request to obtain crypto-codes and keys.Some serial number suppliers provide crypto-codes directly with imported serial numbers. Polling neednot be set up for such suppliers. For information on the modules, see [Import SerialNumbers } Page 90].

To activate the Polling Scheduler, do the following:

1. Settings > System Settings > Polling Requests.

2. Mark the activate checkbox.

3. Use the Cron Maker to schedule repetitive starts of the polling scheduler.

4. Choose Start Scheduler to start the scheduler immediately.

The scheduler reports on completion of CTC requests and on failures to complete a request for crypto-codesin the Log Entries.

A crypto-code request must finish successfully in order for "Russian" sGTINs (serial number and GTINcombinations) to be available for production. Until the crypto-codes are available, downloaded "Russian"serial numbers have the status "pending".


12.9 CTC Purge SchedulerIn Settings > System Settings > CTC Purge Scheduler, you can activate a job that deletes Russian crypto-codes and keys when they are no longer needed. Crypto-codes are cryptographical signatures that mustaccompany sGTINs in labeling for item-rank products that are to be sold on the Russian market.According to Russian Federation regulations, crypto-codes must be deleted as soon as they have beenused. The CTC Purge Scheduler therefore looks for crypto-codes that have been used and that are not beingheld in local cache storage. These crypto-codes and keys are then automatically deleted. The accom-panying serial numbers are not affected. The Purge Scheduler reports the number of crypto-codes and keysit has deleted in Log Entries after every run. A message is logged even if no crypt-codes are deleted.

You need to activate the CTC Purge Scheduler only if you are producing for the Russian Federation marketand are subject to the crypto-code requirement. (Most if not all pharmaceuticals become subject to thisrequirement as of 1.1.2020.)

Settings > System Settings CTC Purge Scheduler

To activate the CTC Purge Scheduler, do the following:

1. Settings > System Settings > CTC Purge Scheduler.2. Mark the activate checkbox.

3. Use the Cron Maker to schedule repetitive starts of CTC Purge Scheduler.

4. Choose Start Scheduler to start the scheduler immediately.

The scheduler reports on its activities in the Log Entries. You will find information on purging of crypto-codes and keys.Note that because of their transient nature in the system, crypto-codes and keys are visible to users only onprinted labels. They are not shown in system displays or reports on orders and production.


13 Settings for all LinesIn the menu Settings > Settings for all Lines can be selected. This is an alternative to defining these settings with the "DEFAULT"-line in PLM (see PLM manual for moreinformation).

13.1 Serial Number Management

Settings > Settings for all Lines > Serial Number Management

If this checkbox is activated, the lines will use serial number ranges that are imported from a Level 4system; if it is deactivated, PLM generates own serial number ranges.


13.2 Password and Login Settings

Settings > Settings for all Lines > Password and Login Settings

This menu allows displaying and modifying rules for Auto Login and password settings for the PLM usermanagement.

NOTICE


13.2.1 Active Directory Settings

Settings > Settings for all Lines > Password and Login Settings

This menu allows displaying and modifying Active Directory settings for the PLM user management.


13.3 Rank Descriptions

Settings > Settings for all Lines > Rank Descriptions

In this menu, the default rank descriptions used in PLM and PSM can be modified.


14 Log Entries

NOTICEUser "SYSTEM"If the user "SYSTEM" exists, global log entries (log entries without a user) fromwebservices or schedulers are assigned to this user. The user is not created automaticallyby PSM but has to be added manually. It is recommended that the user "SYSTEM" doesnot have any rights and is not assigned to a user group. See also chapter [Adding aUser } Page 22].

This feature allows you to view all log entries (the Audit Trail) made by any line to which PLM and PSM areconnected. If you have activated archiving, then the Active tab shows you log messages in the productiondatabase. The Archived tab shows you messages that have been moved to the archive database.

1 Click Log Entries. The following screen appears:

Log Entries

2 At the Log Entries screen all entries are shown. To search some log data click the field below ‘Search’and enter the word you are looking for, e.g. “logged”.ð Then you get a list with all entries containing the word logged in the message text. See below:

Log Entries (Search Entry)

• It is also possible to filter the results by using the scroll down menus: ‘Type’, ‘User’ or ‘Line’. Select theitems to filter the search.

• Additionally you can restrict the time frame; click on the fields ‘from’ and ‘until’ and select the start andend time.

Exporting or printing the actually shown entries as report is possible byclicking the corresponding buttons below the search fields. After clicking,the print or the save/open dialog box appears.


Language of log entriesFor logs with validation messages from the order service, the language is chosen depending on the sourceof the request. If the request comes from a client via SOAP the logs will be in the system language. If therequest comes from the UI (e.g. order export via UI) the logs will be in the user language.


15 Appendix

15.1 Modules

Setting ValidationSingle tenancy as well as multi tenancy modules can now validate a single setting in the module settingsview. A setting can also be validated based on other module settings.

Cross setting validation

Multi tenancy modules highlight the tab that contains invalid module settings.

Multitenancy Setting - Invalid Tab highlighted

Required module settings cannot be disabled by the user.

15.1.1 SecurPharm

15.1.1.1 Purpose

The SecurPharm Order Export Module exports work orders from the PCE Database to the PU System.• All messages can be exported as files directly to the file system (local or shared network drive) or sent

via HTTP POST to the PU system.• The xsd SchemaDefinition for the generated message files can be found in appendix A, B & C.• To trigger the OrderExport see the PSM Core Manual to either configure the OrderExport timer or export

the orders manually.

15.1.1.2 General Settings - Order Export

See chapter [Exporting Orders } Page 53].

15.1.1.3 Specific Module Settings - SecurPharm

Please edit specific modules settings in the PSM menu > Settings > Module Settings.

At the SecurPharm OrderExport Module the following settings can be edited:


Setting Description ValuecompanyID IFA Number.

The module will lookup thecompany prefix (R05) on Rank 0and if it is not set the companyIDwill be used as fallback.

Integer

RUU Responsible Unit Upload (E-mailaddress)

String

RUD Responsible Unit Data (E-mailaddress)

String

Splitting Size Define the quantity of how manyserial numbers put per XMLmessage, if this is less than thewhole order quantity, multiplemessages will be generated. If nosplitting size is set, the default is1000.

Integer

Output The output setting defines thetargets to where the generated XMLfiles should be put. That can beany URL referring to a folder in afile system or network, a RestfulService listening for HTTP PostRequests, a FTP Server or even E-mail addresses.

String


15.1.1.3.1 Output

The output setting defines the targets to where the generated XML files should be put. That can be any URLreferring to a folder in a file system or fetwork, a Restful Service listening for HTTP Post Requests, a FTPServer or even E-mail addresses.Further conditions can be defined to specify which work orders should be exported. The xsd for the outputxml can be found in appendix D.In the simplest case only output destinations (URLs) will be defined.Example:<output>

<output_dest url="http:///xxx.xxx.xxx.xxx:yyy/path" user="user"password="secret" /><output_dest url="file:///Users/xyz/orderexport" user="" password="" /></output>

In this case the XML file will be exported to either of the defined URLs. In addition, it is possible to defineconditions if a work order should be exported to the defined URL or not. All conditions can be logicallylinked. A condition defines if specific order data is contained or not in the work order to be exported.It can be defined for example, that only work orders with a lot number contained (AI 10) or AI X01 on rank2 should be exported to the folder /Users/xyz/orderexport, while only work orders with the name like >Test>and which do not have AI X02 included in order data will be exported to http://xxx.xxx.xxx.xxx:yyy/path.The following example shows the setup for this scenario:<output>

<output_dest url="file:///Users/xyz/orderexport" user=" " password=" " ><conditions boolean_operation="and"><condition boolean_operation="or"><contains type="true" ai="10" /><contains type="true" ai="X01" rank="2" /></condition> </conditions></output_dest><output_dest url="http://xxx.xxx.xxx.xxx:yyy/path" user="user"password="secret" ><conditions boolean_operation="and"><condition boolean_operation="and"><contains type="true" ai="R08" ai_value=“%Test%“ /><contains type="false" ai="X02" /></condition></conditions></output_dest></output>


15.1.1.3.2 Configure RUU / RUD Dynamic

When the e-mail addresses for Responsible Unit Upload or Responsible Unit Data are differing for orders,there is a simple way to configure this scenario. Use: dynamic([AI]) as setup and the exported order willcontain the value for the specified AI as Responsible Unit Upload or Responsible Unit Data.

ExampleExample Setting:

Example Order Data:

Note: The AI must be added on global rank as order data.Advice:• Take one of the AIs starting with X.• There is a way to prohibit the option to set this AI as order data on any other rank. Inform your IT

department that in the PCE database column i16_fixrank in tbl_ai has to be 0 for the AI specified in thesetting. Be aware that this should be documented and only done by experts.

15.1.1.4 Message Codes

The following message codes & audit trail entries will be generated in this module:

Message N° Message Text Description95000 OrderExport successful Message if order export was successful

(includes order name and URL)

95001 OrderExport failed Message if order export failed (includesorder name, URL and reason)


15.1.1.5 Appendix

15.1.1.5.1 Appendix A

G220.xsd<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"xmlns:tns="urn:types.pu.pu-system:v1.0" targetNamespace="urn:types.pu.pu-system:v1.0" elementFormDefault="qualified" attributeFormDefault="qualified"><xs:include schemaLocation="PUS_PU_Composite_Types.xsd" /><xs:include schemaLocation="PUS_PU_Base_Types.xsd" /><xs:element name="G220_UploadPUData_Request" type="tns:G220Request_Type"><xs:annotation><xs:documentation> Structure for package data upload to PU-System </xs:documentation></xs:annotation></xs:element><xs:complexType name="G220Request_Type"><xs:complexContent><xs:extension base="tns:BatchRequestHeader_Type"><xs:sequence><xs:element name="ProcessInput" type="tns:G220ContentRequest_Type" /></xs:sequence> </xs:extension></xs:complexContent></xs:complexType><xs:complexType name="G220ContentRequest_Type"><xs:sequence><xs:choice><xs:annotation><xs:documentation>Please provide PPN or NTIN</xs:documentation></xs:annotation><xs:element name="PPN" type="tns:PPN_Type" /><xs:element name="NTIN" type="tns:NTIN_Type" /></xs:choice><xs:element name="LOT" type="tns:LOT_Type"><xs:annotation><xs:documentation>defines a Lot</xs:documentation></xs:annotation></xs:element><xs:element name="EXP" type="tns:EXP_Type"><xs:annotation><xs:documentation>expiration date of LOT</xs:documentation></xs:annotation></xs:element><xs:element name="Notification"><xs:annotation><xs:documentation>notification recipient structure for process status infor-mation</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="Responsible_Unit_Upload"><xs:annotation><xs:documentation>email of responsible business unit for data upload process</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="Email" type="tns:EMail_Type" minOccurs="1" maxOccurs="1" /></xs:sequence></xs:complexType></xs:element><xs:element name="Responsible_Unit_Data"><xs:annotation><xs:documentation>email of responsible business unit of data content</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="Email" type="tns:EMail_Type" minOccurs="1" maxOccurs="1" /></xs:sequence>


</xs:complexType></xs:element></xs:sequence></xs:complexType></xs:element><xs:element name="SerialNumbers"><xs:annotation><xs:documentation>list of serial numbers</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="SN" type="tns:SN_Type" minOccurs="1" maxOccurs="2000000" /></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType></xs:schema>


15.1.1.5.2 Appendix B

PUS_PU_Base_Types.xsd<?xml version="1.0" encoding="UTF-8"?>

<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="urn:types.pu.pu-system:v1.0" targetNamespace="urn:types.pu.pu-system:v1.0" elementFor-mDefault="qualified" attributeFormDefault="qualified"><simpleType name="EXP_Type"><annotation><documentation>Verfallsdatum einer Productpackung - YYMMDD </documentation></annotation><restriction base="token"><pattern value="([0-9]{2})((0[1-9])|(1[0-2]))((0[0-9])|([1-2][0-9])|(3[0-1]))"/></restriction></simpleType><simpleType name="LOT_Type"><annotation><documentation> Datentyp zur Identifikation einer Charge 0-9; A-Z; ErlaubteSonderzeichen „-“ und „ _ “ keine Kleinschreibung, keine Umlaute. </documen-tation></annotation><restriction base="string"><minLength value="1"/><maxLength value="20"/><pattern value="([A-Z]*[0-9]*_*-*)+"/></restriction></simpleType><simpleType name="CompanyId_Type"><annotation><documentation>Merkmal zur Identifizierung eines PU/Herstellers als IFACompany ID </documentation></annotation><restriction base="int"><minInclusive value="1"/><maxExclusive value="999999999"/></restriction></simpleType><simpleType name="ExternalTransactionID_Type"><annotation><documentation> TransaktionsID externes System </documentation></annotation><restriction base="string"><minLength value="1"/><maxLength value="32"/><pattern value="([A-Z]*[a-z]*\d*-*)+"/></restriction></simpleType><simpleType name="NTIN_Type"><annotation><documentation> Code zur Identifikation eines Produktes </documentation></annotation><restriction base="string"><minLength value="13"/><maxLength value="13"/><pattern value="[0-9]*"/></restriction></simpleType><simpleType name="PPN_Type"><annotation><documentation> Code zur Identifikation eines Produktes </documentation></annotation><restriction base="string"><minLength value="12"/><maxLength value="22"/><pattern value="([A-Z]*[0-9]*)+"/></restriction></simpleType><simpleType name="SN_Type"><annotation>


<documentation> Code zur Identifikation einer Produktpackung 0-9; A-Z KeineSonderzeichen, keine Kleinschreibung, keine Umlaute. </documentation></annotation><restriction base="string"><minLength value="1"/><maxLength value="20"/><pattern value="([A-Z]*[0-9]*)+"/></restriction></simpleType><simpleType name="EMail_Type"><annotation><documentation> Datentyp E-Mail </documentation></annotation><restriction base="string"><minLength value="0"/><maxLength value="100"/><pattern value="\w+([\-+.']\w+)*@\w+([\-.]\w+)*\.\w+([\-.]\w+)*"/></restriction></simpleType></schema>


15.1.1.5.3 Appendix C

PUS_PU_Composite_Types.xsd<?xml version="1.0" encoding="UTF-8"?>

<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="urn:types.pu.pu-system:v1.0" targetNamespace="urn:types.pu.pu-system:v1.0" elementFor-mDefault="qualified" attributeFormDefault="qualified"><include schemaLocation="PUS_PU_Base_Types.xsd" /><complexType name="BatchAuthenticationData_Type"><sequence><element name="CompanyID" type="tns:CompanyId_Type"><annotation><documentation>IFA Company-ID</documentation></annotation></element></sequence></complexType><complexType name="RequestTransactionData_Type"><sequence><element name="ExtTrxId" type="tns:ExternalTransactionID_Type" minOccurs="1"maxOccurs="1"><annotation><documentation>Transaction-Id of calling system</documentation></annotation></element></sequence></complexType><complexType name="BatchRequestHeader_Type"><sequence><element name="Authentication" type="tns:BatchAuthenticationData_Type"><annotation><documentation>Structure for authentication data</documentation></annotation></element><element name="Transaction" type="tns:RequestTransactionData_Type"><annotation><documentation>Structure for technical transactional data </documentation></annotation></element></sequence></complexType></schema>


15.1.1.5.4 Appendix D

Out.xsd<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"xmlns:xs="http://www.w3.org/2001/XMLSchema">

<xs:element name="output"><xs:complexType><xs:sequence><xs:element name="output_dest" maxOccurs="unbounded" minOccurs="0"><xs:complexType><xs:sequence><xs:element name="conditions" minOccurs="0" maxOccurs="1"><xs:complexType><xs:sequence><xs:element name="condition" maxOccurs="unbounded" minOccurs="0"><xs:complexType><xs:sequence><xs:element name="contains" maxOccurs="unbounded" minOccurs="0"><xs:complexType><xs:simpleContent><xs:extension base="xs:string"><xs:attribute type="xs:boolean" name="type" use="required" /><xs:attribute type="xs:string" name="ai" use="required" /><xs:attribute name="rank" use="optional"><xs:simpleType><xs:restriction base="xs:integer"><xs:minInclusive value="0"/><xs:maxInclusive value="8"/></xs:restriction></xs:simpleType></xs:attribute><xs:attribute type="xs:string" name="ai_value" use="optional" /></xs:extension></xs:simpleContent></xs:complexType></xs:element></xs:sequence><xs:attribute name="boolean_operation" use="required"><xs:simpleType><xs:restriction base="xs:string"><xs:enumeration value="and"/><xs:enumeration value="or"/></xs:restriction></xs:simpleType></xs:attribute></xs:complexType></xs:element></xs:sequence><xs:attribute name="boolean_operation" use="required"><xs:simpleType><xs:restriction base="xs:string"><xs:enumeration value="and"/><xs:enumeration value="or"/></xs:restriction></xs:simpleType></xs:attribute></xs:complexType></xs:element></xs:sequence><xs:attribute type="xs:string" name="url"/><xs:attribute type="xs:string" name="user"/><xs:attribute type="xs:string" name="password"/></xs:complexType></xs:element></xs:sequence></xs:complexType></xs:element></xs:schema>


15.1.2 TraceLink

15.1.2.1 The TraceLink Module

The installable file of the TraceLink module installs two separate modules in your PSM system:• The TraceLink Serial Number Import module, which imports serial numbers from TraceLink for GTINs,

NTINs, or product codes; and• The TraceLink Order Export Module, which exports produced serial numbers and complete order infor-

mation to TraceLink.This document describes the use of both of these modules.TraceLink comes in single-tenancy and multitenancy forms. This document describes both the single-tenancy and multitenancy versions of the TraceLink Order Export and Serial Number Import Modules. Thesingle-tenancy versions of the module must be installed for multitenant operation. Differences in the multi-tenancy version of the module are described where needed.The menu paths specified in this manual are for the single-tenancy version of the module, unless otherwisespecified. You can find the settings for the multitenancy version under Settings > Multi-tenancy Modules.Only one version of the modules appears in a single installation of PSM.

15.1.2.2 Installing New Versions of the Modules

If you install an upgrade of the TraceLink Modules AND the upgraded modules introduce new parameters inthe module settings or change or delete parameters, then there is an extra maintenance step that you musttake as part of the installation.This additional step is to re-create each of the customer definitions that you have created for the affectedmodule. If, for example, an upgrade of the TraceLink Order Export Multitenancy Module introduces a newmodule setting, then you must re-create each of the customer definitions that you have previously set up forthis module. In these new definitions, you can make any setting that is required for the new moduleparameter.The procedure to follow for re-creating customer definitions when you make such a module upgrade is asfollows:1. Document and delete all existing customer definitions.2. Clear the Glassfish cache.

That is, delete the contents of the generated directory in the Glassfish directory structure:\glassfish4\glassfish\domains\PCE-PSM\generated.

3. Re-create each of the customer definitions of the affected module.The reason for this additional task is that it is not possible for an updated module to propagate new modulesettings to existing customer definitions. It is therefore necessary to recreate these definitions.When you install an updated version of the TraceLink Multitenancy Modules, please check the VersionHistory to see if there has been a change in the available module settings. If so, then you can re-create thecustomer definitions of the affected module.

15.1.2.3 Order Export Module

The PSM Tracelink Order Export Module exports produced serial numbers as well as all data related to theorder from the PCE PSM system as XML files to Tracelink via secure FTP or HTTP post.For example, the production date (AI 11) is populated to the item detail for any type of order as long as it isdefined in the order.


General SettingsGeneral Order Export Settings can be found in the PSM menu under Settings > System Settings > OrderExport. The section extended Settings contains the work order states to be exported.

Specific Module SettingsThe Tracelink specific order export settings can be defined under Settings > Module Settings > TraceLinkOrder Export Module. Some of the settings are described in the following chapters but not all as they areexplained in the column Description of the Module Settings table.

Be aware that the column Activated is not considered in the module settings. You do not activate ordeactivate the setting by activating this checkbox.

15.1.2.3.1 Product Definition

The product is defined in Tracelink by the internal material code or by the country drug code. Therefore youhave to correctly define the product mapping in PSM so that the exported workorder can be matched in theTracelink system.There are two different mapping definitions to work with Tracelink.1. Product is defined by the internal material code

The internal material code set in the Tracelink system must be known. In PSM you have to define howthe internal material code should be populated. There are two different ways to define it:

– By product nameThe product name created in PSM must match the internal material code on the TraceLink side. Inthis case, set the TraceLink parameter AI for the Internal Material code to AI R07. R07 is setautomatically to the product name.

– By AI definition

You specify that an AI, for example X30, contains the internal material code. You then identify it inthe module configuration in parameter AI for the Internal Material code, as shown in thescreenshot below. This AI must be present in the order data definition with the correct value of theinternal material code.

Note that you MUST set the AI for the Internal Material code parameter to R07 or to an Xnn AI ofyour own definition, if the parameter AI-Code containing country drug code ID is empty. That is,you are not using the second type of mapping via the AI-Code containing country drug code IDparameter.You can regard the "By product name" and "By AI definition" possibilities for identifying the productname as equivalent options. If you define the product name to be identical to the TraceLink internalmaterial code, then you can specify R07 as the value for parameter AI for the Internal Materialcode. If your product name is different than the TraceLink internal material code, then you candefine your own AI to contain the TraceLink internal material code and specify this Xnn AI as thevalue for AI for the Internal Material code.


2. Product is defined by country drug codeThe country drug code set in the Tracelink system must be known. In PSM you have to define twomodule settings:

– the AI containing the country drug code ID– AI code containing country drug code valueThese two AIs have to be present in the order data definition with the correct value of the country drugcode ID and value.

AI-Code containing country drug code valueThe country drug code is a mandatory information in most specifications. The code is linked to the internalmaterial code.For China production, the country drug code is populated automatically by the TraceLink PSM Connector. Inother types of production such as GS1 (Korea, Saudi Arabia), this information must be populated from anadditional application identifier. Please use the specified configuration fields for this. If you need to populatethe country drug code, add two new order data on Rank 0. For example, AI X29 might be used to identifythe drug code ID, and AI X32 is the value.

Drug Code IDs

Drug Code ID CountryUS_NDC_541 USA

US_NDC_532 USA

US_NDC_442 USA

US_NDC_542 USA

SA_SAUDI_DRUG_CODE Saudi Arabia

KR_KFDA_CODE Korea

CN_SUBTYPE China

AI Validation before ExportYou can execute an order data validation before export. The validation checks if configured ApplicationIdentifiers and their value format match a given regex pattern. The export is interrupted if the AI validationfails.

In order to use the validation, activate the setting Enable AI Validation and define the rules for the validationin the setting AI Validation XML.

Triggering the ExportYou can trigger a work order export via scheduler or manually. For details on scheduling the export, seePSM User Manual.


Use the PSM interface to export a work order manually. Navigate to Management > Order Managementand click export order.If you use the multi-tenancy implementation, click Export Order for Target Customer.

15.1.2.3.2 File Processing

Option DescriptionActivate processing check This option can only be activated if on the Tracelink

side the processing report is activated so thatTracelink after file processing generates a processingstatus file that can be downloaded and evaluated byPSM. This option is usually used together with filesplitting and the full_way strategy. Because theTracelink system is based on transactional fileprocessing and therefore when using file splitting itcan happen that the files are not processed in theright order. With file processing it is ensured thatPSM sends the next file only if the previous one wasprocessed correctly without any errors or warnings.This is also valid for the full_way strategy in whichthe file order is important.

Processing attempt count This option defines how many times PSM will lookfor the processing file in the defined folder. The wait-ing between two attempts is always 30 seconds andcannot be changed. Predefined attempts are 10. Youmay need to increase the number of attempts ifTracelink needs more time than 10 x 30 seconds toprovide the processing file. The larger the splittingsize the more attempts for processing you may need.

Splitting size Number of items after which the export files are split.Tracelink supports files with a maximum size of 100MB.The configured splitting size is used to generatesmaller XML file parts if you want to upload thegenerated files through the Tracelink portal. Note thatthe number of units given as splitting size, is thenumber of units that must be stored in the memory!In case of "Out of memory" errors, this setting isprobably too large. E.g: 50000.


15.1.2.3.3 Secure File Transfer (sFTP) Settings

Note that the sFTP account is provided by Tracelink.

When exporting via sFTP, the following fields are mandatory:

Field DescriptionsFTP Host The server address of the secure FTP server.

sFTP Port The port used by the PSM sFTP client to connect tothe Tracelink secure file server.

sFTP Private key Path The path to the private key file. The private key filecan be generated with the putty tool. You also needto generate a public key and send it to Tracelink inorder to authenticate.

sFTP Private Key Passphrase The private key passphrase is needed if you use apassphrase when generating the private/public keypair.

sFTP User The username used for the authentication.If youselect the Public Key field, it will be used instead ofusername and password.

sFTP Password The password used to identify the connected user. Ifyou select the Public Key field, it will be used insteadof username and password.

15.1.2.3.4 HTTP Settings

Note that these credentials are provided by Tracelink.

When exporting via HTTP post, the following fields are mandatory:

Field DescriptionHTTP URL An URL provided by Tracelink. Allows a post request

to push your data.

HTTP User The username used for the authentication.

HTTP Password The password used to identify the connected user.

15.1.2.3.5 End of Batch (EOB) Settings

Optionally, you can turn on the Tracelink End of Batch message exchange. An End of Batch (EOB) inboundmessage enables the PSM-Tracelink Connector installed in a CMO or pharmaceutical manufacturerpackaging location (a.k.a. plant location) to communicate the batch production status after commis-sioning.


The EOB message is sent by PSM via sFTP to Tracelink with the quantity of serial numbers commissionedand enables a check and validation of the amount produced. Tracelink responds with an EOB Acknowl-edgement, various types of messages depending on whether an error has been found during the check ornot. EOB confirmation messages appear in the log. Alternatively, you can check the EOB file directly. The fileis in the directory defined in the EOB Directory parameter of the module.There are three parameters for the End of Batch function.

Enable End of Batch ParameterOptionally, mark the checkbox of this parameter to turn on the End of Batch feature.If you mark the Enable End of Batch checkbox, then the EOB Directory and EOB Delay parameters arerequired.

EOB Directory ParameterEnter the pathname to an existing directory for the End of Batch SNX exchange. You can select any existingdirectory that you wish to use.

EOB Delay ParameterThis parameter specifies the period in seconds that PSM should wait before sending an EOB message toTracelink. The delay that you set in this parameter - in seconds - must be long enough to allow Tracelink toprocess all Disposition Assign and Disposition Update messages. The default value is 300 seconds.

15.1.2.3.6 Strategies for Export

There are two different strategies you can use for the export. The field is mandatory and needed to definehow the content of the disposition assigned file looks like.

Full wayThe full strategy consists of exporting the entire production as a disposition assigned XML file. Valid,verified, and printed are not considered as every produced order unit will be populated as a commissionedevent.This strategy is usually used by CMOs.Prerequisites:• Order is aggregated or only serialized.• Serial numbers used in production are fully or partially requested from a third party serial number

manager and are not requested from Tracelink.Tracelink will receive 3 files at most:• A Disposition Assigned file that contains all units of that production• A Disposition Update File that contains all decommissioned units: STATUS DECOMMISSIONED• A Disposition Update File that contains all destroyed units if some exist. STATUS DESTROYED

Easy strategyThe easy strategy consists of exporting only the good produced Units (bit valid, bit verified and bit printedare true) as a disposition assigned XML file followed by a disposition update file with a DEACTIVATED State.This workflow supports serialization across different ranks without aggregation.Prerequisites:• Order is aggregated or only serialized• Serial Numbers are provisioned from Tracelink.

For example, serial numbers for ranks rank 1, 3, and 4 were previously requested from Tracelink.Tracelink will receive 2 files:• A Disposition Assigned file that contains all good units of that production in the commissioned event.


• A Disposition Update File that contains all Decommissioned and Destroyed units with STATUSDEACTIVATED.

Activating the strategy1. Go to Settings > Module Settings > TraceLink Order Export Module.

2. In the field Export Strategy type in either "Full_WAY" or "EASY_WAY".

3. Click save.

15.1.2.3.7 Exporting a Purchase Order Number

To export a purchase order (PO) number to TraceLink with an order, activate the Purchase Order AI setting.Specify the AI that contains the purchase order. The AI must be defined on Rank 0 of an order. It mustcontain a value, or it is ignored at export. By default, the AI that is expected to contain the purchase order isAI 400.The format of the purchase order in the XML export file is as follows:<ReferenceDocuments><PONumber>230813</PONumber><WorkOrderNumber>230813</WorkOrderNumber> </ReferenceDocuments>

15.1.2.3.8 Further configuration

Go to Settings > Module Settings > TraceLink Order Export Module.

The table gives further explanation to some of the module settings.

Name ExplanationUpload to Tracelink If you want to export generated XML files (dispo-

sition_assigned and disposition_update files)automatically, activate the checkbox. This optionneeds either a sFTP configuration or a HTTP configu-ration in order to ping the server and validate yourdata before the automatic export is started.

Export Pallets This configuration is useful for non-aggregatedproduction (US scenario). This function will beconsidered by the connector if the production is onlyserialized on more than one rank.

Pallet Rank If you want to exclude the pallet from the dispositionassigned file, define the pallet rank that you want toexclude.


Tracelink Specific ConfigurationThese configurations have to be requested from Tracelink.

Full/Partial Pallet/CaseWhen implementing the FULL/PARTIAL bundle/case scenario, the Tracelink module can detect it andgenerates a separated commission event for every state (FULL and PARTIAL), allowing the usage of differentcompany prefixes in each aggregation level.

Custom NTIN definitionsThis setting takes a regular expression as a value. GTINs that match the regular expression will be identifiedas NTINs. If the setting is disabled, all GTINs will be identified as GTINs regardless of the setting value.

NOTICEMutltitenancy configurations not updated automaticallyFor multitenancy installations this setting is only available for new customer configu-rations.

See also2 Strategies for Export } Page 116

15.1.2.4 Serial Number Import Module

The Tracelink serial number import module imports serial numbers from a SOAP Web Service provided byTracelink in to the PSM – PCE Database. The Tracelink SN Import Module can handle serial numbers indifferent lengths. Serial numbers within the PCE System are either based on GTINs (SGTIN), NTIN, CompanyPrefix and Extension Digit (SSCC) for GS1 work orders, or a product code reference for China Coding.Supported NTINs are:• GERMANY ("4150")

+PZN + CheckDigit• AUSTRIA ("908888")

+PZN + CheckDigit• FRANCE ("3400")

+ CIP/ACL Code + CheckDigit• SPAIN ("847000")

+ Codigo Nacional• NORDICS ("704626")

+ Nordic Drug Code from Nordic Number Office + CheckDigitFor Sweden, Finland, Denmark, Iceland, Norway

• SWITZERLAND ("7680")+ Swissmedic Code (5-digit product license number + 3 digits pack size indicator) + check digit

• POLAND_AND_SLOVAKIA ("590999")Shared prefix for Poland and Slovakia

The serial numbers can be either imported manually or automatically (Scheduler).


The TraceLink Order Export Module recognizes a serial number as an SSCC in part with the letter combi-nation "SC". A serial number is considered to be an SSCC if it begins with the letters "SC", has a length of20 characters, of which the final 18 are numbers.

Importing Serial Numbers for Production for the Russian FederationAs of Version 1.33 of the PSM Tracelink Module, the serial number import module can import serialnumbers for production for the Russian Federation. As of 2019 for some products, item-rank productsdestined for the Russian Federation market must be coded with an additional crypto-code and key (CTC), inaddition to the sGTIN.The Tracelink serial number import module recognizes "Russian" GTINs and stores serial numbers importedfor such a GTIN in a special table, tbl_prodcodecryptolists. From there, a new Tracelink module, forimporting crypto-codes and keys, gathers newly imported serial numbers and submits them to the CRPT inRussia for generation of the crypto-codes and keys (CTCs). Note that at the time of release of this manual,final interface specifications for the new Tracelink interface have not been released; the connector istherefore not yet available. In the iterim, it is possible to use the MDLP Connector to import CTCs forTracelink serial numbers.Since generation of crypto-codes is time consuming, this request is completed asynchronously. The CRPTanswers the request from the Tracelink CTC import module with a request ID, which is stored in thetbl_asyncjobs table. The Polling Scheduler in PSM taks over completion of CTC import requests. It repeats arequest until the crypto-codes and keys can be downloaded or an error is returned.Note that special products must be defined at Tracelink for Russian production. The Russian regulationsrequire that serial numbers have a length of 13 characters. Otherwise, crypto-codes and keys cannot begenerated for the serial numbers.

15.1.2.4.1 Module Settings

General settingsGeneral serial number import settings can be found in the PSM menu under Settings > System Settings >import Serial Numbers.

The section extended Settings contains the option append Ranges, which can be selected to append serialnumber ranges instead of creating a new range for each request (not valid for SN list import). For automaticserial number import and timer settings, see chapter [Module Trigger via Scheduler } Page 156].

Specific Module SettingsAll specific module settings are provided by Tracelink. The settings are the same for single-tenant and multi-tenant implementations of Tracelink. The multi-tenant version allows you to define separate configurationsfor each customer in your system.

Mandatory fields are:

Name DescriptionSN-Request web service Port Provided SOAP server address to request serials.

Web service User Username needed for the Authentication


Name DescriptionWeb service Password Password used to identify the user

Sender Identification flag, needed to proceed the request.

Receiver Identification Flag

Custom NTIN definitionsThis setting takes a regular expression as a value. GTINs that match the regular expression will be identifiedas NTINs. If the setting is disabled, all GTINs will be identified as GTINs regardless of the setting value.

NOTICEMutltitenancy configurations not updated automaticallyFor multitenancy installations this setting is only available for new customer configu-rations.

Serial Number FormatSerial numbers coming from Tracelink will be persisted in the database in the following format: (extensiondigit)(company-Pref)(SSCC-serial).

Triggering the ImportBefore importing serials, all defined Product codes (GTIN, SSCC, and China) have to be inserted in the PCEdatabase at the Tracelink site. All unknown or unreleased product codes cannot be served.• Import serials manually

Use the PSM interface to import serial numbers. Refer to the PSM User Manual.• Import serial numbers automatically

– Create a serial number mapping. The mapping ensures a correct import if you use more than oneimport module or the multi-tenancy implementation. A product code mapping can be created perproduct code and rank so that you can use the same company prefix and extension digit on differentranks.

– Configure the scheduler.– Activate the scheduler.

– To start the import, click Start Scheduler.

See also2 Product Definition } Page 112

15.1.2.5 Supported Regulations

Supported regulations are:


• GS1Serial number import: the module supports the request of serial numbers related to a GTIN or SGTINOrder export: the Tracelink specifications are met. For example, the item code definition is set correctly.

• CHINASerial number import: the module supports the request of serial numbers related to a china prodcode.Order export: the Tracelink specifications are met. For example, the item code definition is set correctlyand the production date is mandatory.When adding a prodcode in PSM for CHINA, it is important that the prodcode has a specific format sothat Tracelink can recognize it. Type in the prodcode in the following format: <prodcode>|rank

• SecurpharmSerial number import: the module supports serial number requests related to a NTIN for the followingcountries : Germany, Austria, France, Spain, Nordics, Switzerland.Order export: the Tracelink specifications are met. For example, the item code definition is set correctly.


15.1.3 Multitenancy

15.1.3.1 Overview

Multitenant Serial Number Imports and Order ExportsPSM supports multitenancy for serial number imports and order exports. With the PSM MultitenancyModule, you can import serial numbers from a source (e.g. Tracelink or Arvato) for different customers ofyours.

A customer in PSM is a customer-specific configuration for an order export module or for a serial numberimport module. See chapter [Creating a Customer Configuration } Page 124].Also, you can export orders from different customers to the same source (e.g. an ERP system).


Multitenant Order Export DispatchingPSM supports multitenancy for order export dispatching. The Order Export Dispatcher Module makes itpossible for you to run a series of order export modules when an order is exported. For example, you canuse the Order Export Dispatcher Module in production for the Russian Federation to 1) execute the OrderExport Module that exports the order to your L4 System and 2) execute the additional CRPT Order ExportModule that exports the order to the Russian authorities. The Order Export Dispatcher Module is integratedinto PSM as of Release 1.14.

Order Export Dispatcher Module

Multitenant Import of Crypto-Codes and Keys for Production for the Russian FederationPSM supports multitenant import of crypto-codes and keys with the MDLP Connector for production for theRussian Federation.The MDLP connector can be used to import both serial numbers and crypto-codes and keys from the MDLPsystem of the CRPT (Center for Research in Perspective Technologies), the provider of crypto-codes andkeys.The MDLP Connector can also be used together with the serial number import module of another provider.In this case, it requests and imports crypto-codes and keys for the serial numbers imported from the otherprovider. The MDLP connector can be used in this way with any other SN import module that does not itselfimport crypto-codes and keys.


In both usage scenarios, multitenancy allows the MDLP connector settings to be customer specific.

Crypto-Code and Key Import with the MDLP Connector

15.1.3.2 Requirements

• The Multitenancy Module requires the PCE database schema version 2.2 or higher.• For multitenancy order exports and serial number imports, multitenancy modules must be installed.

For example the PSM Multitenancy Tracelink Order Export Module.• Each multitenancy module requires the installation of the corresponding singletenancy connectors.

See example below.

You can check all installed modules in the System Information panel under Settings > System Settings.

Example: System Information > Settings > System Settings

15.1.3.3 Module Upgrades and Customer Definitions

If you upgrade a multitenancy module (or its single-tenant version) and the new version adds, deletes, orchanges a module setting, then you must re-create the customer definitions of the upgraded module.Please check the version history of a module when you perform an upgrade. The version history will informyou if changes to module settings were made.For more information, please see [Re-Creating Customer Definitions After an Upgrade with Changes inModule Settings } Page 126].

15.1.3.4 Creating a Customer Configuration

A customer in PSM is a customer-specific configuration for an order export module or for a serial numberimport module.


You can create a customer in the Settings view of multitenancy modules at Settings > Multi-tenancyModules > select a module.

Example for Multitenancy Tracelink Order ExportIf you did not yet create a customer, the view of the module will look as follows:

Settings view of multitenancy modules at Settings > Multi-tenancy Modules > Multitenancy Tracelink Order Export

1 Click on the button at the end of the frame Customer Configuration.

2 Click on + New configuration.

3 Enter the customer's name.

4 Click Save Settings.

ð The customer is created. You can now configure the module settings for this customer. Instead ofconfiguring the settings for the singletenancy module itself, you can now define own settings for everycustomer. Refer to the user manual of the corresponding single tenancy modules.

NOTICEConfigurations not updated automaticallyIf settings are added, deleted or changed in a single-tenancy module, then you must re-create your existing multitenant customer definitions. The reason for this is that changesin the module settings cannot be propagated automatically to existing definitions. Suchchanges are visible only in new customer definitions. Please see the next section, "Re-Creating Customer Definitions After an Upgrade with Changes in Module Settings".


15.1.3.5 Re-Creating Customer Definitions After an Upgrade with Changes in Module Settings

If settings are added, deleted or changed in the single-tenant version of a multitenant module, then youmust re-create your existing multitenant customer definitions. The reason for this is that in multitenancy,changes in the module settings cannot be propagated automatically to existing customer definitions.The procedure to follow for re-creating customer definitions when you make such a module upgrade is asfollows:1. Document and delete all existing customer definitions.2. Clear the Glassfish cache.

That is, delete the contents of the generated directory in the Glassfish directory structure:\glassfish4\glassfish\domains\PCE-PSM\generated.

3. Re-create each of the customer definitions of the affected module.

Example: If an upgrade of the TraceLink Order Export Multitenancy Module introduces a new setting, thenyou must re-create each of the customer definitions that you have previously set up for this module.In the new customer definitions, you can make any setting that is required for the new module parameter.Re-creating customer definitions is necessary even if the new module setting provides a suitable defaultvalue or does not need to be set in your case.

15.1.3.6 Rework Hierarchy Import

15.1.3.6.1 Overview

Orders usually have a certain lifecycle. In case of PLM/PSM a simple lifecycle could be that the order isinitially created, produced on a line using PLM and send out of the plant for distribution. As the order is onits way its original structure may be changed.Sometimes the order might need to return to the plant for rework. The purpose of the Rework HierarchyImport module is to enable this particular step in the lifecycle of an order.

15.1.3.6.2 Requirements

In order to use the Rework Hierarchy Import module the PSM must be installed in version 1.10 or later.

For further information regarding general PSM requirements, see the PSM Installation Guide chapter"Configuring Glassfish for Rework Hierarchy Import module".

15.1.3.6.3 Workflow

This chapter describes the general workflow during rework.

① The rework is always started at the PLM. It will create a copy of the original order. The rework process isstarted for the copied order by writing a message to the rework queue.

② PSM reads the rework queue and triggers the import for each message.


③ The Rework Hierarchy Import module executes the import of serial numbers and their hierarchy infor-mation from a level 4 system like SAP OER. The module validates the data in order to guarantee integrityand might abort the import if the imported data is not in the expected state.

④ Once the import is finished the PSM will write an answer to the rework response queue regardlesswhether the import was successful or not.

⑤ The PLM processes the answer from the rework response queue.

15.1.3.6.4 Configuration

The module provides some configuration options after you installed it. You find the options in PSM underSettings > Module Settings > Hierarchy Import Module.

Currently these options are:

Option DescriptionGet metadata URL The URL from which metadata will be imported.

Get hierarchy URL The URL from which hierarchy data will be imported.

User The user name used to connect to the URL if authentication is required. Canbe empty if no authentication is required.

Password The password used to connect to the URL if authentication is required. Can beempty if no authentication is required.

Timeout The hierarchy import can be a long lasting operation. This option determinesthe latency in seconds for the remote system to respond before the request iscancelled.

Rework order identifier The module distinguishes orders from Track-and-Trace (T) and End-to-End(E) orders. This option determines what AI in the processed order specifiesthe type of the order. For example if the value of the option is R89 the modulewill search for an order data with AI R89 on rank 0 and process it as eitherTrack-and-Trace or End-to-End depending on what value the order data has.For values other than T or E the import is aborted.

Hierarchy level AI The AI that represents the hierarchy level (HIERARCHY_LVL). This AI is used tomap SAP OER ranks to PSM/PLM ranks. For example if the order for whichthe hierarchy is imported contains an order data with the HIERARCHY_LVL AIon rank 4 and contains the value 7 this means that during hierarchy importSAP OER rank 7 is mapped to PSM/PLM rank 4.

Response target directory For debugging purpose. The target directory where the last sGTIN andhierarchy responses are stored as XML files in case of error. Older files will beoverwritten. For example C:\psm\hierarchyimport\

Metadata request method SOAP method to use when requesting metadata. This is visible in the WSDLfile of the SAP OER webservice.

Hierarchy request method SOAP method to use when requesting hierarchy data. This is visible in theWSDL file of the SAP OER webservice.

Request namespace Namespace used in SOAP requests. This is visible in the WSDL file of the SAPOER webservice.

See also2 Mapping ranks } Page 127

Mapping ranks

The L4 system may use other ranks than you use in PSM. The Rework Hierarchy Import module provides amapping for different ranks. For every mapped rank the order must contain order data with the AI that islisted in the Hierarchy level AI setting. The value of the order data must be the level 4 rank.For example, if you want to map the level 4 (SAP OER) rank 8 to the PSM rank 4, you define an order dataon rank 4 with the AI specified in the Hierarchy level AI setting and the value 8. This means if the ReworkHierarchy Import module receives SGTINs for this order then the HIERARCHY_LVL 8 is mapped to rank 4.


15.1.3.6.5 Logging

The module will log specific events to the PSM log entries table. Message codes that can occur are listed inthe table below.

Code Name Description92001 Import error General error code that is logged if no other known

error applies.

92002 Import succeeded Informational code that states that the hierarchy forthe order was successfully imported.

100100 Illegal order state The reworked order is in an illegal state. At the timeof writing only SENT and PENDING_REWORK arevalid states.

100101 Invalid hierarchy Ranks for children/parent order units do not match.For example a child order unit has the same rankas its parent order unit. Parent serial number ofchild does not match serial number of parent.

100102 Required order data missing Order has some order data missing for hierarchyimport. Required is Material number and batchnumber on rank 0.

100103 SOAP error General SOAP error. Maybe a connection problem tothe SOAP webservice, failed authentication,malformed XML in response etc..

100104 Export failed Could not (internally) export order from PSM to themodule for hierarchy import.

100105 XML parse error sGTIN's May occur if the XML with the requested sGTIN'scould not be processed.

100106 XML parse error hierarchy May occur if the XML with the requested hierarchydata could not be processed.

100107 Import failed General error code that is logged during import if noother known error applies.

100108 Extension mismatch Error code that is logged if the sGTIN responsecontains extensions that do not match order datavalues in the rework order.

100109 Unknown order type Import failed because the order was not a Track-and-trace (T) or End-to-end order (E).

100110 Extension missing This log indicates that hierarchy import was abortedbecause the metadata response did not contain allrequired SAP EPC Extensions. Required areHIERARCHY_LVL, BATCH_ID, EXPIRATION_DATE. Ifthe order is an end to end order CONTENT_QTY isrequired for serial numbers that start with (00).

100111 Hierarchy in E2E order This log indicates that hierarchy import was abortedbecause the hierarchy for the end to end ordercontained aggregations.

100112 Missing hierarchy mapping This log indicates that hierarchy import was abortedbecause the order does not contain a rankmapping. See chapter [Configuration } Page 127],Option 'Hierarchy level AI'.


15.1.3.7 Importing Serial Numbers

15.1.3.7.1 Importing Serial Numbers Automatically

Note: This section describes the procedure for importing serial numbers for a "normal" GTIN. For instructionson importing serial numbers for a "Russian" GTIN, please see [Import Serial Numbers } Page 90].To import serial numbers you must create a prodcode mapping. With this mapping you define whichmodule is responsible to import serial numbers for a prodcode and customer.

Prerequisites• Customers are already created. See also chapter [Creating a Customer Configuration } Page 124].• Product codes are available. See the PSM User Manual, chapter [Product Code Numbers } Page 79].

Procedure1 Go to Settings > System Settings > section import Serial Numbers.

2 In the section Prodcode Mapping table, select from the dropdown lists the combination of Productcode, module, and customer you want to create the mapping for.

3 Click Create Mapping.

Settings > System Settings > import Serial Numbers > section Prodcode Mapping table

ð The Product code mapping is created and inserted at the end of the table.ð With customer configurations and product code mappings provided, the PSM can run automatic serial

number imports via scheduler. For detailed instructions on configuring an automatic serial numberimport, refer to the PSM User Manual, chapter "[Module Trigger via Scheduler } Page 156]".

ExampleIn the example below, the module Multitenancy Tracelink SN Import will import serial numbers for theproduct codes shown using the customer configuration named mycustomer.

Settings > System Settings > import Serial Numbers

See also2 Importing Serial Numbers Manually } Page 130


15.1.3.7.2 Importing Serial Numbers Manually

Note: This section describes the procedure for importing serial numbers for a "normal" GTIN. For instructionson importing serial numbers for a "Russian" GTIN, please see [Importing Serial Numbers } Page 71].To start a manual serial number import:


ð The example below shows an import of a GTIN product code that uses the customer configurationnamed "Customer D" from the Multitenancy Tracelink SN Import Module.


2 Click Import.ð Serial Numbers are imported into the PCE Database. You can see/access the serial numbers at

Management > Serial Number Management > Serial Number Overview or Management > SerialNumber Management > Serial Number List Overview depending on what module and configurationwas used to import serial numbers.

See also2 Import Serial Numbers } Page 90

15.1.3.8 Exporting Orders

15.1.3.8.1 Exporting Orders Automatically

1 Go to Settings > Multi-tenancy Modules > <Multitenancy Module for order export>. For example youcan select the Multitenancy Tracelink Order Export, if installed.


2 Select the tab of the customer for which you want to define the customer configuration or create a newcustomer. See chapter [Creating a Customer Configuration } Page 124].

Example of customer configurations for Multitenancy Tracelink Order Export

3 Define all necessary module settings that are required for the order export and click save. For furtherinformation regarding the specific module settings, refer to the User Manual of the singletenancy module.

4 To assign a product to a customer configuration, go to Management > Product Management > editProducts and select an Owner Name that corresponds to the desired customer configuration name.


ð The owner name is saved in the product data in the AI R51.


5 Optional: you can edit the product owner name AI R51 in the Master Data form. See also [AIs withspecial behavior during export } Page 156].

Example of a product that is assigned to Customer A

6 To define which module installed in PSM is responsible for exporting the order, go to Management >Order Management > edit Orders and select the Destination Module.

Management > Order Management > edit Orders

ð The destination module is saved in the AI R50 in the order data. See also [AIs with special behaviorduring export } Page 156].

ð PSM can now run automatic multitenancy order exports. For detailed instructions on configuring anautomatic order export, refer to the PSM User Manual, chapter "[Module Trigger viaScheduler } Page 156]".

15.1.3.8.2 Exporting Orders Manually

To start a manual order export:

1 Open Management > Order Management > Export Order for Target Customer.


2 After a consistency check of the order you can select a multitenancy order export module and acustomer configuration from this module.ð In the example below the order will be exported using the customer configuration named "Customer

B" from the Multitenancy Tracelink Order Export Module:

Management > Order Management > Export Order for Target Customer.

3 Click Export.ð The order you selected is exported to the source that is identified by the settings in the customer configu-

ration of the selected module. In this example it is the customer configuration "Customer B" of the "Multi-tenancy Tracelink order export".


15.1.4 Generic XML Order and Product Import

NOTICEUpgrade this Module and Revise Product Definitions if You Upgrade to PSM1.14With PSM 1.14, AIs R09 (Line Format) and R10 (Line) in product definitions are replacedby AIs R90 (Default line for product) and R91 (Default line for product). Because of thischange, you should update this module to the newest release when you upgrade to PSM1.14. You should also review your product definitions. Wherever R09 and R10 are used,please replace them in the product definitions with R90 and R91. See the moduledocumentation for conversion scripts.

15.1.4.1 Generic XML Order Import

The Generic XML Order Import module is used to import orders from any valid XML document either bysending them to the PSM via HTTP POST request or by placing them in a defined "hot folder."


To open the module settings, go to Settings > Module Settings > Generic XML Order Import. In thecolumn "Value" you can find an example for the XPATH_Mapping.

OptionsThe form contains the following options:• XPATH_Mappings

This option contains the configuration that is used to map parts of the imported XML document specifiedby XPath (XML Path Language) expressions to the order.

• StrictThis option determines whether mappings defined in the XPATH_Mappings option can be optional ornot. If this option is activated, the imported XML document must contain values for all mappings definedunder XPATH_Mappings. Otherwise the operation is aborted, and the import of the XML file fails. If theoption is unchecked or deactivated, the module is more forgiving and will import of the XML file even if itonly contains a subset of data that match the mappings defined.

• Prioritize Line Format from ProductThis setting controls how an imported order is assigned to a line and line format. These assignmentscan come from either the product, if any, defined in an order with R07 or from assignments madedirectly in the order XML.Please note that this setting has been changed with the newest release of PSM (1.14.1) and Version2.1 of the module to correct problems with line and line format assignments that were occurring if theproduct data contains R09 (Line format) or R10 (Line). R09 and R10 are no longer permitted to bedefined in products and are ignored if present. Instead, R90 (Default line of product) and R91 (Defaultline format of product) are offered when you define a product.At order import, the line and line format assignments for an order are resolved as follows:

– If Prioritize Line Format from Product is activated, then the module looks for a default line (R90)and line format (R91) in the product cited in R07 in the order XML. If R90 (Default Line) is found inthe product, then any R10 setting in the order is ignored. If R91 (Default Line Format) is found in theproduct, then any R09 setting in the order is ignored.

If the line or line format assignment is missing in the product, then the missing assignment is takenover from the order definition, if the missing assignment is available there.

– If Prioritize Line Format from Product is not activated, then the module looks for line (R10) andline format (R09) assignments in the order XML. If R10 (Line) is found in the order, then any R90setting in the product is ignored. If R09 (Line Format) is found in the order, then any R91 setting inthe product is ignored.

If the line assignment is missing in the order XML, then the order is assigned to the line from theproduct definition. If the product definition also specifies a line format, then this is also used inpreference to any line format specified in the order XML.If the line format assignment is missing from the order XML, then the order is assigned to the lineformat from the product.


If the order specifies a line format that does not exist in PSM, then the order is assigned to the lineformat in the product definition.

– If the line assignment remains unresolved, then the order is imported with the status CREATED; noline assignment is made.

– If the line format element does not specify a value (intentionally left empty), then the order isimported with a warning message written to the audit log. The message text: Order xxx importedwithout a lineFormat.

– If the line assigned to the order does not exist in PSM, then the order import is rejected.

– If the line format does not exist in PSM, then the order import is rejected. Message text: LineFormatxxx is invalid/deactivated for line xxxxx. Deactivated line formats are considered to be non-existentfor purposes of the order import.

Note: If you would like to convert existing product definitions to use R90 and R91 instead of R09 andR10, please see the appendix of this user manual.

• Archive FolderIf this setting is active, checked and contains a valid path, the module will write or transfer the XMLDocument to the specified path after the import operation is completed.Example:C:\temp\import\idocs\

• Import FolderThis setting will contain a path which serves as a "hot folder" for XML files that are to be imported by themodule. By default, all valid XML files found inside this folder will be imported after doing a manualimport through PSM or by activating the order import scheduler. This option provides an easier alter-native to the traditional way of importing XML files through an HTTP POST request.

• Filename PatternThis setting contains text that serves as a filter for XML files that are to be imported from the hot folderdefined by the setting "Import Folder." If this setting is empty or inactive, the default behav-ior of the hotfolder is to import all valid XML files contained therein. If the "Filename Pattern" setting is active andcontains a value, only valid XML files whose filenames contain the specified text will be imported.

• Prioritize Data from ProductSimilar to the setting "Prioritize Line Format from Product", this setting allows conflict resolution if thesame data is found on the import XML file and a corresponding product (via mapping AI R07 – ProductName) already existing on PSM. If this setting is active and checked, the value of the product data fromPSM overrides the value indicated on the XML file. Otherwise, the order data value from the XML file isimmediately assigned to the imported order.

• Order status after importThe default status of the order after import is ASSIGNED or CREATED but you can define another statushere, like READ_ONLY. Orders in status READ_ONLY are not visible in PLM. Note that this option isoffered only in a special customer-specific version of this module, not in the generic product module.

For further information on the configuration, see chapter [Sample Configuration for Order Import (StaticMode) } Page 136].For further information on date formats, see chapter [Specifying Date Formats } Page 142].


After configuring the options, click save.

Sample Configuration for Order Import (Static Mode)

Importing the sample XML document with the specified configuration will create an order with the name"AO010320171139" and description "Special order from secret customer.". The order will also containorder data with AI R07 on rank 0 with the value PA2342, AI 17 on rank 0 with the value 2022-01-01(because dates are always converted to yyyy-MM-dd format) and AI 01 on rank 1 with the value18375637564737.<?xml version="1.0" encoding="UTF-8"?>

<order><id>19293847235</id><name>AO010320171139</name><description>Special order from secret customer.</description><product><id>86757439</id><name>PA2342</name><exp>01-01-2022</exp><gtin>18375637564737</gtin></product></order>

XPATH_MappingThe order should be imported with its name, description as well as AIs R07 (product), 17 (expiry date),and 01 (GTIN). A possible value for the option XPATH_Mappings is:<?xml version="1.0"?>

<XPATHMappings><mappings>


<mapping><ai>R08</ai><xpath>/order/name/text()</xpath><rank>0</rank></mapping><mapping><ai>R16</ai><xpath>/order/description/text()</xpath><rank>0</rank></mapping><mapping><ai>R07</ai><xpath>/order/product/name/text()</xpath><rank>0</rank></mapping><mapping sourceDateFormat="dd-MM-yyyy"><ai>17</ai><xpath>/order/product/exp/text()</xpath><rank>0</rank></mapping><mapping><ai>01</ai><xpath>/order/product/gtin/text()</xpath><rank>1</rank></mapping></mappings></XPATHMappings>

The tag xpath can contain any XPath expression for the supported XPath version. The supported XPathversion is determined by the Java version.

Sample Configuration for Order Import (Dynamic Mode)

The following sample XML is used to import the order:<?xml version="1.0" encoding="UTF-8"?>

<order> <id>19293847235</id><name>AO010320171139</name><description>Dynamic order from secret customer.</description><custom1>Custom Data For Template 1</custom1><custom2>Custom Data For Template 2</custom2><custom3>Custom Data For Template 3</custom3><product><id>86757439</id><name>PA2342</name><exp1>01-01-2021</exp1><exp2>01-01-2022</exp2><exp2>01-01-2023</exp2><gtin>18375637564737</gtin></product></order>

XPATH_Mappings TemplateThe order should be imported with its name, description as well as AIs R07 (product), 17 (expiry date),and 01 (GTIN). A possible value for the option XPATH_Mappings is:<?xml version="1.0"?>

<XPATHMappings><mappings><mapping><ai>R08</ai><xpath>/order/name/text()</xpath><rank>0</rank></mapping><mapping><ai>R16</ai><xpath>/order/description/text()</xpath><rank>0</rank></mapping><mapping><ai>R07</ai>


<xpath>/order/product/name/text()</xpath><rank>0</rank></mapping><mapping><ai>01</ai><xpath>/order/product/gtin/text()</xpath><rank>1</rank></mapping><mapping><ai>X100</ai><xpath>/order/custom${customDataIndex}/text()</xpath><rank>1</rank></mapping><mapping sourceDateFormat="dd-MM-yyyy"><ai>17</ai><xpath>/order/product/${expIndex}/text()</xpath><rank>1</rank></mapping></mappings></XPATHMappings>

XPath for Product/order/product/name/text()

Template Maps<Templates>

<Template id="1"><var name="customDataIndex" value="1"/><var name="expIndex" value="exp1"/></Template><Template id="2"><var name="customDataIndex" value="2"/><var name="expIndex" value="exp2"/></Template><Template id="3"><var name="customDataIndex" value="3"/><var name="expIndex" value="exp3"/></Template></Templates>

Product AI for Template IDX41

ResultsIf the product named PA2342 has AI X41=2, the resulting order has the following properties:

Order Name: AO010320171139

Order Description: Dynamic order from secret customer.

Product Name: PA2342

GTIN (Rank 1): 18375637564737

X100: Custom Data For Template 2

Expiry Date: 01-01-2022The red values are the ones substituted with values from the template map.

Special AIs for Order Import

Usually values for mappings defined under XPATH_Mappings are mapped 1:1 to order data. For example, ifthe tag <mappings> for the order import contains the following mapping, the imported order will containan order data with AI 01 (GTIN), rank 1 and the value specified by the XPath expression.<mapping>

<ai>01</ai><xpath>order/gtin/text()</xpath>


<rank>1</rank></mapping>

But for some AIs there is special treatment. In the order import:• AI R08 maps to the order name• AI R16 maps to the description of the order• AI R07 has special behavior if the configuration option 'prioritizeLineFormatFromProduct' is activated.

Please see [Configuration } Page 134].You can map constant values to AIs through the tag <value>.

15.1.4.1.2 HTTP Post request

The generic XML Order Import module processes XML documents received by HTTP POST requests. Afterdefining the XPATH_Mapping, send an order from a HTTP-Client (ERP or other) to PSM. The URL for theorder import is:http://[hostname]:8080/[contextRoot]/orderImportServletThe contextRoot is assigned on application deployment. You can verify the contextRoot in the admin-istration console of your application server. In case of PSM it will usually be psm. The webservice willrespond with HTTP Codes 200 OK if the order import was successful or otherwise with 500 Internal ServerError.After processing, the imported order will have the name defined in the XPATH_Mapping for AI R08 and willbe listed under Management > Order Management > edit Orders.

Message CodesThe following message codes and audit trail entries can be generated by this module:

Message Code Name Type Description95014 Order import successful INFO Message generated if the

order import succeeded

95015 Order import failed ERROR Message generated if theorder import failed

15.1.4.1.3 Importing through a "Hot Folder"

The generic XML Order Import module can also process XML documents by placing them in a "hot folder"defined by the setting "Import Folder." By default, the module will import all valid XML files foundimmediately within this folder (subfolders are not searched). You can provide a filter for these XML files byactivating and placing a value on the module setting "Filename Pattern" and as such, only XML filescontaining the pattern in their filename will be imported.After processing the XML files, the module will move them to the folder defined by the module setting"Archive Folder" if activated. This allows you to refer back to the original source file for the order. You mayalso notice that XML files that have been processed by the module will change their file extensions from".xml" to ".xm_"After processing, the imported order will have the name defined in the XPATH_Mapping for AI R08 and willbe listed under Management > Order Management > Orders.

15.1.4.2 Generic XML Product Import

The Generic XML Product Import module can be used to import products from any valid XML documenteither by sending them to the PSM via HTTP POST request or by placing them in a defined "hot folder".


To open the module settings, go to Settings > Module Settings > generic XML ProductImport.

OptionsThe form contains the following options:• XPATH_Mappings

This option contains the configuration that is used to map parts of the imported XML document specifiedby XPath (XML Path Language) expressions to the product.

• Strict


This option determines whether mappings defined in the XPATH_Mappings option can be optional ornot. If this option is activated, the imported XML document must contain values for all mappings definedunder XPATH_Mappings, otherwise the operation is aborted and the import of the XML file fails. If theoption is un-checked or deactivated, the module is more forgiving and will import of the XML file even ifit only contains a subset of data that match the mappings defined.

• Archive FolderIf this setting is active, checked and contains a valid path, the module will write or transfer the XMLDocument to the specified path after the import operation is completed.Example:C:\temp\import\idocs\

• Import FolderThis setting will contain a path which serves as a "hot folder" for XML files that are to be imported by themodule. By default, all valid XML files found inside this folder will be imported after doing a manualimport through PSM or by activating the product import scheduler. This option provides an easier alter-native to the traditional way of importing XML files through an HTTP POST request.

• Filename PatternThis setting will contain text which will serve as a filter for XML files that are to be imported from the hotfolder defined by the setting "Import Folder." If this setting is empty or inactive, the default behav-ior ofthe hot folder is to import all valid XML files contained therein. If the "Filename Pattern" setting is activeand contains a value, only valid XML files whose filenames contain the specified text will be imported.

For further information on the configuration, see chapter [Example Configuration for ProductImport } Page 140].For further information on date formats, see chapter [Specifying Date Formats } Page 142].

After configuring the options, click save.

Example Configuration for Product Import

The following example XML document should be imported as a product:<?xml version="1.0" encoding="UTF-8"?>

<product><id>19293847235</id><name>P010320171140</name><description>Special product from secret customer.</description><exp>01-01-2022</exp><gtin>18375637564737</gtin></product>

XPATH MappingThe product is imported with its name, description as well as AIs 17 (expiry date) and 01 (GTIN). Apossible value for the option XPATH_Mappings is:<?xml version="1.0"?>

<XPATHMappings><mappings><mapping><ai>R07</ai><xpath>/product/name/text()</xpath><rank>0</rank></mapping><mapping><ai>R11</ai><xpath>/product/description/text()</xpath><rank>0</rank></mapping><mapping sourceDateFormat="dd-MM-yyyy"><ai>17</ai><xpath>/product/exp/text()</xpath><rank>0</rank></mapping><mapping><ai>01</ai><xpath>/product/gtin/text()</xpath><rank>1</rank>


</mapping></mappings></XPATHMappings>

The tag xpath can contain any XPath expression for the supported XPath version. The supported XPathversion is determined by the Java version.Importing the sample XML document with the specified configuration will create a product with the name"P010320171140" and description "Special product from secret customer.". The product will also containproduct data with AI 17 on rank 0 with the value 2022-01-01 (because dates are always converted toyyyy-MM-dd format) and one with AI 01 on rank 1 with the value 18375637564737.

Special AIs for Product Import

Usually values for mappings defined under XPATH_Mappings are mapped 1:1 to product data.But for some AIs there is special treatment. In the product import:• AI R07 maps to the product name• AI R11 maps to the description of the product

15.1.4.2.2 HTTP Post request

The generic XML Product Import module processes XML documents received by HTTP POST requests. Afterdefining the XPATH_Mapping, send a product from an HTTP-Client (ERP or other) to PSM. The URL for theproduct import is:http://[hostname]:8080/[contextRoot]/productImportServletThe contextRoot is assigned on application deployment. You can verify the contextRoot in the admin-istration console of your application server. In case of PSM it will usually be psm. The webservice willrespond with HTTP Codes 200 OK if the product import was successful or otherwise with 500 InternalServer Error.

After processing, the imported product will have the name defined in the XPATH_Mapping for AI R07 andwill be listed under Management > Product Management > edit Products.

Message CodesThe following message codes and audit trail entries can be generated by this module:

Message Code Name Type Description95016 Product import successful INFO Message generated if the

product import succeeded

95017 Product import failed ERROR Message generated if theproduct import failed

15.1.4.2.3 Importing through a "Hot Folder"

The generic XML Product Import module can also process XML documents by placing them in a "hot folder"defined by the setting "Import Folder." By default, the module will import all valid XML files foundimmediately within this folder (subfolders are not searched). You can provide a filter for these XML files byactivating and placing a value on the module setting "Filename Pattern" and as such, only XML filescontaining the pattern in their filename will be imported.After processing the XML files, the module will move them to the folder defined by the module setting"Archive Folder" if activated. This allows you to refer back to the original source file for the order. You mayalso notice that XML files that have been processed by the module will change their file extensions from".xml" to ".xm_"After processing, the imported order will have the name defined in the XPATH_Mapping for AI R07 and willbe listed under Management > Product Management > edit Products.


15.1.4.3 Specifying Date Formats

When you map to a date AI, specify the attribute sourceDateFormat in the mapping tag. The exampleXPATH_Mapping maps a date to the AI 17 (expiration date). See chapter [Sample Configuration for OrderImport (Static Mode) } Page 136].<mapping sourceDateFormat="dd-MM-yyyy">

<ai>17</ai><xpath>/order/product/exp/text()</xpath><rank>0</rank></mapping>

The attribute sourceDateFormat imports the date format in the XML document as dd-MM-yyyy (e.g.20-12-2018). Internally, dates are converted to the format yyyy-MM-dd.

15.1.4.4 Appendix

The provided XML schema definition describes the XML structure that can be used in the XPATH_Mappingssetting.

15.1.4.4.1 Schema for Acceptable Content of XPATH Mappings Template<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"xmlns:xs="http://www.w3.org/2001/XMLSchema">

<xs:element name="XPATHMappings"><xs:complexType><xs:sequence><xs:element name="mappings"><xs:complexType><xs:sequence><xs:element name="mapping" maxOccurs="unbounded" minOccurs="0"><xs:complexType><xs:sequence><xs:element type="xs:string" name="ai"/><xs:element type="xs:string" name="xpath"/><xs:element type="xs:integer" name="rank"/></xs:sequence><xs:attribute type="xs:string" name="sourceDateFormat" use="optional"/></xs:complexType></xs:element></xs:sequence></xs:complexType></xs:element></xs:sequence></xs:complexType></xs:element></xs:schema>

15.1.4.4.2 Schema for Acceptable Content of Template Maps<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified"xmlns:xs="http://www.w3.org/2001/XMLSchema">

<xs:element name="Templates"><xs:complexType><xs:sequence><xs:element name="Template" maxOccurs="unbounded" minOccurs="1"><xs:complexType><xs:sequence><xs:element name="var" maxOccurs="unbounded" minOccurs="1"><xs:complexType><xs:attribute name="name" type="xs:string" use="required"/><xs:attribute name="value" type="xs:string" use="required"/></xs:complexType></xs:element></xs:sequence><xs:attribute name="id" type="xs:string" use="required"/></xs:complexType></xs:element></xs:sequence></xs:complexType>


</xs:element></xs:schema>

15.1.4.4.3 Upgrading to PSM 1.14 and Module Version 2.1: Default Line and Line Format

BackgroundDefining the line and line format to which an order is assigned by assigning the AIs R09 and R10 in theproduct has led to issues in the past and bears the risk of inconsistent assignments (line format can have alink to a product, which is linked to a different line format).For that reason, the new AIs R90 and R91 have been introduced that define the default line formatrather than the actual line format.Line and line format will continue to be mapped using R09 and R10 in the XPath Mappings of the order-import, but depending on the other modulesettings, the default data can be prioritized or used as a fallback,if no valid lineformat is found in the order-xml.This document describes the adaptations that need to be made to the PCE database to benefit from the newfeature, introduce the new AIs and migrate all R09/R10 assignments in product data to R91/R90assignments.As the steps taken here are performed using a database tool, they are not recorded in the audit trail andshould be documented by screenshots and/or database extracts properly.

Conversion Instructions1. Perform the script

select * from tbl_products p inner join tbl_productdata pd on p.id=pd.id_product where pd.str_ai in('R10','R09')Document the result appropriately (e.g. screenshots, or by copying the resulting table with headers intoan excel-tab for documentation of the before state).

2. Insert the new AIs into the database (done by Schema 2.3 upgrade scripts – see also the explanationsafter these scripts):INSERT INTO tbl_ai (str_ai, int_sort, str_name, str_description, int_length_min, int_length_max,str_type, str_default_type_format, bit_static, bit_valid, i16_fixrank) VALUES('R90', 0, 'DEFAULT LINEPRODUCT', 'Default line a product gets assigned to if not specified in order', 0, 64, 'STRING', 'x..64', 1,1, 0);INSERT INTO tbl_ai (str_ai, int_sort, str_name, str_description, int_length_min, int_length_max,str_type, str_default_type_format, bit_static, bit_valid, i16_fixrank) VALUES('R91', 0, 'DEFAULT LINEFORMAT PRODUCT', 'Default line format a product gets assigned to if not specified in order', 0, 64,'STRING', 'x..64', 1, 1, 0);These 2 statements are also part of the DB upgrade scripts insert_DEFAULT.sql, insert_MSSQL.sql andinsert_ORACLE.sql for PLM 4.19, so once these scripts have been executed it is already done. Clientsremaining on less than PLM 4.19, but upgrading to PSM 1.14 and psm-m-xmlimportxpath 2.1 mustexecute them manually, as they won’t use the DB upgrade scripts provided with PLM 4.19.

3. Document successful execution with a screenshot, or by checking the new entries:select * from tbl_ai where str_ai in ('R90', 'R91')Either replace all R10 entries in products by R90 entriesupdate tbl_productdata set str_ai = 'R90' where str_ai = 'R10';

4. Or create new R90 entries while keeping the old R10 entriesinsert into tbl_productdata(id_product, str_ai, str_type_format, i16_boxingrank, str_value, bit_readonly)select id_product, 'R90', str_type_format, i16_boxingrank, str_value, bit_readonly from tbl_productdatawhere str_ai = 'R10';Either replace all R09 entries in products by R91 entriesupdate tbl_productdata set str_ai = 'R91' where str_ai = 'R09';

5. Or create new R91 entries while keeping the old R09 entriesinsert into tbl_productdata(id_product, str_ai, str_type_format, i16_boxingrank, str_value, bit_readonly)select id_product, 'R91', str_type_format, i16_boxingrank, str_value, bit_readonly from tbl_productdatawhere str_ai = 'R09';


The Replace-option is the preferred one (as it doesn’t leave unneeded entries in the DB), it howevercan’t be prepared in advance. So the necessary sequence here is “Stop using old PSM/Connectorversions ==> Deploy the new versions ==> Do the updates ==> Start using new PSM/Connectorversions”. If for any reason a switch back to the old PSM/Connector version should become necessarythen the updates must be made in the backward direction.The option of creating new additional entries allows to do the DB manipulations in advance and switchbetween old/new PSM/Connector versions at any time.Document successful execution by a screenshot, or by selecting all updated/changed products:select * from tbl_products p inner join tbl_productdata pd on p.id=pd.id_product where pd.str_ai in('R10','R09')This query should yield no results if the Replace-option has been applied, it should give the sameresults as initially otherwise.select * from tbl_products p inner join tbl_productdata pd on p.id=pd.id_product where pd.str_ai in('R90','R91')This query should list the same products as initially documented for R10/R09.Changing the XPath Mapping of the orderimport connector is not required.


15.1.5 Arvato MAH

15.1.5.1 Overview

Arvato describes an XML-based format for structuring and describing physical objects. It is used toexchange production information between IT-systems. The Arvato Order Import Module imports work ordermaster data including serial numbers into the PSM database to be produced/consumed from PLM. TheOrder Export Module generates XML files for the produced work order and exports them via sFTP.To trigger the automatic order import as well as the order export, see chapter [Module Trigger viaScheduler } Page 156].

15.1.5.2 General Settings

General import and export settings are described in the PSM User Manual, chapter "System Settings".

15.1.5.3 Specific Module Settings

Specific Arvato Module settings can be edited in the PSM Menu under Settings > Module Settings. Thesesettings describe the tags generated in the Arvato message and their values.

Order ImportSending/receiving partner ID, sFTP url, sFTP Username/password, incoming remote directory are infor-mation provided from Arvato. The incoming remote directory must be set to the subfolder From_csdbsFTP.


Order ExportBy setting the sender, note that the sending and receiving COM partner ID must be inverted unlike the orderimport settings. All other settings are the same like the order import. The outgoing remote directory must beset to the subfolder to_csdb sFTP.


15.1.6 Arvato CMO

15.1.6.1 Overview

An order export and import connector exists for Arvato CSDB, wherein PSM is able to import an order fromArvato CSDB along with the serial numbers provisioned, and in return PSM can export the same order backto Arvato CSDB along with the serial numbers and aggregation hierarchies, if any exist.Often the order is defined and initiated on the line and therefore defining the order in Arvato CSDB andimporting it before production starts is not possible. So there is a need to support a workflow that allows theArvato CSDB to recognize orders initiated from an external party or system.This workflow is supported by Arvato by providing interfaces and standard XML formats for the following:• Serial Number Request and Provision (3-step process)

– Sending a Serial Number Request Document (VS-009)– Importing a Serial Number Response Provision Document (VS-010)– Sending a Serial Number Import Acknowledgment File (VS-011)

• Production Order Export (2-step process)– Sending a Production Order Document (VP-062)– Importing a Production Order Import Acknowledgment File (VP-063)

This process assumes that enough serial numbers are imported from the Arvato CSDB system prior toproduction, and that those provisioned serial numbers by Arvato will be the same serial numbers consumedduring production until it finishes and becomes ready for export. All communication with Arvato CSDB isdone through a SFTP Gateway server.

See also2 Module Trigger via Scheduler } Page 156

15.1.6.2 Installation

15.1.6.2.1 Prerequisites

• Properly installed PSM• Two jar files for cryptography library (BouncyCastle ver. 1.56) used for secure communication with the

FTP server:– bcpkix-jdk15on-1.56.jar– bcprov-jdk15on-1.56.jar

• Jar files for the singletenancy modules (also required for multitenancy scenarios):– psm-m-arvato-snimport_onejar-<version>.jar– psm-m-arvato-lineorderexport_onejar-<version>.jar

• For multitenancy installations, the jar files for the multitenancy functionality are required on top of thesingletenancy installation:– psm-m-arvato-snimport-multitenancy-<version>.jar– psm-m-arvato-lineorderexport-multitenancy-<version>.jar

15.1.6.2.2 Procedure

1 Stop the GlassFish service.2 Copy all four jar files to this folder:

ð <GLASSFISH_HOME>/glassfish/glassfish/domains/<domain_name>/applications/<psm_folder>/WEB-INF/lib

3 Delete all contents of these folders:ð <GLASSFISH_HOME>/glassfish/glassfish/domains/<domain_name>/generatedð <GLASSFISH_HOME>/glassfish/glassfish/domains/<domain_name>/autodeployð <GLASSFISH_HOME>/glassfish/glassfish/domains/<domain_name>/osgi-cacheð <GLASSFISH_HOME>/glassfish/glassfish/domains/<domain_name>/logs --> back-up before

deleting if you need old logs4 Start the GlassFish service.


15.1.6.2.3 Verification

After logging in to PSM, go to Settings > System Settings, expand the System Information section, andyou should see the following entries:

Note that this screenshot is just an example to show the modules installed. Details, like versions, in your systemsettings may vary.

15.1.6.3 General Settings

General import and export settings are described in the PSM User Manual, chapter "System Settings".

15.1.6.4 Specific Module Settings

Specific Arvato Module settings can be edited in the PSM Menu under Settings > Module Settings. Thesesettings describe the tags generated in the Arvato message and their values.

NOTICEFilename PatternFor the Filename Pattern settings, Arvato has a specification document. The defaultsettings are intended for communication with Arvato CSDB through a gateway.

15.1.6.4.1 Serial Number Import

Setting Description Sample ValueSender ID Sending Com Partner ID 1026FP01

Receiver ID Receiving Com Partner ID 56285670000000

SFTP Host IP address or DNS name of theArvato SFTP Gateway

transfergate.de

SFTP Port Number Port number for the SFTP service(default: 22)

22

SFTP Username Username for SFTP access csdb_dev_pce

SFTP Password Password for SFTP access the_password

Outgoing Remote Directory Directory on the SFTP server whereyou expect to upload VS-009 (SNRequest) and VS-011 (Acknowl-edgment) files

/to_csdb


http://transfergate.de/

Setting Description Sample ValueIncoming Remote Directory Directory on the SFTP server where

you expect to receive VS-010 (SNProvision) files

/from_csdb

Max retries for SN provisionresponse

Maximum number of times theconnector will try to find aresponse to a previously sentserial number request (default: 5times)

5

Second(s) between retries for SNprovision response

Second(s) between checks forresponses (default: 120,minimum: 5)

180

Asynchronous SN provision Allow the connector to sendanother request before the currentrequest's provision is available.This allows the scheduler toprocess SN requests in quickersuccession but the serial numbersimported may not be immediatelyvisible on the UI.

unchecked

Delete local message after upload Delete local copies of VS-009 andVS-011 after uploading them tothe SFTP server.(For a production environment, itis best to check this because filesaccumulate over time and maychoke the PSM host's file system.Disable this only for debuggingpurposes).

checked

Delete provision file afterprocessing

Delete local and remote copies ofVS-010 from the SFTP server afterprocessing.(For a production environment, itis best to check this because filesaccumulate over time and maychoke the PSM host's file system.Disable this only for debuggingpurposes).

checked

Temporary folder for downloading/uploading VS files

Temporary folder for downloading/uploading VS files. (e.g.C:PSMTEMP).This must be a writable folder onthe GlassFish host machine.

C:\PSM\Arvato\Temp

VS-009 Filename Pattern Portion of the file name thatidentifies a VS-009 file to theCSDB server

-CSDB_VS009_Gateway-

VS-010 Filename Pattern Portion of the file name thatidentifies a VS-010 file to themodule

-Gateway_VS010_CSDB-

VS-011 Filename Pattern Portion of the file name thatidentifies a VS-011 file to theCSDB server

-CSDB_VS011_Gateway-

15.1.6.4.2 Order Export

Setting Description Sample ValueSender ID Sending Com Partner ID 1026FP01


Setting Description Sample ValueReceiver ID Receiving Com Partner ID 56285670000000

SFTP Host IP address or DNS name of theArvato SFTP Gateway

transfergate.de

SFTP Port Number Port number for the SFTP service(default: 22)

22

SFTP Username Username for SFTP access csdb_dev_pce

SFTP Password Password for SFTP access the_password

Outgoing Remote Directory Directory on the SFTP server whereyou expect to upload VP-062(Production Order Export)

/to_csdb

Incoming Remote Directory Directory on the SFTP server whereyou expect to receive VP-063(Order Export Acknowledgment)files

/from_csdb

Max retries for checking anacknowledgment response

Maximum number of times theconnector will try to find anacknowledgment file for anexported order (default: 5 times)

5

Second(s) between retries for anacknowledgment response

Second(s) between checks foracknowledgment files (default:120, minimum: 5)

180

Asynchronous order exportacknowledgment

Allow the connector to exportanother order before the currentorder's acknowledgment filebecomes available. This allowsthe scheduler to export orders inquicker succession but the orderstate (sent or failed) will not be setuntil the acknowledgment file isreceived later.

unchecked

Delete local message after upload Delete local copies of VP-062 andVP-063 files after uploading themto the SFTP server. (For aproduction environment, it is bestto check this because filesaccumulate over time and maychoke the PSM host's file system.Disable this only for debuggingpurposes).

checked

Delete acknowledgment file afterprocessing

Delete local and remote copies ofVP-063 files from the SFTP serverafter processing (For a productionenvironment, it is best to checkthis because files accumulate overtime and may choke the PSMhost's file system. Disable thisonly for debugging purposes).

checked

Temporary folder for downloading/uploading VS files

Temporary folder for downloading/uploading VS files. (e.g.C:PSMTEMP). This must be awritable folder on the GlassFishhost machine.

C:\PSM\Arvato\Temp

VP-062 Filename Pattern Portion of the file name thatidentifies a VP-062 file to theCSDB server

-CSDB_VP062_Customer-


http://transfergate.de/

Setting Description Sample ValueVP-063 Filename Pattern Portion of the filename that

identifies a VP-063 file to themodule

-Gateway_VP063_CSDB-

15.1.6.4.3 Required AIs for Exporting an Order

The following are the minimum AIs that an order must have in order to be exported. Without these AIs, theorder export will fail. If the values for these AIs are not expected to change between orders, it is recom-mended to add these AIs as product data so that the order will inherit the default AIs and correspondingvalues when the order has been assigned to a Line Format that is associated with that product.

AI Rank Description10 0 Batch / Lot. Number

11 0 Production Date. Format : YYYY-MM-dd

17 0 Use By or Expiry Date. Format:YYYY-MM-dd

R06 0 Production Quantity. The totalnumber of units required to beproduced by this order

R07 0 Product Name. The name of theproduct produced. IMPORTANT:This must exactly match theProduct ID defined on ArvatoCSDB.

01 / 9N / R25 / CH03 Variable GTIN / PPN / SSCC PREFIX / CHINASUBTYPE. The applicable productcode to identify the producedproduct at every rank.Note that for some of these likeSSCC PREFIX, supporting AIs alsoneed to be added such as SSCCCOMPANY PREFIX (R05) andSSCC PACK ID (R04) tocompletely identify the product onArvato CSDB.


15.1.7 The MDLP Connector

15.1.7.1 Overview

The MDLP Connector is a multitenant module for doing either of the following:• Importing both serial numbers and crypto-codes and keys from the MDLP system of the CRPT (Center

for Research on Perspective Technologies) in the Russian Federation. The CRPT is the provider of crypto-codes and keys for production for the Russian Federation.In this case, the MDLP Connector is the only module to enter for a particular "Russian" GTIN in theProdcode Mapping table in the System Settings > import Serial Numbers. (A "Russian" GTIN is anitem-rank GTIN that has been declared to be for production for the Russian Federation market. No entryis needed in the CTC-GTIN Mapping Table.

• Importing crypto-codes and keys for a list of serial numbers that have already been imported by anotherserial number import module.

In this case, enter MDLP Connector in the CTC-GTIN Mapping Table, as a companion entry to the SNimport module in the Prodcode Mapping table.

Operation with the Automatic Serial Number Import JobThe automatic job for importing serial numbers uses the entries that you make in the Prodcode Mappingtable and in the CTC-GTIN Mapping Table. (Entries in the CTC-GTIN Mapping Table are necessary only ifthe MDLP Connector is working together with a separate serial number import module, as describedabove.)If there are entries in both tables, then the serial number import module is executed by the job first. Then,the MDLP Connector is started for the same "Russian" GTIN. The customer does not need to start the MDLPConnector separately from the SN import module.After the serial number import module has imported serial numbers, the MDLP Connector reads in the list ofserial numbers of the "Russian GTIN" for which no crypto-code is available and for which no request forcrypto-codes is pending. The number of serial numbers that the MDLP collects for a request is limited by theSplitting Size. If the Splitting Size is smaller than the number of eligible serial numbers, then the MDLPConnector will not request crypto-codes for all of the eligible serial numbers. Coordinating the number ofserial numbers requested and the Splitting Size of the MDLP Connector is therefore a good idea to avoid alag in making imported serial numbers available for production.Because generating crypto-codes is time-consuming, the MDLP Connector operates asynchronously. Thatis, the response from MDLP to a request for serial numbers and crypto-codes or for crypto-codes alone is aUUID that identifies the request, not the SNs and crypto-codes. The finished crypto-codes and serialnumbers are imported in later, in a follow-up request. The follow-up request using the UUID is managedand run by the Polling Requests Scheduler, in the System Settings.

Operation in Manual Serial Number ImportsIf you use Management > Serial Number Management > import Serial Numbers, then you set themodules to use for the import by hand. The mapping tables are not used. Extra fields are opened for a"Russian" GTIN so that you can enter both a serial number import module and the MDLP Connector orsome other module for importing crypto-codes and keys.Other aspects of the operation of the MDLP Connector are as described in the section above.

MultitenancyFor a description of multitenancy in the MDLP Connector, please see the multitenancy[Overview } Page 122].

15.1.7.2 Requirements

The MDLP Connector is supported as of PSM Release 1.14.You must register and obtain a login from the CRPT in order to request crypto-codes and keys.

15.1.7.3 Configuration

To open the configuration settings for the MDLP Connector, select Settings > Multi-tenancy Modules >MDLP Connector.


Since the MDLP Connector is a multitenant module, you can define a different configuration for eachcustomer that you create.

Configuration Settings: MDLP Connector

The table below describes these settings.

Setting Use NotesAPI URL The URL of the API offered by the

MDLP system for obtaining crypto-codes and keys. The same APIcan be used for requesting crypto-codes and keys (CTCs) for serialnumbers that have already beenimported or for serial numbers andcrypto-codes and keys from theCRPT (Center for Research inProspective Technologies). TheCRPT is the organization in theRussian Federation that isresponsible for providing crypto-codes and keys and, optionally,serial numbers.

You must obtain the URL from theCRPT.

OMS ID The user ID provided to you uponregistration with the CRPT.

You obtain the OMS ID and ClientToken upon registration with theCRPT.Client Token The client token that is provided to

you upon registration with theCRPT. The token is used toauthenticate your requests to theMDLP.


Setting Use NotesSplitting Size The maximum number of serial

numbers for which the MDLPConnector makes a request.If you are using the MDLPConnector to get both serialnumbers and cryto-codes andkeys from the CRPT, then this isthe maximum number of serialnumbers / CTCs that the MDLPConnector will request in a singlecall.If you are using the MDLPConnector to get CTCs for serialnumbers that have already beenimported, then this is themaximum number of serialnumbers that the Connector willselect from the database for asingle call. If the number of serialnumbers you have imported isgreater than the Splitting Size, thenthe Connector will not requestCTCs for all of the serial numbers.Some will remain without CTCsand therefore unavailable forproduction until the next requestwith the MDLP Connector for therelevant sGTINs.

Owner ID This is a static property thatidentifies the owner of a product.You can set it to the name of yourcompany. The attribute issubmitted to the RussianFederation authorities with arequest for serial numbers / crypto-codes and keys.

Subject ID This is a static property thatidentifies the product for whichserial numbers / crypto-codes andkeys are being requested. Theattribute is submitted to theRussian Federation authorities witha request for serial numbers /crypto-codes and keys.

15.1.7.4 Messages and Trouble-Shooting

The MDLP Connector issues the messages listed below.

• Given asynch job <UUID> could not download CTC with module MDLP Connector. Reason: Couldnot get buffer status. Reason: Bad Request: "globalErrors":["Participant. OrderNotFound,<orderID>"], "success":falseThe CTC polling request identified by the UUID in the message is not known in the MDLP system at theCRPT. When the polling scheduler repeats the request, the MDLP system responds with an error, asreported above.Correct the problem by marking the asynchronous request as "finished." Using the database adminis-tration tool, set the value fo field i16_status to 3 in table tbl_psm_asynchjobs.


15.1.8 Order Export Dispatcher ModuleThe Order Export Dispatcher Module is a multitenant module that is integrated into PSM and does not needadditional installation.The Order Export Dispatcher Module makes it possible for you to run a series of order export modules whenan order is exported. For example, you can use the Order Export Dispatcher Module in production for theRussian Federation to 1) execute the Order Export Module that exports the order to your L4 System and 2)execute the additional CRPT Order Export Module that exports the order to the Russian authorities. The OrderExport Dispatcher Module is integrated into PSM as of Release 1.14.

Order Export Dispatcher Module

If you want to use the Order Export Dispatcher Module to export an order, then the order must contain theseAIs:

• R50, specifying the Order Export Dispatcher Module• R51, specifying the customer configuration that the dispatcher should use for the order export.

You can also use the Order Export Dispatcher Module for manual order export with Management > OrderManagement > Order Export.

Setting Up Customer ConfigurationsYou can define customer configurations for the module under Settings > Multi-tenancy Modules > OrderExport Dispatcher Module. In the settings, specify the sequence of order export modules - as "export steps"- that should be run for a particular customer. Only one configuration is allowed per customer. Each "exportstep" consists of an index indicating whether it is the first / second / third step in the sequence; the name ofan order export module; and, for multitenant order export modules, a customer name. Multitenant orderexport modules may therefore run with their own customer configurations under the Order Export DispatcherModule. You may enter only modules that implement the order export or multitenancy order export interface.The Order Export Dispatcher Module itself implements the multitenant order export interface, so that it lookslike an order export module to the system.

The configuration XML that you enter into the Export Steps field has the following form:

<chain> <step order="0" module="EPCIS+ELVIS export" /> <step order="1" module="ERP feedback+ATTP EPCIS export" customer="Doku"/> </chain>

Order Export Dispatcher Module: ExecutionWhen it is called, the Order Export Dispatcher Module delegates the export to the modules as specified bythe customer-specific configuration. Execution continues to the next export step only if the previous stepfinished successfully. The modules called as export steps record their activity as usual in the system log asthey run.


15.1.9 Module Trigger via SchedulerPSM makes use of schedulers that execute specific tasks in predefined intervals. These can be order exportsor serial number imports for example. It is possible to trigger each module (Data Archiving, Order Export,Order Import, Product Import, and Serial Number Import) automatically via timer. Each timer can beactivated / deactivated and a schedule can be set for the timer via cron expressions. Cron expressions thatrange from minutes to hours are supported. To activate the import or export scheduler, open Settings >System Settings.

Modules may have different scheduler settings.

NOTICEScheduler active after PSM restartIf the scheduler is left active and the PSM server is restarted, the 'Stop' button is visible bydefault to enable you to stop the scheduler when the PSM has successfully restarted.

Example1 To configure the scheduler with cron expressions, open Settings > System Settings > Order Export.

Settings > System Settings > Order Export

2 If activated, this will schedule the module according to the cron expression provided. Find instructionsfor building cron expressions at http://www.cronmaker.com/. Or use the cron maker dialog to generatesimple cron expressions by clicking Cronmaker. If you work with cron expressions, click Save to savethe configuration. The button Start Scheduler and Stop Scheduler starts or stops the scheduler respec-tively. If you activate the option, the option 'Only export orders that are at least ... in state FINISHED orQA_RELEASED' is displayed.

3 In order to run the export with a delay related to the endtime of a finished workorder, activate the option.When you activate the delay configuration, the scheduler exports only orders that fulfill the delaycondition.

15.1.10 AIs with special behavior during export

Destination Module (R50)Similar to the owner of a product, the destination module of an order is identified using an order data with AIR50. With this assignment you define which module is responsible for exporting the order.You can only add a destination module (R50), if the order status is created or assigned.

NOTICEWorking without R50If you do not define a destination module, PSM will trigger all export modules installed.The modules then will be triggered one by one which may take some time.

The AI R50 can be used for all export modules installed.

Owner Name (R51)The owner name is identified by the product data with AI R51 and can be edited any time using the ProductMaster Data form.When you use Multitenancy, the owner name (R51) has to be identical with the customer name in theMultitenancy settings configuration name. If the owner names don’t match, the export will not be started.The owner name R51 is shown as soon as an export module is installed.


http://www.cronmaker.com/

15.2 User Rights TableThis table lists all user rights and shows which actions the user (PSM Administrator, Manager or Viewer)can perform by default. You can configure the default user groups and add/delete these user rights to/fromthe user group.Default Password

The default password is: "000"

Table: PSM User Rights

User Right Description PSM Adminis-trator

Manager Viewer

GeneralaccessPSA User may access PSM web

interfaceyes yes yes

isSupervisor User has supervisor rights yes no no

System SettingsmayChangeActiveDirecto-rySettings

User may change ActiveDirectory Settings

yes no no

mayChangeArchiveSettings

User may change the settingsin the Archive Settings

yes no no

mayChangeAutocom-pleteResults

User may change the settingsfor autocomplete hints in theGeneral Settings

yes no no

mayChangeCTCPurgeScheduler

User may configure the CTCdeletion mechanism underCTC Purge Scheduler

mayChangeEmailNotifica-tionSettings

User may change email -Notification Settings

yes no no

mayChangeLanguage User may change the UIlanguage of PSM in theGeneral Settings

yes no no

mayChangeLogReason-ForChangeFlag

User may activate or deactivateEudralex change-reasonrecording

yes no no

mayEditLogSettings User may edit log settings. yes no no

mayEditModuleSettings User may change PSM modulesettings

yes no no

mayChangeActivate-DisplayProductGtinSetting

User may edit the changeactivate displayproduct gtin setting.

yes no no

mayEditSysGlobals User may edit global systemsettings

no no no

mayChangeLogReason-ForChangeFlag

User may activate or deactivateEudralex-compliant logging ofreasons for changes to theconfiguration of PSM.

yes no no

AI ManagementmayAddAIs User may add new application

identifiersyes yes no

mayEditAIs User may edit new applicationidentifiers

yes yes no

mayDeactivateAIs User may activate/deactivateapplication identifiers

yes yes no

Order ManagementmayAddOrders User may create new orders yes yes no



Manager Viewer

mayEditOrder Button visible: User may createand edit orders

yes yes no

maySeeButtonOrderMove Button visible: User may enterthe move order menu

yes yes no

mayResetOrder Button visible: User may resetstatus of orders

yes yes no

mayRunTestProduction User may access TestProduction Generator in PSM

yes yes no

mayImportOrders User is allowed to access theImport Orders page andperform an import operationfrom an external system.

yes yes no

mayExportOrders User may export Orders to ERPSystem

yes yes no

mayDeleteOrders User may delete workorders yes yes no

Product ManagementmayAddProducts User may add new products yes yes no

mayEditProducts Button visible: User may createand edit products

yes yes no

mayDeleteProducts User may delete products yes yes no

Serial number ManagementmayAddGTINNumbers User may register new GTIN

Numbers in PSMyes yes no

mayEditGTINNumbers User may edit GTIN Numbersin PSM

yes yes no

mayAddProdCode-Numbers

User may register newProdCode Numbers in PSM

yes yes no

mayEditProdCode-Numbers

User may edit existingProdCode Numbers in PSM

yes yes no

mayAddSSCCNumbers User may register new SSCCNumbers in PSM

yes yes no

mayEditSSCCNumbers User may edit existing SSCCNumbers in PSM

yes yes no

mayImportSerialNumbers User may import serialnumbers

yes yes no

mayAddPPNNumbers User may register new PPNnumbers in PSM

yes yes no

mayEditPPNNumbers User may edit existing PPNnumbers in PSM

yes yes no

mayCreateSNRanges User may create a new serialnumber range

yes yes no

mayEditSNRanges User may edit existing serialnumber ranges

yes yes no

Line ManagementmayAddLines User may add new lines yes yes no

mayEditLines User may edit lines yes yes no

mayDeleteLines User may delete lines yes yes no

mayAddLineformat User may add lineformat yes yes no

mayEditLineformat User may create and editlineformat

yes yes no



Manager Viewer

mayAssignLineformat User may add lineformat toOrder

yes yes no

mayDeleteLineformat User may delete lineformat yes yes no

mayAddLineSettings User may add linesettings yes yes no

mayEditLineSettings User may edit lnesettings yes yes no

mayDeleteLineSettings User may delete linesettings yes yes no

User ManagementmayAddUsers User may add Users yes yes no

mayChangeUsers User may change User settings yes yes no

mayDeleteUsers User may delete Users yes yes no

mayAddGroups User may add groups yes yes no

mayEditGroups User may edit groups yes yes no

mayDeleteGroups User may delete groups yes yes no

Log EntriesmayPrintAuditTrail User may export audit trail via

Printeryes yes yes

mayExportAuditTrailA-sExcel

User may export audit trail asExcel file

yes yes yes

mayExportAudit-TrailAsPDF

User may export audit trail asPDF file

yes yes yes

15.3 The PSM WatchdogThe PSM Watchdog is a utility program whose purpose is to alert you automatically by e-mail if PSM hasnot started correctly, has stopped running or is otherwise unavailable (for example, server not reachable).The PSM Watchdog is a free-standing Java application that you install separately from PSM and which youmust start and stop separately from the PSM application in Glassfish.The PSM Watchdog ensures that you receive quick notification if PSM is not running when it ought to be.The PSM Watchdog works by periodically calling the standard login URL of PSM (for example: http://<host>:<port>/psm-1.14.0/login.jsf). The Watchdog then checks the HTTP status code that is returned bythe URL call. If the HTTP status code is not 200 OK, then the Watchdog retries the connection a specifiednumber of times. If the HTTP status code remains unfavorable, then the PSM Watchdog automatically sendsan e-mail to one or more preconfigured addresses reporting the problem.The PSM Watchdog sends an e-mail only if it detects that PSM is not running. The application keeps a logof its activities, so that you can also check its successful calls to PSM.For information on installing and using the PSM Watchdog, please see the PSM Watchdog User Manual.

15.4 Troubleshooting Guide

WARNINGTrained personnel onlyBefore attempting any corrective action, be sure that the person doing the action has beentrained on the PCE Site Manager and has read the entire operator manual. Failure to doso can result in injury and/or property damage. Corrective actions denoted with "MTService Technician" should not be attempted by operators or in-house technicians.

ScopeThis Troubleshooting Guide is intended to be used by operators and in-house technicians that have beentrained on the PCE Site Manager. It covers the basic symptoms and most usual fixes to failures that mayoccur on the PSM.This Guide can be applied to all machines with a PSM that have been installed by a trained METTLERTOLEDO service technician.


DisclaimerThis troubleshooting list contains a selected subset of alarms. Due to its generic character, it might notserve as a comprehensive troubleshooting guide for a specific installation. No customer specific data isgiven, for example no alarm messages for customized implementation of a module.

Language of messagesIf the message comes from a client via SOAP, the logs will be in the system language. If the messagecomes from the UI (e.g. order export via UI), the logs will be in the users language.

AlarmNumber

Alarm Message AlarmCategory

Probable cause/ How to fixthe issue

How to test/ Why not testable

90002 Line Name {0}already exists. Linecan not be created.

ERROR Happens if a line cannot becreated.

Try to create a new line with aname that is already present.

90010 Line Format couldnot be added.Reason: {0}.

ERROR Lineformat already exists forthat line.

Try to add a new lineformatwith an already existinglineformat name for that line.

90014 Line Format withName: {0} alreadyexists on Line: {1}.Lineformat can notbe created.

ERROR Happens if the user tries tocreate a line format with aname that already exists.

Try to create a new line formatwith a name that is alreadypresent.

90023 Line Setting: {0}could not be addedon Line: {1}.Reason: {2}.

ERROR Happens if the user tries to adda line setting to a line with aninvalid input.

Try to add the line settinglogin_max_failed with input"abc".

91008 Order: {0} could notbe imported.Reason: {1}.

ERROR Order cannot be overwritten.The WebService method forimporting orders allows tooverwrite a true/falseargument. If this is false andthe order already exists, anexception will be thrown.Another cause could be invalidorder data (e.g. invalid GTIN,wrong exp. date format, etc.).

Try to import an alreadyexisting order with argumentoverwrite = false.

91015 Product: {0} couldnot be imported.Reason: {1}.

ERROR Product cannot be overwritten.The WebService method forimporting products allows tooverwrite a true/falseargument. If this is false andthe product already exists, anexception will be thrown.Another cause could be invalidproduct data (e.g. invalidGTIN, etc.).

Try to import an alreadyexisting product with argumentoverwrite = false.

91030 Order: {0} could notbe imported fromWS. Reason: {1}

ERROR Happens if the order importfailed.

Try to import an order usingthe generic XML OrderImportwith invalid XML data.

91122 AI {0} alreadyexists. AI can notbe created.

ERROR The AI already exists in thedatabase. The AI has a uniqueconstraint and can only beused once. Choose a differentvalue for the AI.

Add a new AI with an alreadyexisting AI value.

91151 GTIN Number: {0}could not becreated. Reason:{1}.

ERROR Invalid value for GTIN or aGTIN number with the sameGTIN value already exists on adifferent rank.

Try to create a GTIN numberwith an invalid GTIN value(e.g. 15 digits or wrongchecksum).


AlarmNumber




91158 GTIN Number: {0}could not becreated. Reason:{1}.

ERROR GTIN input does not match thestandards (e.g. length ofnumber, checksum).

Try to create a GTIN with alength unequal 14 or a wrongchecksum.

91159 GTIN Number: {0}already exists.Cannot createduplicateGTINNumber.

ERROR Happens if the user tries tocreate a Product Code Numberfor a GTIN where the GTINalready exists.

Try to create a new ProductCode Number with AI 01 andan existing GTIN as theProduct Code Ref.

91161 SSCC Number withCompany Prefix:{0}, Pack ID: {1}and rank: {2} couldnot be created.Reason: {3}.

ERROR Invalid value for Compa-nyPrefix, packID, and rankvalue or the same SSCCnumber already exists on adifferent rank.

Try to create a SSCC numberwith an invalid packID (> 8).

91168 SSCC Number withCompany Prefix:{0}, Pack ID: {1}and rank: {2} couldnot be created.Reason: {3}.

ERROR Happens if the user tries tocreate a SSCC Number withinvalid inputs.

Try to create a new SSCCnumber with a company prefixwith more than 10 digits.

91169 SSCC Number withCompany Prefix:{0} and rank: {1}already exists.Cannot createduplicateSSCCNumber.

ERROR Happens if the user tries tocreate a SSCC number with acombination of CompanyPrefix and rank that alreadyexists.

Try to create a new SSCCnumber with a combination ofCompany Prefix and rank thatalready exists.

91178 PPN Number: {0}could not becreated. Reason:{1}.

ERROR Happens if the user tries tocreate a PPN with invalidinput.

Try to create a new PPN withmore than 12 digits in the PPNinput.

91179 PPN Number: {0}already exists.Cannot createduplicatePPNNumber.

ERROR Happens if the user tries tocreate a PPN that alreadyexists.

Try to create a PPN thatalready exists or try to createthe same PPN twice. (e.g.111663189657)

91188 Prod Code Numberwith prodCode: {0},AI: {1} and Rank:{2} could not becreated. Reason:{3}.

ERROR Happens if a Product CodeNumber cannot be created dueto invalid input.

Try to create a new ProductCode Number with AI 01 andProduct Code Ref 123.

91189 Prod Code Numberwith prodCode: {0},AI: {1} and Rank:{2} already exists.Cannot createduplicate ProdCo-deNumber.

ERROR Happens if the user tries tocreate a Product Code Numberwith a combination of ProductCode, AI, and rank that alreadyexists but does not exist in oneof the synchronized tables(e.g. GTIN).

Find a Product Code Numberfor AI 01 (GTIN) where theGTIN does not exist underManagement->Serial NumberManagement->edit GTINNumbers. Try to create a newProduct Code Number with thesame combination of ProductCode, AI, and rank.


AlarmNumber




91191 Product: {0} couldnot be saved.Reason: {1}.

ERROR Invalid Order Data (e.g. invalidGTIN).

Edit product data and changecheck digit of GTIN to beinvalid. Try to save theproduct.

91197 Product Name {0}already exists. Cannot createduplicate Product.

ERROR Happens if the user tries tocreate a product where thename equals the name of anexisting product.

Try to create a product wherethe name equals the name ofan existing product.

91203 Order: {0} couldnot be saved.Reason: {1}.

ERROR Invalid Order Data (e.g. invalidGTIN).

Edit order data and changecheck digit of GTIN to beinvalid and try to save theorder.

91205 Order: {0} couldnot be deleted.Reason: {1}.

ERROR Order State for work order isnot CREATED or not ASSIGNED.

Try to delete a work order withstatus FINISHED.

91207 Order Data couldnot be added.Reason: {0}.

ERROR Order Data already exists orinvalid value.

Try to add invalid order data(e.g. invalid GTIN or exp.date).

91210 Order Name {0}already exists. Cannot createduplicate Order.

ERROR The order name already existsin the database. The ordername has a unique constraintand can only be used once.Choose a different value fororder name.

Add a new order with analready existing order name.

91211 Order: {0} couldnot be savedbecause it haswrong state {1}.

ERROR The order is neither in the stateCREATED nor ASSIGNED.

Try to edit and save an orderwith the state FINISHED.

91227 Password Repeatdoes not matchPassword.

ERROR When changing a passwordthe repeated password doesnot match the new password.

When changing the passwordof a user try to use differentinputs for password andpassword repeat.

91228 User: {0} alreadyexists. User cannot be created.

ERROR The user name already existsin the database. The username has a unique constraintand can only be used once.Choose a different value foruser name.

Add a new user with analready existing user name.

91229 User: {0} alreadyexists. User cannot be updated.

ERROR Happens if the user tries tochange the name of a user to auser name that already exists.

Try to change the name of auser (e.g. "pceadmin") to aname that already exists (e.g."root").

91239 Group: {0} alreadyexists. Group cannot be created.

ERROR The group name already existsin the database. Group namehas a unique constraint andcan only be used once.Choose a different value forgroup name.

Add a new group with analready existing group name.

91240 Group: {0} alreadyexists. Group cannot be updated.

ERROR Happens if the user tries tochange the name of a group toa group name that alreadyexists.

Try to change the name of agroup (e.g. "Sysadmin") to aname that already exists (e.g."Administrator").


AlarmNumber




91265 Serial number withstart: {0}, end: {1}overlaps withexisting range withstart: {2}, end: {3}

ERROR Happens during import ofserial number ranges if theimport affects multiple rangeswhere at least two rangesoverlap in their start and endvalues. (e.g. Range1[100-1100], Range2[1000-2000]).

Hard to test. PSM needs aserial number import modulewith proper setup and aconnection to a system thatexports serial number ranges.

91282 Order: {0} couldnot be exported byModule: {2}.Reason: {1}.

ERROR May happen during export oforders if the settings of anorder export module are notcorrect.If the reason states "sleep inter-rupted", one probable cause isthat the server timed out therequest. A fix is to increase theRequest Timeout setting of theGlassfish server.

Install the TraceLink OrderExport Module with invalidsettings and try to run the orderexport.Use the Tracelink Module withthe settings "Upload toTracelink" and "ActivateProcessing Check" enabled toexport an order that takeslonger than the RequestTimeout setting (by default900 seconds).

91301 Test Order: {0}failed. Reason: {1}.

ERROR May happen when running testorder due to invalid input.

Under 'Management->OrderManagement->run Test Order'run an order with a negativequantity.

91302 No Order selected ERROR 'Run test order' was startedwith no order selected.

In PSM make sure you have noorder in state CREATED orASSIGNED. Then try to run atest order without an orderselected.

91314 Email Address: {0}could not be added.

ERROR May happen when addingemail notification settings.

Try to add a new email notifi-cation setting with an invalidemail. (e.g. test.com)

92033 Module Setting:{0} , value: {1},active: {2} forModule: {3} couldnot be updated.Reason: {4}.

ERROR Happens if a module settingcannot be updated/savedbecause of wrong user input.

In a module setting thatexpects a number type a letterand try to save.

95000 MSG-CODE: {0} {1} INFO Audit Log for serial numberimport.

Perform a serial number importoperation.

95001 Invalid setting in{0} : {1}

ERROR Invalid settings on theTraceLink serial number importmodule. Settings are found on'Settings > Module Settings'.

Enter an invalid setting on'Settings > Module Settings'.

95002 variable ERROR Connection Failure. Possiblydue to inaccessible TraceLinkservice endpoint, or authenti-cation/authorization failureswhile trying to connect.

Provide invalid URL orcredentials for the TraceLink'sweb service for serial numberimport.

95003 variable ERROR Serial Number Import Failure.Possibly due to databaseconstraint violations (duplicateidentifiers, keys, etc.), orinvalid serial number formats.

Try a manual serial numberimport and enter an invalidserial number format.


AlarmNumber




95004 variable ERROR SFTP-related exceptions whileexporting the order. Possiblyrelated to connectivity issues orauthentication/authorizationerrors during the SFTP access.

Provide a well-formed butinvalid URL on the module'sSFTP settings or provide wrongauthentication credentials.

95009 Failed to parse EPC-Hex string for {0} /Failed to create epc-hex string for {0} /other genericvariable messagesare possible

ERROR Generic exception on themodule while importing serialnumbers. Usually thrown if thespecific cause of the exceptioncannot be deduced.

Provide an invalid EPC-Hexpattern

95010 variable INFO Generic info message for usernotifications such as confir-mations when changing fieldvalues.

Edit a field value in theTraceLink module and save it.

95014 variable ERROR Generic error message whenthe cause is not easilydeduced. Needs developerassistance to trace or debug.

Too many possible causes.

95100 {0} {1} after {2}msec

INFO Audit Log for order export. Perform an order exportoperation.

95101 Invalid settings in{0} : {1}

ERROR Invalid settings on theTraceLink order export module.Settings are found on 'Settings> Module Settings'.

Enter an invalid setting on'Settings > Module Settings'.

95102 Invalid WorkOrder{0}

ERROR Invalid work order wasattempted to be exported.Possibly from an order thatdoes not pass consistencycheck, or a databaseconstraint was violated duringthe export (duplicate identifiers,keys, etc.).

Try to export a work order thatis known to be invalid.

95106 variable ERROR Malformed XML on theexported order. Possiblycaused by a corrupt file orinconsistent/invalid XPATH.

Provide a well-formed butinvalid XPATH mapping on themodule's settings.

95109 {0} failed within/after {1} msecbecause {2}

ERROR Generic exception on themodule while exporting orders.Usually thrown if the specificcause of the exception cannotbe deduced.


98001 BusinessException. Reason:{0}

ERROR This is a general code thatmay occur on differentoccasions.

Try to create a serial numberrange for a GTIN that overlapswith another serial numberrange for a GTIN.


AlarmNumber




99020 May output differentmessagesdepending on errorcase. For example:Error encounteredwhile exportingorders: {0} / ExportJob failed for Order[{0}]. / Errorrequestingexportable ordersin {0}

FATAL Happens if a timer startedorder export of serial numberimport task fails.

Install an order export modulein PSM with wrong configu-rations in the settings. Start theorder export timer and wait forit to trigger the order export.

999999 variable variable Preserved for any INFO,WARNING, ERROR type ofmessage during manual serialnumber import.



Inten

tiona

lly le

ft blan

k


GlossaryAI

GS1 Application Identifier

Bundle

A bundle is a packaging unit at the aggregationprocess. It consists of several items. It is usuallyaggregated to a case or directly to a pallet.

Case

A case is a packaging unit at the aggregation process.It consists of several items or bundles. It is usuallyaggregated to a pallet.

EPC

An Electronic Product Code (EPC) is a universalidentifier that gives a unique identity to a specificphysical object.

ERP

Enterprise Resource Planning; planning the use ofresources within an enterprise with the aid of software(e.g., SAP)

ERP-System

Enterprise Resource Planning System (typically ordertransaction)

GS1

Global Standards One. GS1 is dedicated to the designand implementation of global standards and solutionsto improve the efficiency and visibility of supply anddemand chains globally and across sectors. The GS1system of standards is the most widely used supplychain standards system in the world.

GTIN

Global Trade Item Number

Item

An item is the smallest unit at the aggregation process.This can be a carton or a blister. It is usuallyaggregated to a bundle or directly to a shipping case.

Pallet

A pallet is a packaging unit at the aggregationprocess. It consists of several cases.

PCE

Pharmacontrol Electronic GmbH

PLM

PCE Line Manager

PSM

PCE Site Manager

Rank

At each aggregation rank, unambiguous assignment ofunits to parent-child aggregation levels is done

SOAP

Simple Object Access Protocol is a protocol specifi-cation for exchanging structured information in theimplementation of web services in computer networks.

SSCC

Serial Shipping Container Code maintained by GS1

Unit

A unit is the result of an aggregation level. The termunit is used for an item, a bundle, a shipping case ora pallet.


Inten

tiona

lly le

ft blan

k


Inten

tiona

lly le

ft blan

k


Pharmacontrol Electronic GmbHHarzstraße 164646 Heppenheim, GermanyTel. +49 6252 6736 0Fax +49 6252 6736 111www.mt.com

Subject to technical changes.© Pharmacontrol Electronic GmbH 09/2019PCE Site Manager - PSM 1.14 - User Manual - Document Version D

For more informationwww.mt.com/pce

PCE Site Manager - PSM 1.14 - User Manual - Document Version D 9/12/2019 9:05 AM - SchemaST4 PDF engine - Layout by Victor Mahler