Extracting and Uploading data onto MIMS

MIMS or Ellipse have:
- an application layer that consists of programs where all the business rules and logic are implemented: "The Application"

-a data layer where all the client's records are physically stored: "The Database"

The data layer is implemented using a database such as Oracle, DB2, SQL Server or another database supported by Mincom, depending on you particular platform and environment

This topic is concerned with methods of extracting and uploading records to the Database, other than the obvious methods supplied by the Application.

Extracting data from MIMS
======================================================
You can use RDL, CorVu, SQL, MIMS Connector, VB or any other ODBC software or query tool compatible with the Database, provided that adequate security access to the database exists.


Loading data to MIMS
======================================================
- some interface programs MSB* and interface files MST* dictionary entries exist for some areas eg Journal, Supplier, Bank Transactions, Labour Costing, etc.

These are standard interfaces and are documented in the respective User Reference manuals supplied by Mincom.

Usually in order to implement the interface, some customisation is required, for instance by writing auxiliary steps in RDL, that will convert the external data to the format specified by MST*

- MINT scripts available from Mincom or user group; they take their data from a text file in CSV format and simulate data entry via the Application's screens, using the standard Mincom code behind that particular screen(MSO* program) to perform all validations as if data were manually keyed in. This is a safe way of uploading data, however for high volumes it may prove too slow.

- MIMS Connector: supplies an equivalent method to MINT scripts(ie safe but slow), and is available for object-enabled versions of the Application, eg MIMS 4.3

- batch programs MS* supplied by Mincon are appropriate for high record volumes.

- SQL and other software compatible with the Database can be used, but the essential aspect is that if you bypass the Application going directly to the Database, you need to insure that in doing this you do not load records that are inconsistent with the Application's rules.

Because of the complex relationship in the data model, it is very easy to overlook cross reference records and other related records and end up with inconsistent or corrupt data.

***Note that Mincom does not recommend loading data into its MIMS/Ellipse Databases unless via an authorised means, ie load programs or screens provided by Mincom.