Attribute

Description

Field type

Microsoft Dynamics 365 for Finance and Operations field

Remark

Warehouse

Warehouse

String(20)

Warehouse

ArticleCode

Article code (SKU)

String(40)

Released product (Released product variant)

Supplier

Number

This is the code associated with your supplier. If more than one supplier exists for an article, use the suppliers file/table, or supply the preferred supplier code only.

String(20)

Primary vendor

Supplier

Name

This is the name of the supplier associated with the code above.

String(60)

Vendor name

LeadTime

This is the time that expires between the point of order and when an item is available for use. This includes the manufacturing time as agreed with the supplier, as well as goods processing, shipping, etc.  Note: The unit in which the lead time is given (days, weeks or months) must be equal to the unit of the review time and consistent for all items.

Num(15,2)

Purchase or production lead time in days. Site specific lead times or default lead times 

If working days: 7/5 * lead time

ReviewTime

This is the time that expires between two points of ordering. Note: The unit in which the review time is given (days, weeks or months) must be equal to the unit of the lead time and consistent for all items.

Num(15,2)

Prio 1: coverage group review time 

Prio 2: primary vendor review time

Supplier

Reliability

This field allows for additional time to be added to the lead time to cover for uncertainty in supply. There are 3 options: a. Add extra lead time (in same unit of measure as the lead time); b. Multiply lead time by a factor (1.xx); c. Deviation of the lead time.

Num(15,2)

Coverage group:

order margin + receipt margin

Supplier

Reliability

Type

Supplier reliability can be given as add (1), multiply (2) or deviation (3).

Integer

1 (add the reliability days to the lead time)

Stocked

Item

This field can be used to separate the Slim4 database into stocked items, non- stocked items and promotion items. Slim4 will calculate forecasts and generate exceptions for all items. Slim4 will only calculate a buffer stock, order level and order suggestions, automatically and continuously, for stocked items. Non-Stocked items will have a buffer stock and order level of zero; order suggestions will only be made if there is insufficient stock (including outstanding purchase orders) to meet customer requirements (back/confirmed future orders). Promotion items need to be set up manually, or loaded through the promotions file, and will be ordered accordingly. Stocked items are identified as “Y”. Non-stocked items are identified as “N”. Promotion items are identified as “P”.

String(1)

Y = Slim4 stock item

N = Slim4 non stock item.

Setting on the Coverage group, field Slim4 services - planning. Promotion items are not identified separately.

NB: the definition of a Slim4 non stock item is not related to the setting Stocked Product on the item model group. 

Item model groups flagged as Stocked product = No are never exported

MOQ

This is the minimum purchase order quantity permitted, as agreed with your supplier. If an entry is given in this field, any order suggestion in Slim4 will be rounded up to at least this value. It is also possible to enter a calculated Economic Order Quantity (EOQ) in this field.  Note: If there is no MOQ data available, this field must be left blank. Slim4 will then use a default value (usually 1, configurable in Slim4).

Integer

Site specific or default order settings Purchase/Inventory: Minimum order quantity

Quantity in purchase unit is converted to inventory units

IOQ

This is the incremental order quantity, to be used once the minimum order quantity has been reached. For any order suggestion in Slim4 that exceeds the MOQ, the order suggestion will be rounded up to multiples of this field, e.g. the MOQ is equal to a pallet quantity, the IOQ can be a pallet layer or the smallest amount permissible on a pallet.  Note: If there is no IOQ data available, this field must be left blank. Slim4 will then use a default value of 1.

Integer

Site specific or default order settings Purchase/Inventory: Multiple order quantity

Quantity in purchase unit is converted to inventory units

EOQ

This is the Economic Order Quantity (EOQ), the optimum order quantity for an item according to rules and limits set by your company. Note: If there is no EOQ data available, this field must be left empty. Slim4 will use a default value of 1.

Integer

Site specific or default order settings Purchase/Inventory: Standard order quantity

Quantity in purchase unit is converted to inventory units

Logistics

Unit1

Number of articles per logistic unit. Smallest till largest. i.e. Consumer Unit, Box, Pallet Layer, Pallet

Integer

Product unit conversion (smallest)or export according to EOQ unit mapping in units

Logistics

Unit2

Number of articles per logistic unit. Smallest till largest. i.e. Consumer Unit, Box, Pallet Layer, Pallet

Integer

Product unit conversion or export according to EOQ unit mapping in units

Logistics

Unit3

Number of articles per logistic unit. Smallest till largest. i.e. Consumer Unit, Box, Pallet Layer, Pallet

Integer

Product unit conversion or export according to EOQ unit mapping in units

Logistics

Unit4

Number of articles per logistic unit. Smallest till largest. i.e. Consumer Unit, Box, Pallet Layer, Pallet

Integer

Product unit conversion or export according to EOQ unit mapping in units

Logistics

Unit5

Number of articles per logistic unit. Smallest till largest. i.e. Consumer Unit, Box, Pallet Layer, Pallet

