Americas' SAP Users' Group

SAP Support for GS1 Standards

GS1 at Johns Hopkins
Dow Weeks, SAP Project Manager, Johns Hopkins Medical Center
Jon Arck, Director, SAP Healthcare Provider IBU
FIND YOUR EDGE
 Introduction: GS1 Data Standards
Global Location Number and Global Trade Item Number

 Poor data negatively impacts many areas in the extremely complex healthcare supply chain. Most
importantly, poor data jeopardizes patient safety when the supply chain fails to deliver the right medical
product of the right quality to the right patient at the right place and at the right time.
 As a result, supply chain data standards have been a major topic for the healthcare industry – and standards
adoption is now considered a requirement for effectively controlling both patient care quality and cost.
 In the past, there have been numerous discussions in healthcare regarding the value of standards and which
standards to use; now, the emphasis is on implementing them, and data standards developed by GS1 have
emerged as the pre-eminent system for healthcare.
 Industry groups (e.g., AHRMM, CHeS, and SMI) and various integrated delivery networks (IDNs), group
purchasing organizations (GPOs), and suppliers have endorsed GS1 standards. In addition, many of the
healthcare industry’s supply chain partners voluntarily established the end of 2010 -- known as the “2010
GLN Sunrise” -- for the adoption of GS1 Global Location Numbers (GLNs) to replace custom account numbers
and locations on specific EDI transactions.
 SAP supports GLNs, as well as Global Trade Item Numbers (GTINs), which have their own Sunrise target of
December 31, 2012. SAP also supports Traceability and ePedigree, which become law in California in 2015
and have legislation in place or pending in other states and countries.
 In this presentation, we’ll see how SAP solutions support GLN, GTIN, and other GS1 standards (often
exceeding them) to enable our customers to realize the benefits shown in various pilot programs, and we’ll
also learn how Johns Hopkins has implemented GS1 standards and lessons that were learned.
Topics

 What is GS1 and its standards?

 What are the GLN and GTIN and their role?
 Core and enhanced GLN functionality
 Implementing GS1 standards
 Core GTIN functionality
 Bar Coding and Labels
 Global Data Synchronization
 Supply Network Traceability/Traceability
 ePedigree/Authentication
 GS1 at Johns Hopkins
 Key Points
 GS1 (formerly, the Uniform Code Council, or UCC) identifies and proposes, through its membership
organizations, an integrated suite of global standards that provide supply chain visibility and improve
business processes through the accurate identification, capturing, and sharing of information regarding
products, services, locations, and assets
 Traceability (AKA Track-and-Trace) ensures patient safety by enabling track-and-trace and
authentication across the entire healthcare continuum – from manufacturing through patient
dispensing and reporting – and is a major tool to improve patient safety and care, and combat
increasing counterfeiting and diversion.

 Global Data Synchronization (GDS) ensures that suppliers and buyers share the same product and
service data to avoid procurement errors and lengthened procurement cycles
 SAP support for GLNs
• Procure-to-Pay transactions
• EDI Transaction Sets
• Healthcare IBU-sponsored GLN Enhancement Project extends core GLN functionality
 SAP Support for GTINs
• Source-to-Pay transactions
• EDI Transactions
• Mapping to Material Numbers
Why Adopt the Standards? Product Safety, as
numerous incidents occur and regulation increases

Serious recalls around the World

Increasing # regulations globally:

Example - Food Safety Bill H.R. 2749 – USA
New Requirements Imported Food New Enforcement Authority
-HACCP -Import certification -Criminal penalties
-Food Defense Plans -Product testing -Civil money penalties
-More frequent inspections -FDA registration (brokers) -Power to suspend license
-Broad access to records -Expedited entry (TBD) -Mandatory recall
Why Adopt the Standards?

COMPLIANCE
The accelerating trend towards regulation and mandates
on serialization requirements affects Healthcare, Life
Sciences, Higher ED & Research, Public Sector, Wholesale
Distribution, Consumer Products, Retail, Defense, High
Tech, Chemicals, and others

Regulations in place

Under development

Initiatives EFPIA ITU

Why Adopt the Standards?
“Implementing global standards across the entire healthcare
supply chain could save 22-43,000 lives and avert 0.7 to 1.4
million patient disabilities.“
“Rolling-out standards based systems could prevent tens of
billions of dollars’ worth of counterfeit drugs from entering the
legitimate supply chain.“
“Global standards could enable substantial safety benefits and
enable healthcare cost reduction of $40-100 billion".
"The healthcare industry faces a potentially costly patchwork of
requirements. Over the long term this patchwork could become
unworkable. The adoption of a single set of global standards will
cost significantly less than two, and far less than three or more".

From McKinsey & Company healthcare report "Strength in unity: The promise of global standards in healthcare,“ as presented at the 22nd Global
GS1 Healthcare conference in Portugal from 23rd to 25th October.
Why Adopt the Standards? ROI!
Documented benefits from “real-world” implementations
 Enhanced patient safety and brand protection
 Product traceability in a complex, global supply chain > brand protection, product authentication and reduction in risk of
counterfeiting, diversion, and fraud
 Reduced medication errors (patient/drug matching)*
 Product safety and support withdrawal or recall with near-real-time corrective action
 Comply with regulatory and quality standards and reduce cost of nonconformance
 BD/Mercy ROI study
 30% reduction in days payable outstanding
 73% reduction in discrepancies on POs
 Fewer stockouts due to simplicity offered to nursing staff for scanning barcodes at the bedside
 Improved sourcing of products by use of a barcode to determine right product and to reorder
 One source for product data > improved data accuracy
 Global uniqueness of data with no Unit of Measure errors
 Accurate product data (manufacturer ID, expirations, clinical attributes, etc.) > eliminates synchronization “work-around”
processes
 Improved process efficiency
 More accurate POs, invoicing, and payment processes
 Perfect alignment on contract eligibility
 Reduced billing and shipping errors / clean data on delivery locations and account info
 Better product and lot number tracking
 Greater insight into demand patterns and inventory management
 Integration with diverse mobile equipment (Tablet PC, BlackBerry, iPhone, other cell phones
 Reduced costs *Hospitals average 1 medication error per patient each day (Institute of Medicine)
 The Destination:
Patient Care and Safety

Effective, Efficient Business Processes

Global Data Synchronization
Supply Network Traceability
ePedigree/Authentication
 The Global Data Synchronization Network (GDSN) uses GLNs
and GTINs for Synchronizing Data among Trading Partners

GDSN-certified data pools serve as electronic catalogs for product, service, and location data, based on GS1 Identification Keys
(Global Trade Item Number, GTIN, and Global Location Number, GLN).
 They provide users with a single point for accessing the GDSN, a central location for storing and managing product and
service data and accessing the Global Registry.
 In addition to storing data, they facilitate synchronization of data among supply chain partners
Supply Network Traceability with ePedigree/Authentication
Customs
Will be supported in
his territory duties
Distributor
Wholesaler
Logistics Service Provider
Automates processes and
Hospital
authenticates goods
Packaging hierarchy changes
Manufacturer
Increases brand value
and sales volume
After-Sales Services
Capability to deliver Service
Patient
Safety is enhanced by
reduced risk of
medication errors and
Tracking of supplies, medications (even in unit doses), devices, and
counterfeits
equipment
Tracking of patients, assets, blood samples …
Patient / drug matching * PTA Product Tracking & Authentication
** OER Object Event Repository
Facilitated recall and returns
 Traceability using Patient Management, Event
Management, and Object Event Repository
SAP Object Event Repository
OER
Product Need a way to track a product as it SAP OER is an EPCIS-compliant enterprise level
serialization moves through the supply chain solution that serves as the system of record about
uniquely identified objects.
Need a way to store and manage EPCIS INTERFACE  tagged product flow at multiple locations,
Data capture multiple local processes
millions of transactions acquired by AUTO-ID Repository
& repository  interrelated tracking of child & parent objects
tracking product movement Event Management Analytics
Security Services and document associations
Industry Need a standards-based mechanism for  centralized data exchange with trading partners
Standard sharing data for multiple use cases  single set of interfaces and repository to
growing number of enterprise consuming
Secure data Need a way to share data with trading applications
EPCIS CAPTURE INTERFACE  support various data streams [EPC, Transaction,
exchange partners to identify business value
POS, …] to drive business value

Production on track Shipment received Send ASN Ship Ship Authenticate

Unpack Receive Dispense

Production completed
Authenticate Receive
Pack

Production Warehousing Distribution Sale

Suppliers
Retailers 3 PLs
Non-SAP
system Subcontractors
Authentication using GS1 EPCIS and SAP
Object Event Repository
Manufacturer
Hospital
2. Ship original item

1. Write authentication data into

central repository 4. Check original item
Original ID
Original TID
EPCIS identifier, 2D barcode, easy 0AF4439B07745113CE56
to duplicate

TID – Tamper proof security code

0AF4439B07745113CE56
3. Ship suspicious item. EPCIS identifier is
registered at central repository, but security
5. Check suspicious item code can not be copied
Original TID
Original Counterfeit TID EPCIS identifier, 2D barcode, easy
111122223333444455556666 to duplicate

TID – Tamper proof security code

Suspicious 111122223333444455556666

Counterfeiter
* PTA Product Tracking & Authentication
** OER Object Event Repository
SAP Support for GS1 Standards:
Making the Supply Chain Run Better
GS1 System of Standards & SAP Solutions

SAP Solution Offering

 EPCIS - certified Object Event Repository (OER)
 Secure Track –and-Trace
 ePedigree for anti-counterfeiting and anti-diversion
 The SAP solution portfolio (specifically SAP Auto-ID Enterprise)
supports RFID, barcode and 2-D Barcode

 Supported by SAP Business Suite (master data and electronic

GLN
transactional data, like request-to-pay and order-to-cash)
 GLN Site Sub-Location Types (SSLT) supported by SAP Auto-ID

 Supported by SAP Business Suite (master data, and transactional

GTIN

data, like order-to-cash and procure-to-pay)

 Serialized GTIN (S-GTIN) support by SAP Auto-ID

 SAP for Global Data Synchronization (consumer product MDM

GDSN

solution to upload data to/download data from GDSN Data Pools)

 Global Data Synchronization for Retail (part of SAP ERP)
UNSPSC

 Supported by SAP Business Suite (for master data – as Material

Group and Product Category and for business processes, like
request-to-pay and order-to-cash)
Healthcare Value Chain
SAP Solutions Support GS1 Healthcare Mission

Wholesalers & Hospitals & Healthcare

Manufacturers Pharmacy
Distributors Providers
Retailers

Government Regulations

GS1 Mission SAP Solution Offerings

Reduce medication errors SAP Auto-ID Enterprise Solution with Event Management (EM)and Object Event Repository (OER)

SAP Auto-ID Enterprise – secure Tracking & Tracing solution, including product tracking & authentication

 Documentation of serialized medical products within SAP/non-SAP Patient Management (e.g., legal
Enable global traceability &
requirement in France)
authentication
 For advanced authentication, we are looking at partnering with providers in collaboration with major
healthcare manufacturers

Improve supply chain SAP Auto-ID Enterprise – Secure Track-and-Trace solution

efficiency SAP SCM product portfolio integrated within SAP Business Suite

GS1 Standards adoption for SAP Auto-ID Enterprise

Automatic Identification &  The Object Event Repository (part of SAP Auto-ID Enterprise) is certified by EPCglobal to be
Traceability EPCIS-compliant
SAP and GS1 Standards
SAP provides GLN, GTIN, and UNSPSC support on Purchasing, Inventory, Sales, and Invoice documents, as
well as manufacturer-to-patient tracking of supplies, medications, devices, and equipment, using GS1
standards and an EPCIS-certified Repository

SAP Healthcare providers, manufacturers, suppliers, distributors, GPOs, exchanges, retailers, TPLs, and insurers can
take advantage of SAP’s ERP and EPCIS-certified Auto-ID Enterprise products that support GS1 standards.

SAP solutions for ERP and Auto-ID and item serialization enable:
Supply chain execution -- identify and track items during supply chain execution, enhancing the ability to
support outbound and inbound logistics, tracking, tracing, and reporting on inventory movements
Outbound logistics – maintain (GLNs and GTINs on Purchase Orders (new and changes), commission and
encode tags (according to EPCIS standards), pack and load units, cases, and pallets using RFID, issue goods
automatically, handle unit-level tracking-and-tracing;
Inbound logistics -- automated goods receipt and validation with Order Confirmations and Advanced Shipping
Notifications, using automatic processing of shipping and receiving, based on automatic ID and tracking of
items
Invoice processing – GLNs and GTINs are maintained on invoices
Asset management -- track and maintain stationary and reusable assets, identify equipment, select work
orders, record work, and update equipment histories
NOTE: GS1 Compliance in ECC is part of standard delivery since ECC 6.0, EhP2; no additional licensing is
required

Documentation on SAP GS1 support, including GLN and GTIN functionality, can be found at
http://help.sap.com/saphelp_dbm700/helpdata/EN/62/e0391eaa73b64f9ac8991ecf20b3b3/frameset.htm
SAP Support for the
Global Location Number (GLN)
 What is the GLN?

The GLN is a standardized, globally-unique, 13-digit number used to identify any legal or functional
entity, trading party, or physical location in the world (at whatever level of granularity is needed by the
healthcare provider, manufacturer, supplier, etc.). It is a required component of the Global Data
Synchronization Network™ (GDSN™) and used in conjunction with Global Trade Item Numbers (GTINs)
on purchase orders, sales orders, delivery, payment, and rebate and chargeback documents, and others.
Its basic components are:

*NOTE: The Prefix is variable-length. The GLN Registry uses five seven-digit Prefixes to create GLNs for providers (i.e., providers don’t
create their own GLNs -- they submit a list of their GLN hierarchy to the Registry, which then creates and assigns the GLNs).

 Physical locations with a single point of access with a physical  Legal entities
address  Healthcare hospitals and providers
 Hospital, manufacturing location/plant, or distribution center  Manufacturers
 Warehouse or specific door within a dock within a warehouse  Wholesalers
 Truck  GPOs and Exchanges
 Ship-to location  Distributors
 Deliver-to location (not necessarily the same as Ship-to location)  Third-party logistics
 Aisle/shelf/bin in a store room  Functions within a legal entity (e.g., Accounts
 Department/Cost Center Payable)
 A storage or distribution cabinet (e.g., Pyxis or Omnicell unit)  Nursing stations
 Ancillary departments
GLN Assignment can Vary by Organization Size and
Needs

For smaller organizations, it may be sufficient to assign a single GLN at the highest level. The
GLN may be used as a replacement for an custom account number or similar identifier (e.g.,
supplier number, manufacturer number, customer number, etc.). This requires collaboration
with trading partners in advance of the transition from an existing custom account number to
the GLN.
Larger, more complex organizations usually have many GLNs to represent different physical
or logical entities and/or subsidiaries – e.g.,
 A hospital may have a separate GLN for its shared-service Accounts Payable Department
 A hospital may have different ship-to GLNs for Pharmacy, operating theaters, ancillary
departments, and Receiving departments
 A manufacturer, distributor, or pharmaceutical, biomedical, or medical device supplier
may have different GLNs for various internal or customer locations (e.g., internal
manufacturing, packaging, and inventory locations; and customer ship-to, deliver-to, and
bill-to locations)
Mayo Clinic GLN Hierarchy (used for EDI POs)
Healthcare Applications

 GLNs in supply chain operations: The healthcare supply chain can be highly complex, particularly
with products that follow multiple routes between the manufacturer and a hospital or pharmacy.
GLNs can be used to uniquely identify individual shipping and delivery points, as well as the final
destination of a product or service. This information can be provided in electronic commerce
messages that can be used for track-and-trace purposes, as well as appearing on the shipping label in
a bar code or RFID tag.
 GLNs in eCommerce transactions: The use of GLNs is required in many types of electronic commerce
transactions, and is most commonly used in conjunction with GTINs for purchasing, shipping, and
invoicing transactions. They can identify suppliers, purchasers, and ship-to, bill-to, and other locations
(e.g., pay-from and pay-to). GLNs are increasingly important in healthcare transactions to ensure that
correct pricing is applied to specific customers and that ordering and delivery processes are
increasingly efficient, requiring minimal (if any) intervention from clinical staff.
 GLNs in data synchronization: When hospitals and their trading partners exchange price and other
information about the products or services they trade, this process is called Data Synchronization.
The data exchanged by data synchronization is non-transactional and includes the unique product
identifier (GTIN, Global Trade Item Number) and additional data attributes, such as product and
service descriptions, regulatory information, units of measure, latex content, sizes, and weights. This
ensures that resulting purchasing transactions are based on accurate and complete data.
Healthcare Applications

 GLNs in product traceability and recall

 Increasingly important for companies in all sectors to be able to trace their products through the supply chain.
 Companies have legal and regulatory obligations to trace and be able to recall their products.
 GLNs in patient safety applications
 Uniquely identify the location where a product is administered or used by a patient (also, caregiver who
administered the product).
 Helps to ensure that the correct product for the patient is used and, in the case of an adverse event, to trace both
the product and the patient

 GLNs in sterile equipment management

 Many national healthcare regulators are mandating that each instrument and/or instrument tray must be
uniquely identified and each use of the instruments and each decontamination activity recorded.
 GLNs are used to support this process by uniquely identifying the locations where instruments are used and
stored

 GLNs in medical asset management

 Recent studies have highlighted the costs and inefficiencies which result in healthcare through the lack of
visibility of the location of medical equipment.
 Clinical staff spends a lot of time looking for particular items of equipment
 Lack of visibility leads to additional equipment being purchased or rented > increases costs and reduces asset
utilization.
 Increasing number of healthcare facilities have implemented real-time tracking of medical equipment
Standardized Master Data: High-Level Example of
Trading Partner Scenario with Document Exchanges

Price Catalog (832)* Rebates and

Hospital Chargebacks
Purchase Order (850)
Order Acknowledgement (855) (844, 845, 849,
852, 867)
Despatch Advice / ASN (856)

Remittance Advice/Invoice (810) Supplier/

Supply Network Traceability Manufacturer/
Distributor/
GPO/Exchange

* GLN not supported in SAP

GLN Registry for Healthcare®: What is It and
Why Use It?
What is It?
 A registry of GS1 member (provider, supplier, distributor, GPO, exchange, software vendor, and any
other subscriber) GLNs and locations. Each location defined and registered by a member has been
assigned a unique 13-digit GLN, and includes the name, address, class of trade, and organizational
hierarchy information about each GS1 member.
 A subscription-based service that provides a comprehensive list of healthcare and healthcare-related
trading partners, with their corresponding Global Location Numbers (GLNs) and data (i.e., it is an
electronic catalog of standardized party/location information about healthcare providers and
healthcare-related trading partners, and serves as the “single source of truth” for healthcare location
information.
Why Use It?
 A subscription member (one that has entered its GLNs in the Registry), can go to the Registry to look-
up any other subscriber’s location information at any time, as well as download it. Then, by simply
cutting-and-pasting the data, they can easily update their system without having to re-key the data.
Alternatively, their Information Systems Department could write a simple interface program to keep it
synchronized with the industry database if they have many providers.
GLN Registry for Healthcare® and the Creation/
Assignment of GLNs
Providers:
 Providers can submit a spreadsheet with their location hierarchy to the Registry, which assigns GLNs (that
contain an up-to-seven-digit prefix -- there are five Prefix values that are not provider-specific, and the GLNs
for a provider may consist of different Prefixes – so, different providers may have GLNs with the same
Prefix).
 Optionally, providers can manually enter their GLNs into the Repository once they have one or more
assigned prefixes. The GLN Registry for Healthcare has an automated notification process for subscribers --
initial or ongoing maintenance generate emails to subscribers of the provider’s Repository records. Once
the GLNs are entered into the Repository, a spreadsheet can be generated for loading values in a provider’s
MMIS.

Suppliers
 Apply to GS1 for an assigned GS1 Company Prefix to be able to create their GLNs. After obtaining a Prefix,
they decide how granular their GLN structure will be, and assign GLNs to their locations, based on their GS1
Company Prefix, GS1 standards, and GLN Allocation Rules.
 Once the company defines or validates its GLNs, it registers them with the GS1 US GLN Registry for
Healthcare®, which acts as an index /”Yellow Pages directory”) to the various suppliers’ data pools, which
are electronic catalogs in the Global Data Synchronization Network (GDSN) that contain product and service
data). The GDSN also provides information for sharing data through subscriptions to hospitals and other
data “customers,” who use the data for sourcing and procurement.

Refer to the GDSN diagram on an earlier slide for a depiction.

2010 GLN Sunrise Goals

The 2010 GLN Sunrise goals enable Healthcare trading partners to be able to conduct
business using GLNs -- and realize their benefits -- by the end of 2010:
 GLNs are assigned by location owners (providers, distributors, manufacturers, GPOs,
exchanges, etc.)
 GLN hierarchies are defined and maintained by location owners
 The GLN Registry for Healthcare® is used to facilitate correct location identification
 GLNs are used in appropriate business transactions and processes among trading
partners
Trading Partner Scenario with Document
Exchanges of GLNs and GTINs
SAP supports GLN, GTIN, and UNSPSC standards on Purchasing, Inventory, Sales & Distribution, Invoice, and Rebates
& Chargebacks functions, as well as (via Traceability functions) manufacturer-to-patient tracking of supplies, meds,
devices, and equipment in an EPCIS-certified Repository

CUSTOMER MANUFACTURER

GDSN

GDS Upload via

Price Catalog
(832)

GPO,
DISTRIBUTOR,
or
EXCHANGE

SAP Healthcare providers (private and public), life science manufacturers, distributors, GPOs, exchanges,
consumer products, retailers, and insurers can take advantage of SAP’s ERP and EPCIS-certified Auto-ID
Enterprise products that support GS1 standards -- today.
GS1 GLN Transaction Priorities
(GLN Sunrise 2010)
SAP Support for the GLN
GLNs are maintained in three GLNs are contained in the following four EDI transactions*
sources  Purchase Order/PO Change (850)
 Sold-to Party/Buyer
1. Vendor Master (used by customers) – one  Vendor
per Partner Function, e.g.:  Ship-to Party (at header if all lines’ Ship-to =; line level if differs by
 Organization Entity line)
 Order-from Party
 Order Acknowledgement (855)
 Invoice Presenter
 Sold-by Party(Sales Organization)  Sold-to Party
 Bill-to/Invoice Recipient
 Ship-from Party (Shipping Point)
 Payer
2. Customer Master (used by manufacturers,  Ship-to Party
suppliers, distributors, GPOs, exchanges, etc.)  Despatch Advice / Advance Shipment Notification -- ASN
– one per partner function, e.g.: (856)
 Organization Entity  Ship-from Party – Vendor Shipping Point)
 Buyer/Sold-to Party  Ship-to Party – Customer Plant)
 Sold-to Party -- Customer SP partner function)
 Ship-to Party (header and line levels)
 Seller/Sales Org)
 Deliver-to Party (header and line levels)
 Bill-to Party/Invoice Recipient  Invoice (810)
 Payer  Invoicing Party
 Sold-to Party
