SAP Form Functional Specification FSD_PTP_F031_Material Label

SAP Form Functional Specification FSD_PTP_F031_Material LabelARTHREX

Table of Contents

1OBJECT REQUIREMENTS SUMMARY41.1Object Information and Attributes41.2Requirements Summary and Business Driver41.3Assumptions41.4Current Functionality41.5Required Functionality51.6Project / Development Constraints51.7Performance Criteria51.8Other Objects Affected51.9External References61.10Definitions/Acronyms/Abbreviations62FORM DESIGN DETAILED SPECIFICATIONS82.1 Detail Requirements:82.2Data Selection-Screen / Criteria:82.3Form Output Layout:82.4Form Other Information92.5Printing / Media Requirements:102.6Error Handling Method:112.7Post Execution Notification Details:142.8Process Log Details143ADDITIONAL INFORMATION143.1Unit Test Plan143.2Information Security163.3Audit193.4Questions / Issues / Risks19

Business Process Organizational StructurePTP

Process OwnerRich Hughes

Original Author(s)Melissa Jeng

Current Revision Author(s)Prakash P

VersionDateAuthor(s)Revision Notes

0.1Feb 8 2014Melissa JengInitial Draft

0.2Mar 25 2014Melissa JengContent

0.3Mar 27 2014Prashanthi BolluConfiguration steps

0.4Apr 8 2014Melissa JengFormat layout

0.5Apr 11 2014Prakash PTable-field mapping/logic addedEnhancement details with selection screen added.

0.6Apr 12 2014Dimitri KoutsourasReview

0.7Apr 27 2014Prakash PUpdates as advised by Rich H in FDS approval meeting on 04/16/2016

OBJECT REQUIREMENTS SUMMARY

Object Information and Attributes

Req No.Requirement DescriptionGXP(Yes/No)Risk(H/M/L)Probability(H/M/L)

URS.4.5.1.1.0010Ability to receive materials with vendor batch number as the SAP batch numbersN

URS.4.5.1.1.0020Ability to receive serialized materialsN

URS.4.5.1.1.0050Ability to create a transfer order for received materials going to stock based on business rules. (create transfer order but do not confirm transfer order)N

The following is current information about this object and document:

Object ID146 - FSD_PTP_F031_Material Label

TitleFSD_PTP_F031_Material Label (Material, Quantity, Batch, Serial Number, SLED)

Author(s)Melissa Jeng

Team Which Owns the ObjectPTP

System VersionECC 6.0

Development TypeForm

PriorityHigh

Estimated ComplexityMedium

Link to Process FlowFDD_PTP_4.5.1.1_WM Inbound Process

FTM Team Validation Required|_| Yes |X| 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.

2. The material label should include a. Material,b. Material Descriptionc. 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)

.

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.

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.

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.

Assumptions

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 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:

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 interface2. 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 transaction2. A Custom Print Program3. 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.

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 isAssigned a serial number profile by checking if the a valid value of serial number profile exists (Table /Field MARC-SERNP)

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.

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 MSC3NDriver Program Logic:1. Pass the material number and Batch to MCH1 table2. 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 moduleTo perform validation technically.

The print program is then required to print the material labels the same way as it does for scenario 1.

Project / Development Constraints

All warehouse management and goods receipt configuration needs to be completed prior to testing this transaction.

Performance Criteria

Performance Requirements for Forms

Average Frequency: 5/MinuteMinute

Frequency per Peak:10/Minute5 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:Sub-second

Expected Peak Response Time:1 Second

Other Objects Affected

ObjectImpact/Change Description

N/A

SAP SystemSAP ModuleImpact/Change Description

N/A

NON-SAP / Legacy SystemImpact/Change Description

N/A

Dependencies:Dependent Configuration:N/A

External ReferencesDocument TitleAuthorAttachment / Links

Graphic IdentifyArthrex

