SSIS Fiscal Setup Instructions€¦ · APPENDIX D: Related Documents ... 2.2 DriverName – Defaults to the AS/400 driver. For IFS counties this should always be CA400. For custom

SSIS Fiscal Setup Instructions

Business Organization/County AccountingSystem Vendor Data Interchange

Prepared By: Scott W. Sorenson

Project Manager: Kate Stolpman

Last Updated: May 23, 2005

Change Sheet

Revision Description Date

Original Apr. 28, 2005

1 Modified the instructions for running the Generation ofthe Initial Import Data in the County Accounting Systemfor IFS Counties. Changed data cleanup report “241 -Potentially Invalid County Vendor Number” to be a nonshow stopper report.

May 18, 2005

Table of Contents

SECTION One: Preparation and Setup Check List ............................................... 1

1.0 Introduction ........................................................................................ 1

1.1 SSIS Preparation.................................................................................. 2

SSIS Data Cleanup reports....................................................................... 2

1.1.1.1 Show Stoppers ....................................................................... 2

1.1.1.2 Non Show Stoppers................................................................. 2

1.2 SSIS Vendor Import Settings ................................................................. 3

1.2.1 SSIS Vendor Import Settings Worksheet .......................................... 3

1.2.2 Entering Vendor Import Setup Settings............................................ 6

1.2.2.1 Vendor Import Setup Tab ........................................................ 7

1.2.2.2 County Accounting System Connection Settings Tab ..................... 8

1.2.2.3 Vendor Import Settings Tab ..................................................... 9

1.3 County Accounting System Preparation ...................................................10

1.3.1 IFS Counties ..............................................................................10

1.3.2 Non IFS Counties ........................................................................10

1.3.3 Validate the connection settings, SSIS Vendor Data, and Initial VendorImport Data .........................................................................................11

SECTION Two: Initial SSIS Vendor Import .......................................................12

2.0 Introduction .......................................................................................12

2.1 Running ............................................................................................12

SECTION Three: SSIS Vendor Import as a Service............................................13

3.0 Introduction .......................................................................................13

3.1 Running ............................................................................................14

SECTION Four: ERROR HANDLING .................................................................15

4.0 Introduction .......................................................................................15

4.1 SSIS Vendor Import Log Files and Errors .................................................15

4.1.1 Where will the files be? ................................................................15

4.1.2 Normal Files...............................................................................16

4.1.3 Fatal Error Files ..........................................................................17

4.2 Data Errors ........................................................................................18

4.2.1 Data Errors that are unique to Vendor Import ..................................18

4.2.2 Other Data Errors........................................................................19

4.2.3 Resolving Data Errors ..................................................................19

4.3 System Errors ....................................................................................23

4.4 Network Errors ...................................................................................23

APPENDIX A: SSIS Initial Vendor Import Generation Script Requirements............24

APPENDIX B: Instructions for executing the SSIS Initial Vendor Import GenerationScript .......................................................................................................27

APPENDIX C: Vendor Import and Push/Pull .....................................................29

APPENDIX D: Related Documents .................................................................35

Business Organization DI SetupInstructionsLast Updated: 05/23/05


Page 1 of 36

SECTION One: Preparation and Setup CheckList

1.0 Introduction

The purpose of this section is to help you determine if you are ready for VendorImport to run. It will also guide you through the steps required to run VendorImport, including:

• Data Cleanup

• Configuration of Vendor Import

• Generating the Initial Vendor Import

Following the step by step checklist below will ensure that you are ready forsuccessful implementation of the SSIS Vendor Import Service.



Page 2 of 36

1.1 SSIS Preparation

The purpose of this section is to help you determine if you have completed all thenecessary tasks in your Social Services Information System to begin using SSISVendor Import.

SSIS Data Cleanup reportsUsing either SSIS Fiscal or SSIS Worker please execute all of the SSIS BusinessOrganization Cleanup Reports.

1.1.1.1 Show StoppersThe following report must be empty in order for vendor import to successfully run:

o 196 - Vendors with Duplicate County Vendor Numbers

It is required at the time of the import that all SSIS Business Organizations with acounty vendor number have a corresponding vendor number in your CountyAccounting System/IFS. This can be done by printing and comparing a list ofproviders/vendors within SSIS and the County Accounting System/IFS. It is best tocomplete this step after some of the cleanup on the other reports has beencompleted.

1.1.1.2 Non Show StoppersAll of the following reports should be run to ensure that the SSIS BusinessOrganization Data is clean. If you do not resolve the issues found by these reportsthe data will still be inaccurate, and may get overwritten by running SSIS VendorImport.

o 241 - Potentially Invalid County Vendor Number

o 200 - Potential Provider/Bus Org/Vendor Records Available for Deletion

o 169 - Potentially Invalid Provider/Bus Org/Vendor Names and County VendorNumbers

o 197 - Bus Orgs that do not have a County Vendor Number

o 203 - Vendors with Duplicate County Individual Providers Names

An additional reason to resolve the issues in these reports is to ensure that thebusiness organizations in the dropdown lists in Placement and Service Arrangementare the correct Bus Org/vendors that can be paid. If you have extraneous orincorrect business organizations, workers will not know which ones to select and mayselect a bus org that cannot be paid or does not have the correct information fromthe county accounting system (if there is no county vendor number, there is no linkto the county accounting system).



Page 3 of 36

1.2 SSIS Vendor Import Settings

The SSIS Vendor Import Settings are broken into three parts: SSIS ConnectionSettings, County Accounting System Connection Settings, and Vendor ImportSettings. This section is designed to help you collect and enter all the necessaryinformation to Connect to SSIS, and to the County Accounting System.

1.2.1 SSIS Vendor Import Settings WorksheetPlease have a member of your county’s IT staff or SSIS Administrator fill out thispage and the following two pages for use in entering all of the necessary informationto setup SSIS Vendor Import.

1. SSIS Connection Settings

Item – Description Example Value

1.1 Host – IP Address of SSIS ApplicationServer.

Localhost

1.2 User – Valid SSIS user logon. SSIS

1.3 Password - Valid password for SSIS logonused (Don’t write here for security reasons).

*********

1.4 Database – Should be set to theproduction database alias used in your county.

SSIS_DATA



Page 4 of 36

2. County Accounting System Connection Settings


2.1 Using external interface tables? – Do you want SSIS to read theinterface tables from your County Accounting System?

NOTE: In IFS counties this will always be YES. Non-IFS countiesplease see your IT personnel for the answer. Indicate “Yes” if youintend for SSIS Vendor Import to connect to your County AccountingSystem. Indicate “No” if you intend to populate the interface tablesin the SSIS Oracle Database using Push / Pull. For more informationon using push / pull with vendor import please see APPENDIX C atthe end of this document.

Yes

The following information in the County Accounting System Connection SettingsSection of this worksheet is only needed if the above answer (2.1) is Yes. If noproceed to section 3 Vendor Import Settings.

2.2 DriverName – Defaults to the AS/400 driver. For IFS countiesthis should always be CA400. For custom counties you will need toselect the appropriate driver to connect to your County AccountingSystem. Determine the type of database you’re using.

AS/400,SQLServer,Oracle, etc

The following information in the County Accounting System Connection SettingsSection of this worksheet is specifically designed for the AS/400 connection. Mostof the settings below will also be required by other types of databases as well, butthere may be additional information needed to connect. Non-IFS Counties: Contactthe SSIS Help Line if you need assistance.

2.3 Database – Name of the AS/400 Database as it appears in thehost file or under the System DSN – System Name box

SSIS400

2.4 User Name – Should be a user logon with limited rights to thecounty accounting system interface tables VNIMPORT and SSISVNDR.Should be setup so that the user’s password does not expire to avoidpassword issues in the future. Should have the right to read, write,and update both VNIMPORT and SSISVNDR

SSISPP

2.5 Password – Valid password for the selected logon above *********

2.6 RoleName - Should be set to the AS/400 Library Name that is thehome of the data interchange tables. For IFS Counties this should beIFXH__ or IFXC__. Example: Here at SSIS it is IFXH04. Todetermine the RoleName; Logon to IFS on your county AS/400.Press the System Request key to get the system request prompt (onmost personal computers use Shift + Escape). Press enter to get theSystem Request Menu. Take option 3 to display the current job.Take option 13 to display the library list. Look for library IFXH__ orIFXC__ with type of CUR, where __ is your county or region number.

IFXH04



Page 5 of 36

3. Vendor Import Settings


3.1 Active – Determines whether SSIS VendorImport should run recursively.

NOTE: This sho5uld not be checked untilinitial import has been completed

FALSE

3.2 Start Date/Time – The starting Point of theinterval timing

03/15/20057:00 AM

3.3 Interval – How often SSIS Vendor Importshould run.

Hrs: 0

Minutes: 20

3.4 Exclude a time period – Turns SSIS VendorImport off during a selected period of time

NOTE: This is useful to permit the county to shutVendor Import off all night long or during yourcounty’s backup and reboot times.

TRUE

Excluded Time Start & End Time Start Time:6:00 PM

End Time:

6:00 AM



Page 6 of 36

1.2.2 Entering Vendor Import Setup Settings1. Go to the SSIS Application Server.

2. Select Start.

3. Select Programs.

4. Select SSIS Server.

5. Select Vendor Import Setup.

6. Using the SSIS Vendor Import Settings Worksheet, fill out each of the tabs.

7. Click the Save button.

8. Select the SSIS Connection Settings Tab.

9. Click the Test Connection button.

10. If the message “Connection was Successful” displays, move on to step 12.

11. If the message “Connection Failed” displays, verify the settings on this tab andrepeat step 9 until the “Connection was Successful” message displays. If, afterrepeated attempts, you cannot get a “Connection is Successful” message; pleasecontact the SSIS Helpline.

12. If the setting “Using external interface tables” is yes then proceed on to step 13.If the setting is no then move on to step 17.

13. Select the County Accounting System Connection Settings Tab.