3. GLN Table (used by all users, but some  Bill-to Party/Invoice Recipient
business objects are used only by customers,  Payer
while others are used only by manufacturers,  Company
distributors, suppliers distributors, GPOs,  Sold-by/Sales Org
exchanges etc.) *Rebates and chargebacks are addressed by the SAP
Paybacks and Chargebacks by Vistex solution
How SAP Currently Supports GLNs:
Vendor Master

Three fields are concatenated to create the Vendor’s GLN. This is

similar to the use of three GLN-relevant fields in the Customer
Master.
Vendor GLNs for Organization Entity, Order-from, and Pay-to are
required and obtained via the Partner functions in the Vendor Master.
How SAP Currently Supports GLNs:
Customer Master

As done with the Vendor Master, three location-

related fields are concatenated to create the
Customer’s GLN.
GLNs for Buyer/Sold-to, Ship-to, Bill-to, and Payer
are maintained via Partner functions in the
Customer Master.
 How SAP Currently Supports GLNs:
GLN Table for Business Objects
In addition to the Vendor and Customer Masters, the GLN Table (Table V_EAN_GLN, Transaction Code
EANGLN) is used to maintain GLNs for other business objects.
Five core Business Objects include
 BUKRS: Company
 EKORG: Purchasing Organization
 OSP: Shipping Point
 PLANT: Plant/Facility
 VKORG: Sales Organization
Issues:
 Plant is too high-level for ship-to
 Use of Plant for ship-to and bill-to
Two meta-tables, EANC_GLN_META and
EANC_GLN_META_DS, are used to
maintain Business Objects and descriptions
for which GLNs can be maintained.
Actual mapping of Business Objects and their simple (e.g., Plant) or compound (e.g., Storage Location requires both Plant
and Storage Locations keys) GLNs are maintained in the EANC_GLN_MAPP table).
 While additional Business Objects can be added, it isn’t advised, since validation and drop-downs for the five delivered
Business Objects are hard-coded and aren’t supported for added Business Objects.
 Instead, implement the enhanced GLN Table program that is provided via a Guide “Enhanced GLN Table - Technical Guide”
that is available in the SAP Market Place for Healthcare at http://service.sap.com/healthcare-guides (there is an accompanying
document, “Enhanced GLN Table - Users Guide – BPD” that provides an overview of the GLN Table program enhancements.
 Example: GLNs on Outbound PO (850)

 Buyer (Purchasing Org) – header level

 Vendor – header level
 Ship-to and Bill-to (Plant) – header or line level
 If all lines’ Ship-to are the same, then GLN appears at header level
 GLNs on Outbound PO: ORDERS and ORDCHG
(850) IDoc at Header Level w/Single Facility

This example shows multiple lines with the same Facility/Plant (therefore, the Ship-to/Bill-to will be at header level). Note use of GuiXT tool to
change “Company” to “Organization ID,” “Material Group” to “UNSPSC,” “Plant” to “Facility,” and “EAN/UCC” to “GTIN”
 Core functionality uses the Facility/Plant for both the ship-to and bill-to GLNs
 Core functionality does not handle ship-to/bill-tos below the Facility/Plant level.
 A PO with differing line Facilities/Plants will have the Ship-to/Bill-to at the line level.
 GLNs for Storage Locations (and other lower-level, ship-to business objects, such as warehouses, cost centers, etc.) are supported by enhanced
functionality available via Guides/”cookbooks” in the SAP Service Marketplace for Healthcare at http://service.sap.com/healthcare-guides
GLNs on Outbound PO – ORDERS, ORDCHG
(850): GLNs @ Header Level (Line Ship-tos =)

 AG: Buyer (Purch Org)

 LF: Vendor
 WE: Ship-to/Bill-to (Plant)
GLNs on Outbound PO – ORDERS, ORDCHG
(850) IDoc: Buyer (Purch Org)
GLNs on Outbound PO – ORDERS, ORDCHG (850) IDoc:
Vendor
GLNs on Outbound PO (850) IDoc: Ship-to/Bill-to
(Plant) – Same Ship-to GLNs > Header Level
GLNs on Outbound PO: ORDERS and ORDCHG
(850) IDoc at Line Level w/Multiple Facilities

NOTES:
 This example shows differing Facilities/Plants (therefore, Ship-to/Bill-to GLN will be at line level)
 GLNs for Storage Locations (and other lower-level, ship-to business objects, such as warehouses, cost centers, etc.) are
supported by enhanced GLN functionality available via Guides/”cookbooks” in the SAP Marketplace for Healthcare at
http://service.sap.com/healthcare-guides
GLNs on Outbound PO (850) IDoc: Ship-to/
Bill-to Differs by Line
GLNs on Outbound PO (850) IDoc: Ship-to/
Bill-to Differ by Line: Lines 1 and 2
GLNs on Outbound PO (850) IDoc: Ship-to/
Bill-to Differ by Line: Lines 3 and 4
GLNs on Order Confirmation (855) IDoc

 AG: Sold-to Party (Customer Sold-

to)
 RE: Customer (Recipient/Bill-to)
 RG: Customer (Payer)
 WE: Customer (Ship-to/Bill-to)
GLN on Order Confirmation (855) IDoc:
Sold-to Party (Customer)
GLN on Order Confirmation (855) IDoc:
Bill-to/Invoice Recipient (Customer)
GLN on Order Confirmation (855) IDoc:
Payer (Customer)
GLN on Order Confirmation (855) IDoc:
Ship-to (Customer)
GLNs on Outbound ASN (856) IDoc

 LF: Vendor
 WE: Customer (Ship-to/Bill-to)
 AG: Customer
GLN on Outbound ASN (856) IDoc:
Ship-to (Customer)
GLN on Outbound ASN (856) IDoc:
Sold-to (Customer)
GLNs on Outbound Invoice (810) IDoc

 RS: Invoicing Party (Customer)

 AG: Buyer (Customer)
 RE: Invoice Recipient
(Customer)
 RG: Payer (Customer)
 BK: Bank
 LFL: Sales Org (Supplier)
GLN on Outbound Invoice (810) IDoc:
Invoicing Party (Customer)
GLN on Outbound Invoice (810) IDoc:
Buyer (Customer)
GLN on Outbound Invoice (810) IDoc:
Invoice Recipient (Customer)
GLN on Outbound Invoice (810) IDoc:
Payer (Customer)
GLN on Outbound Invoice (810) IDoc:
Sales Org (Supplier)
Maintenance of Locations and GLNs in SAP
Auto-ID Infrastructure and Mapping to ERP
Location GLNs in SCM
Global Batch Traceability:
Vendor and Customer Master GLN
Maintenance
SAP Support for GLNs in Business Intelligence
Characteristics
 0OIS_BTTYPE Business Transaction
Type
 0OIS_COM_PRE Company Prefix
 0OIS_GLN Global Location Number
 0OIS_SSLT Site Sublocation Type
 0OIS_SSLTA Site Sublocation Type
Attribute
 0OIS_SSL Site Sublocation
Data Sources
 0OIS_SSLT_TEXT Site Sublocation
Type Description
 0OIS_SSLTA_TEXT Site Sublocation
Type Attribute Description
 0OIS_BTTYPE_TEXT Business
Transaction Description
Queries
 0OIS_MP03_Q0002 Movements Across
Locations
 0OIS_MP02_Q0002 Movements Across
Locations (Document Level)
 0OIS_MP01_Q0002 Movements Across
Locations (ID Level)
 0OIS_MP03_Q0003 Movements at
Location
 0OIS_MP02_Q0003 Movements at
Location (Document Level)
 0OIS_MP01_Q0003 Movements at
