Questionnaire for Cloud Adoption Services Engagement

Name: Diego Ordonez

Company Name: Leica Biosystems

Title: Salesforce Admin and Technical Architect

Email: diego.ordonez@leicabiosystems.com
Phone: +34 678 084 200

Primary Technical Contact: Email

Location/Time zone: Spain/CEST

Overview

 Software Installation Date: ASAP

 Development Start Date: ASAP

 Production Go-Live Date: TBD

 Business Objective:
Currently, Leica Biosystems (LBS) data is being processed by an Access database and transferred
into Callidus using some basic scripts.
Main purpose of this project is to replace above process, implementing a more robust tool with an
SQL Server and Informatica Cloud.
In addition, some data captured in Callidus will need to be transferred into the LBS SQL Server for
reporting purposes.

 Project Overview:
Informatica Cloud will capture data from several sources, which will be transferred into the LBS
SQL Server.
The SQL Server will process the information and it will produce an output that will be transferred
into Callidus by Informatica Cloud.
In addition, some data defined by the business will need to be transferred from Callidus into LBS
SQL Server using Informatica Cloud for reporting purposes.

 Implementation Partner:
BlueNet Technologies
5473 Firefly Court,
Clarence, NY 14031,
United States

Technical Overview
 Current Technical Architecture:
o Integration methodology Tools:
 Visual Basic scripts.
They pick up the source information and transfer the output that will feed Callidus.
 Access database
It captures all information from the sources and generates the output files that will feed
Callidus.
 Questionnaire for Cloud Adoption Services Engagement

 SFTP protocol
Protocol used to transfer output files into Callidus Drop Zone
(dmzdrop.callidusondemand.com).

o Informatica products used:

 Not used yet.

 Future Technical Architecture:

Informatica Cloud will capture the information from SAP and an email attachment (VWR files).
Above data will be transferred into the LBS SQL Server.
Above SQL Server will expose some output data thought SQL views that Informatica Cloud will
consume to feed Callidus.
In addition, the Callidus data selected by the business will need to be transferred into the LBS SQL
Server by Informatica Cloud for reporting purposes.

Engagement Overview
The customer is interested in learning about configuration and planning. See use case below.
 Use Case Overview (Include details):
In a daily basis, Order and Revenue recognition data is being extracted from SAP into csv files for
US and Canada:
 Order Information US (CAL_ZNPAN_157_yyyymmdd.csv)
 Order Information Canada (CAL_ZNPAN_135_yyyymmdd.csv)
 Revenue recognition US (CAL_ZNCON_157_yyyymmdd.csv)
 Revenue recognition Canada (CAL_ZNCON_135_yyyymmdd.csv)
*yyyy=today’s year, mm= today’s month, dd= today’s day.

In addition, commissions team is getting by email a flat file capturing the distributors’ order
information (VWR files).
Above information is being imported into an Access data base (DataProcessing.accdb).
Above mentioned data together with some information manually maintained within Access
generates the flat files (ODJB and ODI files) that are going to be consumed by Callidus.
Above flat files are being transfer into the Callidus Drop Zone (dmzdrop.callidusondemand.com) by
some scripts using the SFTP protocol.

It is required that Informatica Cloud consumes the following information:

 Americas, EMEA and APAC Order and Revenue Recognition data exposed by SAP through
RFCs.
 VWR files provided as an attachment by email.
 Flat files capturing Participants information (Key info: Name, Title, DHR ID, ADP File Info,
Start Date, Manager)

Above information will be transferred into the LSB SQL Server, which will process it and will
generate the output that will be transferred into Callidus through the Informatica connector.

In addition, Informatica Cloud will transfer Callidus processed commissions, Order, Revenue
Recognition, Leasing Agreement Data, Service Agreement Order Data and Transaction data into
the LSB SQL Server for reporting purposes.
 Questionnaire for Cloud Adoption Services Engagement

Estimated Callidus tables capturing the data that needs to be transferred into SQL Server (pending
of confirmation by the business and Callidus Support Team):
 CS_PIPELINEPROFILES
 CS_PIPELINERUNSTAGETABLES
 CS_PIPELINERUN_POSITIONS
 CS_PIPELINE_PROPERTIES
 CS_TRANSACTIONADJUSTMENT
 CS_TRANSACTIONASSIGNMENT
 CS_CREDIT
 CS_MEASUREMENT
 CS_INCENTIVE
 CS_COMMISSION
 CS_DEPOSIT
 CS_DEPOSITADJUSTMENT
 CS_DEPOSITAPPLDEPOSITTRACE
 CS_DEPOSITINCENTIVETRACE
 CS_DEPOSITPMTRACE
 CS_PAYMENT
 CS_PAYMENTSUMMARY
 CS_TRANSACTIONASSIGNMENT
 CS_PARTICIPANT
 CS_POSITION

Additional items to discuss:



Integration Environment Details

 Cloud Products:
 Callidus Cloud.
 Informatica Cloud Application Integration and Data Integration.
 SQL Server implemented within an AWS Server.
 3rd party endpoints [List most common –
 TEST Callidus Drop Zone: dmzdrop.callidusondemand.com:22
 PROD Callidus Drop Zone: dmzdrop.callidusondemand.com:23
 TEST Callidus: https://lcbr-dev.callidusondemand.com/SalesPortal/#!/
 PROD Callidus: https://lcbr-prd.callidusondemand.com/SalesPortal/#!/
 Latency [near real-time, batch?]:
 Batch, due to the fact SAP can only provide Order and Revenue recognition information in
batches.

 Expected Data Volume:

 From SAP into SQL: 300k records/run
 VWR files: 1k records/file
 SQL Server into Callidus: 117k records/run
 Callidus into SQL: unknown.

Please include any additional project documents or diagrams.