SAP Global Batch Traceability - websmp204.sap-ag.desapidp/... · Protect your Brand with SAP Global Batch Traceability Collection of slides: Guido Luft, Business Solution Architect,

Protect your Brand withSAP Global Batch TraceabilityCollection of slides: Guido Luft, Business Solution Architect, SAP Consulting

Slides: SAP GBT Development & Solution Management & SAP Consulting Update: Aug. 2014

http://youtu.be/S0-2D23CZt4

© 2014 SAP SE or an SAP affiliate company. All rights reserved. 2Public

Disclaimer

“This presentation 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.”


What Is SAP Global Batch Traceability?

What can you do with SAP Global BatchTraceability 1.0?

Trace complete product batch genealogies,their origin of supply as well as their internaland external distribution across SAP ERP andnon-SAP batch record systems systemsImmediate reporting on material balances andthe corporate internal and external distributionof batches

Business ValueProtect the brand owners‘ consumersProtect the brand in case of product issues with newspeed of action and extended reachIdentify parallel trade activitiesComply to reporting timeline requirements ofauthorities associated with recallsAssure that no inferior materials have been introducedinto product manufacture from increasingly globalsupply chains


Example GBT 1.0 Customer InsightBefore and after SAP Global Batch Traceability

Before SAP Global Batch Traceability: reactivetraceability in case of issue, puzzling data together

With SAP Global Batch Traceability: proactivemonitoring of global batch genealogy and distribution

Manual work, effort & time intensive…meanwhile the batch issue spreads…

ERP 1 ERP 2 ERP 3 ERP 4 NonSAP

Batch issueMany people trying topuzzle the batchgenealogy togethertrying to make sense ofbroken links

1. Search 2.Explore 3. Report

Aggregate &cleanse data

??

Complete global product batch genealogy from rawmaterial to finished product batches and their distribution

SAP Global Batch Traceability Repository

ERP 1 ERP 2 ERP 3 ERP 4 NonSAP


Future platform: Supply Chain Integrity for Pharma

SAP Object EventRepository

SAP Quality Issue Management

Supply Chain Integrity for Pharmaserialized traceability &reporting to authorities

cross-system qualityissue management

cross-system batchtraceability andreporting

track the progress of quality issues from issuenotification to resolution

trace the genealogy ofyour products and relatedtracked objects

track & trace serializedproducts and handlingunits

SAP Global BatchTraceability


Introduction to the SAP Global Batch TraceabilityRepository –Example Network (Graphical View)

Exploration of a batch at aspecific location (also Orders likeProduction Order, Purchase Order,Delivery,.. are possible)

Top-Down & Bottom up batchnetwork unified in one view

Connect various types of objectsfor traceability

Cross-System: Connect Objectsof different systems


Filtering & AggregationExample 2 - at first again without filtering: Screenshot (1)


Filtering & AggregationExample 2 - result of ‚Filter Out Production Orders‘ - Screenshot (2)


Solution highlights Key benefits

The batch network has been extended to understand batch distribution onHandling Unit/ Storage Unit level (with next Release 2.0 of SAP GBT)

• Search batches by handling unit• Display HU’s and SU’s in the batch network• Example Report “Distribution Records” to

show in addition to the batches delivered to acustomer also the HU’s /SU’s

GBT 2.0 supports the following scenarios:1. Material is “batch managed” and “handling

unit managed” with and without SAP WM2. Material is “batch managed” and “storage

unit managed”

• The batch network has been extended tounderstand batch distribution on Handling Unit/Storage Unit level.

• An important requirement communicated byConsumer Products Companies.

Extension of the batch network to include handling units/ storage units



Introduction of a work list to collaboratively work on product batch issueinvestigations (with next Release 2.0 of SAP GBT)

• Work list to save search results, share theseresults with colleagues, and further processthe involved objects at a later point in time

• Add Items to a work list manually ( e.g. fromthe graphical batch network view).

• Add one or more objects to a work list via areport based on a business logic.

• The corresponding follow-up function can betriggered from the overview list for singleobjects, multiple objects, or for all objects atonce.

• Example follow-up function: “Conversion ofunrestricted batch stock to stock in qualitycontrol movement type 322” issue

The Introduction of a work list enables customersto collaboratively work on product batch issueinvestigations, document investigations andtrigger follow-up actions, e.g. in ERP

Work List


Customer Testimony: SAP GBT is more than a solution foraccelerating time to insight into product batch issues

Customers communicated the following additional use and value of SAP GBT:Monitor Supply chain lead times by tracking material movement timestampsacross systemsPerform Quality assessments which are not triggered by formal events 10minutes versus hoursMonitor Parallel trade – customer returns material sold in another marketGBT as a source for continuous product verification looking through batchcharacteristics across sites / locationsMonitor multiple compliant shipments temperature control OK in eachshipment, but combined impact can be easily evaluated across systemsUnderstand global batch stock distribution at different stages of productionIdentification of process breaks


SAP GBTSAP ERPECC6.0x

ECC6.0x Integration – Delta Load Where Used Data

