I am looking for an ISV or streamline process to accomplish the below task:
Tickets will be entered into a new Page “Tickets” which will be based on the NAV Sales Invoice page. The Page will have standard FastTabs (General, Invoicing, etc.) and custom FastTabs (Site, Employees).
Specific views are required depending on the type of service (services, hot oil, or water transfer). User will select the view by defining the type of service, or possibly by user setup. MBI would like to use responsibility center to drive which ticket entry view is provided to the user.
If the ticket is for a Vendor (Owner Operator), the Vendor Number will be selected in the header from a Vendor list, filtered to show only Vendors flagged as Owner Operators.
A Primary Resource (Job Description) will be included on the header and flow to the first line only. Also, an Object (Equipment) will be selected on the header and flow to only the first line, subsequent lines will default to a blank resource – any additional resource will be selected by the user. (All resources are editable on the line).
Company Man fields will be replicated as they are in Rentals. Push effort to Phase 2
The Site FastTab (sans EDI) will be replicated as it is in Rentals. Site will include a link to the Wells table, just as they are in Rentals.
The Lines Section with be used for all charges on the Ticket. Resources will be the Default line type.
An Object Look up will be added to the lines. The object value set in the header will copy to the first line, but will be editable (blank is valid). Postings from the line must post to the Object Entries Table, and therefore be traceable to both the resource and object. The line dimensions will be set from the object selected in that line.
Several control fields will be added to the lines that will be programmatically set based on sales and purchase transactions.
The Ticket will have statistics to allow for ticket totaling.
Scan tickets and link to the Ticket using a drag and drop feature. [JRK1]
Once ticket entry is complete the user will “Release” the ticket by clicking the release button. If the ticket has not been invoiced OR settled, it may be reopened and edited.
When a ticket has been invoiced and fully paid, the program will update the Ticket to indicate has been paid. This is a required filter for the settlement process. Push effort to Phase 2
Correction Process
if a ticket has a posted invoice (sales or purchase), a process is required to correct one or both. Tickets that have been invoiced may not be manually edited. A process will be created to correct the ticket, programmatically adding reversal lines to the ticket and adding new lines for the corrected data. Reversals using a credit memo will be posted to the object entries.
ID | Sales Posted | Settlement Posted | |
1 | No | No | |
2 | Yes | No | Ticket Locked; Reversal w/Sales Credit Memo if necessary |
3 | No | Yes | Ticket Locked; Reversal w/Purchase Credit Memo if necessary |
4 | Yes | Yes | Ticket Locked; Reversal w/Sales and/or Purchase Credit Memo if necessary |
Invoicing will only look at Released Tickets. A new List Page, Tickets Waiting to be Invoiced will be used to filter Released Tickets. The default filters will be Customer No., Site (Location), Job Description, and Document Date. Other filters will be available for users to select.
The user will then select the tickets to be merged into a single Sales Invoice (Boolean field or similar). Select All and Unselect all buttons will be available. Manually selection of the Tickets is possible. A function will then be executed to Create a Sales Invoice.
Ticket headers will be updated to indicate that an invoice has been created and disallow the ticket from being re-invoiced. Tickets that have had an invoice created will be filtered out for the Tickets Waiting to be Invoiced View.
The newly created sales invoice(s) will be in the standard Sales Invoice List view page. The Sales Invoice can be reviewed, but is not editable (with the exception of EDI fields).
A Performa Invoice is required (New Report).
Followed up fields (date & follow up) similar to those used on a rental order are required (List View and Page View).
Combine Ticket PDF Documents into a single pdf attached to the Sales Invoice. Push Effort to Phase 2.
If changes are required, the sales invoice will be deleted, the ticket updated, and sales invoice recreated.
After adding EDI fields (where applicable) the Sales Invoice will be posted and archived as a Posted Sales Invoice. Allow editing of EDI fields on Posting Sales Invoice, as in Rentals (See EDI Process).
Posted Sales Invoice Report will require modification to specifications.
EDI Process
The Sales Invoice (SI) and Posted Sales Invoice (PSI) will have all relevant EDI fields added to the header in a new FastTab.
On the generation of the SI, the program will copy from the customer all EDI values. The use is responsible to edit the EDI fields per invoice.
The printed Performa Invoice Report must contain this information for verification by the company man.
All EDI fields must flow to the PSI.
Once the SI is posted, the responsible user will Create EDI Document. This feature will be similar to the Rental Invoice feature. However, the file created will be to the specification of the customer for tickets. This requires a report per customer using EDI.
An Edit EDI Fields button is required to allow editing and regeneration of the EDI file.
New field for EDI Created Date and EDI File Path are required on the PSI and Posted Sales Invoice List Pages. This functions is the same as rentals.
