Interface Agreement Document

– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

Integration: OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS

Table of Contents
Revision History..................................................................................................................................................................... 2
Reference/Contact Information............................................................................................................................................2
Review / Sign-off...................................................................................................................................................................2
Description............................................................................................................................................................................ 4
Context Diagram...................................................................................................................................................................4
Integration Summary............................................................................................................................................................4
Source System Overview...................................................................................................................................................4
Middleware.......................................................................................................................................................................5
Target System Overview....................................................................................................................................................5
Assumptions......................................................................................................................................................................6
Processing Type.................................................................................................................................................................6
Triggers.............................................................................................................................................................................. 6
Frequency.......................................................................................................................................................................... 6
SLA Requirements and Performance.................................................................................................................................6
Delivery Sequence / Interface Flow...................................................................................................................................6
Expected Volumes.............................................................................................................................................................7
System Availability............................................................................................................................................................7
Data Retention..................................................................................................................................................................7
Error Processing............................................................................................................................................................7
Acknowledgement and Notification..............................................................................................................................8
Audit Processes.................................................................................................................................................................8
Foreign Language Support /..............................................................................................................................................8
Functional Specification Mapping.................................................................................................................................8
Filtering......................................................................................................................................................................... 9
Conversion....................................................................................................................................................................9
Security......................................................................................................................................................................... 9
Risks.............................................................................................................................................................................. 9
Acceptance Criteria.......................................................................................................................................................9
Legacy Integration Obsolescence..................................................................................................................................9

Page 1 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

Revision History
Version Date of Revision Description of Change Affected Section(s) Approved By
1.00 07/29/2014 Original Version All Sections Tony Crisci

Reference/Contact Information
Master EA1382.02
Integration
#:
Project Impact 2017
Name:
... RICEFW http://teamsite.inside.pb.com/sites/GlobalERP/Lists/RICEFW%20Inventory%20Tracker/DispForm.aspx?
Number: ID=229

Existing TD https://teamsite.inside.pb.com/sites/EDSS/EAT/Middleware%20Documents/Integrations/
for Canada TechnicalDesigns(TD)/OTC_I_0229_TD_EA1382.01_SAP_Draft5_to_TSYS.docx
deployment
... http://teamsite.inside.pb.com/sites/GlobalERP/Deliverables/Design/Functional%20Designs/OTC%20-
Functional %20Order%20to%20Cash/OTC_I_0229_FD_SAP%20to%20TSYS%20Draft5.docx
Design:
Contacts (Name/Email Id):
Functional Designer Alisa Moore, Judy Walsh
Technical Designer TBD
Legacy Designer Chuck Brainard
Middleware Designer TBD
Process lead - PB Thomas Coon
Process lead - ACN Keith Stone
IT Lead – PB Tom Kerr
Sub-Process Business Lead Linda Lonergan
Billing
Sub-Process IT Lead A/R Alisa Moore
Sub-Process Business Lead A/R Ed Dryoff

Review / Sign-off
Functional Designer Alisa Moore, Judy Walsh
Page 2 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

Technical Designer TBD

Legacy Designer Chuck Brainard
Middleware Designer Tony Crisci
Process lead - PB Thomas Coon
Process lead - ACN Keith Stone
IT Lead – PB Tom Kerr
Sub-Process Business Lead Linda Lonergan
Billing
Sub-Process IT Lead A/R Alisa Moore
Sub-Process Business Lead A/R Ed Dryoff

Page 3 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

Description
This document describes the topology and attributes for sending SAP Accounts receivables and other files to the TSYS for
providing select PB customers with one consolidated TSYS monthly statement.
This integration is being developed in order to meet the Impact 2017 project business requirements.

PER CR 702 – this service is being significantly re-written. An RFC will no longer be used and SAP RFC function will be
replaced by file pass through SPARC processing.
This IA addresses three files (1-U.S. and 1-Canada) sent from the new Global SAP instance to TSYS. More files will be
included for Impact release 2 - EAME Draft5 and is addressed in IA :
https://teamsite.inside.pb.com/sites/EDSS/EAT/Middleware%20Documents/Integrations/InterfaceAgreements(IA)/
IA_EA1382.03_OTC_I_0229_SAPECC_Draft5_To_TSYS.docx

