ISoft Wiki - User contributions [en]

ISoft Data Systems

2009-02-04T20:09:43Z

Charwood: Added picture of turbine flats and a summary of what we do.

ISoft Data Systems is a software development company in Lincoln, Nebraska. They specialize in custom web development and business management solutions for the recycling and salvage industries.

[[Image:TurbineFlatsEast.jpg|frame|ISoft Data Systems is located in the Turbine Flats Building.]]

==Phone Numbers==
* Toll free phone: 800-929-1829
* Nebraska phone: 402-435-3850
* Fax: 402-435-7076

==Address==
2124 Y Street Flat 201 
Lincoln, NE 68503

==See also==
[[:Category:ISoft Employees|ISoft Employees]]

File:TurbineFlatsEast.jpg

2009-02-04T20:08:20Z

Charwood: A photograph of the Turbine flats building's east side taken from the street.

A photograph of the Turbine flats building's east side taken from the street.

ITrack/Enterprise/Order Requests

2008-11-24T19:47:51Z

Charwood: New page: When a work order or sales order requests some quantity of parts that are not available, an order request can be created. Order requests indicate that a particular line of a particular do...

When a work order or sales order requests some quantity of parts that are not available, an order request can be created. Order requests indicate that a particular line of a particular document is in need of some quantity of items. A document with unfulfilled order requests cannot be closed. Purchase orders and Transfer orders are two ways of fulfilling order requests.

[[Category:Enterprise Concepts]]

Date Fields

2008-11-19T23:21:57Z

Charwood: Date Fields moved to Date Fields (ITrack): This is an ITrack and not an ISoft thing. I'm a little isolated. Sometimes I forget that they are different things.

#REDIRECT [[Date Fields (ITrack)]]

ITrack/Date Fields

2008-11-19T23:21:57Z

Charwood: Date Fields moved to Date Fields (ITrack): This is an ITrack and not an ISoft thing. I'm a little isolated. Sometimes I forget that they are different things.

Most places in ITrack where dates need to be entered there exist special Date Controls. These objects have a drop down calendar and are specially designed to help people view dates visually. Some places, however, there is either little room for a large date control or for other design reasons a simple edit box is used. Even though the edit boxes aren't as visually appealing, they are still very powerful and efficient.

Date edits in ITrack can parse a large number of possible formats.

==Absolute Dates==
Absolute dates are precise dates. ITrack supports two formats:
* American Format - This is the standard American 'mm/dd/yyyy' format. ITrack supports just typing in the month/day part or even just the day part. The year can be entered as a two digit or four digit number.
* SQL Format - This is a the commonly used computer format 'yyyy-mm-dd'. ITrack supports just typing in the month-day part of even just the day part. The year can be entered as a two digit or four digit number.

==Relative Dates==
The flexibility of the date system is greatly enhanced by the allowance of relative dates. A relative date can be entered on its own (in which case it will be relative to the current date) or it can be inputted following an absolute date. Relative dates can be in many formats:
* "<+/->n <period>" - The plus or minus tells whether to add or subtrack, the number n represents an integer, and the <period> can be any of "days", "weeks", "months", or "years" or simply their first letters "d", "w", "m", and "y". The period is case insensitive and the pluralization is optional. Some examples:
** "+5 weeks" - Five weeks from now
** "-1 year" - Last year
** "+12w" - Twelve weeks from now
** "12/25/1985 +60d" - Sixty days after Christmas in 1985
** "3 -7" - Seven days before the third of this month
* "[<modifier>] <day of week>" - By day of the week. <modifier> is optional and can be either a plus or minus followed by a number or one of the words "this", "last", of "next" and is case insensitive. <day of week> can be "Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday" or their usual shorter forms "Su(n)", "Mo(n)", "Tu(es)", "We(d)", "Th(urs)", "Fr(i)", "Sa(t)". It is case insensitive. If a plus or minus and a number is placed before the day of the week then ITrack interprets it as that man <day of week>s ago. If no number is used then ITrack assumes that the day listed is the day of the current week (even if it has passed or is yet to come). Weeks in ITrack begin on Sunday and end on Saturday. Some examples:
** "Th" - The Thursday of this week.
** "-1 Friday" - The Friday of the previous week.
** "next sat" - The Saturday of the next week
** "4/1 Mon" - The Monday in the week of April first.
** "1976-06-04 Sunday" - The Sunday of the week 200 years after the the United States declared their independence.
* "<special>" There are a few special strings that ITrack recognizes. While there is generally no good reason to, they can be appended to absolute dates. They are case insensitive:
** "today" - Today
** "tomorrow" - Tomorrow
** "yesterday" - Yesterday

