ADMINISTRATION GUIDE | CONFIDENTIAL
SAP Advanced Track and Trace for Pharmaceuticals
2019-02-06
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
Administrator's Guide for SAP Advanced Track
and Trace for Pharmaceuticals
Release 2.0, Feature Package 3
THE BEST RUN
Content
1
Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1
About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2
Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Useful Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Related Master Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Related Operations Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3
Overview of Required SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
SAP Notes Relevant for Advanced Track and Trace for Pharmaceuticals Repository Instance
.......................................................................8
SAP Notes Relevant for SAP Advanced Track and Trace for Pharmaceuticals Add-On for ECC
and SAP S/4HANA® 1610 and 1709 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
SAP Notes Relevant for SAP Advanced Track and Trace for Pharmaceuticals ECC or SAP S/
4HANA Add-On to Convert/Upgrade to SAP S/4HANA 1809 FPS01 or Higher. . . . . . . . . . . . . . . 11
SAP Notes Relevant for the SAP Advanced Track and Trace for Pharmaceuticals Add-On for
EWM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4
Installing and Upgrading SAP Advanced Track and Trace for Pharmaceuticals . . . . . . . . . . . . . . . . . 13
Upgrading from SAP Advanced Track and Trace for Pharmaceuticals 1.0 to SAP Advanced
Track and Trace for Pharmaceuticals 2.0 or higher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Upgrading from SAP Advanced Track and Trace for Pharmaceuticals 2.0 to Release 2.0, FP02
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Upgrading from SAP Advanced Track and Trace for Pharmaceuticals 2.0 FP01 to Release 2.0,
FP02. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Installing SAP Advanced Track and Trace for Pharmaceuticals 2.0, FP02 (No Upgrade). . . . . . . . . 16
Upgrading from SAP Advanced Track and Trace for Pharmaceuticals 2.0 to Release 2.0, FP03
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Upgrading from SAP Advanced Track and Trace for Pharmaceuticals 2.0 FP01 to Release 2.0,
FP03. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Upgrading from SAP Advanced Track and Trace for Pharmaceuticals 2.0 FP02 to Release 2.0,
FP03. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Installing SAP Advanced Track and Trace for Pharmaceuticals 2.0, FP03 (No Upgrade) . . . . . . . . 19
Converting or Upgrading from SAP Advanced Track and Trace for Pharmaceuticals ECC or SAP
S/4HANA 1610/1709 Add-On to SAP S/4HANA 1809 FPS01 or Higher. . . . . . . . . . . . . . . . . . . . 20
2
About SAP Advanced Track and Trace for Pharmaceuticals . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1
Software Units of SAP Advanced Track and Trace for Pharmaceuticals. . . . . . . . . . . . . . . . . . . . . . . 21
2.2
Software Component Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3
System Landscape for SAP Advanced Track and Trace for Pharmaceuticals . . . . . . . . . . . . . . . . . . . 27
2.4
Overall Implementation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Content
3
Security Information for SAP Advanced Track and Trace for Pharmaceuticals. . . . . . . . . . . . . 33
3.1
Other Required Documents for Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2
Authorization Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Authorizations in Master Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Authorizations in Serial Number Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Authorizations in Object and Event Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Authorization Object for Authentication Request /STTP/AUTH. . . . . . . . . . . . . . . . . . . . . . . . . .41
Further Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Authorizations in ECC Add-On and SAP S/4HANA for SAP Advanced Track and Trace for
Pharmaceuticals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Authorizations EWM Add-On for SAP Advanced Track and Trace for Pharmaceuticals. . . . . . . . . 48
4
References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.1
Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.2
SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5
Release Availability Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Content
CONFIDENTIAL
3
1
Getting Started
Make sure to read the information in this section before you get started with SAP Advanced Track and Trace for
Pharmaceuticals.
1.1
About This Guide
This guide is the central starting point for the implementation of SAP Advanced Track and Trace for
Pharmaceuticals . It tells you how to install and implement SAP Advanced Track and Trace for Pharmaceuticals
and also provides security and operations information. You can find cross-scenario implementation
information as well as scenario-specific information in this guide.
 Note
The central starting point for the technical upgrade of your SAP application/solution is the administrator’s
guide, which you can find on the help portal at http://help.sap.com/attp.
Use the Administrator’s guide to get an overview of SAP Advanced Track and Trace for Pharmaceuticals, its
software units, and its scenarios from a technical perspective. The administrator’s guide is a planning tool that
helps you to design your system landscape. It refers you to the required detailed documentation, mainly the
following:
● Installation guides for single software units
● SAP Notes
● Configuration documentation
● SAP Library documentation
 Note
You can find the most current information about the technical implementation of SAP Advanced Track and
Trace for Pharmaceuticals and the latest installation and configuration guides on the help portal at http://
help.sap.com/attp.
We strongly recommend that you use the documents available here. The guides are regularly updated.
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in your
company. The business scenarios are only intended as models and do not necessarily run the way they are
described here in your customer-specific system landscape. Ensure that you check your requirements and
systems to determine whether these scenarios can be used productively at your site. Furthermore, we
recommend that you test these scenarios thoroughly in your test systems to ensure they are complete and free
of errors before going live.
This administrator’s guide primarily discusses the overall technical implementation of SAP Advanced Track and
Trace for Pharmaceuticals, rather than its subordinate components. This means that additional software
4
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
dependencies might exist without being mentioned explicitly in this document. You can find more information
on component-specific software dependencies in the corresponding installation guides.
Document History
This section provides details about the changes made in each version of this document.
 Note
The latest version of this document is available on SAP Help Portal at http://help.sap.com/attp
Version
Date
Comment
2.4
2019-02-06
Updates on integration with SAP S/4HANA
2.3
2018-12-17
Updated for Release 2.0, Feature Package 03
2.2
2018-04-06
Updated for Release 2.0, Feature Package 02
2.1
2017-08-07
Updated for Release 2.0 , Feature Package 01
2.03
2017-05-09
Updated SAP Notes Relevant for SAP Advanced Track and Trace for Pharma­
ceuticals Add-On for ECC with recommended SAP notes
2.02
2017-03-15
Updated Software Units of SAP Advanced Track and Trace for Pharmaceuticals
with information on CDBASIS 100 SP01
2.01
2016-12-09
Correction of report in chapter 1.4.1
2.0
2016-12-05
Updated version for Release 2.0
1.1
2016-04-01
Updated version for SP1
1.0
2015-09-15
Final version
1.2
Related Information
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
CONFIDENTIAL
5
1.2.1 Useful Links
The following resources provide access to more information about general topics, such as software downloads,
customer incidents, or high availability.
Resource
Where to Find It
User assistance for SAP Advanced Track and Trace for Phar­
http://help.sap.com/attp
maceuticals
Information about creating customer incidents
http://support.sap.com/incident
SAP Notes search
http://support.sap.com/notes
SAP Software Download Center
http://support.sap.com/swdc
Product Availability Matrix
http://support.sap.com/pam
Early Knowledge Transfer and role-specific learning maps
http://support.sap.com/ekt
Sizing
http://service.sap.com/sizing
Network security
http://service.sap.com/securityguide
High availability
http://www.sdn.sap.com/irj/sdn/ha
Performance
http://service.sap.com/performance
Information about support package stacks, latest software
http://support.sap.com/sp-stacks
versions and patch level requirements
Information about Unicode technology
http://www.sdn.sap.com/irj/sdn/i18n
1.2.2 Related Master Guides
This administrator’s guide is based on Master Guides for cross-industry applications. You can find more
information about the relevant applications in the following documents:
Title
Location
Master Guide
SAP Help Portal at http://help.sap.com/aif
SAP Application Interface Framework 3.0
Master Guide
SAP Help Portal at http://help.sap.com/nw74
SAP NetWeaver 7.4
6
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
Title
Location
Master Guide
SAP Help Portal at http://help.sap.com/erp
SAP ERP 6.0
1.2.3 Related Operations Information
SAP Advanced Track and Trace for Pharmaceuticals is based on an SAP Net Weaver 7.4 system and on SAP
Application Interface Framework 3.0
Therefore, the general operations information for the areas listed below is covered in the operations guide of
SAP NetWeaver. In addition, the operations information specific to Application Interface framework are covered
by the application help of the SAP Application Interface Framework in the sections The SAP Application
Interface Framework for Business Users and The SAP Application Interface Framework for IT Personnel
(relevant topics are marked with “also AIF” in the list given below):
● Technical system landscape
● Overview of technical runtime scenarios, which result from setting up the corresponding business
scenarios
● Monitoring concept (also AIF)
● Logging and tracing (also AIF)
● Technical configuration (also AIF)
● Backup and recovery
● Periodical tasks (also AIF)
● High availability concept
● Starting and stopping (by which means and in which sequence)
● Scenario administration concept (possible dependencies between scenario components)
● Concept for monitoring, error handling, restart and recovery of interfaces (also AIF)
● Concept for data archiving and management of outdated technical data
● Software change management
● Scenario maintenance concept
● Concept for handling customer development
● Support desk management
● Troubleshooting
You can find more information about the corresponding operations guides for SAP NetWeaver in the following
table:
Title
Location
Master Guide
SAP Help Portal at http://help.sap.com/nw74
SAP NetWeaver 7.4
Operations information for SAP NetWeaver
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
SAP Help Portal at http://help.sap.com/nw74
CONFIDENTIAL
7
Title
Location
SAP NetWeaver Administrator’s Guide – Technical Opera­
SAP Help Portal at http://help.sap.com/nw74
tions Manual
under System Administration -> Technical Operations Man­
ual
SAP Application Interface Framework 3.0 operations infor­
SAP Help Portal at http://help.sap.com/aif
mation
Application Help of the SAP Application Interface Framework
in the sections – The SAP Application Interface Framework
for Business Users and The SAP Application Interface
Framework for IT Personnel
1.3
Overview of Required SAP Notes
The following SAP Notes are essential for installing, upgrading, and operating SAP Advanced Track and Trace
for Pharmaceuticals .
 Note
