This function is used to determine the production cost (PC) for a work order and to underline the variance between the actual cost and the standard cost (cost based on the data in the BOM) or the cost based on the work order data.
SEEINFOIf the processing is not performed in a simulation but in a actual situation, the work order must be closed.

The PC calculation can be carried out on a single work order or according to the conditions expressed in a filter in the SCOHEAD, SCOITM and MFGWIP tables.

The PC calculation is based on the WIPCOST table which is fed by input of the subcontract product receptions (material consumption). The standard cost variance records, the adjustment and the WIP balance can be created.

A print-out can be requested at the end of the calculation.

A certain number of inquiries are available to view the cost price history for a product, to compare the PC with respect to the other cost types for the site or for another site.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Selection

A site and then a work order must be specified.

In the Order no. field, 2 options can be accessed by right click:

  • Selection: this option displays the list of closed subcontract orders.
  • EO filter: displays a window used to do a selection using a filter on the SCOHEAD table of subcontract order header.
    The selection based on a filter is used to launch a calculation for the work orders that meet the filter criteria. For these choices the filter box is checked.
Variance origin

The basis for the calculation of the planned subcontract cost, must be specified:

  • Standard data: specifies that the planned PC will be determined using a standard basis (data of the routing and the BOM).
    Caution: the routing and the BOM must be of cost type.
  • Subcontract order: specifies that the planned PC will be created from the work order data.
Printing
  • No: No print-out will be proposed when the PC is calculated.
  • Detail: A detailed print-out of the PC will be proposed at the end of the calculation.
  • Summary: A print-out summing up the calculations will be suggested.
Flexible budget

The flexible budget flag is used to correct the calculation database planned with respect to the Planned/Actual ratio.

Selection

Simulation (field SIMFLG)
Cost calculation (field PRF1)

If this check box is selected, the subcontract orders whose PCs have never been calculated will be processed.

Cost update (field PRF2)

If this check box is selected, the subcontract orders whose PCs have already been calculated will also be processed. It is thus possible to re-calculate a PC after the first calculation.

Receiving site (field STOFCY)

Production site This is initialized by default with the normal production site for the user.

Order no. (field VCRNUM)

Subcontract order or filter number. It is possible:

  • to enter a specific EO reference.
  • to select a WEO (using the "Selection" contextual menu).
  • to introduce selection criteria (using the "Filter" contextual menu).

Printing

Report (field PRNCOD)

The printing of the cost price can be:
- deactivated
- detailed: (materials, services, overheads, sub-totals...)
- reduced to the summary (total of the price components of all the processed orders)

Update planned/actual ratio (field FLXBUD)

The flexible budget flag is used to correct the calculation database planned with respect to the Planned/Actual ratio.
Variance source (field ORIDEVCLC)

This field is used to specify the calculation basis for the planned production cost:

  • Standard data: specifies that the planned PCP will be determined using a standard basis (data of the routing and the BOM),
    SEEWARNING The type of route and the BOM must be cost.
  • WO data: this option is used to indicate that the planned production cost will be based on the Work Order data.
Print expected cost (field PRVCSTPRT)
Print of non-achieved planned (field EDIPRV)

Batch task

This function can be run in batch mode, but no dedicated standard task is delivered to run it.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation