Pfizer’s Implementation of ECM for Labeling and ... - SAPfm.sap.com/data/UPLOAD/files/Pfizer HCL...

Packaging Integration

Location: SAP America Inc., Newtown Square, PA

Date: March 17, 2010

Pfizer’s Implementation ofECM for Labeling andPackaging Processes

Bob Woodward – Pfizer Inc.Rakesh Shah – HCL-Axon Inc.

2

Pfizer – Who We Are

Pfizer is a global leader in pharmaceuticals, consumer health care products,and animal health care products.

Pfizer PharmaceuticalsPfizer has a long history of pioneering developments in pharmaceuticalsand biotechnology, with leading products in many areas.

Pfizer Consumer HealthcareSome of our well-established product lines — Advil®, Centrum®, andRobitussin® — are among the top 20 non-prescription medicines in theworld.

Pfizer Animal HealthAnimal Health offers a broad range of biological and pharmaceuticalproducts for the companion animal, equine, livestock, swine and poultryindustries.

3

Business Problem

• Master data replicated in multiple systems with manualhandoffs.

• Many disparate change processes and systems for ShipperCase Labels, Specifications, BOMs, Artwork, and LabelingDocuments.

• Legacy platform no longer supported and not integrated intoSAP.

• Collaboration across operating units and divisions difficult

• Process Order Released before BOM and Packaging Specs areeffective.

4

Project Goals

• Institute worldwide labeling and packaging change controlprocesses.

• Visibility to the change process through out the life cycle.

• Integrate the Labeling and Packaging Divisions into a seamlessprocess.

• Drive global standardization, and increase visibility to thesestandards, in packaging and labeling across sites.

• Decrease complexity of current process and help ensurecompliance.

• Consolidate information management in a single system

5

Project Challenges

• SAP was designated as the system of record for data andDocumentum was designated as the system of record fordocuments.

• Real-time integration of enterprise systems

• The Business required a web-based solution that was userfriendly and supported collaboration.

• SAP’s Engineering Change Request/Order process did notsupport object management records for EH&S Specificationobjects.

6

Learning Points

• SAP can be used to manage change control processesacross enterprise applications (SAP and Documentum)

• SAP Engineering Change Management (ECM) can bedelivered by SAP Portal to provide a seamless userexperience.

• SAP’s BW provides the capability to report acrossenterprise systems with a consolidated view.

• SAP’s ECR/ECO function can be enhanced to supportEH&S objects and Object Dependency Checks as well asprocess order release integration .

• SAP’s GLM module can be used to support Shipper CaseLabels.

7

Workflow 5.0

SAP Enterprise Portal 7.0 DCTM 5.3EP 7 iViews – SAP ECC 6.0, NW 2004s BI

Change ManagementNotification / ECR / ECO 5.0

DocumentInfo

Record

Web Services

DocumentInfo

RecordDocument

InfoRecord

DocumentInfo

Record

SpecificationsBill of MaterialsMaterial Master

PMIS

Drawings

Label Text

Artwork

Supporting Documents

Solution Architecture for Integration

Integration via Web Services

WAS 6.40 BPM 5.3 WorkflowWebServices

8

Request to ECR to ECO

Web Request Process Notification WAS ECR/ECO Process R/3

Request Review Evaluate Authorize

Attach/Create Documents and Objects

Analyst Convertto ECO

ObjectWorkflow

(Edit, Review)

ApproveEach Object

Add Supporting Documents

ReleaseECO

ApproveECR

ReleaseEach Object

Coordinator

BOM Matl'sWF

ArtworkDIR

DrawingDIR

LabelTextDIR

CoreData

SheetDIR

ShipperLabelSPEC PMIS

amendment

Project Tracking and Reporting - BW

Project Overview

9

Object Relationship

Material Master(SAP MM)

ComponentSpecification(SAP EHS)

ArtworkDCTMDIR

DrawingDCTM

BOM

DIR

PMISSpecification(SAP EHS)

N:N

1:11:1

1:1N:1

N:1

DIRLabel Text

DCTM

1:1

N:1

PMIS Reviewand Annotation

ReportSAP DMS

1:1

1:N

ShipperLabel

SAP Objects

DCTM Objects

10

Managing Change Control Across Many Systems

• The complex nature of these changes required one system tomanage the process. SAP’s OTB functions for statusdependent change control provided the framework to manageall of the objects across the enterprise systems.

• The use of SAP’s Document Info Record is used to representthe document content stored in Documentum. We leveraged‘Web Services’ in SAP and Documentum to enable the cross-system integration.

11

SAP ECM and Enterprise Portal (EP)

• Initiated a stage gate process to manage and build the changecontrol.

• The EP provides role based content based upon their jobfunction. Access to ECC 6.0 transactions, BSP applications,Documentum iViews and BW reporting provided thru SAP’s EP.

• Utilized EP Universal Work List (UWL) to provide a commoninbox for SAP related work items.

• Built a common process which supports all of the operatingunit business functions.– Consumer Health, Vaccines, Nutritionals, and

Pharmaceuticals will all use the same change requestprocess for packaging and labeling.

12

Labeling & Packaging Home Screen

13

Portal – Universal Work List

14

Request Form

15

Request Form - Objects

16

Request History

17

ECR/ECO for Specification

18

ECR/ECO for Specification

19

SAP’s Netweaver platform

• Utilized SAP’s Web Application Server (WAS 6.40) to developBusiness Server Page (BSP) applications to front end thechange request process.

• Implemented Single Sign On to support the process.

• Provided an application frame work from which other changecontrol processes can leverage the building blocks.

• Enables integration to Documentum via Web Services.

20

Project Reporting via SAP BW

• SAP BW 7.0 used to support management reporting from bothSAP and Documentum.

• Provides an overview of the change control process and thestatus of the objects at their various workflow states.

• Provides drill down capability to detailed change controlinformation.

• Out of the Box integration into SAP’s EP allows the end usersto log in once to the Portal and have access to all of theirinformation needs.

21

SAP’s ECR/ECO function can be enhanced tosupport EH&S objects

• Enhanced the ECR/ECO transactions to support the EH&SSpecification Master.

• Activated Specification view for the material master.

• Specification Master status driven workflow and digitalsignature integrated with ECR/ECO process.

• Specification Master with linkage to the DIR.

• Utilize Windows Word Integrator (WWI) to automaticallygenerate various specification reports.

22

SAP’s GLM to Support Shipper Container Labeling

• Activated the Label Data view for the material master.

• Bar Code enabled through an Active-X product. (TEC-IT)

• Built label templates utilizing the WWI capability of EH&S,including pulling data from Material Masters, Process Orders,Specifications and calculation of the check digit.

23

Specification with Status Network & ChangeNumber Effectivity

24

Specification with Document Links

25

Questions

Questions?

Robert Woodward – robert.woodward@pfizer.com

Rakesh Shah – rakesh.shah@hcl-axon.com