FSD PTP F031 Material Label 05-13-2014 SO

SAP Form Functional
Specification
FSD_PTP_F031_Mate
rial Label
FSD_PTP_F031_Material Label
ARTHREX
Page 1
Table of Contents
1
OBJECT REQUIREMENTS SUMMARY...................................................................4

1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
FORM DESIGN DETAILED SPECIFICATIONS........................................................8

2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
OBJECT INFORMATION AND ATTRIBUTES.................................................................4

REQUIREMENTS SUMMARY AND BUSINESS DRIVER................................................4
ASSUMPTIONS.......................................................................................................4
CURRENT FUNCTIONALITY.....................................................................................4
REQUIRED FUNCTIONALITY....................................................................................5
PROJECT / DEVELOPMENT CONSTRAINTS...............................................................5
PERFORMANCE CRITERIA......................................................................................5
OTHER OBJECTS AFFECTED..................................................................................5
EXTERNAL REFERENCES.......................................................................................6
DEFINITIONS/ACRONYMS/ABBREVIATIONS...............................................................6
DETAIL REQUIREMENTS:.....................................................................................8
DATA SELECTION-SCREEN / CRITERIA:...................................................................8
FORM OUTPUT LAYOUT:........................................................................................8
FORM OTHER INFORMATION...............................................................................9
PRINTING / MEDIA REQUIREMENTS:.....................................................................10
ERROR HANDLING METHOD:................................................................................11
POST EXECUTION NOTIFICATION DETAILS:...........................................................14
PROCESS LOG DETAILS.......................................................................................14
ADDITIONAL INFORMATION.................................................................................14
3.1
3.2
3.3
3.4
UNIT TEST PLAN.................................................................................................14

INFORMATION SECURITY......................................................................................16
AUDIT.................................................................................................................19
QUESTIONS / ISSUES / RISKS...............................................................................19
Page 2
Business Process Organizational Structure

Process Owner
Original Author(s)
Current Revision Author(s)
Version
0.1
0.2
0.3
0.4
0.5
Date
Feb 8 2014
Mar 25 2014
Mar 27 2014
Apr 8 2014
Apr 11 2014
Author(s)
Melissa Jeng
Melissa Jeng
Prashanthi Bollu
Melissa Jeng
Prakash P
0.6
0.7
Apr 12 2014
Apr 27 2014
Dimitri Koutsouras
Prakash P
PTP
Rich Hughes
Melissa Jeng
Prakash P
Revision Notes
Initial Draft
Content
Configuration steps
Format layout
Table-field mapping/logic added
Enhancement details with selection
screen added.
Review
Updates as advised by Rich H in FDS
approval meeting on 04/16/2016
Page 3
1 OBJECT REQUIREMENTS SUMMARY

1.1
Object Information and Attributes
Req No.
Requirement Description
URS.4.5.1.1.001 Ability to receive materials with
0
vendor batch number as the SAP
batch numbers
URS.4.5.1.1.002 Ability to receive serialized materials
0
URS.4.5.1.1.005 Ability to create a transfer order for
0
received materials going to stock
based on business rules. (create
transfer order but do not confirm
transfer order)
GXP
(Yes/No)
Risk
(H/M/L)
Probability
(H/M/L)
N
N
N
The following is current information about this object and document:

Object ID
Title
Author(s)
Team Which Owns
the Object
System Version
Development Type
Priority
Estimated
Complexity
Link to Process
Flow
FTM Team
Validation
Required
1.2
146 - FSD_PTP_F031_Material Label

FSD_PTP_F031_Material Label (Material, Quantity, Batch, Serial
Number, SLED)
Melissa Jeng
PTP
ECC 6.0
Form
High
Medium
FDD_PTP_4.5.1.1_WM Inbound Process
Yes
No
Requirements Summary and Business Driver

When goods of a purchase order are received at Arthrex, materials will be unpacked and
transferred put-away.
1. The material label is required to be printed from SAP as desired by Arthrex for
any material in the Goods Receipt for a Purchase Order. This is to be enable
easy identification and tracking of package in Warehouse.
Page 4
2. The material label should include