Definitions/Acronyms/AbbreviationsWM Warehouse ManagementGR Goods ReceiptFDD Functional Design DocumentUT Unit TestSLED Shelf Life Expiration Date

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 (4 x 2.875) and have the same font as the sample form below.

0. 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.Field NameTable Field / Checkbox / Radio ButtonSelect-Option (S) or Parameter (P)Comments (Range, Single/Multiple Selection, Patterns, Mandatory, etc.)Validations (For Each Field if any)Default Value

Material MSEGMATNRMaterial NumberScenario 1:Populated by system based on the material document number & Item number combination scanned/entered by user. The user should visually verify this data.

Material DocMKPF MBLNRMaterial Document NumberEntered by user using RF device or manuallySystem validation required

Mat Doc Itm # MSEG ZEILEMat doc Item #Entered by user using RF device or manuallySystem validation needed.

Mat. Doc. yearMKPFMJAHRMaterial doc. YearDefault value Current year.This field may be hidden for user interface

Serial NumberEQUISERNRSerial # This is a display field only. The system populates value Yes in this field if material has a serial number profile assigned to it. Pass Material document no to SER03 table to get SERNR) (serial numbers.)

Quantityn.an.aUser desired value up to 999Number should be less than 999This field is populated with value 1 if the materials having serial number profile (MARC-SERNP not equal to blank

PrinterLabel printer on SAP network

0. 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 LayoutTable NameField NameField DescriptionConditions / Data Retrieval LogicMaximum Number of Characters to print

1N/AN/ALogoRefer section 1.9 and the logo in the Arthrex label currently used ( sample provided)

2MSEGMATNRMaterial NumberDefaulted by system from Material document #, item number and current year18

3MAKTMAKTGMaterial DescriptionPass MATNR to MAKT table and get MAKTG 40

4MAKTMATNRMaterial BarcodeConvert MSEG-MATNR to bar code format using EAN 128 standard

5MSEGCHARGBatch (Lot) NumberFrom MSEG table.10. If longer, truncate the value

6MSEGCHARGBatch BarcodeConvert MSEG-CHARG to bar code format using EAN 128 standard

7MSEGVFDATShelf life expiration date10

8CAWNATWRTRevision NoHeres 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.

8N.AN.AQuantityUser Input in selection screenScenario 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

9Quantity BarcodeConvert value of number in row # 8 to bar code using EAN128 standard

10EQUISERNRSerial NumberThe user shall input this number.

The system should validate the number by using Function Module GET_SERNOS_OF_DOCUMENT (Pass goods receipt Document # to the function module as MBLNRMJAHR - 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 LayoutTable NameField NameField DescriptionConditions / Data Retrieval LogicMaximum Number of Characters to print

1N/AN/ALogoRefer section 1.9 and the logo in the Arthrex label currently used ( sample provided)

2MSEGMATNRMaterial NumberEntered by user18

3

3MAKTMATNRMaterial BarcodeConvert MSEG-MATNR to bar code format using EAN 128 standard

4MSEGCHARGBatch (Lot) Number10. If longer, truncate the value

5MSEGCHARGBatch BarcodeConvert MSEG-CHARG to bar code format using EAN 128 standard

6MSEGVFDATShelf life expiration dateMM/DD/YYYY format10

7N.AN.AQuantityUser Input in selection screenIf serial number is required to be printed the allowed value is 1.If different, return suitable error message

8Quantity BarcodeConvert value of number in row # 8 to bar code using EAN128 standard

10SER03SERNRSerial NumberThe user shall input this number.

The system should validate the number by using Function Module GET_SERNOS_OF_DOCUMENT (Pass goods receipt Document # to the function module as MBLNRMJAHR - 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.

11AUSPATWRTHeres 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.

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

SAPScript / SMARTFORM / Adobe Form:(Mention the type of form)Smart Form

SAPScript / SMARTFORM / Adobe Form Name:PRODUCT_LABEL

Output Type:ET01

Print Program Name:RTLABEL0

Standard Text:N/A

Logo:(Attach as files)

Bar Codes (field names):TANUM

Language translation constraints:(List languages to be considered for form development)All SAP supported language. EN, DE etc.

Output Destination:(Check all that apply)|_| Hard Copy |_| EDI |_| FAX|X| Hard copy to a specific printer

Number of forms to print per run:1

IMG Configuration, if any:

Menu Path to Generate Form:

0.2 Form Other Information

Form Processing RequirementsCalculations / Transformations

Value to be DerivedBusiness Rules / Algorithm For This Transformation

N/A

Other Updates Performed During Processing Not Specified Above

Initiating EventUpdated InformationRules For Update

N/A

Other Form Requirements (Not Specified Elsewhere in This Document)

NumberDescription of Requirement

1. N/A

2.

0.3 Printing / Media Requirements:Output Device Name:(Mention the Output Device Name)LOCL

Number of Copies:(Mention number of copies to be printed)1

Spool Request Name:(Mention if any specific spool request name)TBD

Print Immediately:(Check the box if yes)|_|

Delete after Output:(Check the box if yes)|X|

New Spool Request:(Check the box if yes)|X|

Close Spool Request:(Check the box if yes)|_|

Paper FormatLabel with adhesive

Paper Size4 x 2.875

0.4 Error Handling Method:

Failure Points

Possible Point Of FailureRules For Handling Failure

Scanning, security, or connectivity issuesResolve issue with technical team

Transfer Order is not foundResolve issue with receiving management group

System does not allow entry of a given valueResolve issue with receiving management group

Material is not found or no quantity Resolve issue with receiving management group.

Error Handling Requirements

Information NeededDescription

Error DetectionRange 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.

Error NotificationContact COE help desk

Error Logging (beyond notification)None

Error Remediation

0.5 Post Execution Notification Details:N/A

0.6 Process Log DetailsN/A

ADDITIONAL INFORMATION

0.7 Unit Test Plan

Identify the Test Scenario to be used to test the development with:

Test ConsiderationsScope of Testing (Inside SAP (IS) / Outside SAP (OS) / Both (BO))Target Test Date

IS05-30-2014

0. Information Security

3.2.1 Information ClassificationGeneral Information

Businesses Impacted: Arthrex

Information Classified by whom:Rich HughesDate3/25/2014

Contact Information

CompanyNamePhoneE-mail Address

List PotentialInformation Owners:ArthrexRich Hughes,Rick KoharkiRichard.hughes@arthrex.com

Architecture

Environments: (impacted by this T spec):|X| Development |X| Test |_| Training |X| Production

Architecture: (system exposure):|_| Public (Internet) Facing |X| Internal Only|_| 3rd Party Hosted |_| Company * Hosted

Identity & Access Management

During Project3rd party system access required?|_| Yes|X| NoOffshore?|_| Yes|X| NoList the 3rd Parties:

Post Implementation3rd party system access required?|_| Yes|X| NoOffshore?|_| Yes|X| NoList the 3rd Parties:

Business Impact Analysis

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|X| Productivity|X| 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:

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? |_| Confidential data transmitted? |_| Confidential data stored and transmitted?

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

3.2.2 Security Roles (Profiles and Authorizations)

Security Requirements for Workflow

Security TypeRoleAccess Allowed

Screen Level SecurityTransaction basedread, read/update

Field Level SecurityN/A

Button SecurityN/A

Data SecurityN/A

3.2.2.1 Table Security (if applicable)Custom TableAuthorization Group

N/A

3.2.2.2 ABAP Program Security (if applicable)Value

N/A

Transaction Code

Process StepBusiness Process Role

N/A

Data set / FunctionalityDescribe what authorization a User must be assigned to access the data set or functionality

N/A

3.3 Audit

Audit Trail Requirements

Audit EventDescriptionAudit Trail Updates

N/A

3.4 Questions / Issues / Risks

Questions/Issues/Risks

Asked ByQuestion/Issue/RisksResolutionResolution Date

FSD_PTP_F031_Material Label Page 1

FSD_PTP_F031_Material Label Page 8

Section 1-1

GRAPHIC IDENTITY

The Arthrex brand image is not arbitrary. This section includes the graphic standards for the Arthrex logo, corporate color palette, guidelines on size and relationship to layout and samples of application.

Proper usage of these visual elements is key to maintaining a distinct and recognizable brand. Thus, it is extremely important that all corporate components adhere to these standards.

Section 1-2

Arthrex is the short term for Arthroscopic Excision Instruments. Reinhold Schmieding, the founder of Arthrex, Inc., designed the logo in 1981 and it has not changed from its original design.

The Logo design is comprised of the name Arthrex with the x becoming a ligature combining a symbolic, arthroscopic grasper and arthroscopic cannula. Arthrex holds the copyright on the name and logo, and therefore the symbol must be present in all applications.

Primarily the logo is printed in blue, black or silver, and in some cases may be reversed to white.

Arthrex Logo

Section 1-3

Size

The preferred size of the logo for the majority of Arthrex marketing materials is 2.25 (~5.715 cm) (216 pixels for website usage).

The absolute minimum width of the logo is 1.5 (~3.81cm, 112 pixels for Website usage), unless necessary and only if approved by Arthrex Marketing.

2.25 (~5.715 cm)

1.5 (~3.81 cm)

Section 1-4

BLUE

SILVER (METALLIC)

BLACK

WHITE

TITANIUM

Color Specifications

PMS 280

C M Y K

100 78 5 18 R G B 0 39 118

H E X 274583

PMS 0

C M Y K

0 0 0 100 R G B

39 36 37 H E X

272425

PMS 877C

PMS 0

C M Y K

0 0 0 0 R G B

255 255 255 H E X

ffffff

C M Y K

0 0 0 74 R G B 101 102 104

H E X 656668

PMS 8400C - TITANIUM

The color specifications of Arthrex color palettes are as follows:

Section 1-5

Blue Black

Silver White

CORPORATE

INFORMATIONAL

INTERFACE*

Logo Usage and Color Specifications

Corporate collateralcorporate brochures/web content/white papers/visual aides/identity package/signage/specialty collateral

Corporate advertising

Internal communication newsletters/email/econnect

e-marketing (external) collateral blog, etc.

Corporate collateralcorporate brochures/some informational (product) brochures/identity package/specialty materials

Informational/educational collateralsurgical techniques/brochures/catalogs/sell sheets/charts/white papers/visual aides/video

e-marketing collateral mobile applications/3D/iBooks

Advertising

e-marketing collateralmobile applications (Surgeon Media Application)

APPLICATIONS:

Blue Black

Silver White

Titanium

*use logo in this color only for a special project; approval must be a made by Marketing Department

Section 1-6

Correct Usage

BLUE Placement should be on white background only.

BLACK/WHITE/TITANIUM Design and color palette used in the individual marketing piece would dictate which of these three color options to use.Titanium may only be used on a black background, currently in e-marketing applications only, and only with the permission of Arthrex.

In all cases the Arthrex logo must be used against a solid white or neutral background. Avoid using the logo on an overly complex textured or a colored background that provides inadequate contrast.

The Arthrex logo must be used as flat artwork only. No animating, morphing, three-dimensional effects or other manipulation of the logo is permitted. Do not alter, modify, recreate or scan Arthrex artwork.

The Arthrex logo should always be reproduced in full color or in black and white. Color integrity in reproduction is important. Always match color swatches when printing or reproducing the logo.

Always use original camera-ready or electronic logo artwork as it is provided by the Marketing Department. It is preferred that the native format of the logo, which is .eps or .ai (Adobe Illustrator) be used. Should a .psd, .tif, .jpeg or .png file be needed please place your request with the Marketing Department at the actual size it

will be used. If there is a need for a large logo on a large graphic, always use the Adobe Illustrator file formats (.eps or .ai).

All originally created materials containing the Arthrex logo or name must be submitted for approval.

To request original artwork, logo artwork, approval or any other marketing material, please contact the Marketing Department at AskMarketing@Arthrex.com

Section 1-7

Company information

Never use the logo in any color other than PMS 280 blue, white, black, Pantone 8400 C (titanium)* or Metallic Pantone (silver) 877c Never stretch, rotate or distort the logo Never add embossing or apply filters/effects to the logo Never link or place any other image or typeface in front of the logo Never place the logo over a complicated or patterned background Never place the logo inside a box

Incorrect Usage

*use only for a special project, in high-contrast color application; approval must be a made by Marketing Department

Nos:

Section 1-8

CLEAR SPACEAlways maintain a minimum amount of clear space around the Arthrex logo to maintain its integrity and ensure optimal legibility.

The area of isolation is based on the height from the baseline to the part of the cannula. SEE DIAGRAM.

Layout Specifications

Section 1-9

ACTUAL CENTER

VISUAL CENTER

BALANCEIt is recommended that you reference the visual center when determining alignment of logo. The visual center is the right side of the vertical stroke of the r. Please make use of the white space diagram on the previous page for placement justaposed to other elements on the layout.

Layout Specifications

Section 1-10

Relationship to Other Logos

When the Arthrex logo is used in conjunction with other logos, it must appear at the same height. Always refer to the rules of the other logos, particularly when it comes to free space around the logo. As a rule, there should be sufficient space between each logo to distinguish one from the other and maintain brand integrity.

In cases where other logos appear in grayscale, the black version of the Arthrex logo must be used. Visual balance should be implemented to avoid an accompaning logo overpowering the Arthrex logo.

Material

Batch

MATERIAL #

1

2

3

MATL DESCRIP

LOT #

SERIAL NUMBER

9

Qty

mm/dd/yy

#

SLED

8

4

7

6

5

10

6

Batch

Batch

REV

REV 5

11

Sheet1Sr. No.RequirementTest Case NameTest TypeScript TypeDesignerDescriptionTest stepTest step descriptionExpected resultPass/FailGxPSubjectApproval StatusFI Verification1N/AUTP001_PTP_F030_WM Goods Receipt Form with Quality Inspection Lot and BarcodeManualUTpbolluName: UTP003_PTP_F031_WM Material label (Material, Quantity, Bach no, Serial No, Country of Origin and Self life expiration date)

FDD: 4.5.1.1

Objective: The objective of this test case is to perform a unit test to print a Material label (material, quantity, batch no, serial no, country of origin and self life expiration date) General Procedure: 1. Take and attach screenshots to the Screenshots tab, whenever required. 2. Attach to the test case any additional support documentation obtained during the execution of this test, as applicable. Insert as embed files into the Actual Results cell, if needed. 3. If the Actual Result is as the Expected Result answer "Pass" in the "Pass/ Fail" column; otherwise answer "Fail". Any discrepancies (Failed steps) should be rectified and marked as "Pass" before this script is accepted.

Prerequisites: 1. At least 2 materials have been created.2. A purchase order has been created.3. A goods receipt has been created.

Acceptance Criteria: The following general acceptance criteria apply to the overall acceptance of this Test Case: 1. All expected results are met or deviations are resolved or have workarounds that meet system requirements. 2. All corresponding test cases have been filled out and reviewed for accuracy by the appropriate reviewer. 3. All supporting documentation is attached to the test case.Step 1Login to SAP with assigned username and passwordUser is logged in successfullyNN/ADraftN/AStep 2Enter custom TcodePrint Material Label screen appearsStep 3Input required deails -Material -Material Document (Goods Receipt )-Material Document year ( default current year)-Serial Number ( if applicable)-quantity ( Qty per box)-Printer (Label printer on SAP network)-Click the checkmark to confirm.

-Click 'Execute'.The required labels get printed and message appears'Labels printed succesfully'Step 4Logout of SAP.User is logged out successfully.

Sheet2

Sheet3