FDS Inventory Purchases data entry Dialog: 
      		**** Exit to Return ****

Purchase data entry:

1. Enter or Select Inventory item stock number.

         2. Enter Purchase QUANTITY in purchase units.  If purchase units are cases and there are 12 boxes in a case and inventory is maintained in boxes, then one (1) case will expand to 12 boxes added to inventory.  In this example the conversion factor of purchase units to inventory units is 12.

3. Purchase units entered as 500 will be 500.00 and 5.00 is the same as 5.00. 

4. Enter Inventory Units in the second quantity field.  Entering 6 (or 6.00) will assume six boxes.  Following the above example, six (6) boxes will be the same as ½ (one half) case.  If 5 is entered in the first quantity field and 6 in the second 5*12 + 6 or 66 boxes will add to inventory.

5. When the amount is entered, the purchase is added to the purchase list.  When all purchases are entered, select ACCEPT to accumulate these purchases to the inventory purchases database.  Purchase will not accumulate to the inventory Quantity On Hand (GOH) until purchase are posted.

When purchases entry is complete, select ‘ACCEPT’.  The items in the right side list then updated the INV-R database.  A file is made of all entries, and this file is displayed when the ‘ACCEPT’ control is taken.  The batch file can be read back into the dialog (entry screen display) by selecting ‘Read File’.  This file can be transported to other facilities and read into the system.  Upon ‘ACCEPT’ on the read file, the local INV-R is updated.

Update Purchase Records (Modify or Add New):

1. Most information regarding purchases is contained in the item inventory records.  

Concept of process:

1. The FDS Inventory information is stored in the INV-R database.  The database is segmented based on data function in the following manner:
a.	Stock records (FDS_Maintenance.exe).
b.	Sales records (FDS_Sales.exe).
c.	Purchase records (FDS_Maintenance.exe).
d.	Waste and Transfers In & Out (FDS_Waste.exe).
e.	Explosion records (FDS_Explosion.exe).

Other modules produce reporting, merge data files, start new cycles, compute shortages, etc.

 Cautions:

a.	Perform events in the right sequence.
b.	Be careful that conversion units between purchases and inventory are correct.
c.	Maintain backup of the INV-R database.
d. Maintain backup of the file maintenance batches.