Location (ID Level)
 0OIS_MP03_Q0001 Proof of Receipt
 0OIS_MP02_Q0001 Proof of Receipt
(Document Level)
 0OIS_MP01_Q0001 Proof of Receipt (ID
Level)
Healthcare IBU-Funded
Add-on GLN Enhancements
GLN Enhancements

SAP has offered basic GLN functionality (originally developed for CP and Retail in
2006) in the core solution since ECC 6.0 EhP2.
While this GLN functionality exceeds recommended GS1 minimum requirements
(which are only for Ship-to and Invoice locations), customers in numerous
industries told us that they require GLN support for additional business objects
(notably, for Ship-to locations) on IDocs in order to be able to accurately conduct
business.
You also told us that they need GLN Search Help for vendors and customers.
After verifying the requests and researching potential approaches, we created
Guides (“cookbooks”) for enhanced Global Location Number (GLN) functionality
that document (with embedded coding examples) how to build the needed GLN
enhancements.
Requested GLN Enhancements
Additional Business Objects w/Search Help & Validation

1. Enhanced GLN Table with additional Business Objects; this required a new GLN Table transaction to
enable the maintenance of GLNs for existing and new objects with search help and validation:
 Storage Location (LGORT) – override Plant for Ship-to Locations
 Warehouse (LGNUM) – overrides Plant for Ship-to Locations
 MRP Area (BERID) – overrides Plant for Ship-to Locations
 Purchasing Group (EKGRP) – overrides Purchasing Org for Buyer and Sold-to Locations
 Cost Center (KOSTL) – for Buyer, Sold-to, and Ship-to Locations
 GL Account (SAKNR -- CoA + GL Account) – lower-level GLN for Cost Center (e.g., multi-disciplinary
research or project teams that are geographically dispersed)
 GL Account (SAKST -- CoA + CO Area + GL Account + Cost Center)
 Asset (ANLNR) -- for Ship-to Locations
 Project/WBS Element (POSID) – for Ship-to Locations
 Internal Order (AUFNR) – for Ship-to Locations
 Distribution Channel (VTWEG) -- for Sold-by Party (overrides Sales Org)
 Sales Division (SPART) -- for Sold-by Party (overrides Sales Org and Channel)
These additional business objects provide flexible GLN determination for EDI transactions and XML messages (XML
messages are used by the Supplier Relationship Management product in lieu of EDI transactions, but were not in
scope of the GLN Enhancement Project).
2. Provide search help and validation for all GLN business objects (core and new) in the enhanced GLN
Table program
Requested GLN Enhancements:
Additional Business Objects (Enhanced GLN Table Program)

Core GLN Table Business Objects Enhanced GLN Table Business Objects

New Business Objects

ANLNR: Asset (with Co) KOSTL: Cost Center (with Co) SAKNR: GL Account (with Cost Center)
AUFNR: Internal Order (with Co) LGNUM: Warehouse (with Plant) SAKST: GL Account (with CoA, Company, and Cost Center)
BERID: MRP Area (with Plant) LGORT: Storage Location (with Plant) SPART: Sales Division (with Sales Org & Distribution Channel)
EKGRP: Purchasing Group POSID: WBS Element (with Plant) VTWEG: Distribution Channel (with Sales Org)
New GLN Table Program: Create GLN

Create GLN (ZGLN01)

Create GLN (ZGLN01)

New GLN Table Program: Create GLN

Create GLN (ZGLN01)

Create GLN (ZGLN01)

New GLN Table Program: Change GLN

Change GLN (ZGLN02)

Change GLN (ZGLN02)

GLN Table with New/Changed Storage Location Entry

GLN Table with New/Changed Entry

 Requested GLN Enhancements:
