Technical Sheet plan

• Site (field FCY)

It is for this site that the tracking is carried out.
This field is initialized with the production site associated with the operator.

• Employee ID (field WEMPNUM)

This field corresponds to the Labor operator.

• field EMPDES

• Tracking start date (field WMTKDATD)

This field is used to select the operation trackings whose creation date is included in the date range that is being searched.

• Tracking end date (field WMTKDATF)

• Production tracking (field WTRKNUMD)

This field is used to filter the search by production tracking number.

• field WTRKNUMF

• Operation (field WOPENUMD)

This field is used to filter the operation tracking lines based on their operation numbers.

• field WOPENUMF

• Work center (field WWSTD)

This field is used to filter the operation tracking lines based on the work center.

• field WWSTF

• Tracking number (field MFGTRKNUM)

The WO tracking is identified by this unique number.
It is automatically generated upon each creation.

• Tracking type (field TIMTYP)

This field can take the following values:

• WO: the declared time concerns a WO operation,
• product: the declared time concerns a routing operation,
• miscellaneous: the declared time concerns time on a work center.

• Order no. (field MFGNUM)

This field displays the work order number (unique ID).
This number is automatically or manually generated upon each creation.
Click the Selection icon to open the list of work orders (which only includes 'Firm' or 'Closed' work orders) and select a work order.

• Routing (field ITMREF)

This field indicates the product reference code. It is generated by a sequence number counter (set up in function Sequence number counters) in the case when the product category has a sequence number counter code.

The reference cannot be modified. It is automatically assigned and displayed when the product creation is complete.

• Code (field ROUALT)

Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality (for use in a manufacturing environment, for costing or for capacity planning).

• Technical sheet (field TECCRD)

This field indicates the technical sheet name.

• Operation (field OPENUM)

The production routing is described by means of operation numbers.
Each operation corresponds to a task carried out on a given resource, with given times.

• Split (field OPESPLNUM)

The field corresponds to the operation fraction number.

• Std oper (field STDOPENUM)

The standard operation is a "template" operation used to create or modify the routing operations.
The definition of the fields of a standard operation is very similar to that of a routing operation.

Recover the standard operation data:

• if the operation unit is mentioned in the standard operation, it is used again, otherwise, the stock unit of the product in the routing is used.
  If not entered, the conversion coefficient is extracted from the coefficient table
• The times (rate, setting time and operating time) are converted if the time unit of the routing header is different from that of the standard operation.
  The standard operation is referenced in the operation that called it as a template.

 When modifying a standard operation, the modifications are not passed on to the associated operations.

• Type (field WSTTYP)

The type of a work center can be either machine, labor or sub-contracting.
The work centers of "sub-contracting" type are used to manage the operations carried out externally by sub-contracting suppliers.

• Actual work center (field CPLWST)

This field indicates the actual work center.
The work center is attached to a work center group. It corresponds to a production resource on which a routing operation has been carried out.  
 

• Description (field WSTSHO)

This field specifies the "short" description of the work center.

• Actual labor W/C (field CPLLAB)

A labor work center can be associated with the machine-type principal work center.

The labor work center times are calculated using two coefficients:

• setting coefficient,,
• operating coefficient applied to the setting time and to the operating time of the main work center.
  A control is applied to verify that the attachment site for the work center is the same as the site dedicated to the BOM code.
  

• UNIT (field OPEUOM)

The operation unit expresses the operating time in another unit than that of the product described by the routing.

Example :

A product managed by unit can be subject to three operations, without any intermediate stock. It is not necessary to create semi-finished products for each production phase:

• Mixing: time is expressed for a lot with the kilogram as the unit,
• Extrusion: time is a rate in meters per hour,
• Cutting: time is expressed in hours per unit.

This unit is associated with a conversion coefficient for the stock unit of the product for which the routing has been set up and the operation unit.

The quantities of the work order operations are expressed in the operation unit.

• U-OPE conversion (field OPEWORCOE)

• Labor time set fac (field SETLABCOE)

This is the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center.

This coefficient applied to the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center.
This field is only available for entry if the labor work center is entered.

• OP UOM (field XOPEUOM)

• Remaining quantity (field EXTQTY)

This field indicates the expected quantity for this tracking product.

• Labor r-time fact (field OPELABCOE)

This is the coefficient applied to the planned operation time. It is used to obtain the operation time for the labor work center linked to the principal work center. This field is only available for entry if the labor work center is defined.

Operation times are subdivided as follows:

Proportional times are expressed for the production of an operation unit (and not in the stock unit of the finished product using the routing).

• Total actual quantity (field CPLQTY)

