Refer to documentation Implementation
The component requirement calculation is subdivided into two stages:
Presentation
This first part is used to supply the following selection criteria:
It is possible to view the results of the calculation on the screen and/or on paper.
Close
Fields
The following fields are present on this tab :
Block number 1
| Use this field to define the storage and/or production site. The site defined on the user record is displayed by default but can be amended.
|
| The code type is used to draw the distinction between the BOMs intended for sales use, those used for manufacturing and those used for sub-contracting. |
| Select the alternative (or enter using 2 digits) for which the processing will be carried out. |
| Only the BOMs links valid at this date are processed in the calculation.
|
| This field indicates the ID of the component product. |
|   |
|   |
| This field is used to indicate the calculation quantity. |
| This field indicates the product management unit in which are expressed:
This information is always displayed, regardless of the transaction used. It cannot be modified. |
Processing
| Requested processing type. |
| Select the classification criteria for the display of the returned lines. |
| If this box is ticked, the available stock of a semi-finished component will be taken into account in the BOM descent: in the processing of the first level going through a phantom product (if there is insufficient available), in the processing of multi-level in descending down for the missing quantity. |
Display
|   |
|   |
|   |
|   |
|   |
|   |
Issues
| The result of the process will be displayed on the screen if this indicator is set. |
| Select this check box to print a report of the MRP or MPS calculations at the end of the processing run. |
Close
Presentation
Display of the components depending on the calculation level
For each component, the system calculates:
Close
Fields
The following fields are present on this tab :
|   |
| This field indicates the ID of the component product. |
|   |
|   |
| Number of BOM levels above the component. |
|   |
|   |
|   |
|   |
| This field displays the quantity related to the requirement. |
| This field indicates the product management unit in which are expressed:
This information is always displayed, regardless of the transaction used. It cannot be modified. |
| This field indicates the shortage quantity. |
| This field displays the available quantity expressed in the stock unit of the components. |
|   |
|   |
|   |
| This field indicates the lead-time asked for the reception of the products, displayed in number of days. |
|   |
| Use the status to change product availability. The titles in the local menu can be set up and managed as follows:
Non blocking and blocking messages according to the context and status:
|
| This field indicates the status on the shop floor of the preparation of the operations and tools in this routing. This field will be set to one of the following values:
|
| This checkbox specifies that the site is a purchase site. |
| When checked, this box specifies that the site is a production site. |
|   |
Close
Action icon
Fields
The following fields are present on this tab :
| Each of the lines in the grid corresponds to a line in the log file. |
In addition to the generic error messages, the following messages can appear during the entry :
The entered code does not exist in the BOM code table.
The entered BOM code is linked to a site that is different from the one that has been entered.
The parent product for which the calculation should be launched does not exist in the product table
The parent product for which the calculation should be launched does not have any BOM in the BOM code specified above.
The parent product entered in the grid is already present on another line.
The BOM of the parent product for which the calculation should be launched is not valid on the reference date entered.
The log file following the calculation can contain the following messages:
"Problem on erasing the temporary file"
The transaction used to erase temporary records is cancelled.
The specified parent product has no valid link on the reference date entered. (only for the last level calculation)
A problem has occurred when creating the work file: please try again.