The SAP Notes relevant for installation and upgrade are also listed in the respective sections in this guide.
These SAP Notes contain the most recent information on the installation, as well as corrections to the
installation documentation.
Make sure that you have the latest version of each SAP Note, which is available on SAP Support Portal at
http://support.sap.com/notes .
1.3.1 SAP Notes Relevant for Advanced Track and Trace for
Pharmaceuticals Repository Instance
Installation Notes: SAP Advanced Track and Trace for Pharmaceuticals System
SAP Note Number
Title
Description
2203586
Release Strategy for the ABAP Add-on
Provides detailed information about
STTP
how to install SAP Advanced Track and
Trace for Pharmaceuticals
Relevant Notes of SAP NetWeaver
8
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
SAP Note Number
Title
Description
2068120
Runtime Error OBJECTS_TA­
Installation of this note is recom­
BLES_NOT_COMPATIBLE in Gateway
mended before using any OData serv­
Framework
ices with SAP Advanced Track and
Trace for Pharmaceuticals
2127137
Dump DYNP_TOO_MANY_RADIOBUT­
TONS_ON in sm59
Installation of this note is recom­
mended before starting to customize
SAP Advanced Track and Trace for
Pharmaceuticals
Relevant Notes of SAP Application Interface Framework
SAP Note Number
Title
Description
2213557
Implementation of BC Sets for AIF
This note must be installed before acti­
vating the BC set contents for the in­
cluded AIF interfaces
1926599
Error Handling: URL field is too short
Installation of this note is recom­
mended before using AIF with SAP Ad­
vanced Track and Trace for Pharma­
ceuticals interfaces
2134116
Error Handling: Displaying data content
Installation of this note is recom­
for web services created through up­
mended before using AIF with SAP Ad­
loading an WSDL file
vanced Track and Trace for Pharma­
ceuticals interfaces
2175174
Serialization: Option to skip serializa­
Installation of this note is recom­
tion under certain conditions
mended before using AIF with SAP Ad­
vanced Track and Trace for Pharma­
ceuticals interfaces
2177497
Runtime: wrong Serialization customiz­
Installation of this note is recom­
ing may leads to dump
mended before using AIF with SAP Ad­
vanced Track and Trace for Pharma­
ceuticals interfaces
2198348
Custom Time and Date will be overwrit­
Installation of this note is recom­
ten from /AIF/UTIL_ADD_MSG
mended before using AIF with SAP Ad­
vanced Track and Trace for Pharma­
ceuticals interfaces
2269477
Alerting with AIF not possible
No Alerts can be created with the SAP
Application Interface Framework if an
error in the processing of an EPCIS
Message occurs.
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
CONFIDENTIAL
9
SAP Note Number
Title
Description
2318079
Alerting with SAP AIF not possible (fol­
No Alerts can be created with the SAP
low-up)
Application Interface Framework if an
error in the processing of an EPCIS
Message occurs
2368509
AIF/CREATE_ALERT: bug fix for
The user/role could not be correctly de­
BAdI /AIF/ALERT_DET_RECIPIENTS
termined due to wrong logic after
BAdI /AIF/ALERT_DET_RECIPIENTS in
Function Module /AIF/CREATE_ALERT.
1.3.2 SAP Notes Relevant for SAP Advanced Track and Trace
for Pharmaceuticals Add-On for ECC and SAP S/
4HANA® 1610 and 1709
Installation Notes ECC Add-On for SAP Advanced Track and Trace for Pharmaceuticals
SAP Note Number
Title
Description
2213945
Release Strategy for the ABAP Add-on
Provides detailed information about
for STTPEC
how to install SAP Advanced Track and
Trace for Pharmaceuticals Add-on for
ECC
Installation Notes SAP S/4HANA Add-On for SAP Advanced Track and Trace for Pharmaceuticals
SAP Note Number
Title
Description
2616163
Redirect Inconsistency error in S/
Provides detailed information about
4HANA after installing Advanced Track
how to overcome the redirect inconsis­
& Trace add-on
tency error after installing SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on for SAP S/4HANA
Recommended Notes for SAP Advanced Track and Trace for Pharmaceuticals
SAP Note Number
Title
Description
2393995
Performance Improvement when Post­
Installation of this note is recom­
ing a Goods Issue
mended before using the SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on for ECC
10
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
SAP Note Number
Title
Description
2444191
Optimization of selection of document
Installation of this note is recom­
segments for materials
mended before using the SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on
2405762
Popup prevents shipping of an out­
Installation of this note is recom­
bound delivery via RF Dialog
mended before using the SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on
Relevant Notes of SAP NetWeaver
SAP Note Number
Title
Description
2008119
Error message when entering or dis­
Installation of this note is recom­
playing a date
mended before using the SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on
2079598
IWCOR – HTTP POST call fails when us­ Installation of this note is recom­
ing class CL_REST_HTTP_C
mended before using any OData service
within the SAP Advanced Track and
Trace for Pharmaceuticals Add-on for
ECC
2127137
Dump DYNP_TOO_MANY_RADIOBUT­
TONS_ON in sm59
Installation of this note is recom­
mended before starting to customize
the SAP Advanced Track and Trace for
Pharmaceuticals
1.3.3 SAP Notes Relevant for SAP Advanced Track and Trace
for Pharmaceuticals ECC or SAP S/4HANA Add-On to
Convert/Upgrade to SAP S/4HANA 1809 FPS01 or
Higher
Conversion/Upgrade guidelines for SAP Advanced Track and Trace to move to SAP S/4HANA 1809 FPS01
or higher
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
CONFIDENTIAL
11
SAP Note Number
Title
Description
2716224
S/4HANA 1809+ Conversion Guidelines Provides general information and impli­
for Advanced Track & Trace
cations of moving to SAP S/4HANA
1809 FPS01 or higher.
Installation Notes for SAP Advanced Track and Trace for Pharmaceuticals ECC or SAP S/4HANA Add-On
SAP Note Number
Title
Description
2507495
S4TC STTPEC Master Check for S/4
Installation of this note is required be­
System Conversion Checks
fore starting the conversion/upgrade to
allow the move from a lower SAP S/
4HANA release or ECC to SAP S/
4HANA 1809 FPS01 or higher.
2733437
S/4HANA 1809+ Migration Report be­
Starting with SAP S/4HANA 1809
fore Conversion/Upgrade
FPS01, the ECC Add-on functionality is
now part of the SAP S/4 HANA core de­
livery. Therefore, the integration to Ad­
vanced Track and Trace for Pharma­
ceuticals does no longer require an ad­
ditional installation, but can be
switched on via a business function.
The move however includes changes to
the data dictionary and therefore re­
quires defined steps to be executed be­
fore the conversion/upgrade.
Specifically, the data from the MARM-/
STTPEC/GTIN field needs to be moved
to the standard EAN11 field within
MEAN table with a relevant EAN cate­
gory that specifies the EAN to be a
compliant GTIN14.
2745034
S/4HANA 1809+ Migration Report be­
fore Conversion/Upgrade DDICs for
SAP note 2733437
2699253
S4TC STTPEC Master Check for S/4
To implement SAP note 2733437
correctly, certain data dictionary ob­
jects need to be created.
Before the release of SAP S/4HANA
System Conversion Checks (Update for 1809 FPS01, the conversion to SAP S/
FPS1)
4HANA 1809 was blocked as this could
cause data loss. To remove the block for
conversion for SAP S/4HANA 1809 or
higher, you need to implement this up­
date of the check class.
Installation Notes for SAP Advanced Track and Trace Repository system
12
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
SAP Note Number
Title
Description
2719090
Activity Validation with BizTransaction­
Installation of this note is recom­
List
mended to allow the correct behavior of
the SAP S/4HANA 1809 FPS01 code
line.
1.3.4 SAP Notes Relevant for the SAP Advanced Track and
Trace for Pharmaceuticals Add-On for EWM
Installation Notes ECC Add-On for SAP Advanced Track and Trace for Pharmaceuticals
SAP Note Number
Title
Description
2380100
Release Strategy for the ABAP Add-on
Provides detailed information about
for STTPEW
how to install SAP Advanced Track and
Trace for Pharmaceuticals Add-on for
EWM
1.4
Installing and Upgrading SAP Advanced Track and Trace
for Pharmaceuticals
This section provides information about how to prepare for installation and what to do before and after the
installation of SAP Advanced Track and Trace for Pharmaceuticals .It also tells you how to upgrade to a newer
release of SAP Advanced Track and Trace for Pharmaceuticals.
1.4.1 Upgrading from SAP Advanced Track and Trace for
Pharmaceuticals 1.0 to SAP Advanced Track and
Trace for Pharmaceuticals 2.0 or higher
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
CONFIDENTIAL
13
1.4.1.1
STTP200: Programs to Run Immediately After
Update, Before Starting Testing or Productive Work
The following programs must be executed once, if updating from SAP Advanced Track and Trace for
Pharmaceuticals 1.x to SAP Advanced Track and Trace for Pharmaceuticals 2.0 or higher:
● /STTP/MIG20_AUTH
● /STTP/MIG20_CUST
● /STTP/MIG20_GLNHIST_BUP
● /STTP/MIG20_GLNHIST_LOC
● /STTP/MIG20_BUP_ROLEVAR
● /STTP/MIG20_NROBJ_GCP
● /STTP/MIG20_BUPREG
You may either select and execute the above reports separately or alternatively execute report /STTP/
MIG20_ALL which gives you access to all above-mentioned single reports.
For more details, please refer to the report documentation.
Also execute the following reports :
● /STTP/MIG_SERNO_MGMT_TYPE Migration of Trade Item Serial Number Management Type
● /STTP/MIG_REP_COMMUNIC_ATTR Migration of Country Reporting Communication Settings
Execute transaction /STTP/OMSL_INIT on all development systems. After this initialization you can configure
the material number conversion routine via transaction /STTP/OMSL. For more information, see chapter 5.1.16
Country-specific Customizing in the configuration guide for SAP Advanced Track and Trace for
Pharmaceuticals on the SAP Help Portal at http://help.sap.com/attp .
1.4.1.2
STTP200: Manual Steps After Update
The maintenance of the repository authorization has been improved in many aspects. Consequently, you need
to set up the authorization data from a scratch after migration from release 1.0 to release 2.0. The existing
transaction from release 1.0 /STTP/DM_AUTH, and also the database table from release 1.0 /STTP/DM_AUTH
are retired with release 2.0.
For the Web-UI to function correctly the following new service must be activated and the SICF node must be
started in Transaction /IWFND/MAINT_SERVIC:
● /STTP/ATT_COCKPIT_210_SRV
Related Information
Authorizations in Object and Event Repository [page 37]
14
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
1.4.1.3
STTPEC200: Programs to Run Immediately After
Update Before Starting Testing or Productive Work
The following programs must be executed once if updating from SAP Advanced Track and Trace for
Pharmaceuticals 1.x to SAP Advanced Track and Trace for Pharmaceuticals 2.0 or higher:
● /STTPEC/MIG20_AUTH
● /STTPEC/MIG20_CUST
● /STTPEC/MIG20_MARMSYNC
For more details, please refer to the report documentation.
1.4.2 Upgrading from SAP Advanced Track and Trace for
Pharmaceuticals 2.0 to Release 2.0, FP02
1.4.2.1
STTP200: Programs to Run Immediately After
Update
The following programs must be executed once after the installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTP/MIG20_AUTH
● /STTP/MIG202_PML_IDX – Migration of PML Messages from Standard AIF Index Table
● /STTP/MIG_REP_COMMUNIC_ATTR – Migration of Country Reporting Communication Settings
1.4.2.2
STTP200: Manual Steps After Update
For the Web-UI to function correctly, the following new service must be activated and the SICF node must be
started in Transaction /IWFND/MAINT_SERVIC:
● /STTP/ATT_COCKPIT_210_SRV
1.4.3 Upgrading from SAP Advanced Track and Trace for
Pharmaceuticals 2.0 FP01 to Release 2.0, FP02
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
CONFIDENTIAL
15
1.4.3.1
STTP200: Programs to Run Immediately After
Update
The following programs must be executed once after the installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTP/MIG_REP_COMMUNIC_ATTR – Migration of Country Reporting Communication Settings
● /STTP/MIG202_PML_IDX – Migration of PML Messages from Standard AIF Index Table
1.4.3.2
STTP200: Manual Steps After Update
For the Web-UI to function correctly, the following new service must be activated and the SICF node must be
started in Transaction /IWFND/MAINT_SERVIC:
● /STTP/ATT_COCKPIT_210_SRV
1.4.4 Installing SAP Advanced Track and Trace for
Pharmaceuticals 2.0, FP02 (No Upgrade)
1.4.4.1
STTP200: Programs to Run Immediately After
Installing, Before Starting Testing or Productive
Work
The following programs must be executed once after installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTP/MIG20_AUTH
Execute transaction /STTP/OMSL_INIT on all development systems. After this initialization you can configure
the material number conversion routine via transaction /STTP/OMSL. For more information, see chapter 5.1.16
Country-specific Customizing in the configuration guide for SAP Advanced Track and Trace for
Pharmaceuticals on the SAP Help Portal at http://help.sap.com/attp .
16
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
1.4.4.2
STTP200: Manual Steps After Update
For the Web-UI to function correctly, the following new service must be activated and the SICF node must be
started in Transaction /IWFND/MAINT_SERVIC:
● /STTP/ATT_COCKPIT_210_SRV
1.4.4.3
STTPEC200: Programs to Run Immediately After
Installing, Before Starting Testing or Productive
Work
The following programs must be executed once after installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTPEC/MIG20_AUTH
1.4.4.4
STTPEW200: Programs to Run Immediately After
Installing Before Starting Testing or Productive
Work
The following programs must be executed once after installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTPEW/MIG20_AUTH
1.4.5 Upgrading from SAP Advanced Track and Trace for
Pharmaceuticals 2.0 to Release 2.0, FP03
1.4.5.1
STTP200: Programs to Run Immediately After
Update
The following programs must be executed once after the installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTP/MIG20_AUTH
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
CONFIDENTIAL
17
● /STTP/MIG202_PML_IDX – Migration of PML Messages from Standard AIF Index Table
● /STTP/MIG_REP_COMMUNIC_ATTR – Migration of Country Reporting Communication Settings
● /STTP/MIG202_STTPS_IDX – Migration: Move STTPS Msgs. fr. std. AIF-Idx Table to STTPS Idx Table
1.4.5.2
STTP200: Manual Steps After Update
For the Web-UI to function correctly, the following new service must be activated and the SICF node must be
started in Transaction /IWFND/MAINT_SERVIC:
● /STTP/ATT_COCKPIT_210_SRV
1.4.6 Upgrading from SAP Advanced Track and Trace for
Pharmaceuticals 2.0 FP01 to Release 2.0, FP03
1.4.6.1
STTP200: Programs to Run Immediately After
Update
The following programs must be executed once after the installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
/STTP/MIG_REP_COMMUNIC_ATTR – Migration of Country Reporting Communication Settings
/STTP/MIG202_PML_IDX – Migration of PML Messages from Standard AIF Index Table
/STTP/MIG202_STTPS_IDX – Migration: Move STTPS Msgs. fr. std. AIF-Idx Table to STTPS Idx Table
1.4.6.2
STTP200: Manual Steps After Update
For the Web-UI to function correctly, the following new service must be activated and the SICF node must be
started in Transaction /IWFND/MAINT_SERVIC:
● /STTP/ATT_COCKPIT_210_SRV
18
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
1.4.7 Upgrading from SAP Advanced Track and Trace for
Pharmaceuticals 2.0 FP02 to Release 2.0, FP03
1.4.7.1
STTP200: Programs to Run Immediately After
Update
The following programs must be executed once after the installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTP/MIG202_STTPS_IDX – Migration: Move STTPS Msgs. fr. std. AIF-Idx Table to STTPS Idx Table
1.4.8 Installing SAP Advanced Track and Trace for
Pharmaceuticals 2.0, FP03 (No Upgrade)
1.4.8.1
STTP200: Programs to Run Immediately After
Installing Before Starting Testing or Productive
Work
The following program must be executed once after installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTP/MIG20_AUTH
Execute transaction /STTP/OMSL_INIT on all development systems. After this initialization you can configure
the material number conversion routine via transaction /STTP/OMSL. For more information, see chapter
Country-specific Customizing in the configuration guide for SAP Advanced Track and Trace for Pharmaceuticals
on the SAP Help Portal at http://help.sap.com/attp .
1.4.8.2
STTP200: Manual Steps After Update
For the Web-UI to function correctly, the following new service must be activated and the SICF node must be
started in Transaction /IWFND/MAINT_SERVIC:
● /STTP/ATT_COCKPIT_210_SRV
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
CONFIDENTIAL
19
1.4.8.3
STTPEC200: Programs to Run Immediately After
Installing, Before Starting Testing or Productive
Work
The following programs must be executed once after installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTPEC/MIG20_AUTH
1.4.8.4
STTPEW200: Programs to Run Immediately After
Installing Before Starting Testing or Productive
Work
The following programs must be executed once after installation of SAP Advanced Track and Trace for
Pharmaceuticals 2.0 or higher:
● /STTPEW/MIG20_AUTH
1.4.9 Converting or Upgrading from SAP Advanced Track and
Trace for Pharmaceuticals ECC or SAP S/4HANA
1610/1709 Add-On to SAP S/4HANA 1809 FPS01 or
Higher
The following sections list the minimum programs to be executed. For more details on the conversion process,
- S/4HANA 1809+ Conversion/Upgrade Guidelines for Advanced Track & Trace.
see SAP Note: 2716224
1.4.9.1
STTPEC200 or Higher / STTPEC800: Programs to
Run Before Update
The following programs must be executed once before the conversion/upgrade to SAP S/4HANA 1809 FPS01
or higher:
● /STTPEC/MIG_S4GTINSYNC - SAP S4 HANA Migration Report: Migrating GTIN to MEAN table
This report handles the migration of GTINs from MARM-/STTPEC/GTIN field into the relevant standard EAN11
field within MEAN table with an appropriate EAN category that specifies the EAN to be a compliant GTIN14.
20
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Getting Started
2
About SAP Advanced Track and Trace for
Pharmaceuticals
This section provides an overview of SAP Advanced Track and Trace for Pharmaceuticals , including relevant
business scenarios and technical system landscape.
SAP Advanced Track and Trace for Pharmaceuticals provides a corporate serialization repository and
management solution for regulatory reporting, supporting compliance with international legislation to fight
falsified medicines.
It allows you to do the following:
● Report serial number events to authorities and business partners, enabling compliance to international
legislation
● Integrate with SAP S/4HANA, ERP, warehouse management systems, and packaging lines
● Capture serial numbers from packaging lines and warehouse systems and store serial number events
centrally
● Track and Trace serial number of medicinal sales units and their aggregations
● Track batches and their serial number relation
● Globally manage number ranges and randomized or sequential serial number lists
● Browse and effect internal reporting on the usage and distribution of serial numbers globally
2.1
Software Units of SAP Advanced Track and Trace for
Pharmaceuticals
The following list contains the software units that you require to set up your SAP Advanced Track and Trace for
Pharmaceuticals system landscape:
Software Unit
Release
SAP Advanced Track and Trace for Pharmaceuticals 2.0
STTP 200
SAP Application Interface Framework 3.0 (component AIF)
702
CDBASIS 1.0
CDBASIS 100 SP02
SAP NetWeaver
740, SP07 or higher
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
21
If you want to use the ECC Add-On for SAP Advanced Track and Trace for Pharmaceuticals, then the following
software units are required for the ECC Add-On:
Software Unit
Release
ECC Add-On for SAP Advanced Track and Trace for Pharma­
STTPEC 200
ceuticals 2.0
CDBASIS 1.0
CDBASIS 100 SP02
SAP ERP
SAP ERP 6.0 (EHP 6, SP02 or EHP7 or EHP8)
SAP NetWeaver
731 (EHP6) or 740 (EHP7/EHP8)
If you want to use the EWM Add-On for SAP Advanced Track and Trace for Pharmaceuticals, then the following
software units are required for the ECC Add-On:
Software Unit
Release
EWM Add-On for SAP Advanced Track and Trace for Phar­
STTPEW 200
maceuticals 2.0
CDBASIS 1.0
CDBASIS 100 SP02
SAP EWM
SCMEWM 702 or 900 or
SCMEWM 910 or 920 or 930 or 940
SAP NetWeaver
Depends on SCMEWM
If you use the ECC Add-On for SAP Advanced Track and Trace for Pharmaceuticals (STTPEC 200 and higher) or
SAP S/4 HANA Add-on (STTPEC 800) and want to convert to SAP S/4HANA 1809 or higher, then the following
software units are required:
Software Unit
Release
SAP Advanced Track and Trace for Pharmaceuticals 2.0, Fea­ STTP 200 FP02 or higher
ture Package 02
2.2
Software Component Matrix
This section provides an overview of which business scenario of SAP Advanced Track and Trace for
Pharmaceuticals uses which software unit.
Supported Integration Scenarios
● Integrate SAP ERP with SAP Advanced Track and Trace for Pharmaceuticals
22
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
● Integrate Local and Central SAP Advanced Track and Trace for Pharmaceuticals
● Integrate SAP EWM with SAP ERP and SAP Advanced Track and Trace for Pharmaceuticals
● Integrate SAP S/4HANA with SAP Advanced Track and Trace for Pharmaceuticals
The above mentioned integration scenarios can be combined with each other.
Integration scenario – Integrate SAP ERP with SAP Advanced Track and Trace for Pharmaceuticals
SAP Advanced Track and Trace for Pharmaceuticals can be connected with SAP ERP in order to integrate
master data and transactional data and integration with warehouse processing through SAP Advanced Track
and Trace for Pharmaceuticals functions.
Integrate SAP ERP with SAP Advanced Track and Trace for Pharmaceuticals
SAP Advanced Track and Trace for Pharmaceuticals System:
Software Unit
Obligatory or Optional
SAP Advanced Track and Trace for Pharmaceuticals 2.0
Obligatory
(STTP200)
SAP Application Interface Framework 3.0
Obligatory
CDBASIS100
Obligatory
SAP NetWeaver
Obligatory
SAP ERP System
Software Unit
Obligatory or Optional
ECC Add-On for SAP Advanced Track and Trace for Pharma­
Obligatory
ceuticals 2.0 (STTPEC 200)
CDBASIS100
Obligatory
SAP ERP
Obligatory
SAP NetWeaver
Obligatory
Integration scenario – Integrate Local and Central SAP Advanced Track and Trace for Pharmaceuticals
SAP Advanced Track and Trace for Pharmaceuticals supports different deployment models. The recommended
deployment is to have one Central Repository System only.
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
23
Besides this, SAP Advanced Track and Trace for Pharmaceuticals also supports a distributed deployment of
one Central SAP Advanced Track and Trace for Pharmaceuticals Instance and one or more local SAP Advanced
Track and Trace for Pharmaceuticals Instances.
Integrate Local and Central SAP Advanced Track and Trace for Pharmaceuticals
All instances of SAP Advanced Track and Trace for Pharmaceuticals must have the same software units
installed:
Software Unit
Obligatory or Optional
SAP Advanced Track and Trace for Pharmaceuticals 2.0
Obligatory
(STTP 200)
SAP Application Interface Framework 3.0 (component AIF)
Obligatory
CDBASIS100
Obligatory
SAP NetWeaver
Obligatory
Integration Scenario-Integrate SAP EWM with SAP ERP and SAP Advanced Track and Trace for
Pharmaceuticals
SAP Advanced Track and Trace for Pharmaceuticals can be connected with SAP ERP in order to integrate
master data and transactional data and with EWM for warehouse processing through SAP Advanced Track and
Trace for Pharmaceuticals functions.
24
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
Integrate SAP EWM with SAP ERP and SAP Advanced Track and Trace for Pharmaceuticals
SAP Advanced Track and Trace for Pharmaceuticals System:
Software Unit
Obligatory or optional
SAP Advanced Track and Trace for Pharmaceuticals 2.0
Obligatory
(STTP200)
SAP Application Interface Framework 3.0
Obligatory
CDBASIS100
Obligatory
SAP NetWeaver
Obligatory
SAP ERP System
Software Unit
Obligatory or optional
ECC Add-On for SAP Advanced Track and Trace for Pharma­
Obligatory
ceuticals 2.0 (STTPEC 200)
CDBASIS100
Obligatory
SAP ERP
Obligatory
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
25
Software Unit
Obligatory or optional
SAP NetWeaver
Obligatory
SAP EWM System
Software Unit
Obligatory or optional
EWM Add-On for SAP Advanced Track and Trace for Phar­
Obligatory
maceuticals 2.0 (STTPEW 200)
CDBASIS100
Obligatory
SAP SCMEWM
Obligatory
SAP NetWeaver
Obligatory
Integration scenario – Integrate SAP S/4HANA with SAP Advanced Track and Trace for Pharmaceuticals
SAP Advanced Track and Trace for Pharmaceuticals can be connected with SAP S/4HANA in order to integrate
master data and transactional data and integration with warehouse processing through SAP Advanced Track
and Trace for Pharmaceuticals functions.
SAP Advanced Track and Trace for Pharmaceuticals System:
Software Unit
Obligatory or optional
SAP Advanced Track and Trace for
Obligatory
Comments
Pharmaceuticals 2.0 (STTP200)
SAP Application Interface Framework
Obligatory
3.0
CDBASIS100
Obligatory
SAP NetWeaver
Obligatory
SAP S/4HANA System
26
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
Software Unit
Obligatory or optional
S/4 HANA Add-On for SAP Advanced
Obligatory
Track and Trace for Pharmaceuticals
2.0 (STTPEC 800)
CDBASIS100
Obligatory
S/4 HANA 1610 or S/4 HANA 1709
Obligatory
2.3
System Landscape for SAP Advanced Track and Trace
for Pharmaceuticals
 Caution
