all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Yellow
|
|
|||
|
|||
|
|
|
Notes:
|
|
Duplicate a PO: - Maybe add the word split – not right now - Any PO including a voided PO - One page wonder - Main info at top, line items next - Allow for manual or auto calculate of the PO total - On line items, either lock or show both request quantities and like quantities. This needs to check the master… if live and never was a request, don’t allow requests. If a request, don’t allow for live, etc. Then again maybe we just open it up and let the users do what they want. - We do need to check for permission if PO is other than a basic live or basic request… remember update PO’s, internal build, and special requests an special live. - On the success message… add a link to the master, reduplicates, or view new - When creating… check for any request quantities… if yes mark as was_po_request. Actually… match the master was request setting. - Open up extended costing fields… use auto as a keyword or allow for new values. Use the extended so we can back into the costs and include a rounding error if any. - We need a way to skip or don’t use a line item… this could be a check mark or leave the fields blank - Along with the skip option… we need a select/deselect all check box - We are not doing any chaining at this point… this may be a future project, AKA… linking PO’s together (brother/sister, parent/child, etc.) - The goal is one, function & two, speed PO Types: Id = name 1. Dummy 2. Basic Live 3. Update 4. Internal Build 5. Basic Request 6. Special Request 7. Special Live |