ITrack/Date Fields

2008-11-19T23:21:24Z

Charwood: This isn't implemented too many places in the software but I used this to kind of test out how it would be and to document its eventual existence.

My ISoft is Broke

2008-10-30T22:38:23Z

Charwood: New page: No. Your '''ITrack''' is broke.

No. Your '''ITrack''' is broke.

ITrack Enterprise Accounting

2008-10-30T20:45:59Z

Charwood: ITrack Enterprise Accounting moved to Accounting (Enterprise): To be consistent with existing structure.

#REDIRECT [[Accounting (Enterprise)]]

ITrack/Enterprise/Accounting

2008-10-30T20:45:59Z

Charwood: ITrack Enterprise Accounting moved to Accounting (Enterprise): To be consistent with existing structure.

ITrack Enterprise uses a very flexible accounting system. It is designed to allow for both complex and simple general ledger practices and to easily integrate with any sort of external general ledger based accounting package. 
 
----
 
'''Accounts:''' 
The Accounting Screen in ITrack Enterprise allows a user (probably an administrator) to set up a chart of accounts. This is done in the Accounting screen on the Accounts tab. Accounts in ITrack have a number, a name, a description, and a type. For example: 
Name: Accounts Receivable 
Number: 1000 
Description: An account that shows how much money the company is owed from customers. 
Type: Asset 
 
----
 
'''Categories:''' 
Every item in inventory and every kind of labor used is assigned a "GL Category". A "GL Category" defines the kinds of accounts that that item needs to affect in different situations. These situations are called "GL Contexts" and are described below. 
Some examples of GL Categories that people might use: 
New Parts 
Used Parts 
Labor 
 
----
 
'''Contexts:''' 
The software defines certain contexts, or situations where accounting applies. A complete list of the contexts is here: 
Core Sale - Occurs for every inherent core on a sales order that affects inventory when it is finalized 
Core Return - Occurs for every dirty core returned on a sales order that affects inventory when it is finalized 
Core Transfer - Occurs for every core as it is transferred on a transfer order 
Core Purchase Return - Occurs when cores are returned to vendors 
Purchase - Occurs when an item is received from a purchase order 
Purchase Return - Occurs when an item is returned on a purchase order 
Return - Occurs when an item is returned on a sales order 
Sale - Occurs when an item is sold on a sales order 
Transfer - Occurs when an item is transferred on a transfer order 
Work In Progress - Occurs for each line and labor item on a work order whenever it is saved 
Work Order Consumption - Occurs for each line and labor item on a work order when it is finalized 
Work Order Production - Occurs for the master record on a work order when a work order is finalized 
Work Order Sold - Occurs for each line and labor item on a work order when it is finalized 
 
Each combination of category and context allows the definition of four accounts. The user can set these up in the Accounting screen on the Categories tab: 
Transaction Debit Account - Debits this account (usually by price) 
Transaction Credit Account - Credits this account (usually by price) 
Inventory Debit Account - Debits this account (usually by cost) 
Inventory Credit Account - Credits this account (usually by cost) 
 
For certain categories in certain contexts, it might not make sense to fill in an account. For instance taxes are ordinarily applied on the transaction side rather than the inventory side. 
 
In general, for categories that represent inventory items, the Inventory Credit Account should always be the account that represents the value of that inventory item.
 
----
 
'''Transactions:''' 
Whenever the General Ledger is affected, all of the entries are grouped into a transaction. The transaction verifies that all of the debits and all of the credits are equal, that balance being the fundamental rule of GL based accounting. The transaction also applies a timestamp recording the exact second that the accounting occurred and exactly how much money was involved. It also allows for user comments. 
 
----
 
'''Entries:''' 
Each accounting entry is stored as a single record and therefore can be copied into whatever accounting system the user chooses (assuming their accounting package has some mechanism to either import or directly input data). 
 
----
 
'''Accounting Packages:''' 
ITrack Enterprise was designed specifically with Sage's Mas90 accounting system in mind http://www.sagemas.com/products/sagemas90_mas200/

[[Category:Enterprise Concepts]]

ITrack/Enterprise/Accounting

2008-10-30T20:45:12Z

Charwood:

ITrack/Enterprise/Accounting

2008-10-30T20:44:11Z

Charwood:

ITrack/Enterprise/Accounting

2008-10-30T20:42:57Z

Charwood:

ITrack/Enterprise/Accounting

2008-10-30T20:40:36Z

Charwood: Fixed some wording

