Materials parameters

Materials parameters are related to assets, inventory, and pricing features that must be set for the features in the application to work properly.

Set values for materials parameters according to the following table.

Code	Description	Fixed
ASSETASS	This code indicates whether to associate an asset with parts tracked by asset during receipts (`R`) or during creation of a purchase order (`P`).	No
AUTOPART	This code determines whether the system automatically updates the Parts Associated list. Update the Parts Associated list for approved lines on a receipt. If `AUTOPART` is set to `AUTO`, the system verifies whether the received part is associated with an equipment’s Parts Associated list when a purchase order receipt is approved for a work order. If the received part is not associated with the equipment’s Parts Associated list, the system adds the part to the list using the quantity of the transaction as the Parts Associated quantity. If the part is already associated on the Parts Associated list, then the system updates the quantity of the part on the Parts Associated list to the transaction quantity if the transaction quantity is greater than the existing quantity on the Parts Associated list. If the transaction quantity is not greater, then the system does not make any updates. Also applies to issues, not just receipts.	No
AUTOPNUM	This code indicates whether the system automatically generates part numbers. Example: NO	No
AUTOSTOK	This code indicates whether the system automatically creates records in tables `R5STOCK` and `R5INSTOCK` (+) for data collection. Example: Yes	No
CHILDTXN	If the user issues or returns a Track by Asset part that has a Track by Asset child part, the system will create a record of the transaction for the child part based on the setting of CHILDTXN.	NO
DEFLDTIM	Default item lead time (in days) to use for calculation of Requisition Requested Before date and Purchase Order Due Date.	No
DEFSTOCK	This code indicates whether the stock management fields (e.g., reorder level, min/max, order level, etc.) should be copied from the highest-level parent store to the child store when a stock record is created in the child store. Example: YES	No
DEFRQTP	Determines the default line type for requisitions. Specify a user status equivalent to the system status of`PS` (Stock Parts), `PD` (Direct Purchase), or `RE` (External Repair) for the `PLTP` entity. The line type is automatically defaulted to the specified user status. If `DEFRQTP` is null or if you enter an invalid value, the line type of requisitions is automatically defaulted to the system status of `PS`.	No
DEFUOM	Base unit of measure for transactions, such as store issues and returns. Changing this default will not affect existing data. However, Infor strongly recommends using `EA` (Each) or `PEC` (Piece, e.g, individual part) as the base unit of measure because of the part-by-asset mechanism. Example: EA	No
DELTMATL	Delete materials list. Valid values are `Y` and `N`. `Y` implies that the system will remove the temporary material lists upon completion of the related work order. `Y` also indicates that after completion, the estimated material costs will no longer include data from the temporary material lists. `N` implies that the system will not remove the temporary material lists. Example: Y	No
ENABLEOS	URL for the OneSource server.	No
IPSUPP	Determines the value of the Part Org. when a new part is created via the iProcure interface. Set to `H` for the Part Org. to come from the Requisition or PO header. Set to `S` for the Part Org. to come from the Supplier. Set to `C` to use the common org specified in the `IPSUPPC` install parameter. Example: H	No
LOTNRG	Lot number generation. This code indicates how Infor EAM should generate lot numbers. Valid values are `T` (each receipt), `P` (only parts that are tracked by lot), or - (no lot numbers; lot number * is always used). It is possible to change this parameter in a live installation; however, Infor strongly recommends determining a lot-numbering policy before entering data. Changing the value does not affect existing data. Example: P	No
MOBSHWRV	Specify if mobile will do a blind receive of parts on the Active Lines for PO Receipt. Specify YES to show the expected Receipt Quantity. Specify NO to hide the Receipt Quantity.	No
OBSTCASC	This code indicates whether parent equipment status changes of I (Installed) or D (Withdrawn) will be cascaded to the child equipment. If set to `A`, parent equipment status changes are cascaded to all children. If set to `D`, only parent equipment status changes are cascaded to dependent children.	No
OSTAXUSR	Value for the OneSource username.	No
OSTAXPWD	Value for the OneSource Password. The user will key in the OneSource user password. The user will then click Save and the system will encrypt the entered value.	No
OVERRECV	Indicates whether you can receive more parts than the number of parts originally ordered. If set to `YES`, you can receive more parts than the number ordered. If set to `NO`, you cannot receive more parts than the number originally ordered.	No
DRCPTTO	This code indicates whether the system receives direct on-dock materials directly to stores or against a work order. Example: STORE	No
PICKONCE	This code indicates whether the system can issue multiple work orders against the same pick list. For example, if this parameter is set to `YES` and you have a pick list associated with a work order and the pick list includes four items for which you only issue one item for the pick list, you can no longer issue items against that pick list again. If the parameter is set to `NO`, you can still issue against the remaining three items on the pick list.	No
PLNDRQPO	This code indicates whether requisitions and unapproved purchase order totals are included in cost summaries for project reports. If the value is `ON`, then the system includes the cost of requisitions or unapproved purchase orders in the calculation of the total displayed in Planned throughout the system, as well as estimated work order costs that are not yet linked to a requisition or purchase order. If the value is `OFF`, the system does not include the cost of requisitions or unapproved purchase orders in the calculation of the total displayed in Planned throughout the system. The value for Planned is calculated based only on estimated work order costs. Purchase orders with Approved status are displayed in On Order throughout the system until they are Received. However, after purchase orders are received, the purchase order costs are displayed as Actual and used in the calculation of Estimate to Complete. The system calculates Estimate to Complete for project costs based on the following formula: Current Estimate to Complete – (Planned + Actual)	No
POSTALLR	Auto status for the DOST entity for full PO receipts. Specify a user status equivalent to the system status `A` (Approved) for the `DOST` entity, and the system automatically changes the purchase order status to the specified value when all the lines on the purchase order are fully received or canceled. If the purchase order header status is already set to the status defined in this parameter, then the system does not modify the purchase order status. Note: If you have set the `POSTALLR` parameter, then the processing rules associated with the `POSTALLR` parameter overrides the rules for the `POSTRECV` parameter.	No
POSTRECV	Auto status for the `DOST` entity for PO receipts. Specify a user status equivalent to the system status `A` (Approved) for the `DOST` entity, and the system automatically changes the purchase order status to the specified value when one or more lines on the purchase order are partially received. When a `RECV` transaction is approved for a part associated to a purchase order, the system updates the purchase order header status to the specified status. If the purchase order header status is already set to the status defined in this parameter, then the system does not modify the purchase order status. Note: If you have set the `POSTALLR` parameter, then the processing rules associated with the `POSTALLR` parameter override the rules for the `POSTRECV` parameter. Example: A	No
PRICELEV	Price level. This code indicates whether prices must be kept at part level (same part prices for all stores) or at store level (part can have different prices in different stores). Valid values are `P` and `S`. You cannot change this setting once in use.	Yes
PRICETIM	Pricing updates. This code determines when the system updates average unit price and last purchase price. Valid values are `I` (calculate new price at invoice approval) or `R` (calculate new price at receiving approval on basis of PO prices.) Inconsistencies in data will occur if you change this value. After a change, some prices will still be based on the old mechanism while others will be based on the new mechanism. Over time (usually the amount of time required for a complete inventory turnover), a shift will take place from the old mechanism to the new. If the price type of a stock record in the `R5STOCK` table is LIFO or FIFO, Infor EAM calculates pricing updates when you approve a receipt regardless of the setting of this parameter. However, if the setting of this parameter is `I`,Infor EAM calculates pricing updates again when you approve an invoice and/or credit/debit note. Note: This parameter is not fixed however Infor strongly discourages changing this setting. Example: R	No
PRICETYP	This code determines the default value for Price Type when creating stores and indicates the manner in which the system prices storeroom materials at the store level. Valid values are `A` for Average price, `FIFO` for First in first out, `L` for Last price, `LIFO` for Last in first out, and `S` for Standard price. `LIFO` or `FIFO` pricing is a time-based pricing method; therefore, you should only set `PRICETYP` to `FIFO` or `LIFO` on the store record if you have selected to keep prices at store level. (See `PRICELEV` earlier in this section.) Note: This parameter is not fixed however Infor strongly discourages changing the price type setting because inconsistencies in data may occur. See the `PRICETIM` parameter. Example: A	No
PROJTRCK	Budget tracking for projects. This code indicates whether Cost Area, Cost Center, and Code of Accounts are displayed and enabled on the Budgets tab of the Project form. Cost Area, Cost Center, and Code of Accounts enable you to track project costs and budgets more precisely by associating cost areas, cost centers, and codes of accounts with budget codes, as well as enabling project and financial managers to access more detailed information about project budgets on project reports. Cost Area, Cost Center, and Code of Accounts are linked to the `PRCA` (Cost areas), `PRCC` (Cost codes), and `PCOA` (Code of accounts) entities. You can define cost areas, cost codes, and codes of accounts as user codes as necessary based on your project budget tracking preferences on the System Codes form. Example: ON	No
RECVAUTO	This code indicates whether the system should automatically populate the quantity to receive on purchase order receipts. If `RECVAUTO` is set to `YES`, the system automatically populates the Receipt Qty. (UOM) on the Active Lines page of the PO Receipts form with the outstanding quantity for each line on a purchase order receipt. If `RECVAUTO` is set to `NO`, a value must be manually entered for the receipt quantity for each line on the receipt. Example: YES	No
REQDESC	Default requisition description. Changing this value does not affect existing data. Example: Requisition	No
RPPRCCAL	This code indicates whether price calculations should be performed when receiving internally repaired spare parts. Example: NO	No
RQSTALLR	Auto-status for the `RQST` entity for full PO receipts. Specify a user status equivalent to the system status `A` (Approved), and the system automatically changes the requisition status to the specified value when all lines are fully received or canceled for a PO receipt. When a `RECV` transaction is approved for a part associated to a purchase requisition via a purchase order (the system does not consider receipts for store to store requisitions) and all of the requisition lines on the requisition are fully received or canceled, then the system updates the requisition header status to the specified status. If the requisition header status is already set to the value defined by this parameter, then the system does not modify the status. Likewise, if all the lines on a requisition are canceled and none of the lines have been received, then the system does not consider the setting of this parameter.	No
RQSTRECV	Auto-status for the `RQST` entity for PO receipts. Specify a user status equivalent to the system status `A` (Approved), and the system automatically changes the requisition status to the specified value when one ore more lines are partially received for a PO receipt. When a `RECV` transaction is approved for a part associated to a purchase requisition via a purchase order (the system does not consider receipts for store to store requisitions), then the system updates the requisition header status to the specified status. If the requisition header status is already set to the value defined by this parameter, then the system does not modify the status. Likewise, if all the lines on a requisition are canceled and none of the lines have been received, then the system does not consider the setting of this parameter. Example: A	No
RRISSWAR	This code indicates whether Infor EAM should generate a warning message to check whether you need to create a work order for a spare that has failed when you issue a repairable spare part on the Issue/Return Parts issues form. Example: YES	No
RTNANY	The `RTNANY` parameter indicates whether you can return a greater quantity of a part than the original issue quantity of the part, and/or whether or not the system allows you to return a part to a different store than the store from which it was issued. If `RTNANY` is set to `YES`, you return any quantity of any parts to any store for which there is a part record on the Stores tab of the Parts form (the system only requires that a part record exists for the part in the store, not that a bin-stock record exists for the part in the store). If `RTNANY` is set to `NO`, you cannot return a greater quantity of a part than the original issue quantity. The system only allows you to return the quantity of the part that was originally issued to that entity to the same store, bin, and lot. When issuing a part, you issue to an entity (work order, equipment, etc.) from a store. When returning a part, you return from an entity (work order, equipment, etc.) to a store. For example, if `RTNANY` is set to `NO` and if you issue 20 parts to a work order for a piece of equipment on the work order, you can only return those parts from the work order. You cannot return the part directly from the equipment. The `RTNANY` parameter indicates whether you can return a greater quantity of a part than the original issue quantity of the part. If `RTNANY` is set to `YES`, you can return a greater quantity of a part than the original issue quantity. If `RTNANY` is set to `NO`, you cannot return a greater quantity of a part than the original issue quantity.	No
SHOWQTY	This code indicates whether to show the expected quantity for Infor EAM Mobile physical inventory. Example: NO	No
STTKDISC	Physical inventory discrepancies. This code indicates how the system handles physical inventory discrepancies for parts tracked by asset when signing off physical inventories on the Physical Inventory form. Valid values are `1`, `2`, or `3`, with `2` being the default value. You can change this value. If the value is `1`, the system ignores physical inventory discrepancies for parts tracked by asset. If the value is `2`, the system ignores physical inventory discrepancies for parts tracked by asset, but prints the discrepancies on the sign-off document. If the value is `3`, the system disables signing off stock-takes for parts tracked by asset.	No