9


Rows 11 and 12 could then be changed to products by entering a '2.0' in

column 17 for these rows.

 To more fully illustrate the preparation of part 6 of the input form,

the coding of the sample corn grain budget shown in Appendix VI is dis-

cussed in the following sections.

 Production Data. The first 10 rows of part 6 of the input form are

typically used for specifying the products of the enterprise, such as

grain, grazing, etc. For the corn grain example shown in Appendix VI

the only product considered is 75 bushels of corn grain produced in August.

The appropriate entry for this product is, therefore,

 Col. 8 Col. 13 Col. 15 Col. 16
 Line No. Aug. Price Units Item

 (1) Corn 75. 2.40 2. 104.

 The '75.' in the August column (8) indicates that 75 units of the product

 are produced in August. The '2.40' entered in the Price column indicates

 that the product is sold at $2.40 per unit. The '2.' entered in the Units

 column is the code for bushels (Appendix V), indicating each unit.of

 product is measured in bushels. Thus, 75 bushels of corn grain are pro-

 duced. From the name list (Appendix III) it can be seen that the code for

 corn is '104.' which is entered in the Item column to identify the product

 under consideration. For this example, with only one product in one month,

 no other entries are made in rows 1-10.

 Should the user wish to use the price contained in a previously

 selected price vector (see sections on Processing System Selection and

 Budget Identification Number) for corn grain, a '-1.0' would be entered

 in the Pricecolumn (13) instead of '2.40'. The entry of '-1.0' will cause