MaterialVendorCustomerBatch

MaterialMovements

Idoc Inbound

Table CHVW

ALE

RFC Pull (report)

GBT Objects, Business Partners

IDOC

Monitor

RFC Pull (report)Plant

GBT

TransferTable

Trans. Obj

Order, ...

RFC

RFC


ERP 1

The Basic Data Transfer Principle from SAP ERP

ERP Integration package for GBT (GBT Transfer Table)

Create POMat Doc:

GR with ref toPO

CreateProcess Order

Mat Doc:Confirm GR/GI

to Process Order

GBT scheduler pulls the data from the GBT Transfer table inERP

Batch

BatchProd.Ord.

Purch. Item

BatchPurch. Item

All ERP events being transferred toSAP Global Batch Traceability (GBT)are material document (goodsmovement) based, in which otherdocuments such as purchase ordersand process orders are referenced.

GBT then fetches additional datausing an RFC for those in thematerial document referenceddocuments

Data Transfer

Proc

ess

inER

PB

atch

Trac

eabi

lity

inG

BT


How the Product Batch Genealogy is being created…

ERP 1

CreatePurchase

Order

Mat Doc:GR with ref to

PurchaseOrder

CreateProcessOrder

Mat Doc:ConfirmGR/GI toProcessOrder

Proc

ess

inER

PB

atch

Trac

eabi

lity

inG

BT

CreateProcessOrder

Mat Doc:ConfirmGR/GI toProcessOrder

CreateDelivery

Mat Doc: PostGI w/ref to

delivery

1st manufacturing step 2nd manufacturing step

Batch 100Batch 100Apple

Concentrate

PurchaseOrder

48000852888

Process Order70011702

Batch 200Apple-OrangeMixture

ProcessOrder

700117098

Batch 300Apple-

Orange FruitDrink

Delivery item

Delivery item

Delivery item

Batch 101Orange

Concentrate

PurchaseOrder

48000852702

PurchaseOrder

48000852503

Batch 109Batch 1091 Ltr Bottles

Data transfer


Simple Example: Cross-system batch traceability

ERP 1

Proc

ess

inER

PB

atch

Trac

eabi

lity

inG

BT

ERP 2

1st manufacturing step

Data transfer

CreatePurchase

Order

Create SalesOrder

Process OrderPost GI w/ refto Outbound

Delivery

GR with ref toPurchase

Order


Concentrate

GR fromProcess Order

Process Order70011702

OutboundDelivery

80004711

PurchaseOrder

450001213


Concentrate



B2B SOA Inbound Service to capture upstream batch usage data(functionality with next Release 2.0 of SAP GBT)

B2B SOA service communication through amiddleware or point to point.

• Based on standardized Global DataTypes relaying on UN/EDIFACTstandard.

• Separation of transactional data andmaster data.

• Message interface is enabled forcustomer enhancements

With this service customers can capture supplierbatch usage information such as component batchwith associated origin data used in suppliedbatches, so as to assure that no inferior materialsenter the legitimate manufacturing chain.Full traceability back to farm will be required forlooming food traceability directives

B2B SOA Inbound Service


Table of CommunicationsConnection type Usage Reason for type usageHTTP Connection toABAP System(connection type H)

This connection is used toenable the navigation from theGBT details screens (forexample the batch detailsscreen) to the source ERPsystem for invoking display-transactions. It is optional. AWEB Service of the ERP with adedicated service no. is used.

The usage of the flexiblelaunchpad makes a HTTPconnection as mandatory in theconfig settings (via TA SM59)

ABAP Connections oftype 3 with a technicaluser (system)

This connection is used totransfer data created in ERP tothe GBT system. Without thisconnection no data will beavailable in GBT.

For initial load of ‚batch-were-used-data‘ for example

ABAP Connection oftype 3 with a dialog user

Connection is used to readadditional information from theERP systems. If you want to usereports like the stock informationor other custom reports thatneed to read additional datafrom ERP please create thisadditional RFC connection

Forced to have an authorizationfor accessing certain sourcesystem / or SSO (tunneling)possible


Deployment options

SAP GBT can be deployed in the following ways:1. SAP GBT as stand alone repository with SAP Net Weaver 7.31 basis

In this case, both SAP GBT and SAP ERP are deployed on different servers.

2. Co-deployment onto any existing NW 7.31 system such as SAP ERP EhP6

Additional system in the landscapeNo upgrade of ERPs required

No additional system in the landscapeERP on EHP6 (7.31) required

1. Standalone deployment

GBT ECCsGBTRINT 100

EA-APPL 6.06

SAP_APPL 6.00

NW 7.00

GBTR 100

BS_FND 7.31

NW 7.31

2. ECC Co-deployment

ECC with GBT ECCsGBTRINT 100

EA-APPL 6.00

SAP_APPL 6.00

NW 7.00

GBTR100

BS_FND 7.31

NW 7.31

GBTRINT100

EA-APPL6.06

SAP_APPL6.06