IDoc
3. Add User Exit
new GLN for
logic forNew
IDocs that
GLNs,utilizes
GLNallSearch
business objects and determines and populates
Help
appropriate GLNs
 ORDERS, ORDCHG / ORDERS05 (850 – PO for create and change PO)
 ORDRSP (855 – Order Acknowledgement)
 DESADV / DESADV01 (856 – Advance Shipment Notifications)
 INVOIC / INVOIC02 (810 – Invoice)
 MBGMCR / MBGMCR03 (867 – Product Transfer/Resales Report – Inbound)*
 SHPCON / DELVRY03 (867 – Product Transfer/Resales Report – Outbound)*
 Product Transfer Account Adjustment)(844*
 Price Authorization Adjustment/Status (845)*
 Response to the 844 Product Transfer Account Adjustment (849)*
 Product Activity Data Report (852)*
NOTES: GLNs also are captured on the Sales Order at the header and line levels (in GLN comment field). These populate the 855
and 856 Ship-to GLNs
GLNs on rebate and chargeback EDI transactions are supported in the SAP Paybacks and Chargebacks by Vistex solution
(NOTE: 849 and 852 transactions exceed the GS1 recommended requirements).

4. GLN Search Help for Vendors and Customers

Requests not included in GLN Enhancement Project
1. Add GLNs to core transaction screens
2. Add GLNs at sub-line level
3. Allow leading zeros in GLN (like GTIN)
4. Allow > 1,000 Ship-tos per customer and >1,000 Deliver-tos per Ship-to
GLNs on Outbound PO: ORDERS and ORDCHG (850)
IDoc: Line-Level Facilities and Storage Locations

NOTES:
 This example shows differing Facilities/Plants (therefore, Ship-to/Bill-to will be at line level)
 GLNs for Storage Locations (and other lower-level, ship-to business objects, such as warehouses, cost
centers, etc.) are supported by enhanced functionality available via Guides/”cookbooks” in the SAP
Marketplace for Healthcare at http://service.sap.com/healthcare-guides
GLN for Line 1 (Park Clinic, Storage Location =
Pharmacy)
GLN for Line 2 (Park Clinic, Storage Location = Clinic
Pharmacy)
GLN for Line 3 (Diablo Valley Medical Center, Storage
Location = Pharmacy) – not in GLN Table
GLN for Facility/Plant
0002 used, since Storage
Location 0002/RX not
defined in GLN Table
GLN for Line 4 (Diablo Valley Medical Center, Storage
Location = Satellite Pharmacy)
Sales Order with Ship-to GLN in Line Text Field
Vendor Search Help by GLN: Transactions
Customer Search Help by GLN: Master Data
Customer Search Help by GLN: Master Data
GLN Enhancement Guides/”Cookbooks”
These five Guides, which will provide SAP customers and partners with a flexible approach to build
enhanced GLN functionality, according to your individual needs, have been written to assist you in
creating enhanced GLN functionality to meet those needs.

The Guides for the enhanced GLN Table, GLN search helps and IDocs include sample code and/or
build instructions that you can use to create your own enhancements. While we have tested these
enhancements in a prototype, you need to perform testing on your own system.
These Guides are:
• Introduction to Enhanced GLN Functionality Project
• Enhanced GLN Table Technical Guide
• Enhanced GLN Table Users Guide
• Enhanced IDocs Technical Guide (enables defining GLNs for new business objects, with
determination logic, on IDocs)
• GLN Vendor and Customer Search Helps

and have been posted on the SAP Service Marketplace for Healthcare at
http://service.sap.com/healthcare-guides
SAP Support for the Global Trade
Item Number (GTIN)
What is the GTIN?
 The Global Trade Item Number® (GTIN®) is an “umbrella” term that describes globally-unique GS1 identification
numbers that are used to identify products and services that are sold, delivered, and invoiced at any point in the
supply chain. GTINs are assigned by the brand owner of the product or service, and identify products as they move
through the global supply chain to the hospital or ultimate end user/customer. If a product is modified in any
significant manner along the supply chain, the party performing the modification assigns its own GTIN and GLN
(which are linked to the original GTIN and GLN for traceability)
 Once the GTIN is assigned, all trading partners can use and reference the GTIN. GTINs can be encoded into various
types of GS1 bar codes and Electronic Product Codes™ (EPC) that are programmed into Radio Frequency
Identification (RFID) tags.
 The GTIN is a required component of the Global Data Synchronization Network™ (GDSN™) and used in conjunction
with Global Location Numbers (GLNs) on purchase orders, delivery and payment documents, and others (see a
prioritized list of transactions on the next slide). It also has other equivalent identifiers, such as the UDI and NDC.
 14-Digit Structure
• One digit representing the packaging level/unit of measure

• Twelve digits: the GS1 Company Prefix and the Item Reference assigned by your company

• Check Digit
How GTINs are Assigned: Parent/Child Relationship
The Challenge: Why GTINS are Needed

Whenever an order is placed with a supplier, the supplier requires that each order line
contain the GTIN, a globally-unique, proprietary number in the supplier’s sales system
(which is different than existing Manufacturer and Supplier Part Numbers, and vary not
only by material or service, but by unit of measure, as well). This means that:
 Thousands of numbers are maintained within both suppliers’ and hospitals’ purchasing and sales
systems
 Hospitals spend significant time looking-up product and service numbers before placing phone
and other manual orders
 Suppliers spend significant time verifying that the customer order product and service numbers
are correct
What are GTIN Uses?
Besides serving as unique identifier for products and services, GTINs are used in conjunction with Global
Location Numbers (GLNs) to create product and service content for data pools within the Global Data
Synchronization Network (GDSN).
It is this consistency and timeliness of data (including near real-time collaboration of additions, changes,
and deletions) that is critical to the smooth functioning of the healthcare supply chain and are the
reasons for GS1 standards’ raison de être.
 Example: one customer, was experiencing a 16% rejection rate of order lines due to outdated and incomplete data,
and this led to the need to carry extra inventory due to the lengthened procurement cycle, as well as extra labor for
both the hospital and the supplier to identify and correct the errors. Data synchronization would have avoided this.
 Why Adopt GTIN: Usefulness

Why is the GTIN Useful?

 Uniqueness: The GTIN identifies an item or service uniquely.
 Non-significance: The GTIN numbering structure does not contain any meaningful information in itself.
 Multi-sector: GTINs are unique across all business sectors.
 International: GTINs are unique worldwide.
 Security: Security of GTINs is provided through a combination of database look-up and the fixed length,
numeric format that includes a standard Check Digit.
 Data Integrity: The Check Digit ensures the integrity of data passing through the system.
 Source Numbering: The GTIN is assigned by the brand owner of the product or service.
 Automatic Data Capture: One of the key benefits of the GTIN is that it can be encoded in many automatic
data capture technologies (such as a bar code or EPC used in RFID tags).
 Why Adopt GTIN: Key Benefits

Industry-wide implementation of data standards, such as GS1, can improve supply chain
data integrity. The GS1 System enables global and unique identification of products and
locations, as well as the continuous, automatic update (i.e., synchronizing) of standardized
product and service data across all supply chain partners.
These standards provide the necessary foundation for achieving the best results when
using complementary applications like automatic data capture, e-commerce, electronic
record management, assets and equipment tracking, and traceability.
 Facilitates the global flow of trade items (products and services) and associated information used in
electronic commerce
 Uniquely identifies trade items at all levels of packaging (item, case, and pallet)
 Allows accurate machine reading of trade items when placed in bar codes and EPCs that are
programmed into RFID tags
 Delivers trade item data in a consistent format and structure
 Simplifies supply chain management
 Employs the globally-accepted GS1 System, whose language is standardized, understood, and used
by multiple industries
What is GTIN Compliance?

A company that is able to process, store, and communicate information about their
products with trading partners using all GTINs, whether 8, 12, 13, or 14 digits, is
considered to be GTIN-compliant. Companies become GTIN-compliant by expanding the
appropriate systems and applications to 14 digits.
This will support the GTIN on products at all levels of packaging (consumer, inner packs,
multi-packs, cases, and pallets, etc.)
It is necessary to become GTIN- compliant to take advantage of the benefits of:

 Data synchronization, using the Global Data Synchronization Network (GDSN)

 Reduced Space Symbology® (RSS®)

 EPCglobal Network™
GTIN Best Practices

 GTINs are assigned to products and services, and registered with GS1

 Product and service providers and data aggregators (e.g., exchanges) create “data
pools” (electronic catalogs) in the Global Data Synchronization Network (GDSN)

 Healthcare provider create their own data pools and subscribe to the suppliers’ data
pools

 Data maintained in suppliers’ data pools update their subscriber’ data pools
2012 GTIN Sunrise Goals

 GTINs are assigned to healthcare products and services

 GTINs are marked on appropriate packaging levels
 GTINs are used in business transactions
 GTINs are scanned at points-of-delivery to enhance clinical process
 GTINs are used in product returns and recalls
 GTINs are registered in a GS1 GDSN-certified Data Pool

Together, these goals support a standardized approach to identifying, capturing and

sharing precise product information across U.S. healthcare.
 Relationship between GTIN and Unique Device
Identifier (UDI)
In his Federal Device Administration presentation on
the UDI, Jay Crowley (Senior Advisor for Patient
Safety) outlines the attributes and uses for the UDI,
which parallel those of the GTIN, including its being
applied to all levels of packaging and to the
components of a product/kit, as well as the
product/kit itself.
He also lists the first step for developing the UDI as
developing UDI code, according to ISO 15459 (GS1,
HIBCC) and concatenating Device and Product
Identifiers which, like GTINs, enable control by serial,
lot number, expiration, and manufacturing date.
Finally, the FDA’s UDI database contents can be
loaded from GS1’s GDSN, which uses the GTIN.
GS1 recommends that all medical devices should have
a UDI assigned, using the Healthcare GS1 GTIN
Allocation Rules
Relationship between GTIN and National Drug Code
(NDC)
For more than 30 years, the GS1 System has
incorporated the National Drug Code and the National
Health Related Item Code (NHRIC) within the Global
Trade Item Number (GTIN) and the Universal Product
Code (U.P.C.). The National Drug Code (NDC) identifies
pharmaceutical products and the National Health
Related Item Code (NHRIC) identifies medical/surgical
products.
Furthermore, the GS1 System provides identifiers for lot
number and expiration date.
The Food and Drug Administration (FDA) assigns the
Labeler Code portion of the NDC and NHRIC
(www.fda.gov). The Labeler Code is the basis for
identifying the company and must be registered with
GS1 US prior to bar coding products.
The GTIN is formed by placing the U.P.C. Prefix 3 in
front of the NDC or NHRIC number and then adding a
Check Digit to the end.
GTIN Flow

GS1
Compliance
Supplier Retailer

Receive: Vendor GTIN Create: Receive: Create:

Inquiry RFQ Inquiry RFQ

Create: Receive: Create: Receive:

Quotation Quotation Quotation Quotation

Receive: Vendor GTIN Create: Receive: Create:

Sales Order Purchase Order Sales Order Purchase Order

Create: Receive: Create: Receive:

Order Response Order Response Order Response Order Response

Create: Receive: Create: Receive:

Dispatch Advice/ASN Dispatch Advice Dispatch Advice Dispatch Advice

Create: Receive: Create: Receive:

Invoice Invoice Invoice Invoice
How SAP Supports GTINs

Standard GTINs (i.e., not GTIN batches or serialized GTINs) in ECC Procure-to-Pay Process
Flow
 Purchase Order
 Vendor Quotation
 Sales Order
 ASN
 Goods Receipt
 Invoice
Vendor GTIN
GTIN Mapping
Consistency check for GTINs
GTIN Processes with Specific Customer Data
 GTIN Mapping
Enables the automatic substitution of a material number by the GTIN
GTIN mapping provides the flexibility of the condition technique (well-known from pricing)
Choosing the fields and specifying their combinations
 Specifying the sequence of the various key combinations – e.g.:
 GTIN -- this is the only mandatory field
 GTIN variant type
 Customer
 Country
 Distribution Channel
 Sales Organization
 Division
 Using free selection fields that enable you to maintain generic condition records
 As soon as determination for one condition type (in the procedure) is successful, determination stops
 As soon as one access (in access sequence) is successful, determination process stops
GTIN Mapping
 EAN1 – Create GTIN Mapping
 EAN2 – Change GTIN Mapping
 EAN3 – Display GTIN Mapping
 EAN4 – Create GTIN Mapping with Template

Details can be found at http://help.sap.com/erp2005_ehp_04/helpdata/EN/eb/c8cddb698911d6b23000508b5d5211/frameset.htm

 NOTE: See http://help.sap.com/erp2005_ehp_04/helpdata/EN/62/e0391eaa73b64f9ac8991ecf20b3b3/frameset.htm

 Consistency Check for GTIN Attributes

In case multiple materials are assigned to the same GTIN (or GTIN Variants), the following attributes
must be the same:
 Length
 Width
 Height
 Volume
 Net and gross weight
 Unit of Measure (e.g. EA, CS ...)
GTIN CONSISTENCY CHECK
 Report can be used to change the attributes of all the materials in the database with the same Global Trade Item
Number (GTIN) variant combination
 Report ensures that the attributes for this GTIN are consistent
 GTIN Processes with Specific Customer Data
Purpose
 The GS1 GTIN compliance component covers three elementary business processes that are divided into
internal and external processes:
 Ordering
 Delivery
 Invoicing
Process Flow
In IDocs for the following processes, a material number is determined from a GTIN and additional data,
using determination logic
 Customer Inquiry – outgoing
 Customer Inquiry – incoming
 Customer Quotation – outgoing
 Customer Quotation – incoming
 Purchase Order
 Order Confirmation
 Shipping Notification – outgoing
 Shipping Notification – incoming
 Invoice

The process data can be entered manually or sent as an EDI message.

For these processes, the GS1 GLN Compliance component provides the standard functions and an
extended help function (F4) that you can use to enter the GTIN.
Vendor-Specific GTIN Table (Txn EANVENDOR)
Maintain Material/Vendor/Unit of Measure

Maintains Material
Master (Additional Data
View/Units of
Measure/EAN/UCC) –
do not maintain the
Material Master
manually; use this
transaction.
Populates GTIN on
Vendor Quotation, PO,
Sales Order, Goods
Receipt, and Invoice
(see following slides)
Vendor Quotation GTIN
Purchase Order GTIN (UoM = PAC)
GTIN on Purchase Order (850) IDoc
GTIN on FAX
GTIN on Sales Order
GTIN on Outbound ASN
GTIN on Goods Receipt
GTIN on Outbound Invoice
GTIN on Inbound Invoice
GS1 Functionality in CRM
GS1 Functionality in CRM

 GLN in the CRM Customer Master (per Partner Profile)

 GTIN in the Product Master (appears on Sales Order lines, Order Acknowledgements,
ASNs, and Invoices)
 SAP Support for
GS1-128 Bar Code
and
Label Creation
GS1-128 Barcoding: GS1 ID Numbers are Used
with Bar Codes & EPC-enabled RFID Tags
GS1-128 barcodes are used to encode product data for packaging units, such as cartons,
cases, pallets, and reusable packaging or transport equipment (returnable assets) and help
manage fast and accurate tracking of inventory.
Specific information also can be encoded in GS1-128 barcodes to add security and
sustainability to your supply chain, such as Best Before Date, Batch/Lot Number, Serial
Number, and the GS1 System’s Serial Shipping Container Code (SSCC).
Items marked with GS1-128 symbols are not intended to pass through retail point of sale.
Capturing the Identification Key … and More

Some data carriers maintain more detailed

information about a specific unit than others

Item Identifier/GTIN Expiration Date

Batch Number
Serial Number
AI Data Content/Element

(21)123 00 SSCC (Serial Shipping Container Code)

01 Global Trade Item Number (GTIN)
02 GTIN of Contained Trade Items
10 Batch or Lot Number
Application Identifier 11 Production Date (YYMMDD)
12 Due Date (YYMMDD)
13 Packaging Date (YYMMDD)
15 Best Before Date (YYMMDD)
17 Expiration Date (YYMMDD)
20 Variant Number
21 Serial Number
…
GS1 Data Carriers for Healthcare

GS1 DataMatrix
Preferred option if: EPC/RFID
GS1-128 &
Additional option
GS1 DataBar Large amount of data on
small space Not line-of-sight
Preferred options if:
 Variable information at  Large amount of
Package allows data
high production rates
Direct part marking

Image bar code scanners are needed!

You can Work Concurrently with RFID and 2-D Barcodes
in SAP Auto-ID Infrastructure & SAP OER

EPCs encoded on RFID Tag

IDs encoded on 2-D Barcode

GS1-128 Bar Code and Label Creation in SAP
The SAP Label Toolbox uses the IDAutomation C128M font to generate the barcode.

 The Start, Check, and End Code are generated automatically by the Label Toolbox.
 The only things that the user has control over are the FNC, the application identifier, and
the 5-digit ZIP code that follows it.
 The FNC character is always ASCII code 202, which corresponds to FNC1 with the
attached font (the Label Toolbox had used a different Code 128 font in the past
and the FNC1 character corresponded to ASCII code 185).
 Our usage is specific to the United States Postal Service, as defined at
http://pe.usps.com/text/dmm300/708.htm#1352960
 As of ECC 6.0 Enhancement Pack 6, GS1-128 labels can be created and customized with
Adobe Life Cycle Designer
 In previous versions, customers had to create their own labels.
 This new feature enables companies to generate the label without additional
costs.
 Bar Code and Label information can be found at GS1 US Healthcare at
http://www.gs1us.org/sectors/healthcare/barcoding_and_epc_rfid
Printing GS1-128 Labels

The Trading Industry requires the Shipping Process to be based on GS1 Standard to enable more
effective business processes. Finished products can be tagged with Information about Best-Before Date,
Batches, Serial Shipping Container Code, etc.

Features
 Pre-definition of a GS1 Label
 Generation of a GS1 Label as message of handling
unit
 Automation: Printed barcode based on EAN128
 Dynamic determination of EAN numbers, based on
Material Master
 Processing of mixed pallets
 Easy adjustment of the Label with Adobe Life Cycle
Designer
 Form: CFB_V6_EAN128_FORM
2D Bar Code Examples
SAP Support for Global Data
Synchronization (GDS)
Uploading and Downloading GDSN
Data Pool Data to/from SAP
GDS Process
Maintaining Product and Service Data Integrity
in a Complex Business Network is Challenging
Complex global demand and supply networks require timely, accurate and consistent product coding

Product Partner Emerging Global

Proliferation
 High-volume, granularity, and change
frequency
 Inconsistent and / or inaccurate
product and service information
 Management and error-handling
increases costs and complexity
Collaboration
 Inaccurate item information creates
errors, increases costs (e.g., high
rejection rate for contract releases)
 Reconciling product codes slows
orders, returns & claims
 Inconsistent view of shared codes
disrupts customer service
Standards
 Retailer mandates driving manufacturer
process changes
 Maintaining consistent data across a
global supply network
 Data synch needs extend to other
topics: sustainability, traceability
What does this mean for your business?

Top executive issues

 How do I create a manage a consistent and accurate
product data pool to enable business partner
collaboration?

 How do I reduce time, effort and cost of communicating

updated product information to my retailer partners?

 How do I improve collaboration with my supply network to

ensure timely manufacturing and adequate inventory?

 How do I increase order and shipment accuracy to lower

inbound and outbound logistics costs?
SAP Provides Best-In-Class EIM Solutions: Deliver
Complete, Accurate, and Accessible Information
Enterprise Data Warehousing: Data Integration & Quality Management:

 SAP NetWeaver Business Warehouse  SAP BusinessObjects Data Services

 SAP NetWeaver Business Warehouse  SAP BusinessObjects Data Federator

Accelerator  SAP BusinessObjects Text Analysis
 SAP BusinessObjects Rapid Marts  SAP BusinessObjects Data Insight
 SAP BusinessObjects Metadata Management  SAP Data Migration services

Content & Information Lifecycle Management: Master Data Management:

 SAP NetWeaver Information Lifecycle Management  SAP NetWeaver Master Data Management
 SAP Extended ECM by Open Text  SAP Master Data Governance for Financials
 SAP Document Access by Open Text  SAP Data Maintenance by Vistex
 SAP Archiving by Open Text
SAP NetWeaver MDM Global Data Synchronization:
How It Works
Extraction Enrichment Register Trade Publish to
Items trading partners

SAP
NetWeaver
GDS
Console

SAP Global
MDM Registry
ERP
Data Pool Data Pool

PI
GDSN

Hospital
or Retailer
Manufacturer,
Distributor, GPO
SAP NetWeaver MDM Global Data Synchronization:
How It Works
Extraction Enrichment Publication
Validation

SAP
NetWeaver
GDS
Console

SAP Global
MDM Registry
ERP
Data Pool Data Pool

PI
GDSN

Hospital
or Retailer
Manufacturer,
Distributor, GPO
SAP NetWeaver MDM Global Data Synchronization:
How It Works
Extraction Enrichment Publication
Validation

SAP
NetWeaver
GDS
Console

SAP Global
MDM Registry
ERP
Data Pool Data Pool

PI
GDSN

Hospital
or Retailer
Manufacturer,
Distributor, GPO
SAP NetWeaver MDM Global Data Synchronization:
How It Works
Extraction Enrichment Publication
Validation

SAP
NetWeaver
GDS
Console

SAP Global
MDM Registry
ERP
Data Pool Data Pool

PI
GDSN

Hospital
or Retailer
Manufacturer,
Distributor, GPO
SAP NetWeaver MDM Global Data Synchronization:
How It Works
Extraction Enrichment Publication
Validation

SAP
NetWeaver
GDS Subscribe and
Synchronize
Console data pools

SAP Global
MDM Registry
ERP
Data Pool Data Pool

PI
GDSN

Hospital
or Retailer
Manufacturer,
Distributor, GPO
 What is Transported During the GDS Process?
The main purpose of the GDSN is the synchronization of product and service information.
A Product, in GS1‘s definition, is called a “TRADE ITEM.“
Definition:
 Any item (product or service) upon which there is a need to retrieve predefined information that may
be priced, ordered, or invoiced at any point in any supply chain (GS1 definition).
A trade item is described by a number of attributes that vary, depending on the context in
- Source: GSMP
which it is used.
 In GDS 2.1, the Price Management function is used to maintain and synchronize price data with retailers.
With Price Management, you can reduce the number of invoice errors by automating the process of
supplying price data.
NOTE: Price Management is not a negotiation tool, and does not replace the current negotiation
process.
A trade item to be exchanged is identified by a triple key:
 GTIN (Unit of Measure, Vendor Prefix, and Product/Service) + GLN of Info Provider + Target Market
 GTIN = Global Trade Item Number
 Uniquely identifies a trade item
 GTIN is just a new name for all EANUPC numbers
 GLN = Global Location Number of the Information Provider
 Uniquely identifies a source trading partner in the GDSN
 Target Market for which region the trade item is intended
SAP ERP Attributes for GDS (others can be easily added)
What’s Needed for GDS?

 Providers and other data recipients who need to download GS1

product and service data into SAP require
 IS-Retail (we are researching alternatives)
 GDS for Retail
 SAP NetWeaver Process Integrator (PI) middleware component
 AS2 adaptor for encryption that runs in the PI adapter framework
 Consulting services for adding attributes (which differ among countries and
regions)
 Manufacturers and other data sources who need to upload product
and service data into GS1 require:
 GDS Source system (either SAP ERP or NW MDM Scenario)
 SAP NetWeaver Process Integrator (PI)
 GDS component (covered by GDS license)
 AS2 adaptor for encryption that runs in the PI adapter framework
 NW WAS
 NW MDM Server (covered by GDS license)
Key Trends driving future innovations areas for SAP
global data synchronization

Enterprise
Master Data
Management

Cloud

Business
Networks
Blog Social Networks (B2B, B2C)
Mobile
SAP MDM-GDS 2.1 Strategy

Preparation for GS1 Major Release 3 (MjR 3) support – Modular Items

 GS1 Standard (anticipated) release dates:
• Q1 2014: GDSN Beta Testing Environment Available for Certified Data Pools
• Q2 2015: GDSN Data Pool Technical Certification Event Begins
• Q2 2016: GDSN Production Environment Deployment

No major technical changes until the end of the next major release (GS1 /
1WorldSync)

We think about a new long-term roadmap (after 2016-2017) for SAP GDS

We will continue to ship minor functional improvements until the major

release
 Customers Realizing Value with the GDS Solution

 Rapid deployment of new markets by leveraging global platform

 Elimination of manual maintenance effort

 Fewer errors, due to elimination of manual tasks and spreadsheets

 Streamlined sales processes, enhanced supply chain & order execution
 Decreased trade partner setup time

 Eliminated data maintenance redundancy

 Reduced time to market

 Totally automated the process of communicating data

 Facilitated the global flow of products

Other customer examples include Wal-Mart, Colgate, and Unilever

We have customers connecting to the following data pools:
 1Worldsync
 GS1 Sweden
 ECCNet
 RXS (planned)
SAP Support for Traceability /
Track & Trace

Supply Network Traceability and Serialization

in the Healthcare Supply Chain
Serialization in Healthcare

 Patients

 Patient records

 Counterfeit protection for supplies, drugs, implants,

devices, instruments, equipment, and other assets

 Blood products

 Lab and pathology sample tracking

 Medical waste
Growing supply complexity increases product safety
risks, while incidents have greater impact than ever
before
Authorities

R&D

Quality/
Purchasing Compliance

Production
Marketing
& Sales

Serving more patients and Rising costs and Better informed patients and
customers in more markets shrinking margins customers around the globe

Growing product and network Global sourcing and outsourced One incident can damage consumer
complexity is increasing risk and manufacturing make it difficult to trust and loss of preferred supplier
challenging traceability ensure safe products status at Retail
 Traceability

“Tracing” refers to the business process of discovering and acting upon the path that a
product or other asset takes through the supply chain.
At each step in the supply network for a given product, there may be generated a physical
event, a business transaction, or both. All data may be relevant in a traceability scenario
where the business goal is to understand the “chain of custody” and what happened in the
supply network.
 A trace is comprised of data that is created by multiple parties in a supply network.
 In order for a trace to be understood by any party, all parties must adhere to
standards.
 The GS1 System provides global standards for physical events and for business
transactions, as well as for the supporting master data
 These standards support the potential implementation and use of Key Data Elements
(KDEs) and Critical Tracking Events (CTEs)
Why Traceability?
Need for Serialization – Key Issues
Standards

Gov’t regulations Safe & Secure

in US & Europe Supply Chain

Patient safety

Increasing operating costs

Counterfeits
Downward margin pressure

Reduced operating efficiency

Diversions

Business issues

• Cost Pressure (esp. generics)

• Supply Chain and reverse logistics
opportunity
• Complex, multi-step Supply Chain
Industry Pain Points for Drug Traceability
Intense Competition and Reducing Margins
 Continuous pressure to improve supply chain
efficiency
 Increasing pressure from poor chargeback
and rebate accuracy

Safe and Secure Supply

Chain
Increasing Government
Regulations  Growing concerns of
patient safety
 Pedigree mandates Patient Safety
from FDA and US  Increasing number of
states (FL, CA, IN) Increasing Operating Costs counterfeits and
diversions
 Increasing drug Downward Margin Pressure
traceability  Increasing theft,
requirements in Reduced Operating Efficiency security requirements
European countries like for controlled
Turkey, Italy, and others substances
 Brand Protection

Constant pressure to improve Reverse Logistics

 Increasing incidents of product recalls
 Inventories of expired, overstock products
 Increasing pressure to improve logistical errors and
returns processing
Track-and-Trace Base Reference Mode

Source: EPC Global

Safe & Secure
Supply Chain
Is the product
genuine?
Is the chain of
custody intact?

Authentication Pedigree

Product Physical Track Trace

Identity Features

Is the EPC associated Does the unit of sale Where is the product Where was the product?
with the unit of sale have the expected and where is it (Locations &
valid? covert and/or overt headed? Custodians)
features?
Overall Mission of SAP Track & Trace

“ Enable a holistic end-to-end product traceability from raw

material to point of consumption“
1. Relate a batch genealogy to item-serialized products and vice-versa

2. Enable track-and-trace for products in transit

3. Ensure process compliance throughout the supply network

4. Interrelation of the above

Traceability Best Practices

 Key to generating value from Auto-ID technologies is to incorporate the data

into everyday business processes (standalone deployment of Auto-ID solutions
provides only limited value)
 Implement and conduct business using GLNs and GTINs
 To most efficiently identify, trace and track Critical Tracking Events (CTEs) and
Key Data Elements (KDEs) and share this information with multiple parties,
businesses need to use a single, global, open system of supply-chain standards
 Implement an EPCIS-certified Object Event Repository to capture CTEs and
KDEs
SAP Solutions for Auto-ID & Item Serialization

SAP Solutions for Auto-ID & item serialization address

 Compliance
to Product and Part instance serialization instance object identity related regulations and mandates

 Business Process Automation

with Automatic Identification Data Capture (AIDC) & Sensor integration

 Situational Insight to Action

Intra- and Inter-Company High Resolution Product and Part instance (Supply and Value Chain)
Lifecycle Event Management & Tracking across distributed systems
SAP Solutions for Compliance with Item Serialization
Regulation and Mandates
It can be RFID, but it doesn’t have to be…
You can use various Auto-ID capture and sensor integration technologies,
as well as ERP backend integration options to implement item serialization
Capturing Integrating Auto-ID into
instance serialized data Business Processes
 RFID  ERP integration
 Linear Barcode  Delivery integration
 2-D Matrix Barcode [ECC200]
 Sensors  Production order integration
 …  Kanban integration
SAP  ERP integration EhP4-upwards
Solutions
 IUID Process integration
for
Auto-ID  Central Serialization repository
Automation
The XML-based and
 Without line of sight
Capture data capture
interface Item Universal Traceability
Additional process integration
 Remote Is data capture
agnostic of the Serialization  Unifying information spaces in central
 Data carried by data/ asset Is possible with customization
repositories
Auto-ID and Sensor Capture
 Verification at source You
 Single canof also
point accessleverage SAP PI
for business
Technology used
to connect
network to your
data discovery & analysis
 Single point of consolidated reference for
legacy systems
object lifecycle tracking and analysis
 How SAP Supports Traceability
GS1 Vision
 All authentic items are identified with the appropriate GS1 identifier at point of production
 Identification remains with/on the item throughout its intended useful life
 All physical locations are identified with the appropriate GS1 identifier across the entire supply chain
 Agreed master data is captured and shared (e.g., via GDSN) on demand amongst trading partners
 Agreed event data is captured and shared (e.g., via EPCIS) on demand among traceability stakeholders
Goals
 Items can be tracked
o Forward / downstream (production to use), across the entire supply chain, in real time, on-demand
o Backward / upstream (from current location back to the producer), across the entire supply chain, in real time, on-
demand
 Electronic Health Records (EHRs) are updated with agreed-upon traceability information
 Counterfeit products are detected upon entering the legitimate supply chain
 A product recall would be fast, efficient, and effective
SAP solutions for auto-ID and item serialization support a set of preconfigured business processes that enable tracking
a product’s chain of custody, from manufacture to patient administration.
Four classes of applications
1. Automation: leverage auto-ID to increase the efficiency of the workforce required to execute a business process or to increase data
accuracy of a process.
2. Track-and-Trace: business value is derived from awareness of the status and location of serialized objects
3. Decision support and analytics. Data captured through the process of tracking serialized information through the supply chain
4. Enriching business solutions: enables highly-innovative applications of auto-ID and serialization that SAP customers have designed
that take advantage of the technology in unique ways
Quick Overview

Corporate event SAP Object Event

management-enabled EPCIS Repository
repository for serialized Supports RFID, 2-D
product items (SAP OER)
barcode, and linear
barcode data capture

Enables flexible definition

Middleware that processes
SAP Auto-ID Infrastructure of ID schemes and
Auto-ID raw events for
vocabularies
business process automation (SAP AII)
and event capture for SAP
OER

SAP ERP
SAP Solutions for Auto-ID & Item Serialization
Cover Solution Aspects of Supply Network
Traceability
SAP Solutions for Auto-ID and Item
Serialization
SAP Track & Trace Solution Map:
Enabling Corporate Product Traceability

End-to-end corporate traceability solution enabled

Investment in repeatable
customer solution

Regulatory
reporting for OER

SAP Global Batch SAP Object Event SAP Event

Traceability Repository (OER) Management

Corporate product batch Corporate item serialized product Process compliance, Asset and
genealogy and tracking of related traceability with SAP Object Transportation Tracking with
objects with SAP Global Batch Event Repository/SAP AII SAP Event Management
Traceability

Investment in NEW product Investment in SAP Event

Management integration with TM
Track & Trace with SAP – Segregation of Duty
Corporate Product Batch
Genealogy and tracking of related
objects with SAP Global Batch
Traceability
 Trace throughout product genealogy
 Trace related objects, such as deliveries
and production and purchase order
references
 One-click reporting: delivery
distribution, stock overviews, basis for
material balances
 Report processing of multiple batches in
a single run
Process, Asset, and
Transportation Tracking with
SAP Event Management
 Management by exception
 Visibility for / procure-to-pay and order-
to-cash processes
 Track goods and assets while in-transit
within the entire supply network
 Process compliance and support of
business partner integration
Item-serialized product
traceability with SAP Object
Event Repository/SAP AII
 Track & Trace throughout
downstream distribution
 Basis for traceability reporting to
authorities
 Corporate item serialized product
and component traceability across
distributed business and sensor
systems
Innovations for Track & Trace
2012
Advanced Capabilities
for SCE (SAP EM)
• Geo Tracking and Usability
• Content for booking-based
container tracking, door-to-
door shipments and
instructions
Product Genealogy
(SAP GBT)
• Graphically explore a cross-
system batch relation
network for root cause
analysis and immediate
reporting
• Comprehensive tracing of
batch-managed products and
components
RCS for Regulatory
Reporting (SAP OER)
• Creation, transfer, and
acknowledgement of
notifications to authorities
for regulatory compliance
based on serialized
processes
SAP Solutions for Auto-ID and Item Serialization
Product Electronic
Returnable Parts
tracking Promotion proof
transport Assembly
and management of delivery
items Tracking
authentication (EPOD)

SAP OER* EPCIS**-compliant

Query interface

Auto-ID repository
Legacy Event management analytics
Process Security services
integration (PI)

Capture interface EPCIS-compliant

Trading Partners

*SAP Object Event Repository

**Electronic Product Code Information Service

© SAP 2008 / Page 155

SAP Solutions for Auto-ID & Item Serialization for
Business Process Automation
Shipped standard SAP Auto-ID-Enabled Processes
 Product Tracking & Authentication
 RFID-Enabled Outbound & Inbound Delivery Processing
 iUID-Enabled Outbound & Inbound Delivery Processing
 RFID-Enabled Centralized LES WMS
 RFID-Enabled Kanban
 Returnable Transport Items

Configurable Processes
 Auto-ID Enabled Returns Processing
 Auto-ID Enabled Production Order
 Cool Chain Monitoring

Customizable Processes
 You can use the SAP Solutions for Auto-ID & item serialization to
customize and integrate additional Auto-ID enabled business processes
and also connect to legacy system
 Manufacturer (1/5)

Manufacturer

The manufacturer transmits serialized information to the central database (global

OER) - optionally via RFID and 1D barcode (e.g. for containers, pallets) and 2D
barcode (e.g. for pallets and products). Standards like GS1, EPC or CLEPA Matrix
Code are useful. Centralized maintenance of packaging hierarchy in SAP OER
simplifies logistics processes across company and country boundaries.

6x 12x

© SAP 2008
2007 / Page 157
 Customs (2/5)

Customs

The Customs officer scans the barcode

at container, pallet, or item level,
retrieving manufacturer information and
item lifecycle from a global OER, to
prove validity and authenticity of the item
– along with the AES reference to allow a
comparison with the Atlas Customs
System

© SAP 2008
2007 / Page 158
 Wholesale Distributor (3/5)
Wholesale
Distributor

Wholesaler distributors use mobile or

stationary readers (mostly RFID-based)
to read containers and pallets to retrieve
manufacturer information, optimize their
own logistics processes, and post further
logistics milestones into a global
repository for further tracking.

© SAP 2008
2007 / Page 159
 Hospital (4/5)

Hospital

The hospital uses this function to track total or

partial trading unit quantities (e.g., single pills or
liquid mixtures) from the central pharmacy to the
patient. Other uses include patient/med matching,
recall by batch or serial number, authentication
spot-checks, reporting, and visual tracking of
serialized objects, such as documents, equipment,
patients, personnel, etc.

© SAP 2008
2007 / Page 160
 Hospital - Patient (4/5)

Patient

Increase patient safety, reduce human error

danger by automatic patient/drug matching when
dispensing. Quickly identify patients who
received medications, devices, etc. from particular
packaging (single serial number) or batch. Patient
or nurse can scan the serial number at the item
level and verify the authenticity of medications,
devices, etc.

© SAP 2007 / Page 161

 Patient (5/5)
Patient

Patients can read the 2D barcode at

product level with cell phone cameras SAP Verification Portal

Manufacturer: Bayer
and verify the authenticity of goods. Product: Voltaren
GTIN: 00370001122334
Lot: A255ZT98
Expiry Date: 20151017
EPC:01.000A89.00016F.000169DC0
Status: Known

© SAP 2008
2007 / Page 162
SAP Object Event Repository
Extended Product Safety and Stewardship
Holistic and Integrated Support by SAP Applications

Object Event Global Batch Quality Issue

Repository / AII Traceability* Management*

HR PP QM MM SD

EHSM: Prod. &

EHSM: Env. REACH Compl. EHSM: Product Recycling
Compl. EHSM: Health & Safety Administration
Safety
PLM Recipe
Development
ERP

Global Trade Management of PLM Project &

Services Change* Portfolio Mgmt
Core PSS Extended PSS Integrates with PSS
 SAP Object Event Repository
GS1 - EPCIS Standards-Based Data Repository

Need a standards-based
Product Need a way to track a product as Industry
mechanism for sharing data for
serialization it moves through the supply chain
SAP Object Event multiple use cases
Standard

Repository
Data capture Need a way to store and manage (SAP OER) Need a way to share data with
Secure data
& millions of transactions acquired trading partners to identify
exchange
repository by tracking product movements business value

SAP Object Event Repository is an EPCIS-compliant, enterprise-level solution

that serves as the system of record about uniquely-identified objects.
 Tagged product flow at multiple locations, multiple local processes
 Interrelated tracking of child & parent objects and document associations
 Centralized data exchange with trading partners
 Single set of interfaces and repository for growing number of enterprise-consuming
applications
 Supports various data streams [EPC, transactions, POS, sensed conditions …] to drive
business value
Supply Network Traceability with GS1 EPCIS
and SAP Object Event Repository
Customs
Will be supported in
his territory duties
Distributor
Wholesaler
Logistics Service Provider
Automates processes and
Hospital
authenticates goods
Packaging hierarchy changes
Manufacturer
Increases brand value
and sales volume
After-Sales Services
Capability to deliver Service
Patient
Safety is enhanced by
reduced risk of
medication errors and
Tracking of supplies, medications (even in unit doses), devices, and
counterfeits
equipment
Tracking of patients, assets, blood samples …
Patient / drug matching * PTA Product Tracking & Authentication
** OER Object Event Repository
Facilitated recall and returns
Secure Supply Network Traceability with GS1
EPCIS and SAP Object Event Repository
SAP Solution

■ Integration with diverse tracking equipment (bar

code scanners, RFID readers)
■ Reporting related to GS1 Healthcare Traceability
Handling and Standard
■ Legal compliance with national, regional, and
Fulfillment global regulation
■ Smooth Integration with SAP Patient
Management (IS-H) or non-SAP systems

SAP Differentiators

Increased Patient Safety by facilitating product recalls through withdrawals, isolation,

and returns; and reducing medication errors (patient/drug matching)
Complete Product Traceability, including reporting, in a complex, global supply chain,
from the manufacturer to the patient.
Authentication provides brand protection, product authentication, and reduced risk of
counterfeit or fraud
 Standard Pre-configured, Value-add Business
Processes in Auto-ID Enterprise
Auto-ID – Enabled Outbound
Delivery Processing
 Generate serial numbers
 Commission tags
 Associate tags and items
 Generate flexible multilevel product or
parts and handling unit hierarchies
 Scan and track outbound items
 Associate EPCs/ iUIDs with deliveries
 Verify delivery requirements at the data
capture source
 Automatically process goods issue in
the back-end ERP Application
 Automatically trigger ASNs enriched
with EPCs
© SAP 2008 / Page 168
Auto-ID – Enabled Inbound
Delivery Processing
 Scan and validate goods receipts based
on ASN data (Advanced Shipment
Notification)
 Automatically process goods receipts in
the back-end Enterprise Resource
Planning (ERP) application
 Automatically generate proof-of-delivery
documentation based on predefined
conditions
RTI Process
 Closed-loop tracking of returnable
transport items/containers, or rotables*
 Commissioning of tags per the
standard Global Returnable Asset
Identifier (GRAI) format
 Automatic monitoring of events, such
as empty and full status, using event
management tools
* Component or inventory item that can be
repeatedly and economically restored to a fully
serviceable condition.
 Value-Added Business Processes with
Auto-ID Infrastructure
Secure Track-and-Trace
 Processes to track and trace in the
supply network, using serialized data
 Authenticate items throughout the
supply network
 Track, based on business context
(Purchase Order, Sales Order,
Delivery, Receipt, etc.)
 Ability to track additional information
© SAP 2008 / Page 169
RFID-Enabled Kanban
 Automatic Kanban status change
 Creation of a replenishment element,
(e.g., Purchase Requisition or Order)
 Automatic goods receipt posting
 Creation of the material document
Customer Returns Delivery
 Process Customer Returns Delivery in
Auto-ID Infrastructure
 Scan and validate receipts with respect
to returns delivery expectations
 Automatically process goods receipt in
the back-end ERP application
 Verify return requirements at the data
capture source
 Value-Added Business Processes with
Auto-ID Infrastructure
Pedigree Tracking
 Pedigree integration to ERP Processes
 Ensure chain of custody
 Weave Authentication and Traceability
into processes
 Same repository supports multi-level
product authentication (EPC, tag-id
and EPC combination, EPC and
security marking combination, case-
item, pallet-case-item association)
© SAP 2008 / Page 170
DoD IUID Support
 Items with IUID barcodes can be
managed with standalone and
integrated outbound and inbound
processes
 Support for DoD constructs
CNSTR1EID and CNSTR2PART for
DoD mandate for IUID
 Mapping between ERP serial nos and
UIIs now possible
 Generic Document Interface may be
used to create new documents and list
of IDs to be marked
Production Order Confirmation
 Production order (or any other
document) is brought into Auto ID
Infrastructure, using Generic
Document Interface
 All order information is available in
Auto-ID Infrastructure
 Existing rule is modified to leverage
SAP standard functionality and add
custom logic for confirmation
 Value-Added Business Processes with Auto-
ID Infrastructure

RFID-Enabled Centralized WMS PTA with Cold Chain Monitoring

 RFID-Enabled Outbound Processing  You can extend Product Tracking &
 RFID-Enabled Internal Warehouse Authentication for cold chain
movements monitoring
 RFID-Enabled Inbound Processing

© SAP 2008 / Page 171

 SAP Product Tracking and Authentication

Enables companies to ensure safe production and secure

distribution of their products by providing visibility and
traceability of product flow across the enterprise and the
extended supply chain network
 Tracking the flow of products at multiple levels of hierarchy (item,
case, pallet, etc.) across the enterprise and extended supply network
to detect discrepancies between expected and actual product flow
such as shipping/receiving discrepancies, malicious product
movement, diversions, etc.

 Provide full traceability of all business events and transactions at

unique object level (item, case, pallet, etc..)

 Automated multi-layered authentication of products and validation

during any kind of goods movement to ensure product legitimacy

 Establishment of a chain of custody of the product to ensure consumer

/ patient safety, brand protection and a secure supply chain
SAP Product Tracking and Authentication Process Flow
 SAP Object Event Repository as Extended GS1 Object
Event Repository
SAP Object Event Repository
OER
Product Need a way to track a product as it SAP OER is an EPCIS-compliant enterprise level
serialization moves through the supply chain solution that serves as the system of record about
uniquely identified objects.
Need a way to store and manage EPCIS INTERFACE  tagged product flow at multiple locations,
Data capture multiple local processes
millions of transactions acquired by AUTO-ID Repository
& repository  interrelated tracking of child & parent objects
tracking product movement Event Management Analytics
Security Services and document associations
Industry Need a standards-based mechanism for  centralized data exchange with trading partners
Standard sharing data for multiple use cases  single set of interfaces and repository to
growing number of enterprise consuming
Secure data Need a way to share data with trading applications
EPCIS CAPTURE INTERFACE  support various data streams [EPC, Transaction,
exchange partners to identify business value
POS, …] to drive business value

Production on track Shipment received Send ASN Ship Ship Authenticate

Unpack Receive Dispense

Production completed
Authenticate Receive
Pack

Production Warehousing Distribution Sale

Suppliers Providers and

Retail RXs 3 PLs
Non-SAP
system Subcontractors
 SAP Object Event Repository
Sense & Respond with SAP Event Management

SAP Object Event Repository

OER
Empowered by the extensive tracking & tracing SAP Event Management offers full
functionalities of built-in SAP Event Management, flexibility to model end-to-end tracking
SAP OER is the global instance providing scenarios that deliver visibility for all your
EPCIS INTERFACE
visibility along your entire supply chain. supply chain activities
 Extract relevant process information from AUTO-ID Repository  Visibility on process level (Product
Event Management Analytics Tracking & Authentication, Order
globally distributed system into one central
Security Services
repository fulfillment, Procurement,
 Process monitoring, automated exception Transportation, Production)
resolution mechanisms, proactive alerting,  Visibility on asset level (track the
extensive reporting capabilities in one single lifecycle of inventories, capacities,
EPCIS CAPTURE INTERFACE resources)
solution
  Visibility on agreed performance
goals (measure and control
performance of SCM community
participants)
monitor notify adjust analyze

Suppliers
Retailers 3 PLs
Non-SAP
system Subcontractors
SAP GS1 OER Extension: SAP Event Management

Actual events

Unexpected event

event 1 event 2 event 3

event 1 event 2 event 4

Early/Late
Regular event
event Unreported event

Expected events
process milestones
 Visibility Processes in SAP Event Management

SAP ERP SAP Auto-ID

RFID-Enabled Outbound / Inbound
Procurement Outbound / Inbound Delivery
Delivery

Fulfillment Seasonal Procurement (Retail) Product Tracking & Authentication

RFID-Enabled Returnable Transport

Production Malfunction Railcar Management (Custom Dev)
Item
Ocean Carrier Booking (with TM
Transportation
Add-On)

Transportation Management Supply Network Collaboration

Resource Transportation Execution Responsive Replenishment

Order Taking Tendering Purchase Order

 New with SAP Auto-ID Infrastructure 7.1
New deployment option: SAP Auto-ID Infrastructure 7.1 as add-on to SAP ERP EhP5
 You now have the option to deploy SAP Auto-ID Infrastructure (AII) as add-on to ERP EhP5
 Note: SAP AII continues to integrate with SAP Object Event repository using SAP PI
New RFID-Enabled Process: RFID-Enabled Centralized WMS
 Goods Receipt w/ ref to inbound delivery and subsequent putaway
 1- or 2-step Internal bin-to-bin warehouse transfers
 Picking to Goods Issue with homogeneous HU

SAP Auto-ID Infrastructure Mobile Data Entry with SAP ITSmobile

 SAP ITSmobile is the mobile data entry integration platform used with SAP Auto-ID Infrastructure 7.1
 makes it easier to integrate online mobile devices and create custom mobile transaction

GS1/ EPCglobal Standards Updates

 Additional Application Identifier support for GS1 Data Matrix
 Added EPC Tag Data Standards support: GSRN-96, GDTI-96 and GDTI-113
SAP OER Performance enhancements: The new High-Volume Product Tracking & Authentication Process
 Optimization of SAP OER for high-volume processing allows handling of high volumes, including a specialized archiving
concept

“Cold Chain Monitoring“

 Cold chain monitoring capabilities have been introduced as an extension to Product Tracking & Authentication

New archiving features in SAP Auto-ID Infrastructure and SAP Object Event Repository
 AII: Archiving Kanban and objects without actions data with read access
 OER: Additional capability to define archiving sequences and access archived data from the Web Interface
 Business Intelligence – Reports with SAP AII
Business Monitoring & Reporting
 Stock Situation at Different Locations
 Movements across Locations
 Movements at Location by Action Type
 Cycle Time across Locations
 Current State of RTI Objects

Technical Monitoring & Reporting

 Read Rate quality reports
 Write Rate quality reports

Movements Across Locations

 Show shipping durations between different locations across the supply network

Movements at Location
 Show processing durations at a location

Proof of Receipt
 Check whether an object was received at any other subsequent location
Authentication / ePedigree
Pharmaceutical Drug Pedigree

Definition:
A drug pedigree is a statement of origin that identifies transfer of ownership for
each prior sale, purchase, or trade of a drug, including the date of those
transactions and the names and addresses of all parties to them.

Pedigree is a Drug Product’s Chain of Custody throughout the Supply Chain

Pharmaceutical Co Wholesaler Pharmacy

A Pedigree manifests itself as a signed, secure, documented

transactional record of a drug product’s every movement within
the supply chain.

© SAP 2008 /
 ePedigree Key Terms to Know

EPC (Electronic Product Code)

016.37000.123456.100000000
123456
123456
276543
276543
786459
786459
675439
675439
785923
785923

Serialization
1D
RFID

Pedigree Pedigree Pedigree

PharmaDrug PharmaDrug PharmaDrug
NDC # NDC # NDC #
Manufacturer Manufacturer Manufacturer
Wholesaler Wholesaler
Pharmacy

Pedigree 2D
© SAP 2008 /
Page 183
 California ePedigree Requirements
 For each RxDrug sold within the California supply chain, there
are three main components:
1. All RxDrug products must be serialized with a unique serial number
at an item level.
2. An ePedigree record (electronically signed) must be passed from
manufacturer to wholesaler to dispensing entity.

3. The ePedigree must be created in an electronic version that’s

interoperable with the Supply Chain as a whole.

2015: 50% of drugs sold in California must be authenticate-able

2017: 100%

© SAP 2008 /
 Food Safety Modernization Act
The FDA Food Safety Modernization Act (FSMA), was signed into law on January 4, 2011. It aims to ensure that the U.S.
food supply is safe by shifting the focus from responding to contamination to preventing it.
 This act gives FDA new and enhanced mandates and authorities to protect consumers and promote public health.

 Inspection and Compliance consists of

 Product Tracing
 Registration
Mandated inspection frequency: The FSMA establishes a mandated inspection frequency, based on risk, for food facilities and requires
the frequency of inspection to increase immediately. All high-risk domestic facilities must be inspected within five years of enactment and
no less than every three years thereafter. Within one year of enactment, the law directs FDA to inspect at least 600 foreign facilities and
double those inspections every year for the next five years.

Records access: FDA will have access to records, including industry food safety plans and the records firms will be required to keep
documenting implementation of their plans.

Product Tracing: The U.S. Food and Drug Administration announced Sept. 7, 2011, that the Institute of Food Technologists (IFT) will carry-
out two new pilot projects, one for processed foods and one for produce, at the direction of FDA to explore and demonstrate methods for
rapid and effective tracking and tracing of food, including types of data that are useful for tracing, ways to connect the various points in the
supply chain, and how quickly data can be made available to the FDA. The pilots are required, as is the FDA’s establishment of
recordkeeping requirements for high-risk foods to help in tracing products

After the pilots are completed and additional data are gathered, the FDA will initiate rulemaking on recordkeeping requirements for high-
risk foods to facilitate tracing

Registration: domestic and foreign facilities that manufacture, process, pack or hold food for human or animal consumption in the U.S.
must register with the FDA
About 48 million people (1 in 6 Americans) get sick, 128,000 are hospitalized, and 3,000 die each year from
foodborne diseases, according to recent data from the Centers for Disease Control and Prevention

© SAP 2008 /
 SAP Solution for Serialization & ePedigree

Life Sciences Company

Enterprise
Solution

OER EPCIS
Events
E-Pedigree Provider

SAP PI Pedigree

Trading
Partners

Plant Warehouse
Device Mgmt Device Mgmt
WMS

Manufacturing Distribution
Site Solution Site Solution

© SAP 2008 /
Authentication using GS1 EPCIS and SAP
Object Event Repository
Manufacturer
Hospital
2. Ship original item

1. Write authentication data into

central repository 4. Check original item
Original ID
Original TID
EPCIS identifier, 2D barcode, easy 0AF4439B07745113CE56
to duplicate

TID – Tamper proof security code

0AF4439B07745113CE56
3. Ship suspicious item. EPCIS identifier is
registered at central repository, but security
5. Check suspicious item code can not be copied
Original TID
Original Counterfeit TID EPCIS identifier, 2D barcode, easy
111122223333444455556666 to duplicate

TID – Tamper proof security code

Suspicious 111122223333444455556666

Counterfeiter
* PTA Product Tracking & Authentication
** OER Object Event Repository
Recent customers
Number of RFID Customers by Industry [225]
Mill Products

350+
1%
Media
1%

Services Mining
3% 1%

Industrial Retail Other

3% CPG
4% 3%
23%
O&G
5%
Utilities
5%

PS Chemica
5% 11%
A&D
5% Lifesciences
Auto
5% Hi-Tech Transportation 10%
6% 7%

© SAP 2008 /
Page 188
Example: Secure Tracking and Tracing, using SAP Patient
Management and SAP Solution for Auto-ID & Item Serialization

Mildred
Parker - Nurse

Rebecca Hansen –
Pharmacist

© SAP 2008 /
Novartis Focuses on Product Authentication
and Traceability
SAP Ramp-up Program Helps Firm Take Lead in
Defining Serialization Standards for Industry
 Closed-Loop Medication
Management

“Organizations use an integrated, electronic process from order to dispense for all
medication to eliminate errors in prescribing, transcription, dispensing, and
administration.”
 Impact of Current Medication Administration
Processes on Patient Safety

 7,000 deaths per year

 Number of serious ADEs

underestimated
 Medication errors are the greatest fear
of adults entering a healthcare system
 Potential ADE rate is 3 times greater in
a pediatric setting than an adult setting

Lancet: Vol. 351,February, 1998

AJHP: Vol. 46, May, 1998
ASHP: Research Report, September, 1999
JAMA: Vol. 285, April 25, 2001

© SAP 2008 /
 Where Do Med Errors Occur?

© SAP 2008 /
 Types of Medication Errors

 Drug omission  Wrong Rate

 Improper dose  Wrong Duration
 Wrong Strength/Conc.  Wrong Time
 Wrong Dosage Form  Wrong Patient
 Wrong Technique  Monitoring Error
 Wrong Route  Expired Drug

In this list of errors several have the potential to cause serious harm to a patient, others while in and of themselves
are errors, may not cause harm.

For example, a medication given at the wrong time, that is outside of the times specified by the medication order’s
frequency and schedule. These “wrong time” errors can be masked in a manual process; however, with a schedule
range set by a barcode-assisted administration system, these types of errors are identified each time.
Closed-Loop Medication Management
Reducing Medication Errors and
Adverse Drug Events, thus improving
medication safety
 Better documentation of drug orders
 Better administration (before, during, and
after patient stay),
 Tracking errors retrospectively,
 Predicting errors,
 Capturing interventions against errors.
Ensuring the “five rights” of medication administration:
 the right patient
 the right drug
 the right dose
 the right route
 the right time
Workflow transformation: eliminate error-prone steps in the process
 Closed-Loop Medication Management

The Challenge
Improve the efficiency and effectiveness of the medication management process.

The Approach
 Standardize the process
 Reduce process variation
 Eliminate unnecessary steps (waste) > Six Sigma, LEAN
 Reduce opportunity for error
 Measure results

The Tools
 Process redesign
 Cultural change management
 Technology

© SAP 2008 /
Closed-Loop Medication Management:
Key Components
CPOE and/or
e-prescribing
Medication orders pass CDS and
flow to Pharmacy
and/or Ward

eMAR
Update and availability for Pharmacy /
review, override management Nurse
and future CDSS interactions Validation of order
and dispensing
of Unit Doses
(e.g. by ADM) with bar code or
complete prescription information
NB: compounded vs. packaged med

ADM
Optional
POC Administration
Secure identification of nurse,
patient and medication at POC by
 bar code scanning or RFID
 POC registration in eMAR
 dual signature for critical meds
Closed-Loop Medication Management: Stage 5

The closed-loop medication administration environment is

fully implemented. The eMAR and bar coding or other auto-
identification technology, such as radio frequency identification
(RFID), are implemented and integrated with CPOE and pharmacy
to maximize point-of-care patient-safety processes for
medication administration.
VALUES
 Improves patient safety - reduces or eliminates medication errors
 Improves outcomes by reducing the time from medication order to medication
administration
 Improves medication management by identifying potential medication errors that
clinicians may not be aware of
 Improves the tracking of all medications dispensed and administered
 Provides a data set to improve the management and administration of medications for
use in both outcomes and protocols analyses
 Nurse recruiting and retention are improved
Case Study: Wake Forest University Baptist Medical
Center
People, Process, and Technology

1. An integrated systems approach.

2. Ensure that the software flexibility is used in the design

3. Be prepared to introduce best practice processes.

4. Implement a cultural change management plan to assist staff to accept change

80-90% of major IT projects fail to achieve their human and technical objectives on time
and within budget.

90% of project failures are due to neglecting the human factors of the project.
Achieving Maximum Value from IS.
D. Remeni, M. Sherwood-Smith, T. White 1997
Importance of Process: Developing Standard Work
with LEAN Principles

Steps to establish standard work processes

 Observe and understand the work (“walking the Gemba”)
 Measure and time the activities in the work process
 Analyze the work
 Validate the process
 Identify and eliminate the waste
 Standardize the new work cycle
 Set targets and re-measure
 Measure Value by Process, using KPIs

Starting at the right of the diagram

the organization’s strategic
initiatives or success factors are
identified.

These should reflect a Balanced

Scorecard approach, based on
Kaplan’s original balanced
scorecard model. This model
suggests that organizations must
focus on more than one area or
objective to achieve strategic
success.

Traditional ROI has cash implications and can mislead an organization into believing that returning $$ to the bottom line is the
strongest objective. The Balanced Scorecard approach includes cost savings, but focuses on other strategic objectives, such as quality.
The 4 quadrants of the balanced scorecard start with what your value is and the strategic success factors defined by your organization
– e.g.,
 Medication errors at administration -- costs associated with each ADE is $4,685 per occurrence (credit in notes)
 Compliance with the 5 rights
 Time savings in the administration process
Ordering: Error Reduction

Key Considerations
 Standardized pre-printed order forms.
 Approved protocols.
 Policies limiting verbal orders – requiring read-back.
 Computerized Prescriber Order Entry (CPOE)
CPOE Order Set and Guideline Approval
Advantages and Benefits Realized

 Eliminated all manual order transmission activities.

 Eliminated all order transcription activities.
 Integrated physician, nurse and pharmacist workflows.
 Provided consistent patient and clinical information to all caregivers.
 Eliminated shift and 24-hour chart checks.

However, it should be acknowledged that CPOE does introduce new types of

errors -- the “point-and-click” errors that will cause the wrong dose, or even
the wrong “John Smith,” error.
Benefits Measured: EMR and CPOE*

 Concurrent access to charts (no more “chart-chase”).

 Prevention of over 65,700 duplicate/conflicting tests per year.
 Avoids $2,673,989 in direct expenses per year.
 Reduction of $322,445 per year in Medical Records costs.
 Reduction of $149,000 in Outcomes Management administrative costs per
year.
Administration: Error Reduction

 Point of care verification and documentation system.

 Ensure compliance with the five rights of medication
administration.
 Accurate and efficient documentation.
 Nursing double check at administration.
 Barcode-Assisted Medication Charting
Barcode Medication Charting

Requirements
 Worklist charting capability that supports BCMC.
 Radio frequency capability.
 Barcoded wristbands for patients.
 Barcodes on nursing badges.
 A non-punitive error reporting system.
 Utilize error reports to foster Continuous
In adding BCMC to the medication management process, additional cultural
change, process and technology changes had to be addressed. These issues were
vital to success.
Objectives and Benefits

 Aligns KPIs with strategic success factors.

 Provides methodology to define and achieve value through people, process,
and technology improvements.
 Demonstrates performance improvements through pre- and post-
implementation KPI measurements

The key to maximizing benefits is to utilize a combination of cultural change

management, process improvement and technology to drive and sustain change
in an organization. Should any one of these key components be missing, the
benefits achieved will not be a full as they could have been.
The process component and the cultural change component are more important
than the technology itself.
From Manufacturing to Dispensing:
Step-by-Step Event Recording
in the Object Event Repository
1. Manufacturer: Serialized Product Transferred to
SAP OER

Globally-unique identifiers are  Attributes related to identifier optionally are encoded

encoded in 2D barcode on the into barcode on the packaging and not used for
packaging. Four smaller packages, identification. Created by manufacturer, they remain
serial numbers 2020100 to constant throughout the lifecycle.
2020103, are packed into a larger  GTIN is maintained in EAN/UCC field in the standard
package with serial number ERP and IS-H Material Master, as well as in the SCM
2020. Product Master.
1. Manufacturer: Commissioning-to-Shipping
Single Item Lifecycle in SAP OER
1. Manufacturer: Commissioning-to-Shipping
Package Lifecycle in SAP OER
1. Manufacturer Packaging Hierarchy in SAP OER
2. Medication Received at Central Pharmacy, Delivered
to, and Received by, Nursing Unit
3. Box Unpacked from Case 2020 at Nursing Unit
3. Dispensing Units 2020102 and 2020103 Unpacked
from Box 2020
3. Dispensing Unit 2020100 Given to Patient
3. Three Pills taken from Dispensing Unit 2020101 and
Given to Three Patients
Reporting Example: Batch
Unit Dose Quantity/Tracking of Partial Quantities

 Serialized/batch managed unit can be disaggregated before

consumption
 Pills from one blister pack can be dispensed to several patients
 Single pills are associated with serialized daily dose box, which is tracked
until dispensed
 Partial quantities of serialized unit may be mixed during hospital
pharmacy production (e.g., compounds). The resulting batch GTIN is
tracked until dispensing, thus relating the patient and ingredients.
 Disaggregated quantity is posted as physical unit of measure, not
as number of pills, because one pill could be divided into 2 or
more parts
 Approach with unit of measure also works for liquids dispensed in
partial quantities or used in hospital Pharmacy production (e.g.,
for hyperalimentation solutions)
How to Get Started

1. Contact your GS1 Member Organization for guidance

2. Get familiar with the standards / guidelines
 Participate on GS1 implementation projects / team
 Download: GS1 System Landscape http://bit.ly/hYVe1y & GS1
Integrated Communication (ICOM) http://bit.ly/ebjqk6
3. Do a gap analysis…your items vs. GS1 Standards
 Focus on key items and facilities…don’t “‘boil the ocean”
 Build action plans, budgets, and management approval
Implement your multi-project action plan
 3-5 years
 “Walk before you run” -- start small, conduct pilot projects, learn by doing, and
build on successes
 References

SAP and GS1 Standards Wiki: http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=141262923

 Contains, among other things, a section on Bar Code printing and other GS1 standards information
SAP and GS1 Standards BPX (Business Process Expert) BLOG: http://www.sdn.sap.com/irj/bpx/gs1-standards
GS1 at SAP Collaborative Workspace: https://cw.sdn.sap.com/cw/community/sap/gepg_sms/gs1
SAP GS1-related links in SDN and online magazines: http://wiki.sdn.sap.com/wiki/display/GS1/Links
SAP Help GS1 Documentation:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/eb/c8cddb698911d6b23000508b5d5211/frameset.htm
GS1 U.S. Healthcare: http://www.gs1us.org/sectors/healthcare
 Includes, among many items, Healthcare Provider and Supplier Toolkits and Healthcare Provider, Supplier, and
Solution Provider GLN Scorecards that show you which providers, suppliers, and solution providers are GLN-ready
GLN Registry: http://healthcareportal.gs1us.org/glnregistry/Home/tabid/36/Default.aspx
 Includes GLN Subscription, GLN Industry Readiness Scorecards, GLN Customer Support, and many related Quick Links
GS1 Community Room:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/eb/c8cddb698911d6b23000508b5d5211/frameset.htm
GS1 at Johns Hopkins
Who We Are

 In 1873, Johns Hopkins, the merchant and investor,

bequeathed $7 million to fund a hospital and
university in Baltimore, Maryland
 It was the largest philanthropic gift in the history of the United
States at that time
 The majority of his wealth was acquired by investments in the
Baltimore and Ohio Railroad
 Johns Hopkins is a world leader in patient care,
research, and teaching
 The Hopkins enterprise consists of the university and health
system
 Combined gross revenues are in excess of $6 billion dollars
 Employee base is approximately 45,000
Johns Hopkins Organizational Structures

Johns Hopkins consists of two parent corporations with subsidiaries – Johns Hopkins
University and Johns Hopkins Health System (JHHS). A virtual entity, Johns Hopkins
Medicine (JHM), consists of JHHS and the School of Medicine.
SAP History
 Live since January 1, 2007. Upgrade went live May 18, 2010.

 SAP ERP 6.0, EHP 6

 SAP SRM 7.0, EHP1
 SAP NetWeaver® BW 7.0, EHP 1
 SAP NetWeaver Portal 7.0, EHP 1
 SAP NetWeaver PI 7.1
 SAP Solution Manager 7.0, EHP 1
SAP NetWeaver MDM (new for
SAP SRM)
 GRC Access Control 5.3
SAP History (cont.)

The original implementation in 2007 was a “big

bang” go-live, as was the May upgrade
One SAP company code was chosen with business
areas representing some legal entities, lines of
business, or consolidation requirements
Currently have approximately 10,000 SAP users
The Johns Hopkins solutions are considered fairly
complex and require a sizeable team to support and
maintain them
Johns Hopkins was one of the first customers
worldwide to implement SAP SRM 7.0
GS1 at Johns Hopkins – GLNs

All delivery addresses are mapped to a specific GLN in a

custom table (table also includes “customer number”):
GS1 at Johns Hopkins – GLNs
 Johns Hopkins utilizes SRM for 100% of its Procurement
 SRM users create shopping carts/requisitions using an SRM Internal Delivery
Address Number. The associated GLN and Customer Number is sent to the vendor.

 Johns Hopkins uses GHX for much of the PO and Invoice transmissions*. Currently,
28 vendors receive the Johns Hopkins’ GLN; 10 use the GLN exclusively.
 Only Delivery Addresses are set-up with GLNs at this time. Invoice addresses,
Purchasing Department address do not have associated GLNs.
GS1 at Johns Hopkins – GTINs
GS1 at Johns Hopkins – GTINs

Johns Hopkins has created a “holding table” for material GTIN information. This
information has not yet been imported to the Johns Hopkins Material Master
records.
GS1 at Johns Hopkins – GTINs

 Vendor barcoding of GTINs is not yet standardized

 The GTIN Tool Kit has 29 different barcode examples!

 St. Jude and other clinical vendors are heading in various directions!
GS1 at Johns Hopkins – Where we’re headed…

Hospital Acquisitions and yearly SAP implementations are

requiring a process of consolidating material master
information:
• Matching based on MPN and UOM
• Assignment to existing or creation of new Material Master record
Process is not clean or foolproof
Exploring GTIN as available

UDI – Unique Device Identifier begins to come into focus

Will ultimately require consolidation of Materials data set
and Patient information (EPIC)
GS1 at Johns Hopkins – Where we’re headed…

Live with GLNs!

Exploring the SAP options for capture and transmission of
GTIN information
Largely awaiting the Healthcare Supply Chain members to
align and communicate
Anticipate a data cleansing effort to consolidate product
GTIN information to the SAP Material Master records
(could REALLY use an SAP load program to do this!)
KPIs for error reduction
How to Get Started

1. Contact your GS1 Member Organization for guidance

2. Get familiar with the standards / guidelines

 Participate on GS1 implementation projects / team

 Download: GS1 System Landscape http://bit.ly/hYVe1y & GS1 Integrated
Communication (ICOM) http://bit.ly/ebjqk6

3. Do a gap analysis…your items vs. GS1 Standards

 Focus on key items and facilities…don’t “‘boil the ocean”

 Build action plans, budgets, and management approval

4. Implement your multi-project action plan

 3-5 years
 “Walk before you can run” -- start small, conduct pilot projects, and learn by doing
 ©
SAP
Thank you! 2008
/
Page
245
Contact

Dow Weeks Jon Arck

SAP Project Manager Director, Healthcare Provider IBU
Johns Hopkins Medical Center SAP Labs, LLC
dow@jhu.edu jonathan.arck@sap.com
... 925-325-5317
 APPENDIX

GS1 Approach to Enabling Customers

Premier GLN Transaction Program
Additional GDS and Traceability Details
Executive Summary: Roadmaps for GLN
Implementation Across U.S. Healthcare
GLN Roadmap: a Collaborative Industry
Implementation Plan
GS1 Standards: Implementing GLNs (1/3)

1.Establish Executive Support: inform and educate executive management on standards adoption and
the need for organization-wide implementation, and to obtain executive approval to proceed with
GLN implementation
2.Form a GLN Management Advisory Group: establish an Advisory Group. Formation of a cross-
functional Group including members outside of supply chain functions promotes buy-in, supports
communication efforts, and ensures proper input from the areas most impacted by implementation
3.Determine whether a GLN Registry Exists in your Country: there must be one person (i.e., the
Primary Point of Contact) that has the primary responsibility to build and load the hierarchy in the
GLN Registry. Contact your local GS1 Member Organisation to determine whether a national GLN
registry exists
4.Develop & Initiate Project Communication: inform your community of your commitment to GLN
implementation. Utilize internal communication tools such as newsletters and intranet to introduce
the concept and benefits of the GLN, and the GLN Registry for Healthcare if it exists, to your
company, and external communication tools like websites and corporate letters for your customers
and suppliers.
5.Initiate Education for the Advisory Group & Operational Team: educate company participants. A
base level of knowledge about GLNs, the GLN Registry, GS1 Healthcare, and GS1 standards is
necessary for all active participants
GS1 Standards: Implementing GLNs (2/3)

6.Assess Information System Issues & Make Necessary Changes: evaluate the readiness of your
information systems, and make the appropriate system changes required to accommodate the use of
GLN. The capability of your information system to contain and utilize GLN numbers must be assessed,
and the necessary changes made. The necessity of parallel files between the old location numbers
and GLNs must be discussed.
7.Identify/Allocate Your GLNs: allocate your GLNs. In this effort, you must consider your company’s
GLN strategy and current customer requirements and then align the two. Specifically, you must
determine:
8.Whether your company will allocate GLNs to the main corporate address only, or also to divisions,
departments, receiving locations, etc.
9.How your organisation will manage the issuing / allocation of GLNs and associated record keeping,
i.e., will these two functions be undertaken by a central entity within the organisation, in a
distributed manner by different regional branches or in a hybrid model
10. Establish Implementation Strategy: establish a GLN utilisation strategy and corresponding
hierarchal organisational chart (e.g., warehouse system hierarchy; divisional hierarchy; etc.). The
establishment of your organisation’s GLN hierarchy is a critical step in the implementation process.
It is necessary to consider not only how business is currently conducted, but also future business
processes and supply system possibilities.
GS1 Standards: Implementing GLNs (3/3)

11. Build Your GLN Database: build an internal database to house GLNs and to enter the company GLNs
into the GLN Registry if applicable. Specific information for each location that has been identified
for enumeration must be gathered for this effort.
12. Engage Customer & Supplier Involvement: prepare your customers or suppliers community and
identify partner(s) for testing. This is the most important step in this process. Collaboration and
communication with your customers and suppliers is critical to implementation success
13. Conduct Transactional Testing With Customers & Suppliers: successfully exchange purchase
transactions with your customers and suppliers. At this point, you are ready to conduct
transactional tests. The testing process will provide validation of the initial hierarchy, information
system capabilities and operational impact.
14. Make Adjustments to Initial GLN Hierarchy & Implementation Plan: keep the hierarchy consistent
with your company’s business model and to ensure that it remains accurate in order to obtain
maximum benefit and to ensure accurate delivery locations. This is an iterative process based on
your transactional testing with customers and suppliers
15. Create Standard Operating Procedures: document standard operating procedures and obtain sign
off, both internally and externally. Following testing and the implementation of the necessary
adjustments, it is necessary to prepare standard operating procedures for internal and external
staff. The Advisory Group and Operational Team should be heavily involved in this process.
Premier GLN Transaction Program
Launched in mid‐2009 to outline the process for GLN implementation for its member hospitals.
Objectives
 Better understand the use of GLN Registry for Healthcare®
 Identify the steps to GLN implementation
 Identify challenges in implementation
 Share lessons learned
Project Milestones and Action Items
Trading Partner Selection
 Providers: Start by pairing-up with one or more Suppliers that meet requirements
 Suppliers: start by pairing-up with one or more Providers that meet requirements
GLN Synchronization
 Providers: Your GLN Hierarchy already has been set-up in the GS1 US GLN Registry for
Healthcare®. Validate that the locations are correct, and then share your primary Ship-to GLNs
with your Supplier Partner(s).
 Suppliers: there is no need to enumerate your company at this time, though it is recommended.
You will receive the Primary Ship-to GLNs from your Provider Partner(s) and confirm that they
match-up to your current Ship-to Accounts for them.
System Integration
 Providers: Your validated GLNs now need to be uploaded to your MMIS. You may either load
all GLNs or limit yourself to just those GLNs tied to your old Account Numbers. In preparation
for transactions, you will need to ensure that the GLN is included on the PO. It is recommended
to first test in a Development environment. If applicable, confirm that your Exchange is ready to
receive and transmit your orders.
 Suppliers: Ship To GLNs for your Provider Partner should be uploaded to your fulfillment
system. Your system will need to be able to receive a PO with the GLN and recognize that GLN
as the correct customer and Ship To. It is recommended to first test in a Development
environment. You may need to coordinate with your Exchange to confirm how the GLN will
appear in the orders they forward to you.
Transact Purchase Orders
 Providers: Begin sending POs to your Supplier partner(s) in your Test, then Production,
environments
 Suppliers: Begin sending POs to your Provider partner(s) in your Test, then Production,
environments
Lessons Learned Document
 Providers and Suppliers: Document lessons learned and cost savings/avoidance
Premier GLN Transaction Program:
Key Experience Takeaways and Prep Benefits
Key Takeaways
 Take control and clean-up your hierarchy in the GLN Registry for Healthcare® as early in the process
as you can.
 Communicate and plan with your vendor partners frequently during the process.
 It is better to try things on a smaller scale and grow from there.
 Make sure that your roster update process is robust and include the GLN on all RFPs to accelerate
adoption.
 Wait until you have a good understanding of GLNs and the hierarchy before assigning GLNs to every
delivery location.
 Work with your suppliers, your MMIS/ERP vendor and your e‐commerce/exchange provider as early
as possible to ensure that your system and partners are ready to conduct transactions.

Preparation for GLN usage has many benefits, including :

 Cleansed master data (“got MDM and MDG?”)
 Strengthened supplier and GPO relationship with streamlined communications
 Confidence in the information the GPO and supplier partner has for “ship‐to” locations
 Established a replicable GLN preparation process that can be used for the next trading partner
Experience summaries of program are available.
GS1 Standards: Implementation (Premier
Example)
The 7-digit company prefix allows 100,000 GLNs or GTINs, which should be more than enough
 VA has one prefix for its 164-hospital system
 Sisters obtained one prefix for GLNs and GTINs their entire system. They are the 8th largest Catholic hospital
system in the US.

Premier ‘s approach to comprehensive standards adoption

 2008 – Launched outreach and education program for providers and suppliers; modified contract to include
requirements for standards compliance.
 2009 – Requested that providers and suppliers recognize GLNs and that the suppliers begin to register GTINs for
their products.
 2010 – Champion recognition and use of GLN by all providers and suppliers.
 2012 – Champion use of GTIN for all products from all suppliers, and the use of GTINs by all providers.

As a service to its members, Premier has allocated GLNs to providers, including all owned facilities and
affiliates. There are more than 70,000 locations registered to Premier providers in the Registry. As a
result of this effort, the hierarchy used in the Registry matches the structure used in the Premier
member roster
Premier’s official GLN hierarchy for all members and associated addresses:
 Level One is the Main Parent, the location that actively receives products or the corporate entity used in Premier
records.
 Level Two is any entity that reports directly to the Main Parent.
 Level Three is other buildings and/or the subordinate departments of Level Two.
 Level Four is an additional level that can be used for desktop delivery or Just-in-Time (“JIT”) locations.
GS1 Standards: Implementation (Premier
Example) -- Steps to GLN Implementation
1. Reconcile with GPO Roster: although Premier had registered GLNs on behalf of its membership, provider
participants found that the information housed in the Registry was not always consistent with how they
themselves would ascribe GLNs for their organization. Providers worked to cleanse and reconcile the information
in the Registry – either directly with the Registry or with Premier.
 Providers in this program reported that this process took approximately five to eight hours. “You should cleanse
your location data before you build your GLN hierarchy. No one knows your hospital system like you do, so make
sure your GPO and the GLN Registry are in sync with how you want your organizational structure to look like,
and have them make corrections if needed.”
2. Take maintenance control of Registry information: As hospitals open and close, new affiliations are added or
offices move, GLNs will need to be updated. Participants recommended that someone on staff be assigned to
either work with the GPO to keep the Registry and GPO Roster information up to date and current, or
self‐maintain the information work.
3. Establish proper GLN hierarchy strategy: Once you have accurate GLNs assigned at the highest levels (parent
location), you’ll need to establish the proper hierarchy of locations in the Registry, including affiliated clinics,
laboratories and other facilities. Keep in mind, when making assignments, that GLNs can be used for many
business purposes, including, but not limited to: GPO rostering, distributor sales tracings and ecommerce
transactions.
4. Communicate with your GPO and those organizations enabling your e‐commerce transactions to make sure
your GLN hierarchy is in alignment across all parties: This is an important step to ensure that GPO reporting is
accurate, rebates are sent to the correct facility at the correct time, and orders sent via electronic commerce have
accurate information for shipping and other supply chain requirements.
GS1 Standards: Implementation (Premier
Example) -- Steps to GLN Implementation
5. Cleanse and reconcile your “ship‐to” locations: Early coordination with your trading partners and
e‐commerce/exchange provider is critical to this process. Without proper coordination between all parties in the
transaction process, your transactions could fail.
Select supportive supplier partners who are ready to meet your GLN needs. Review your “ship‐to” locations with
participating suppliers to ensure GLNs in the suppliers’ systems are appropriately mapped to the existing
supplier‐assigned account numbers for those “ship‐to” locations.
6. Upload GLN to your MMIS or ERP system
7. Begin transacting using GLN: Understand the method by which your supplier conducts e‐commerce and how it
works with your system before you begin transacting with the GLN. There is no “one size fits all” approach
8. Identify challenges and establish work-around solutions, when appropriate: Participants experienced challenges
in two main areas: systems which required upgrades or patches to allow the use of GLNs in EDI, and the need for
dedication and close communication among all parties involved in transacting purchase orders: provider, supplier,
MMIS vendor and e‐commerce/exchange provider.
Barriers not encountered, but considered possible by participants, included lack of available resources to
support upfront time involved in cleansing and reconciling account information with GPO or supplier or MMIS
vendor, e‐commerce/exchange provider partners.
9. Stay involved and contribute to the growing healthcare GLN knowledge bank: Take advantage of existing
resources, including educational programs and materials from organizations such as your GPO, your MMIS/ERP
Vendor, your ecommerce/exchange provider, GS1 Healthcare US, and industry organizations, such as AHRMM,
SMI, and MDSCC
Premier GLN Transaction Program:
Lessons learned from Phase 1
 Preparing to implement the GLN can be done right now and in short order, with immediate benefits ‐‐
regardless of other implementation challenges that may exist. By doing so, the mystique involved with
GLNs will become manageable

 Participants identified several steps of GLN implementation that were consistent across the board, and
that are detailed in the program summary.
• Reconciliation with GPO Roster.
• Establishing maintenance control of Registry information.
• Establishing proper GLN hierarchy strategy.
• Communications with GPO to align GLN hierarchy.
• Cleansing and reconciliation of “ship‐to” locations with suppliers & exchange providers.
• Uploading of GLN to provider information systems; make necessary changes to enable EDI
transactions to include GLNs and replace custom numbers.
• Begin transacting using GLN.
• Identifying challenges and establishing work around solutions when appropriate
• Staying involved
 Participants agreed that implementing the GLN is completely achievable within a reasonable
timeframe.
 Participants found that the work required to support GLN implementation is largely front‐loaded.
Premier GLN Transaction Program:
Lessons learned from Phase 1 (cont’d)
 All participants felt that providers should start small and basic -- work on Level 1 in the GLN
Registry (parent organizations) and establish the correct “ship‐to” locations.
 Providers agreed that establishing a process for maintaining GLN information in the
Registry is extremely important.
 Providers felt that selecting a strong, customer‐oriented supplier partner for the initial GLN
implementation is important – “we’re all in this together”
 Participants felt strongly that hospitals should drive GLN implementation with supplier
partners. In most cases, suppliers will comply with customer requests and collaborate to
figure out how to overcome implementation challenges.
 Providers felt that the exercise in preparing for GLN implementation was valuable and
important, and overwhelmingly felt that they “were ready to go.”
 All participants felt that providers should get started with GLN implementation right away,
and, by doing so, the mystique involved with GLNs will become manageable.
 Participants agreed that implementation can and should occur in a phased approach.
 Stay educated and get involved in GS1 Healthcare workgroups
A Kraft document “Kraft Foods Best Practices for GS1 Company Prefixes” can be found here.
Premier GLN Transaction Program:
Lessons learned from Phase 2
In Wave Two of the Premier GLN Transaction Program, member organizations and supplier partners
were put together in 14 “pairings” to implement GLN and advance industry knowledge of the challenges
and opportunities related to GLN adoption. Participants from all sides of the supply chain – group
purchasing organization, provider, manufacturer, distributor, MMIS/ERP vendor and EDI exchange
provider.
 As in Wave One, participants felt that even in circumstances where transactions did not take place,
they had become better prepared through the participation experience.
 Participants agreed that GLN adoption is at an early stage, and there is no clear “GLN implementation
template” that can currently be leveraged completely across the board. Experiences like Premier’s
GLN Transaction Program, according to participants, are helping in bringing the right parties to the
table to drive industry momentum for GLN implementation
 It is essential that the GLNs enumerated and used by the healthcare provider are displayed accurately
on the GPO roster and are the same ones utilized by the distributor, supplier, and any exchange
partner or third‐party company that will handle the transaction data between the trading partners.
 Ship-to locations, in particular, must be cleansed and reconciled with suppliers, including distributors and
manufacturers with which you have direct trading relationships and with exchange providers that facilitate EDI
transactions.
 It is essential that trading partners agree on common process rules and timing when changing, adding
or modifying locations using GLNs.
 Understand your MMIS system capabilities, as well as process protocols established by trading
exchanges (e.g., GHX).
 Significantly Reduce Manual Steps in Data Creation
and Communication
Embedding of MDM Workflow
 Different triggers available: Import, New Trade Item, Item Modification, Automation Process,
Unprocessed Messages (Registration, Publication, Link and Import Error), Manually
 Standard Workflows for each Trigger are part of the delivery
 Workflows can be extended or completely new created*
 Actions available: Create, Start, Cancel, Next Step, Repeat Step, Reassign
 Approval Step Feature
Automation of the following processes
 Validation of trade items in inbound process
 Registration of successfully validated trade items
 Correction of modified trade items, that have already been published

*requires appropriate MS visio license

©
Placeholder WF Screenshot
 Limit Access and Focus Users on What Really Matters
Granular authorization concept to better embed work into existing roles and focus on
specific tasks

 For different operations, access

can be granted, based on
values of specific attributes
Identify Who did What for Better Error Reconciliation

Reuse of the MDM change tracker functionality

 Search by different categories
 Target Market-specific
 Global Data
 By specific criteria
 Date
 User
 Field
 Language
 Free-text
 Display complete item history, including old values
Hierarchy of Systems

SAP Object Event Repository = Corporate traceability repository for item

serialized products

SAP NetWeaver Process Integration (PI)

SAP AII

SAP AII
SAP NetWeaver Process Integration (PI)

SAP ERP SAP ERP SAP ERP SAP ERP Non-SAP Non-SAP
SAP OER Item Tracking

on
tracked items via freely
configurable selection
profile

to
actual status of serialized
products all across the
globe

– SAP OER stores each transaction that

is performed for serialized products and serves as the global system of record.
SAP OER Item / UII lifecycle Tracking
High Resolution Traceability & Situational Insight

-
SAP OER stores
hierarchies between
objects along their entire
lifecycle
SAP Product Tracking and Authentication

Status can be verified in

the Repository

EPC number is
authenticated against Tag
ID and/or other
configurable attributes
that are known in the
repository
Usage of Fixed RFID Readers and Forklift and Location
Identification
Example Usage of Fixed Gate Readers Warehouse Bin
Location Identification
Unload Readpoint with Passive RFID Tags

Storage Location Entry Readpoint

Storage Location Exit Readpoint

Storage Location Load Readpoint

Forklift mounted RFID Readers

RFID-Enabled Forklift with

Mounted RFID Readers
 RFID-Enabled LES with Centralized Warehouse
 Required Components if deployed with AII as add-on to ERP EhP 5

SAP Auto-ID Infrastructure 7.1 Add-on installation on ERP 6.0 EhP 5

 SAP Auto-ID Infrastructure 7.1
 ERP EhP 5 on ERP 6.0 Instance
 SAP EHP2 for SAP NetWeaver 7.0

SAP AII 7.1 Add-on

SAP ERP 6.0 EhP5

(SAP ERP 6.0)

SAP EHP2 FOR

SAP NETWEAVER 7.0
Auto-ID Standards: New Application Identifier Support
for 2-D Data Matrix Data Capture
 A data matrix symbol can include several elements, each of which is identified by an
application identifier (AI).
 Examples of application identifiers:
 GTIN
AI Data Content/Element
 SSCC
 Serial Number 00 SSCC (Serial Shipping Container Code)
01 Global Trade Item Number (GTIN)
 Batch or Lot Number 02 GTIN of Contained Trade Items
 Expiration Date 10 Batch or Lot Number
11 Production Date (YYMMDD)
12 Due Date (YYMMDD)
13 Packaging Date (YYMMDD)
15 Best Before Date (YYMMDD)
17 Expiration Date (YYMMDD)
20 Variant Number
21 Serial Number
…
What is the relevance?
> Pharma item serialization requires the 2-D Data Matrix <
Copyright 2012 SAP AG
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 AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400,
S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect,
RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP France in the United States and in other countries.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of
SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product
and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without
notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This
document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials
.
This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse
your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.
Stay in Touch
Join ASUG or Learn About Your Membership Benefits
memberservices@asug.com
Stay in the Know, Subscribe to ASUG Newsletters
Visit asug.com/newsletters
Visit ASUGNews.com for independent, unbiased,
and customer-focused coverage of SAP.
 TWITTER:
https://twitter.com/ASUG365
 FACEBOOK:
https://www.facebook.com/ASUG365
 LINKEDIN: http://www.linkedIn.com/groups/Americas-SAP-Users-Group-
ASUG-112172/about