DIH Work Order

Imports Work order definitions.

A work order has the following objects:

•	Work order header

•	Work order position

•	Work order bill of materials and routing position

Example:

The old system contains all item, bill of materials and routing information. This data can be imported with the integration hub. After this is complete, work orders can be imported.

Only the top level assembly can be defined. Beas reads bill of materials and routing information from imported master data.

It is not possible to import routing or bill of materials for every work order separately.

import_workorder1

A third-party application can define the work orders in Beas. You can use this option if you have an external planning tool for production in stock.

import_workorder2

import_workorder3

Example: A machine needs to be produced and while producing the technical planning continues. You can import and synchronize the bill of materials in the work order directly from the CAD program.

Area

Insert

Update

Work order header (BEAS_FTHAUPT)

Use this if you want to update the header information or if you want to create new work orders and you need only the item code and quantity for the work order position.

Inserts all header information.

Inserts first work order position with item code and quantity.

Beas explodes the bill of materials, routing position and all order-related sub-assemblies.

Note:

Creating reference to other documents or changing any properties in the work order line is not possible.

You can change the work order type, but it is not possible to change the work order type related flags; Beas ignores these changes.

You cannot define the document number (BEAS_FTHAUPT.BELNR_ID), only the order number (BEAS_FTHAUPT.AUFTRAG).

Most properties are changeable, but you cannot change the created work order positions.

Beas will ignore the item code and quantity property.

Work order position (BEAS_FTPOS)

Use this to import work order positions with extended position information.

The assembly can be defined, but Beas always uses the BOM and routing information from item master data.

Add position to existing work orders.

Beas explodes the bill of materials, routing position and all order-related sub-assemblies.

If you do not define a work order number, Beas creates a new work order (BELNR_ID=0).

It is not possible to define additional information for work order header if the system creates a new work order.

Defines linked information.

It is not possible to update existing positions.

Bill of materials (BEAS_FTSTL)

Use this to synchronize the BOM with external programs.

you can add and change bill of materials position of existing work order positions.

The work order document number, work order position and bill of materials position are mandatory.

When trying to insert an exiting BOM position, Beas updates the position.

Beas does not explode order related assemblies. Multilevel work orders cannot be created.

All properties of an existing bill of materials position can be updated.

Beas does not change existing sub-position.

You can delete a BOM if you set the quantity to 0, but only if no related transaction or reservation exists.

Routing position

Not possible.

Imports Work Order Bill of Materials definitions.

The following fields are mandatory:

•	Document number, work order position number, bill of materials position number

•

Quantity

Entries can only be changed if changes are allowed and the work order position is not closed.

Position numbers:

•	The internal position number. If this is a new number or if it is 0, Beas creates a new position.

•	If you do not set the position text, Beas sets the position number in position text.

•	The internal position number does not define the sorting. You must define this separately. See Sorting rules.

Position text:

•	If this is not set manually, Beas inserts the defined or generated internal position ID.

•	It can be defined and changed every time.

ItemCode:

Item code is mandatory and the item must exist.

The integration hub does not check additional rules.

If you change the item and the related position, reservation or transactions exist, Beas does not change anything.

Note: If you insert an order-related item, Beas does not create an order-related sub-position.

ItemVersion:

The system check, if the Item Version is existing and not locked

But it's allowed to use it, if not released.

Quantity:

Rules for quantity in the BOM import:

•	A value > 0 inserts a positive amount.

•	A value < 0 inserts a negative amount.

•	A value of 0 deletes an existing position. See Delete a bill of materials position.

•	A value of +0 adds a position with 0 amount.

If you only have 0 quantity in the importfile, you can convert the value

DIH_import_zero

Delete a bill of materials position:

It is possible to delete an existing Bill of materials position. Beas requires the following fields: BELNR_ID,BELPOS_ID and POS_ID and Quantity=0.

•	If any transaction exists on this position, the position cannot be deleted.

•	If a reservation exists, Beas deletes the reservation.

•	If the position is an order-related assembly, Beas deletes all related sub-positions.

•	If a deletion of a sub-position is not possible, Beas closes all related sub-positions.

Sorting (SortId):

Defines the sorting for the bill of materials positions. You can define a positive number or special sorting rules.

Sort Id	Description
-1	Order by internal position number. The system searches by position, and chooses a number that is lower than the current position and higher than the lowest existing position. It receives this sortid, increments it with 1 and defines it as a sortid from the current position. Example: Pos 10 – Sort 10 Pos 20 – Sort 20 You insert Pos 15 Pos 10 – Sort 10 Pos 15 – Sort 11 Pos 20 – Sort 20 This is a fast variant, because Beas must only insert Pos 15, but in other situations this can generate a problem. Example: Pos 10 – Sort 1 Pos 20 – Sort 2 You insert Pos 15 Result in MSSQL: Pos 10 – Sort 1 Pos 15 – Sort 2 Pos 20 – Sort 2 Result in HANA: Pos 10 – Sort 1 Pos 20 – Sort 2 Pos 15 – Sort 2 In this case Pos 20 and Pos 15 have the same Sort id and it is not clear which position is the first position.
-2	Order by internal position number. In this case Beas sorts the complete bill of materials position by internal position number Beas must save every change from every bill of materials position. In case a large number of positions must be inserted, this concept produces a lot of change requests. Do not use this for mass import. Example: Pos 10 - Sort 10 Pos 20 - Sort 20 Pos 30 - Sort 30 You insert Pos 15 Pos 10 – Sort 10 Pos 15 – Sort 20 <- insert Pos 20 – Sort 30 <- update Pos 30 – Sort 40 <- update
-3	Order by position text (alphanumeric). Example Pos Text A10 Sort 10 Pos Text A20 Sort 20 Pos Text A50 Sort 30 You insert position with Pos Text = A30 Pos Text A10 Sort 10 Pos Text A20 Sort 20 Pos Text A30 Sort 20 <- insert Pos Text A50 Sort 30 <- update Attention: You can encounter the following issue when working with numbers: Example Pos Text 10 Sort 10 Pos Text 20 Sort 20 Pos Text 100 Sort 30 Insert Position Pos Text = 50, and the result (alphanumeric sorting) is the following: Pos Text 10 Sort 10 Pos Text 100 Sort 20 <- update Pos Text 20 Sort 30 <- update Pos Text 50 Sort 40 <- insert
-4	Order by position text (converted to number) Example Pos Text 10 Sort 10 Pos Text 20 Sort 20 Pos Text 100 Sort 30 You insert position with Pos Text = 50 Pos Text 10 Sort 10 Pos Text 20 Sort 20 Pos Text 50 Sort 30 <- insert Pos Text 100 Sort 40 <- update If you insert a position with alphanumeric position text, Beas sets this to first position. Example: insert position with text A001 Pos Text A001 Sort 10 <- insert Pos Text 10 Sort 20 <- update Pos Text 20 Sort 30 <- update Pos Text 100 Sort 40 <- update

Help URL: https://help.beascloud.com/beas202105/index.html?dih_work_order.htm