SAP Support for GS1 Standards

SAP Support for GS1 Standards Jon Arck CMRP, CIRM / Director, Healthcare Provider IBU, SAP Labs

Dow Weeks / Chief Solution Architect for the SAP Solution and Project Manager of the

SAP Support Supply Chain Team, Johns Hopkins

[

Real Experience. Real Advantage.

[

2

You, the Audience

Who among you:

Is familiar with the GS1 data standards GLN and GTIN, the

Global Data Synchronous Network, and Traceability?

Is conducting business using any of them?

Is in the process of implementing any of them?

Is aware that SAP has supported GLNs and GTINs for several

years, and has the functionality in core since 2010?

Has downloaded any of the GLN Enhancement

Guides/”Cookbooks” that were made available in December

2010 in the SAP Market Place for Healthcare? .


[

3

Learning Points

What is GS1, its role in data standards, and the overall vision of

the standards?

What are the GLN and GTIN; why should you implement them?

Core GLN functionality in SAP ECC

Enhanced GLN functionality available through published guides/

”cookbooks”

Core GTIN functionality in SAP ECC

Bar Coding and Labels

Global Data Synchronization

Supply Network Traceability through the SAP Object Event

Repository (OER) and SAP Event Management


[

4

Key Learnings

GS1 (formerly, the Uniform Commercial Code, or UCC) is a global data standards

organization that is working with the Healthcare industry to establish location and

item data and traceability standards

The GS1 System is an integrated suite of global standards that provides supply chain

visibility through the accurate identification, capturing, and sharing of information

regarding products, locations, assets, and services.

Numerous Industry groups and integrated delivery networks, group purchasing

organizations , and suppliers have endorsed GS1 standards.

SAP currently maintains GLNs for ship-to, bill-to, order-from, ship-from, ordered-by,

and pay-from addresses

Expanded to sixteen with the 2010 GLN Enhancement Project

SAP support for GLNs on transactions

SAP support for GTINs on transactions

How SAP Traceability enables track-and-trace across the entire healthcare continuum

– from manufacture through patient dispensing and follow-on, multi-dimension

reporting.


[

5

Return on Investment

Benefits from “real-world” implementations include

Enhanced patient safety

Product traceability in a complex, global supply chain > brand protection, product authentication and

reduction in risk of counterfeit or fraud

Reduced medication errors (patient/drug matching)*

Product safety and support withdrawal or recall

One source for product data > improved data accuracy

No Unit of Measure EDI errors

Accurate product data (manufacturer ID, expirations, clinical attributes, etc.) > no 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

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

*Hospitals average 1 medication error per patient each day, per the Institute of Medicine


[ SAP and GS1 Standards

SAP provides GLN, GTIN, and UNSPSC support on Purchasing, Inventory, Logistics, and Invoice

documents NOW, 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, 3PLs, insurers, and others can take advantage of SAP‟s ERP and EPCIS-certified

Auto-ID Enterprise products that support GS1 standards.

SAP continues to support evolving GS1 standards worldwide for the healthcare

ecosystem.

SAP solutions for ERP and Auto-ID and item serialization enable: Supply chain execution

Outbound logistics

Inbound logistics

Invoice processing

Asset management

NOTE: GS1 data standards functionality (GLN and GTIN) 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


[

7

GS1 System of Standards & SAP Solutions

SAP for Global Data Synchronization (consumer product

solution to upload data to Data Pools, based on MDM)

GDS for Retail (part of SAP ERP) GD

SN

G

LN

G

TIN

Supported by SAP Business Suite (master data and electronic

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

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

S-GTIN (as EPC encodings) support by SAP Auto-ID

EPCIS-certified repository

Secure Track & Trace SAP Life Science Solution

ePedigree data assembly for ePedigree documentation, together with

partners, such as SupplyScape

SAP Auto-ID Enterprise supports RFID, barcode and 2-D Barcode

(ECC 200 Matrix barcode is the most relevant at this time)

SAP Solution Offering

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) UN

SP

SC

T

raceab

ilit

y


[

© SAP

2008 /

Global Location Number (GLN)


[ What is the GLN?

The GLN is a standardized, globally-unique, 13-digit number used across the supply network to identify any

legal or functional entity, trading party, or physical location for business communications (at whatever level of

granularity is needed by the healthcare provider, manufacturer, supplier, distributor, GPO, exchange, etc.)

Legal entity

Healthcare hospitals and providers

Manufacturers

Wholesalers

GPOs

Exchanges

Distributors

Third-party logistics

Functions within a legal entity

Nursing

Ancillary or business department

A GLN can represent:

Physical locations with a single point of access with a

physical address

Hospital, manufacturing location/plant, or distribution

center

Warehouse or specific door within a dock within a

warehouse

Ship-to and deliver-to location

Aisle/shelf/bin in a storeroom

Department/Cost Center

A storage or distribution cabinet (e.g., Pyxis or

Omnicell unit)

It is a required component of the Global Data Synchronization Network™ (GDSN™) and is used in

conjunction with Global Trade Item Numbers (GTINs) on purchase orders, delivery and payment

documents, and other transactions. GLNs are registered with GS1 in the GLN Registry for Healthcare®

Its basic components are:

GS1 Company Prefix* Location reference Check Digit

N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13

*NOTE: The Prefix is variable-length. Apply for a GS1 company prefix at

https://www.gs1us.org/application_for_barcodes_authorized_by_gs1_us#Contact Information

Defined at appropriate levels of granularity

https://www.gs1us.org/application_for_barcodes_authorized_by_gs1_us


[ Why Use the GLN?

Provides unambiguous location and entity identification on supply chain

transactions between trading partners Ordering products and services

Corresponding with suppliers and customers

Processing supply-related order responses (e.g., acknowledgements and ASNs) and

invoices

Claiming manufacturer rebates

For any other standard business transactions with manufacturers, distributors, group

purchasing organizations, exchanges, or any other stakeholder

Used for the GLN Registry for rostering/membership maintenance (see the GLN

Registry for Healthcare® slide), as well as key to Global Data Synchronization

Network (GDSN)

Used in conjunction with Global Trade Item Numbers (GTINs) to create product

and service content for data pools within the GDSN.


[ Mayo Clinic GLN Hierarchy (used for POs)


[

12

GLN Best Practices

GLN hierarchies are defined and maintained by location owners

GLNs are defined at the proper level of granularity and

registered in the GS1 GLN Registry for Healthcare®.

GLNs are used in business transactions and processes among

trading partners (providers, GPOs, exchanges, distributors,

retailers, manufacturers [pharmaceuticals, medical devices,

equipment, and biotech], consumer products, 3PLs, insurance,

and others)


[ The Global Data Synchronization Network (GDSN) uses

the GLN as Key to Data Pool

GDSN-certified data pools serve as warehouses for product, service, and location information, 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 supply chain information , and

the Global Registry. In addition to storing information, GDSN-certified data pools also ensure the confidentiality of user information,

ensure that all of the information is properly defined and formatted, and manage the ongoing communication of information among supply

chain partners. Data pools can be run by a GS1 Member Organization or a solution provider.


[

© SAP

2008 /

Standardized Master Data: High-Level Example of

Trading Partner Scenario with Document Exchanges

Purchase Order (850)

Order Acknowledgement (855)

Price Catalog (832)

Remittance Advice/Invoice (810) Supplier/ Distributor/

GPO/Exchange

Hospital

Track-and-Trace

Despatch Advice / ASN (856)

Rebates and

Chargebacks

(844, 845, 849,

852, 867)

Manufacturer


[ Trading Partner Scenario with Document

Exchanges of GLNs and GTINs

CUSTOMER

GPO,

DISTRIBUTOR,

or

EXCHANGE

MANUFACTURER

GDSN

GDS Upload and

Download

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

SAP Healthcare providers (private and public), life sciences 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


[ SAP Support for GLNs

GLNs currently are used in the following four EDI

transactions*:

Purchase Order/PO Change (850/860)

Sold-to Party/Buyer

Vendor

Ship-to Party (at header if all lines‟ Ship-to =; line

level if differs by line)

Order Acknowledgement (855)

Sold-to Party

Bill-to/Invoice Recipient

Payer

Ship-to Party

Despatch Advice / Advance Shipment Notification --

ASN (856)

Ship-from Party – Vendor Shipping Point)

Ship-to Party – Customer Plant)

Sold-to Party -- Customer SP partner function)

Seller/Sales Org)

Invoice (810)

Invoicing Party

Sold-to Party

Bill-to Party/Invoice Recipient

Payer

Company

Sold-by/Sales Org

Minimum GLNs to Include in Each EDI Transaction

850 Purchase Order (Ship-to)

855 Order Acknowledgement (Ship-to)

856 Advance Ship Notice/Manifest (Ship-to)

810 Invoice (Ship-to, Bill-to)

832 Price Catalog (no minimum)

867 Product Transfer/Resales Report -- AKA

Trace Chargeback (no specified requirement)

844 Product Transfer Account Adjustment --

AKA Rebate (no specified requirement)

845 Price Authorization Adjustment/Status (no

specified requirement)

NOTE: See

http://help.sap.com/erp2005_ehp_06/helpdata/en/ff/516a6749d811

d182b80000e829fbfe/frameset.htm > EAN-UCC/GS1 Compliance

> Global Location Number


[ Maintain GLNs for Vendors and Customers via Partner

Functions

Vendors Vendor Entity (VN)

Order-from Party (OA)

Invoice Presenter (PI)

Sold-by Party (Sales Organization -- )

Ship-from Party (Shipping Point – 01)

Customers Manufacturers, distributors, GPOs, 3PLs, and other supply-side

customers require support for multiple Customer GLNs on IDocs - Organization Entity

- Sold-to Party (SP)

- Ship-to Party (SH)

- Deliver-to Party (DL)

- Bill-to Party/Invoice Recipient (BP)

- Payer (PY)

Optionally, maintain hierarchies (e.g., multiple DLs within SH)


[ Maintain Vendor GLNs

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

is similar to the use of three concatenated location 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.


[ Maintain Customer GLNs

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.


[ GLN Table for Business Objects (Core as of ECC 6.0

EHP2)

Besides the Vendor and Customer Masters, the GLN Table (Transaction Code EANGLN) is used to

maintain GLNs for these other business objects: Company (default if Plant GLN not maintained)

Plant (Ship-to and Bill-to)

Purchasing Organization (Buyer)

Sales Organization (Sold-by)

Shipping Point (Ship-from)


[ Mapping of GLNs to SAP IS-Healthcare Application

Locations (non-U.S. Customers)


[ IDoc Example: Outbound PO (850)

GLNs

Buyer (Purchasing Org) – header level

Vendor – header level

Ship-to and Bill-to (Plant) – header and line levels

See the Appendix for IDocs for Order Confirmation, ASN, and Invoice


[ GLNs on Outbound PO – ORDERS and ORDCHG

(850) IDoc at Header Level (All Line Ship-tos =)

24


[ GLNs on Outbound PO – ORDERS and ORDCHG

(850) GLNs at Header Level (All Line Ship-tos =)

AG: Buyer (Purch Org)

LF: Vendor

WE: Ship-to/Bill-to (Plant)


[ GLNs on Outbound PO (850) IDoc: Buyer (Purch Org)


[ GLNs on Outbound PO (850) IDoc: Vendor


[ GLNs on Outbound PO (850) IDoc: Ship-to/Bill-to

(Plant) – All Ship-to GLNs are the Same > Header Level



(Plant) – GTIN for Lines 1 and 2

29


[ GLNs on Outbound PO: ORDERS and ORDCHG (850)

IDoc at Line Level with Multiple Facilities (Plants)

NOTE: GLNs for Storage Locations (and other ship-to business objects, such as warehouses, cost centers, etc.) are supported by enhanced

functionality available via Guides/”cookbooks” in the SAP Market Place for Healthcare at http://service.sap.com/healthcare-guides

.

http://service.sap.com/healthcare-guides





(Plant) GLNs at Line Level (Lines 1 and 2)

31



(Plant) GLNs at Line Level (Lines 3 and 4)

IDocs for Order Acknowledgement, ASN, and

Invoice are in Appendix


[ 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

DataSources 0OIS_SSLT_TEXT Site Sublocation Type Description

0OIS_SSLTA_TEXT Site Sublocation Type Attribute Description

0OIS_BTTYPE_TEXT Business Transaction Description


[ SAP Support for GLNs in Business Intelligence

The following business content has been changed:

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)

Data Sources BWBCT_DS_0OIS_LOCG_ATTR Object Event Repository: Business Location

Attributes

BWBCT_DS_0OIS_PTA_1 Object Event Repository: PTA Data


[ Requested GLN Enhancements Additional GLN Business Objects with 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 Location.

Warehouse (LGNUM) – overrides Plant and Storage Location for Ship-to Location

MRP Area (BERID) – overrides Plant for Ship-to Location

Cost Center (KOSTL) -- for Buyer, Sold-to, and Ship-to Locations

GL Account (SAKNR) – lower-level GLN for Cost Center (e.g., multi-disciplinary research or

project teams)

Asset (ANLNR) – for Ship-to Locations

Project/WBS Element (POSID) – for Ship-to Location

Internal Order (AUFNR) – for Ship-to Location

Purchasing Group (EKGRP) – overrides Purchasing Org for Buyer and Sold-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).

NOTE: All GLN enhancements covered here are supported by enhanced functionality available via Guides/”cookbooks” in the

SAP Market Place for Healthcare at http://service.sap.com/healthcare-guides.





[ Requested GLN Enhancements: Additional Business Objects (Requires Enhanced GLN Table)

New Business Objects ANLNR: Asset (with Co) LGORT: Storage Location (with Plant)

AUFNR: Internal Order (with Co) POSID: WBS Element (with Plant)

BERID: MRP Area (with Plant) SAKNR: GL Account (with Cost Center)

EKGRP: Purchasing Group SPART: Sales Division (with Sales Org & Channel)

KOSTL: Cost Center (with Co) VTWEG: Distribution Channel (with Sales Org)

LGNUM: Warehouse (with Plant)

Core GLN Table Enhanced GLN Table


[ New GLN Table Program: Create GLN

37

Create GLN (ZGLN01)

Create GLN (ZGLN01)


[ New GLN Table Program: Create GLN

38

Create GLN (ZGLN01)

Create GLN (ZGLN01)


[ New GLN Table Program: Change GLN

39

Change GLN (ZGLN02)

Change GLN (ZGLN02)


[ GLN Table with New/Changed Storage Location Entry

40

GLN Table with New/Changed Entry


[ Requested GLN Enhancements: GLN Determination Logic in IDocs

2. Add new GLN logic for IDocs that utilizes all business objects and determines

and populates appropriate GLNs ORDERS, ORDCHG / ORDERS05 and PORDCR01, 02, 05 (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)*

NOTE: GLNs also are captured on the Sales Order at the header and line levels (comment fields).

GLNs on rebate and chargeback EDI transactions are supported in the SAP Paybacks and Chargebacks by Vistex

solution (849 and 852 transactions are beyond the GS1 recommended requirements).

3. GLN Search Help for Vendors and Customers

4. Add GLNs to core transaction screens (not part of GLN Enhancement

Project; must be done as custom work)

5. Add GLNs to sub-item level on documents (not part of GLN Enhancement Project,

since no sub-item segment exists on IDoc


[ GLNs on Outbound PO: ORDERS and ORDCHG (850)

IDoc at Line Level w/Multiple Plants & Storage Locations


[ GLNs on Outbound PO (850) IDoc: Ship-to (Storage

Location) GLNs at Line Level (Lines 1 and 2)

43


[ GLNs on Outbound PO (850) IDoc: Ship-to (Storage

Location) GLNs at Line Level (Lines 3 and 4)


[ Vendor Search Help by GLN: Transactions

45


[ Customer Search Help by GLN: Master Data

46


[ Customer Search Help by GLN: Master Data

47


[ GLN Enhancement Guides / ”Cookbooks”

Five Guides, which provide you 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) – available Monday, December 6

GLN Vendor and Customer Search Helps

and have been posted on the SAP Service Market Place for Healthcare at


48





[

© SAP

2008 /

Global Trade Item Number (GTIN)


[ What is the Global Trade Item Number® (GTIN®)?

An “umbrella” term that describes the entire family of globally-unique GS1 identification numbers that

is used to identify products and services that are sold, delivered, and invoiced. GTINs are assigned by

the product or service owner, and identify products as they move through the global supply chain from

the manufacturer or service provider to the hospital, retail pharmacy or med/surg store, repackager,

or ultimate end-user/patient/customer. GTINs may have serial or lot numbers appended to them.

If a product is modified in any manner along the supply chain, the party performing the modification

assigns its own GTIN and GLN (which can be maintained for traceability in an Object Event Repository)

The GTIN is a required component of the Global Data Synchronization Network™ (GDSN™) and

used in conjunction with Global Location Numbers (GLNs) on quotaations, 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.

Once the GTIN is assigned, all trading partners and internal users can use and reference the GTIN.

GTINs can be encoded into various types of GS1 bar codes and Electronic Product Codes™ (EPC)

which are programmed into Radio Frequency Identification (RFID) tags.

14-Digit Structure

• One digit represents the packaging level/unit of measure (1-9)

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

• Check Digit


[ How GTINs are Assigned: Parent/Child Relationship

51


[ Why GTINS are Needed

Thousands of numbers are maintained in both suppliers‟ and their customers‟

purchasing, sales systems, and inventory 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-ordered product

and service numbers are correct

Solution: Whenever an order is placed, each order line contains a GTIN, a

globally-unique, globally-applicable number that is “owned” by the supplier

(which is different than Manufacturer and Supplier Part Numbers, and identifies

not only the material or service, but also the unit of measure).


[ 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™

SAP GS1 compliance, including GTIN functionality, can be accessed at

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


[ What are GTIN Uses?

Besides serving as unique identifier for products and services, GTINs are used with Global

Location Numbers (GLNs) to create product and service content for data pools within the

GDSN. It is this consistency and timeliness of data that is critical to the smooth

functioning of the healthcare supply chain and are the GS1 standards‟ raison d‟etre.


[ 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 UDI

Federal Device Administration 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.

Like GTINs, UDIs enable control by serial, lot

number, expiration, and manufacturing date.

First step for developing UDI is developing UDI

code, according to ISO 15459 (GS1, HIBCC) and

concatenating Device and Product Identifiers.

FDA‟s UDI database contents can be based on data

from GS1‟s GDSN, which uses the GTIN.

GS1 recommends that all medical devices have a UDI

assigned, using the Healthcare GS1 GTIN Allocation

Rules.


[ Relationship between GTIN and 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.

http://www.fda.gov/


[ GTIN Flow

Receive:

Inquiry

Create:

Quotation

Receive:

Sales Order

Create:

Order Response

Create:

Dispatch Advice

Create:

Invoice

Retailer

Create:

RFQ

Receive:

Quotation

Create:

Purchase Order

Receive:

Order Response

Receive:

Dispatch Advice

Receive:

Invoice

Supplier

Receive:

Inquiry

Create:

Quotation

Receive:

Sales Order

Create:

Order Response

Create:

Dispatch Advice/ASN

Create:

Invoice

Create:

RFQ

Receive:

Quotation

Create:

Purchase Order

Receive:

Order Response

Receive:

Dispatch Advice

Receive:

Invoice

Vendor GTIN

Vendor GTIN

GS1

Compliance


[ How SAP Supports GTINs

Standard GTINs (i.e., not GTIN batches or serialized GTINs) in ECC

Procure-to-Pay Process Flow

Vendor Quotation

Purchase Order

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 GTIN by a material number

Executed during the sales order inbound process. It checks whether GTIN mapping is active. If

yes, then the system determines the material number that matches the specified GTIN.

Choose the fields and specify their combinations Specify the sequence of the various key combinations – e.g.:

GTIN – the sole mandatory field

GTIN variant type

Customer

Country

Distribution Channel

Sales Organization

Division

Using free selection fields enable you to maintain generic condition records

Determination stops

As soon as determination for one condition type (in the procedure) is successful

As soon as one access (in access sequence) is successful

GTIN Mapping EAN1 – Create GTIN Mapping

EAN2 – Change GTIN Mapping

EAN3 – Display GTIN Mapping

EAN4 – Create GTIN Mapping with Template

NOTE: See http://help.sap.com/erp2005_ehp_06/helpdata/en/ff/516a6749d811d182b80000e829fbfe/frameset.htm > EAN-UCC/GS1

Compliance > GTIN Mapping


[ Consistency Check for GTIN Attributes

Ensures that the Global Trade Item Number (GTIN) attributes match when a

GTIN (or GTIN Variant) is assigned to several materials: 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

Ensures that the attributes for this GTIN are consistent


Compliance > GTIN Consistency Check and GTIN Consistency Report


[ GTIN Processes with Specific Customer Data

Purpose

The GS1 GTIN compliance component covers three elementary business 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.


Compliance > GTIN Processes with Specific Customer Data


[ Vendor-Specific GTIN Maintenance (EANVENDOR)

Automatically, maintains

Material Master (Additional

Data View/Units of

Measure/EAN/UCC, using

MM01 or MM02) do not

maintain the Material

Master; use this transaction.

Populates GTIN on Vendor

Quotation, PO, Goods

Receipt, Sales Order, and

Invoice (see following

slides). Also, transferred

into Auto-ID for subse-

quent encoding in SGTINs.

You can maintain only one

GTIN for a unit of measure

of a material for a vendor


[ Vendor Quotation GTIN


[ Purchase Order GTIN for PAC Unit of Measure


[ Ship-to GLN and GTIN Display on Printed PO or is

Mapped into the EDI Output


[ GTIN on PO/FAX Form


[ GTIN on Purchase Order IDoc (850)

68


[ Sales Order GTIN


[ Outbound ASN GTIN


[ Goods Receipt GTIN


[ Outbound and Inbound Invoice GTINs


[

© SAP

2008 /

SAP Support for

GS1-128 Bar Code

and Label Creation


[ GS1-128 Barcoding: GS1 Identification 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 (21)123


[ GS1 Data Carriers for Healthcare

GS1-128 &

GS1 DataBar

Preferred options if:

Package allows

GS1 DataMatrix

Preferred option if:

Large amount of data on

small space

Variable information at

high production rates

Direct part marking

EPC/RFID

Additional option

Not line-of-sight

Large amount of

data

Image bar code scanners are needed!


[ 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

http://pe.usps.com/text/dmm300/708.htm

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

2008 /

SAP Support for Global Data

Synchronization (GDS)

Uploading and Downloading GDSN

Data Pool Data to/from SAP


[ The Global Data Synchronization Network (GDSN)

uses GLN and GTIN as Keys to Data Pools


[

High-volume, granularity, and change

frequency

Inconsistent and / or inaccurate

product and service information

Management and error-handling

increases costs and complexity

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

Retailer mandates driving manufacturer

process changes

Maintaining consistent data across a

global supply network

Data synch needs extend to other

topics: sustainability, traceability

Maintaining Product and Service Data Integrity within a

Complex Business Network is Challenging

Product

Proliferation

Partner

Collaboration

Emerging Global

Standards

Complex global demand and supply networks require timely, accurate and consistent product coding


[

Objective:

Ensure compliance with GS1 rules and regulations and create a data foundation for GDS

Best practice solution:

Establish a framework for adoption and use of the GS1 product and price information for

collaboration with retailers

Extract and Enrich Product and Price Info Objectives, issues, capabilities and benefits

■ Establishing and maintaining a global

framework for consistent data

management

■ Enforcing global data standards

across a dynamic global business

network

■ Enabling compliant standards for data

exchange and business partner

collaboration

■ Establish and ensure a global data

quality framework leveraging the GS1

standard

■ Enable up-to-date connections to

Global Data Synchronization Network

(GDSN) data pool

■ Define procedures for transferring

timely product iand price nformation

into the GS1 format

■ Consistent, standard data available

globally eliminates errors and reduces

costs

■ Standard, easy to communicate

pinformation enables effective data

exchange

■ Compliant standards Improve data

quality foundation and simplify

communication channels & formats

Issues Key business capabilities Benefits


[ Ensure Data Quality Objectives, issues, capabilities and benefits

■ Inconsistent, non-compliant

processes for local exceptions and

error reconciliation

■ Lack of standards for product and

service data updates, attributes and

properties increases inconsistencies

& errors

■ Globally-enforced, locally-managed data

validation and exception rules improve

data quality & compliance

■ Roles, rights and permissions enable

standards and accountability for updates

and exception management

■ Improve data quality foundation locally

and globally while enabling and ensuring

compliance

■ Eliminate errors, streamline transaction

processing, & measure KPIs for errors

& exceptions

Issues Key Business Capabilities Benefits

Objective:

Compliance with internal and external data standards


Use predefined GS1 standard validations and deploy them flexibly in a seamless end-to-end

process


[ Exchange Trade Item and Price Information Objectives, issues, capabilities and benefits

■ Inability to spot data errors and

process breaks creates downstream

exceptions, increasing costs

■ Manual, inefficient labor-intensive

processes for exception management

and validation

■ Inability to measure data quality KPIs

and targets = inability to assess costs

of errors

■ Enable process automation and

workflows to flag exceptions and

route for resolution

■ Validate item information against the

GS1 standard to ensure ongoing,

timely data accuracy

■ Manage and monitor errors and

exceptions versus other KPIs across

the business network

■ Fast and accurate data error

resolution eliminates downstream

transaction issues, lowers costs

■ Reduce efforts and streamline

processes associated with item

maintenance and publication

■ Measure the business impact of data

accuracy, data quality and fast

exception management

Issues Key Business Capabilities Benefits

Objective:

Efficiently manage the publication process and its exceptions


Leverage an end-to-end data synchronization process automated by trade partner profiles

and guided workflows


[ What‟s Needed?

87

• Provider GDS • IS-Retail

• SAP NetWeaver Process Integration (PI)

• For encryption, an AS2 adaptor that runs in the PI adapter

framework

• Consulting services (e.g., to add attributes)

• Manufacturer GDS • Source system (either SAP ERP or NW MDM Scenario)

• SAP NetWeaver Process Integration (PI)

• GDS component (covered by GDS license)

• For encryption, an AS2 adaptor that runs in the PI adapter

framework

• NW WAS (covered by GDS license)

• NW MDM Server (covered by GDS license


[

© SAP

2008 /

Auto-ID Enterprise: SAP Support for

Traceability / Track-and-Trace

Serialization in the Healthcare Supply Chain


[ 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.

The path through the supply chain, or “trace,” is the data history that accumulates as an asset

moves through the supply chain. This data history includes both physical observations of the

asset (visibility data, as defined in the previous section) and business transactions that pertain

to that asset.

At each step in the supply chain 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 chain.

A trace is comprised of data that is created by multiple parties in a supply chain.

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 and

Critical Tracking Events


[

Patient Safety and Effectiveness

Increasing Operating Costs

Downward Margin Pressures

Reduced Operating Efficiency

Gov’t regulations in US & Europe

Need for Serialization: Key Issues

Standards

Business issues

Cost Pressure (esp. generics)

Supply Chain and Reverse Logistics opportunity Complex, multi-step Supply Chain

Safe & Secure Supply Chain

Counterfeits

Diversions


[ Industry Pain Points for Traceability

Patient Safety and Effectiveness Increasing Operating Costs Downward Margin Pressures Reduced Operating Efficiency

Increasing Government Regulations

Pedigree mandates from FDA and US states (FL, CA, IN)

Increasing drug traceability requirements in Brazil, Germany, Turkey, Italy, Greece, Belgium, Ireland, China, Spain, and others

Intense Competition and Reducing Margins

Continuous pressure to improve supply chain efficiency and effectiveness

Increasing pressure from poor chargeback and rebate accuracy

Constant pressure to improve Reverse Logistics

Increasing incidents of product recalls

Inventories of expired, and overstocked products

Increasing pressure to reduce logistical errors and

improve returns processing

Safe and Secure Supply Chain

Growing concerns of patient safety

Increasing number of counterfeits and diversions

Increasing theft, security requirements for controlled substances

Brand Protection


[

92

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)

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 and conduct business using GLNs and GTINs

Implement an EPCIS-certified Object Event Repository to capture CTEs and

KDEs


[

SAP Object Event Repository


[

© SAP

2008 /

Serialization in Healthcare

Patients

Patient records

Counterfeit protection for supplies,

drugs, implants, devices, instruments, and

other medical assets

Blood products

Lab and pathology sample tracking

Medical waste


[

95

Supply Network Traceability with GS1 EPCIS and SAP

Object Event Repository (OER)

Manufacturer Increases brand value and sales volume

Customs

Supported in territory duties

Automates processes and authenticates goods Packaging hierarchy changes

Patient

Safety is enhanced by reduced risk of medication errors and counterfeits

After - Sales Services

Capability to deliver Service

* PTA Product Tracking & Authentication

** OER Object Event Repository

Track supplies, medications (even in unit doses), devices, and equipment

Track patients, assets, blood samples … Patient / drug matching Facilitated recall and returns

Hospital

Distributor

Wholesaler

Logistics Service Provider


[

Handling and

Fulfillment

SAP Differentiators

SAP Solution

■ Integration with diverse tracking equipment (bar

code scanners, RFID readers)

■ Reporting related to GS1 Healthcare Traceability

Standard

■ Legal compliance with national, regional, and

global regulation

■ Smooth Integration with SAP Patient

Management (IS-H) or non-SAP systems

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

Secure Supply Network Traceability with GS1

EPCIS and SAP Object Event Repository


[

© SAP 2008 / Page 97

Pre-Configured, Value-added Business Processes in

Auto-ID Enterprise

Outbound Process Inbound Process RTI Process

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

Scan and validate goods receipts based

on ASN data (Advanced Shipment

Notifice)

Automatically process goods receipts in

the back-end Enterprise Resource

Planning (ERP) application

Automatically generate proof-of-delivery

documentation based on predefined

conditions

Closed-loop tracking of returnable

transport items/containers (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.


[

© SAP 2008 / Page 98

Pre-Configured, Value-added Business Processes in Auto

ID Enterprise

Secure Track-and-Trace Kanban Process Customer Returns Delivery

Processes to track and trace in the

supply chain, using serialized data

Authenticate items throughout the

supply chain

Track, based on business context

(Purchase Order, Sales Order,

Delivery, etc.)

Ability to track additional information

Automatic Kanban status change

Creation of a replenishment element

(e.g., a Purchase Order)

Automatic goods receipt posting

Creation of the material document

Process Customer Returns Delivery in

Auto-ID Infrastructure

Scan and validate receipts with respect

to return delivery expectations

Automatically process goods receipt in

the back-end ERP system

Verify return requirements at the data

capture source


[

© SAP 2008 / Page 99

Pre-Configured, Value-added Business Processes in

Auto-ID Enterprise

Pedigree Tracking DoD IUID Support Production Order Confirmation

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, and

case-item, pallet-case-item

association)

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 (or any other

document) is brought into Auto-ID

Infrastructure, using Generic

Document Interface

All the order information is available in

AII

Existing rule is modified to leverage

SAP standard functionality and add

custom logic for confirmation


[ SAP Object Event Repository as Extended GS1 Object Event Repository

AUTO-ID Repository

Event Management Analytics

Security Services

EPCIS INTERFACE

EPCIS CAPTURE INTERFACE

OER SAP OER 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 to

growing number of enterprise consuming

applications

support various data streams [EPC,

Transaction, POS, …] to drive business value

Suppliers

Subcontractors

Retailers 3 PLs

Non-

SAP

system

Production Warehousing Distribution Sale

Production on track

Production completed

Shipment received

Unpack

Pack

Send

ASN Ship

Receive

Authenticat

e

Ship Authenticate

Dispense

Need a way to track a product as

it moves through the supply chain

Product

serialization

Need a way to store and manage

millions of transactions acquired

by tracking product movement

Data capture

& repository

Need a standards-based

mechanism for sharing data for

multiple use cases

Industry

Standard

Need a way to share data with

trading partners to identify

business value

Secure data

exchange

Receive


[ SAP Object Event Repository Sense & Respond with SAP Event Management


AUTO-ID Repository

Event Management Analytics

Security Services

EPCIS INTERFACE

EPCIS CAPTURE INTERFACE

OER

monitor adjust analyze notify

Empowered by the extensive tracking & tracing

functionalities of built-in SAP Event Management,

SAP OER is the global instance providing

visibility along your entire supply chain.

Extract relevant process information from

globally distributed system into one central

repository

Process monitoring, automated exception

resolution mechanisms, proactive alerting,

extensive reporting capabilities in one single

solution

SAP Event Management offers full

flexibility to model end-to-end tracking

scenarios that deliver visibility for all your

supply chain activities

Visibility on process level (Product

Tracking & Authentication, Order

fulfillment, Procurement,

Transportation, Production)

Visibility on asset level (track the

lifecycle of inventories, capacities,

resources)

Visibility on agreed performance

goals (measure and control

performance of SCM community

participants)

Suppliers

Subcontractors

Retailers 3 PLs

Non-SAP

system


[

© SAP 2007 / Page 102

Actual events

Expected events process milestones

SAP GS1 OER Extension: SAP Event Management

Unreported event

event 4

Regular event

event 1

event 1

Unexpected event

event 3

Early/Late

event

event 2

event 2


[

© SAP 2007 / Page 103 © SAP 2008 / Page 103

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.

Manufacturer (1/6)

Manufacturer

6x 12x


[

© SAP 2007 / Page 104 © SAP 2008 / Page 104

Customs (2/6)

Customs

Customs officer scans the barcode at

container, pallet, or item level •Retrieves manufacturer information and

item lifecycle from global OER

•Proves validity and authenticity of the item,

along with the AES reference, to allow a

comparison with the Atlas customs system


[

© SAP 2007 / Page 105 © SAP 2008 / Page 105

Wholesalers use mobile or stationary

readers (mostly RFID-based) to read

containers and pallets and retrieve

relevant manufacturer information.

Optimizes own logistics processes and

posts further logistics milestones into

global repository.

Wholesaler (3/6)

Wholesale

Distributor


[

© SAP 2007 / Page 106 © SAP 2008 / Page 106

The hospital uses this function for

tracking of total or partial trading unit

quantities (e.g., single pills or liquid

mixtures) from central pharmacy to the

patient. Other uses include •Patient/med matching

•Recall by batch or serial number,

•Authentication spot-checks

•Visual tracking of serialized objects

(documents, equipment, patients, personnel,

etc.)

•Multi-dimensional reporting

Hospital (4/6)

Hospital


[

© SAP 2007 / Page 107 © SAP 2008 / Page 107

Increase patient safety, reduce human error

danger by automatic patient/drug matching

when dispensing.

Quickly identify patients who received

medications, devices, etc. from particular

package (single serial number) or batch.

Nurse can scan the serial number at the item

level with commercially-available cell phone

camera and verify the authenticity of

medications, devices, etc.

Hospital - Caregiver (5/6)

Clinician


[

© SAP 2007 / Page 108 © SAP 2008 / Page 108

Patients can read the 2D barcode at product

level with commercially-available cell phone

cameras and verify the authenticity of goods.

Patient (6/6)

Patient

SAP Verification Portal

Manufacturer: Bayer

Product: Voltaren

GTIN: 00370001122334

Lot: A255ZT98

Expiry Date: 20151017

EPC:01.000A89.00016F.000169DC0

Status: Known


[

Globally-unique identifiers,

encoded in 2D barcode on the

packaging. Four smaller units,

serial numbers 2020100 to

2020103 are packed into

larger unit that has serial

number 2020.

Attributes related to identifier optionally are

encoded into barcode on the packaging and not

used for identification. Created by manufacturer,

they remain constant throughout the lifecycle.

GTIN also is maintained in EAN/UCC field in the

standard ERP and IS-H Material Master

1a. Manufacturer: GS1 EPCIS Events: EPC


[ 1b. Manufacturer – Commissioned Serialized Items

Transferred to SAP OER

Globally-unique identifiers,

encoded in 2D barcode on the

packaging. Four smaller units,

serial numbers 2020100 to

2020103 are packed into

larger unit that has serial

number 2020.

Attributes related to identifier optionally are

encoded into barcode on the packaging and not

used for identification. Created by manufacturer,

they remain constant throughout the lifecycle.

GTIN also is maintained in EAN/UCC field in the

standard ERP and IS-H Material Master


[ 1c. Manufacturer – Commissioning-to-Shipping

Single Item Lifecycle in SAP OER


[ 1d. Manufacturer – Commissioning-to-Shipping

Package Lifecycle in SAP OER


[

© SAP

2008 /

2. Medication Received at Central Pharmacy and

Delivered to Nursing Unit


[

© SAP

2008 /

3a. Box Unpacked from Case 2020 at Nursing Unit


[

© SAP

2008 /

3b. Dispensing Units 2020102 and 2020103 Unpacked

from Box 2020


[

© SAP

2008 /

3c. Dispensing Unit 2020100 Given to Patient


[

© SAP

2008 /

3. Three Pills Taken from Dispense Unit 2020101 and

Given to Three Patients

Remaining quantity of the pack 2020101 is the

original total quantity reduced by cumulated

disaggregated quantity:

Original total qty: 20 x 5 mg = 100 mg

Cumulated disaggregated qty: 3 x 5 mg = 15 mg

Remaining qty: 100 mg – 15 mg = 85 mg


[

GS1 at Johns Hopkins


[

119

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

120

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.


[

121

SAP History

Live since January 1, 2007. Upgrade went live May 18, 2010.

SAP R/3 4.7 SAP ERP 6.0, EHP 4

SAP SRM 4.0 SAP SRM 7.0

SAP BW 3.5 SAP NetWeaver® BW 7.0, EHP 1

SAP EP 6.0 SAP NetWeaver Portal 7.0, EHP 1

SAP XI 3.0 SAP NetWeaver PI 7.1

SAP SM 3.0 SAP Solution Manager 7.0, EHP 1

SAP NetWeaver MDM (new for

SAP SRM)

No GRC tool (installed 5.2 in 2009) GRC Access Control 5.3


[

122

SAP History

Added or planned since upgrade:

BusinessObjects 4.0 (first project will go live July 2012)

ECC EHP 5 (planned for late summer 2012)

SRM EHP 1 (planned for late summer 2012)

Netweaver EHP 3 (evaluating)


[

123

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


[ Supply Chain Management at Johns Hopkins

124

= utilized at Johns

Hopkins

= under review or

being implemented

at Johns Hopkins

Legend SCM Supply Chain

Management

SUS Supplier Self-Service

SAP Workflow

Shopping cart approval (SRM)

Non-PO invoice approval (ECC)

PO discrepancies (ECC)

MM Materials

Management

Bidding

IM Inventory

Management

WM Warehouse

Management

Shopping Cart

Contract Management

Purchasing

Master Data

Biller Direct

MDM-Catalogs

SRM Supplier Relationship Management

SAP History (cont.)


[ Production Database Size

Size in terabytes

125

0

0.5

1

1.5

2

2.5

3

3.5

4

ECC SRM BW

FirstYearCurrent


[

126

GS1 at Johns Hopkins – GLNs

*Reminder: Johns Hopkins utilizes SRM for Procurement

All delivery addresses are mapped to a specific GLN in a custom

table (table also includes “customer number”):


[

127

GS1 at Johns Hopkins – GLN‟s

*Reminder: Johns Hopkins utilizes SRM for Procurement

SRM users create shopping carts/requisitions using a 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.


[

128

GS1 at Johns Hopkins – GTIN‟s

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.


[

129

GS1 at Johns Hopkins – GTIN‟s

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!


[

130

GS1 at Johns Hopkins – GLN‟s

Cook Medical has announced alignment with GS1!


[

131

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

http://bit.ly/hYVe1y

http://bit.ly/ebjqk6


[

133

[

] Thank you for participating.

SESSION CODE: 3102

Please remember to complete your evaluation following this session.

For ongoing education on this area of focus, visit the Year-Round

Community page at www.asug.com/yrc


[

Appendix

Additional Details


[

135

Healthcare Value Chain

SAP Solutions Supporting GS1 Healthcare Mission

Manufacturers Healthcare

Providers Wholesalers &

Distributors

Hospitals &

Pharmacy

Retailers

Government Regulations

GS1 Mission SAP Solution Offerings

Reduce medication errors Basis: SAP Auto-ID Enterprise Solution

Enable global traceability &

authentication

SAP Auto-ID Enterprise – secure Tracking & Tracing solution ,including Product Tracking &

Authentication

Documentation of serialized medical products within SAP Patient Management (legal requirement

France)

For advanced authentication, we are looking at partnering with provider in collaboration with major

healthcare manufacturers

Improve supply chain

efficiency

SAP Auto-ID Enterprise – Secure Track-and-Trace solution

SAP SCM product portfolio integrated within SAP Business Suite

GS1 Standards adoption for

Automatic Identification &

Traceability

SAP Auto-ID Enterprise

The Object Event Repository (part of SAP Auto-ID Enterprise) is certified by EPCglobal to be

EPCIS -compliant


[ GLN Uses

GLNs in supply chain operations: The healthcare supply chain can be highly

complex, particularly with products being able to follow multiple routes between the

manufacturer and a hospital. GLNs can be used in such cases to uniquely identify

individual delivery points and the final destination of a product. This information can be

provided in electronic commerce messages as well as appearing on the shipping label in a

data carrier.

GLNs in eCommerce transactions: 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, ship to and bill to locations. GLNs are increasingly important in healthcare

transactions to ensure correct pricing is applied to specific customers and that ordering

and delivery processes can become increasingly efficient, requiring minimal intervention

from clinical staff.

GLNs in data synchronization: When suppliers and their trading partners exchange

item and/or price information about the products they trade, this process is called Data

Synchronization. The information exchanged for data synchronization is non-

transactional and includes the unique product identifier (GTIN) and

additional information such as product descriptions, regulatory

information, sizes and weights. This will ensure resulting purchasing

transactions are based on accurate and complete information.


[ GLN Registry for Healthcare®

What is the GLN Registry for Healthcare? Registry of healthcare-related partners and physical and entity locations in the United

States. Each location has been assigned a GLN.

Subscription-based service that provides a comprehensive list of healthcare providers,

suppliers, manufacturers, distributors, GPOs, retailers, clinics, retail and mail-order

pharmacies, etc. in the United States, with their corresponding GLNs (also name,

address, class of trade, and organizational hierarchy)

Electronic catalog of standardized party/location information about healthcare entities

in the United States > “single source of truth” for location information, enabling

subscribers to access up-to-date, reliable location information for industry partners to

improve the accuracy of their supply chain activities.

Why use the GLN Registry for Healthcare? Ensures uniqueness

A registered member can go to the Registry to look-up and download any subscriber‟s

location information. Then, by simply cutting and pasting, you can easily update any

customer or supplier‟s information without having to re-key it.

Alternatively, your IS Department could write a simple interface program to keep it

completely synchronized with the industry database.


[ 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 the provider‟s MMIS.

Suppliers

Need an assigned GS1 Company Prefix to be able to create their GLNs, and apply to GS1 for one.

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.

See the Hopkins, UKY, and Mayo Clinic GLN structures in the Appendix.

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 the next 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, 3PLs, 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


[ GLNs on Order Confirmation IDoc (855)

AG: Sold-to Party (Customer Sold-

to)

RE: Customer (Recipient/Bill-to)

RG: Customer (Payer)

WE: Customer (Ship-to)


[ GLN on Order Confirmation IDoc (855) – Sold-to Party

(Customer)


[ GLN on Order Confirmation IDoc (855) – Bill-

to/Invoice Recipient (Customer)


[ GLN on Order Confirmation IDoc (855) – Payer

(Customer)


[ GLN on Order Confirmation IDoc (855) – Ship-to

(Customer)


[ GLNs on Outbound ASN (856) IDoc


[ GLN on Outbound ASN (856) IDoc – Ship-to (Customer)


[ GLN on Outbound ASN (856) IDoc – Sold-to (Customer)


[ GLNs on Outbound Invoice (810) IDoc


[ 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

(Customer)


[ Inaccurate Product Data Increases Costs, Lowers

Revenue and Decreases Customer Satisfaction Redundant, inconsistent, and fragmented data management increases costs and limits operational efficiencies

■ Distributed, disconnected global product

data management

■ Redundant data entries across the

business network

Inefficient Product Data Management

■ Unable to provide consistant, accurate

information to trading partners

■ Incorrect orders, shipments, and claims increase

costs, impact patient care and employee

satisfaction

Inaccurate Product & Price Information

■ Non-standard global product coding

policies and processes

■ Inability to enforce data management

standards locally

Lacking Global Standards


[ Accurate, Consistent Data Across the Business Network

Lowers Costs, Improves Results

Timely, Accurate Information Updates

Improve order processing, item

administration and new trading partner

on-boarding

Reduce data management efforts and

costs, ensure timely accurate data

Efficient Data Administration

Reduce item data issues in procurement processes

(e.g., UOM and pricing changes)

Improve process efficiency and transparency for

logistics, distribution and stock via consistent

product coding across the business network

Right product, med, or equipment for the right

patient, at the right time, …

Consistent, timely and accurate product data synchronized with trading partners create efficiencies across the

entire business network

■ Global product coding policies, processes

and guidelines

■ Enforceable global standards ensure local

compliance

Globally-Accepted Standards


[

CIO

Aligning stakeholders to achieve Global Data

Synchronization

Effective Global Data Synchronization requires alignment between several stakeholders with differing responsibilities

How do I identify and resolve

errors and exceptions quickly

and efficiently?

Exceptions as a % of total

item updates

Error rate time to

resolution

Data Quality Mgmt.

How do I reduce the cost of

bad product data with trading

partners?

Compliance to GS1 rules

Validation rules to enable

data quality framework

Ensure Data Quality

How do I establish global

synchronization standards &

ensure compliance?

Enterprise GS1

subscription guidelines

Compliance with coding

standards

Extract and Enrich

Product and Price

Information

Exchange Trade Item and

Price Information

GDS Coordinator Product Data Mgmt.

How do I align our internal data

management processes with

global data standards?

Percentage of item data

compliance with GS1

Total cost of data synch

errors and exceptions

Enterprise Data

Management


[ Global Data Synchronization supports efficient

collaborative processes Global Data Synchronization delivers the foundation for effective Business Network Collaboration

CIO

IT

Trade Partner

Sales

Product Management

Research & Development

Extract

Product

Information

Accept Reject Review

Publish GS1

Product & Price

Information

Establish

Connection

GDSN

Enrich

Product Data

Data Quality Mgmt.

Ensure Data Quality

Extract and Enrich

Product and Price

Information

Product Data Mgmt.

Define

Validation

Rules

Exchange Trade Item and

Price Information

Define

GDSN

Framework

Manage

Validations/

Exceptions

Create

New

Product

Informatio

n

Data

Validation

Maintain &

Update Item

Data

GDS Coordinator

Enterprise Data

Management

Maintain &

Update Price

Data

Extract Price

Information

Maintain

Price

Doc.

User & Trade

Partner

Profiling


[ Extract and Enrich Product and Price Info SAP Solution

■ Ensure ongoing deployment and use of the latest version

of the GS1 standard

■ Define attribute framework and processes for mapping of

product and price data to GS1 compliant formats

■ Enrich and maintain attribute values for trade items

■ Extract pricing from SAP ERP backend (requires

customer project work)

SAP differentiators

SAP solution

Up-to date: Regular upgrades ensure GS1 compliance

Usability: Simple trading partner and target market maintenance

Flexibility: Quickly adapt to changing requirements of the GS1 standard and trading partners

Furture Proof: In line with new GS1 standard for price synchronization

Establish

Connection

GDSN

Enrich

Product Data

Define

GDSN

Framework

Create New

Product

Information

Maintain &

Update Item

Data

Maintain &

Update Price

Data

Extract Price

Information

Maintain

Price Doc.

Extract

Product

Information


[

■ Predefined GS1

attributes and extensions

■ Create and maintain

additional attributes

■ Create and maintain

extensions

■ Set-up trading partner

specific attributes for

each trade item

Process overview

Extract and Enrich Product and Price Info Define GDSN Framework

Define GDSN Framework enables Consumer Products manufacturers to establish

GS1 compliant standards for product item data management.

■ Use graphical mapping

tool

■ Define complex

mappings in xslt or

ABAP

■ Set common default

values

■ Consolidate or branch

data

■ Quickly onboard new

target markets

■ Use role based business

partner model

■ Enable multiple info

providers per company

Gather Inputs Statistical Modeling Publish Forecast

2 1 3

Attribute

Framwork Mapping

Target Market and

Business Partners

Enrich Product

Data

Define GDSN

Framework

Extract Price

Information

Maintain Price

Doc.

Extract Product

Information


[ Extract and Enrich Product and Price Info Extract Product Information

Extract Product Information enables Consumer Products companies to extract

data from a source system to initiate the synchronization process and ensure

consistent, accurate data across the business network

■ Determine relevant

product information

■ Set import criteria

■ Align with mapping

■ Extract simple and

complex hierarchies

■ Manual or batch load

Process overview

■ Determine message type

■ Decide on message size

■ Set upload frequency

Initial Load Delta Load

2 1

Enrich Product

Data

Define GDSN

Framework

Extract Price

Information

Maintain Price

Doc.

Extract Product

Information


[ Extract and Enrich Product and Price Info Extract Price Information

Extract Price Information enables Consumer Products companies to extract data

from an SAP ERP system to initiate the synchronization process and ensure

consistent, accurate data across the business network

■ Use PRICAT extraction to get GDS relevant price

information from an SAP ERP system

■ All prices and the appropriate condition sets

■ sequence information needs to be added

Process overview

Initial Load Delta Load

2 1

Enrich Product

Data

Define GDSN

Framework

Extract Price

Information

Maintain Price

Doc.

Extract Product

Information


[ Extract and Enrich Product and Price Info Enrich Product Data

Enrich Product Data allows Consumer Products companies to store and maintain

synchronization specific attributes to ensure compliance with trade partner and

GS1 requirements

■ Align with mapping

■ Set default values in GDS

console

■ Set up workflows e.g. for

maintenance and approval

■ Determine access

authorization

■ Limit visibilty

Process overview

■ Store initial values

■ Store images

■ Create trade items for

multiple target markets

Establish data

foundation Maintain data

2 1

Enrich Product

Data

Define GDSN

Framework

Extract Price

Information

Maintain Price

Doc.

Extract Product

Information


[ Extract and Enrich Product and Price Info Maintain Price Document

Maintain Price Data allows Consumer Products companies to store and maintain

price relations with trade partners together with price components and price types

■ Align trade items to

conditions and partner

■ Select, deselect , add and

maintain conditions

■ Store price document

Process overview

Maintain Price

document

1

Enrich Product

Data

Define GDSN

Framework

Extract Price

Information

Maintain Price

Doc.

Extract Product

Information


[ Ensure Data Quality

Create and enforce data validation rules to ensure compliance to

internal and external data standards


[ Ensure Data Quality SAP Solution

Integration: Manage data quality integrated with core business processes

Quality: Establish rules for product item data validation at each process step

Consistency: Ensure consistent use of trade item information

■ Manage data quality within a framework to ensure local

compliance with global standards

■ Validate product data fixes and new product data updates

against GS1 rules

SAP differentiators

SAP solution

Data

Validation

Define

Validaition

Rules


[

■ GS1 rules delivered as

pre-defined content

■ Set-up of simple

company specific rules

directly in MDM

■ Complex rule

development in JAVA

Process overview

Ensure Data Quality Define Validation Rules

Define Validation Rules enables Consumer Products companies to set up of a data

quality framework to ensure compliance to GS1 and company internal quality

standards

■ Rules can be deployed

per role

■ For automated

processes

■ For use in workflows

Rule Set-up Rule Deployment

2 1

Data

Validation

Define

Validaition

Rules


[ Ensure Data Quality Data Validation

Data Validation ensures compliance to GS1 and internal data quality rules

■ Automatic validation of

items during data

extraction

■ Manual role based

validation

■ Forced validation prior to

registration or publication

Process overview

Use of Validation

Rules

1

Data

Validation

Define

Validaition

Rules

■ Restrict manipulating of

attribute values

■ Restrict operations

access

■ Limit visibility

■ Data approval steps

Data Access

Control


[ Exchange Trade Item and Price

Information

Manage the publication process


[ Exchange Trade Item and Price Information SAP Solution

Automation: Manage item synchronization via automated workflows and exception processes

Compliance: Exchange price using the GS1 standard

Measurement: Track and manage error and exception rates against other business KPIs

■ Leverage workflows and process automation to flag

errors and exceptions for routing and fast resolution

■ Control level of automation per trade partner

■ Manage effective, timely communication towards the data

pool and trading partners

SAP differentiators

SAP solution

Publish GS1

Product & Price

Information

Manage

Validations/

Exceptions

User & Trade

Partner

Profiling


[ Exchange Trade Item and Price Information Manage Validation Exceptions

Manage Validation Exceptions enables Consumer Products companies to run data

synchronization as automated processes with minimal manual interference

■ Approve and Accept

product publication and

registration requests

■ Fill in missing attributes

■ Mass deletion of

workflows

■ Worklfow identification

by item

Process overview

■ Trigger correction

processes

■ Handle modification

requests

■ Identify owner of

erroneous trade items

■ Process log files

■ Process Log (GTIN,

Validation, Mass Delete,

Co-Relation Manager in

Log)

Workflow

Handling

Automation

Exceptions Error Handling

2 1 3

Publish GS1

Product & Price

Information

Manage

Validations/

Exceptions

User & Trade

Partner

Profiling


[ Exchange Trade Item and Price Information User & Trade Partner Profiling

User & Trade Partner Profiling enables Consumer Products companies to automate

global data synchronization according to different trade partner criteria.

■ Switch on automatic

initial publication per

trade partner

■ Use predefined criteria

like brand, target markte

or info provider

■ Define own criteria for

publication

Process overview

■ Authorization for

publication operations

per TM, Brand, Info

Provider etc

■ Define Uis for

publication only

■ Approval and publication

workflows

Set Trade Partner

Profiles Set User Roles

2 1

Publish GS1

Product & Price

Information

Manage

Validations/

Exceptions

User & Trade

Partner

Profiling


[ Exchange Trade Item and Price Information Publish GS1 Product and Price Information

Publish GS1 Product and Price Information allows Consumer Products companies

to manage complex publication and registration processes for trade items and

prices

■ Automatic registration

after data extraction

■ Manual and workflow

based registration

Process overview

■ Automatic initial publication

by predefined criteria

■ Automatic publication of

modified/corrected items

■ Manual/workflow guided

publications

■ Trade partner pre- selection

in manual publication

■ P2P catalogue publication

Registration Publication

2 1

Publish GS1

Product & Price

Information

Manage

Validations/

Exceptions

User & Trade

Partner

Profiling


[

© SAP 2008 / Page 175

SAP Solutions for Auto-ID and Item Serialization

Returnable transport items

Promotion management

Electronic proof of delivery (EPOD)

Parts Assembly Tracking

Product tracking and authentication

Process

integration (PI)

EPCIS-compliant

SAP OER*

Auto-ID repository Event management analytics Security services

Capture interface

Query interface

Trading Partners

Legacy

**Electronic Product Code Information Service

*SAP Object Event Repository

EPCIS**-compliant


[ 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

Integrating Auto-ID into

Business Processes Capturing Instance-serialized data

RFID

Linear Barcode

2-D Matrix Barcode [ECC200]

Sensors

…

ERP integration

Delivery integration

Production order integration

Kanban integration

ERP integration EhP 4 upwards

IUID Process integration

Central Serialization repository

Additional process integration

Is possible with customization

You can also leverage SAP PI

To connect to your

legacy systems

Automation

Without line-of-sight data capture

Remote data capture

Data carried by data/ asset

Verification at source

Universal Traceability Unifying information spaces in central

repositories

Single point of access for business

network data discovery & analysis

Single point of consolidated reference for

object lifecycle tracking and analysis

SAP

Solutions

for

Auto-ID

and

Item

serialization


[ Solution Scope – SAP Solution for Auto-ID and Item

Serialization

AII AII AII EmbeddedEmbedded

DM DM DM

Situatio

nal

Insight

Acti

on


[

© SAP

2009 /

Solution Scope – SAP Solution for Auto-ID and Item

Serialization

AII AII AII EmbeddedEmbedded

DM DM DM

Situatio

nal

Insight

Acti

on


[ Connectivity Options

© SAP

2008 /


SAP Auto-ID

Infrastructure

SAP Process Integration

EPCIS Interfaces

Web Services: Capture, Poll …

SAP Supply Chain

Event Management

EPCIS

Non-EPCIS Interfaces

File upload

IDoc, RFC, XML …

EPCIS

SAP or non-SAP

Patient Management

Clinical System

Partners‘ OER

Regional OER

Cell Phones

Tracking devices

and systems

http://images.google.com/imgres?imgurl=http://www.rfid-barcode.net/yj/back/upload/20083291523510.jpg&imgrefurl=http://www.rfid-barcode.net/yj/english/productsinfo.asp?pid=181&id=75&usg=__NSfPTe-4_fdT-DelfYjqWpHpkos=&h=259&w=259&sz=33&hl=en&start=4&um=1&tbnid=apG_ggkL7n4zZM:&tbnh=112&tbnw=112&prev=/images?q=fixed+RFID+reader&hl=en&um=1

http://images.google.com/imgres?imgurl=http://www.ferret.com.au/odin/images/241927/LXE-MX8-handheld-computers-available-from-Dematic.jpg&imgrefurl=http://www.ferret.com.au/t/Handheld-Computers&usg=___19_Xg73NM8TDLH6EuTrPz-CiHo=&h=235&w=227&sz=12&hl=en&start=12&um=1&tbnid=P5Ll3zELPfnXvM:&tbnh=109&tbnw=105&prev=/images?q=warehouse+handheld&hl=en&um=1

http://images.google.com/imgres?imgurl=http://www.mapds.com.au/newsletters/0807/iphone_home.gif&imgrefurl=http://www.mapds.com.au/newsletters/0807/Newsletter_18_July_2008.htm&usg=__9BQoqRpk7EGBuSYVGp8OxkJcEoQ=&h=495&w=300&sz=41&hl=en&start=1&um=1&tbnid=AaWJZbhjD6s-CM:&tbnh=130&tbnw=79&prev=/images?q=iphone&hl=en&um=1

http://images.google.com/imgres?imgurl=http://writenow.files.wordpress.com/2009/03/blackberry-curve1.jpg&imgrefurl=http://writenow.wordpress.com/2009/03/31/jerry-and-a-blackberry-not-jam/&usg=__o-mYHvrMSm3ZFA8lj2scSh0Qs0s=&h=2700&w=2092&sz=512&hl=en&start=10&um=1&tbnid=f_kGNqpvZ3m12M:&tbnh=150&tbnw=116&prev=/images?q=blackberry&hl=en&um=1


[ Local and Global Object Event Repositories

Regional / National OER

e.g., EFPIA (global)

Supplier

Hospital OER

(local)

Hospital

Arrive

Unpack

Reservation

Disaggregation

Packing

Return

Authenticate

Dispensing Authenticate

Dispensing

Goods Flow

Events Flow

Manufacture

Pack

Ship

Supplier‟s OER

(local)

Shipping Notification


[ Enabling Traceability at Hospital

1. Apply for GS1 Company Prefix if one is not already assigned, and define numbering schemes, like

GTINs

2. Map business processes and identification schemes into GS1 EPCIS standard and extensions, like

custom business steps, locations, disposition codes …

3. Define data-sharing standards and scenarios among Hospital OER and external systems or OERs

Suppliers„ or distributors„ systems or OER

Regional or national OER

Electronic Healthcare Record systems

4. Integrate equipment for automatic traceability (fixed scanners, mobile devices …) with OER

5. Set-up a system landscape

Clinical system (SAP or 3rd party)

Patient management system (SAP or 3rd party)

SAP Auto-ID Infrastructure for smooth integration for tracking equipment, scanners and

mobile devices

SAP Object Event Repository used as local GS1 EPCIS repository

6. Start with smaller scenarios and upscale them

Tracking of different objects: blood samples, implants, documents, devices, medications …

Volume of tracked objects

Collaboration scenarios based on traceability data

7. Provide feedback to GS1 EPCIS group for Global Traceability Standard in Healthcare

© SAP

2008 /


[

© SAP

2008 /

Overview of Business Locations

RIGHTS RIGHTS Policies

Central

Pharmacy

Nursing

Unit

Company Code

0370000

Site Sublocation

Extension

Production

Packaging

Shipping

Company Code

0370001

Site Sublocation Extension

Pharmacy

Nursing Unit

urn:epcglobal:fmcg:loc:0370000000028.Packaging


[

© SAP

2008 /

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)


[

© SAP

2008 /

Overview of Medication Track-and-Trace Process Steps

Prescription is

created in

Clinical system,

followed by

case-related

material

requisition in

HIS

Medication

picked at

Central

Pharmacy and

sent to Nursing

Unit

Expected events

for dispensing

created

Receipt of

medications is

automatically

registered at

Nursing Unit

Manufacturer,

Logistics Service

Providers,

Distributors,

Wholesalers

replicate

medication

lifecycle

milestones to

global repository

Shipping

Notification is

replicated from

Wholesaler local

repository to

Hospital local

repository

Unload with EPC

matching

Optional check

of traceability

history in local

OER

Alert if

dispensing

timeline has

passed

Patient / drug

match

performed

Quantity

corrections

recorded

All patients who

received pills

from certain

packaging

(SGTIN), GTIN

or batch

All medications

that one patient

received (should

match MAR)

1. Medication

Lifecycle

2. Medication

Received at

Hospital

3. Medication

Prescribed,

Picked, Sent to

RX

4. Medication

Received at

Nursing Unit

5. Medication

Dispensed to

Patient

6. Multi-

dimensional

Reporting

SAP Object Event Repository with SAP Event Management (local OER at Hospital)


[ Medication Tracking Overview

Prescription is

created in

Clinical system,

followed by

case-related

material

requisition in

HIS

Medications

picked at

Central

Pharmacy and

transferred to

Unit

Expected events

for dispensing

are created

Receipt of

medications is

recorded

automatically at

Unit

Manufacturer,

Logistics Service

Providers,

Distributors,

Wholesalers

replicate

medication

lifecycle

milestones in

global repository

ASN is

replicated from

Wholesaler „s

local repository

to Hospital „s

local repository

Delivery

checked against

Advanced

Shipping

Notification

Goods receipt

entered and

event recorded

in local

repository

Alert generated

if dispensing

timeline has

passed

Patient / drug

match

performed

Quantity

corrections

recorded

All patients

whoreceived

meds from

certain packaging

(SGTIN) or from

certain batch

(GTIN/batch)

All Medications

received by a

patient (should

match MAR)

1. Medication

Lifecycle

2. Medication

Received at

Hospital

3. Medication

Prescribed,

Picked, Sent to

RX

4. Medication

Received at Unit

5. Medication

Dispensed to

Patient

6. Multi-

dimensional

Reporting

SAP Object Event Repository with SAP Event Management (local at Hospital)


[ Patient Tracking Overview

Patient-id

number from

HIS is printed on

wristband

Case created in

HIS

Patient assigned

to room

Case-id and

patient-id

replicated from

HIS to Hospital

local repository

Nurse transfers

the patient to

another room,

and scans

patient-id and

location number

Patient/room

matching is

performed

1. Patient

Admission

2. Patient

Transfer

SAP Object Event Repository with SAP Event Management (local at Hospital)


[ Drug Anti-Counterfeiting Overview

Scan one or more

Medication id (serial

numbers)

Authentication codes

embodied into

Medication packaging

(e.g. Copy Detection

Pattern)

Send serial number and

optional

authentication code(s)

to Global Repository

Status check is

performed against

serial number

Authentication check is

performed against

authentication code(s)

Result is added to

Medication lifecycle

history in Global

Repository

1. Authentication

Check Request

2. Authentication

Check Response

SAP Object Event Repository with SAP Event Management (Local / Global)

SAP Support for GS1 Standards

Documents

Transcript of SAP Support for GS1 Standards