14. Click the Test Connection button.

15. If the message “Connection was Successful” displays, move on to step 17.

16. If the message “Connection Failed” displays, verify the settings on this tab andrepeat step 14 until the “Connection was Successful” message displays. If, afterrepeated attempts, you can not get a “Connection was Successful” message;please contact the SSIS Helpline.

17. Congratulations! You have successfully gathered and entered all of the Settingsnecessary for SSIS Vendor Import to run!



Page 7 of 36

Full Size Vendor Import Setup Screens

1.2.2.1 Vendor Import Setup Tab



Page 8 of 36

1.2.2.2 County Accounting System Connection Settings Tab

NOTE: Database, User_Name, Password, and RoleName must be set based on yoursite information.



Page 9 of 36

1.2.2.3 Vendor Import Settings Tab



Page 10 of 36

1.3 County Accounting System Preparation

The purpose of this section is to help you determine if you have completed all thenecessary tasks in your County Accounting System to begin using SSIS VendorImport.

1.3.1 IFS CountiesThe following check list will walk you through the steps required to execute theinitial vendor import generation program. The initial vendor import generationprogram will verify that you have the latest version and patches of IFS, and it willgenerate the initial vendor import data based on IFS and CSIS social servicesvendors.

o Verify that you have completed all the necessary requirements. SeeAPPENDIX A: SSIS Initial Vendor Import Generation Script Requirements atthe end of this document.

o CSIS counties must do a Push in SSIS Push/Pull and then an Import in CSISand then a Pull in SSIS Push/Pull. This must occur each time before the scriptdescribed in the next step is executed.

o Execute the SSIS Initial Vendor Import Generation Script. See APPENDIX B:Instructions for executing the SSIS Initial Vendor Import Generation Script atthe end of this document. The script is located on the SSIS Server in“E:\softwardis\as400ftp\SSIS038\VendorImport.sf”.

1.3.2 Non IFS Countieso Verify that you have setup the SSIS Vendor Interface Tables correctly as

specified in the SSIS Business Organization Data Interface Specificationdocument or that you have taken the steps required to include VNIMPORT(3100) and SSISVNDR (3105) in Push / Pull. See Related Documents Sectionfor instructions on how to access this document. For more information onusing push / pull with vendor import please see APPENDIX C at the end of thisdocument.

o Verify that you have created a program to generate a record in the SSISVendor Import Interface table VNIMPORT, with a VIA_CD of “X” for eachsocial services vendor in your County Accounting System. See the SSISVendor Import Interface Specification document for detailed instructions onhow this program should work.

o Generate your initial Vendor Import Interface VNIMPORT Data, using theabove described program.

o Verify that you have modified your County Accounting System’s VendorMaintenance program to generate records in the SSIS Vendor ImportInterface Table VNIMPORT for each social services vendor added, or modified.Records in this table should have a VIA_CD of “A” if the record doesn’t existin SSISVNDR, or a VIA_CD of “U” if the record does exist in SSISVNDR. Alsoverify that logic has been added to verify that social services vendors can’t bedeleted if they exist in SSISVNDR, and have a VIDELT = “N”.



Page 11 of 36

1.3.3 Validate the connection settings, SSIS VendorData, and Initial Vendor Import Data

1. Go to the SSIS Application Server.

2. Select Start.

3. Select Programs.



6. Select the Connect & Validate Data button.

One of the following messages will display:

• Import connected successfully and the import data is valid.

• Import connection failed or the import data was invalid. If thisdisplays please double check each connection using the TestConnection buttons. If both connections are successful you likely havea data validation problem. If one or both of the Test Connections failsplease review your settings. For additional information on any ofthese errors please see section four of this document.

Based on the # of records in data interchange table VNIMPORT one of thefollowing messages will also be displayed:

• 2000 records or less – “You have 1050 records in VNIMPORT toprocess.”

• Between 2000 and 4999 records - “You have 2050 records inVNIMPORT to process. SSIS recommends that you run vendorimport during off hours, because processing this many records willbe system intensive and may affect user performance.”

• 5000 records or more - “You have 5050 records in VNIMPORT toprocess. SSIS recommends that you review the logic used togenerate the records in VNIMPORT. If you have questions pleasecontact the SSIS Helpline.” Non IFS Counties should verify thatthe initial load program is only selecting Active Social ServicesVendors, for import into SSIS.



Page 12 of 36

SECTION Two: Initial SSIS Vendor Import

2.0 Introduction

This section will guide you through the step by step process of running Initial SSISVendor Import. Section One of this document MUST be completed before your canbegin working on Section Two of this document.

2.1 Running

NOTE: Section One of this document MUST BE COMPLETED before youcontinue. DO NOT perform these steps on a Friday. SSIS only retainsbackup copies of the tables for 24 hours and can recover and restore them ifyou have a major problem and wish to start over.

NOTE: IFS Counties must perform the steps described in Section 1.3.1 andNon IFSC Counties must perform the steps described in Section 1.3.2 beforeeach attempt at Initial SSIS Vendor Import.

