Ticket Entry and Consolidated Invoice
Overview:
Your company generates multiple 'tickets' each day that contain the detail of the goods that are shipped. Each is currently entered as a separate Sales Order in Macola. Multiple tickets and Sales Orders are often generated for the same customer each day. You would like to consolidate these tickets onto a single Sales Order per Customer per Job while maintaining visibility of the individual ticket numbers.
Proposed Solution:
A program will be developed to allow the users to input the Ticket details during the week.
An additional process will be developed to consolidate the Tickets by Customer and by Job and create a single 'I'nvoice type Sales Order for each Customer/Job combination found. Line items will be entered for each Ticket with the Ticket Number maintained in a Line Item User Defined field.
A custom Crystal Report Invoice will be developed to show the Order details, including Ticket Number, Ticket Date and Customer PO Number.
Detail of Requirements:
OE Enter Orders:
The user will select function key {F12} to display a Ticket Data entry form.
Records will be saved in new database tables named OETICHDR_SQL and OETICLIN_SQL. Editing Data: User may double click any line in the listbox to place the line in 'Edit' mode. The data for this line will be moved into the corresponding textboxes above. User will make changes and 'Save' the line. Header data may not also be edited by selecting (double click) any line to put the screen in edit mode. Header data will be updated when user clicks 'Save'. (Note: Changes to the Header data affects all line items!) Generate Sales Orders: When the user selects 'Generate Orders', a form will be displayed. The user will enter the Order date (default will be the current date). The user may Print an 'Edit List' report showing all Job Tickets and details that will be converted to Sales Orders. The report will print to screen and optionally, to printer. Report will be grouped by Customer and within Customer, by Job. When the user selects 'Generate Orders', all Tickets currently in the OETICHDR_SQL table that have not previously been processed (Status does not equal 'P'rocessed) will be converted to Sales Orders. Tickets will be grouped by Customer and within Customer, by Job. A separate 'I' type Sales Order will be created for each Customer/Job combination found. All Tickets without a Job No will be written to a single Sales Order. Sales Orders will be created using the next Order No from the Macola OE Control file. The file will be incremented for each order created. A separate line item will be written for each Ticket with the Ticket Number written to the Line Item User Defined Field 2. Appropriate records will be written to the OE Header and Line Audit Tables and the OE Inquiry Order table. Inventory will be allocated and appropriate Inventory transaction records written. Kit Items are supported by this interface without changes to the Kit components. Feature Items, Serialized Items, Lotted Items, Binned Items, Tax Schedules and Sales Commissions are not supported via this interface. As Ticket records are converted to Sales Orders, the header record 'Status' field will be updated to Status 'P' (Processed) to insure they are processed only once. When all Sales Order have been created, the Order Number range will be reported back to the user via a standard message box. Invoice: User will run invoices through the regular Macola 'Print Invoice' function. Invoices will print/post to file. User may then print invoices to printer via the 'Reprint Posted Invoices' function. The 'Reprint' function will be modified to print a new Crystal Invoice to display the Ticket Number on each Line Item. Invoice will be based on the standard Macola ICR "OEINVFRMSQL.rpt". The Ticket Number will be exposed in the Item detail section. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| General Information | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Languages | Exact Product Line | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Platform | Modules Impacted | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Database Supported | Version | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Industries | Horizontal Focus | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||