Feature - Trigger an Event When Printing Duplicate Posted Invoices
Release date: 3/28/2019
Version: 8.2 and up
In the past, Elliott supported invoice printing events for regular invoice printing, but not for printing duplicate invoices from invoice history. Starting with this revision, Elliott added the ability to trigger an event when printing duplicate posted invoices similar to the events generated when printing regular invoices. The main reason behind this change is because some users are using the printing invoice from invoice history function to send out PDF PostOffice invoices, and they want to get email notifications when that happens.
The following events will be triggered on an invoice-by-invoice basis. All of the events use the same fields as their regular invoice printing counterparts. Since the Event Types are different, they need to be subscribed separately from the regular invoice printing event. Users can subscribe to the event where the file listed is maintained.
Type: DUPINVCU
Description: Dupl Invoice Printing Customer
File: ARCUSFIL (Subscribe to Event from Customer File Maintenance)
Description: Dupl Invoice Printing Customer
File: ARCUSFIL (Subscribe to Event from Customer File Maintenance)
Fields: same as INVPRTCU
1) Customer No
2) Order No
3) Ship To No
4) Bill-To Name
5) Ship-To Name
6) Cust Po No
7) Salesman No
8) Inovice No
9) Invoice Date
10) Location
Type: DUPINVSM
Description: Dupl Invoice Printing Salesman
File: ARSLMFIL (Subscribe to Event from Salesman File Maintenance)
Description: Dupl Invoice Printing Salesman
File: ARSLMFIL (Subscribe to Event from Salesman File Maintenance)
Fields: same as INVPRTSM
1) Salesman
2) Customer No
3) Ship To No
4) Bill-To Name
5) Ship-To Name
6) Cust Po No
7) Order No
8) Inovice No
9) Invoice Date
10) Location
Type: DUPINVSH
Description: Dupl Invoice Printing Ship-To
File: CPSHPFIL (Subscribe to Event from Ship-To File Maintenance)
Description: Dupl Invoice Printing Ship-To
File: CPSHPFIL (Subscribe to Event from Ship-To File Maintenance)
Fields: same as INVPRTSH
1) Ship-To-Key
2) Customer No
3) Order No
4) Bill-To Name
5) Ship-To Name
6) Cust Po No
7) Salesman No
8) Inovice No
9) Invoice Date
10) Location
Type: DUPINVIT
Description: Dupl Inv Print Item-Base Info
File: IMITMFIL (Subscribe to Event from Item Master File Maintenance)
Fields: same as INVPRTIT
1) Item No
2) Customer No
3) Ship To No
4) Bill-To Name
5) Ship-To Name
6) Cust Po No
7) Salesman No
8) Order No
9) Item Desc-1
10) Invoice No
Type: DUPINVI2
Description: Dupl Inv Print Item-Pricing
File: IMITMFIL (Subscribe to Event from Item Master File Maintenance)
Description: Dupl Inv Print Item-Pricing
File: IMITMFIL (Subscribe to Event from Item Master File Maintenance)
Fields: same as INVPRTI2
1) Item No
2) Customer No
3) Qty To Ship
4) Unit Price
5) Unit Cost
6) Margin Pct
7) Product Category
8) Order No
9) Item Desc-1
10) Item User Def Cd
There is also a new management event. This event will be triggered one time when the batch of invoices is complete:
Type: DUPINVBR
Description: Dupl Inv Printing Batch Result
File: COMPFILE (Subscribe to Event from Company File Maintenance)
Description: Dupl Inv Printing Batch Result
File: COMPFILE (Subscribe to Event from Company File Maintenance)
Fields:
Record No
Order# Range:
Invoice# Range:
Invoice Date Range:
Salesman Range:
Ship Via Range:
Terms Code Range:
Location:
Customer Type:
Total No. of Inv/CM:
Modified: CPINVPRT.WS, CPINVPRT.PL (CPINVPRT and CPINVPRH re-compiled)
DLM