Clientele/SAP Interface

System Software Requirements

Table of Contents

1.introduction

1.1.Document Objectives

1.2.Document Scope

1.3.References

1.4.Special Issues

1.5.Acronyms

2.Requirements

2.1.Problem Context

2.2.Requirements Representation

2.3.Project Objectives and Scope

2.4.Detailed Requirements

2.4.1.Inputs

2.4.2.Internal and External Interfaces

2.4.3.Functional Requirements

2.4.4.Data

2.4.5.Error Handling

2.5.Traceability

1.introduction

1.1.Document Objectives

The purpose of this document is to outline and define the System Software Requirements that address the development of a new interface which will facilitate the passing of data between existing Boston Scientific Neuromodulation (BSN) Systems and SAP. The intent of this document is to identify and describe the software requirements that are necessary to support the business processes as describe in the document, BPR-SAP Interface. Further more, this System Software Requirement (SSR) is for the design, development, implementation as well as testing and validation of the SAP Interface.

1.2.Document Scope

The scope of this document is limited to the features and functionality associated with the SAP Interface for Clientele.

1.3.References

Document Number / Title
90514734 / NMSIP Program Plan
90518751 / SAP Interface Business Process Requirement
90343104 / GSM Requirements Specification Template

1.4.Special Issues

This document is limited to processes at BSN and does not apply to other legacy BSC systems or processes.

1.5.Acronyms

  • CSVComma Separated Values
  • EAI Enterprise Application Integration
  • ERPEnterprise Resource Planning

2.Requirements

2.1.Problem Context

BSN has several systems which are used and currently interface with the DataFlo ERP application. Due to the implementation of SAP, these outside systems must have the ability to exchange data with SAP. Currently there is no interface which will allow for the passing of data with SAP, hence, an interface must be developed. By developing this interface, it will ensure the data in these other systems has the ability to be captured and stored in SAP.

2.2.Requirements Representation

Requirements for this project are specified in the Detailed Requirements section of this document. The requirements are separated by business processes and each business process contains their associated requirements. Each requirement has a unique identifier and requirement description.

The requirement attributes used are as follows:

  • Business Process
  • Requirement ID (Unique Identifier)
  • Requirement Description

2.3.Project Objectives and Scope

The objective of this project is to develop an Interface which facilitates the passing of data between Clientele and SAP.

This project scope is limited to the implementation of the SAP Interface for the overall SAP Project.

2.4.Detailed Requirements

The Clientele application manages the database for tracking and follow up of Pre-surgical Authorizations for Implantable Devices and Procedures and also for the pre-authorizations for the SCS replacement supplies and accessories. This interface is unidirectional from SAP to the Clientele application.

2.4.1.Inputs

2.4.1.1SAP shall have the ability to generate a SurgicalCenter file which meets the following conditions:

2.4.1.1.1SurgicalCenter is Boston Scientific Neuromodulation specific

2.4.1.1.2Customer Type Group is valid (e.g., educational institution, surgical center)

2.4.1.1.3Customer Type is not Sales Rep or BSN employee

2.4.1.1.4Country = “USA”, “Canada”, “Mexico”

2.4.1.1.5Customer Record has been updated since the last processing cycle

2.4.1.2SAP shall have the ability to generate a SurgicalCenter file containing the following fields:

2.4.1.2.1Unique Surgical Center ID (type = alphanumeric; length = 25)

2.4.1.2.2Name (type = alphanumeric; length = 40)

2.4.1.2.3Address 1 (type = alphanumeric; length = 50)

2.4.1.2.4Address 2 (type = alphanumeric; length = 50)

2.4.1.2.5City (type = alpha; length = 20)

2.4.1.2.6State (type = alpha; length = 20)

2.4.1.2.7Postal Code (type =alphanumeric; length = 10)

2.4.1.2.8Country (type = alpha; length = 20)

2.4.1.2.9Phone Number (type = alphanumeric; length = 20)

2.4.1.2.10Fax Number (type = alphanumeric; length = 20)

2.4.1.2.11Inactive Flag (type = alpha; length = 2)

2.4.1.2.12Product Division (type = alphanumeric; length = 3)

2.4.1.3SAP shall have the ability to generate a Surgical Center Role file which meets the following conditions:

2.4.1.3.1SurgicalCenter is Boston Scientific Neuromodulation specific

2.4.1.3.2Customer Type Group is valid

2.4.1.3.3Customer Type is not Sales Rep or BSN employee

2.4.1.3.4Country = “USA”, “Canada”, “Mexico”

2.4.1.3.5Customer Record has been updated since the last processing cycle

2.4.1.4SAP shall have the ability to generate a Surgical Center Role file containing the following fields:

2.4.1.4.1Unique Surgical Center ID (type = alphanumeric; length = 25)

2.4.1.4.2Role (type = alpha; length = 50)

2.4.1.4.3Product Division (type = alphanumeric; length = 3)

2.4.1.5SAP shall have the ability to generate a Medical Professional file which meets the following conditions:

2.4.1.5.1Medical Professional is Boston Scientific Neuromodulation specific

2.4.1.5.2Country = “USA”, “Canada”, “Mexico”

2.4.1.5.3Customer Type Group = medical professional

2.4.1.5.4Customer Type is not Sales Rep or BSN employee

2.4.1.5.5Customer Record has been updated since the last processing cycle

2.4.1.6SAP shall have the ability to generate a Medical Professional file containing the following fields:

2.4.1.6.1Unique Medical Professional ID (type = alphanumeric; length = 25)

2.4.1.6.2First Name (type = alphanumeric; length = 45)

2.4.1.6.3Last Name (type = alphanumeric; length = 45)

