Refer to documentation Implementation
Presentation
Prioritizing requests and resources
During the automatic assignment process, the system starts by sorting out the requests to be assigned by requirement date and priority (if this criteria is considered).
For resources, an algorithm runs on filter lines in order to find the orders available for assignment. If the quantity found on the orders of the first filter line is too small, the next lines are applied until the requirement quantity is fully covered, or until declaring that the assignment cannot be completed.
Examples:
Order | Date | Product | Quantity | Unit |
SOF | 30/06 | CD100 | 10 | Pallet of 10 boxes |
POF | 15/06 | CD100 | 100 | Boxes of 10 units |
POF | 20/06 | CD100 | 1,000 | Units |
Using one filter line and a single unit.
No new assignment can be created because there are different units linked to the SOF and the POF.
The first filter line uses a single unit, but the second filter line has no restrictions.
An assignment will be created between the SOF and the first POF, as no restriction applies to the second line.
Close
Fields
The following fields are present on this tab :
Block number 1
| The assignment rule is used to create a link between a requirement (sales order, material requirement, etc.) and a resource (work order, purchase order, etc.). |
| This long description is used as a title in screens and reports. By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.
|
| Short title used in the screens and reports. This title is recorded in your connection language. By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.
|
Back-to-back
| This field indicates if the assignment rule is used to have multiple links or not. |
Parameters
| This field indicates if the products including this assignment rule are taken into account in the automatic assignment processing. |
| This field indicates whether the assignments must evolve automatically upon order update or creation.
|
Horizon
| This field indicates if the assignment must be active only on a horizon. |
| Indicates in number of days the horizon on which the assignment is managed. |
|   |
Automatic adjustment
| Indicates if the assignment update must be done in real time upon requirement evolution. |
| Indicates if the forced assignments can be put into question in real time upon resource and requirement evolution. |
| Indicates if the assignment update must be done in real time upon resource evolution. |
Order priority considerations
| This field indicates if the priority in requirements must be taken into account. |
| This factor is a number of days to be applied so as to sort the requirements to be assigned. The factor is calculated as follows: (Priority code -1) * Priority factor The priority code is 1 for Normal, 2 for Urgent and 3 for Very urgent. For instance: Priority factor 10 Here, the request to be assigned in priority is the SOF number 2 for its fictive requirement date changes to 06/30 - 10 = 06/20. |
| This field indicates if the presence of shortages on requirements must be taken into account. |
| This factor is a number of days to be applied so as to sort the requirements to be assigned. The factor is calculated as follows: 1 * Priority factor = shift day number For instance: Priority factor 10 Here, the request to be assigned in priority is the SOF number 2 since its fictive requirement date changes to 06/30 - 10 = 06/20 due to the shortage quantity. |
|
|
|
Grid Supply priority
|
| Indicates whether the resource and requirement units must be equal for the automatic assignment. |
| Indicates whether the resource and requirement quantities must be equal for the automatic assignment. The limits expressed in percentage are used to select resources with quantities close to the requirement's. |
| Indicates the accepted limit between the requirement quantity and the resource quantity upon automatic assignment. |
|   |
| Indicates if the purchase orders to be assigned in priority are the priority supplier's. |
| Indicates whether the resource end date and the requirement date must be equal for the automatic assignment. The margins expressed in days are used to select resources around the requirement date. |
| Indicates the number of days accepted between the requirement date and the resource date upon automatic assignment. (Number of days before - or after + requirement) |
|   |
Close