We strongly recommend that you use a minimal system landscape for test and demo purposes only. For
performance, scalability, high availability, and security reasons, do not use a minimal system landscape as
your production landscape.
SAP Advanced Track and Trace for Pharmaceuticals offers various system landscape options depending on
customers’ business requirements and possible system deployments. SAP Advanced Track and Trace for
Pharmaceuticals can be installed on any SAP system that meets the basic NW requirements.
However, SAP recommends installation of the productive instance of SAP Advanced Track and Trace for
Pharmaceuticals on a separate hardware because very high data volumes are expected.
The solution also supports a distributed SAP Advanced Track and Trace for Pharmaceuticals landscape with
one central and one or more decentralized SAP Advanced Track and Trace for Pharmaceuticals instances as
shown in the integration scenarios above. However, the installation stack on each of the systems is the same as
above.
Also for the third integration scenario, the installation stack for the SAP Advanced Track and Trace for
Pharmaceuticals instance remains the same as given above.
2.4
Overall Implementation Sequence
Purpose
The following table describes the overall installation sequence for SAP Advanced Track and Trace for
Pharmaceuticals. This table contains all available software units. However, to implement a specific scenario,
you only need a subset of available software units. Some are only required for special processes
Process
Implementation Sequence for SAP Advanced Track and Trace for Pharmaceuticals
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
27
Action
Step
1
[Required Documentation]
Remarks/Subsequent Steps
Installation of SAP NetWeaver 740 as
SAP Help Portal at http://
described in a separate master guide
help.sap.com/nw74
[Master Guide]
SAP Help Portal at http://
Installation of SAP NetWeaver 750 as
help.sap.com/nw75
described in a separate master guide
[Master Guide]
2
SAP Application Interface Framework
Refer to the Master guide on SAP Help
3.0 as described in the separate master Portal at http://help.sap.com/aif
guide
[Master Guide]
3
Installation of CDBASIS 100
See note 2304555
2304555
4
Installation of SAP Advanced Track and
See note 2203586
Trace for Pharmaceuticals 2.0
2203586
28
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
Action
Step
5
[Required Documentation]
Remarks/Subsequent Steps
Activate BC sets offered for SAP Ad­
You need to first activate the AIF BC-set
vanced Track and Trace for Pharma­
for the namespaces (/STTP/
ceuticals
The following hierarchical BC sets con­
CUST_AIF_01...) before you can activate
any other AIF related BC-set.
tain all needed customizing settings.
The AIF BC-sets are included within the
You can activate the BC set as a whole
respective overall BC-sets for SAP Ad­
or any sub BC set.
vanced Track and Trace for Pharma­
●
●
/STTP/
ceuticals
CUST_ALL_WITH_CNT_2_0 Short
Hint: In case you encounter issues with
Text: SAP Advanced Track & Trace
activation of a hierarchical BC set
(Release 2.0): Cust with Countries
please try to activate the BC set multi­
/STTP/CUST_ALL_WO_CNT_2_0
ple times. In most cases the issue will
Short Text: SAP Advanced Track &
be gone then.
Trace (Release 2.0): Cust without
Countries
For Feature Pack 01 activate the follow­
ing BC sets, in addition.
●
/STTP/CUST_AIF_2_1 Short Text:
SAP Advanced Track & Trace (Re­
lease 2.0 FP01): AIF Customizing
●
/STTP/CUST_ATT_2_1 Short Text:
SAP Advanced Track & Trace (Re­
lease 2.0 FP01): ATT Customizing
For Feature Pack 02 activate the follow­
ing BC sets, in addition.
●
/STTP/CUST_AIF_2_2 Short Text:
SAP Advanced Track & Trace (Re­
lease 2.0 FP02): AIF Customizing
For Feature Pack 03 activate the follow­
ing BC sets, in addition.
●
/STTP/CUST_AIF_2_3 Short Text:
SAP Advanced Track & Trace (Re­
lease 2.0 FP03): AIF Customizing
[Master Guide]
6
Setup SAP Advanced Track and Trace
for Pharmaceuticals specific AIF Cus­
tomizing
See the configuration guide for SAP Ad­
vanced Track and Trace for Pharma­
ceuticals on the SAP Help Portal at
http://help.sap.com/attp
[Configuration Guide]
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
29
Action
Step
[Required Documentation]
Remarks/Subsequent Steps
7
Customize settings for SAP Advanced
[Configuration Guide]
See the configuration guide for SAP Ad­
vanced Track and Trace for Pharma­
ceuticals on the SAP Help Portal at
http://help.sap.com/attp
Optional: Configure Web UI
Optional step in case Web UI shall be
Track and Trace for Pharmaceuticals
8
used
[Configuration Guide]
See the configuration guide for SAP Ad­
vanced Track and Trace for Pharma­
ceuticals on the SAP Help Portal at
http://help.sap.com/attp
Implementation Sequence for ECC Add-On for SAP Advanced Track and Trace for Pharmaceuticals
Only relevant in case Integration with SAP ERP is in scope.
Action
Step
[Required Documentation]
Remarks/Subsequent Steps
1
Installation of CDBASIS 100 SP02
See note 2304555
[SAP Note: 2304555
]
In case of CDBASIS 100 SP1 you need
to implement the following notes before
upgrading to ATTP 2.0 FP01:
2
[SAP Note: 2474699
]
[SAP Note: 2475748
]
Installation of ECC Add-On for SAP Ad­
See note 2213945
vanced Track and Trace for Pharma­
ceuticals
[SAP Note: 2213945
3
]
Customize settings for SAP Advanced
Track and Trace for Pharmaceuticals
Add-On for ECC
See the configuration guide for SAP Ad­
vanced Track and Trace for Pharma­
ceuticals on the SAP Help Portal at
http://help.sap.com/attp
[Configuration Guide]
Implementation Sequence for SAP S/4HANA 1610 and 1709 Add-On for SAP Advanced Track and Trace for
Pharmaceuticals
Only relevant in case Integration with SAP ERP is in scope.
30
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
Action
Step
[Required Documentation]
Remarks/Subsequent Steps
1
Installation of CDBASIS 100 SP02
See note 2304555
[SAP Note: 2304555
]
In case of CDBASIS 100 SP1 you need
to implement the following notes before
upgrading to ATTP 2.0 FP01:
2
[SAP Note: 2474699
]
[SAP Note: 2475748
]
Installation of S/4 HANA Add-On for
SAP Advanced Track and Trace for
service.sap.com/sap/support/notes/
Pharmaceuticals
2213945
[SAP Note: 2213945
3
See note at http://
]
Customize settings for SAP Advanced
You can access the latest version of this
Track and Trace for Pharmaceuticals
guide on the help portal at http://
Add-On for ECC
help.sap.com/attp
[Configuration Guide]
Conversion sequence for SAP S/4 HANA 1809 FPS01 and higher
For information on the conversion sequence for SAP S/4 HANA 1809 FPS01 and higher, see SAP Note:
2716224
- S/4HANA 1809+ Conversion/Upgrade Guidelines for Advanced Track & Trace.
Implementation Sequence for EWM Add-On for SAP Advanced Track and Trace for Pharmaceuticals
Only relevant in case Integration with SAP EWM is in scope.
Action
Step
[Required Documentation]
Remarks/Subsequent Steps
1
Installation of CDBASIS 100
See note 2304555
[SAP Note: 2304555 [HYPERLINK RE­
MOVED] ]
2
Installation of EWM Add-On for SAP Ad­ See note 2380100
vanced Track and Trace for Pharma­
ceuticals
[SAP Note: 2380100 [HYPERLINK RE­
MOVED]]
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
31
Action
Step
[Required Documentation]
Remarks/Subsequent Steps
3
Customize settings for SAP Advanced
See the configuration guide for SAP Ad­
vanced Track and Trace for Pharma­
ceuticals on the SAP Help Portal at
http://help.sap.com/attp
Track and Trace for Pharmaceuticals
Add-On for EWM
[Configuration Guide]
Third Party Libraries Used by SAP Advanced Track and Trace for Pharmaceuticals
JSON2XML by Stefan Goessner
The warehouse manager app introduced with ATTP 200 FP01 uses a third-party library for converting JSON to
XML to generate the EPCIS XML structure. The library is used as of version 0.9 (2006) and references the
license GNU LGPL 2.1.
32
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
About SAP Advanced Track and Trace for Pharmaceuticals
3
Security Information for SAP Advanced
Track and Trace for Pharmaceuticals
This section deals with security topics relevant for SAP Advanced Track and Trace for Pharmaceuticals. The
solution is built on a SAP NetWeaver 740 (or higher) system. Therefore, the corresponding security settings
also apply to SAP Advanced Track and Trace for Pharmaceuticals.
3.1
Other Required Documents for Security
This section provides an overview of other security-related documents.
SAP Advanced Track and Trace for Pharmaceuticals is based on SAP NetWeaver. This means that the
corresponding security guides also apply.
Resource
Where to Find It
SAP NetWeaver Security Guide
Go to the SAP Help Portal at http://help.sap.com/nw and se­
lect the appropriate release. The security guide is in the sec­
tion Security on the product page.
3.2
Authorization Concept
This section describes the authorizations available in SAP Advanced Track and Trace for Pharmaceuticals.
SAP Advanced Track and Trace for Pharmaceuticals allows you to make specific authorization settings for all
business entities of the solution. The following sections provide information about the authorization concept
and the authorization objects used.
In general, authorization checks are executed when searching, displaying or updating data within the repository
system.
3.2.1 Authorizations in Master Data Management
Following Master Data Management entities exist in SAP Advanced Track and Trace for Pharmaceuticals:
● Business Partners
● Trade Items
● Locations
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
33
● Systems
3.2.1.1
Authorization Object for Business Partner /
STTP/BUP
The section lists the security-relevant authorization objects that are used by SAP Advanced Track and Trace for
Pharmaceuticals.
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
01 Create or generate
02 Change
03 Display
06 Delete
07 Activate, generate
/STTP/BPT
Business Partner Role Type
1 Customer
2 Vendor / Supplier
3 Contract Manufacturer
4 Service Provider
5 Own Organization
/STTP/LQS
Logical System Group
Logical System Group can be defined in
Customizing using transaction Define
Logical System Groups . In Customizing,
go to
SAP Advanced Track and Trace
System Customizing
. Alternatively,
use transaction /STTP/LOGQS.
34
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
3.2.1.2
Authorization Object for Trade Item /STTP/PRD
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
01 Create or generate
02 Change
03 Display
06 Delete
07 Activate, generate
/STTP/CTY
Country Code
Country key as available in domain
LAND1 (value table T005)
/STTP/LQS
Logical System Group
Logical System Group can be defined in
Customizing using transaction Define
Logical System Groups . In Customizing,
go to
SAP Advanced Track and Trace
System Customizing
. Alternatively,
use transaction /STTP/LOGQS.
The authorization object is used within the transaction /STTP/COCKPIT – Advanced Track & Trace Data
Cockpit to check whether the user is allowed to create, change, display, delete or activate trade items.
Furthermore, the authorization object is used within the following transactions :
● India master data reporting
○ /STTP/IN_PRD_DETAILS – India: Product Details. The user needs activity 02-change to enter the
transaction and to trigger the product details reporting.
● Europe master data reporting
○ /STTP/EU_PRD_MD_DISP – Product Master Data Single Reporting . The user needs activity 02change to enter the transaction and to trigger the product details reporting.
○ /STTP/EU_PRD_MD_MASS – Product Master Data Mass Reporting : The user needs activity 02-change
to enter the transaction and to trigger the product details reporting.
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
35
3.2.1.3
Authorization Object for Location /STTP/LOC
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
01 Create or generate
02 Change
03 Display
06 Delete
/STTP/LQS
Logical System Group
Logical System Group can be defined in
Customizing using transaction Define
Logical System Groups . In Customizing,
go to
SAP Advanced Track and Trace
System Customizing
. Alternatively,
use transaction /STTP/LOGQS.
3.2.1.4
Authorization Object for System /STTP/SYT
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
01 Create or generate
02 Change
03 Display
06 Delete
3.2.2 Authorizations in Serial Number Management
Following Serial Number Management entities exist in SAP Advanced Track and Trace for Pharmaceuticals:
● Range Definitions
● Ranges
● Range Requests
● Serial Numbers
36
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
3.2.2.1
Authorization Object for Serial Number
Management /STTP/SNR
All serial number management entities share one common authorization object as there is no work separation
in serial number management entities like this is possible for the master data entities. The only entity which
requires special treatment are the serial numbers as they are very sensitive. To display serial numbers, the
special activity 61-Export must be assigned to the user.
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
01 Create or generate
02 Change
03 Display
06 Delete
07 Activate, generate
49 Request
61 Export
The following specifics apply to the users that create or process/respond to serial number requests
● Creating serial number requests (serial number requestor)
○ The user who creates serial number requests in a system must have the following authorization: /
STTP/SNR + activities: 01-create, 02-change.
● Responding to serial number requests (serial number provider)
○ The user which is used to receive, process and reply to a serial number request in a system must have
the following authorization: /STTP/SNR + activities 02-change and 49-request
3.2.3 Authorizations in Object and Event Repository
Foreword
Based on customer feedback, the maintenance of the repository authorization was improved in many aspects.
As a consequence you need to set up the authorization data from a scratch after migration from release 1.0 to
release 2.0. The existing transaction from release 1.0 /STTP/DM_AUTH, and also the database table from
release 1.0 /STTP/DM_AUTH are retired with release 2.0.
However the general functioning of the authorization concept has not changed. So the authorization concept
for repository data still works based on GLNs as in release 1.0. Only how the GLNs are assigned to the user has
changed.
The following changes were realized :
● Authorizations are managed with application tables instead of Customizing tables
● GLNs can be grouped and the group can be assigned to the user
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
37
● A “role-like approach” was introduced which enables “automated” assignment of authorizations based on
SAP roles assigned to the user.
As migration is not possible, you have to define the new authorizations manually. If you use the “role like
approach”, the effort will be manageable.
New maintenance of repository authorizations
In the new approach, you define GLN groups and assign GLNs to the groups. In a second step you assign the
GLN group to the users. All underlying database tables are application tables now.
You can name the GLN group like SAP roles, and select the checkbox Corresponds to Role in the GLN group
maintenance. Then you can execute a transaction / report which automates the GLN group to user
assignment.
The authorization concept for transactional data is based on location information (GLN). To maintain it go to
the
SAP Easy Access screen
SAP Advanced Track and Trace
Repository Customizing
Authorization
Management . Alternatively you can also maintain this in Customizing. Here you can find the following entries:
● Transaction: /STTP/GLNGRP_DEF – Define and Manage GLN Group for Repository Layer Authorization
● Transaction: /STTP/USR_GLNGRP – Assign GLN Group to User for Repository Layer Authorization
● Transaction: /STTP/USR_SYNC – Synchronize User to GLN Group Assignment with User to SAP Role
Assignment
Define and Manage GLN Group for Repository Layer Authorization
To define or maintain GLN groups,use transaction /STTP/GLNGRP_DEF – Define and Manage GLN Group for
Repository Layer Authorization.
● GLN Group
○ You can define the GLN Group ID, the description, and select the checkbox Corresponds to Role
○ Checkbox Corresponds to Role: Only those GLN groups with this checkbox selected will be considered
by the report below to synchronize the user to GLN group assignment.
● Assign GLNs to GLN group
○ GLN: Assign explicit GLNs or alternatively an asterisk (*) if the group is supposed to include all GLNs
○ Display: Grant display authorization for the particular GLN
○ Change: Grant change authorization for the particular GLN
 Tip