(*) The GBT 1.0 Co-deployment option onto any existing NW 7.31 system is available only on special request. Please [email protected].


Integration - Overview

Integration

Out-of-the-box integration with SAP ERP ECC 6.0x• for Batches, transactional and master data

•Call ERP Transactions from GBT for detailed Object Views with all details

•RFC to read additional data (Stock Infos,..)

SOA-Service for GBT-Events

File Import for GBT-Events

BAdI to add own rules for creating Object relations

Easy to Enhance without modification


Solution Proposal – INon-SAP Integration (without ERP)

GBTNWA

Monitoring

Mapping

SOAService

InboundQueue

File UploadReport

GBT DB

Non-SAP Systems

Where UsedData

Master Data

TransferFile

ConnectionLayer

SAP PI orSAP MII(optional)

Mapping

HTTP


Solution Proposal – IINon-SAP Integration (with ERP)

SAP GBT

Monitoring

SAP ERPECC6.0x

Non-SAP Systems

RFC PullReport

GBT Objects

WhereUsed Data

Connection

Layer

TableCHVW

MaterialMovements

GBTTransfer

Table

Trans. ObjOrder, ...

RFC


Product Genealogy solution

Product Genealogy

Features SAP ERP BatchWhere Used List

SAP Global BatchTraceability

Top Down / Bottom Up Analyze (Tree View) Yes Yes

Top Down / Bottom Up Analyze (Graphical View) No Yes

Cross-system tracing capabilities No Yes

Consider non SAP Systems No Yes

Consider Non SAP Tracked Objects (e.g. Pallets) No Yes

Analyze multiple tracked objects in one run No Yes

Identify broken links and maintain batch network No Yes

Reporting for regulatory and customers needs No Yes

New data model for high performance No Yes

Compare ERP Batch Management with Global BatchTraceability


Reduction to time of insight for actionWhat Customers achieved with GBT 1.0

0

100000

200000

300000

400000

500000

600000

700000

800000

900000

BeforeAfter

288000

35

864000

300

Customer A Customer B

Time inseconds

Customer A could reduce the timetaken to investigate a complex batchissue from 2 weeks (=288000 seconds)to 35 seconds >8000x faster*

Customer B could reduce the timetaken to investigate a complex batchissue f from 6 people for one 1 week to1 person in 5 minutes >2800x faster*

*Insights communicated by customers from GBT testing,where customer loaded historic batch issue data to comparetime to insight achieved with GBT compared to time takenprior to GBT

Assumption is 1 work week= 5 days x 8 hours


Extensibility of SAP Global Batch Traceability (I)

SAP GBT can be extended:

A) Master data - related:

Batch master extensibility by usingclassification

Get more data from IDOC

Multiple systems with same names ofcharacteristics and classes: can be separated

B) Business documents - related:

Field extensibility (support of customerincludes)

New business documents: registering in GBT

Integration ERP/GBT: Usage of BADI/ AccessClass in ERP / enhanced data of GBT-events

Integration of non-SAP ECC Systems (SOA-Services, File Import)


Extensibility of SAP Global Batch Traceability (II)

C) UI extensibility(in order to make objects visible additionally in SAP GBT…)

The UI in SAP GBT is based on:

Floor Plan Manager (FPM) for WebDynpro ABAP

Microsoft Silverlight ® for the Graphic

For the UI extensions…

mainly the configuration of FPM needs to be adopted.

Navigation to other systems: by the Launchpad

Technical concept is based on object types/ node types,specific DDIC structures, with customer includes


Solution Video & Technical Information

Get a quick overview as to thevalue, the solution and 2 exampledemos – see the SAP GBTSolution Video on YouTubehttp://youtu.be/S0-2D23CZt4

Technical Guides – such as MasterGuide can be downloaded fromhttp://help.sap.com/gbt10


Visit the SAP Solution Browser @www.sap.com/solutionexplorer

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

…a GBT Business Case

33© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Bill, a plant supervisor, identifies a malfunction on aproduction line

34© 2014 SAP SE or an SAP affiliate company. All rights reserved.

John, a Quality Management Expert, can now immediatelyexplore the issue and pinpoint all affected bad product batch

stock


The supervisor calls and advises that there has beenissue with production line A on (the) 12th December 2011.


The supervisor calls and advises that there has beenissue with production line A on (the) 12th December 2011.


Immediately the QM expert understands that the secondbatch was already distributed to external parties


Immediately the QM expert understands that the secondbatch was already distributed to external parties


Push of button creation of a distribution report formultiple batches in a single run


Push of button creation of a distribution report formultiple batches in a single run


Create a Material balance report at a push of a button


Create a Material balance report at a push of a button


© 2014 SAP SE or an SAP affiliate company.All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or anSAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additionaltrademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE orSAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products andservices, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any relatedpresentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliatedcompanies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may bechanged by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertaintiesthat could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-lookingstatements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Documents

SAP Global Batch Traceability - websmp204.sap-ag.desapidp/... · Protect your Brand with SAP Global Batch Traceability Collection of slides: Guido Luft, Business Solution Architect,