Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
|
||||||
|
||||||
|
Notes:
|
Database tie-ins - Take the guess work out of database tie-ins – this may include going to the line item id number instead of the main id tie-in. - Everything that goes in must be able to come back out while still holding hands. - Everything that gets tied together must be updated as a whole or if removed or voided, removed as a whole. - The add and reverse logic must be on both sides of the fence. This means if the main is modified, the subs must be modified, or if a sub is modified, the main must be modified. - Need to go back through entire application and modify the tie-in’s to the “no questions” level (line item id level) - What if I allow edits on main tie-ins. If changed, ties with subs will not exist. This could cause problems. - Maybe the solution is “tie where possible” to the exact detail but leave some flexibility to be “generally tied” to another section. - At what point do we ice it down? Maybe limit the edit features on special transactions. - Flags for original pass and flag for tweaked - Human (see it, touch it) – computer (check integrity and flags) |