1. Go to the SSIS Application Server.

2. Select Start.

3. Select Programs.



6. Select the Run Import Now button. Initial SSIS Vendor Import takes about 1second per Vendor, so if you have 600 Vendors you should expect the processto complete in about 10 minutes.

7. Upon completion, you should receive a message as to whether the import wassuccessful or if it failed.

8. If the message “Import Successful” displays, continue on to step 9. If themessage “Import Failed” displays, please see Section Four. Upon resolutionof the issue(s) repeat steps 1 through 7.

9. Immediately inform SSIS Fiscal that Initial Vendor Import has beencompleted successfully, by sending an e-mail [email protected].

10. Please check your SSIS Business Organization data within 24 hrs ofcompleting the initial import. SSIS only retains backup copies of thetables for 24 hours and can recover and restore them if you havemajor problems and wish to start over. If you think there may be aproblem with your data please contact the SSIS Helpline immediately.



Page 13 of 36

SECTION Three: SSIS Vendor Import as aService

3.0 Introduction

This section will guide you through the step by step process of running SSIS VendorImport as a Service recursively (maintenance mode). Sections One and Two of thisdocument MUST be completed before your can begin working on Section Three.



Page 14 of 36

3.1 Running

NOTE: Sections One and Two of this document MUST BE COMPLETED beforeyou begin this process. DO NOT perform these steps on a Friday. SSIS onlyretains backup copies of the tables for 24 hours and can recover and restorethem if you have a major problem and wish to start over.

1. Go to the SSIS Vendor Import Setup Application.

2. Select the Vendor Import Settings Tab.

3. Check the Active Check Box.

4. Click the Save button.

5. Close the SSIS Vendor Import Setup Application.

6. Go to Windows Explorer.

7. Right Click on My Computer.

8. Select Manage.

9. Select Services and Applications.

10. Double Click On Services.

11. Scroll to “SSIS Vendor Import”.

12. Right Click on “SSIS Vendor Import”.

13. Select Start.

14. Message “Service has started” should display, if so move on to step 15. If notsee Section Four for troubleshooting.

15. Congratulations! SSIS Vendor Import is now running recursively (inmaintenance mode).

16. Immediately inform SSIS Fiscal that Vendor Import has beensuccessfully setup to run as a service, by sending an e-mail [email protected].

17. Please make a change in your County Accounting System that should bereceived by SSIS, and verify that SSIS receives the change using the SSISFiscal Import Log.

18. Please check your SSIS Business Organization data within 24 hrs.SSIS only retains backup copies of the tables for 24 hours and canrecover and restore them if you have major problems and wish tostart over. If you think there may be a problem with your data pleasecontact the SSIS Helpline immediately.



Page 15 of 36

SECTION Four: ERROR HANDLING

4.0 Introduction

This section describes the data errors and how to resolve them, along with systemand network errors. Data errors are broken into two types those that are unique toVendor Import and those that you would see in the GUI when editing a businessorganization. System and network errors are recorded in text files located in thesame directory as Vendor Import (usually “\\SSISAppServer\ProgramFiles\DHS\SSIS\Server\SISVIMP.exe”).

4.1 SSIS Vendor Import Log Files and Errors

This section gives you a quick overview of the two types of files used by the SSISVendor Import. The first type includes the Normal Files, such as VendorImport.ini orSSISVIMP.log. The second type includes error files such asDuplicateCntyVendorNum.err or InvalidCntyVendorNum.err.

This section also includes the standard messages found in these files, along withsome of the business rules that are unique to SSIS Vendor Import.

4.1.1 Where will the files be?1. Go to the SSIS Application Server.

2. Open Windows Explorer.

3. Navigate to “C:\Program Files\DHS\SSIS\Server\”

4. All of the .ini, .log, and .err files will reside in this directory.



Page 16 of 36

4.1.2 Normal FilesFile Name Description

VendorImport.ini Contains all of the connection and interval information needed to run SSISVendor Import.

SSISVIMP.log Contains history of import connections, # of records processed, and showsfatal errors.

Standard Messages found in SSISVIMP.LOGStarted Import ProcessingCompleted Import ProcessingNo Data to ProcessSuccessfully Connected to SSISSuccessfully Connected to County Accounting SystemStarted Validation of SSIS and County Accounting System Vendor dataCompleted Validation of SSIS and County Accounting System Vendor dataStarted Importing DataFinished Importing DataStarted Updating Vendor Usage Table SSISVNDRCompleted Updating Vendor Usage Table SSISVNDR

# Processed: [#of]# Successful: [#of]# Warnings: [#of]# Errors: [#of]# Action Code Errors: [#of]# Data Errors: [#of]# Save(ApplyUpdates) Errors: [#of]