ITrack Enterprise uses a very flexible accounting system. It is designed to allow for both complex and simple general ledger practices and to easily integrate with any sort of external general ledger based accounting package. 
 
----
 
'''Accounts:''' 
The Accounting Screen in ITrack Enterprise allows a user (probably an administrator) to set up a chart of accounts. Accounts in ITrack have a number, a name, a description, and a type. For example: 
Name: Accounts Receivable 
Number: 1000 
Description: An account that shows how much money the company is owed from customers. 
Type: Asset 
 
----
 
'''Categories:''' 
Every item in inventory and every kind of labor used is assigned a "GL Category". A "GL Category" defines the kinds of accounts that that item needs to affect in different situations. These situations are called "GL Contexts" and are described below. 
Some examples of GL Categories that people might use: 
New Parts 
Used Parts 
Labor 
 
----
 
'''Contexts:''' 
The software defines certain contexts, or situations where accounting applies. A complete list of the contexts is here: 
Core Sale - Occurs for every inherent core on a sales order that affects inventory when it is finalized 
Core Return - Occurs for every dirty core returned on a sales order that affects inventory when it is finalized 
Core Transfer - Occurs for every core as it is transferred on a transfer order 
Core Purchase Return - Occurs when cores are returned to vendors 
Purchase - Occurs when an item is received from a purchase order 
Purchase Return - Occurs when an item is returned on a purchase order 
Return - Occurs when an item is returned on a sales order 
Sale - Occurs when an item is sold on a sales order 
Transfer - Occurs when an item is transferred on a transfer order 
Work In Progress - Occurs for each line and labor item on a work order whenever it is saved 
Work Order Consumption - Occurs for each line and labor item on a work order when it is finalized 
Work Order Production - Occurs for the master record on a work order when a work order is finalized 
Work Order Sold - Occurs for each line and labor item on a work order when it is finalized 
 
Each context allows the definition of four accounts: 
Transaction Debit Account - Debits this account (usually by price) 
Transaction Credit Account - Credits this account (usually by price) 
Inventory Debit Account - Debits this account (usually by cost) 
Inventory Credit Account - Credits this account (usually by cost) 
 
For certain categories in certain contexts, it might not make sense to fill in an account. For instance taxes are ordinarily applied on the transaction side rather than the inventory side. 
 
In general, for categories that represent inventory items, the Inventory Credit Account should always be the account that represents the value of that inventory item.
 
----
 
'''Transactions:''' 
Whenever the General Ledger is affected, all of the entries are grouped into a transaction. The transaction verifies that all of the debits and all of the credits are equal, that balance being the fundamental rule of GL based accounting. The transaction also applies a timestamp recording the exact second that the accounting occurred and exactly how much money was involved. It also allows for user comments. 
 
----
 
'''Entries:''' 
Each accounting entry is stored as a single record and therefore can be copied into whatever accounting system the user chooses (assuming their accounting package has some mechanism to either import or directly input data). 
 
----
 
'''Accounting Packages:''' 
ITrack Enterprise was designed specifically with Sage's Mas90 accounting system in mind http://www.sagemas.com/products/sagemas90_mas200/

ITrack/Enterprise/Accounting

2008-10-30T20:36:39Z

Charwood: Added very brief descriptions of entries, transactions, and accounting packages

ITrack Enterprise uses a very flexible accounting system. It is designed to allow for both complex and simple general ledger practices and to easily integrate with any sort of external general ledger based accounting package. 
 
----
 
'''Accounts:''' 
The Accounting Screen in ITrack Enterprise allows a user (probably an administrator) to set up a chart of accounts. Accounts in ITrack have a number, a name, a description, and a type. For example: 
Name: Accounts Receivable 
Number: 1000 
Description: An account that shows how much money the company is owed from customers. 
Type: Asset 
 
----
 
'''Categories:''' 
Every item in inventory and every kind of labor used is assigned a "GL Category". A "GL Category" defines the kinds of accounts that that item needs to affect in different situations. These situations are called "GL Contexts". 
Some examples of GL Contexts that people might use: 
New Parts 
Used Parts 
Labor 
 
----
 
'''Contexts:''' 
The software defines certain contexts, or situations where accounting applies. A complete list of the contexts is here: 
Core Sale - Occurs for every inherent core on a sales order that affects inventory when it is finalized 
Core Return - Occurs for every dirty core returned on a sales order that affects inventory when it is finalized 
Core Transfer - Occurs for every core as it is transferred on a transfer order 
Core Purchase Return - Occurs when cores are returned to vendors 
Purchase - Occurs when an item is received from a purchase order 
Purchase Return - Occurs when an item is returned on a purchase order 
Return - Occurs when an item is returned on a sales order 
Sale - Occurs when an item is sold on a sales order 
Transfer - Occurs when an item is transferred on a transfer order 
Work In Progress - Occurs for each line and labor item on a work order whenever it is saved 
Work Order Consumption - Occurs for each line and labor item on a work order when it is finalized 
Work Order Production - Occurs for the master record on a work order when a work order is finalized 
Work Order Sold - Occurs for each line and labor item on a work order when it is finalized 
 
