Attribute

Description

Field type

Microsoft Dynamics 365 for Finance and Operations field

Remark

Transaction

Number

Transaction number, for example a delivery note number, receipt number or sales order number. Multiple SKUs can be part of this transaction.

String(50)

Packingslip or transfer order voucher or production BOM line voucher

and line record ID

Unique

Transaction

Type

Type of the transaction and is a number. This type can be used to filter or exclude certain transaction types from the historical demand. It can also be used to distinguish the extended demand channels.

For example, returns are transaction type 1, sales to customers are transaction type 2 and inter-branch deliveries are type 3. For plotting the demand pattern, we exclude type 1, type 2 and 3 both have a separate extended demand channel and sum to the total demand that serves as the basis for the forecast.

String(50)

2=Sales

3=Transfer shipment

4=Production BOM line

Transaction

Name

Name of the transaction type for clarifying the types given in the 'Transaction type' field.

String(50)

Sales order

Transfer shipment

Production order

Transaction

Status

Status of the transaction. For example, is it an active transaction (the articles are already delivered, but no invoice is send) or a completely processes transaction (the articles are delivered and the invoice is send).

String(50)

Deducted (packing slip posted) or Sold

Warehouse

Warehouse

String(20)

Warehouse

ArticleCode

Article code (SKU)

String(40)

Released product (Released product variant)

IssueDate

Actual date of the physical goods movement. This date is used to set up the historical demand in time buckets.

YYYYMMDD

Physical date of the inventory transaction

RequestedDate

Delivery date confirmed to the customer. This can be used for delivery performance reporting.

YYYYMMDD

Sales: date that was confirmed to customer

Production: raw material date

IssueQuantity

Actual quantity delivered on the issue date. This quantity is used to sum up in the historical demand fields.

Num(38,15)

Issue quantity (-1 * summarized inventory transactions status delivered or sold)

LineNumber

Line number of the transactions

String(50)

Line number *1000

Confirmed

Quantity

Quantity confirmed to the customer, to be delivered on the confirmed date. This can be used for delivery performance reporting.

Num(15,4)

Sales: quantity confirmed to customer

Transfer shipment: original quantity

Production BOM: startup quantity

Requested

Quantity

Quantity requested by the customer, to be delivered on the requested date. This can be used for delivery performance reporting.

Num(15,4)

Sales: quantity requested by customer

Transfer shipment: original quantity

Production BOM: estimated quantity

Customer

Number

Unique customer ID number.

String(25)

Sales: Customer ID

Transfer shipment:To-warehouse

Production BOM line: work center ID

Customer

Type

In this field, the type of customer is represented. It can be used to make a customer segmentation in historical demand. For example: Business types (B2B, retail, or export) or Regions (EMEA, APAC, or America).

String(50)

Customer group

Customer

Name

Name of the customer belonging to the unique customer ID number.

String(100)

Sales: blank (or organisation name if export GDPR data = yes)

Transfer: to warehouse

SalesPrice

Sales price on the demand transaction can be given. Price per piece

Num(15,4)

Sales amount / quantity

Delivery

Location

Location where the articles of the transaction are delivered to. For example: Deventer, 7418 AH, The Netherlands

String(255)

City and country (or organisation address if export GDPR data = yes)

Supplier

Number

Unique supplier ID number. Usually this is the number of your current primary supplier. However, in case of cross-docking, this can be the supplier of your cross-docking order.

String(25)

Sales: vendor linked to the sales line.

Else primary vendor

Supplier

Type

Type of supplier is represented. It can be used to make a supplier segmentation in historical demand. For example: OEM, distributor, or factories.

String(50)

Vendor group of this supplier

Supplier

Name

Name of the supplier belonging to the unique supplier ID number. Usually this is the name of your current primary supplier. However, in case of cross-docking, this can be the supplier of your cross-docking order.

String(255)

Vendor name of this supplier

BuyingPrice

The buying price of the order can be given. This is usually the unit price of the stock. However, in case of cross-docking, this is the actual buying price of the transaction. Price per piece

Num(15,4)

Cost price per unit

Depends on costing model

Supplying

Location

Location from where the articles are delivered. However, for cross-docking orders, this is the location of the supplier.

String(255)

Supplied from city and country

Conversion

Factor

Conversion factor can be necessary because some ERP systems do not have negative transactions, but returns should be converted to a negative demand. Or the transaction is in Meters and Slim4 in Centimeters.

Num(38,15)

Empty

Transaction

FreeField1

Free field, some extra information on the transaction can be added.

String(255)

Field mapping

Transaction

FreeField2

Idem

Idem

Field mapping

Transaction

FreeField3

Idem

Idem

Field mapping

Transaction

FreeField4

Idem

Idem

Field mapping

TransactionIssueTime

Actual time of the physical goods movement hh:mm

Time hh:mm

Sales packing slip posting time

Transfer packing slip posting time

Raw material time

LinkedTransactionNumber

Linked transaction number

String(50)

Empty