Home >Documents >CP-106: Making Costpoint Integrations Part of Your World · PDF file • Cognos (CER)...

CP-106: Making Costpoint Integrations Part of Your World · PDF file • Cognos (CER)...

Date post:23-Mar-2020
Category:
View:1 times
Download:0 times
Share this document with a friend
Transcript:
  • 1

    CP-106: Making Costpoint Integrations Part of Your World

    Martin McGann III, Premier Consulting & Integration

  • 2

    Premier Consulting & Integration, LLC (PCI) is the leading provider

    of financial management consulting services, implementation and

    audit support for government contractors and marketing agencies.

    Our consultants combine 30+ years of relevant experience acting as

    former CFO’s, controllers and accountants. We offer small business

    solutions that are affordable, easy to use and profitable.

    Intro To PCI

  • 3

    About Me

    Martin McGann

    • Former CFO and Controller for growing government contractors

    • In 2009, I started PCI, in effort to provide best-in-class implementation, training and accounting support for small to mid-sized government contractors.

  • 4

    Agenda

    1. Integrations Defined

    2. Building an Integration with Costpoint

    3. Getting Data Out of Costpoint

    4. Getting Data Into Costpoint

    5. Benefits & Challenges of using the WIC

    6. Q&A

    During this session we will review a how to make Costpoint Integrations Part of your World by:

  • 5

    The Challenge

    • More than 1 data source houses similar information • One application has preferred functionality over another • User Preference

  • 6

    Integrating with Costpoint

    You have options!

    • Costpoint Offerings • Copy FROM excel to Costpoint • Costpoint Family of Preprocessors • Web Integration Console (API)

  • 7

    Considerations Before Integration Begins

    • Frequency – How many times a day/week/year will this take place?

    • Time to Enter Manually – What time savings will we get?

    • Benefit outside of time savings – What other benefits are derived?

    • Data – What will get transferred?

    • Directionality – Which way/ways is the data going?

    • User – Who benefits from the proposed improvements?

    • Methodology – Based on your options we discussed which makes the most sense?

    • Cost – Is there a budget?

    • Time – Is there an urgency?

  • 8

    Integrations from Costpoint

    • Why SQL is not a future option • Simple

    • Copy to Excel • Costpoint Output Reports

    • Moderate Difficulty • Cognos (CER) report to excel/csv/html • Cognos report emailed/saved to a location • Cognos report scheduled to email/saved to a location

    • Advanced • SOAP API to 3rd Party

    • Questions

  • 9

    Integrations to Costpoint

    • Simple • Copy paste FROM Excel

    • Moderate • Preprocessors

    • Vendors, employees, projects, vouchers, cash receipts, Journal Entries, Labor

    • Credit Card Data

    • Advanced • API – most likely a REST to SOAP API for integration

  • 10

    API

    • API – Application Programming Interface – designed to make it easier for developers to access data from platforms.

    • Why they are cool – API provides us a recurring transfer of data from one place to another without the user doing anything.

    • Talent Management -> Costpoint -> Talent Management

    • Why they are not cool – if you thought Cognos (CER) was hard…you really need a developer or consultant to build this structure.

  • 11

    SOAP vs REST

    Deltek uses a SOAP based API; the other option is REST here is the difference:

    • REST API has no has no official standard at all because it is an architectural style. SOAP API, on the other hand, has an official standard because it is a protocol.

    • REST APIs uses multiple standards like HTTP, JSON, URL, and XML while SOAP APIs is largely based on HTTP and XML.

    • As REST API deploys multiple standards, so it takes fewer resources and bandwidth as compared to SOAP that uses XML for the creation of Payload and results in the large sized file.

    • The ways both APIs exposes the business logics are also different. REST API takes advantage of URL exposure like @path("/WeatherService") while SOAP API use of services interfaces like @WebService.

    • SOAP API defines too many standards, and its implementer implements the things in a standard way only. In the case of miscommunication from service, the result will be the error. REST API, on the other hand, don't make emphasis on too many standards and results in corrupt API in the end.

    • REST API uses Web Application Description Language, and SOAP API used Web Services Description language for describing the functionalities being offered by web services.

    • REST APIs are more convenient with JavaScript and can be implemented easily as well. SOAP APIs are also convenient with JavaScript but don't support for greater implementation.

  • 12

    For those of us who are not Technical

    • If your 3rd party uses REST and you want to communicate with Deltek, we have to write a translation form JAVA (or similar) to XML

    • This takes a bunch of time and needs to be tested

    • It will take a couple tries to iron out all the variables

    • If you change your mind on something you need to recode for the change

  • 13

    Turning on the Deltek Web Integration Console

    • If you are hosted in the cloud: • Book a service ticket - >

    • If you host your own Costpoint: • This is turned on in the WebLogic console • There is a KB article that you can reference for the steps

    • You typically turn this on in a “development” state first, then “promote” the integration to your production environment

  • 14

    Samples of Integrations we have completed

  • 15

    Questions?

    Ask Away!

  • 16

Click here to load reader

Reader Image
Embed Size (px)
Recommended