better (?) place to put display and taxation data than overloading real line items

1 files changed, 33 insertions, 0 deletions

diff --git a/FS/FS/Schema.pm b/FS/FS/Schema.pm
index 0d08abaa0..d354561e5 100644
--- a/FS/FS/Schema.pm
+++ b/FS/FS/Schema.pm
@@ -522,6 +522,39 @@ sub tables_hashref {
       'index' => [ [ 'billpkgnum' ], [ 'pkgnum', 'invnum' ] ],
     },
 
+    #instead of 'duplicate',  'char', 'NULL', 1, '', '',
+    # that way we keep display vs *TOTALLY* out of the table for actual
+    #  finanancial line items
+    'cust_bill_pkg_display' => {
+      'columns' => [
+        'billpkgdisplaynum', 'serial', '', '', '', '', 
+        'billpkgnum', 'int', '', '', '', '', 
+        'section',  'varchar', 'NULL', $char_d, '', '', 
+        #override the linked real one?#'unitsetup', @money_typen, '', '', 
+        #this too?#'unitrecur', @money_typen, '', '', 
+        'post_total', 'char', 'NULL', 1, '', '',
+        'type',       'char', 'NULL', 1, '', '',
+        #any other fields we need to control this display-only line item...
+      ],
+      'primary_key' => 'billpkgdisplaynum',
+      'unique' => [],
+      'index' => [ ['billpkgnum'], ],
+    },
+
+    #and this, to break down a line item into slices for taxation purposes
+    #(instead of creating usage line items for each usage class)
+    'cust_bill_pkg_slice' => {
+      'columns' => [
+        'slicenum', 'serial', '', '', '', '', 
+        'billpkgnum', 'int', '', '', '', '',
+        'amount',  @money_typen, '', '', 
+        'classnum', 'int', '', '', '', '',
+      ],
+      'primary_key' => 'slicenum',
+      'unique'      => [],
+      'index'       => [ [ 'billpkgnum' ], [ 'classnum' ], ],
+    },
+
     'cust_credit' => {
       'columns' => [
         'crednum',  'serial', '', '', '', '',