Change authorization includes display authorization. If you only select the checkbox Change, then upon
save the checkbox Display is selected automatically. Also it is not possible to deselect a Display
authorization checkbox without first deselecting the Change authorization checkbox.
The transaction is protected via authorization object /STTP/GLNG: GLN Group Maintenance
The following activities are supported:
● 01: Create or Generate
● 02: Change
● 03: Display
● 06: Delete
Assign GLN Group to User for Repository Layer Authorization
38
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
To display the current GLN group to user assignment and make changes to this assignment or create new
assignments, use transaction /STTP/USR_GLNGRP – Assign GLN Group to User for Repository Layer
Authorization.
● User: User name
● GLN Group: GLN group as defined above. You can assign every GLN group once to a user.
● Valid from / to: Validity of the assignment of a GLN group. The user can see data of the GLNs assigned to
the GLN group only if the current date lies within the validity period.
A user can have one or several GLN groups assigned. If the user has more GLN groups assigned, then the
authorization is additive and the highest authorization is considered.
 Example
● GLN group 1
○ GLN 1 – Display: yes, Change: no
○ GLN 2 – Display: yes, Change: no
● GLN group 2
○ GLN 1 –Display: yes, Change: yes
○ GLN 3 – Display: yes, Change: yes
● Resulting authorizations if a user has both GLN groups 1 and 2 assigned
○ GLN1: Display and Change because GLN group 2 has change flag set for GLN1
○ GLN 2: Display only
○ GLN3: Display and Change
The transaction is protected via authorization object /STTP/GLNU: User assignment to GLN group
The following activities are supported:
● 01: Create or Generate
● 02: Change
● 03: Display
● 06: Delete
Synchronize User to GLN Group Assignment with User to SAP Role Assignment
The transaction /STTP/USR_SYNC determines all GLN groups with the checkbox Corresponds to Role selected,
and checks whether an SAP role with the exact same name is assigned to any user in the system. If yes, then
the GLN group is assigned to this user along with the valid from and valid to of the SAP role assignment.
So although this approach does not fully implement the SAP role concept, it uses / leverages the role concept
in an intelligent way to automate the GLN group to user assignment.
As the transaction handles the GLN group to user assignment, it is also protected via authorization object /
STTP/GLNU: User assignment to GLN Group.
Checking Authorizations
A normal authorization check based on an authorization object works in the following way - a user selects a
certain number of objects and then, object by object, it is checked whether the user is authorized for certain
actions (for example, display or change) on this object. This approach works well when the data volume is low
to moderate. Therefore this approach is used, for example, in case of master data or serial number
management entities. When dealing with large data volumes however, this approach is not practical and would
result in unacceptable performance.
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
39
Therefore an alternative approach is used for the object event repository data (repository data) of SAP
Advanced Track and Trace for Pharmaceuticals. Instead of first selecting a huge amount of data and then
checking authorizations, and then excluding a large number of objects, this approach includes the authorized
GLNs into the query, and only selects data the user is authorized for. The end result is the same. The user
cannot query more than authorized, but the procedure is much more performant, because both the query, as
well as the authorization check, are handled in one step.
So in reality this is not an ‘authorization check’ but a ‘selection of authorized data’ which results in significantly
higher query performance.
The following entities exist in Object and Event Repository of SAP Advanced Track and Trace for
Pharmaceuticals:
● Events
● Objects of type serialized trade items (SGTINs), serialized containers (SSCCs) and Lots (LGTINs)
● Business Transactions
● Reporting Events
Displaying of Data (Check Whether Display Allowed)
The authorization check is done when searching for authorized GLNs.
Objects of Type Serialized Trade Items (SGTINs), Serialized Containers (SSCCs) and Lots (LGTINs)
● Single object query (through the search parameter object ID): Authorization check (display allowed) on
actual business location GLN plus check against business locations of all events of this object. If the user is
authorized for one of the GLNs, the instance can be seen.
● Mass queries (all other search parameters except object ID): Authorization check (display allowed) on
actual business location GLN. If user is authorized for these GLNs, the instance can be seen.
 Note