Integer

Product unit conversionor export according to EOQ unit mapping in units

Logistics

Unit6

Number of articles per logistic unit. Smallest till largest. i.e. Consumer Unit, Box, Pallet Layer, Pallet

Integer

Product unit conversion (largest) or export according to EOQ unit mapping in units

Insurance

Inventory

This is the number of stock units that Slim4 should use to determine the minimum available stock on hand. It is designed to ensure Slim4 will always hold a specified minimum regardless of other factors.Note: This entry is used in combination with the settings options below.

Integer

Empty

Insurance

Inventory

Type

This is the setting that influences how the Insurance Inventory units above are used in Slim4. This field is integer, limited to 1 position, decimals are not permitted. If left empty, the existing setting in Slim4 will be used. Five settings are available (entered into the interface as 0-4): 0 – Add (This will add the number of units above to the Slim4 calculated buffer stock. This guarantees a minimum stock level will always be maintained, on top of the calculated requirement.); 1 – Bottom (This sets a minimum level for the buffer stock. Slim4 will use the larger value out of the number of units above and the Slim4 calculated buffer stock.); 2 – Overwrite (This means the number of units above is used as the minimum, the Slim4 calculated buffer stock is ignored.); 3 – Bottom Order Level (This guarantees a minimum order level. Slim4 will use the larger value out of the number of units above and the Slim4 calculated order level.); 4 – Overwrite Order Level (This means the number of units above is used as the order level, the Slim4 calculated order level is ignored.)

Integer

Empty

Target

Service

Level

This is the Service Level that should be achieved for an item. Every item should have a target service level. It is common to apply the same Service Level to groups of articles on the basis of e.g. ABC classification or product group. If this data does not exist within your ERP system, this field must be left blank. Slim4 will then use a default setting of 95% (configurable in Slim4). An analysis of Service Levels can also be carried out in Slim4, through What-if simulation. The entry in this field must be in the range from 0 to (but not including) 1, e.g. 0.9999.

Num(15,2)

Empty

plcArticle

Code

This is successor item code. The warehouse is the same as for the original item code, in the start of this data set.

String(85)

Alternative item (successor, i.e. this alternative item ALWAYS replaces the current item) Due to limitations in standard, no successor can be specified on a product variant, only on the product master.

plcDate

This is used in combination with the predecessor/successor field above. It defines the end of life cycle date for the predecessor and simultaneously the life cycle start date for the successor.

YYYYMMDD

Empty

plcPerc

This is the percentage relation between a predecessor and a successor item. It can be used to indicate if the relation is not 1-to-1, e.g. due to a change in pack size. When used, it should be given as a “percentage figure”. (Example: 200 on the interface file will result in the successor having two times the demand of the predecessor, e.g. in a case where the pack size has gone from 12 to 6). No percentage signs are permitted, e.g. 80 for 80%.

Num(15,2)

Empty

ABC

This is the ABC classification from your ERP system. If no ABC classification is present or used in your ERP, leave this field blank.

String(2)

ABC class based on revenue

BuyingPrice

This is the buying price per unit.

Num(15,4)

Purchase price at the primary vendor, for one inventory unit, in company currency. The price-per qty (aka price unit) is taken into account. In the Export interface setup - Logistics specify gross purchase price or net purchase price

Trade agreements are evaluated for the inventory unit or for the purchase unit (export interface setup). This price is retrieved again from the trade agreements when Update export data is executed.

MSQ

This is the Minimum Selling Quantity for this item which is used in calculating an order level that is minimized with this value.

Integer

Site specific or default order settings Sales: Minimum order quantity

ISQ

This is the Incremental Selling Quantity for this item which is used in calculating an order level that is rounded with this value.

Integer

Site specific or default order settings Sales: Multiple order quantity

coverDate

Only used in combination with coverSetting value date. The cover period will be adjusted if this date is larger than the caluclated cover period.

Empty

coverSetting

Value for Add(0), Min(1) and Date(2)

Integer

0

coverTime

If filled for "Add" the value wil be added to the coverperiod, if filled with "Min" the largest value wil be used for the cover period

Integer

0

supplierArticleCode

This is the article code used in communicating with your supplier.

String(65)

External item id for primary vendor

replenishmentScheduleId

Replenishment schedule id

String(60)

Empty

inboundGuaranteedShelfLife

Guaranteed shelf life as negotiated with supplier

Num(15,6)

0

outboundGuaranteedShelfLife

Guaranteed shelf life as negotiated with customers or with your shop

Num(15,6)

0

netShelfLife

The difference between ‘Inbound guaranteed shelf life’ and ‘Outbound guaranteed shelf life’. For shops the Outbound guaranteed shelf life will typically be 0 (or 1), as on the date of expiration the item may still be sold..

Num(15,6)

0

productionResource

The production resource

String(65)

Empty

productionResourceName

The production resource name

String(100)

Empty