Business Organization

1
Business Organization

• Presented By
• Scott W. Sorenson
• SSIS Fiscal Designer / Developer

2
Business Organization

• Defining Business Organization, Vendor, and
  Provider
• Data Cleanup
• Data Interchange Vendor Import
• Data Interchange Setup Vendor Import Setup

3
What is an SSIS Business Organization?

• Any private or public sector entity that has been
  entered into SSIS Worker or SSIS Fiscal.
• Examples Schools, Employers, Foster care
  providers, Daycare providers.
• Each Business Organization may have one or many
  Addresses, Phones, E-mails, Client Will Serve
  Preferences, Licenses, Services Offered,
  Profession Collaterals, and Sub Organizations.
  It may also have one Parent Organization.

4
What is an SSIS Vendor?

• An SSIS Business Organization that has a County
  Vendor .

5
What is an SSIS Provider?

• An SSIS Business Organization that has a
  Provider Tab.
• When a Provider Tab exists, the Individual
  Providers folder will display.

6
Data Cleanup

• Why does the data need to be Clean?
• Data Cleanup Reports
• Data Cleanup Search
• Fixing Dirty data
• Merging Business Organizations

7
Why does the data need to be Clean?

• Vendors in SSIS must have a unique County
  Vendor for linking between SSIS and the County
  Accounting System.
• Each County Vendor in SSIS must be
• Left justified string.
• 1 20 numeric characters.
• Leading zeros are optional, all SSIS lookups by
  County Vendor disregard leading zeros.
• Because it is fun to Clean!!!!!!!!!!!!

8
Data Cleanup Reports

• Show Stoppers - All of the following reports must
  be empty in order for vendor import to
  successfully run
• 196 - Vendors with Duplicate County Vendor
  Numbers
• 241 - Potentially Invalid County Vendor Number
• It is required at the time of the import that all
  SSIS Business Organizations with a County Vendor
  have a corresponding Vendor in your County
  Accounting System/IFS. This can be done by
  printing and comparing a list of
  providers/vendors within SSIS and the County
  Accounting System/IFS. It is best to complete
  this step after some of the cleanup on the other
  reports has been completed.
• Non Show Stoppers - All of the following reports
  should be run to ensure that the SSIS Business
  Organization Data is clean. If you do not
  resolve the issues found by these reports the
  data will still be inaccurate, and may get
  overwritten by running SSIS Vendor Import.
• 200 - Potential Provider/Bus Org/Vendor Records
  Available for Deletion
• 169 - Potentially Invalid Provider/Bus Org/Vendor
  Names and County Vendor Numbers
• 197 - Bus Orgs that do not have a County Vendor
  Number
• 203 - Vendors with Duplicate County Individual
  Providers Names
• An additional reason to resolve the issues in
  these reports is to ensure that the business
  organizations in the dropdown lists in Placement
  and Service Arrangement are the correct Bus
  Org/vendors that can be paid. If you have
  extraneous or incorrect business organizations,
  workers will not know which ones to select and
  may select a bus org that cannot be paid or does
  not have the correct information from the county
  accounting system (if there is no county vendor
  number, there is no link to the county accounting
  system).

9
Data Cleanup Search

• Dynamic generation of Data Cleanup Reports.
• Customization of Data Cleanup Reports including
  which columns to include, sort, group, and
  filter.
• Search capabilities within a specific Data
  Cleanup Report by Bus. Name, SSIS Bus. Org. , or
  County Vendor .
• Immediately resolve issues with Dirty data.

10
Fixing Dirty data

• Use Business Organization entry screen either
  through the Business Organization Cleanup or
  Business Organization Search. If you need to
• Delete the Business Organization
• Clear the County Vendor
• Rename the Business Organization
• Merge two Business Organizations

11
Merging Business Organizations

• Business Organization Merge can be execute
  through SSIS Worker or SSIS Fiscal Business
  Organization Cleanup or Business Organization
  Search by selecting the Merge action.
• When two Business Organization become one, all of
  the data associated to the Delete Bus Org will
  be moved to the Keep Bus Org.

12
Data Interchange Vendor Import

• Overview
• Data Interchange Flow
• Data Interchange Table Structures
• Discuss changes to the County Accounting System
• Generating the Initial Vendor Import Data

13
Overview

• Ensure that vendor data is accurate in both
  systems for future use in Service Arrangements
  and Payments.
• Keep vendor data synchronized between SSIS and
  the County Accounting System.
• Reduce duplicate data entry.