a. Material,
b. Material Description
c. Quantity,
d. Batch number,
e. serial number, and
f. Shelf Life Expiry Date (SLED)
3. This process is not to be automatic but the labels are required to be printed On
Demand basis.
4. If the material for which the label is demanded to be printed is serial number
managed one label for each serial number is required to be printed automatically
5. A custom print program needs to be created for this requirement. SAP Material
Label print program (RTLABELO) may be used as a reference to create a
Zprogram (say ZRTLABELO)
.
1.2.1
Alternatives to Object
An alternative would be to use the current label printing program using legacy
systems, which requires to manually keying in the information outside of SAP.
1.2.2
Impact of Implementation
Warehouse team members will be able to print material labels when and with
what field entries they would like. They can affix each material that is received
with the label to identify its master data components. The barcode will allow its
master data components to be identified and added to a transaction when
scanned.
1.2.3
Impact of No Implementation
There runs a risk of human error when the operator enters the goods receipt in
SAP and then enters the information again in Label Matrix.
1.3
Assumptions
1.4
All the data for material labels exist in SAP

All relevant configuration is in place
Output condition is maintained in goods receipt
Printers are configured in SAP
All master data elements required to support the goods receipt are available
Current Functionality
Currently Arthrex keys in the goods receipt in QAD, and has a separate system for
printing labels. The operator goes over to Label Matrix to enter the same information, in
Page 5
order to print the corresponding label. This process is prone to errors, as the operator
enters the information twice: once for the goods receipt and once to print the label.
A sample material label that is currently used at Arthrex is included below:
1.5
Required Functionality
Arthrex requires a custom transaction code for printing the material label to print Material
Labels as needed.
The material label needs to get printed either using GUI interface, or using RF device
interface.
So the user interface has to be provided for both the interface(Using GUI and using RF)
It will also be necessary to create
1. custom TCode for GUI interface
2. For RF interface.
Arthrex does not need Material Labels for all the materials received. For example, sterile
goods will not require a material label.
This functionality requires a custom development for following objects
1. A custom GUI transaction
2. A Custom Print Program
3. A Custom RF transaction
Using these custom objects, the user is to be enabled to print the required labels.
.based on the inputs in selection screen.
The Arthrex label needs to be containing required information as specified in details in
sections that follow.
When the user needs to print a label, he/she will access a custom transaction (mock
selection screen included below) and provide inputs.
Page 6
Scenario 1
The label is to be printed when the Material Document number ( that is Goods Receipt
Document number) & Item number is known.
(This is expected to be the most common scenario. Labels are required to be printed
immediately following the Goods Receipt Document is printed before the Putaway is
completed.)
In that case, the user inputs the material document number and Item number
1. By Scanning the bar code on GR printed document ( ID 145: FDS
FSD_PTP_F030_Goods Receipt Form bar coded with QA inspection lot )
For RF interface.
Or
2. By providing manual input using RF device.
The material document year value should be defaulted in the background to current year
for user convenience.
Based on the material document number and Item number combination (for the current
year) the system retrieves the material number and populates it in the Material Number
field.
The system also checks the if the material master record specifies if the material is
Assigned a serial number profile by checking if the a valid value of serial number profile
exists (Table /Field MARC-SERNP)
Page 7
If the material number is assigned a value, then the program automatically populates
value 1 in Quantity field in Display only mode.
The system also populates value Yes in field Serialized Label.
It also automatically checks the quantity in the material document (MSEG-ERFMG)
And populates this number in the No of Labels ( a custom field) field in display only
mode. The user would not be able to change this value.
If the material is assigned a serial number profile and hence having a serial number, one
label each is required for each serial number based on the material document.
The printer to be selected by the user has to be a bar code printer on SAP network.
The quantity per box appearing on the label needs to be user defined for materials that
are not assigned a Serial Number profile (MARC-SERNP is blank)
The Number of Labels field is also to be a field available for user input.
The user executes the GUI or RF transaction and the label should get printed.
If the print is successful, then the system will display the message: xxx Labels printed
successfully..
If the label cannot be printed suitable error messages should be provided.
The label should include the following fields:
Arthrex logo
Material with barcode
Material Description.
Batch (Lot) number with barcode
Serial number
Shelf life expiration date
Quantity with barcode
For items that are not batch managed, the field will return blank.
Page 8
Scenario 2:
Arthrex needs one more user interface for printing labels as per details below:
There needs to be another transaction code for this interface both in GUI and RF
In this case, the user shall input :
the material number &
batch number.
Qty:
No of Labels:
The system shall validate that the batch number is valid for the material by checking
In if the batch number provided is a valid one.
From a functional view point, this can be done using TCode MSC3N
Driver Program Logic:
1. Pass the material number and Batch to MCH1 table
2. Also pass value if MCH1- LVORM is (Batch deletion indictor is not set)
Only if the system returns an entry proceed to print the labels the same way as in
scenario1.
From Development perspective, pass the mate
The developer is requested to find suitable Table name/field name or function module
To perform validation technically.
The print program is then required to print the material labels the same way as it does
for scenario 1.
Page 9
1.6
Project / Development Constraints