Fatal Error Messages found in SSISVIMP.LOGSSIS Connection Failed - "[ExceptionMessage]"County Accounting System Connection Failed - "[ExceptionMessage]"Vendor Import could not run, because of the errors above.[#of] duplicate County Vendor #s exist. Please see DuplicateCntyVendorNum.err.[#of] Invalid County Vendor #s exist. Please see InvalidCntyVendorNum.err.[#of] Invalid Payees exist. Please see InvalidPayee.err.[#of] Vendors are in SSIS, but not in County Accounting System. Please seeVendorInSSISNotInCAS.err.Error Updating Vendor Usage Table. - "[ExceptionMessage]"



Page 17 of 36

4.1.3 Fatal Error FilesThe following files are only created if there are records that prevent SSIS Vendor Import fromrunning. SSIS Vendor Import WILL NOT process records if any of the following files aregenerated.

File Name Description

DuplicateCntyVendorNum.err List of Vendors who do not have a unique County Vendor # inSSIS.

InvalidCntyVendorNum.err List of Vendors who have invalid county vendor # in SSIS.

InvalidPayee.err List of Vendors who have a payee or service vendor that doesnot have County Vendor #.

VendorInSSISNotInCAS.err List of Vendors who are in SSIS, but not in County AccountingSystem.



Page 18 of 36

4.2 Data Errors

4.2.1 Data Errors that are unique to Vendor ImportThe following table contains a list of error messages, which are unique to the VendorImport. They are a set of special business rules that only apply to the VendorImport Interchange tables.

VNIMPORT–FIELDNAME

Message Comments / Resolution

VIA_CD* Invalid Vendor ImportAction Code (VIA_CD)"[VIA_CDValue]", forCounty Vendor #"[VIVNOValue]".

Should only display if there is a programming error inthe County Accounting System. Vendor Import ActionCode (VIA_CD) must be one of the following values:A, U, X, or P.

VIA_CD* Invalid Vendor ImportAction Code (VIA_CD)"[VIA_CDValue]", forCounty Vendor #"[VIVNOValue]".Vendor already existsin SSIS ([BUS_NAME- BUS_ORG_ID]).

Vendor Import Action Code (VIA_CD) was set to “A(Add)”, but the County Vendor # already exists inSSIS. Two possible programming problems: TheCounty Accounting System is not correctly usingSSISVNDR to determine if County Vendor # is alreadyin SSIS, or SSIS is not writing records to SSISVNDRcorrectly.

VIA_CD* Invalid Vendor ImportAction Code (VIA_CD)"[VIA_CDValue]", forCounty Vendor #"[VIVNOValue]".Vendor does not existin SSIS.

Vendor Import Action Code (VIA_CD) was set to “U(Update)”, but the County Vendor # does not exists inSSIS. Two possible programming problems: TheCounty Accounting System is not correctly usingSSISVNDR to determine if County Vendor # is alreadyin SSIS, or SSIS is not writing / deleting records inSSISVNDR correctly.

VIA_CD* Invalid Vendor ImportAction Code (VIA_CD)"[VIA_CDValue]", forCounty Vendor #"[VIVNOValue]".Vendor ([BUS_NAME- BUS_ORG_ID]) isused in SSIS, thus itcan not be deleted.

Vendor Import Action Code (VIA_CD) was set to “P(Purge)”, but the County Vendor # is used by SSIS ina placement, or other module and can not be deleted.Two possible programming problems: The CountyAccounting System is not correctly using theSSISVNDR to determine if a County Vendor # is beingused by SSIS, or SSIS is not correctly updatingSSISVNDR to indicate County Vendor #s used inSSIS.

VIPAYE** Payee County Vendor# "[VIPAYE]", does notexist in SSIS.

Payee County Vendor # (VIPAYE) is set to a CountyVendor # that does not exist in SSIS. Verify that theCounty Vendor # used in VIPAYE is a valid CountyVendor # that has been sent to SSIS.

NOTE*: VIA_CD errors should not be a common occurrence. They are usuallycaused by a programming error in the County Accounting System. Please contactSSIS Help Desk for assistance.

NOTE**: Depending on the County Accounting System’s Vendor Maintenanceprogram this could be user error or a programming error. The Payee County Vendor# must be associated with a vendor that is in SSIS.



Page 19 of 36

4.2.2 Other Data ErrorsAll of the other data errors and business rules are documented in the SSIS BusinessOrganization Specification Documents and training materials; please see RelatedDocuments for a detailed description and how to find these documents. All SSISBusiness Organization business rules and errors are applied to each vendor importthrough the SSIS Vendor Import process.

4.2.3 Resolving Data ErrorsIn order to resolve the data errors you must first identify them. To identify the erroryou will use the SSIS Fiscal Business Organization Import Log. It may be accessedby:

1. Opening SSIS Fiscal on your workstation.

2. Select the Business Organization bar within the Outlook bar to the left of thescreen.

3. Select Import Log (Screen shots are at the end of this section).

Once in the import log you can use it like all of the other searches in SSIS; it hasthe ability to show you those records that were successful as well as those thatfailed. You may also search for a specific vendor by using the “Search thecontents of the Imp/Exp Log Data”. Using this box, you may type any datavalue that should have been part of your record. This search is a very powerfulword search that does allow wild card characters, and other advanced searchingfeatures. Examples:

Example 1

County Vendor #: 000100101

Can be found by typing *.*100101

Example 2

County Vendor Name: Jones Family Foster Care

Can be found by typing: Jones

Can be found by typing: Jones Family

Can be found by typing: Jones Foster Care

NOTE: The more search criteria you enter the faster the search will perform,and the more accurate the results will be.

Once you have found an error; note the error and the County Vendor # (VIVNO),both of which are located in the preview panel at the bottom of the screen (Screenshots are at the end of this section). With this information proceed to the CountyAccounting System, fix the problem, and wait for the next run of Vendor Import*.

*The next run of Vendor Import will occur based on the interval your county hassetup in the Vendor Import Settings

NOTE: IFS users – You must save changes and exit IFS Vendor Maintenance for thechanges to be saved and exported to the data interchange tables for processing.



Page 20 of 36

Full View of the Import Log viewed through the SSIS Fiscal Application.

Full screen view of the Import Log with the Outlook bar and tree view collapsed.



Page 21 of 36

Full screen view of the Import Log search panel and results grids, with the Outlookbar, tree view, and preview panel collapsed.

The Import Log without the rest of the screen elements.



Page 22 of 36

The Import Log’s preview panel:



Page 23 of 36

4.3 System Errors

All system errors will be trapped by exception handling and will be logged to a textfile SSISVIMP.log for manual follow-up. This file can be found in the same directoryas Vendor Import Vendor Import (usually “\\SSISAppServer\ProgramFiles\DHS\SSIS\Server\SISVIMP.exe”).

4.4 Network Errors

Vendor data interchange tables may be accessed in one of two ways depending onuser settings. The first and most likely way is through a native DBExpress driverover TCP/IP. The second is through the same standard connection used by all SSISclient applications. This setting is determined by checking Vendor Import Setup orviewing VendorImport.ini (usually “\\SSISAppServer\ProgramFiles\DHS\SSIS\Server\SISVIMP.exe”).

All errors will be trapped by exception handling and will be logged to a text fileSSISVIMP.log for manual follow-up. This file can be found in the same directory asVendor Import Vendor Import (usually “\\SSISAppServer\ProgramFiles\DHS\SSIS\Server\SISVIMP.exe”).

The following table contains some examples of possible network errors that mayoccur and the solutions:

Message Solution

SSIS Connection Failed - "Connection Error.Could not connect to an available server.When a server becomes available, retryoperation. Error Messages Follow:"

The SSIS Application Server is eithernot available or the Host specified inthe Vendor Import Setup – SSISConnection tab is incorrect. Verifythat the host is correct and that theSSIS Application Server is runningcorrectly.

County Accounting System ConnectionFailed - "Missing Database property"

The “Database” property in theVendor Import Setup – CountyAccounting System tab is incorrect.Verify that it is set to the correct“Database”.

County Accounting System ConnectionFailed - "cwbCO_Connect returned errorcode 8002.

CWBSY0002 - Password for user SSISPP onsystem SSIS400 is not correctServer error class 0 code 0"

AS/400 specific error, although asimilar error may display for othertypes of databases. The passwordspecified in the Vendor Import Setup– County Accounting System tab isincorrect. Verify that you havespecified the correct password andretest the County Accounting SystemConnection.



Page 24 of 36

APPENDIX A: SSIS Initial Vendor ImportGeneration Script Requirements

1. IBM AS/400 with IBM operating system at V5R1M0 or higher. SSIS no longersupports non-RISC machines, or operating systems that IBM no longer supports.

2. You will need to be able to sign-on to the SSIS Server with enough authority torun the SSIS Script Processing Utility (SPU).

3. Within the SPU you will need to use an AS/400 Profile which has enoughauthority to run the necessary commands. The minimum AS/400 Profilerequirements are:

A. Sufficient authority to create files in library QTEMP using the CRTSRCPFand CRTPF commands.

B. *USE authority on the following IFS programs (if you are an IFS county):1. IFXOBJ/IFD002. IFXOBJ/IFD103. IFXOBJ/IFD19

GRTOBJAUT OBJ(IFXOBJ/IFD00) OBJTYPE(*PGM) USER(your_user) AUT(*USE)





Page 25 of 36

C. *CHANGE authority on file VNIMPORT in the library specified as the“Rolename” in the Vendor Import Setup County Accounting SystemConnection Settings tab on the SSIS server.

GRTOBJAUT OBJ(xxxxxx/VNIMPORT) OBJTYPE(*FILE) USER(your_user) AUT(*CHANGE)

D. Authority to read the following files where xx is the CSIS county or ‘00’ for aCSIS region, yy is the CSIS county or region number, and zz is the IFS regionnumber:1. CSISFxx/PVNGNL2. CSISFxx/PVNGNL3. CSISFxx/PVCLIN4. CSISFyy/CLIPLOCHFL5. IFXHzz or IFXCzz/IFVEND (if you are an IFS county)

TCP/IP and FTP must be running on the AS/400. You can use the CSIS ReleaseMenu option 11 to check this. If either is not running, it/they must be started. Thisprocess may vary for each AS/400 configuration. You may need to consult theAS/400 manuals for help in starting TCP/IP and/or FTP.



Page 27 of 36

APPENDIX B: Instructions for executing theSSIS Initial Vendor Import Generation Script

1. Display SSIS SPU Screen. From the Start Menu, go to Programs ->SSIS_SPU -> ssis_spu

2. Using the SSIS Script Processing Utility (SPU) Screen.

a. Use the Browse button to select the script file for this release:

E:\softwardis\as400ftp\SSIS038\VendorImport.sf

b. Review the Script File name to ensure you have loaded the correctscript.

Note: This is a screenshot of past CSISreleases. Browse to the correct SSISscript version per these instructions.



Page 28 of 36

c. AS/400 Logon1. IP Address

Select your AS/400 from the drop-down list. At leastthree IP addresses will be displayed in the drop-down list -- your AS/400, your SSIS NT Server, andthe AS/400 at the SSIS project site in St. Paul. TheIP address you select here will be displayed the nexttime the SSIS Script Processing Utility (SPU) is used.

2. AS/400 User IDEnter the user ID of an AS/400 user with sufficientauthority to create files on the AS/400. The AS/400user ID entered here will be displayed the next timethe SSIS Script Processing Utility (SPU) is used.NOTE: In AS/400 terms, the user ID is referred to asthe AS/400 User Profile.

3. AS/400 PasswordEnter the password associated with the user ID(Profile) above. For security reasons this will not besaved.

d. Click the Process button to run the script. As the script executes,the SPU Log displays on the screen. The processing time for thescript will depend on several factors, including the size and speedof your AS/400, the speed of your communication links, and thesize of your SSIS database.

e. Review the SPU Log to confirm that all commands in the scriptwere executed. Errors or failures will appear in red. Ignore errorsin blue. Close the SPU log window by clicking the Done button, thissaves the log to a file and closes the window.

f. Click the Exit button to close the SSIS Script Processing Utility.

If you have questions or problems with SPU, call the SSIS Help Line.



Page 29 of 36

APPENDIX C: Vendor Import and Push/Pull

Background

Unlike most other tables used in SSIS, vendor-related tables are maintained in thecounty accounting systems and then pulled into SSIS. The vendor import interfacetable VNIMPORT is used to update a number of underlying tables within SSIS.Because of the complexity of the underlying data mappings, SSIS designed thisinterface table to simplify keeping the county database system synchronized with theSSIS system.

Maintaining SSIS vendor tables by sending data through the Push/Pull module differsfrom other Push/Pull table maintenance because VNIMPORT is an interface-only tabledesigned to pass adds, changes, and deletes to a series of SSIS tables. This is incontrast to most tables that the counties maintain directly through Push/Pull, such asthe PERSON table. For this reason, SSIS requires each row in the TRANS_OUT tablefor VNIMPORT to have a unique value in its key field (VIKEY) and requires thetransaction to be completely populated with current county vendor information forboth add and change transactions. This logic differs from all other tablesmaintained through Push/Pull.

Please read the following documentation carefully in order to avoid data loss in theSSIS vendor tables when using Push/Pull.



Page 30 of 36

Initial Vendor Load

Initially loading the vendor data from county accounting files works much like otherPush/Pull processes. Load all the required vendor information and write a Push/Pulltransaction to add the data to the VNIMPORT table (3100).

Note that the action code (ACT_CD) is set to “A” for an add transaction and that field2708, VIA_CD, is set to “X” to indicate that this is an initial load transaction into theSSIS vendor tables.

In order to determine if the data passed all edits and has been added to SSIS, Pushthe updated 3100 transactions back to the county system and examine field 2709,VIR_CD. “0” indicates a successful add, “1” indicates a warning error, and “2”indicates the data was not added due to errors.

To correct data during the initial load, build a new VNIMPORT transaction with thecorrect data and pull it into SSIS. The vendor import process will not attempt to re-process transactions once it has updated VIR_CD, so you may continue to try addinga vendor until it is successful. Transactions with VIA_CD equal to “X” will be treatedas either an add or update transaction, based on whether or not the vendor alreadyexists in SSIS.

SSIS key values for vendors are not passed back to the county through VNIMPORTtable. SSIS maintains vendor links between SSIS and the county accounting systemusing the county vendor number. If your county needs to create a cross-reference within your county accounting system between SSISBUS_ORG_ID and your county’s vendor number, you must push table 2300BUS_ORG to your system in order to build the cross reference. This is truewhether or not you use Push/Pull to maintain the SSIS vendors, i.e. this isstill true if SSIS processes the VNIMPORT table directly from your databasemanagement system.



Page 31 of 36

On-Going Vendor Import

On-going adds, changes, and deletes to the VNIMPORT table through Push/Pull arecoded differently than for other SSIS tables. Following are sample transactions forVNIMPORT, with a discussion differences in logic from most tables processed throughPush/Pull.

Add Transactions

Shown below is a Push/Pull add transaction for table 3100, VNIMPORT. ThePush/Pull action code is “A” for an add transaction to table VNIMPORT. Field 2708,VIA_CD, is also coded with an “A” to indicate this is an add transaction for a vendor(as opposed to an add transaction to VNIMPORT). The new vendor’s number iscoded in field 2728, VIVNO.

As with the initial load, in order to determine if the data passed all edits and hasbeen added to SSIS, push the updated 3100 transactions back to the county systemand examine field 2709, VIR_CD. “0” indicates a successful add, “1” indicates awarning error, and “2” indicates the data was not processed due to an error. As withthe initial load, transactions with a status of “2” must be corrected in the countyaccounting system and re-pulled into SSIS.



Page 32 of 36

Change Transactions

A Push/Pull change to field 0140, CNTY_PERSON_NUM, in the PERSON table has thefollowing values in the TRANS_CD, ACT_CD, and DATA columns of tableTRANS_OUT:

TRANS_CD ACT_CD DATA

500 C 0625 5678910|0140168723|

The transaction above is coded with an action code of “C” for a change to an existingperson row. Field 0625 contains the key value for the person being changed, whilefield 0140 shows the new value for the CNTY_PERSON_NUM column in the PERSONtable. Unchanged columns are not included in the transaction; all column values inthe PERSON table other than CNTY_PERSON_NUM retain their current values afterthis transaction is applied.

The logic for a Push/Pull update to field 2727 VINAME in the VNIMPORT table has thefollowing values in the DATA column of table TRANS_OUT:

There are several important points to note about the transaction for the 3100 table.All transactions (adds, changes, and deletes) for this table must be marked with anaction code of “A”, meaning add. Field 2708, VIA_CD, has the value “U”, meaningthis is an update to an existing vendor’s data. The key value in field 2720 is onlyused as a unique identifier for the row in the interface table. The actual countyvendor number being changed is coded in field 2728. Table VNIMPORT may havemany rows added over time to maintain the same vendor. All fields must be filledwith all current data from the county accounting system for eachtransaction, even for changes to a vendor. Unlike all other field changes sentthrough Push/Pull, any field values passed in for VNIMPORT through Push/Pull thatare empty, null, or spaces will cause the corresponding columns in SSIS tables to beset to null.

Push table 3100 back to your county and examine field 2709, VIR_CD, to determinethe transaction’s status. “0” indicates a successful add, “1” indicates a warningerror, and “2” indicates the data was not processed.



Page 33 of 36

The Push/Pull transactions against interface table VNIMPORT to make severaldiscrete changes to the same vendor follow:

All transactions are coded with an action code of “A” for add. The first transactionshows an update to the vendor name. Note the value for field 2720 is 9852371.The second transaction shows an update to the same vendor’s address. The valuefor field 2720 is 9852372, while the vendor number field value (field 2728) is still1862. The third transaction shows an update to the same vendor’s city, while thefourth transaction shows an update to the same vendor’s email address. Eventhough the data in only one column is being changed, all of the vendor’scurrent data must be sent to SSIS in each transaction. Any column valuesomitted will result in the corresponding column values in SSIS being set to null.



Page 34 of 36

Delete Transactions

A Push/Pull delete transaction for the VNIMPORT table is show below. The actioncode is “A”, for an add transaction to VNIMPORT. The vendor number to be deletedis coded in field 2728. Field 2708, VIA_CD, has the value of “P” for Purge, which willcause the vendor data to be deleted from SSIS. As with other transactions, push the3100 table back to your county and examine field 2709, VIR_CD, to see if thetransaction was successful.

Summary

VNIMPORT was designed to simplify updates to vendors in SSIS by centralizing allvendor information in one table for your county to populate. SSIS will update theappropriate underlying tables based on the values you provide in VNIMPORT.

The VNIMPORT table can reside in your county database management system andSSIS can process it using an ODBC or other link that you define, or VNIMPORT canreside in SSIS and you can populate it using Push/Pull. If your county chooses tohost VNIMPORT in the SSIS database, you must be careful in building Push/Pulltransactions to maintain vendors. You will cause data loss in the SSIS vendortables if you do not send all the column values each time you update avendor.

If you intend maintaining VNIMPORT through Push/Pull, the SSIS projectrecommends that you notify us, so that we can evaluate any initial developmentissues you may experience.



Page 35 of 36

APPENDIX D: Related Documents

Document Title Location Purpose / Comments

SSIS Fiscal DataInterchange Specification– Business Organization /County Accounting SystemVendor Data

DHS Website\CountyLink\SSIS Fiscal\PaymentsWorkgroup\PW DetailedDesign

Detailed designspecification for thetransfer of CountyAccounting System VendorData to SSIS. Includesdetailed flow charts ofrequired programminglogic within the CountyAccounting System’sVendor MaintenanceProgram, along withdocumentation regardingthe required interchangedatabase table structures

Business OrganizationSoftware Specification

DHS Website\CountyLink\SSIS Fiscal\PaymentsWorkgroup\PW DetailedDesign

Detailed designspecification for theBusiness Organizationmodule within SSIS.



Page 36 of 36