Laddawn.com : Samples Orders - Technical Design

Meeting w/Susan, Tina and Cathy - 6/9/15:

1. Reviewed Susan's wiki document - refer to revised version after today
2. We will provide a load program to be run yearly to load up the sample bank for each sales organization - will probably be a calculation using prior year sales$.
3. Conversion program will be required when we go live (mid-year) to convert the samples used thus far
4. When creating the sample bundle - see if primary warehouse has at least 1 case or roll of inventory for every one of the sample items.  If not, look at alternate.  Do not split up a sample bundle between warehouses.  If alternates don't have enough inventory, create the bundle for the primary warehouse with +72 hour date.
5. Investigate which is easier:  Showing 15.00 for each sample item, then reducing it by the available sample bank in the cart total - or show 0.00 price for the samples that will be handled by the bank
6. Figure out the best way to have a mixed cart that includes stock, MOD and samples (must allow item 480 to be ordered in cases and also get a sample of item 480).  Possibilities:
   1. Add a "-S" to the end of the sample item# (000480-S or 000480S) when writing to the cart
   2. Put the sample item numbers into a new set of fields in the cart - the shopping cart getbyfilter would have to put them back together (but probably won't be in the same order they were originally entered)
7. Which is easier on the checkout labeling screen: showing sample items in a different format (just a disclaimer saying these are samples and disabling all boxes below) or not showing sample lines at all in the label display

Current Sales Order Acknowledgement:

Current Invoice:

6/17/15 - meeting w/John, where we decided:

1. A new multi-valued field associated with item numbers in field 1 will be added:  SAMPLE.ITEM - it will contain a 1 if the item# in the associated multi-value in field 1 is a sample.
2. RPC$SHOPPINGCARTITEM_ADDTOCART - Add a sample - or add "1" if sample already exists.
3. The RPC$SHOPPINGCARTITEM_SAVE will be modified to write the sample flag - the UI will pass a new named param SAMPLE.ITEM indicating that this was selected from the sample tab
4. On the UI side - they would have to keep the part numbers unique by prefixing the sample item with an "*" - this way we could have part# 000500 and sample part# 000500
5. DATAFIELDS pass from ORDERITEM.READ and SHOPPINGCARTITEM.READ would have to pass SAMPLE.ITEM to UI (from new shopping cart field or from the order itself).  The UI will handle adding "- Sample" to the end of the item description that is passed from the database.  What about the UOM?
6. RPC$SHOPPINGCARTITEM_GETBYID - pass sample flag.
7. Pricing - Because the first sample item in a cart is priced at 20.00 and the remaining samples in the cart at 10.00, we would have to locate the sample item in SHOPPINGCART.USR to determine if it's the first sample in the cart and assign price accordingly.  IN SHOPPINGCARTITEM.READ - ONLY SEND BACK 20.00 IN EXT.PRICE.
8. RPC$SHOPPINGCARTITEM_DELETE - if SAMPLE.ITEM is true, delete the sample item from SHOPPINGCART.USR else delete the real item from the cart.
9. VALIDATE_ADDTOCART - If they are adding a sample item from the results 'sample' tab, make sure that sample isn't already in the cart.  If it is, error saying they must change the quantity in the cart.  If they are adding a regular item to the cart, make sure that if the non-sample item is found, that is the one that we are updating the quantity on.  Do not update the sample item when the regular item is added to the cart.  *** INSTEAD OF ERROR, JUST ADD TO THE QTY BUT DON'T EXCEED 3 - THEN WE ERROR.
10. Validation on the cart quantity - max quantity of 3 for sample items. *** will ui call a validation routine?  Write a new RPC$SHOPPINGCARTITEM_VALIDATEQTY for all items.  Will need sample flag.
11. Uom - Bags or Feet: PRODUCTITEM.READ - field called singular UOM. BAG, FEET ... only used for samples. - If not(continuous) we pass Bags else Feet.  If perf sheeting we pass Sheet.  Maybe store in CATALOG.CD.USR.  If the UI doesn't get a singular.uom then don't display the tab (UI).
12. Question: are we modifying the Avante optio ackn form - we will be obsoleting it in the near future.  *** yes, it is needed for Fax customers and Re-prints.
13. Make sure that CE can override a sample price to 0.00.  Currently they have to enter at least .01.