The Rejected Records File # This file contains all records that were rejected by the migration process. The records written to this file are an exact copy of the rejected records from the input file. After the error that generated the rejected records has been corrected the file of rejected records can be used as the input file for processing. The Error Message File # In this file you will get an explanation as to why your records were rejected. ...
General # Physically, the Access Codes are stored as instances of SicsRefAccessCode (SicsReferenceData subclass 260), in the REFERENCE_DATA table. Each table affected by the Access Code segregationhas a new Access Code foreign key: FRK_ACCESS_CODE FSK_ACCESS_CODE The FSK_ACCESS_CODE column always contains the value (subclass number) 260. The FRK_ACCESS_CODE column contains one of the CODE values defined for the “Access Code” reference data type (see Reference Data Maintenance window). The value in the FRK_ACCESS_CODE column decides which Access Code each row belongs to. ...
Getting Started # NB! When working against the reporting tables using SICS, it has to be logged in as table owner. Here is a complete guide and document references for initial setup for SICS BO reporting tables, views, stored procedures and stored functions. For huge data volume or large number of users , the replicated reporting database is a better option from the database performance point of view. For small and mid size database the production database can be used for the reporting purpose. ...
SICS Task Management has its own User Groups, separate from the SICS Security User Role groups. Task Management User Groups are maintained from the Task Management Maintenance function. Create User Group Link a group of users and / or security user roles together in a User group: Open Task Management from SICS Desktop Select Task Management Maintenance / User Groups tab Select New from pop-up menu Enter a User Group Name Select a Language, if wanted Assigned wanted Users Assign wanted Security User Roles Press OK Edit User Group ...
Logging of SQL statement can be activated by modifying the log4j configuration, as mentioned in the preceding sections. For SICS Workstation and SICS System Administration Utility it is also possible to enable SQL logging or tracing by selecting from the menu, Help - About SICS - System Info… - Logging. This will open a window where SQL logging can be directly configured. The SQL Log Analyzer button will open a file selection window so you can select a log file. ...
For details on how to utilize SICS Live Desktop, please refer to the document ‘SICS Live Desktop Setup and Configuration.pdf’ which is part of the SICS installation package. The following diagram shows how communication takes place between the external application, SNS and SICS Workstation.
Upgrade Path for IDT # UDT - Universe Design Tool Using .UNV file universe # IDT - Information Design Tool Using .UNX file universe # Add all the customizations in to the 25.1 UNV/UDT version and then Upgrade from which ever version you are on up to 25.1 UNV version universe. Overwrite your version of the universe with the 25.1 UNV universe as normal. This will upgrade all reports to use the latest 25. ...
Update RetroPairing Table icon When you click the Update Retro Pairing Table icon in the Periodic Functions Folder in the System Administration Utility, you see a message asking you whether or not you want to update the table.
User Preferences icon You can change some default settings in SICS. When you click the User Preferences icon in the System Administration folder on the SICS desktop, you see the User Preferences window. You can also access this window by selecting User Preferences from the File menu on the desktop. Information about this window is explained in the Getting Started chapter of the User’s Guide. Refer to Setting User Preferences in the Getting Started section of the User’s Guide for more information. ...
This section is for information only. It explains briefly the differences and similarities between Access Code data segregation, segregation by Application Environment, and segregation of data between P&C and SICS Life (if running both systems against a combined database schema). Access Code vs. Application Environment # When logging into SICS, the user must choose which Environment(schema) to log on to. An “environment” is a set of database tables. The tables in one environment are physically separated from the tables in another environment. ...