2.4.1.6.4Credentials (type = alphanumeric; length = 15)

2.4.1.6.5Address 1 (type = alphanumeric; length = 50)

2.4.1.6.6Address 2 (type = alphanumeric; length = 50)

2.4.1.6.7City (type = alphanumeric; length = 20)

2.4.1.6.8State (type = alphanumeric; length = 20)

2.4.1.6.9Postal Code (type = alphanumeric; length = 10)

2.4.1.6.10Country (type = alphanumeric; length = 20)

2.4.1.6.11Phone Number (type = alphanumeric; length = 20)

2.4.1.6.12Fax Number (type = alphanumeric; length = 20)

2.4.1.6.13Email Address (type = alphanumeric; length = 80)

2.4.1.6.14Status (type = alphanumeric; length = 3)

2.4.1.6.15Product Division (type = alphanumeric; length = 3)

2.4.1.7SAP shall have the ability to generate a Medical Professional Role file which meets the following conditions:

2.4.1.7.1Medical Professional is Boston Scientific Neuromodulation specific

2.4.1.7.2Country = “USA”, “Canada”, “Mexico”

2.4.1.7.3Customer Type Group = medical professional

2.4.1.7.4Customer Type is not Sales Rep or BSN employee

2.4.1.7.5Customer Record has been updated since the last processing cycle

2.4.1.8SAP shall have the ability to generate a Medical Professional Role file containing the following fields.

2.4.1.8.1Unique Medical Professional ID (type = alphanumeric; length = 25)

2.4.1.8.2Role (type = alphanumeric; length = 50)

2.4.1.8.3Product Division (type = alphanumeric; length = 3)

2.4.1.9SAP shall have the ability to generate a Patient file which meets the following conditions:

2.4.1.9.1Patient is Boston Scientific Neuromodulation specific

2.4.1.9.2Customer Type Group = Patient

2.4.1.9.3Country = “USA”, “Canada”, “Mexico”

2.4.1.9.4Customer Type is not Sales Rep or BSN employee

2.4.1.9.5Customer Record has been updated since the last processing cycle

2.4.1.10SAP shall have the ability to generate a Patient file containing the following fields:

2.4.1.10.1Unique Patient ID (type = alphanumeric; length = 25)

2.4.1.10.2First Name (type = alphanumeric; length = 25)

2.4.1.10.3Last Name (type = alphanumeric; length = 20)

2.4.1.10.4Address 1 (type = alphanumeric; length = 50)

2.4.1.10.5Address 2 (type = alphanumeric; length = 50)

2.4.1.10.6City (type = alphanumeric; length = 20)

2.4.1.10.7State (type = alphanumeric; length = 20)

2.4.1.10.8Postal Code (type = alphanumeric; length = 10)

2.4.1.10.9Country (type = alphanumeric; length = 20)

2.4.1.10.10Email Address (type = alphanumeric; length = 80)

2.4.1.10.11Phone Number (type = alphanumeric; length = 20)

2.4.1.10.12Gender (type = alpha; length = 6)

2.4.1.10.13Date of Birth (type = date; length = 10)

2.4.1.10.14Surgeon ID (type = alphanumeric; length = 32)

2.4.1.10.15Care Center ID (type = alphanumeric; length = 25)

2.4.1.10.16Inactive Flag (type = alphanumeric; length = 3)

2.4.1.10.17Product Division (type = alphanumeric; length = 3)

2.4.1.11SAP shall have the ability to generate a Patient Role file which meets the following conditions:

2.4.1.11.1Patient is Boston Scientific Neuromodulation specific

2.4.1.11.2Customer Type Group = Patient

2.4.1.11.3Country = “USA”, “Canada”, “Mexico”

2.4.1.11.4Customer Type is not Sales Rep or BSN employee

2.4.1.11.5Customer Record has been updated since the last processing cycle

2.4.1.12SAP shall have the ability to generate a Patient Role file containing the following fields:

2.4.1.12.1Unique Patient ID (type = alphanumeric; length = 25)

2.4.1.12.2Role (type = alphanumeric; length = 50)

2.4.1.12.3Product Division (type = alphanumeric; length = 3)

2.4.1.13SAP shall have the ability to pass the file to an intermediate location where they are available to the Clientele import process.

2.4.2.Internal and External Interfaces

2.4.2.1.The Clientele Application Interface shall have the ability to communicate with the EAI WebSphere middleware.

2.4.3.Functional Requirements

2.4.3.1.The unidirectional interface shall use a push model when sending data from SAP to Clientele. This will start at 11:00 PM Monday through Friday.

2.4.3.2.In order to minimize the risk by not changing the existing structure on the application side, the processing cycle for importing the Clientele data files will happen in three stages starting at the specified times:

2.4.3.2.1.Center and Center Roles are at 2:45 AM Tuesday through Saturday.

2.4.3.2.2.Medical Professional and Medical Professional Roles are at 3:05 AM Tuesday through Saturday.

2.4.3.2.3.Patient and Patient Roles are at 3:15 AM Tuesday through Saturday.

2.4.4.Data

2.4.4.1The files outlined in the previous requirements are Tabbed Delimited file format.

2.4.5.Error Handling

2.4.5.1The EAI interface shall trap the followingtypes of errors:

2.4.5.1.1Adapter error – errors out on when trying to create the file from the incoming message.

2.4.5.1.2Internal flow error – errors out when trying to build the message.

2.4.5.1.3iDoc error – errors out when trying to process the incoming iDoc.

2.5.Traceability

The SAP Interface project is rated as medium. Traceability of BPR to SSR to test cases shall be documented.

Boston Scientific

Clientele/SAP Interface Requirements Specification

90529255 Rev/Ver. AB

Page 1 of 8