These are the main libraries that K3S uses to setup their application at an environment. Because of the nature of the IBM i, the individual libraries are added to a user’s (user meaning the user needed by an application to have access to parts of a system) Library list.
The IBM i will go through the library list searching for an object, from first to last, and will take the first result that matches the object. This allows configurations and modifications specific to a customer’s setup to be added without altering the core code.
Example Library List: QTEMP QGPL K3S_5MOD K3S_5DTA K3S_5OBJ K3S_5WEB
It is allowed for custom library names to be used for each install. These library names listed below would still exist if named something else.
These are the configurable objects that can be setup to match a customers environment as well as add configurations that might be unique to the setup.
These are the main database files for Replenish and ReStore (ex: Product table, Supplier table, Suggested Orders table, etc…).
The Night Job (objects contained in K3S_5OBJ and invoked at a set point after the completion of your EOD process) does the majority of the calculations and updating of the system. Every night K3S will pull directly from your database (if the install is on premise) or receive a copy of a few files via CSV over SFTP, and import them into the database for processing.
All interfaces are expected to work through APIs to delete, update, or create records in the database. Querying may be done directly. This technique is referred to as CQRS.
These are the main compiled objects for the K3S system. These do not change per environment and are part of the core code.
These are the web database files setup for the R6 environment. These files are not used by the Night Job and do not require APIs for updating. They are at the disposal of the interface.
These are the APP Record settings that allow the turning on and off of features for a customers environment.