Monday, 8 December 2014

Do You Want Your Own Fully Programmable ERP? - Part 22

In the first article they mentioned the main characteristics that ought to have a program to be used as a Front-End with some functions of an Enterprise Resources Planning ERP:
Computed Views,
Integrated e-Mail,
and they used the Lotus Notes example, but in principle will be feasible to make use of other softwares with similar functions.
They assume that your company already have an online managerial/accounting process, with evidently its own database.
Now they will see a practical case, a process to detect and control - marketing, sales, new purchase orders - your aground products. As they know, the salesperson prefer to sold new products only, and your aground products will be less and less sold.
From Notes to your relational database
From your relational database to Notes
From a Notes database to another Notes database
From ASCII files to Notes database
From Notes database to ASCII files
Synchronization of both databases
Scheduled type transfers - in a defined time, or hour or minute or day, etc.
Normally this type of program works with the following databases - and this probably include the database type used by your company:one. They will use a process to transfer your managerial/accounting information to the Notes relational database, and although this last has tools for that - ODBC for example - they recommended the acquisition of a specific program for that purpose in order to be more flexible and with more powerful features, that must permit the following transfers:
two. They will choose what fields from your managerial/accounting process - here so called of dbCompany - you need in your new ERP. They can, for example
ALLBASE/SQL, Btrieve, Clipper, DB2, dBASE, Excel, Gupta SQLBase, IMAGE/SQL, INFORMIX, INGRES, InterBase, Microsoft SQL Server, Microsoft Access, Microsoft FoxPro, Netware SQL, Oracle, Paradox, Progress 6, SQL/400, SQL/DS, Sybase, Teradata, Files text, XDB, and also the databases types ODBC, client/server and desktop, etc.
four. Summarizing the above functions Second and Third - about each different product they need from your dBcompany:
To establish the relationship of one-to-one, field x in Notes field y in the dBcompany,
Or they need a non-existent knowledge, what fields they must bring from the dBcompany to compute - in Notes - in order to get the desired knowledge. They are speaking about "information", not of information.
three. They will choose if they need information transcriptions and/or information conditionally computed. A simple example would be the necessity - in Notes - to generate the resulting knowledge x of the information y,k,z from the dBcompany.
All the P.Os, products received, code, description, in the coursework of the period t, with dates, quantities, costs, vendors, etc
The whole sales, in the coursework of the period t, with dates, quantities, sales prices, responsible salesman, etc.
five. They acquire - extract - those information, to be placed in specific Notes fields, and generating the Notes "Views".Customer relationship management

They will continue in the next article.--Publishing Guidelines: You may publish my article in your newsletter, on your net site or in your print publication provided you include the resource box at the finish. Notification would be appreciated but is not necessary.

No comments:

Post a Comment