All warehouse management and goods receipt configuration needs to be completed
prior to testing this transaction.
1.7
Performance Criteria
Performance Requirements for Forms
Average Frequency:
5/Minute
Minute
Frequency per Peak:
10/Minute
5 People per Location (ALC, AMI East, AMI

North, etc.) will be using the transaction at the
same time
Availability:
24/7
Expected Average Response

Time:
Expected Peak Response
Time:
1.8
Sub-second
1 Second
Other Objects Affected
Object
Impact/Change Description
N/A
SAP System
SAP Module
N/A
NON-SAP /
Legacy
System
N/A
Dependencies:
Dependent Configuration:
N/A
Page 10
1.9
External References
Document Title
Author
Graphic Identify
Arthrex
Attachment / Links
Arthrex GRAPHIC
IDENTITY Guidebook.pdf
1.10
Definitions/Acronyms/Abbreviations
WM Warehouse Management
GR Goods Receipt
FDD Functional Design Document
UT Unit Test
SLED Shelf Life Expiration Date
Page 11
2 FORM DESIGN DETAILED SPECIFICATIONS

2.1 Detail Requirements:
Upon entering goods receipt, the operator should be given the option Yes or No to
create a material label. If the operator chooses Yes, he/she is asked to enter number of
labels desired and the quantity for each label. Then the label is printed, as per the layout
below.
The form should measure 4 x 2
form below.
(4 x 2.875) and have the same font as the sample
Data Selection-Screen / Criteria:
Scenario 1 ( The most common scenario)