From FD
Two Global SAP files:
Data Type TransID TransDesc
Rentals – U.S. I3698DF9 EQUIP1
Rentals – Canada I4698PEB PEBRAS
Billing – U.S. I3698SAP 36SAPA

We have to accounted for transaction description = 36SAPA in the CR.

Page 4 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

Context Diagram

Integration Summary
This document contains the general process of sending the SAP Accounting Invoice information in the form of a DRAFT5
TSYS file. This agreement covers the architecture for U.S. and Canada. The EAME design is detailed in another IA
referenced below.

Flow overview:
1. SAP places two draft5 files (U.S. and Canada) in the SAP application server (/sapio
2. SPARC will pull the files and generate the file and the appropriate TSYS JCL for TSYS
3. SPARC runs a scheduled script to send of FTP (VPN) to TSYS

Page 5 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

Error: Reference source not found

Source System Overview

<Source Application> to <Middleware-Component>

Application Name: SAP Global ERP
Application Type: ERP Application, Internal to Pitney Bowes Infrastructure
Security: Middleware Adapter is registered with SAP
SAP Global ERP is the new SAP instance in support of the Impact-2017 project, supporting all countries and the ECC
business suite.

SAP File and Folder

We will need to segregate US and Canada files by separating by file names. Confirmed with SAP team.:

/sapio/outbound/TSYS
/sapio/outbound/TSYS/backup.

1. The file naming pattern for US Billing will be: TSYS_SAP_ADJUST_US_DATE_TIME (ex.
TSYS_SAP_ADJUST_US_20160209_095345)
2. The file naming pattern for US will be: TSYS_FILE_US_DATE_TIME (ex. TSYS_FILE_US_20160209_095345)
3. The file naming pattern for Canada will be: TSYS_FILE_CA_DATE_TIME (TSYS_FILE_CA_20160209_095345)
Error: Reference source not found

Middleware
SPARC is the standard middleware solution for file-transfer integrations.

<Middleware-Component> to <Middleware-Component>
Application Name: SPARC
Application Type: Enterprise File Manager.
Security: Data is protected only during transit via MQ (from WBI) using
internal server security measures. For calls to targets – uses sFTP or
PGP encryption

Target System Overview

<Middleware-Component> to <Target-Application>
Application Name: TSYS
Application Type: External Bank
Security: FTP using PGP encryption
Page 6 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

Error: Reference source not found

Assumptions
1. There is no sensitive data – encryption at rest is not required.
2. No transformation requirements
3. SAP will provide separate files for U.S. and Canada
Error: Reference source not found

Reuse
The current EAME SPARC scripts will remain until Release 2 – EAME is deployed.

Processing Type

File Pass-through- SAP will provide files of U.S. and Canadian TSYS Draft5 files to TSYS.

Error: Reference source not found

Triggers
This integration is to be scheduled.
Error: Reference source not found

Frequency
Daily
Error: Reference source not found

SLA Requirements and Performance

This integration must deliver its content within 5 minutes of the process being triggered (as defined above), assuming no
errors occur. In the event of any errors, an ADM alert must be generated within that same 5-minute timeframe, and a
full resolution to the underlying issue must be identified and fully resolved within a 50 minute period from the time the
process was first triggered.
Error: Reference source not found

Delivery Sequence / Interface Flow

SAP to TSYS
1. SAP will initiate the process by placing DRAFT5 files on their application server.
2. A SPARC Get File process will pull the U.S. and Canadian files.
3. This script will invoke the standard Q2FTP SPARC service to send to TSYS.
4. Upon successful transfer to TSYS, the file is moved to the backup directory; else it is moved
to the error directory.
5. The necessary JCL file is also sent to TSYS to process the DRAFT5 File.

Error: Reference source not found

Page 7 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

System Availability
The middleware system is available on a 24x7 basis year round, with no planned down-time.
Error: Reference source not found

Data Retention
Follow SPARC standards for Daily schedule (14 days) file processing.
Error: Reference source not found

Error Processing
If any error occurs during the standard scheduled processing of the middleware integration on a given day, an
automated alert will be delivered to the middleware ADM team for investigation of the root cause of the issue. This may
require the team to contact the SAP ADM team to determine if any SAP File problem may have existed that prevented
middleware from obtaining the files on their server. There may also be a need to contact TSYS support (Chuck Brainard)
in the event that the TSYS server is unavailable. If the FTP transfer fails, ADM my need to contact TSYS,
In the event of any such problem, it is required that the problem be identified and resolved within the SLA agreed upon
for Remedy Incidents.
The resolution of this problem must be achieved within the SLA determined fir Remedy incident tickets.
 Error handling and RCA for failed calls should follow normal EAI procedures for file handling.
 When the target is unavailable, store the file in the /error folder and replaying once it is up.
 In case of validation error, an email should be sent to ADM team and message is to be placed in the error queue.
 If the target is up and target rejects the FTP post for any reason, then
o An email should be sent to ADM team and file placed in error folder -

Error: Reference source not found

Failure Points
No. Possible Failure Point Impact and Cause Rules for Handling Failure
1. File failure from SAP Sap file cannot be ADM alert and incident resolution
retrieved from the SAP
server.
2. File generation failure SPARC fails to generate ADM alert and incident resolution
JCL for file transmission
3. File transmission failure to TSYS FTP file transmission error ADM alert and incident resolution

Acknowledgement and Notification

No automated e-mail notification should be sent to business for success or failures. Error notification will be sent to
ADM production support.
Error: Reference source not found

Audit Processes
There are no audit processes or requirements for this integration, and no historical or audit information will be made
available with respect to the execution or completion of this integration.

Page 8 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

Error: Reference source not found

Foreign Language Support /

Middleware shall provide support for character set translations and data transformations as part of this integration.
Error: Reference source not found

Functional Specification Mapping

N/A – no transformation requirements

-------------------------------------------------------------------------------------------------------------------------------------------

Transaction descriptions, conversion and JCL and file outputs

Design must generate TSYS files based on the transaction description as follows:

Scripting File Name

DRAFT5 Transacti Transaction Convers
DESCRIPTION on ID Description ion Rule
SAPECC_DRAFT5_CABill_to_TSYS_ 'IQP040.FTPI.FTP2969.I
MQ2FTP.sh 4694DF6(+1)'
Canadian SAPECC_DRAFT5_CABill_to_TSYS.
jcl
Rentals
(Currently in
PRODUCTION
) I4694PEB PEBRAS NONE
TSYS_DRAFT5_PPRENTALS_Q2F.xml 'IQP040.FTPI.FTP3
698.I3698DF9(+1)'
TSYS_IMS_DRAFT5.jcl
(rename to
TSYS_SAPECC_EQUIP1_DRAFT5.jcl

IMS/ I3698DF
PPRENTALS 9 EQUIP1 NONE
SAP/BILLING I3698SAP 36SAPA NONE SAPECC_DRAFT5_BILLING_to_TSYS 'IQP040.FTPI.FTP2969.I
_MQ2FTP.sh 3698SAP(+1)'
SAPECC_DRAFT5_BILLING_to_TSYS
_MQ2FTP.jcl

Page 9 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

Sample files to TSYS

Impact version of U.S. feed is under development – please review TD reference

Conversion
N/A
Error: Reference source not found

Security
Data is secured via ruse of SecureFTP and FTP via a VPN.
Error: Reference source not found

Risks
Raised By Risk Date Needed Resolution/Answer Date Completed Resolved By
None

Error: Reference source not found

Acceptance Criteria
Acceptance criteria are based on successful project completion of formal project test cases.
Error: Reference source not found

Legacy Integration Obsolescence

Canada Go-Live feed that should have been obsoleted.

Canada OP
CABILL_OP_TSYS_PEBDRAFT5_Q2FTP.xml
TSYS_PEBS_DRAFT5_CCACCOUNTS_Q2FTP.xml
TSYS_DRAFT5_CCACCOUNTS_Q2F.xml

The Canadian Feed through an RFC was deployed as part of the Impact Canadian release – however this RFC feed will
now be replaced by a File feed from SAP.

Page 10 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

U.S. Go-Live
PER CR701 -- Today the current SAP/PR1 instances send U.S. RFC messages and will be replaced by the new Global SAP
file transmission. Also all IMS feeds will be obsoleted.

IMS
TSYS_DRAFT5_PPINVOICE_Q2F
TSYS_DRAFT5_PPRENTALS_Q2F
TSYS_DRAFT5_PP_PARTS_Q2F

SAP
TSYS_DRAFT5_BILLING_SAP_To_TSYS_Q2F
TSYS_DRAFT5_SUBSCRIPTION_Q2F
TSYS_DRAFT5_SUPPLYLINE_Q2F

Obsoleting list
Obsol JCL File Name
ete
*Note for
Curre DEV
nt replace
SYSTE Transaction “IQP’ with
M DRAFT5 DESCRIPTION Transaction ID Description Conversion Rule IQV’
/mw/ 'IQP040.FT
webmp/ PI.FTP3698.
bin/
TSYS_SAP I3698DF1(+
_DRAFT5. 1)
36SAPA, 36SAPR, jcl
36WPSP, LOCKBX
SAP/SUPPLY_LINE - convert to
SAP (Supply Line Monetary) I3698DF1 LOCKBX IBMMON
X /mw/ 'IQP040.FT
webmp/ PI.FTP3698.
bin/
36SAPA, 36SAPR, TSYS_SAP I3698DF1(+
36WPSP, LOCKBX _DRAFT5. 2)
- convert to jcl
SAP SAP/SUBSCRIPTION I3698DF5 36SAPR IBMMON
X SAP SAP/BILLING I3698SAP 36SAPA 36SAPA, 36SAPR, /mw/ 'IQP040.FT
36WPSP, LOCKBX webmp/ PI.FTP2969.
bin/
- convert to TSYS_SAP I3698SAP(+

Page 11 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

_DRAFT5_ 1)'
BILLING.
IBMMON jcl
/mw/ 'IQP040.FT
webmp/ PI.FTP4694.
bin/
TSYS_OPC I4694DF8(+
CANA ANADA_DR 1)'
DAOP PWORKS - Supplies I4694DF8 CANSUP NONE AFT5.jcl

'IQP040.FT
PI.FTP2969.
CANA I4694DF6(+
DAOP PWORKS - PEB I4694PEB 4CDNPS NONE 1)'
/mw/ 'IQP040.FT
webmp/ PI.FTP2969.
bin/
TSYS_OPC I4694DF6(+
ANADA_PE 1)'
BS_DRAFT
5.jcl
CANA
DAOP PWORKS - PEB I4694PEB PEBRAS NONE
X /mw/ 'IQP040.FT
webmp/ PI.FTP3698.
bin/
TSYS_SAP I3698DF1(+
_DRAFT5. 1)'
jcl
IMS IMS/PPINVOICE I3698DF9 SLMDF5 NONE
/mw/ 'IQP040.FT
webmp/ PI.FTP3698.
bin/
TSYS_IMS I3698DF9(+
_DRAFT5. 1)'
jcl
IMS IMS/PPRENTALS I3698EMA 296EMA NONE
X /mw/ 'IQP040.
webmp/ FTPI.FTP
bin/ 2969.I36
TSYS_IMS 98PAR(+1
_DRAFT5_ )
PARTS.jc
l
IMS IMS/PARTS I3698PAR 36PTLR NONE
IMS IMS/PPRENTALS I3698DF9 EQUIP1 /mw/ 'IQP040.FT
webmp/ PI.FTP3698.
bin/
TSYS_IMS I3698DF9(+
_DRAFT5. 1)'

Page 12 of 13
 Interface Agreement Document
– OTC_I_0229_IA_EA1382.01 _SAP Draft5 to TSYS Version 1.0

jcl

Page 13 of 13