Each context allows the definition of four accounts: 
Transaction Debit Account - Debits this account (usually by price) 
Transaction Credit Account - Credits this account (usually by price) 
Inventory Debit Account - Debits this account (usually by cost) 
Inventory Credit Account - Credits this account (usually by cost) 
 
For certain categories in certain contexts, it might not make sense to fill in an account. For instance taxes are ordinarily applied on the transaction side rather than the inventory side. 
 
In general, for categories that represent inventory items, the Inventory Credit Account should always be the account that represents the value of that inventory item.
 
----
 
'''Transactions:''' 
Whenever the General Ledger is affected, all of the entries are grouped into a transaction. The transaction verifies that all of the debits and all of the credits are equal, that balance being the fundamental rule of GL based accounting. The transaction also applies a timestamp recording the exact second that the accounting occurred and exactly how much money was involved. It also allows for user comments. 
 
----
 
'''Entries:''' 
Each accounting entry is stored as a single record and therefore can be copied into whatever accounting system the user chooses (assuming their accounting package has some mechanism to either import or directly input data). 
 
----
 
'''Accounting Packages:''' 
ITrack Enterprise was designed specifically with Sage's Mas90 accounting system in mind http://www.sagemas.com/products/sagemas90_mas200/

ITrack/Enterprise/Accounting

2008-10-30T20:29:24Z

Charwood: Added basic information about how ITrack does accounting.

ITrack Enterprise uses a very flexible accounting system. It is designed to allow for both complex and simple general ledger practices and to easily integrate with any sort of external general ledger based accounting package. 
 
----
 
'''Accounts:''' 
The Accounting Screen in ITrack Enterprise allows a user (probably an administrator) to set up a chart of accounts. Accounts in ITrack have a number, a name, a description, and a type. For example: 
Name: Accounts Receivable 
Number: 1000 
Description: An account that shows how much money the company is owed from customers. 
Type: Asset 
 
----
 
'''Categories:''' 
Every item in inventory and every kind of labor used is assigned a "GL Category". A "GL Category" defines the kinds of accounts that that item needs to affect in different situations. These situations are called "GL Contexts". 
Some examples of GL Contexts that people might use: 
New Parts 
Used Parts 
Labor 
 
----
 
'''Contexts:''' 
The software defines certain contexts, or situations where accounting applies. A complete list of the contexts is here: 
Core Sale - Occurs for every inherent core on a sales order that affects inventory when it is finalized 
Core Return - Occurs for every dirty core returned on a sales order that affects inventory when it is finalized 
Core Transfer - Occurs for every core as it is transferred on a transfer order 
Core Purchase Return - Occurs when cores are returned to vendors 
Purchase - Occurs when an item is received from a purchase order 
Purchase Return - Occurs when an item is returned on a purchase order 
Return - Occurs when an item is returned on a sales order 
Sale - Occurs when an item is sold on a sales order 
Transfer - Occurs when an item is transferred on a transfer order 
Work In Progress - Occurs for each line and labor item on a work order whenever it is saved 
Work Order Consumption - Occurs for each line and labor item on a work order when it is finalized 
Work Order Production - Occurs for the master record on a work order when a work order is finalized 
Work Order Sold - Occurs for each line and labor item on a work order when it is finalized 
 
Each context allows the definition of four accounts: 
Transaction Debit Account - Debits this account (usually by price) 
Transaction Credit Account - Credits this account (usually by price) 
Inventory Debit Account - Debits this account (usually by cost) 
Inventory Credit Account - Credits this account (usually by cost) 
 
For certain categories in certain contexts, it might not make sense to fill in an account. For instance taxes are ordinarily applied on the transaction side rather than the inventory side. 
 
In general, for categories that represent inventory items, the Inventory Credit Account should always be the account that represents the value of that inventory item.

User:Charwood

2008-10-20T18:56:20Z

Charwood: Added my basic functions.

[[Category:ISoft Employees]]
Charles is a developer at ISoft and is a primary contributor to ITrack Pro, ITrack AX, ITrack Enterprise, and fully wrote ITrack U-Pull-It.