4.2.4. Orders to Ship

To calculate future on-hand inventory more accurately, Streamline can account for information on orders to be shipped to the customers. It describes the items that are on open sales orders or back-orders.

The data types, describing a line in these orders, are shown in the table below.

Data name	Description	Datatype
Item code	The item identifier, also known as SKU.	String
Qty to ship	The item amount that should be shipped to the customer.	Integer
Shipment date	The date when the item should be shipped to a customer. In the case of backorders, this can be some promised date.	Date or DateTime
Location	(Optional). The location where the shipment has been done (or will be done) from. It should be given if you use locations.	String
If the Shipment date is not given, Streamline treats that as if the sales order has been already sent out to the customer and deducts the Qty to ship from the On hand quantity when calculates the ordering plan. If the On hand amount is not enough, Streamline will order the difference.

Bill of Materials

The bill of materials information describes the components of finished products. Components can be considered as sub-assemblies (at the intermediate levels of the production process) or as raw materials (at the lowest level of the process). You can import an unlimited number of assembly levels.

Streamline also supports material requirements planning for batches. I.e. when a BOM describes ingredients that are used to produce several finished products.

To get a material requirements plan, you should provide Streamline with the data types shown in the table below.

Data name	Description	Datatype
Finished good's code	The code of a finished product or a sub-assembled item.	String
Material's code	The material's or component's code.
Material qty/batch	(Optional) The quantity of a material or component that is required to produce the batch of the Finished good's code. If it is not given, it equals 1 by default.	Integer
Batch rounding	(Optional) The batch size multiple, an integer that defines the quantity to which the quantity to manufacture is rounded up. The modified quantity is then divisible by the Batch rounding. For example, if Streamline determines to manufacture 120 units of a finished good, and Batch rounding is 50, the final quantity to manufacture will be 150. If Batch rounding is not given, it is 1 by default.
Manufacturing lead time	(Optional) The time required to manufacture the Finished good's code of the quantity determined using the Batch rounding parameter. It should be given in days. If it is not given, it equals 0 days by default, and the manufacturing process is instantaneous.
Min batch	(Optional) The minimal quantity of the Finished good's code to manufacture. For example, if Streamline determines quantity to manufacture as 5 and Min batch is 10, then the final quantity to order will be 10. If it is not given or equal to 0, this constraint is not applied.

Tracedump:

newBaseSize: 16pt
newBaseSizeInPt: 16