The Material Document # and Item number is available with the user in human readable or
Scanned format.
Page 12
Table Field /
Material
SelectOption (S) or
Checkbox /
Parameter
Radio Button (P)
MSEG
MATNR
Material Number
Material Doc
MKPF
MBLNR
Material Document Number
Mat Doc Itm #
MSEG
ZEILE
Mat doc Item #
Mat. Doc. year MKPF
MJAHR
Material doc. Year
Serial Number EQUI
SERNR
Serial #
Field Name
Comments (Range,
Single/Multiple Selection,
Patterns, Mandatory, etc.)
Validations
(For Each
Field if any)
Scenario 1:
Populated
by system
based on
the material
document
number &
Item number
combination
scanned/ent
ered by
user.
Entered by
user using
RF device
or manually
Entered by
user using
RF device
or manually
Default
Value
The user
should
visually
verify this
data.
System
validation
required
System
validation
needed.
Default
value
Current
year.
This field
may be
hidden for
user
interface
This is a
Pass
display field Material
only. The
document
system
no to
populates
SER03 table
value Yes to get
in this field if SERNR)
material has (serial
a serial
numbers.)
number
profile
assigned to
it.
Page 13
Quantity
n.a
n.a
User desired value up to 999
Number
should be
less than
999
This field is
populated
with value 1
if the
materials
having serial
number
profile
(MARC-
SERNP not
equal to
blank
Printer
Label printer on SAP network
Label Output Layout:
See the table below for required fields for the material label. All SAP default logic should apply
that are not mentioned in the mapping sheet (ex. deleted line items are not printed; line feed;
page break etc.).
Number of
the field on
the attached
Form Layout
Table Name
Field Name
N/A
N/A
Maximum Number of
Field Description Conditions / Data Retrieval
Characters to print
Logic
Logo
MSEG
MATNR
Material Number
MAKT
MAKTG
MAKT
MATNR
Material
Description
Material Barcode
MSEG
CHARG
MSEG
CHARG
MSEG
VFDAT
Batch (Lot)
Number
Batch Barcode
Shelf life
expiration date
Refer section 1.9 and the

logo in the Arthrex label
currently used ( sample
provided)
Defaulted by system from 18
Material document #, item
number and current year
Pass MATNR to MAKT
40
table and get MAKTG
Convert MSEG-MATNR to
bar code format using EAN
128 standard
From MSEG table.
10. If longer,
truncate the value
Convert MSEG-CHARG to
128 standard
10
Page 14
CAWN
ATWRT
Revision No
Heres the logic to use:

Go to table MCH1, enter
material# & Batch# &
ensure that shelf life
expiry date is valid.
Once you find the
record, get the field
value for CUOBJ_BM
(Internal object #). Call
this A.
Go to CABN table,
enter REVLEVEL into
Characteristic field
(ATNAM). Get the
value of ATINN from
here. Call this B.
Go to table AUSP, enter
A into OBJEK field & B
into ATINN field. The
value from the field
ATWRT is the batch
revision value.
N.A
N.A
Quantity
User Input in selection

screen
Scenario 1:
For materials with
Sr.No profile (
If serial number is
required to be
printed the allowed
value is 1.
If different, return
suitable error
message
Quantity Barcode Convert value of number in

row # 8 to bar code using
EAN128 standard
Page 15
10
EQUI
SERNR
Serial Number
The user shall input this

number.
The system should
validate the number by
using Function Module
GET_SERNOS_OF_DOC
UMENT
(Pass goods receipt
Document # to the function
module as
MBLNR
MJAHR - Material
Document Year (optional)
And retrieve the serials
numbers
Compare the entered
serial number
Proceed to print the label
only if a match is found.
Number of
the field on
the attached
Form Layout
Table Name
Field Name
N/A
N/A
Maximum Number of
Field Description Conditions / Data Retrieval
Characters to print
Logic
Logo
Refer section 1.9 and the

logo in the Arthrex label
currently used ( sample
provided)
Entered by user
MSEG
MATNR
Material Number
MAKT
MATNR
MSEG
CHARG
MSEG
CHARG
MSEG
VFDAT
N.A
N.A
Material Barcode Convert MSEG-MATNR to

128 standard
Batch (Lot)
Number
Batch Barcode
Convert MSEG-CHARG to
128 standard
Shelf life
MM/DD/YYYY format
expiration date
Quantity
User Input in selection
screen
18
10. If longer,
truncate the value
10
If serial number is
required to be
printed the allowed
value is 1.
If different, return
suitable error
message
Page 16
8
10
SER03
SERNR
Quantity Barcode Convert value of number in

row # 8 to bar code using
EAN128 standard
Serial Number
The user shall input this
number.
The system should
validate the number by
using Function Module
GET_SERNOS_OF_DOC
UMENT
(Pass goods receipt
Document # to the function
module as
MBLNR
MJAHR - Material
Document Year (optional)
And retrieve the serials
numbers
Compare the entered
serial number
Proceed to print the label
only if a match is found.
In Dev 300, please see
test data directory for test
data.
Page 17
11
AUSP
ATWRT
Heres the logic to use:

Go to table MCH1, enter
material# & Batch# &
ensure that shelf life
expiry date is valid.
Once you find the
record, get the field
value for CUOBJ_BM
(Internal object #). Call
this A.
Go to CABN table,
enter REVLEVEL into
Characteristic field
(ATNAM). Get the
value of ATINN from
here. Call this B.
Go to table AUSP, enter
A into OBJEK field & B
into ATINN field. The
value from the field
ATWRT is the batch
revision value.
Page 18
Material Label.vsd
Additionally, mention the following:

Is it a modification to standard form?
(If yes, check the box)
Is it complete new custom form
development?
(If yes, check the box)
SAPScript / SMARTFORM / Adobe Form:
(Mention the type of form)
SAPScript / SMARTFORM / Adobe Form
Name:
Output Type:
Print Program Name:
Standard Text:
Logo:
(Attach as files)
Bar Codes (field names):
Language translation constraints:
(List languages to be considered for form
development)
Output Destination:
(Check all that apply)
Number of forms to print per run:
IMG Configuration, if any:
Menu Path to Generate Form:
Smart Form
PRODUCT_LABEL
ET01
RTLABEL0
N/A
Arthrex Logo Blk.tif
TANUM
All SAP supported language. EN, DE etc.
Hard Copy
EDI
FAX
Hard copy to a specific printer
1
2.1 Form Other Information

Form Processing Requirements
Calculations / Transformations
Value to be Derived
Business Rules / Algorithm For This Transformation
N/A
Page 19
Other Updates Performed During Processing Not Specified Above

Initiating Event
Updated Information
Rules For Update
N/A
Other Form Requirements (Not Specified Elsewhere in This Document)

Number
1.
2.
Description of Requirement
N/A
1.1 Printing / Media Requirements:

Output Device Name:
(Mention the Output Device Name)
Number of Copies:
(Mention number of copies to be printed)
Spool Request Name:
(Mention if any specific spool request
name)
Print Immediately:
(Check the box if yes)
Delete after Output:
New Spool Request:
Close Spool Request:
Paper Format
Paper Size
LOCL
1
TBD
Label with adhesive

4 x 2.875
Page 20
1.2 Error Handling Method:

Failure Points
Possible Point Of
Failure
Scanning, security, or
connectivity issues
Transfer Order is not
found
System does not allow
entry of a given value
Material is not found or
no quantity
Rules For Handling Failure
Resolve issue with technical team

Resolve issue with receiving management group
Resolve issue with receiving management group
Resolve issue with receiving management group.
Error Handling Requirements

Information Needed
Error Detection
Error Notification
Error Logging (beyond
notification)
Error Remediation
Description
Range check validation errors on screen inputs will be logged on

the screen input via message notification. For forms used for
processing, reporting, Error List will be directed to spool output and
an email notification will be sent.
Contact COE help desk
None
1.3 Post Execution Notification Details:

N/A
1.4 Process Log Details

N/A
Page 21
3 ADDITIONAL INFORMATION
3.1 Unit Test Plan
Identify the Test Scenario to be used to test the development with:
Test Considerations
Scope of Testing (Inside

SAP (IS) / Outside SAP
(OS) / Both (BO))
Target Test Date
IS
05-30-2014
UTP003_PTP_F031_
Material Label.xlsx
Page 22
Information Security
3.2.1 Information Classification
General Information
Businesses Impacted:
Arthrex
Rich Hughes
Date
3/25/2014
Contact Information
Company
Name
Phone
E-mail Address
Rich Hughes,
Richard.hughes@a
List Potential
Arthrex
Rick Koharki
rthrex.com
Information Owners:
Architecture
Environments: (impacted by this T spec):
Development
Test
Training
Production
Public (Internet) Facing
Internal Only
Architecture: (system exposure):
3rd Party Hosted
Company * Hosted
Information Classified by whom:
During Project
3rd party system access required?
Identity & Access Management

rd
Offshore?
Yes
Yes List the 3
Parties:
No
No
Post Implementation
3rd party system access required?
Offshore?
Yes
Yes
No
No
Business Impact Analysis
List the 3rd

Parties:
What may be impacted if the system or information/data is compromised? Check all that may apply.
Brand Reputation/Trust
Associate Relations
Competitive Advantage
Financial Impact
Productivity
Supply Chain
Contractual (i.e. NDAs, MSAs)
Regulatory
Compliance
Securities & Exchange Commission (SEC)
Payment Card Industry (PCI)
Sarbanes-Oxley (SOX)
Privacy Laws
Input any additional details related to business impact in the event of compromise:
Page 23
Information Classification
Action #1: Check the box below that represents the most restrictive classification.
Action #2: If Level 1 or 2 is selected, check the box below indicating data storage or data
transmission.
See Information Classification, Labelling and Handling in [Clients]s ISC Standards for details
on the formal classifications and data handling standards.
Level 1 Confidential Secure Handling Required SHR
Confidential Secure Handling Required represents the most sensitive data classification related to individual
personal identifiable information and personal financial account information. This information considered critical to
[Clients] such that, if disclosed, may disrupt or impede business operations, and due to legal, reputational, or
operational concerns, requires additional security controls. Information in this category includes, but is not limited
to:
1. Social Security Number
2. Drivers License Number or Government-issued Identification Number
3. Financial Account Number (card number or personal bank number)
4. Protected Health Information & Electronic Protected Health Information
SHR data stored?
SHR data transmitted?
SHR data stored and transmitted?
Level 2 Confidential
Confidential represents the second most sensitive data classification related to operationally significant business
information. This information considered critical to [Clients] such that, if disclosed, may disrupt or impede business
operations. Examples of Restricted Confidential include but are not limited to regulatory governed data, trade
secrets, mergers and acquisition discussions, product formulas and designs, corporate earnings data prior to public
announcements, reorganization details prior to announcements, current/closed company investigations and
litigation, detailed network diagrams that could jeopardize network security, strategic development/marketing plans
and information integral to the success and operations of the company.
Confidential data stored?
transmitted?
Confidential data transmitted?
Confidential data stored and
Level 3 Internal [Clients] Use Only

Internal [Clients] Use Only represents the third most data. It represents information that is less critical to privacy
and business operations but still must not be publicly disclosed. This information is not approved for general
circulation outside [Clients].
Level 4 - Public
Public represents information that has been declared public knowledge by the information owner and can freely be
given to anyone without any possible impact to [Clients]. As a result, no special data handling protections are
required.
Page 24
3.2.2 Security Roles (Profiles and Authorizations)

Security Requirements for Workflow
Security Type
Screen Level
Security
Field Level
Security
Button Security
Data Security
Role
Transaction based
Access Allowed
read, read/update
N/A
N/A
N/A
3.2.2.1 Table Security (if applicable)

Custom Table
Authorization Group
N/A
3.2.2.2 ABAP Program Security (if applicable)

Value
N/A
Transaction Code
Process Step
Business Process Role
N/A
Data set /
Functionality
Describe what authorization a User must be assigned to access the

data set or functionality
N/A
3.3
Audit
Audit Trail Requirements
Audit Event
N/A
Description
Audit Trail Updates
Page 25
3.4 Questions / Issues / Risks

Questions/Issues/Risks
Asked By
Question/Issue/Risks
Resolution
Resolution
Date
Page 26

FSD PTP F031 Material Label 05-13-2014 SO

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FSD PTP F031 Material Label 05-13-2014 SO

Uploaded by

Copyright:

Available Formats

SAP Form Functional

OBJECT REQUIREMENTS SUMMARY...................................................................4

FORM DESIGN DETAILED SPECIFICATIONS........................................................8

OBJECT INFORMATION AND ATTRIBUTES.................................................................4

UNIT TEST PLAN.................................................................................................14

Business Process Organizational Structure

1 OBJECT REQUIREMENTS SUMMARY

Object Information and Attributes

The following is current information about this object and document:

146 - FSD_PTP_F031_Material Label

Requirements Summary and Business Driver

2. The material label should include

All the data for material labels exist in SAP

Project / Development Constraints

Frequency per Peak:

5 People per Location (ALC, AMI East, AMI

Expected Average Response

Other Objects Affected

2 FORM DESIGN DETAILED SPECIFICATIONS

(4 x 2.875) and have the same font as the sample

Data Selection-Screen / Criteria:

Scenario 1 ( The most common scenario)

Material Document Number

Mat Doc Itm #

Mat doc Item #

Mat. Doc. year MKPF

Material doc. Year

Serial Number EQUI

User desired value up to 999

Label printer on SAP network

Label Output Layout:

Refer section 1.9 and the

Heres the logic to use:

User Input in selection

Quantity Barcode Convert value of number in

The user shall input this

Refer section 1.9 and the

Material Barcode Convert MSEG-MATNR to

Quantity Barcode Convert value of number in

Heres the logic to use:

Additionally, mention the following:

2.1 Form Other Information

Business Rules / Algorithm For This Transformation

Other Updates Performed During Processing Not Specified Above

Rules For Update

Other Form Requirements (Not Specified Elsewhere in This Document)

1.1 Printing / Media Requirements:

Label with adhesive

1.2 Error Handling Method:

Rules For Handling Failure

Resolve issue with technical team

Error Handling Requirements

Range check validation errors on screen inputs will be logged on

1.3 Post Execution Notification Details:

1.4 Process Log Details

Scope of Testing (Inside

Target Test Date

Identity & Access Management

List the 3rd

SHR data transmitted?

SHR data stored and transmitted?

Confidential data transmitted?

Confidential data stored and

Level 3 Internal [Clients] Use Only