The user will see potentially less objects in the mass query as the check for historic object locations is not
possible out of performance point of view.
Events
● Authorization check (Display allowed) against GLN of Business Location, read point, and all source or
destination GLNs. If the user is authorized for any of these GLNs the instance can be seen.
Reporting Events
● Authorization check (Display allowed) against GLN of reporting event. If user is allowed for this GLN then
the instance can be seen.
Transactions
● Authorization check (Display allowed) against GLNs of Business Transaction or ship from, ship to, sold
from or sold to location. If user is authorized for any of these GLNs the instance can be seen.
Changing of Data (Check Whether Change Allowed)
Changing of object and event data typically happens through event messages which are processed in the
system with a remote user. This remote user needs to be entered to the GLN group to user assignment with a
GLN group assigned that contains display and change authorization for all relevant GLNs or with asterisk (*).
Besides, this data can be changed only through the post manual event UI which is accessible through Data
Cockpit. When calling the post manual event UI, the GLN is not known. So, before entering the UI, only basic
40
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
checks can be done to check if the user is authorized to change data for any GLN (If the user is not authorized,
the user gets an error message saying that there is no authorization to change data). Then, the user enters the
event data and also data like the read point GLN and extension. The user also selects all the serialized objects
that will participate in the event. When posting the event, the following checks are made:
● Check whether the user is authorized to change data for the given read point GLN
● Check whether the user has authorization to change data for the current business location GLN of all the
objects participating at the event.
3.2.4 Authorization Object for Authentication Request /
STTP/AUTH
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
01 Create or Generate
03 Display
Creating an Authentication Request requires authorization for /STTP/AUTH with activity 01-Create or Generate.
Displaying an Authentication Request in the data cockpit requires authorization for /STTP/AUTH with activity
03-Display.
3.2.5 Further Authorizations
3.2.5.1
Authorization Object for Distribution of Data /
STTP/DIS
This authorization object is used in case of distributed setup of SAP Advanced Track and Trace for
Pharmaceuticals with central and local systems.
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
16 Execute
69 Discard
70 Administer
85 Reverse
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
41
Within the central instance both Customizing and master data is distributed from the central to all local
instances. The user who initiates the distribution of Customizing and/or master data needs to have
authorization for object /STTP/DIS and activity 16-Execute.
Moreover, within both central and local instance, the replication of repository data can be triggered via rule
BR_DISTR_DM – Business Rule: Distribution of transaction data. Similarly, the user that is used for event
processing and rules processing also needs the authorization for object /STTP/DIS and activity 16-Execute. In
case of failure in the replication of repository data, the complete RFC interface data is stored into replication
queues for later reprocessing. The user who reprocesses the replication queues needs to have authorization for
object /STTP/DIS and activity 16-Execute, 69-Discard, 70-Administer, 85-Reverse, depending on the intended
reprocessing action.
3.2.5.2
Authorization Object for South Korea Reporting /
STTP/KRRP
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
01 Create or Generate
02 Change
03 Display
06 Delete
This authorization object is used within the BAPI /STTP/KR_MSTR_TMPL_RAW_MAINT. The BAPI offers the
possibility to create, change and delete data. The user calling the BAPI must have the corresponding actions
assigned.
Furthermore the authorization object is used by the transactions /STTP/KR_MSTR_TMP_RW – Korea Master
Template Raw Display and /STTP/KR_SPPL_DET_MS – Korea Mass Supply Details Reporting.
In case of /STTP/KR_MSTR_TMP_RW – Korea Master Template Raw Display the user must have the activity 03Display assigned to enter the transaction and to search and display data. In order to trigger regulatory
reporting the user also needs the activity 02-Change.
In case of /STTP/KR_SPPL_DET_MS – Korea Mass Supply Details Reporting the user must have the activity 02Change assigned.
3.2.5.3
Authorization Object for Data Archiving S_ARCHIVE
Authorization Field
Description
Authorization Object Settings
APPLIC
Application Area
Assign: All values
42
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
Authorization Field
Description
Authorization Object Settings
ARCH_OBJ
Archiving Object
Assign * if role should be able to ar­
chive all objects
Or assign specific objects
/STTP/EVT – SAP ATTP: Archive
Event Data
/STTP/OBJ – SAP ATTP: Archive
Object Data
/STTP/REVT – SAP ATTP: Archive
Report Event Data
/STTP/SNLI – SAP ATTP: Archive
Serial Number Data
/STTP/TRN – SAP ATTP: Archive
Transaction Data
ACTVT
Activity
01 Create or Generate
02 Change
03 Display
3.2.5.4
Authorizations for Maintenance Views
In addition to the authorization object, an authorization group has been assigned to each maintenance view /
underlying views of view clusters according to the delivery class:
● Delivery class = E / C: Authorization Group = ATTC
● Delivery class = A: Authorization Group = ATTO
● Delivery class = S: No Authorization Group.
3.2.5.5
Report / Transaction Authorizations
Authorization checks are run for all transactions or reports with configuration character as follows:
Authorization Object
Transaction
View
Authorization Object
Authorization Field
Settings
/STTP/USR_GLNGRP
/STTP/V_USR_GLNG
/STTP/GLNU
Activity
02 Change
– change mode
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
43
Authorization Object
Transaction
View
Authorization Object
Authorization Field
Settings
/STTP/V_USR_GLNG
/STTP/GLNU
Activity
03 Display
/STTP/V_GLNGR_GL– /STTP/GLNG
Activity
02 Change
Activity
03 Display
– display mode
/STTP/GLNGRP_DEF
change mode
/STTP/V_GLNGR_GL– /STTP/GLNG
display mode
Please find more details on transactions/STTP/GLNGRP_DEF and /STTP/USR_GLNGRP in chapter
“Authorizations in Object and Event Repository”.
Authorization Object Set­
Report
Authorization Object
Authorization Field
tings
/STTP/MIG20_CUST
/STTP/CO
Activity
65 Reorganize
/STTP/CO
Activity
02 Change
/STTP/USR_SYNC
/STTP/GLNU
Activity
02 Change
/STTP/DISTR_CUST
/STTP/DIS
Activity
16 Execute
/STTP/
MI­
GRATE_LOC_GLN_TO_HIST
/STTP/
MI­
GRATE_BUP_GLN_TO_HIST
/STTP/
MIGRATE_INIT_ROLE_VAR
/STTP/MD_MIGRA­
TION_BUP_REG
/STTP/
MI­
GRATE_NROBJ_TO_GS1_GC
P
/STTP/CHECK_DM
/STTP/CHECK_MD
/STTP/ID_GCP_DELETE
/STTP/ID_GCP_MGMT
/STTP/DISTR_MD
44
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
Authorization Object Set­
Report
Authorization Object
Authorization Field
tings
/STTP/DISTR_QUEUE /
/STTP/DIS
Activity
16 Execute
STTP/DISTR_QCLEANUP
69 Discard
70 Administer
85 Reverse
/STTP/
/STTP/REP
Activity
16 Execute
Regulatory Reporting Coun­
AR Argentina
REP_AR_ALERTED_DEL
/STTP/
try Pack
REP_AR_HNDL_UNCNF_TR
N
/STTP/
/STTP/REP
Activity
16 Execute
Regulatory Reporting Coun­
CN China
RR_CN_CODE_REPLACE
try Pack
/STTP/
/STTP/REP
Activity
16 Execute
Regulatory Reporting Coun­
TR Turkey
RR_TR_TRNFPACK_PROC­
ESS
try Pack
/STTP/
/STTP/REP
Activity
16 Execute
REP_SPC_SEND_EPCIS_NTF
ATTP
/STTP/RR_IN_PRD_DETAILS /STTP/REP
Regulatory Reporting Coun­
SCP Supply Chain Notifica-
try Pack
tions
Activity
16 Execute
Regulatory Reporting Coun­
IN India
try Pack
/STTP/EU_MAH_WS_PROF
/STTP/REP
Activity
70 Administer
Regulatory Reporting Coun­
EU European Union
try Pack
/STTP/EU_PACK_TYPE
/STTP/REP
Activity
70 Administer
Regulatory Reporting Coun­
EU European Union
try Pack
/STTP/EU_FORM
/STTP/REP
Activity
70 Administer
Regulatory Reporting Coun­
EU European Union
try Pack
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
45
Authorization Object Set­
Report
Authorization Object
Authorization Field
tings
/STTP/
/STTP/REP
Activity
16 Execute
Regulatory Reporting Coun­
EU European Union
RR_EU_PRD_MD_DISP
/STTP/
try Pack
RR_EU_PRD_MD_MASS
/STTP/
/STTP/REP
Activity
75 Remove
Regulatory Reporting Coun­
EU European Union
RR_EU_BTCH_RECALL
try Pack
/STTP/RR_EU_HUB_PSR
/STTP/REP
Activity
70 Administer
Regulatory Reporting Coun­
EU European Union
try Pack
/STTP/AUTH_TEST_REPORT /STTP/TEST
Activity
16 Execute
/STTP/SNR_USEDUP_TEST
/STTP/
INT_TEST_BUP_MAINT
/STTP/
INT_TEST_BUP_READ
/STTP/
INT_TEST_LOC_MAINT
/STTP/
INT_TEST_LOC_READ
/STTP/
INT_TEST_MAT_MAINT
/STTP/
INT_TEST_MAT_READ
/STTP/INT_TEST_SNR_REQ
/STTP/
MD_TEST_BUP_CREATE
/STTP/
MD_TEST_LOC_CREATE
/STTP/
MD_TEST_PRD_CREATE
/STTP/
MD_TEST_PRD_DELETE
46
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
3.2.6 Authorizations in ECC Add-On and SAP S/4HANA for
SAP Advanced Track and Trace for Pharmaceuticals
3.2.6.1
Authorization Object for Data Integration to SAP
Advanced Track and Trace for Pharmaceuticals /
STTPEC/IN
Authorization Field
Description
/STTPEC/OT
Advanced Track and Trace Business Ob­ BUP Business Partners
ject Type
Authorization Object Settings
LOC Locations
MAT Materials
TRN Transactions
LOT Batches
ACTVT
3.2.6.2
Activity
16 Execute
Authorization Object for Test Programs /
STTPEC/TS
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
16 Execute
3.2.6.3
Authorizations for Maintenance Views
In addition to the authorization object, an authorization group has been assigned to each maintenance view /
underlying views of view clusters according to the delivery class:
● Delivery class = E / C: Authorization Group = ATTC
● Delivery class = A: Authorization Group = ATTO
● Delivery class = S: No Authorization Group.
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
47
3.2.6.4
Report / Transaction Authorizations
Authorization checks are run for all transactions or reports with configuration character as follows:
Authorization Object Set­
Report
Authorization Object
Authorization Field
tings
/STTPEC/MIG20_MARM­
/STTPEC/CO
Activity
65 Reorganize
/STTPEC/IN
Activity
16 Execute
Business Object Type
MAT Materials
Activity
16 Execute
Business Object Type
BUP Business Partners
Activity
16 Execute
Business Object Type
LOC Locations
Activity
16 Execute
Business Object Type
MAT Materials
Activity
16 Execute
Business Object Type
TRN Transactions
Activity
16 Execute
Business Object Type
LOT Batches
Activity
16 Execute
SYNC
/STTPEC/MIG20_CUST
/STTPEC/MIG_S4GTIN­
SYNC
/STTPEC/INTEGRATE_BUP
/STTPEC/INTEGRATE_LOC
/STTPEC/INTEGRATE_MAT
/STTPEC/INTEGRATE_TRN
/STTPEC/INTE­
/STTPEC/IN
/STTPEC/IN
/STTPEC/IN
/STTPEC/IN
/STTPEC/IN
GRATE_BATCH
/STTPEC/
/STTPEC/TS
WHS_TEST_TOOLBOX
3.2.7 Authorizations EWM Add-On for SAP Advanced Track
and Trace for Pharmaceuticals
48
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
3.2.7.1
Authorization Object for Test Programs /
STTPEW/TS
Authorization Field
Description
Authorization Object Settings
ACTVT
Activity
16 Execute
3.2.7.2
Authorizations for Maintenance Views
In addition to the authorization object, an authorization group has been assigned to each maintenance view /
underlying views of view clusters according to the delivery class:
● Delivery class = E / C: Authorization Group = ATTC
● Delivery class = A: Authorization Group = ATTO
● Delivery class = S: No Authorization Group.
3.2.7.3
Report / Transaction Authorizations
Authorization checks are run for all transactions or reports with configuration character:
Authorization Object Set­
Report
Authorization Object
Authorization Field
tings
/STTPEW/TS
/STTPEW/TS
Activity
16 Execute
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Security Information for SAP Advanced Track and Trace for Pharmaceuticals
CONFIDENTIAL
49
4
References
4.1
Documentation
The following table lists all documents mentioned in this administrator’s guide.
Title
Where to Find
Customizing for SAP Advanced Track and Trace for Pharma­
To access the Customizing structure in the system, use the
ceuticals
transaction SPRO
SAP Customizing Implementation Guide
SAP Advanced Track and Trace
Application Help
.
To access the application help for SAP Advanced Track and
Trace for Pharmaceuticals, go to SAP Help Portal at http://
help.sap.com/attp
Configuration Guide
You can access the latest version of this guide on SAP Help
Portal at http://help.sap.com/attp
Master Guide
SAP Help Portal at http://help.sap.com/attp
SAP Application Interface Framework 3.0
Master Guide
SAP Help Portal at http://help.sap.com/attp
SAP NetWeaver 7.4
Master Guide
SAP Help Portal at http://help.sap.com/attp
SAP ERP 6.0
4.2
SAP Notes
The following table lists the SAP Notes mentioned in this Administrator’s guide.
50
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
References
SAP Note Number
Title
Description
2203586
Release Strategy for the ABAP Add-on
Provides detailed information about
STTP
how to install SAP Advanced Track and
Trace for Pharmaceuticals 1.0
2068120
Runtime Error OBJECTS_TA­
Installation of this note is recom­
BLES_NOT_COMPATIBLE in Gateway
mended before using any OData serv­
Framework
ices with SAP Advanced Track and
Trace for Pharmaceuticals 1.0
2127137
Dump DYNP_TOO_MANY_RADIOBUT­
TONS_ON in sm59
Installation of this note is recom­
mended before starting to customize
SAP Advanced Track and Trace for
Pharmaceuticals 1.0
2213557
Implementation of BC Sets for AIF
This note must be installed before acti­
vating the BC set contents for the in­
cluded AIF interfaces
1926599
Error Handling: URL field is too short
Installation of this note is recom­
mended before using AIF with SAP Ad­
vanced Track and Trace for Pharma­
ceuticals interfaces
2134116
Error Handling: Displaying data content
Installation of this note is recom­
for web services created through up­
mended before using AIF with SAP Ad­
loading an WSDL file
vanced Track and Trace for Pharma­
ceuticals interfaces
2175174
Serialization: Option to skip serializa­
Installation of this note is recom­
tion under certain conditions
mended before using AIF with SAP Ad­
vanced Track and Trace for Pharma­
ceuticals interfaces
2177497
Runtime: wrong Serialization customiz­
Installation of this note is recom­
ing may leads to dump
mended before using AIF with SAP Ad­
vanced Track and Trace for Pharma­
ceuticals interfaces
2198348
Custom Time and Date will be overwrit­
Installation of this note is recom­
ten from /AIF/UTIL_ADD_MSG
mended before using AIF with SAP Ad­
vanced Track and Trace for Pharma­
ceuticals interfaces
2213945
Release Strategy for the ABAP Add-on
Provides detailed information about
for STTPEC
how to install SAP Advanced Track and
Trace for Pharmaceuticals Add-on for
ECC
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
References
CONFIDENTIAL
51
SAP Note Number
Title
Description
2008119
Error message when entering or dis­
Installation of this note is recom­
playing a date
mended before using the SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on
2079598
IWCOR – HTTP POST call fails when us­ Installation of this note is recom­
ing class CL_REST_HTTP_C
mended before using any OData service
within the SAP Advanced Track and
Trace for Pharmaceuticals Add-on for
ECC
2127137
Dump DYNP_TOO_MANY_RADIOBUT­
TONS_ON in sm59
Installation of this note is recom­
mended before starting to customize
the SAP Advanced Track and Trace for
Pharmaceuticals
2393995
Performance Improvement when Post­
Installation of this note is recom­
ing a Goods Issue
mended before using the SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on for ECC
2444191
Optimization of selection of document
Installation of this note is recom­
segments for materials
mended before using the SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on
2405762
Popup prevents shipping of an out­
Installation of this note is recom­
bound delivery via RF Dialog
mended before using the SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on
2318079
Alerting with SAP AIF not possible (fol­
No Alerts can be created with the SAP
low-up)
Application Interface Framework if an
error in the processing of an EPCIS
Message occurs
2368509
AIF/CREATE_ALERT: bug fix for
The user/role could not be correctly de­
BAdI /AIF/ALERT_DET_RECIPIENTS
termined due to wrong logic after
BAdI /AIF/ALERT_DET_RECIPIENTS in
Function Module /AIF/CREATE_ALERT.
2304555
2474699
52
CONFIDENTIAL
ABAP Add-on CDBASIS 100: Installa­
Provides detailed information on how to
tion, CSPs
install or upgrade CDBASIS 100
Dynamic Interface Mapping for Remote
This note is required to install STTPEC
Systems
200 FP1. It enables dynamic RFC calls.
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
References
SAP Note Number
Title
Description
2475748
Remote Type description
This note is required to install STTPEC
200 FP1. It enables dynamic RFC calls.
2380100
Release Strategy for the ABAP Add-on
Provides detailed information about
for STTPEW
how to install SAP Advanced Track and
Trace for Pharmaceuticals Add-on for
EWM
2616163
Redirect Inconsistency error in S/
Provides detailed information about
4HANA after installing Advanced Track
how to overcome the redirect inconsis­
& Trace add-on
tency error after installing SAP Ad­
vanced Track and Trace for Pharma­
ceuticals Add-on for SAP S/4HANA
2716224
S/4HANA 1809+ Conversion Guidelines Provides general information and impli­
for Advanced Track & Trace
cations of moving to SAP S/4HANA
1809 and higher.
2507495
S4TC STTPEC Master Check for S/4
System Conversion Checks
Installation of this note is required be­
fore starting the conversion/upgrade to
allow the move from a lower SAP S/
4HANA release or ECC to SAP S/
4HANA 1809 FPS01 or higher.
2733437
S/4HANA 1809+ Migration Report be­
Starting with SAP S/4HANA 1809
fore Conversion/Upgrade
FPS01, the ECC Add-on functionality is
now part of the SAP S/4 HANA core de­
livery. Therefore, the integration to Ad­
vanced Track and Trace for Pharma­
ceuticals does no longer require an ad­
ditional installation, but can be
switched on via a business function.
The move however includes changes to
the data dictionary and therefore re­
quires defined steps to be executed be­
fore the conversion/upgrade.
Specifically, the data from the MARM-/
STTPEC/GTIN field needs to be moved
to the standard EAN11 field within
MEAN table with a relevant EAN cate­
gory that specifies the EAN to be a
compliant GTIN14.
2745034
S/4HANA 1809+ Migration Report be­
fore Conversion/Upgrade DDICs for
SAP note 2733437
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
References
To implement SAP note 2733437
correctly, certain data dictionary ob­
jects need to be created.
CONFIDENTIAL
53
SAP Note Number
Title
Description
2699253
S4TC STTPEC Master Check for S/4
Prior to release of SAP S/4HANA 1809
System Conversion Checks (Update for FPS01, the conversion to SAP S/
FPS1)
4HANA 1809 was blocked as this would
cause data loss. To remove the block for
conversion for SAP S/4HANA 1809 or
higher, you need to implement this up­
date of the check class.
2719090
Activity Validation with BizTransaction­
Installation of this note is recom­
List
mended to allow the correct behavior of
the SAP S/4HANA 1809 FPS01 code
line.
54
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
References
5
Release Availability Information
For more information about currently available releases for SAP Advanced Track and Trace for
Pharmaceuticals, and for each release, the SAP standard software required to install and use the solution, see
http://www.service.sap.com/fbs/availability .
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Release Availability Information
CONFIDENTIAL
55
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
●
●
Links with the icon
: You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
●
The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
●
SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
Links with the icon
: You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features
Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
56
CONFIDENTIAL
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Important Disclaimers and Legal Information
Administrator's Guide for SAP Advanced Track and Trace for Pharmaceuticals
Important Disclaimers and Legal Information
CONFIDENTIAL
57
www.sap.com/contactsap
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form
or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for
additional trademark information and notices.
THE BEST RUN