BSG FUNCTIONAL/TECHNICAL SPECIFICATION

PR#4488 JABIL SINGLE INSTANCE

ACTIVATE ESIGNATURES FOR WORKFLOW ITEMS

Produced by:
Jabil Business Systems Group Version 1
September 23, 2013
Table of Contents

1. DOCUMENT HISTORY (MANDATORY ALL) .............................................................................. 3

2. INTRODUCTION.............................................................................................................................. 4

3. PRODUCT PERSPECTIVE ............................................................................................................. 5

4. LAYOUTS (OPTIONAL FUNCTIONAL / TECHNICAL) .............................................................10

5. DATA ELEMENTS/MAPPING (OPTIONAL FUNCTIONAL/TECHNICAL) ................................10

6. PROCESS FLOWS (OPTIONAL FUNCTIONAL/TECHNICAL) ................................................ 11

7. SYSTEM PROCESS FLOW (OPTIONAL FUNCTIONAL/TECHNICAL)................................... 11

8. TECHNICAL DIAGRAMS (TECHNICAL SEE BELOW) ............................................................ 11

9. CODE COMPONENTS (TECHNICAL OPTIONAL) ...................................................................12

10. DATABASE (NON SAP SPEC) ...................................................................................................13

11. TOOLS AND TECHNOLOGIES ..................................................................................................13

12. TEST PLAN (MANDATORY FUNCTIONAL) ...........................................................................13

13. REQUESTOR SIGN-OFF (MANDATORY FUNCTIONAL) ......................................................13

14. SECURITY DETAILS (SAP T-CODE / ROLE ASSIGNMENT) ...................................................13

QM_E_006 Activate eSignatures for Workflow items Page 2 of 14

1. Document Histor y (Mandatory All)
PR # - Title PR4488-QM-Activate e-signatures for workflow items QM_E_006
Requester Name Larry Dube

Author Name Date Description/Section(s) Affected Revision

Mansi Agrawal 23/09/2013 Initial Draft 1
Alicia Kelly 10/17/2013 Updating with new Nypro notification types 2
and revised screen shots showing
enhancement at multiple points in the
notification process in SBX

QM_E_006 Activate eSignatures for Workflow items Page 3 of 14

2. Introduction
2.1. Overview (Mandatory Functional)
E-Signatures are required for quality notifications anytime there is a change in user
status (header level of the notification) or when task level changes occur. An
enhancement should be implemented to activate this and will be tied into workflow
(specification Workflow QM_W_001).
When the header or task level status changes, the signature box must pop up and
require the appropriate users to sign. This will keep a log of all users signing off on the
necessary actions that were performed in conjunction with the automatic SAP workflow
routing, both at the header level and task level of the quality notification.

2.2. Requirements Reference (Mandatory Functional)

Document Name Version Chapter Link to Document

QM_E_006 Activate This is the name referencing the original
esignatures for workflow Nypro specification.
items.

QM_E_006 Activate eSignatures for Workflow items Page 4 of 14

3. Product Perspective
3.1 Current State (Mandatory Functional)
Standard SAP does not provide electronic signature upon change of a notification. The only
standard functionality that exists is when a notification is put in process or marked
complete/closed. The creation of this enhancement will prompt users to sign anytime the
header level status or task level status changes.

3.2 Future State (Mandatory Functional)

3.2.1. System Requirements

The business requires that there be electronic signature (e-Signature)
functionality within the SAP solution for Quality Notifications. The e-
Signature functionality allows the business to meet the requirements of
the FDAs Code of Federal Regulations, Title 21 Food and Drugs, Part
11 (21 CFR Part 11). Enhancement will be implemented to activate e-
Signatures for quality notifications on changing quality notifications.
Enhancement should only apply to Nypro Quality Notification types N1,
N2, N3, N4, N5, N6, and NC.

3.2.2. Functional Requirements

o Quality notifications such as N4, N5 and N6 are created directly from
the process transactions such as results recoding
o Quality notifications such as N1, N2 and N3 are created by the users
o Quality notifications undergo various changes with respect to
content, task / user assignment and user status changes etc.
o Notification header level / system status changes such as notification
in progress (NOPR) and Notification Completed (NOCO) are
captured by notification signature object via configuration
o Notification task level changes / system status changes such as
tasks released (TSRL), tasks completed (TSCO) etc. are captured by
notification signature object via configuration
o This enhancement must capture all other changes such as user
status changes and or field level changes that are not captured as
explained above using configuration
o All such changes captured must be appended to standard e-
signature object.