14
Data Interchange Vendor Import flow when
connecting directly to the County Accounting
System
County Accounting System (IFS or Other) Data
Interchange Tables (VNIMPORT SSISVNDR)
SSIS Business Organization Data Interchange
Vendor Import Running on the SSIS Application
Server
SSIS Oracle Database
15
Data Interchange Vendor Import flow when using
Push / Pull to transfer data between SSIS and the
County Accounting System
County Accounting System (IFS or Other) Data
Interchange Tables (VNIMPORT SSISVNDR)
SSIS Push / Pull Running on the SSIS Application
Server
SSIS Oracle Database (VNIMPORT SSISVNDR)
SSIS Business Organization Data Interchange
Vendor Import Running on the SSIS Application
Server
16
Data Interchange Table Structures
VNIMPORT (3100) SEE Section 2.1.1 of the
Business Organization Data Interchange
Specification

• This table will be used as the primary data
  interchange table from the County Accounting
  System to SSIS.
• This table is also defined in the SSIS Oracle
  database for use with push / pull.
• VIKEY is the primary key for VNIMPORT it must be
  a unique number. It will be used to update the
  VIR_CD and VIP_DT as each record is processed.
• VIVNO and VIPAYE are both County Vendor s, which
  will be linked to SSIS Business Organization data
  through the BUS_ORG (2300).CNTY_PROV_NUM. Both
  must be all numeric characters.

SSISVNDR (3105) SEE Section 2.1.2 of the
Business Organization Data Interchange
Specification

• This table will be used by the County Accounting
  System to determine if a vendor has ever been
  sent to SSIS and if it is used in SSIS by
  placements, service arrangements, payments, etc.
  
• This table is also defined in the SSIS Oracle
  database for use with push / pull.
• Vendor Import will maintain the data in this
  table. Each vendor that is sent to SSIS will
  automatically have a record in this table.
• Those that have been used in SSIS by placements,
  service arrangements, payments, and other SSIS
  modules will have VIDELT set to N. Those
  records with an N in VIDELT should NOT be
  purged in the County Accounting System SSIS will
  not allow them to be deleted.
• The Vendor Import process will always set VIDELT
  to N or Y.

17
Discuss changes to the County Accounting System

• Allow users to indicate that a vendor is a social
  services vendor
• Must check SSISVNDR every time a vendor is saved
  in the County Accounting System to see if it has
  already been sent to SSIS. If it has been, then
  a VNIMPORT record must be generated with a VIA_CD
  of U. If it has not been sent to SSIS and it
  is marked as a social services vendor, a VNIMPORT
  record must be generated with a VIA_CD of A.
• Must check SSISVNDR to confirm if a vendor may or
  may not be deleted. If the VIDELT field is N,
  the vendor is used in SSIS and may not be deleted
  in SSIS. If the VIDELT field is Y, the vendor
  is not used in SSIS and may be deleted by the
  County Accounting System, but a VNIMPORT record
  must be generated with an Action code of P.

18
Generating the Initial Vendor Import Data

• Make sure your data interchange table VNIMPORT is
  created.
• Determine within your county how to identify the
  social services vendors. Example In IFS
  counties the County Accounting Systems vendor
  data has a status code which was set to a C to
  indicate CCIS / Social Services Vendors.
• Identify the table and fieldname in the County
  Accounting System, and which field in the data
  interchange table VNIMPORT it should fill.
• Create a program to generate the Initial Vendor
  Import Data.

19
Data Interchange Setup Vendor Import Setup

• Setting up SSIS Connection
• Setting up County Accounting System Connection
• Setting up the Vendor Import Settings
• Generate Initial Vendor Import Data
• Connect Validate
• Running Initial Vendor Import
• Running Vendor Import as a service

20
Setting up SSIS Connection
21
Setting up County Accounting System Connection
22
Setting up the Vendor Import Settings
23
Generate Initial Vendor Import Data

• Verify that you have setup the SSIS Vendor
  Interface Tables correctly as specified in the
  SSIS Business Organization Data Interface
  Specification document or that you have taken the
  steps required to include VNIMPORT (3100) and
  SSISVNDR (3105) in Push / Pull. See Related
  Documents Section for instructions on how to
  access this document. For more information on
  using push / pull with vendor import please see
  APPENDIX C at the end of this document.
• Verify that you have created a program to
  generate a record in the SSIS Vendor Import
  Interface table VNIMPORT, with a VIA_CD of X
  for each social services vendor in your County
  Accounting System. See the SSIS Vendor Import
  Interface Specification document for detailed
  instructions on how this program should work.
• Generate your initial Vendor Import Interface
  VNIMPORT Data, using the above described program.

24
Connect Validate
25
Running Initial Vendor Import
26
Running Vendor Import as a service