At line 1 added 88 lines |
%%(display:none) |
{{{ |
WikiUp |
}}} |
/% |
[{TableOfContents }]\\ |
!!! Goal of this document\\ |
To define the parameter set for configuring the MRP planning behaviour. |
# __Planning Scenario__: "basket" in which the planning is set\\ |
# __M51 tab__: MRP main settings tab\\ |
# __Policies - M5A tab__: it refers to the planning policy\\ |
# __Planning parameters__: structure which assigns policies, lots and lead times to items\\ |
# __Source availability and source groups__: they are the fundamental components of the availability analysis\\ |
|
|
!!! Planning scenario\\ |
!! Introduction\\ |
The MRP is run and recorded in a scenario, so that many different MRPs may be planned in several different scenarios. This allows to "try" different situations and analyze their results. |
For example, an MRP may or may not consider the anticipated needs (forecasting and minimum stock), to test the minimum suggestions for satisfying only the sales orders; on the other hand, a scenario can include the next year forecast (budget) as the only anticipated need, in order to assess a budget purchase volume for suppliers. |
|
In the scenario, belonging to M5B tab, we can define these special behaviours: |
[* M5B - Scenari m5|MBDOC_OGG-TA_M5B]\\ |
|
|
!!! M51 tab: MRP basic setting\\ |
!! Introduction\\ |
This is the planning main tab, used by all the scenarios and setting some FUNDAMENTAL behaviour, as: |
* Whether to use a second breaking code besides the item (possible codes: order, provider, change exponent, configuration)\\ |
* Whether to consider working or calendar days\\ |
* Whether to consider a specific timetable for each provider\\ |
* Whether or not to write the excess quantity\\ |
* Which bill of material type to consider and whether to recalculate the low level code for each MRP\\ |
* Whether or not there are multiplant transfers\\ |
* Etc...\\ |
|
For a complete list of the possibilities please read the M51 tab help: |
[M51 - Pianificazione materiali|MBDOC_OGG-TA_M51]\\ |
|
|
!!! Planning policies: M5A tab\\ |
!! Introduction\\ |
This tab defines the planning policy, i.e. whether an item is planned when needed, at reorder point or it does not need any planning. |
It also: |
* Defines the needs grouping method used to define the single reorders.\\ |
* Configures the "missed plannings" allowed ("neglected sources").\\ |
* Allows to associate different group sources from that of the MRP.\\ |
* Defines which planned sources to use for the suggestions and their relevant needs.\\ |
* Allows to change some basic settings of M51 tab (only for the relevant items).\\ |
* Validates the use of the second breaking code defined at M51 level.\\ |
|
Please, read the tab help to understand the advantages offered by M5A tab |
[* M5A - Politica di riordino (1)|MBDOC_OGG-TA_M5A]\\ |
|
!!! Planning parameters: policies, lots, lead time\\ |
!! Introduction\\ |
The planning parameters are divided in four homogeneous information groups: |
# __Planning policy__, which belongs to M5A tab\\ |
# __Allocation percentage of this policy__: if only a policy is defined, it is 100%, otherwise you must indicate the percentage for each policy used (the total must be 100%)\\ |
# __Lead times__ used to determine the suggestions dates (in days):\\ |
## ''Fixed'': time between when the order is issued (suggestion date) and the start of production. It may indicate the set-up time, but also the time needed to "pass" the order to the production department.\\ |
## ''Variable'': days required to make a standard lot. NOTE: the standard lot is defined in the item file; it is not associated to any minimum, multiple or maximum lot!\\ |
## ''Correction'': time between the end date planned for the order and the date for which the item is needed (source/availability date). It represents the days required to test the goods or some backup days to guarantee availability for the shipping.\\ |
These times are not mandatory. |
# Quantities used for lot-sizing\\ |
## ''Minimum lot'': lot size value if under the minimum lot. It indicates a reorder economizing need\\ |
## ''Multiple lot'': multiple value of lot size. It is a material "packaging" constraint\\ |
## ''Maximum lot'': value to suggest a supply split among different orders. Also this is a "packaging" constraint.\\ |
|
!! Structure of planning parameters\\ |
These parameters are in a file structured in N levels. |
* At level 1 there are the parameters defined for the item-plant pair: here you can indicate the lots, lead times and policy assigned to an item.\\ |
* At the higher levels we can assign the parameters to item attributes, such as the material class.\\ |
|
__NOTE__: these N levels may be splitted in another reference code for planning, set in M51 tab, such as the supplier object (E - FOR). This allows, for example, to set different lead times on the same item for different suppliers. |
|
|
!!! Sources and source groups\\ |
!! Introduction\\ |
Sources are the foundations of the availability analysis; they represent events, documents and other things that affect the item quantities in stock now or in the future. |
They are set in M5F and M5E tabs and are very flexible, allowing to make use of any data stored in the server which brings information on an item and a quantity. |
There are existing sources (without date, M5E tab) and future sources (with date, M5F tab); they may be positive (production of material) and negative (lack, or use, of material). |
|
They are assembled in "source groups": a source group is a set of sources that represents a scenario of needs and coverages. |
It's up to the developer to define these source groups in a way that is consistent with the specific task it is created for. |
|
Please, read M5E and M5F tab helps for a thorough understanding of the sources. |
[* M5E - Fonti esistenti di impegno/disponibilità|MBDOC_OGG-TA_M5E]\\ |
[* M5F - Fonti future di impegno/disp.|MBDOC_OGG-TA_M5F]\\ |