QM_E_006 Activate eSignatures for Workflow items Page 5 of 14

The notification number can be found within the notification at the header level. Field name:
VIQMEL-QMNUM:

The user status can be found within the notification at the header level. Field name:
RIW000-ASTXT

QM_E_006 Activate eSignatures for Workflow items Page 6 of 14

The system status can be found within the notification at the header level. Field name:
RIW000-STTXT:

The task level status can be found within the notification at the task level. Field name:
RIW000-SMSTTXT

QM_E_006 Activate eSignatures for Workflow items Page 7 of 14

Upon saving of the notification the enhancement must pop up electronic signature window for
user to enter user ID / PASSWORD at the following times:
Putting notification in process:

Header level change:

Task level status change:

QM_E_006 Activate eSignatures for Workflow items Page 8 of 14

Completing Notification:

The successfully completed signatures are captured in the standard SAP audit trail / log tables

QM_E_006 Activate eSignatures for Workflow items Page 9 of 14

 3.2.3. Non-Functional Requirements
N/A

3.3. Other Considerations (Optional Functional / Technical see below)

3.3.1. Assumptions
N/A

3.3.2. Impacts
N/A

4. Layouts (Optional Functional / Technical)

4.1. User interface / Selection Screen Layout
N/A
4.2. Navigation
N/A
4.3. Reports (on screen display)
N/A
4.4. Output (print to paper)
N/A

5. Data Elements/Mapping (Optional Functional/Technical)

Provide data elements/mapping in the table below. Titles can be changed to meet the needs of the application.

Item Object identifier Object Type Restriction Function

1
2
3
4
5
6
7
8
9
10

QM_E_006 Activate eSignatures for Workflow items Page 10 of 14

6. Process Flows (Optional Functional/Technical)
6.1. User Process Flow
Where applicable, provide a flow chart depicting the process the user will follow

7. System Process Flow (Optional Functional/Technical)

Where applicable, provide a flow chart depicting the process the system will follow

8. Technical Diagrams (Technical)

8.1. Architecture / Interface Diagram (Mandatory New system, interfaces)

N/A
8.2. Data Flow Diagram (Mandatory New systems, interfaces)
N/A
8.3. UML Diagram(s) (Mandatory OO development)
This enhancement is not an OO candidate.

Code Inspector for ZQMEI_NOTI_DIGISIGN

Results for main program SAPLXQQM

8.4. Program Logic Flow / Pseudo Code (per coding module) (Mandatory)
If there is any change in header popup signature window then do the
following steps

QM_E_006 Activate eSignatures for Workflow items Page 11 of 14

 Call Method CHECK_VALUE from Class ZCL_CA_ZRANGE_UTILITY to
confirm if an Enhancement is active or not. Proceed only if the Enhancement
is active, the QM Notification Type is equal to NC and Transaction Code is
QM02..
Call FM QSS7_CREATE_SIGNATURE_NOTIF_0 for notification change
If database status is 'SBCO' or 'UNTT' and new status is 'DTAP' or 'PCNA'
If number of partners specified for partner function 'Y5 ECN Approver' is less
than 1 or greater than 7 display an error message

9. Code Components (Technical optional)

Project : ZQMESGNT
Enhancement : QQMA0014
Function Module exit: EXIT_SAPMIWO0_020
Includes : ZXQQMU20, ZQMEI_NOTI_DIGISIGN, ZQMEI_ECN_PCN_WF &
ZQM_SAVE
Transactions : QM01/QM02

Important Note: Workflow Enhancement QM_W_003 Configurations and Programs

must be installed and Implemented successfully for this
Enhancement to work in the Workflow Process as designed.

QM_E_006 Activate eSignatures for Workflow items Page 12 of 14

10. Database (non SAP spec)
10.1 Database Storage (Optional Functional/Technical)
N/A.
10.2 Database Schemas (Optional Functional/Technical)
N/A.
10.3 Data Dictionary (Optional Functional/Technical)
N/A.
10.4 Database Processing (Optional Functional/Technical)
N/A.

11. Tools and Technologies

12. Test Plan (Mandatory Functional)

TC_QM_E_006.xlsx

13. Requestor Sign-off (Mandatory Functional)

QM specs.pdf

14. Security Details (SAP T-code / role assignment)

14.1 Segregation of Duty Considerations

N/A

--End of document--

QM_E_006 Activate eSignatures for Workflow items Page 13 of 14

QM_E_006 Activate eSignatures for Workflow items Page 14 of 14