This field displays the total completed quantity, including the rejected quantity, expressed in the operation unit.

• Actual rejected qty. (field REJCPLQTY)

This field displays the actual rejected quantity.

The sum of the "quantity produced under quality control" plus the "rejected quantity" cannot exceed the Total completed quantity.

• Time unit (field TIMUOMCOD)

The time unit defines how time for the operations in this routing is expressed. The time unit can be 'hours' or 'minutes'.

It applies to the setup time, run time and the rate of all operations in the routing.

• Actual unit time (field CPLUNTTIM)

The unitary time is the actual operation time necessary for the production of a unit.

• Remaining stp. time (field EXTSETTIM)

The setting time is a fixed amount of time necessary to prepare the work center.
It is part of the work center load.
It is expressed in the time unit specified in the routing.

• Actual stp. time (field CPLSETTIM)

This is the actual setting time.
The setting time is a fixed amount of time necessary to prepare the work center.
It is part of the work center load. It is expressed in the time unit specified in the routing.

• Remaining run time (field EXTOPETIM)

The operation time is the time necessary to manufacture the product described in the routing.

The operating time:

• in hours or minutes (see the time unit),
• is expressed for 1, 100, 1,000 or a lot of units of the operation based on the management unit,
• can be proportional or fixed, based on the type of operation times.
  Example :
  Time unit = Hours
  Time type = Proportional
  Management unit = Time for 100
  Operating time = 2
  Operation unit = Kg
  Finished product unit = One
  Conversion coefficient DU-OU = 0.5
  The operating time equals 2 hours for 100 Kg. If the Work Order is launched for 1,000 units of finished product, the time necessary to produce this operation is 10 hours to obtain 500 Kg.

• Actual run time (field CPLOPETIM)

This is the actual operation time.
It is possible via a contextual button to enter start and end times.
In that case, the system automatically calculates the actual operation time.

The operating time:

• in hours or minutes (see the time unit),
• is expressed for 1, 100, 1000 or a lot of units of the operation based on the management unit,
• can be proportional or fixed based based on the operating time type.
  Example:
  Time unit = Hours
  Time type = proportional
  Management unit = Time for 100
  Operating time = 2
  Operating unit = Kg
  Finished product unit = Un
  REL-OPE conversion coefficient = 0.5
  The operation time is equal to 2 hours for 100 Kg. If the Work Order is launched for 1000 units of finished product, the time necessary to produce this operation is 10 hours to obtain 500 Kg.

• Close (field CLEFLG)

Use this field to specify whether the line must be closed or not ('Yes'/'No').

• Employee ID (field EMPNUM)

This field corresponds to the Labor operator.

• Message (field MSGNUM)

This field displays the information message linked to the operation tracking.
It belongs to the TABMSG table.
It is possible to enter an information message, whether the time unit is entered or not.

• Reject (field SCANUM1)

It is the information message concerning the rejected quantity.
It belongs to the TABSCA table of the scrap messages.

• Scheduling (field SCDCOD)

Scheduling determines the way in which routing operations follow each other. It can take the following values:

• Absolute successor. Position is at the end of the longest operation in the routing.
• Overlapping wait = lots. The following operation can start after a period of time corresponding to the number of lots manufactured during the processed operation.
• Overlapping wait = time. The next operation can start after a period of time equal to a given overlapping time.
• Overlapping wait = quantity. The next operation can start when a given quantity over the processed operation has been produced.
• Start synchronization. The next operation is synchronized to start at the same time as the processed operation.
• End synchronization. The next operation is synchronized to end at the same time as the processed operation.
• All order operations parallel. The next operation is synchronized to start at the same time as the first operation.
• Subcontract synchronization. Code used automatically when a subcontracted operation is distributed over several supplier orders. In this situation the operation is split up and this code is used to link the various components to a single operation.
• Simple successor. Position is just after the previous operation.

• Next operation (field NEXOPENUM)

The next operation is used to link the routing operation in a logical progress order describing the operating process.
This operation does not necessarily start at the end of the operation in process: the scheduling describes the sequencing mode of the operations.

The next operation must be different from the processed operation, and must be part of the operations of the processed routing.
The last operation of the routing must have available a next operation set to zero.

• Start date (field INFCAPSTR)

• End date (field INFCAPEND)

• Milestone (field DACMST)

This field defines the type of production tracking that applies to this operation, as follows:

• No. This operation is not tracked manually.
• Normal tracking. This operation is tracked normally.
• Range. This operation and all the previous non-tracked operations are tracked automatically until the first operation is found that is set to Normal tracking or is itself included in a range of operations.